Details

    • Type: Bug Bug
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 0.8.0
    • Fix Version/s: None
    • Component/s: Product Development
    • Labels:
      None
    • Environment:
      Windows
    • Global Rank:
      565

      Description

      If execute "mvn package" (without clean) twice, the native launcher name can not be changed to the custom launcher name defined in .product. Below is the error message:

      [ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-packaging-plugin:0.8.0:product-export (default-product-export) on project com.ualab.uprint: Could not rename native launcher to uprint.exe -> [Help 1]
      org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.sonatype.tycho:maven-osgi-packaging-plugin:0.8.0:product-export (default-product-export) on project com.ualab.uprint: Could not rename native launcher to uprint.exe
      at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:141)
      at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:77)
      at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:69)
      at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:82)
      at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:54)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.singleThreadedBuild(DefaultLifecycleExecutor.java:218)
      at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:190)
      at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:246)
      at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:95)
      at org.apache.maven.cli.MavenCli.execute(MavenCli.java:430)
      at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:160)
      at org.apache.maven.cli.MavenCli.main(MavenCli.java:124)
      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:597)
      at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
      at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
      at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
      at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
      Caused by: org.apache.maven.plugin.MojoExecutionException: Could not rename native launcher to uprint.exe
      at org.codehaus.tycho.eclipsepackaging.ProductExportMojo.copyExecutable(ProductExportMojo.java:710)
      at org.codehaus.tycho.eclipsepackaging.ProductExportMojo.execute(ProductExportMojo.java:168)
      at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:105)
      at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:133)
      ... 19 more

        Activity

        Hide
        Lothar Krenzien added a comment -

        Are there any plans to fix this bug ? I'm getting the same error everytime I'm calling 'mvn clean install'. At least in 0.10.0 the bug is still there (Windows 7 64-bit + Maven 3 beta).

        Show
        Lothar Krenzien added a comment - Are there any plans to fix this bug ? I'm getting the same error everytime I'm calling 'mvn clean install'. At least in 0.10.0 the bug is still there (Windows 7 64-bit + Maven 3 beta).
        Hide
        Simon Goodall added a comment -

        I have the same problem. I need to perform a clean everytime I try to build or test.
        The issue is due to the use of File.renameTo in ProductExportMojo.java.
        The following sun bug report talks about some issues with renameTo;

        http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4017593

        Show
        Simon Goodall added a comment - I have the same problem. I need to perform a clean everytime I try to build or test. The issue is due to the use of File.renameTo in ProductExportMojo.java. The following sun bug report talks about some issues with renameTo; http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4017593
        Hide
        David Schmitz added a comment - - edited

        Hi I am facing the same problem with tycho 0.9.0, maven3 beta3 and Windows XP.
        So please update the affected version also to tycho 0.9.0.

        I have to add the same project with launcher renaming can be build under Debian GNU\Linux 64bit.

        Show
        David Schmitz added a comment - - edited Hi I am facing the same problem with tycho 0.9.0, maven3 beta3 and Windows XP. So please update the affected version also to tycho 0.9.0. I have to add the same project with launcher renaming can be build under Debian GNU\Linux 64bit.
        Hide
        Simon Dunstone added a comment -

        We are also seeing this issue on our builds when running "mvn clean package install".

        Show
        Simon Dunstone added a comment - We are also seeing this issue on our builds when running "mvn clean package install".
        Hide
        Benedikt Meuthrath added a comment -

        Issue is still existent... (Tycho 0.10.0, Windows XP, Maven 3.0.2)

        Show
        Benedikt Meuthrath added a comment - Issue is still existent... (Tycho 0.10.0, Windows XP, Maven 3.0.2)
        Hide
        Tobias Oberlies added a comment -

        You are using the soon to be deprecated packaging type eclipse-application, so it is unlikely that any of the committers is going to work on this issue.

        You should try to use the packaging type eclipse-repository in version 0.11.0-SNAPSHOT instead.

        Show
        Tobias Oberlies added a comment - You are using the soon to be deprecated packaging type eclipse-application, so it is unlikely that any of the committers is going to work on this issue. You should try to use the packaging type eclipse-repository in version 0.11.0-SNAPSHOT instead.
        Hide
        Jan Sievers added a comment -

        I think Tobias' comment "soon to be deprecated packaging type eclipse-application"
        was premature.

        As we discussed already, if we can change the implementation of eclipse-application to be p2-enabled in 0.12.0, this will be just fine from my point of view.

        I don't really care for the name as long as we can avoid confusion with users.

        Show
        Jan Sievers added a comment - I think Tobias' comment "soon to be deprecated packaging type eclipse-application" was premature. As we discussed already, if we can change the implementation of eclipse-application to be p2-enabled in 0.12.0, this will be just fine from my point of view. I don't really care for the name as long as we can avoid confusion with users.
        Hide
        David Gonzales added a comment -

        Hi As a new user to this I do apologise if this has already been discussed as I am new at this.

        I'm using version 0.11 of tycho and have encountered this problem. This would mean that a clean of the project should allow the rebuilding of the application, I was wondering is the issue around this the attempt to rename the exe that is already there?

        Also regarding Tobias' comment why is eclipse-application going to be removed?
        I assumed eclipse repository would essentially be performing the job of creating a p2 repository that eclipse can do via the PluginAndFeatures command?

        Show
        David Gonzales added a comment - Hi As a new user to this I do apologise if this has already been discussed as I am new at this. I'm using version 0.11 of tycho and have encountered this problem. This would mean that a clean of the project should allow the rebuilding of the application, I was wondering is the issue around this the attempt to rename the exe that is already there? Also regarding Tobias' comment why is eclipse-application going to be removed? I assumed eclipse repository would essentially be performing the job of creating a p2 repository that eclipse can do via the PluginAndFeatures command?
        Hide
        Tobias Oberlies added a comment -

        The currently recommended way to build applications is using an extra POM configuration in eclipse-repository. Eventually, we will introduce a new packaging type "eclipse-product" for this task (see bug 348586). Then, "eclipse-application" will be deprecated. This approach was developed here: https://docs.sonatype.org/display/TYCHO/Discussion+on+eclipse-repository+packaging+type+clean-up

        If you have problems using eclipse-repository, please ask on tycho-user@eclipse.org

        Note that this issue tracker is no longer used by Tycho; the issues are now tracked at the Eclipse bugzilla

        Show
        Tobias Oberlies added a comment - The currently recommended way to build applications is using an extra POM configuration in eclipse-repository. Eventually, we will introduce a new packaging type "eclipse-product" for this task (see bug 348586 ). Then, "eclipse-application" will be deprecated. This approach was developed here: https://docs.sonatype.org/display/TYCHO/Discussion+on+eclipse-repository+packaging+type+clean-up If you have problems using eclipse-repository, please ask on tycho-user@eclipse.org Note that this issue tracker is no longer used by Tycho; the issues are now tracked at the Eclipse bugzilla

          People

          • Assignee:
            Unassigned
            Reporter:
            Forest Gao
            Last Updated By:
            Igor Fedorenko
          • Votes:
            2 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

            • Created:
              Updated:
              Date of First Response: