It might be nice if Maven could be coded to watch for/parse this
exception and provide a more user-friendly error message, though.
Wayne
On 11/27/07, Jorg Heymans <[EMAIL PROTECTED]> wrote:
> It is not a maven limitation, but a java one. I would like the embedded
> maven to still be launched with
It is not a maven limitation, but a java one. I would like the embedded
maven to still be launched with MAVEN_OPTS in any case. It is up to the
developer to not set things in there that cannot be executed concurrently.
Jorg
On Nov 26, 2007 7:03 PM, Bashar Jawad <[EMAIL PROTECTED]> wrote:
> Yup,
Yup, that was the problem, removing the remote debug args fixed it.
Should I file a Jira issue about it?
Bashar
Jorg Heymans wrote:
I've seen this happening when MAVEN_OPTS is set to enable remote debugging.
What happens is that the release plugin invokes a system exec of some sort
of mvn which
What does your SCM configuration look like? Which protocol are you using?
Please give some more information.
With regards,
Nick Stolwijk
-Original Message-
From: Bashar Jawad [mailto:[EMAIL PROTECTED]
Sent: Mon 11/26/2007 5:11 PM
To: Maven Users List
Subject: Re: Maven release plugin
I've seen this happening when MAVEN_OPTS is set to enable remote debugging.
What happens is that the release plugin invokes a system exec of some sort
of mvn which then tries to use the same MAVEN_OPTS and fails because the
debug port is already taken.
Makes sense?
Jorg
On Nov 26, 2007 5:11 PM,
I still can't resolve this issue. I am using Maven 2.0.7. This is a
major blocker issue for me so I would really appreciate any help. Does
anyone at least know what port the release plugin uses ?
Thanks,
Bashar Jawad wrote:
I am trying to use the maven-release-plugin to prepare and perform a
