Component leads, please tag your repositories! $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is called jbosstools, also often called origin $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD $ git push jbosstools jbosstools-4.3.0.Beta1

Le 22 juin 2015 à 16:38, Nick Boldt <nboldt(a)redhat.com&gt; a écrit : git push jbosstools jbosstools-4.3.0.Beta1

Component leads, please tag your repositories! $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is called jbosstools, also often called origin $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD $ git push jbosstools jbosstools-4.3.0.Beta1 -- 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

Do you mean this? http://download.jboss.org/jbosstools/static/mars/development/updates/core...

On 06/23/2015 01:10 PM, Max Rydahl Andersen wrote: > remind me where I can get the list of repo, sha-1 and i'll make this > happen on all of them. > > /max > >> Component leads, please tag your repositories! >> >> $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is >> called jbosstools, also often called origin >> $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD >> $ git push jbosstools jbosstools-4.3.0.Beta1 >> >> >> -- >> 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 > > > /max > http://about.me/maxandersen -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

On 23 Jun 2015, at 21:32, Max Rydahl Andersen wrote: > On 23 Jun 2015, at 21:13, Nick Boldt wrote: > >> Do you mean this? >> >> http://download.jboss.org/jbosstools/static/mars/development/updates/core... >> > This file has the following segment: "http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2/": "Build info file not accessible: http://download.jboss.org/jbosstools/updates/requirements/xulrunner-1.9.2...;, "http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/": "Build info file not accessible: http://download.jboss.org/jbosstools/updates/stable/luna/core/portlet/bui... } how come ? shouldn't this contain the actual used content ? /max http://about.me/maxandersen

On 23 Jun 2015, at 21:13, Nick Boldt wrote: > Do you mean this? > > http://download.jboss.org/jbosstools/static/mars/development/updates/core... > not quite. Last time I suggested we created a file with a line for each repo, like: jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1 You had a txt file before that had this information but in a hard-to-parse format. I can try parse the buildinfo.json too but thought if you had the simpler one I could use that instead. /max > > On 06/23/2015 01:10 PM, Max Rydahl Andersen wrote: >> remind me where I can get the list of repo, sha-1 and i'll make this >> happen on all of them. >> >> /max >> >>> Component leads, please tag your repositories! >>> >>> $ git fetch jbosstools jbosstools-4.3.0.Beta1x #assuming remote is >>> called jbosstools, also often called origin >>> $ git tag jbosstools-4.3.0.Beta1 FETCH_HEAD >>> $ git push jbosstools jbosstools-4.3.0.Beta1 >>> >>> >>> -- >>> 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 >> >> >> /max >> http://about.me/maxandersen > > -- > Nick Boldt :: JBoss by Red Hat > Productization Lead :: JBoss Tools & Dev Studio > http://nick.divbyzero.com /max http://about.me/maxandersen

Done for jbosstools-playground.

On 06/29/2015 12:23 PM, Max Rydahl Andersen wrote: > On 29 Jun 2015, at 9:14, Mickael Istria wrote: > >> Done for jbosstools-playground. > > any ETA on when playground can gets dropped from build ? this one was > intended to only be included for beta1 as fast way to get easyimport > working. > For beta2/GA we need playground to be removed from our build chain. The m2e and WTP support for importer is still to be migrated to the related projects. Given the current weak reactions of those project team after various request, I'm not very optimistic in our ability to move those in the m2e or WTP code-base soon enough for Beta2.

However, we could move them to our jbosstools-javaee and jbosstools-central repository in the meantime. WDYT?