I would give you a good chance to get some reports working.
Never call "mvn compile" or "mvn install", just call "mvn site"
(or "mvn clean site").
Use the <build> element to set your destandarized src directories etc.
Use the <reports> element to set and configure the reports you want,
start with one report and add them sequentially.
Use <dependencies> with the <scope>provided</scope><?>lib/x.jar</?> to
hack it.
See "project reference" on maven.apache.org.
Do note that you won't be able to use the surefire-report or any of the
unit test case reports as they require compiles etc.
But in the end... if you're using svn (instead of cvs), refactor your
directory structure and try to get a parallel build up with m2.
SomeDude wrote, On 2006-10-05 4:46 PM:
I am very new to Maven and from the introductory reading that I have done I
am starting to understand that if I were to use it in our projects I would
have to replace our current build process. Here are my problems:
1) Boss wants me to see if Maven can be useful for us in the documentation
process. He really likes the website feature.
2) Boss likes the way we build our projects since we have been using these
ginormous ant scripts for years now. He will not change the build process.
3) Boss would not even consider messing with our current directory
structures
My Question is:
Is there any way I could use Maven features like the website generation and
report creation without having to interfere with the current project
structure and build process?
Sorry if my question is noobish, FreshGraduate!
Thanx guys.
--
With kind regards,
Geoffrey De Smet
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
