On Mon, Oct 8, 2012 at 10:51 AM, Jason van Zyl <ja...@tesla.io> wrote: > It's continuous delivery. Builds happen via CI, they get deployed to Nexus > and you pick the one you deem release worthy to go into the catalog by > making a pull request to change the catalog. It will get more sophisticated > but this is what it is for now. I will change the triggers so that a build > will happen upon every commit.
OK, thanks. I'll document this for the other M2E committer(s). > > On Oct 8, 2012, at 10:47 AM, Benson Margulies <bimargul...@gmail.com> wrote: > > Jason, > > What's your model of 'releases' for plugins connected to your > structure? How does someone who works on the plugin trigger the > process on your end? > > --benson > _______________________________________________ > 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 > --------------------------------------------------------- > > In short, man creates for himself a new religion of a rational > and technical order to justify his work and to be justified in it. > > -- Jacques Ellul, The Technological Society > > > > > > > _______________________________________________ > 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
