You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Thiago Leão Moreira (JIRA)" <ji...@codehaus.org> on 2010/06/06 21:12:12 UTC
[jira] Created: (MGPG-26) sign-and-deploy-file does not work with
javadoc and sources artifcats
sign-and-deploy-file does not work with javadoc and sources artifcats
---------------------------------------------------------------------
Key: MGPG-26
URL: http://jira.codehaus.org/browse/MGPG-26
Project: Maven 2.x GPG Plugin
Issue Type: Bug
Affects Versions: 1.1, 1.2
Reporter: Thiago Leão Moreira
Attachments: javadoc-sources.patch
If you are trying to deploy an Ant project with javadoc and sources the gpg plugin does not create the ".asc" appropriate file name for these types. Following is a snippet of Ant script that reproduce the issue.
<exec dir="." executable="${maven.executable}" failonerror="true">
<arg value="gpg:sign-and-deploy-file" />
<arg value="-DartifactId=core-client" />
<arg value="-Dfile=core-client-javadoc.jar" />
<arg value="-DgeneratePom=false" />
<arg value="-DgroupId=com.yournamehere" />
<arg value="-Dgpg.keyname=${gpg.keyname}" />
<arg value="-Dpackaging=javadoc" />
<arg value="-Dgpg.passphrase=${gpg.passphrase}" />
<arg value="-DrepositoryId=${maven.repository.id}" />
<arg value="-Durl=${maven.url}" />
<arg value="-Dversion=6.0.2" />
</exec>
The result will be "core-client-6.0.2-javadoc.javadoc.asc" when the right result would be "core-client-6.0.2-javadoc.jar.asc".
--
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
[jira] Updated: (MGPG-26) sign-and-deploy-file does not work with
javadoc and sources artifcats
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MGPG-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann updated MGPG-26:
----------------------------------
Affects Version/s: (was: 1.2)
> sign-and-deploy-file does not work with javadoc and sources artifcats
> ---------------------------------------------------------------------
>
> Key: MGPG-26
> URL: http://jira.codehaus.org/browse/MGPG-26
> Project: Maven 2.x GPG Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Thiago Leão Moreira
> Attachments: javadoc-sources.patch
>
>
> If you are trying to deploy an Ant project with javadoc and sources the gpg plugin does not create the ".asc" appropriate file name for these types. Following is a snippet of Ant script that reproduce the issue.
> <exec dir="." executable="${maven.executable}" failonerror="true">
> <arg value="gpg:sign-and-deploy-file" />
> <arg value="-DartifactId=core-client" />
> <arg value="-Dfile=core-client-javadoc.jar" />
> <arg value="-DgeneratePom=false" />
> <arg value="-DgroupId=com.yournamehere" />
> <arg value="-Dgpg.keyname=${gpg.keyname}" />
> <arg value="-Dpackaging=javadoc" />
> <arg value="-Dgpg.passphrase=${gpg.passphrase}" />
> <arg value="-DrepositoryId=${maven.repository.id}" />
> <arg value="-Durl=${maven.url}" />
> <arg value="-Dversion=6.0.2" />
> </exec>
> The result will be "core-client-6.0.2-javadoc.javadoc.asc" when the right result would be "core-client-6.0.2-javadoc.jar.asc".
--
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
[jira] Closed: (MGPG-26) sign-and-deploy-file does not work with
javadoc and sources artifcats
Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MGPG-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Benjamin Bentmann closed MGPG-26.
---------------------------------
Resolution: Fixed
Fix Version/s: 1.1.1
Assignee: Benjamin Bentmann
Fixed in [r951948|http://svn.apache.org/viewvc?view=revision&revision=951948].
A workaround for your case is to specify {{-Dclassifier=javadoc}} and {{-Dpackaging=jar}}.
> sign-and-deploy-file does not work with javadoc and sources artifcats
> ---------------------------------------------------------------------
>
> Key: MGPG-26
> URL: http://jira.codehaus.org/browse/MGPG-26
> Project: Maven 2.x GPG Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Thiago Leão Moreira
> Assignee: Benjamin Bentmann
> Fix For: 1.1.1
>
> Attachments: javadoc-sources.patch
>
>
> If you are trying to deploy an Ant project with javadoc and sources the gpg plugin does not create the ".asc" appropriate file name for these types. Following is a snippet of Ant script that reproduce the issue.
> <exec dir="." executable="${maven.executable}" failonerror="true">
> <arg value="gpg:sign-and-deploy-file" />
> <arg value="-DartifactId=core-client" />
> <arg value="-Dfile=core-client-javadoc.jar" />
> <arg value="-DgeneratePom=false" />
> <arg value="-DgroupId=com.yournamehere" />
> <arg value="-Dgpg.keyname=${gpg.keyname}" />
> <arg value="-Dpackaging=javadoc" />
> <arg value="-Dgpg.passphrase=${gpg.passphrase}" />
> <arg value="-DrepositoryId=${maven.repository.id}" />
> <arg value="-Durl=${maven.url}" />
> <arg value="-Dversion=6.0.2" />
> </exec>
> The result will be "core-client-6.0.2-javadoc.javadoc.asc" when the right result would be "core-client-6.0.2-javadoc.jar.asc".
--
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
[jira] Commented: (MGPG-26) sign-and-deploy-file does not work with
javadoc and sources artifcats
Posted by "Thiago Leão Moreira (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MGPG-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=224334#action_224334 ]
Thiago Leão Moreira commented on MGPG-26:
-----------------------------------------
Thanks Benjamin! The workaround worked fine.
> sign-and-deploy-file does not work with javadoc and sources artifcats
> ---------------------------------------------------------------------
>
> Key: MGPG-26
> URL: http://jira.codehaus.org/browse/MGPG-26
> Project: Maven 2.x GPG Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Reporter: Thiago Leão Moreira
> Assignee: Benjamin Bentmann
> Fix For: 1.1.1
>
> Attachments: javadoc-sources.patch
>
>
> If you are trying to deploy an Ant project with javadoc and sources the gpg plugin does not create the ".asc" appropriate file name for these types. Following is a snippet of Ant script that reproduce the issue.
> <exec dir="." executable="${maven.executable}" failonerror="true">
> <arg value="gpg:sign-and-deploy-file" />
> <arg value="-DartifactId=core-client" />
> <arg value="-Dfile=core-client-javadoc.jar" />
> <arg value="-DgeneratePom=false" />
> <arg value="-DgroupId=com.yournamehere" />
> <arg value="-Dgpg.keyname=${gpg.keyname}" />
> <arg value="-Dpackaging=javadoc" />
> <arg value="-Dgpg.passphrase=${gpg.passphrase}" />
> <arg value="-DrepositoryId=${maven.repository.id}" />
> <arg value="-Durl=${maven.url}" />
> <arg value="-Dversion=6.0.2" />
> </exec>
> The result will be "core-client-6.0.2-javadoc.javadoc.asc" when the right result would be "core-client-6.0.2-javadoc.jar.asc".
--
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