Re: bcel failure
Antoine Levy-Lambert wrote: Stefan Bodewig wrote: What would be the correct mvn goal to invoke if we want a jatr and maybe run tests? Stefan mvn package builds the jars under target I think. mvn package runs the tests as well (by default, at least) mvn install builds the jars, runs the tests, and copies the jars to $HOME/.m2/repository/groupId/artifactId/version correct -- Stefano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
On Fri, 10 Nov 2006, Stefan Bodewig [EMAIL PROTECTED] wrote: Once Gump says it can find mvn in http://gump.zones.apache.org/gump/test/index.html So far it doesn't, I only set M2_HOME which didn't seem to be enough. I've now added $M2_HOME/bin to PATH as well, that hopefully does the trick. we can use bcel as our test project for the Maven2 support in Gump. bcel doesn't have any dependencies to speak of, so the missing pieces won't hurt too badly. What would be the correct mvn goal to invoke if we want a jatr and maybe run tests? Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
Stefan Bodewig [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] On Fri, 10 Nov 2006, Stefan Bodewig [EMAIL PROTECTED] wrote: Once Gump says it can find mvn in http://gump.zones.apache.org/gump/test/index.html So far it doesn't, I only set M2_HOME which didn't seem to be enough. I've now added $M2_HOME/bin to PATH as well, that hopefully does the trick. Yes, it's the same as for M1. It needs to be on the path as well. I just cloned what Gump was doing for M1. we can use bcel as our test project for the Maven2 support in Gump. bcel doesn't have any dependencies to speak of, so the missing pieces won't hurt too badly. What would be the correct mvn goal to invoke if we want a jatr and maybe run tests? The default goal is package. Of course, mvn will run offline, so all of the dependant jars will have to be in the local repository. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
Stefan Bodewig wrote: What would be the correct mvn goal to invoke if we want a jatr and maybe run tests? Stefan mvn package builds the jars under target I think. mvn install builds the jars, runs the tests, and copies the jars to $HOME/.m2/repository/groupId/artifactId/version Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
On Fri, 10 Nov 2006, Bill Barker [EMAIL PROTECTED] wrote: Actually, we already have the Python part (at least in trunk). Thanks for reminding us, you finally made me scratch one thing from my TODO list. Maven2 is now installed and should be available to the test workspace on it unless I've made any mistakes (which I probably have ;-). Once Gump says it can find mvn in http://gump.zones.apache.org/gump/test/index.html we can use bcel as our test project for the Maven2 support in Gump. bcel doesn't have any dependencies to speak of, so the missing pieces won't hurt too badly. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
On Fri, 10 Nov 2006, Stefan Bodewig [EMAIL PROTECTED] wrote: Maven2 is now installed installed on helios AKA gump.zones.apache.org, that is. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
On Fri, 10 Nov 2006, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: This requires adding in the gump metadata of projects built with ant which are maven dependees the groupId and artifactId of each jar, plus the version that maven wants. version*s* since different Maven projects might ask for different versions. What you describe would either require manually updating all descriptors or making Gump smart enough to parse Maven2 POMs. In an off-list discussion Steve mentioned an idea to me that may even be easier to implement: Create a Web Application that understands Maven's remote repository layout and point mvn to this webapp as the only available repository to use. This webapp would then map the artifact id to the corresponding Gump jar and serve up the latest artifacts from the current build. This way we only need to understand the groupId/artifactId mappings but (1) can ignore the version information completely and (2) don't give mvn a chance to pull in uncontrolled artifacts at all. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
Stefan Bodewig wrote: On Fri, 10 Nov 2006, Antoine Levy-Lambert [EMAIL PROTECTED] wrote: This requires adding in the gump metadata of projects built with ant which are maven dependees the groupId and artifactId of each jar, plus the version that maven wants. version*s* since different Maven projects might ask for different versions. What you describe would either require manually updating all descriptors or making Gump smart enough to parse Maven2 POMs. In an off-list discussion Steve mentioned an idea to me that may even be easier to implement: Create a Web Application that understands Maven's remote repository layout and point mvn to this webapp as the only available repository to use. This webapp would then map the artifact id to the corresponding Gump jar and serve up the latest artifacts from the current build. This way we only need to understand the groupId/artifactId mappings but (1) can ignore the version information completely and (2) don't give mvn a chance to pull in uncontrolled artifacts at all. how about following maven1 footsteps: we force maven2 to stay offline and then we use symlinks in the .m2 repo to point at the gump-generated jars? superhacky, but it could work and doesn't require webapp development/management -- Stefano. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: bcel failure
On Nov 10, 2006, at 12:43 PM, Stefan Bodewig wrote: On Fri, 10 Nov 2006, Stefan Bodewig [EMAIL PROTECTED] wrote: Maven2 is now installed installed on helios AKA gump.zones.apache.org, that is. FWIW Maven2 2.0.2 is also available on Clarus (it's back! it's back!). S. -- [EMAIL PROTECTED]http://www.temme.net/sander/ PGP FP: 51B4 8727 466A 0BC3 69F4 B7B8 B2BE BC40 1529 24AF smime.p7s Description: S/MIME cryptographic signature
