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:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
