You are viewing a plain text version of this content. The canonical link for it is here.
Posted to nmaven-issues@incubator.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2008/07/01 04:27:26 UTC
[jira] Commented: (NMAVEN-138) Code Signature not viewable from
within Visual Studio
[ http://jira.codehaus.org/browse/NMAVEN-138?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140031#action_140031 ]
Brett Porter commented on NMAVEN-138:
-------------------------------------
which "procedures listed" are you referring to? How can the original problem be reproduced?
> Code Signature not viewable from within Visual Studio
> -----------------------------------------------------
>
> Key: NMAVEN-138
> URL: http://jira.codehaus.org/browse/NMAVEN-138
> Project: NMaven
> Issue Type: Bug
> Affects Versions: 0.14 (Unreleased)
> Reporter: Leopoldo Agdeppa III
> Fix For: 0.14 (Unreleased)
>
> Attachments: NMAVEN-138.patch, screenshot-1.jpg
>
>
> When signing the code using the procedures listed, these updates are not reflected in the IDE.
> Example, from solution explorer > Properties > Signing. The display for signature / keyfile is blank.
> Only the pom is updated in the signing by nmaven. It should also update the csproj / vbproj file such that it will reflect the changes in solution explorer > Properties > Signing
--
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