[
http://jira.codehaus.org/browse/NMAVEN-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NMAVEN-138:
--------------------------------
Description:
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
was:
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
Patch Submitted: [Yes]
> 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
