[jbosstools-dev] ACTION REQUIRED: JBT 4.1.1.Alpha2 candidate build STILL contains older Forge features

[Max Andersen]

On Thu, Oct 03, 2013 at 10:42:37AM -0400, Nick Boldt wrote:
>Yes, the plugin went from 1.3.3 to 1.4.1; the issue was that it 
>wasn't being picked up because the feature version was unchanged.

i dont see any version bumps besides the runtime plugin.

So the plugins are rebuilt, rereleased and published with versions from previous releases.

Thats not breaking something because we bump the qualifier automatically but it is inconsistent.

For alpha2 thats a bug that should be fixed in beta.

/max

>All is well now, with this followup problem to solve for Beta1:
>
>https://issues.jboss.org/browse/JBIDE-15606
>
>On 10/03/2013 10:10 AM, Koen Aers wrote:
>>The plugin versions were already changed earlier.
>>
>>Cheers,
>>Koen
>>
>>Op 3-okt.-2013, om 15:48 heeft Max Andersen het volgende geschreven:
>>
>>>I see https://github.com/jbosstools/jbosstools-forge/commit/94821b4acbcff5cded0f7ac894315ba555963512
>>>
>>>but that just changes the feature version, not the plugin versions.
>>>
>>>This looks like incomplete patch/fix ?
>>>
>>>/max
>>>
>>>On Tue, Oct 01, 2013 at 12:33:33PM +0200, Max Andersen wrote:
>>>>Koen - can you do this ASAP ?
>>>>
>>>>Thanks,
>>>>Max
>>>>
>>>>On Mon, Sep 30, 2013 at 02:49:56PM -0400, Nick Boldt wrote:
>>>>>In JBT 4.1.0 [0], we had Forge features 1.0.0 and 1.2.0.
>>>>>
>>>>>[0] http://download.jboss.org/jbosstools/updates/stable/kepler/
>>>>>
>>>>>In JBT 4.1.1.Alpha2, we have Forge features 1.0.0 and 1.2.0 [1] as
>>>>>well, even though things have changed [2].
>>>>>
>>>>>[1] http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_41/all/repo/
>>>>>
>>>>>[2] https://github.com/jbosstools/jbosstools-forge/commits/jbosstools-4.1.1.Alpha2x
>>>>>
>>>>>In JBT 4.2.0 (master branch), we have Forge features 1.1.0 and 1.3.0 [3].
>>>>>
>>>>>[3] http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_master/all/repo/
>>>>>
>>>>>So... if you want the newer forge bits included in the JBT
>>>>>4.1.1.Alpha2 build, you need to bump the features that contain
>>>>>org.jboss.tools.forge.runtime to contain the changed forge runtime
>>>>>(1.3.3 -> 1.4.1), presumably to 1.2.1.
>>>>>
>>>>>Affected files:
>>>>>
>>>>>https://github.com/jbosstools/jbosstools-forge/blob/jbosstools-4.1.1.Alpha2x/features/org.jboss.tools.forge.feature/feature.xml
>>>>>https://github.com/jbosstools/jbosstools-forge/blob/jbosstools-4.1.1.Alpha2x/features/org.jboss.tools.forge.feature/pom.xml
>>>>>
>>>>>https://github.com/jbosstools/jbosstools-forge/blob/jbosstools-4.1.x/features/org.jboss.tools.forge.feature/feature.xml
>>>>>https://github.com/jbosstools/jbosstools-forge/blob/jbosstools-4.1.x/features/org.jboss.tools.forge.feature/pom.xml
>>>>>
>>>>>When this is fixed, please kick your job [4] to respin it using the
>>>>>updated versions. I'll be leaving for the airport in 2hrs, so I won't
>>>>>have time to kick it for you.
>>>>>
>>>>>[4] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-forge_41/
>>>>>
>>>>>--
>>>>>Nick Boldt :: JBoss by Red Hat
>>>>>Productization Lead :: JBoss Tools & Dev Studio
>>>>>http://nick.divbyzero.com
>>>>_______________________________________________
>>>>jbosstools-dev mailing list
>>>>jbosstools-dev at lists.jboss.org
>>>>https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>_______________________________________________
>>>jbosstools-dev mailing list
>>>jbosstools-dev at 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