On 25.11.2007 23:47 Uhr, Joerg Heinicke wrote:
PS: There is also an error somewhere with the dependencies I think. XSP
block includes Avalon Framework 4.1.3 instead of 4.3.1 which causes
bunch of problems in Eclipse. How to trace the dependencies? Grek sent
once a mail with "mvn project-info-reports:dependencies" [1] but this
does not work for me:
Just check file target/site/dependencies.html. You will find
everything (or even more) you need there.
Oh man, I have not even had the idea of looking into an output
directory, I just expected it on the console. Anyway, this report does
not help at all, it only mentions 4.3.1 of Avalon Framework API and
Impl. The generated .classpath has following entries though:
<classpathentry kind="var"
path="M2_REPO/org/apache/avalon/framework/avalon-framework-impl/4.3.1/avalon-framework-impl-4.3.1.jar"
sourcepath="M2_REPO/org/apache/avalon/framework/avalon-framework-impl/4.3.1/avalon-framework-impl-4.3.1-sources.jar"/>
<classpathentry kind="var"
path="M2_REPO/avalon-framework/avalon-framework/4.1.3/avalon-framework-4.1.3.jar"/>
<classpathentry kind="var"
path="M2_REPO/org/apache/avalon/framework/avalon-framework-api/4.3.1/avalon-framework-api-4.3.1.jar"
sourcepath="M2_REPO/org/apache/avalon/framework/avalon-framework-api/4.3.1/avalon-framework-api-4.3.1-sources.jar"/>
Notably the difference in the module name:
org/apache/avalon/framework/avalon-framework-impl resp. -api
vs.
avalon-framework/avalon-framework
But how to trace it back when the dependency report does not even
mention it. I wonder if I'm actually the only one with this problem?
It's probably not critical since it seems to occur only with the Eclipse
plugin and fixing the build path is easy. But it might point to a deeper
error who the next one hit at a completely different point.
Found this thread on the user list which has the same symptoms:
http://marc.info/?t=117511412500001&r=1&w=4.
Joerg
