Christine wrote:
The mvn script for building my project was complaining about deploy-tools:
>[INFO] Trace
>org.apache.maven.BuildFailureException: Compilation failure
>error: error reading
/home/christine/.m2/repository/org/apache/portals/jetspeed-2/jetspeed-deploy-tools/2.2.0/jetspeed-deploy-tools-2.2.0.jar;
error >in opening zip file
>
> at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:579)
The pom.xml says "version 2.2.0" but the file that's downloaded says
"jetspeed-deploy-tools-2.2".
Hi Christine,
What do you mean by "says"?
In the repository, there's a
jetspeed-deploy-tools-2.2.0-SNAPSHOT.
I have manually downloaded the 2.2.0 file and put it in my maven
repository, now the project builds. I take it that some place in a pom
file, someone forgot a ".0"?
I don't think so.
If a specific dependency reference is specified as "2.2", Maven will only look for a 2.2 version, never "magically" append a ".0" to it if
it can't find a "2.2" version.
There is also a feature in Maven for version ranges but to enable and use that requires an explicit configuration, e.g. "[2.2,)" but we
don't use that with Jetspeed.
My guess is the 2.2.0 jar download was botched before, maybe because of a bad network connection at the time. Often Maven detects this
itself and can recover from it, but seemingly not always...
Groet,
Ate
dagdag
Christine
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscr...@portals.apache.org
For additional commands, e-mail: jetspeed-user-h...@portals.apache.org
