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.

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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development

A couple of commonly used options: Alpha3 - Who expects alphas to work anyway? :) M12 - (Milestone 12) N20090220-1200 - Nightly build 02/20/2009 at 12:00 I20090220-1200 - Integration build 02/20/2009 at 12:00 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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jboss-development