|
It is a big multi-module project with many interdependencies. Steps: 1. Import the parent pom -> OK TAG: HEAD (I also tried with the tag i want to use for the release...) [INFO] Updating local copy against the scm... Try downloading the file manually from the project website. Then, install it using the command: >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> 17) ehcache:ehcache:jar:1.3.0 Try downloading the file manually from the project website. Then, install it using the command: Path to dependency: ---------- for artifact: from the specified remote repositories: at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305) We are seeing the exact same behavior with 1.2.2. Our project structure sounds very similar to gulu's. Were you using the default local repository in your project group? I have the same situation as described above. I use continuum 1.2 (Build Number: 697023). I suppose we have same problem, by prepare release using goals: clean install Try downloading the file manually from the project website. Then, install it using the command: Alternatively, if you host your own repository you can deploy the file there: Path to dependency: ---------- for artifact: from the specified remote repositories: at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324) Please, add more informations:
and eventually a small project to reproduce it Hi, I changed my local repo location in settings.xml to one without a space, re built everything and I can use the release correctly now. Fixed parsing of local repo with spaces in it in revision 764682. James Gustards advice works for me on windows with continuum 1.2.3 / svn 1.5.0 / mvn 2.1.0. The default local maven repository is C:\Documents and Settings\Administrator\.m2\repository I have tried various things like changing the maven settings.xml files but this did not work. The following works: I have defined a Local Repository via the GUI (C:\maven\m2\repository). Next, I edited the my project groups "local repository" to use the new location (via group actions, edit). I can build, prepare and perform releases with this setup. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||
What are the steps to reproduce the error?
What does the project structure look like? (Multi-module? inter-dependencies?)
Does a forced build work correctly?
Does a release work if you change the goals to 'clean install' instead of 'clean integration-test'?