DependencyUtil.getFormattedFileName( artifact, removeVersion ) then executes. I cant change apache maven 2.1.1. Hide Permalink Hervé Boutemy added a comment - 01/Aug/12 16:16 duplicate of MDEP-187: closing this duplicate will help focus everybody's energy Show Hervé Boutemy added a comment - 01/Aug/12 16:16 duplicate If it fails this test, as this use case would, it simply logs a warning that the artifact is a directory and bypasses the copyFile call. this contact form
When executing 'mvn clean install' from the person-service-parent module within Eclipse (using either the Maven embedder or Maven 2.0.9) an error occurs related to copying the person-service jar file into the What's the point of repeating an email address in "The Envelope" and the "The Header"? Show Eugene Kuleshov added a comment - 07/May/09 09:10 - edited Guys, you can call this an m2eclipse bug or feature, but it all boils down to the current Maven and We updated Sonar and our builds started failing.
I do not know why it was not working in my case as he set it up. Hide Permalink jurevert added a comment - 24/Nov/11 07:32 - edited I have merge patch information in 2.1.1 maven-war plugin release. share|improve this answer edited Dec 30 '12 at 21:52 answered Dec 26 '12 at 14:47 Sean Dawson 142110 add a comment| Did you find this question interesting? Cheers!
more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed Sonar executes a second build cycle after the main cycle, which presumably excludes the package goal, triggering this error. SUCCESS [5.044s] [INFO] person-service project ................................ That assumption is wrong, and the minimum would be to add a check and fail the build with a meaningful error message if the artifact refers to a directory. 2.
If it fails on the command line, well that points to a Maven issue. How To Tell When Broccoli is Bad? Uncheck 'Resolve dependencies from Workspace projects' which solved the problem with the war plugin in m2eclipse. Hide Permalink Karl Heinz Marbaise added a comment - 17/Feb/16 17:19 Check this page: http://maven.apache.org/plugins/maven-war-plugin/plugin-info.html furthermore Maven 2.X is End Of Life Show Karl Heinz Marbaise added a comment - 17/Feb/16
To resolve this: Open Project->Properties->Maven. How to interpret this decision tree? The only difference I can figure is that those are deployed and I don't do that at home. For me, it was maven-dependency-plugin 2.1 (buggy) instead of 2.0 used by command line maven.