RE: jtidy
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 13 October 2004 12:06 > To: Stephen McConnell > Cc: Gump code and data > Subject: Re: jtidy > > You mean a maven plugin built by magic? Yep (assuming you mean Magic as opposed to magic). > No problem - plugins are just JARs, just as long as the id remains > unique as we've already discussed. No problem there. Cheers, Steve. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jtidy
> I really haven't followed Maven development, but when we tried to list > the dependencies last time, some things (werkz is something I > remember) simply were unbuildable if not un-findable. > > We'll sort that out, I'm sure. I thought the issue was dom4j - since resolved. There are things like werkz, forehead, comons-grant which are pretty much dead outside of Maven. The plan is to fold them in for Maven 1.1, as they are quite small. But we'll still build them for now. We'll sort something out. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jtidy
On Wed, 13 Oct 2004, Brett Porter <[EMAIL PROTECTED]> wrote: > Once we get the current set of Maven projects all building happily, > I'll work with someone to make sure Maven itself bootstraps. Which would be really great- > I don't think there is anything hard there I really haven't followed Maven development, but when we tried to list the dependencies last time, some things (werkz is something I remember) simply were unbuildable if not un-findable. We'll sort that out, I'm sure. Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jtidy
You mean a maven plugin built by magic? No problem - plugins are just JARs, just as long as the id remains unique as we've already discussed. Cheers, Brett > Any ideas what will happen when a project declares a dependency on a > artifact in both the project.xml and the gump project definition, and > the plugin itself is not built by maven? > > This is the case with a plugin in the avalon repository that is build by > Magic and used in Maven under the Fulcrum project. > > Steve. > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jtidy
> "installed package" in the Gump sense. I want to build the build > system from source, whereever possible. Right. Once we get the current set of Maven projects all building happily, I'll work with someone to make sure Maven itself bootstraps. I don't think there is anything hard there - just need to sort out policies behind it, whether we are building 1.1 (HEAD), 1.0.x (branch) or both, where to install, etc. Cheers, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: jtidy
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: 13 October 2004 09:19 > To: Gump code and data > Subject: Re: jtidy > > > > -- it is the last step before Cocoon, it seems. That, or somehow we > > > need to tackle this list below. > > > > Brett, if we built all those plugins from source, would we be able to > > use the freshly compiled versions of them in Maven using jar overrides > > or something? Or would this involve changing the Maven installation? > > I'll give a more explanatory answer, but the short answer is that it > doesn't require changing the Maven installation, so this should be > easy enough. > > plugins are a bit "interesting" in Maven 1.x. > > There are installation-wide plugins in $MAVEN_HOME/plugins > There are user plugins in $MAVEN_HOME_LOCAL/plugins (usually > $HOME/.maven/plugins) > > to gump, I imagine we never go near the second one, and only change > the first one when we start building Maven from source. > > Then there are runtime only plugins - specified as dependencies (as in > the case above), or built as part of a maven build using the reactor > (see geronimo, I think). > > Since these ones are dependencies, they can be built using gump and > handled as regular dependencies with jar overrides. They will not > affect other projects, as they are not installed into either of the > two locations above - just loaded into memory for the current maven > run and forgotten once it stops. > > > I'm very reluctant to make more parts of our build systems "installed". > > Not exactly what you mean by installed here. I agree that they > shouldn't be installed in Maven for all builders to use. > > I think that they have to be treated as with other dependencies: use > jar overrides. But whether you build them from source, or package them > is up to you. I'd say building them is unlikely to be problematic > (unless they have some obscure dependencies): plugin:plugin is a very > simple goal. Brett: Any ideas what will happen when a project declares a dependency on a artifact in both the project.xml and the gump project definition, and the plugin itself is not built by maven? This is the case with a plugin in the avalon repository that is build by Magic and used in Maven under the Fulcrum project. Steve. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jtidy
> > -- it is the last step before Cocoon, it seems. That, or somehow we > > need to tackle this list below. > > Brett, if we built all those plugins from source, would we be able to > use the freshly compiled versions of them in Maven using jar overrides > or something? Or would this involve changing the Maven installation? I'll give a more explanatory answer, but the short answer is that it doesn't require changing the Maven installation, so this should be easy enough. plugins are a bit "interesting" in Maven 1.x. There are installation-wide plugins in $MAVEN_HOME/plugins There are user plugins in $MAVEN_HOME_LOCAL/plugins (usually $HOME/.maven/plugins) to gump, I imagine we never go near the second one, and only change the first one when we start building Maven from source. Then there are runtime only plugins - specified as dependencies (as in the case above), or built as part of a maven build using the reactor (see geronimo, I think). Since these ones are dependencies, they can be built using gump and handled as regular dependencies with jar overrides. They will not affect other projects, as they are not installed into either of the two locations above - just loaded into memory for the current maven run and forgotten once it stops. > I'm very reluctant to make more parts of our build systems "installed". Not exactly what you mean by installed here. I agree that they shouldn't be installed in Maven for all builders to use. I think that they have to be treated as with other dependencies: use jar overrides. But whether you build them from source, or package them is up to you. I'd say building them is unlikely to be problematic (unless they have some obscure dependencies): plugin:plugin is a very simple goal. HTH, Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jtidy
On Tue, 12 Oct 2004, Adam Jack <[EMAIL PROTECTED]> wrote: > The jtidy build.xml vanished, so it is Maven or nada. Anybody else > tempted to package jtidy Yep. Depends on the answer to my question below and/or how easy a migration to a Maven build would be. > -- it is the last step before Cocoon, it seems. That, or somehow we > need to tackle this list below. Brett, if we built all those plugins from source, would we be able to use the freshly compiled versions of them in Maven using jar overrides or something? Or would this involve changing the Maven installation? I'm very reluctant to make more parts of our build systems "installed". Stefan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jtidy
Only one of those comes from Maven. Until we are building Maven from scratch (as always, ready to talk about this when you are, btw), you'll need to package this one. The other 4 come from 3 different distributions. They could either be added and built (you'll find the statcvs link from maven's plugins page) or packaged. Cheers, Brett On Tue, 12 Oct 2004 20:30:59 -0600, Adam Jack <[EMAIL PROTECTED]> wrote: > The jtidy build.xml vanished, so it is Maven or nada. Anybody else tempted > to package jtidy -- it is the last step before Cocoon, it seems. That, or > somehow we need to tackle this list below. > > regards > > Adam > > The build cannot continue because of the following unsatisfied dependencies: > > maven-sourceforge-plugin-1.0.jar (try downloading from > http://maven-plugins.sourceforge.net) > maven-statcvs-plugin-2.4.jar > maven-findbugs-plugin-0.8.4.jar > maven-xhtml-plugin-1.2.jar (try downloading from > http://maven-validator.sourceforge.net) > maven-checkstyle-plugin-2.4.1.jar (try downloading from > http://maven.apache.org/reference/plugins/checkstyle) > > Total time: 1 seconds > Finished at: Tue Oct 12 18:56:25 PDT 2004 > > - > 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]
