Re: Maven 2 (was Re: Maven 1.1)
Ok, here's the opportunity for me to write the mail in my head. Aside from the non-existance of a gump machine right now, what is needed to use Maven 2, a) minimally b) ideally Because it has an even more online nature (plugins are not preinstalled), to use an installed version we'd again need to create a minimal local repository including those plugins, then use offline mode (-o), and ensure it can't get any internet access just to make sure. However, it should be pretty easy to step it up to the next level. Instead of a pre-installed repository, we can add a "Gump artifact resolver". What I'd need to know is the best way to make that work. Can you verify that to resolve a JAR file in gump (assuming gump has already built it) I'd need to: * know the base working directory * know the location of the gump XML file * parse out and within that * look in base/project_name/jar_name The resolver can also parse these files for depends. This would require knowing where everything is, so even better would be: * a list of directories creating gump descriptors * that all files in the descriptor are relative to that gump descriptor Is that how it is currently? We come back to the problem of aligning IDs. I think the best place to solve this is in the gump descriptors. Here is how I'd parse them out in order of preference: * GroupId: 1) 2) 3) * Artifact ID: 1) 2) 3) 4) * Type: 1) 2) means "jar" 3) 4) how do you specify non-jar outputs? * Classifier: 1) 2) 3) default is none If I start adding them, will it break anything? Now, the next issue comes when Gump3 parses multiple input formats. I don't want to duplicate information in Maven - can we get gump to pick a format and produce that as part of the build, regardless of its input? A POM would simplify things :) Ok, this would have a preinstalled Maven using some packaged plugins working offline without a manual repository setup. Next, to build Maven. We have a bootstrap that runs without any dependencies except Java that would produce the installation above - but it downloads the Maven dependencies on the way. We could have it resolve packaged versions of those by reusing the gump resolver. Alternatively, something we are doing so it can be packaged on unix is checking out the sources rather than relying on packaging, then building them, then building m2 (and those packages would later be rebuilt again using the new m2). Is that a better alternative to the above? - Brett On 11/16/05, Stefan Bodewig <[EMAIL PROTECTED]> wrote: > On Tue, 15 Nov 2005, Leo Simons <[EMAIL PROTECTED]> wrote: > > > Actually, someone's looking at changing the excalibur build to use > > maven 2. That pretty much means tree detoriation anyway. We're going > > to start seeing that all over apache as projects migrate to maven 2. > > Pluto's trunk has already jumped to Maven 2. We will need a maven2 > builder, that's "all". > > Stefan > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2 (was Re: Maven 1.1)
On Tue, 15 Nov 2005, Leo Simons <[EMAIL PROTECTED]> wrote: > Actually, someone's looking at changing the excalibur build to use > maven 2. That pretty much means tree detoriation anyway. We're going > to start seeing that all over apache as projects migrate to maven 2. Pluto's trunk has already jumped to Maven 2. We will need a maven2 builder, that's "all". Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1
I don't know of them all, but I believe the following projects are on the way or considering it: Cocoon, Pluto, JetSpeed 2, Struts, Excalibur, Geronimo, Directory, Felix Those are the ones feeling pain points in their build that Maven solves. For the ones where it already just works, there is probably little reason to change. I want to get a good multiproject site/reporting solution together before proposing it as a parallel build in commons, but I think that there could be a lot of benefits there too. - Brett On 11/16/05, Dion Gillard <[EMAIL PROTECTED]> wrote: > On 11/16/05, Leo Simons <[EMAIL PROTECTED]> wrote: > [snip] > > Actually, someone's looking at changing the excalibur build to use maven > > 2. That pretty much means tree detoriation anyway. We're going to start > > seeing that all over apache as projects migrate to maven 2. > > > > cheers, > > > > LSD > > Just out of curiosity, what adoption of Maven 2 has there been @ > Apache. In Jakarta I've seen very little. > -- > http://www.multitask.com.au/people/dion/ > "You are going to let the fear of poverty govern your life and your > reward will be that you will eat, but you will not live." - George > Bernard Shaw > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1
On 11/16/05, Leo Simons <[EMAIL PROTECTED]> wrote: > Actually, someone's looking at changing the excalibur build to use maven > 2. That pretty much means tree detoriation anyway. We're going to start > seeing that all over apache as projects migrate to maven 2. In theory, Gump should be able to build and use Maven 2 very shortly. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1
On 11/16/05, Leo Simons <[EMAIL PROTECTED]> wrote: [snip] > Actually, someone's looking at changing the excalibur build to use maven > 2. That pretty much means tree detoriation anyway. We're going to start > seeing that all over apache as projects migrate to maven 2. > > cheers, > > LSD Just out of curiosity, what adoption of Maven 2 has there been @ Apache. In Jakarta I've seen very little. -- http://www.multitask.com.au/people/dion/ "You are going to let the fear of poverty govern your life and your reward will be that you will eat, but you will not live." - George Bernard Shaw - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1
On Tue, Nov 15, 2005 at 06:28:28AM +0100, Stefan Bodewig wrote: > On Mon, 14 Nov 2005, Brett Porter <[EMAIL PROTECTED]> wrote: > > > We actually started validating the project.xml files. Some people > > have a lot of random content in there that was previously silenty > > ignored. > > > > Maybe its worth considering them a failed build for the purposes of > > Gump so that they update it? > > If it wasn't the excalibur project, maybe. > > You may not have noticed it, but before I destroyed vmgump the only > project still depending on the old Avalon codebase was James - since I > don't find a replacement for meta-tools in Excalibur. All other > dependencies, in particular commons-logging's dependency on framework > and logkit have been migrated to the Excalibur maintained versions. I'm sure the james people would love to hear about the stuff that's keeping them depending on the old avalon codebase. Either we migrate that to excalibur or into james or they stop using it :-) > On the other hand - unless Leo jumps in - I'm afraid that the > Excalibur community doesn't care about Gump that much and we'd be left > with a build tree that is only building around 50% or even less "just" > because Maven started to validate the descriptors. Actually, someone's looking at changing the excalibur build to use maven 2. That pretty much means tree detoriation anyway. We're going to start seeing that all over apache as projects migrate to maven 2. cheers, LSD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
