Hi,
I have updated all the entries in the catalog that I have access to, and the build job for the staged version of the catalog is passing:
Users who want to try the updated version of the catalog can do so by adding
-Dm2e.discovery.url="" href="http://download.eclipse.org/technology/m2e/discovery/directory-test-1.1.xml">http://download.eclipse.org/technology/m2e/discovery/directory-test-1.1.xml
to the end of your eclipse.ini file. For reference your eclipse.ini should look something like this:
With some feedback from users we can publish this as the release version of the catalog in a week or so.
That url is configurable if you specify (in eclipse.ini):
-Dm2e.discovery.url="">
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=337912.
/Anders
On Mon, Sep 24, 2012 at 2:26 AM, Benson Margulies <bimargulies@xxxxxxxxx> wrote:
On Sun, Sep 23, 2012 at 7:34 PM, Jason van Zyl <jason@xxxxxxxx> 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 <bimargulies@xxxxxxxxx>
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@xxxxxxxxxxx
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@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder & CTO, Sonatype
Founder, Apache Maven
{script:nopre:"/Users/jvanzyl/signature/signature.sh"}
|
