Wendy Smoak wrote:
On Tue, Mar 9, 2010 at 11:29 AM, Ron Wheeler
<[email protected]> wrote:
I suggested some rewording and table changes and provided an example to the
web page on transitive dependencies
(http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Transitive_Dependencies)
to make it more readable by someone who does not know how it works but they
were never incorporated.
Link? Is there a JIRA issue with a patch?
This was my posting with the suggestions.
It was at the end of a long discussion where Anders gently but firmly
hammered the concept of transitive dependencies into my thick skull.
I finally got it and now my staff regrets the day I found this. We are
refactoring all of our builds to use Maven differently (and, I hope,
better)!
I am sure that my wording could be improved and the example more detailed.
There was no positive response to my suggestion so I did not press the
issue with a JIRA entry.
Ron
Once you know the answer, the matrix is accurate but it is too
convoluted to be read by someone who does not know the answer already.
Each of the scopes (except for import) affects transitive dependencies
in different ways, as is demonstrated in the table below. If a
dependency is set to the scope in the left column, transitive
dependencies of that dependency with the scope across the top row will
result in a dependency in the main project with the scope listed at the
intersection. If no scope is listed, it means the dependency will be
omitted.
might be written as follows:
"Each of the scopes affects transitive dependencies in different ways.
The table below describes the rules. If a dependency in the higher level
pom is set to the scope in the left column and the transitive
dependencies of the lower level pom are set to the scopes named at the
top of other column, this will result in a dependency with the derived
scope listed in the cell at the intersection. If no scope is listed, it
means the dependency will be omitted.
For example, if the project pom declares a dependency on a group pom
with a scope of "provided" and the group pom includes a jar with scope
"compile", the resulting scope for that jar will be "provided".
Of course, "import" scope does not participate in transitive dependencies."
If it is possible to colour the table or apply fonts so that header
columns and rows are more clearly marked, that would also help.
Thanks for all the help. My test project compiles and produces a 27K war
file instead of a 21Mb war.
Once I get the other 20+ projects fixed up and tested, I will have a
much quicker portal startup and some relief from the Java equivalent of
dll-hell.
It also should make starting a new project much easier since the
dependencies are now grouped much more sensibly.
I just hope it runs after it is deployed.
Ron
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
