[
http://jira.codehaus.org/browse/MRPM-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216848#action_216848
]
Brett Okken commented on MRPM-70:
---------------------------------
{quote}
>From what I can see, it looks like the effective filename of the artifact is
>being calculated twice.
{quote}
I agree that is what appears is happening. However, I cannot reproduce the
issue. Can you attach the generated spec file and a debug (-X) log from an
error run?
{quote}
I suspect maven-rpm-plugin isn't respecting the timestamp conventions... All
other jars have no timestamps.
{quote}
The timestamp is just part of the rpm "release" or "build" portion of the (rpm)
version. This is done so that subsequent SNAPSHOT builds can use RPM's upgrade
command to install the newer SNAPSHOT. When rpmbuilds the file, it names it
following rpm convention. The maven-rpm-plugin just looking for the file at
that expected location. At that point it is just given to maven and maven will
rename it on install/deploy to follow maven's naming conventions.
> install/deploy error "java.io.IOException: File ... does not exist"
> -------------------------------------------------------------------
>
> 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
