My weak use-cases.. Lots of laziness and not wanting to take the time

to split up an existing large project ;)


git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@162520 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Peter A Royal Jr 2003-10-21 00:47:16 +00:00
parent 4a7b5dda5d
commit 38b049c019
1 changed files with 11 additions and 1 deletions

View File

@ -132,5 +132,15 @@ their source trees set up in the same way as their collegues.
- how to declare a dependency on JDK and what are possible implications of such dependency
(e.g javac/javadoc target jdk)
- I don't know if this will add too much complexity, but being able to generate multiple
and compound artifacts from a single project would be nice. If we want to have a
"Ant Compatibility Layer", then this would be required.
Think of a project for a web application, it will have java code as well as web resources.
The java code is collected into a JAR file, and then that is packaged with the web
resources into a WAR.
Of course, none of this is really required, as it can all be accomplished by breaking the
project out into multiple projects with a reactor, per the Maven 1 guidelines. But if this
limitation was removed, it might help Marvin adoption. (PR)