Re: [jboss-dev] AS trunk is broke

Yes exactly. To them you just do a release following the milsestone timestamp version convention e.g jboss-jsf-3.4.5-20100603-M3 etc On Jun 4, 2010, at 11:03 AM, Stan Silvert wrote: > So am I OK if I use versioned snapshots? Sounds like that's the best of both worlds. > > David M. Lloyd wrote: >> One main reason: it makes test suite failures impossible to replicate reliably. Unless you create *versioned* snapshots (e.g. with a specific version like -20100604 or something) then the same AS revision can yield different results depending on what snapshot is out there at the moment. >> >> If you use fixed versions, and something breaks, you can point to the diff and say "this change cause it to break". With a snapshot, it can work initially and then break later, causing the wrong changes to be scrutinized. >> >> On 06/04/2010 10:48 AM, Stan Silvert wrote: >>> Let's talk about this then. >>> >>> It seems to me that this is exactly what snapshots are for. Releases >>> are a pain. Snapshots are quick and easy. When you are doing >>> development and things are changing rapidly, use a snapshot. When you >>> have something stable that's ready for an AS release, do a release. >>> >>> What was the reason for making snapshots verboten? I understand that we >>> can't have snapshots in a release, and we obviously can't use >>> third-party snapshots. But using them for sub-modules is beneficial in >>> the development phase. That's what snapshots are for, right? >>> >>> If I had know this I probably would have done all the development in >>> trunk. Maybe I should move it there? >>> >>> Stan >>> >>> Jason Greene wrote: >>>> No they are most definitely NOT! >>>> >>>> On Jun 4, 2010, at 7:44 AM, Jaikiran Pai wrote: >>>> >>>> >>>>> As an aside, are SNAPSHOT dependencies of non-AS modules, like this one, >>>>> allowed in AS trunk? >>>>> >>>>> -Jaikiran >>>>> Stan Silvert wrote: >>>>> >>>>>> Just a guess, but maybe your settings.xml is not set up for the JBoss >>>>>> snapshot repo? >>>>>> http://community.jboss.org/wiki/MavenGettingStarted-Developers >>>>>> >>>>>> Andrew Dinn wrote: >>>>>> >>>>>>>> Some of us had seen the checksum errors (there's a mail in this dev >>>>>>>> list) too. It kept slowing down the build, but I ignored it. As >>>>>>>> >>>>>>> for the >>>>>>> >>>>>>>> other error you are seeing, could you post the build logs? And what >>>>>>>> command do you use to build the trunk? From what I know, the >>>>>>>> >>>>>>> recommended >>>>>>> >>>>>>>> way is to mvn clean install from the trunk root. >>>>>>>> >>>>>>>> P.S: I think we should really have the hudson.qa instances build >>>>>>>> >>>>>>> the AS >>>>>>> >>>>>>>> trunk against a clean repo using the *public* repo. Right now, >>>>>>>> >>>>>>> it's just >>>>>>> >>>>>>>> a false impression that the AS trunk is building fine. >>>>>>>> >>>>>>> I initially used bash build.sh in the build directory. However, after >>>>>>> posting I retried using mvn clean install and the source of the >>>>>>> problem became more evident: >>>>>>> >>>>>>> [INFO] [dependency:unpack {execution: unpack}] >>>>>>> [INFO] Configured Artifact: >>>>>>> org.jboss.jsf.integration:jboss-jsf-deployer:1.0.0-SNAPSHOT:jar >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [ERROR] BUILD ERROR >>>>>>> [INFO] >>>>>>> ------------------------------------------------------------------------ >>>>>>> [INFO] Unable to find artifact. >>>>>>> >>>>>>> Embedded error: Unable to download the artifact from any repository >>>>>>> >>>>>>> I assume this is why the deployer was not found. >>>>>>> >>>>>>> regards, >>>>>>> >>>>>>> >>>>>>> Andrew Dinn >>>>>>> ----------- >>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> _______________________________________________ >>>>> 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 >> > > _______________________________________________ jboss-development mailing list jboss-development(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-development