Never mind. Found it: http://wiki.eclipse.org/Submitting_M2E_marketplace_entries ----- Original Message ----- > Hey folks, > > Does anybody know how I go about getting the SwitchYard tools to show > up in m2e's discovery list? > > Thanks in advance, > Rob > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

> you got a stable URL for switchyard plugins yet to submit ? > > We need to be careful which we add here :) I don't quite follow. I was assuming nightly would work (i.e. http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/). It doesn't appear that a "version" is required on the catalog entry and the documentation is doesn't specify anything other than, "It is assumed that contents of provided p2 repository will not change in the future unless corresponding m2e marketplace catalog entry is removed or amended," which I interpret as, some version of the feature and bundle must be available from the specified repository. Another thing that was unclear was whether or not my m2e extension needs to be packaged separately from the rest of the SwitchYard tooling. Rob _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

You cant put a nightly build updatesite which changes and can break any minute into the m2e repository used by all users of eclipse. That's insane - you want a *stable* set of bits up there. /max On Feb 22, 2012, at 3:52 PM, Rob Cernich wrote: >> you got a stable URL for switchyard plugins yet to submit ? >> >> We need to be careful which we add here :) > > I don't quite follow. I was assuming nightly would work (i.e. http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/). It doesn't appear that a "version" is required on the catalog entry and the documentation is doesn't specify anything other than, "It is assumed that contents of provided p2 repository will not change in the future unless corresponding m2e marketplace catalog entry is removed or amended," which I interpret as, some version of the feature and bundle must be available from the specified repository. > > Another thing that was unclear was whether or not my m2e extension needs to be packaged separately from the rest of the SwitchYard tooling. > > Rob > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

guys we are working on beta1 - that seem to be a fine place and time to push such a thing aint it ? /max On Feb 22, 2012, at 6:40 PM, Nick Boldt wrote: > So then we take the nightly site, move it a temporary location that > won't be overwritten by subsequent nightly spins, and tell QE to go > wail > on it (Feb 23). > > Then, after QE vets it as being stable enough and safe enough to > release > (Mar 12), it gets moved to here: > > http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/ > > That URL currently contains the M5 bits (which does not yet include > Switchyard 0.4). > > It will persist there until such time as CR1 is done, and then > we'll > replace the site w/ the CR1 bits. > > Isn't that what we do for the JBoss Tools (Core) [1] entry in the > Eclipse Marketplace today? > > [1] http://marketplace.eclipse.org/node/121986 > > N > > On 02/22/2012 10:33 AM, Max Rydahl Andersen wrote: >> You cant put a nightly build updatesite which changes and can >> break any minute into the m2e repository used by all users of >> eclipse. >> >> That's insane - you want a *stable* set of bits up there. >> >> /max >> >> On Feb 22, 2012, at 3:52 PM, Rob Cernich wrote: >> >>>> you got a stable URL for switchyard plugins yet to submit ? >>>> >>>> We need to be careful which we add here :) >>> >>> I don't quite follow. I was assuming nightly would work (i.e. >>> http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/). >>> It doesn't appear that a "version" is required on the catalog >>> entry and the documentation is doesn't specify anything other >>> than, "It is assumed that contents of provided p2 repository >>> will not change in the future unless corresponding m2e >>> marketplace catalog entry is removed or amended," which I >>> interpret as, some version of the feature and bundle must be >>> available from the specified repository. >>> >>> Another thing that was unclear was whether or not my m2e >>> extension needs to be packaged separately from the rest of the >>> SwitchYard tooling. >>> >>> Rob >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev > > _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jbosstools-dev

Well, then, if we target the QE cycle for the SOA Tooling site to start "in a week or two", you could have your Beta1 site (including 0.4.0.Final) out by the end of March. Does that work? It'd be very much like the Eclipse release train model with +0, +1, +2, +3 tier projects [1], and the accompanying date offsets needed to have everyone align with their upstream bits. (Teiid is also a bit behind -- I'd expected that they'd already be testing w/ the SR1-M target platform so when I flipped the switch on them to start building against that, they'd build fine, but they're broken right now. They too are a +3 project to JBT Core's +0.) [1] http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan Adding John, Mark, Burr, and Len so they're in the loop on this "staggered release" idea and suggested 2 week offset. I have no idea if that works from their point of view. On 02/22/2012 01:19 PM, Rob Cernich wrote: > I think I'd want one of our "Final" releases to show up there. > That said, 0.4 won't be complete for another week or two and I > don't remember whether or not the m2e extension was in 0.3. > > I'm happy to wait. > > ----- Original Message ----- >> guys we are working on beta1 - that seem to be a fine place and >> time >> to push such a thing aint it ? >> >> /max >> >> On Feb 22, 2012, at 6:40 PM, Nick Boldt wrote: >> >>> So then we take the nightly site, move it a temporary location >>> that >>> won't be overwritten by subsequent nightly spins, and tell QE to >>> go >>> wail >>> on it (Feb 23). >>> >>> Then, after QE vets it as being stable enough and safe enough to >>> release >>> (Mar 12), it gets moved to here: >>> >>> http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/ >>> >>> That URL currently contains the M5 bits (which does not yet >>> include >>> Switchyard 0.4). >>> >>> It will persist there until such time as CR1 is done, and then >>> we'll >>> replace the site w/ the CR1 bits. >>> >>> Isn't that what we do for the JBoss Tools (Core) [1] entry in the >>> Eclipse Marketplace today? >>> >>> [1] http://marketplace.eclipse.org/node/121986 >>> >>> N >>> >>> On 02/22/2012 10:33 AM, Max Rydahl Andersen wrote: >>>> You cant put a nightly build updatesite which changes and can >>>> break any minute into the m2e repository used by all users of >>>> eclipse. >>>> >>>> That's insane - you want a *stable* set of bits up there. >>>> >>>> /max >>>> >>>> On Feb 22, 2012, at 3:52 PM, Rob Cernich wrote: >>>> >>>>>> you got a stable URL for switchyard plugins yet to submit ? >>>>>> >>>>>> We need to be careful which we add here :) >>>>> >>>>> I don't quite follow. I was assuming nightly would work (i.e. >>>>> http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/). >>>>> It doesn't appear that a "version" is required on the catalog >>>>> entry and the documentation is doesn't specify anything other >>>>> than, "It is assumed that contents of provided p2 repository >>>>> will not change in the future unless corresponding m2e >>>>> marketplace catalog entry is removed or amended," which I >>>>> interpret as, some version of the feature and bundle must be >>>>> available from the specified repository. >>>>> >>>>> Another thing that was unclear was whether or not my m2e >>>>> extension needs to be packaged separately from the rest of the >>>>> SwitchYard tooling. >>>>> >>>>> Rob >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> jbosstools-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>>> >>>>> >>>> >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools& Dev Studio >>> http://nick.divbyzero.com >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

yeah - it think Nick mixed this up with the bigger overall scenario ;) For this specific feature something simpler should be doable. /max > Please don't slip your release on account of me. The SY tooling is a hair beyond a prototype at this point, and I don't think it matters whether it makes it into this milestone or the next. Furthermore, I've been trying to keep the SY tools loosely coupled with JBT and so they can be installed atop any build (I don't think it requires any JBT plugins; m2 facet integration is supported, but optional). > > I don't even know if the SY tools are on anybody's radar at the moment. > > Adding Keith to CC. > > ----- Original Message ----- >> Well, then, if we target the QE cycle for the SOA Tooling site to >> start >> "in a week or two", you could have your Beta1 site (including >> 0.4.0.Final) out by the end of March. >> >> Does that work? It'd be very much like the Eclipse release train >> model >> with +0, +1, +2, +3 tier projects [1], and the accompanying date >> offsets >> needed to have everyone align with their upstream bits. >> >> (Teiid is also a bit behind -- I'd expected that they'd already be >> testing w/ the SR1-M target platform so when I flipped the switch on >> them to start building against that, they'd build fine, but they're >> broken right now. They too are a +3 project to JBT Core's +0.) >> >> [1] http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan >> >> Adding John, Mark, Burr, and Len so they're in the loop on this >> "staggered release" idea and suggested 2 week offset. I have no idea >> if >> that works from their point of view. >> >> On 02/22/2012 01:19 PM, Rob Cernich wrote: >>> I think I'd want one of our "Final" releases to show up there. >>> That said, 0.4 won't be complete for another week or two and I >>> don't remember whether or not the m2e extension was in 0.3. >>> >>> I'm happy to wait. >>> >>> ----- Original Message ----- >>>> guys we are working on beta1 - that seem to be a fine place and >>>> time >>>> to push such a thing aint it ? >>>> >>>> /max >>>> >>>> On Feb 22, 2012, at 6:40 PM, Nick Boldt wrote: >>>> >>>>> So then we take the nightly site, move it a temporary location >>>>> that >>>>> won't be overwritten by subsequent nightly spins, and tell QE to >>>>> go >>>>> wail >>>>> on it (Feb 23). >>>>> >>>>> Then, after QE vets it as being stable enough and safe enough to >>>>> release >>>>> (Mar 12), it gets moved to here: >>>>> >>>>> http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/ >>>>> >>>>> That URL currently contains the M5 bits (which does not yet >>>>> include >>>>> Switchyard 0.4). >>>>> >>>>> It will persist there until such time as CR1 is done, and then >>>>> we'll >>>>> replace the site w/ the CR1 bits. >>>>> >>>>> Isn't that what we do for the JBoss Tools (Core) [1] entry in the >>>>> Eclipse Marketplace today? >>>>> >>>>> [1] http://marketplace.eclipse.org/node/121986 >>>>> >>>>> N >>>>> >>>>> On 02/22/2012 10:33 AM, Max Rydahl Andersen wrote: >>>>>> You cant put a nightly build updatesite which changes and can >>>>>> break any minute into the m2e repository used by all users of >>>>>> eclipse. >>>>>> >>>>>> That's insane - you want a *stable* set of bits up there. >>>>>> >>>>>> /max >>>>>> >>>>>> On Feb 22, 2012, at 3:52 PM, Rob Cernich wrote: >>>>>> >>>>>>>> you got a stable URL for switchyard plugins yet to submit ? >>>>>>>> >>>>>>>> We need to be careful which we add here :) >>>>>>> >>>>>>> I don't quite follow. I was assuming nightly would work (i.e. >>>>>>> http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/). >>>>>>> It doesn't appear that a "version" is required on the catalog >>>>>>> entry and the documentation is doesn't specify anything other >>>>>>> than, "It is assumed that contents of provided p2 repository >>>>>>> will not change in the future unless corresponding m2e >>>>>>> marketplace catalog entry is removed or amended," which I >>>>>>> interpret as, some version of the feature and bundle must be >>>>>>> available from the specified repository. >>>>>>> >>>>>>> Another thing that was unclear was whether or not my m2e >>>>>>> extension needs to be packaged separately from the rest of the >>>>>>> SwitchYard tooling. >>>>>>> >>>>>>> Rob >>>>>>> _______________________________________________ >>>>>>> jbosstools-dev mailing list >>>>>>> jbosstools-dev(a)lists.jboss.org >>>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> jbosstools-dev mailing list >>>>>> jbosstools-dev(a)lists.jboss.org >>>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>>> >>>>> -- >>>>> Nick Boldt :: JBoss by Red Hat >>>>> Productization Lead :: JBoss Tools& Dev Studio >>>>> http://nick.divbyzero.com >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> jbosstools-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>>> >>>>> >>>> >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>> >> >> -- >> Nick Boldt :: JBoss by Red Hat >> Productization Lead :: JBoss Tools& Dev Studio >> http://nick.divbyzero.com >>

(Added Ken and Anne-Louise to the cc list) The current released version of SOA-P is 5.2 - this release is only supported with JBDS 4.1.1 (4.1.2, I guess actually). The first version of SOA-P that will support JBDS 5 is SOA-P 5.3 - and we are several weeks away from a beta-ready build of SOA-P 5.3. So - I think that the ~2 week delay for SOA tooling with JBDS 5.0.beta1 is not an issue.

Ken - would you agree? -- Len ------------------------------------------------------------------------ *From: *"Nick Boldt" <nboldt(a)redhat.com&gt; *To: *"Rob Cernich" <rcernich(a)redhat.com&gt; *Cc: *"Max Rydahl Andersen" <manderse(a)redhat.com&gt;, "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org&gt;, "Len DiMaggio" <ldimaggi(a)redhat.com&gt;, "Mark Yarborough" <myarboro(a)redhat.com&gt;, "John Graham" <jgraham(a)redhat.com&gt;, "Burr Sutter" <bsutter(a)redhat.com&gt; *Sent: *Wednesday, February 22, 2012 1:27:12 PM *Subject: *Slip the release of JBT/JBDS SOA Tooling to a couple weeks after JBT/JBDS Core? (was Re: [jbosstools-dev] Adding Plugins to m2e Discovery Mechanism) Well, then, if we target the QE cycle for the SOA Tooling site to start "in a week or two", you could have your Beta1 site (including 0.4.0.Final) out by the end of March. Does that work? It'd be very much like the Eclipse release train model with +0, +1, +2, +3 tier projects [1], and the accompanying date offsets needed to have everyone align with their upstream bits. (Teiid is also a bit behind -- I'd expected that they'd already be testing w/ the SR1-M target platform so when I flipped the switch on them to start building against that, they'd build fine, but they're broken right now. They too are a +3 project to JBT Core's +0.) [1] http://wiki.eclipse.org/Indigo/Simultaneous_Release_Plan Adding John, Mark, Burr, and Len so they're in the loop on this "staggered release" idea and suggested 2 week offset. I have no idea if that works from their point of view. On 02/22/2012 01:19 PM, Rob Cernich wrote: > I think I'd want one of our "Final" releases to show up there. That said, 0.4 won't be complete for another week or two and I don't remember whether or not the m2e extension was in 0.3. > > I'm happy to wait. > > ----- Original Message ----- >> guys we are working on beta1 - that seem to be a fine place and time >> to push such a thing aint it ? >> >> /max >> >> On Feb 22, 2012, at 6:40 PM, Nick Boldt wrote: >> >>> So then we take the nightly site, move it a temporary location that >>> won't be overwritten by subsequent nightly spins, and tell QE to go >>> wail >>> on it (Feb 23). >>> >>> Then, after QE vets it as being stable enough and safe enough to >>> release >>> (Mar 12), it gets moved to here: >>> >>> http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooling/ >>> >>> That URL currently contains the M5 bits (which does not yet include >>> Switchyard 0.4). >>> >>> It will persist there until such time as CR1 is done, and then >>> we'll >>> replace the site w/ the CR1 bits. >>> >>> Isn't that what we do for the JBoss Tools (Core) [1] entry in the >>> Eclipse Marketplace today? >>> >>> [1] http://marketplace.eclipse.org/node/121986 >>> >>> N >>> >>> On 02/22/2012 10:33 AM, Max Rydahl Andersen wrote: >>>> You cant put a nightly build updatesite which changes and can >>>> break any minute into the m2e repository used by all users of >>>> eclipse. >>>> >>>> That's insane - you want a *stable* set of bits up there. >>>> >>>> /max >>>> >>>> On Feb 22, 2012, at 3:52 PM, Rob Cernich wrote: >>>> >>>>>> you got a stable URL for switchyard plugins yet to submit ? >>>>>> >>>>>> We need to be careful which we add here :) >>>>> >>>>> I don't quite follow. I was assuming nightly would work (i.e. >>>>> http://download.jboss.org/jbosstools/updates/nightly/soa-tooling/trunk/). >>>>> It doesn't appear that a "version" is required on the catalog >>>>> entry and the documentation is doesn't specify anything other >>>>> than, "It is assumed that contents of provided p2 repository >>>>> will not change in the future unless corresponding m2e >>>>> marketplace catalog entry is removed or amended," which I >>>>> interpret as, some version of the feature and bundle must be >>>>> available from the specified repository. >>>>> >>>>> Another thing that was unclear was whether or not my m2e >>>>> extension needs to be packaged separately from the rest of the >>>>> SwitchYard tooling. >>>>> >>>>> Rob >>>>> _______________________________________________ >>>>> jbosstools-dev mailing list >>>>> jbosstools-dev(a)lists.jboss.org >>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>>>> >>>>> >>>> >>>> >>>> _______________________________________________ >>>> jbosstools-dev mailing list >>>> jbosstools-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools& Dev Studio >>> http://nick.divbyzero.com >>> _______________________________________________ >>> jbosstools-dev mailing list >>> jbosstools-dev(a)lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >>> >>> >> >> >> _______________________________________________ >> jbosstools-dev mailing list >> jbosstools-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jbosstools-dev >> -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com -- Len DiMaggio (ldimaggi(a)redhat.com) JBoss by Red Hat 314 Littleton Road Westford, MA 01886 USA tel: 978.392.3179 cell: 781.472.9912 http://www.redhat.com http://community.jboss.org/people/ldimaggio <http://www.redhat.com>