unsubscribe
From: David Hoffer
Sent: Friday, October 31, 2014 12:25 PM
To: Maven Users List
Subject: Re: Maven site fails with PluginContainerException
I think I found the cause of this. I had an older version of
maven-surefire-report-plugin that had the
I think I found the cause of this. I had an older version of
maven-surefire-report-plugin that had the old groupId & artifactId, with
that changed the build is getting further now.
-Dave
On Fri, Oct 31, 2014 at 1:07 PM, David Hoffer wrote:
> I'm trying to create a site report for an existing p
I'm trying to create a site report for an existing project and I get
a PluginContainerException. My command line is package site-deploy
Here is the error in debug:
[INFO]
[INFO] BUILD FAILURE
[INFO]
---
The Apache Maven team is pleased to announce the release of the Maven
Archiver, version 2.6.
This module generates browsable HTML pages from Java source code.
http://maven.apache.org/shared/maven-archiver/
You should specify the version in your project's dependency configuration:
org.apach
Hi Leonie,
I wasn't actually speaking about the Maven version, although that explains
why I couldn't see the versions of the plugins, but I was talking about
the maven-release-plugin version.
Because of that I assume you're using maven-release-plugin 2.0 (if you
haven't specified it in the
Thank you Robert. I'm not using the latest maven release. Using 2.0.10. Will
upgrade.
--
View this message in context:
http://maven.40175.n5.nabble.com/mvn-release-branch-updating-POM-incorrectly-tp5811978p5812022.html
Sent from the Maven - Users mailing list archive at Nabble.com.
--
Hi,
see MRELEASE-165 (release:prepare should fail if the tag already exists)[1]
The main reason why it is still not implemented, is that this must be
solved in the SCM project. If we know how to do a valid(!) check of the
existence of a tag for the scm providers, we could start implementing i
Hello,
one thing which bites me quite regularly with the maven release plugin
is the fact, that it will update the POMs to the release version then
commit them and then tag them. If the tagging fails (especially because
the tag existed already) then it will leave the head on a released
version num
Hi,
I can't see which version you are using.
A good start would be to ensure you're using the latest (i.e 2.5.1) by
locking the version in the pom.xml
If it still happens, go through the Jira list[1] to see if there's an
issue matching your problem.
thanks,
Robert
[1] https://jira.codehaus
Good day,
I hope someone can assist. I have posted something, but did not get any
reply. When running the release:branch, my branch gets created, but my scn
connection url in the trunk POM is not updating to point to the new branch's
URL.
I tried to pinpoint the problem. I opened the POM in notep
10 matches
Mail list logo