[ 
http://jira.codehaus.org/browse/MRPM-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216769#action_216769
 ] 

Graham Leggett commented on MRPM-70:
------------------------------------

It looks like plugin cannot predict the name of the RPM file produced.

The file it is looking for, and the file that is produced have different names. 
The difference seems to be in a timestamp:

[minf...@257233-app1 statement]$ ls -al 
/home/chandler/minfrin/src/code/trunk/statement/statement/target/rpm/statement/RPMS/noarch/statement-0.0.3-SNAPSHOT20100405202256.noarch.rpm
 
-rw-r--r-- 1 minfrin minfrin 19894663 Apr  5 15:23 
/home/chandler/minfrin/src/code/trunk/statement/statement/target/rpm/statement/RPMS/noarch/statement-0.0.3-SNAPSHOT20100405202256.noarch.rpm
[minf...@257233-app1 statement]$ ls -al 
/home/chandler/minfrin/src/code/trunk/statement/statement/target/rpm/statement/RPMS/noarch/statement-0.0.3-SNAPSHOT20100405202253.noarch.rpm

The file the plugin is looking for ends in "56", while the actual file ends in 
"53".


> Silent failure: plugin swallows rpm error, says "java.io.IOException: File 
> ... does not exist" instead
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MRPM-70
>                 URL: http://jira.codehaus.org/browse/MRPM-70
>             Project: Mojo RPM Plugin
>          Issue Type: Bug
>          Components: rpm
>    Affects Versions: 2.0.1
>         Environment: java version "1.6.0"
> OpenJDK  Runtime Environment (build 1.6.0-b09)
> OpenJDK 64-Bit Server VM (build 1.6.0-b09, mixed mode)
>            Reporter: Graham Leggett
>            Assignee: Brett Okken
>
> When the maven-rpm-plugin is run, and an as-yet-unknown error is present 
> which causes rpmbuild to fail, the maven-rpm-plugin swallows the error, and 
> instead returns the next error along, the error that the RPM file does not 
> exist.
> What the plugin should do instead is tell the end user what rpmbuild said, so 
> they can respond to the error message and fix it, instead of being forced to 
> guess the error.
> The full trace looks like this:
> [INFO] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Error installing 
> artifact: File 
> /home/chandler/minfrin/src/code/trunk/statement/statement/target/rpm/statement/RPMS/noarch/statement-0.0.3-SNAPSHOT20100405200626.noarch.rpm
>  does not exist
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:719)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
>       at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
>       at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
>       at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
>       at 
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
>       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.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: Error installing 
> artifact: File 
> /home/chandler/minfrin/src/code/trunk/statement/statement/target/rpm/statement/RPMS/noarch/statement-0.0.3-SNAPSHOT20100405200626.noarch.rpm
>  does not exist
>       at 
> org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:143)
>       at 
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
>       at 
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
>       ... 17 more
> Caused by: org.apache.maven.artifact.installer.ArtifactInstallationException: 
> Error installing artifact: File 
> /home/chandler/minfrin/src/code/trunk/statement/statement/target/rpm/statement/RPMS/noarch/statement-0.0.3-SNAPSHOT20100405200626.noarch.rpm
>  does not exist
>       at 
> org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:119)
>       at 
> org.apache.maven.plugin.install.InstallMojo.execute(InstallMojo.java:105)
>       ... 19 more
> Caused by: java.io.IOException: File 
> /home/chandler/minfrin/src/code/trunk/statement/statement/target/rpm/statement/RPMS/noarch/statement-0.0.3-SNAPSHOT20100405200626.noarch.rpm
>  does not exist
>       at 
> hidden.org.codehaus.plexus.util.FileUtils.copyFile(FileUtils.java:1003)
>       at 
> org.apache.maven.artifact.installer.DefaultArtifactInstaller.install(DefaultArtifactInstaller.java:98)
>       ... 20 more

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply via email to