You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by ul...@gi-de.com on 2006/09/27 17:12:03 UTC

release:perform using clearcase-scm

Hello,
I'm experimenting with the release-plugin of maven using scm:clearcase at
the moment. I finally got to a point, where the snapshot view is
successfully created,
and the originally started "mvn release:perform"  calls "mvn deploy
site-deploy --no-plugin-updates -DperformRelease=true" which fails (Error
stacktraces at the end of this message)
If I run "mvn deploy site-deploy -no-plugin-updates" in the snapshot view
that maven creates directly in the right path, it works without any
problem, so I guess the problem is that mvn release:perform executes mvn
deploy site-deploy  in the wrong place/path.
I would be glad if anyone could help me with this.
Greets,
Ulli Brennenstuhl


[INFO] Executing: mvn deploy site-deploy --no-plugin-updates
-DperformRelease=true
    + Error stacktraces are turned on.
    Maven version: 2.0.4
    [DEBUG] Building Maven user-level plugin registry from: 'C:\Dokumente
und Einstellungen\brennenu\.m2\plugin-registry.xml'
    [DEBUG] Building Maven global-level plugin registry from:
'C:\Programme\Maven\bin\..\conf\plugin-registry.xml'
    [INFO] Scanning for projects...
    [INFO]
----------------------------------------------------------------------------
    [INFO] Building Maven Default Project
    [INFO]    task-segment: [deploy, site-deploy]
    [INFO]
----------------------------------------------------------------------------
    [DEBUG] maven-resources-plugin: resolved to version 2.2 from repository
central
    [DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugins::1 for project:
null:maven-resources-plugin:maven-plugin:2.2 from
the repository.
    [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for
project: org.apache.maven.plugins:maven-plugins:pom:1 from the repos
itory.
    [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
org.apache.maven:maven-parent:pom:1 from the repository.
    [DEBUG] maven-compiler-plugin: resolved to version 2.0.1 from
repository central
    [DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugins::1 for project:
null:maven-compiler-plugin:maven-plugin:2.0.1 from
 the repository.
    [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for
project: org.apache.maven.plugins:maven-plugins:pom:1 from the repos
itory.
    [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
org.apache.maven:maven-parent:pom:1 from the repository.
    [DEBUG] maven-surefire-plugin: resolved to version 2.2 from repository
central
    [DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugins::1 for project:
null:maven-surefire-plugin:maven-plugin:2.2 from t
he repository.
    [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for
project: org.apache.maven.plugins:maven-plugins:pom:1 from the repos
itory.
    [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
org.apache.maven:maven-parent:pom:1 from the repository.
    [DEBUG] maven-jar-plugin: resolved to version 2.1 from repository
central
    [DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugins::3 for project:
null:maven-jar-plugin:maven-plugin:2.1 from the re
pository.
    [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::4 for
project: org.apache.maven.plugins:maven-plugins:pom:3 from the repos
itory.
    [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project:
org.apache.maven:maven-parent:pom:4 from the repository.
    [DEBUG] maven-install-plugin: resolved to version 2.1 from repository
central
    [DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugin-parent::2.0 for project:
null:maven-install-plugin:maven-plugin:2.1
 from the repository.
    [DEBUG] maven-deploy-plugin: resolved to version 2.2.1 from repository
central
    [DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugins::1 for project:
null:maven-deploy-plugin:maven-plugin:2.2.1 from t
he repository.
    [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for
project: org.apache.maven.plugins:maven-plugins:pom:1 from the repos
itory.
    [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
org.apache.maven:maven-parent:pom:1 from the repository.
    [DEBUG] maven-javadoc-plugin: resolved to version 2.0 from repository
central
    [DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugins::1 for project:
null:maven-javadoc-plugin:maven-plugin:2.0 from th
e repository.
    [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for
project: org.apache.maven.plugins:maven-plugins:pom:1 from the repos
itory.
    [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
org.apache.maven:maven-parent:pom:1 from the repository.
    [DEBUG] maven-source-plugin: resolved to version 2.0.1 from repository
central
    [DEBUG] Retrieving parent-POM:
org.apache.maven.plugins:maven-plugins::1 for project:
null:maven-source-plugin:maven-plugin:2.0.1 from t
he repository.
    [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::1 for
project: org.apache.maven.plugins:maven-plugins:pom:1 from the repos
itory.
    [DEBUG] Retrieving parent-POM: org.apache:apache::1 for project:
org.apache.maven:maven-parent:pom:1 from the repository.
    [INFO]
------------------------------------------------------------------------
    [ERROR] BUILD ERROR
    [INFO]
------------------------------------------------------------------------
    [INFO] Cannot execute mojo: resources. It requires a project with an
existing pom.xml, but the build is not using one.
    [INFO]
------------------------------------------------------------------------
    [DEBUG] Trace
    org.apache.maven.lifecycle.LifecycleExecutionException: Cannot execute
mojo: resources. It requires a project with an existing pom.xml,
but the build is not using one.
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
        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: Cannot
execute mojo: resources. It requires a project with an existing pom.xm
l, but the build is not using one.
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:339)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
        ... 16 more
    [INFO]
------------------------------------------------------------------------
    [INFO] Total time: 2 seconds
    [INFO] Finished at: Wed Sep 27 16:29:18 CEST 2006
    [INFO] Final Memory: 4M/7M
    [INFO]
------------------------------------------------------------------------


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Re: maven-native-plugin always re-runs native:link

Posted by dan tran <da...@gmail.com>.
Feel free to file jira, but i dont think you gain much performance on this
feature.

-D


On 9/27/06, dan tran <da...@gmail.com> wrote:
>
> yes, the link state always relink, just like java( jar )  packaging.
>
> -D
>
>
>  On 9/27/06, Brad Harper <br...@epsiia.com> wrote:
> >
> > Have I mis-configured the native:link goal?
> >
> > The maven-native-plugin /always/ re-links even when all of
> > the .o files are up to date.
> >
> > Brad
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>

Re: maven-native-plugin always re-runs native:link

Posted by dan tran <da...@gmail.com>.
yes, the link state always relink, just like java( jar )  packaging.

-D


On 9/27/06, Brad Harper <br...@epsiia.com> wrote:
>
> Have I mis-configured the native:link goal?
>
> The maven-native-plugin /always/ re-links even when all of
> the .o files are up to date.
>
> Brad
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

maven-native-plugin always re-runs native:link

Posted by Brad Harper <br...@epsiia.com>.
Have I mis-configured the native:link goal?

The maven-native-plugin /always/ re-links even when all of
the .o files are up to date.

Brad

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org