Re: [jbosstools-dev] Why does update/kepler now point to Alpha2 ?
On Sun, Mar 24, 2013 at 12:53:20PM -0400, Nick Boldt wrote:
Traditionally, every time a significant change was done to the TP, you
asked that we upversion it so that we could diff the versions. Had I
replaced Alpha2's contents with M6 bits, you would no doubt have
complained that I was overwriting instead of creating new snapshots.
Remember there are two parts here;
A) the .target file
B) the published .target repository built from .target
As long as the content is -SNAPSHOT we are now (since we are using *released* i.e.
non-snapshot target platforms in parent pom's now)
you can overwrite the content of the published site.
But I would say we still should be careful publish the snapshots blindly since
it is more or less unnecessary churn for you and download.jboss.org/jenkins to spend time
on IMO.
Thats why I was doing attempt over the weekend to document how I think this should work
but could
not get the build to work when using the google ADT site so if you could give your insight
on to
why that would be failing that would be great :)
Does it really matter as long as the version goes up?
No need to have the version goes up if we haven't released it yet.
/max
N
On 03/23/2013 11:27 PM, Max Rydahl Andersen wrote:
>On Sat, Mar 23, 2013 at 10:12:47AM -0400, Nick Boldt wrote:
>>Because Alpha2 was an interim state: Kepler M5 w/ newer Jetty 8 (plus
>>Atlassian 3.0.7, SWTBot 2.0.5).
>
>but as Micakel mention, alpha2-snapshot is where interim state is fine
>and its not published anywhere so why not just add what you call alpha3
>into this ?
>
>/max
>
>>Alpha3 is incompatible w/ Alpha2 as it includes Kepler M6, Atlassian
>>3.2, and SWTBot 2.1.
>
>>N
>>
>>On 03/23/2013 09:01 AM, Mickael Istria wrote:
>>>On 03/23/2013 11:37 AM, Max Rydahl Andersen wrote:
>>>>On Sat, Mar 23, 2013 at 11:31:07AM +0100, Mickael Istria wrote:
>>>>>On 03/23/2013 05:41 AM, Nick Boldt wrote:
>>>>>>Alpha2 (M5 + Jetty 8) and Alpha3 (Kepler M6 + Atlassian, etc.)
>>>>>>won't be
>>>>>>linked from there until were release JBT 4.1.0.Alpha2
>>>>>Why would we need an Alpha3, and why would we release an Alpha2 ?
>>>>
>>>>I assume you mean why would we not just release an Alpha2 so the
>>>>latest TP are available to use for next JBT release which coincidently
>>>>is named Alpha2 too ?
>>>Yes, that's what I mean.
>>>I mainly mean: why do we already have an Alpha3 whereas we still are
>>>doing snapshots of Alpha2. All TP changes until we release a new
>>>milestone of JBT should be in the current snapshot (TP
>>>4.30.5.Alpha2-SNAPSHOT).
>>>
>>>--
>>>Mickael Istria
>>>Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
>>>My blog <http://mickaelistria.wordpress.com> - My Tweets
>>><http://twitter.com/mickaelistria>
>>
>>--
>>Nick Boldt :: JBoss by Red Hat
>>Productization Lead :: JBoss Tools & Dev Studio
>>http://nick.divbyzero.com
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com