[jboss-dev] No more snapshots in 5.0!

[Jason T. Greene]

Right, the fundamental problem with snapshots, is being able to have a 
dependency on "X-SNAPSHOT". If you do specify the exact snapshot version 
as a dep, then the only real thing you are gaining (over doing the same 
with a normal release) is having the snapshot exist on another server, 
and having to come up with a timestamp.

The other problem with SNAPSHOTS is that the source tree of the snapshot 
component does not have the version in its pom, just "SNAPSHOT", which 
makes correlating a source rev to a snapshot version difficult.

Carlo de Wolf wrote:
> I have no need for more Maven babysitting. In essence AS is requesting 
> specific releases for each component anyway, so you might as well 
> request a specific snapshot release instead. So instead of 
> jboss-jpa-deployers-1.0.0-SNAPSHOT request 
> jboss-jpa-deployers-1.0.0-20090219.115639-7. That's how I triangulated 
> the VFS version.
> The only problem is that a snapshot has transitive dependencies on other 
> snapshots. I started on a 'generate release pom' plugin, but Maven has 
> got some pretty weird notions around snapshots, so it's not going anywhere.
> 
> Carlo
> 
> Ales Justin wrote:
>> I'm fine with temp releases, as it's quite easy to do this once you 
>> have your project fully mavenized.
>>
>> But we need some common/general consensus on how this is gonna be done.
>> Perhaps Alpha, Beta are not the way to go, as we already treat them as 
>> "official" releases.
>>
>> What is 'normally' used in this case?
>>
>> Jason T. Greene wrote:
>>> We need to stop using snapshots in this Branch, as it's making it 
>>> difficult for everyone to figure out why their tests are suddenly 
>>> breaking. As an example, Brian is now trying to find the cause of a 
>>> deadlock issue that just appeared on a testrun without any changes 
>>> occuring.
>>>
>>> We need to use releases so that a test run can be correlated to a 
>>> component change. Even if you don't call it an official release, just 
>>> make up something like M132 or Beta17, etc.
>>>
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development


-- 
Jason T. Greene
JBoss, a division of Red Hat