On Fri, 29 Apr 2005, Vincent Massol <[EMAIL PROTECTED]> wrote: > From: Stefan Bodewig >> >> On Thu, 28 Apr 2005, Vincent Massol <[EMAIL PROTECTED]> wrote: >> >> > The question is really whether we want to hardcode the >> > dependencies between Cargo subprojects or let Maven handle this. >> >> I have no problem with making Maven do that - as long as everything >> works. > > According to http://gump.apache.org/metadata/builder.html#maven, it > seems that Gump does not support this feature?
What is needed? I mean, how do you need to invoke Maven to make it happen? > I'll try it to see if it works (I've just modifier the cargo GOM). Seen it, thanks. Is there any way (using maven.final.name or something) to provide a consistent name for the generated jar(s) that does not contain the version information. The way it currently is, we'd need to modify the descriptor as soon as 0.5 has been released an Cargo CVS HEAD becomes 0.6-SNAPSHOT. > BTW, there is a gump plugin for maven so if you call "maven gump" on > a Maven project, it generates a GOM file. I think Brett has used that for the directory project descriptors. Since I create descriptors on my local machine and don't have Maven installed, I'm faster when I create descriptors manually. > Again the issue is triggering Gump when you debug (otherwise you > have to wait for a long time to see your change take effect). The next Gump that has a remote chance of actually building Cargo is the JDK 1.5 build. Scheduled to start in about half an hour. We do have four useful builds per day (three of which use JDK 1.4) by now. See <http://brutus.apache.org/>. The Kaffe build is interesting, but many projects fail due to dependencies on Sun VMs (in their prereqs, potentially) or Kaffe bugs. Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
