New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fails when pom is a parent. #137
Comments
Hi, Can you provide the pom.xml (where do you configure the plugin) and the exception stacktrace (run mvn with '-e' ) ? |
Hi, Thank you. |
the pom fragment doesn't show where the plugin is configured : in pluginConfiguration, in build/plugins, in a profile,.... |
A side note about your pom :
|
I updated my parent pom plugins configuration here. I bumped up to latest version of maven-eclipse-plugin (eclipse is fine with Scala from mvn eclipse:eclipse) and I removed maven-helper-plugin. The original problem still there. For completeness, I run mvn with -X but there is no there is no stack-trace neither. Thank for your support. |
The Scala plugin bit looks just fine, so there's likely something else On Mon, Aug 26, 2013 at 10:08 PM, s17t.net notifications@github.com wrote:
|
Here the part (Scala bit omitted for brevity). I also tried
in the project folder but the error is the same. Thank for your support. |
In your pom.xml fragment scala-maven-plugin seems to be define under the , in this case the plugin will not run except if you call it explicitly from command line or also under . So can you provide the FULL pom.xml and the FULL output of 'mvn install -e' (send me a private email if you like) ? Internaly of the plugin management of src/main and src/test are simular, so if the issue come from scala-maven-plugin it should failed before (IMHO). May be the issue comme from an other plugin like the specs2 one (you can try to comment it). |
Very old issue, not enough information from the user and links are now broken. |
I have a parent pom in which the plugin is configured. When I install the parent pom with:
The build fails:
To get the build work I have to specify
-DskipTests
option.The text was updated successfully, but these errors were encountered: