OK, I have now precisely followed the instructions, 1.1 and all, and
had it work.
The sample in the doc would be easier to follow if it looked like:
-Dm2e.discovery.url=file:///path-to-m2e-discovery-catalog/org.eclipse.m2e.discovery.oss/target/classes/catalog-1.1.xml
_
On Mon, Sep 24, 2012 at 2:22 PM, Jason van Zyl wrote:
> So you were able to build the catalog and try it with the instructions here:
>
> https://github.com/tesla/m2e-discovery-catalog
These instructions still call for supplying a catalog XML file to a
property that appears to require a discovery
Ok. But you responded to my mail. :-)
/Anders
On Thu, Sep 27, 2012 at 5:28 PM, Benson Margulies wrote:
> On Thu, Sep 27, 2012 at 10:55 AM, Anders Hammar wrote:
>>> Are we good here? Do you need to read me write that it also worked
>>> with the 1.1 version of the jar?
>>
>> I don't know; you tel
On Thu, Sep 27, 2012 at 10:55 AM, Anders Hammar wrote:
>> Are we good here? Do you need to read me write that it also worked
>> with the 1.1 version of the jar?
>
> I don't know; you tell me. You asked for help configuring m2e to use a
> different catalog file. I told you how to do that.
Anders,
> Are we good here? Do you need to read me write that it also worked
> with the 1.1 version of the jar?
I don't know; you tell me. You asked for help configuring m2e to use a
different catalog file. I told you how to do that.
/Anders
>
> On Tue, Sep 25, 2012 at 12:21 PM, Anders Hammar wrote:
>>
Are we good here? Do you need to read me write that it also worked
with the 1.1 version of the jar?
On Tue, Sep 25, 2012 at 12:21 PM, Anders Hammar wrote:
> That url is configurable if you specify (in eclipse.ini):
> -Dm2e.discovery.url=/some/url/
>
> See https://bugs.eclipse.org/bugs/show_bug.cg
That url is configurable if you specify (in eclipse.ini):
-Dm2e.discovery.url=/some/url/
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=337912.
/Anders
On Mon, Sep 24, 2012 at 2:26 AM, Benson Margulies wrote:
> On Sun, Sep 23, 2012 at 7:34 PM, Jason van Zyl wrote:
>> I automated everything
On Mon, Sep 24, 2012 at 2:22 PM, Jason van Zyl wrote:
> So you were able to build the catalog and try it with the instructions here:
>
> https://github.com/tesla/m2e-discovery-catalog
>
> If you can verify that then I'll merge the pull request.
Well, I didn't use the 1.1 jar, I used the plain jar
So you were able to build the catalog and try it with the instructions here:
https://github.com/tesla/m2e-discovery-catalog
If you can verify that then I'll merge the pull request.
On Sep 24, 2012, at 2:11 PM, Benson Margulies wrote:
> The good news is that the catalog entry now works right. I
The good news is that the catalog entry now works right. If you want
any other testing from me before pulling my pull request, please let
me know.
On Mon, Sep 24, 2012 at 1:24 PM, Benson Margulies wrote:
> On Mon, Sep 24, 2012 at 12:06 PM, Jason van Zyl wrote:
>> Trying these instructions an
On Mon, Sep 24, 2012 at 12:06 PM, Jason van Zyl wrote:
> Trying these instructions and I'll work through them with you until you can
> test your connector:
>
> https://github.com/tesla/m2e-discovery-catalog/README.md
That's a dead link. On the other hand, as soon as I manually install
checkstyle
Sorry, go to this URL:
https://github.com/tesla/m2e-discovery-catalog
I'm in IRC.
On Sep 24, 2012, at 12:06 PM, Jason van Zyl wrote:
> Trying these instructions and I'll work through them with you until you can
> test your connector:
>
> https://github.com/tesla/m2e-discovery-catalog/README.
Trying these instructions and I'll work through them with you until you can
test your connector:
https://github.com/tesla/m2e-discovery-catalog/README.md
On Sep 24, 2012, at 9:58 AM, Benson Margulies wrote:
> On Mon, Sep 24, 2012 at 9:56 AM, Matthew Piggott
> wrote:
>> I think you misread it
On Mon, Sep 24, 2012 at 9:56 AM, Matthew Piggott wrote:
> I think you misread it: the repository does not contain a dependency of what
> you're installing.
OK, this turns on the question of 'the repository'. Which repository?
What I thought we had done was add some metadata to the
m2e-code-qualit
I think you misread it: the repository does not *contain *a dependency of
what you're installing.
On 24 September 2012 09:53, Benson Margulies wrote:
> On Mon, Sep 24, 2012 at 9:44 AM, Matthew Piggott
> wrote:
> > Your repository doesn't contain a dependency.
>
> What would that consist of? The
On Mon, Sep 24, 2012 at 9:44 AM, Matthew Piggott wrote:
> Your repository doesn't contain a dependency.
What would that consist of? The MANIFEST clearly has a dependency, as
per the error below. What is a repository dependency?
>
> On 24 September 2012 08:28, Benson Margulies wrote:
>>
>> Once
Your repository doesn't contain a dependency.
On 24 September 2012 08:28, Benson Margulies wrote:
> Once upon a time, I thought you all helped me set up the metadata on
> these plugins to install their corresponding underlying plugins. It
> seems to have gone pear-shaped. Advice? Other than this
Once upon a time, I thought you all helped me set up the metadata on
these plugins to install their corresponding underlying plugins. It
seems to have gone pear-shaped. Advice? Other than this, all seems
good to go with my pull request.
Operation details
Cannot complete the install because one or
java.io.IOException: Unexpected content: no directory available
at
org.eclipse.equinox.internal.p2.discovery.compatibility.DirectoryParser.parse(DirectoryParser.java:57)
at
org.eclipse.equinox.internal.p2.discovery.compatibility.RemoteBundleDiscoveryStrategy$1.process(RemoteBundle
On Mon, Sep 24, 2012 at 6:40 AM, Igor Fedorenko wrote:
> You should be able to set custom discovery catalog url using
> -Dm2e.discovery.url= eclipse jvm system property.
Gee, a schema would be nice. The file URL works fine in a browser.
>
>
> --
> Regards,
> Igor
>
>
> On 12-09-23 9:26 PM, Benso
On Mon, Sep 24, 2012 at 6:40 AM, Igor Fedorenko wrote:
> -Dm2e.discovery.url=
I tried this with a file URL, and clicking on the "open catalog"
button pops up 'failed to discover all connectors.' and shows nothing.
Any way to find out what's on its mind?
__
You should be able to set custom discovery catalog url using
-Dm2e.discovery.url= eclipse jvm system property.
--
Regards,
Igor
On 12-09-23 9:26 PM, Benson Margulies wrote:
On Sun, Sep 23, 2012 at 7:34 PM, Jason van Zyl wrote:
I automated everything and then ran into problems with the update
On Sun, Sep 23, 2012 at 7:34 PM, Jason van Zyl wrote:
> I automated everything and then ran into problems with the update sites not
> being available. I originally tried pull in catalog entries from source
> repositories and I did that so I could build and publish the entries to make
> sure the re
On Sun, Sep 23, 2012 at 7:34 PM, Jason van Zyl wrote:
> I automated everything and then ran into problems with the update sites not
> being available. I originally tried pull in catalog entries from source
> repositories and I did that so I could build and publish the entries to make
> sure the re
I automated everything and then ran into problems with the update sites not
being available. I originally tried pull in catalog entries from source
repositories and I did that so I could build and publish the entries to make
sure the repository actually existed. But this is still a pain in the a
Back in June or July, I received email from JvZ about
https://github.com/organizations/m2e-code-quality and the marketplace.
The upshot, as best I recall, was that something interesting was
coming that it we would want to incorporate into the plugin set to
make it easier to get it into the marketpl
26 matches
Mail list logo
