[jira] Updated: (MGPG-20) Error with classifiers

["clement escoffier (JIRA)" <ji...@codehaus.org>]

     [ http://jira.codehaus.org/browse/MGPG-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

clement escoffier updated MGPG-20:
----------------------------------

    Attachment: GPG-Classifier-Test.zip
                pom.xml

Upload a pom file reproducing the issue (as well as a project).
The issue comes when the project does not generate an artifact named regularly but always use classifier (in the project -jdk13 and -jdk15). 

Launching mvn clean package gpg:sign failed
Removing the jdk15 classifier fixes the issue.

> Error with classifiers
> ----------------------
>
>                 Key: MGPG-20
>                 URL: http://jira.codehaus.org/browse/MGPG-20
>             Project: Maven 2.x GPG Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0-alpha-4
>            Reporter: clement escoffier
>            Assignee: Benjamin Bentmann
>         Attachments: GPG-Classifier-Test.zip, pom.xml
>
>
> I've a project creating two artifacts with different classifiers. 
> When I try to sign them, I get :
> gpg: .../target/classes: read error: Is a directory
> Here is the stack trace in verbose mode:
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: Exit code: 2
> 	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: Exit code: 2
> 	at org.apache.maven.plugin.gpg.GpgSigner.generateSignatureForArtifact(GpgSigner.java:179)
> 	at org.apache.maven.plugin.gpg.GpgSignAttachedMojo.execute(GpgSignAttachedMojo.java:228)
> 	at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> 	at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> 	... 17 more
> If I change the configuration to generate only one artifact, it works (and the artifacts are signed).

-- 
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