Hi, Two questions:
1) I dug around through the docs and couldn't find information on writing your own goals. I found the maven.xml file and see it has goal definitions--which look like ant fragments with scripting elements added--but I don't see how I can insert a particular goal so it, for instance, is executed before, say java:jar. Or instead of. Or after it. I'd like to--as suggested--copy all my source files to a single directory so Maven will recognize them for site generation purposes only. 2) Is the only way to add libraries to the build CLASSPATH to add a dependency? --kd -----Original Message----- From: Ara Abrahamian [mailto:[EMAIL PROTECTED]] Sent: Friday, August 30, 2002 5:59 AM To: 'Turbine Maven Users List'; [EMAIL PROTECTED] Subject: RE: projects with multiple source directories I'm in the same camp. I'm trying to convert a huge multi-subsystem project to maven. I use xdoclet too. A project.xml for each subsystem is ok for me, but the single source folder approach absolutely not. I like the idea of using Ant style Path for setting up src. At leasy imho a gensrc should be added to Maven. Like tests are treated specially, auto generated sources/artifacts should be too. Ara. > -----Original Message----- > From: J. Matthew Pryor [mailto:[EMAIL PROTECTED]] > Sent: Thursday, August 29, 2002 3:00 AM > To: Turbine Maven Users List > Subject: RE: projects with multiple source directories > > Another complicated scenario is where you have a combination of "real" > source & generated source (xdoclet generated for example) > > Given how well Ant handles Path-like-structures why is it that maven can't > treat src as a path-like-structure rather than a single > directory > > Thanks, > jmp > > > -----Original Message----- > > From: Barry Kaplan [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, August 29, 2002 6:51 AM > > To: Turbine Maven Users List > > Subject: Re: projects with multiple source directories > > > > > > Downey, Kyle wrote: > > > > >Hello, > > > > > >I found a July message that this feature used to exist (in fact, FYI, > in the > > >image of the POM in the documentation it's still there) but was > removed. I > > >saw a reply that said this was done for simplicity, but I know of > multiple > > >projects with this kind of structure. If Maven won't do this, what's > the > > >workaround? > > > > > >For the project I'm converting to Maven there are multiple source > > >directories because it's broken into distinct modules that build their > own > > >JARs (and each has its own third-party library dependencies, which are > > >handled in the existing build.xml files). What are my options if I want > to > > >create a Maven site that has CVS, style and other reports plus Javadocs > for > > >all five modules? > > > > > > > > The general answer has been to create multiple maven projects. Our > > project has multiple directories also, but they don't correspond 1-1 > > with jars. They exists to make development via IDEs easier. (We use the > > IDEs all day, so it was an easy decision.) So what I did, was to write a > > goal to copy the files from their true location into a maven-only src > > tree. I also had to modify the cvs plugins since the cvs info is not in > > the maven src tree, but in the source tree. (Those mods are clean and > > backward compatible. I'll post the them soon and see if the maveners > > will commit them.) > > > > Maven is too nice to not use just because the directory limitation. > > Copying the files is not so tuff. But it does pretty much relegate maven > > to batch mode. > > > > Making maven support multiple source directories would really not be > > that hard. I suppose it seemed like the better thing to do given the way > > the plugins were written. Most would access the pom properties > > directory. If instead a jellybean was defined that would provide the > > appropiate fileset/path, projects could install a multi-directory > > version of that jellybean if they needed to. (At some point, I'll spike > > this to see if it is really that easy.) > > > > > > > > > > -- > > To unsubscribe, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> > > For additional commands, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> > > > -- > To unsubscribe, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:turbine-maven-user- > [EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> ============================================================================== This e-mail is intended only for the use of the addressees. Any copying, forwarding, printing or other use of this e-mail by persons other than the addressees is not authorized. This e-mail may contain information that is privileged, confidential and exempt from disclosure. If you are not the intended recipient, please notify us immediately by return e-mail (including the original message in your reply) and then delete and discard all copies of the e-mail. Thank you. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
