Jonathan Bender wrote:
@Greg: I'm not sure, if I got you right: Do you mean the download-links
of e.g. the pom-files are invalid, so that necessary pom-files are
missing, which leads to the build error? And does Jenks 2.2 contain the
components servicemix-common, servicemix-eip, servicemix-jms plus the
correct download-links?
Not quite. Assuming you haven't already deleted it, take a look at one of
the files it complained about, e.g.
C:\...\.m2\repository\org\springframework\spring-dao\2.0.6\spring-dao-2.0.6.jar
I suspect if you look at that file with a text editor it is actually an
HTML file, not a jar. The issue we had with jencks 2.1 is that its pom has
a reference to a repository URL that is no longer valid but that does not
result in an HTTP 404 when maven tries to download from it. So rather than
giving up and trying another repo, maven happily downloads the HTML
content served up and saves it as the desired artifact.
The first step as Gert suggested is to delete or rename your local repo
and try again to see if you end up in the same state.
--
Greg
