On Mon, Sep 24, 2012 at 6:40 AM, Igor Fedorenko <i...@ifedorenko.com> wrote: > You should be able to set custom discovery catalog url using > -Dm2e.discovery.url=<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, Benson Margulies wrote: >> >> On Sun, Sep 23, 2012 at 7:34 PM, Jason van Zyl <ja...@tesla.io> 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 repository actually existed. But this is still a pain in the >>> ass, >>> I'm happy to provide CI and publishing for those that want to use them >>> but >>> for now let's just allow connector authors to make pull requests to >>> update >>> this file: >>> >>> >>> https://github.com/tesla/m2e-discovery-catalog/blob/master/org.eclipse.m2e.discovery.oss/connectors.xml >>> >>> When you make a pull request it is assumed that you've tested your >>> connector >>> with the catalog entry you want to publish. >> >> >> To be more exact, in my copy of Juno, the catalog URL is sitting in a >> read-only text box, so I can't tell it to use the one I've just asked >> you to pull. >> >> >>> >>> The jobs are already setup on the build grid to publish snapshot catalogs >>> that can be tested: >>> >>> http://ci.tesla.io:8080/view/m2e/job/m2eclipse-discovery-catalog-stage/ >>> >>> So once your pull request is processed the staging catalog can be >>> published >>> and if that's all good we'll publish the release catalog. >>> >>> Igor and I will try and put together the one pager to do this. But go >>> ahead >>> and make pull requests for now and we'll flesh out the process as we go. >>> >>> On Sep 23, 2012, at 10:17 AM, Benson Margulies <bimargul...@gmail.com> >>> wrote: >>> >>> 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 marketplace. >>> >>> I didn't save the email, and I never heard back from him. What's the >>> current status and procedure to publish this sort of thing so that >>> people can find it? >>> _______________________________________________ >>> m2e-users mailing list >>> m2e-users@eclipse.org >>> https://dev.eclipse.org/mailman/listinfo/m2e-users >>> >>> >>> Thanks, >>> >>> Jason >>> >>> ---------------------------------------------------------- >>> Jason van Zyl >>> Founder & CTO, Sonatype >>> Founder, Apache Maven >>> http://twitter.com/jvanzyl >>> --------------------------------------------------------- >>> >>> {script:nopre:"/Users/jvanzyl/signature/signature.sh"} >>> >>> >>> >>> >>> >>> >>> _______________________________________________ >>> m2e-users mailing list >>> m2e-users@eclipse.org >>> https://dev.eclipse.org/mailman/listinfo/m2e-users >>> >> _______________________________________________ >> m2e-users mailing list >> m2e-users@eclipse.org >> https://dev.eclipse.org/mailman/listinfo/m2e-users >> > _______________________________________________ > m2e-users mailing list > m2e-users@eclipse.org > https://dev.eclipse.org/mailman/listinfo/m2e-users _______________________________________________ m2e-users mailing list m2e-users@eclipse.org https://dev.eclipse.org/mailman/listinfo/m2e-users
