From: "Ted Husted" <[EMAIL PROTECTED]>
It is suppose to be a leaning tool, and so the source should be easy to
access.
We'd have the same problem with "blank". We are suppose to be able to
take the source and use it for the base of a new project. [And if it
ends up being a blank Maven project, that's OK by me :)]
Are you talking about where the source is in the repository, (and what the
"source distribution" looks like) or where the source is in the .war files?
What do you want it to look like?
Struts-blank may eventually go away in favor of something like:
$ mvn archetype:create
-DgroupId=my.package
-DartifactId=my-app
-DarchetypeArtifactId=maven-archetype-struts
-DarchetypeGroupId=org.apache.struts
Sort of like 'maven genapp' from Maven 1 except it looks like we'll be able
to publish our own archetypes in the repository with our other artifacts
rather than try to get them included in someone else's plugin.
Another thing I learned recently about Maven: we can publish source and
javadoc to the repository as additional artifacts. Then IDEs and tools can
automatically retrieve it. That's still an issue with Maven builds. You
can set up dependencies, but if you want to debug you have to go find the
source code.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
