Re: Maven release plugin: Address already in use!

Mon, 26 Nov 2007 10:05:48 -0800 

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 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, Bashar Jawad <[EMAIL PROTECTED]> wrote:


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
release. I simply created a new empty maven 2 project and added the
required scm information in the POM. However any time I run the
command: mvn release:clean release:prepare maven asks me for
release/tag/developement version information and then exists with the
following error:

[INFO] Transforming 'Unnamed -
ReleasePluginDemo:ReleasePluginDemo:jar:1.0-SNAPSHOT'...
[INFO] Not generating release POMs
[INFO] Executing goals 'clean verify'...
[INFO] Executing: mvn clean verify --no-plugin-updates -P default
   ERROR: transport error 202: bind failed: Address already in use
["transport.c",L41]
   FATAL ERROR in native method: JDWP No transports initialized,
jvmtiError=JVMTI_ERROR_INTERNAL(113)
   ERROR: JDWP Transport dt_socket failed to initialize,
TRANSPORT_INIT(510) ["debugInit.c",L500]
   JDWP exit error JVMTI_ERROR_INTERNAL(113): No transports initialized
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Maven execution failed, exit code: '1'

[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Maven
execution failed, exit code: '1'
       at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(

DefaultLifecycleExecutor.java:564)

       at


org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(
DefaultLifecycleExecutor.java:493)

       at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(

DefaultLifecycleExecutor.java:463)

       at


org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures
(DefaultLifecycleExecutor.java:311)

       at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(

DefaultLifecycleExecutor.java:224)

       at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(

DefaultLifecycleExecutor.java:143)

       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
       at org.apache.maven.cli.MavenCli.main(MavenCli.java:280)
       at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
       at
sun.reflect.NativeMethodAccessorImpl.invoke(

NativeMethodAccessorImpl.java:39)

       at
sun.reflect.DelegatingMethodAccessorImpl.invoke(

DelegatingMethodAccessorImpl.java:25)

       at java.lang.reflect.Method.invoke(Method.java:585)
       at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
       at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
       at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
       at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: Maven
execution failed, exit code: '1'
       at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(

PrepareReleaseMojo.java:131)

       at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(

DefaultPluginManager.java:443)

       at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(

DefaultLifecycleExecutor.java:539)

       ... 16 more
Caused by: org.apache.maven.shared.release.ReleaseExecutionException:
Maven execution failed, exit code: '1'
       at
org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(

AbstractRunGoalsPhase.java:66)

       at
org.apache.maven.shared.release.phase.RunPrepareGoalsPhase.execute(

RunPrepareGoalsPhase.java:42)

       at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(

DefaultReleaseManager.java:194)

       at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(

DefaultReleaseManager.java:131)

       at
org.apache.maven.shared.release.DefaultReleaseManager.prepare(

DefaultReleaseManager.java:94)

       at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(

PrepareReleaseMojo.java:127)

       ... 18 more
Caused by:
org.apache.maven.shared.release.exec.MavenExecutorException: Maven
execution failed, exit code: '1'
       at
org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(

ForkedMavenExecutor.java:103)

       at
org.apache.maven.shared.release.exec.ForkedMavenExecutor.executeGoals(

ForkedMavenExecutor.java:121)

       at
org.apache.maven.shared.release.phase.AbstractRunGoalsPhase.execute(

AbstractRunGoalsPhase.java:59)

       ... 23 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 7 seconds
[INFO] Finished at: Wed Nov 21 14:37:09 MST 2007
[INFO] Final Memory: 4M/253M
[INFO] -------------------------------------------------------------




What port is maven complaining about ?




Thanks,
Bashar

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]







---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to