On 08 Dec 2014, at 04:19, Nick Boldt <nboldt(a)redhat.com&gt; wrote: his week is the "quiet period" in prep for 4.2.1.Final / 8.0.1.GA. You are required to update your root poms to point at the latest parent pom,

TL;DR: Yes. > I did not create task JIRAs for Hibernate and Livereload, because > neither of those have commits in the 4.2.x branch since 4.2.0.Final and > therefore need not have their root poms adjusted. On 12/08/2014 02:01 AM, Max Rydahl Andersen wrote: > >> On 08 Dec 2014, at 04:19, Nick Boldt <nboldt(a)redhat.com&gt; wrote: >> >> his week is the "quiet period" in prep for 4.2.1.Final / 8.0.1.GA. >> >> You are required to update your root poms to point at the latest parent >> pom, > I assume you mean "If and only if the build your component is in has changed since 4.2.0.Final", correct ? > > As otherwise we are going to have updates to *everything* which is what we don't want for our maintanence builds. > > Just want to make sure the above is what you meant or to know if you found something in our build that requires *every* component to update parent Pom? > >

On 9. 12. 2014, at 11:19, Max Rydahl Andersen <manderse(a)redhat.com&gt; wrote: On 9 Dec 2014, at 2:19, Alexey Kazakov wrote: > Thanks to all component leads who updated their root poms (and I > updated the rest of components: forge, aerogear, central, freemarker). > So all components that have been changed since 4.2.0 are using > 4.2.1.Final-SNAPSHOT root pom now. > However, two components, Birt and Portlet don't have any changes > besides updated root poms. As I understand we should change the root > pom versio ONLY if the component has been changed since 4.2.0.Final. > I reopened the corresponding issues for Birt and Portlet for > clarification: > https://issues.jboss.org/browse/JBIDE-18890 > https://issues.jboss.org/browse/JBIDE-18896 > Should we ignore these changes and not to rebuild Birt & Portlet for > 4.2.1? I would say so - we have the 4.2.0.Final updatesite to get these from so sounds weird why we need to update these. The whole intent we are going for is to *not* burden users with more bits to download AND avoid QE having to test/verify new binaries.

Nick - if our build deletes our actual released bits and not allow using the previous bits then that is a problem. Did the check for publish fail to detect there was no change ? We have had and will have this situation for others than just "dormant" modules like birt and portlet so we should be able to handle this by now IMO. What is missing ? /max > > On 12/08/2014 12:54 PM, Nick Boldt wrote: >> TL;DR: Yes. >> >>> I did not create task JIRAs for Hibernate and Livereload, because >>> neither of those have commits in the 4.2.x branch since 4.2.0.Final >>> and >>> therefore need not have their root poms adjusted. >> >> On 12/08/2014 02:01 AM, Max Rydahl Andersen wrote: >>> >>>> On 08 Dec 2014, at 04:19, Nick Boldt <nboldt(a)redhat.com&gt; wrote: >>>> >>>> his week is the "quiet period" in prep for 4.2.1.Final / 8.0.1.GA. >>>> >>>> You are required to update your root poms to point at the latest >>>> parent >>>> pom, >>> I assume you mean "If and only if the build your component is in has >>> changed since 4.2.0.Final", correct ? >>> >>> As otherwise we are going to have updates to *everything* which is >>> what we don't want for our maintanence builds. >>> >>> Just want to make sure the above is what you meant or to know if you >>> found something in our build that requires *every* component to >>> update parent Pom? >>> >>> > > _______________________________________________ > jbosstools-dev mailing list > jbosstools-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev /max http://about.me/maxandersen <http://about.me/maxandersen> _______________________________________________ jbosstools-dev mailing list jbosstools-dev(a)lists.jboss.org <mailto:jbosstools-dev@lists.jboss.org> https://lists.jboss.org/mailman/listinfo/jbosstools-dev <https://lists.jboss.org/mailman/listinfo/jbosstools-dev>

There are 3 outstanding issues pending for 4.2.1/8.0.1 (for Hibernate and Aerogear) - please take a look and triage them as blocker for this release, or move them to the next one. https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE%22%20...