You can disable the use of the release profile. See the link Nick sent.
/Anders
On Tue, Jun 22, 2010 at 11:53, Daniele Dellafiore wrote:
> Ok, the problem here is that if this conflict with existent source and
> javadocs generation configuration, it causes the release to fail.
>
> On Tue, Jun 2
Ok, the problem here is that if this conflict with existent source and
javadocs generation configuration, it causes the release to fail.
On Tue, Jun 22, 2010 at 11:50 AM, Nick Stolwijk wrote:
> M-R-P activates a release profile by default, which contains the
> source and javadocs. See [1]
>
> [1]
M-R-P activates a release profile by default, which contains the
source and javadocs. See [1]
[1]
http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#useReleaseProfile
With regards,
Nick Stolwijk
~Java Developer~
IPROFS BV.
Claus Sluterweg 125
2012 WS Haarlem
http://www.ipro
ok, I changed executions goal from jar-no-fork to just "jar" and it works
I think that m-r-p by default has the attach-sources on the goal jar active
and if I add a jar-no-fork executions, they are summed.
In fact nowhere in my config I tell maven to make javadoc but the release
plugin just make it
I fixed the last problem removing myProject inheritance from the company
pom.
Now I am stucked cause the release plugin is deploying the source artifact
two times and the second time Nexus give me a 400 cause it does not allow to
overwrite an artifact in the release repository, and it's right.
It
Hi everyone.
MRP just suceeded in the prepare but fails immediately the perform phase,
with a:
Working directory "/home/[...] /myProject/target/checkout/myProject" does
not exist!
In fact it does not exists, the target/checkout folders contains:
src/
pom.xml
company-parent-1.0/
where src/ and
