[jira] [Commented] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15175814#comment-15175814
]
Tony Chemit commented on MSITE-769:
---
That's just I have done. The previous behaviour was a nice help.
I can manage to add a live test.
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
> Attachments: MSITE-769.zip
>
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
> ${project.url}/index.html
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3063)
> at java.net.URI.(URI.java:588)
> at java.net.URI.create(URI.java:850)
> ... 34 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15172076#comment-15172076
]
Tony Chemit commented on MSITE-769:
---
Ok, so 3.5 is a breaking version arf :( Not a good news to me. Let me know if I
can help. thanks for the short notice reply [~michael-o] and [~hboutemy]
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
> Attachments: MSITE-769.zip
>
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
> ${project.url}/index.html
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3063)
> at java.net.URI.(URI.java:588)
> at java.net.URI.create(URI.java:850)
> ... 34 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit updated MSITE-769:
--
Attachment: MSITE-769.zip
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
> Attachments: MSITE-769.zip
>
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
> org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
> at
> org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
> at
> org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 21 more
> Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
> ${project.url}/index.html
> at java.net.URI$Parser.fail(URI.java:2848)
> at java.net.URI$Parser.checkChars(URI.java:3021)
> at java.net.URI$Parser.parseHierarchical(URI.java:3105)
> at java.net.URI$Parser.parse(URI.java:3063)
> at java.net.URI.(URI.java:588)
> at java.net.URI.create(URI.java:850)
> ... 34 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
[
https://issues.apache.org/jira/browse/MSITE-769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15171942#comment-15171942
]
Tony Chemit commented on MSITE-769:
---
The problem only occurs when I use a site descriptor coming from a parent
module.
In the example I give to you if you comment the parent in the pom.xml
everything is ok.
What I suspect is that if a site descriptor attribute coming from a parent does
not resolv variables in it.
In the example I give to you, you can see in the parent site descriptor I put
{noformat}
http://docutils.sourceforge.net/rst.html; name="ReStructuredText"
img="${someUrl}/images/logos/restructuredtext-logo.png"/>
{noformat}
which is well rendered, but in the child module I got this error
{noformat}
Caused by: java.lang.IllegalArgumentException: Illegal character in path at
index 1: ${someUrl}/images/logos/restructuredtext-logo.png
at java.net.URI.create(URI.java:852)
at
org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLogoPaths(DefaultDecorationModelInheritanceAssembler.java:311)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergePoweredByLists(DefaultDecorationModelInheritanceAssembler.java:361)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:87)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
at
org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
at
org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
at
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
{noformat}
> Can't use property in breadcrumbs items in child module site descriptor
> ---
>
> Key: MSITE-769
> URL: https://issues.apache.org/jira/browse/MSITE-769
> Project: Maven Site Plugin
> Issue Type: Bug
> Components: inheritance, site descriptor
>Affects Versions: 3.5
>Reporter: Tony Chemit
>Priority: Critical
>
> In a multi-module project, I have this in pom module site descriptor
> {noformat}
>
>
>href="${project.url}/v/${siteDeployClassifier}/en/index.html"/>
>
> {noformat}
> While running mvn site, the build fail with this error :
> {noformat}
> Caused by: java.lang.IllegalArgumentException: Illegal character in path at
> index 1: ${project.url}/index.html
> at java.net.URI.create(URI.java:852)
> at
> org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
> at
> org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
> at
> org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
> at
> org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
> at
>
[jira] [Created] (MSITE-769) Can't use property in breadcrumbs items in child module site descriptor
Tony Chemit created MSITE-769:
-
Summary: Can't use property in breadcrumbs items in child module
site descriptor
Key: MSITE-769
URL: https://issues.apache.org/jira/browse/MSITE-769
Project: Maven Site Plugin
Issue Type: Bug
Components: inheritance, site descriptor
Affects Versions: 3.5
Reporter: Tony Chemit
Priority: Critical
Fix For: 3.6
In a multi-module project, I have this in pom module site descriptor
{noformat}
{noformat}
While running mvn site, the build fail with this error :
{noformat}
Caused by: java.lang.IllegalArgumentException: Illegal character in path at
index 1: ${project.url}/index.html
at java.net.URI.create(URI.java:852)
at
org.apache.maven.doxia.site.decoration.inheritance.URIPathDescriptor.(URIPathDescriptor.java:69)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler$URLContainer.rebaseLink(DefaultDecorationModelInheritanceAssembler.java:453)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.rebaseLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:300)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:326)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:228)
at
org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:109)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:1171)
at
org.apache.maven.doxia.tools.DefaultSiteTool.getDecorationModel(DefaultSiteTool.java:423)
at
org.apache.maven.plugins.site.descriptor.AbstractSiteDescriptorMojo.prepareDecorationModel(AbstractSiteDescriptorMojo.java:86)
at
org.apache.maven.plugins.site.render.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:279)
at
org.apache.maven.plugins.site.render.SiteMojo.renderLocale(SiteMojo.java:151)
at
org.apache.maven.plugins.site.render.SiteMojo.execute(SiteMojo.java:135)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
... 21 more
Caused by: java.net.URISyntaxException: Illegal character in path at index 1:
${project.url}/index.html
at java.net.URI$Parser.fail(URI.java:2848)
at java.net.URI$Parser.checkChars(URI.java:3021)
at java.net.URI$Parser.parseHierarchical(URI.java:3105)
at java.net.URI$Parser.parse(URI.java:3063)
at java.net.URI.(URI.java:588)
at java.net.URI.create(URI.java:850)
... 34 more
{noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] (MPLUGIN-266) Incorrect warning comment about deprecated @component usage for maven objects
Tony Chemit created MPLUGIN-266:
---
Summary: Incorrect warning comment about deprecated @component
usage for maven objects
Key: MPLUGIN-266
URL: https://jira.codehaus.org/browse/MPLUGIN-266
Project: Maven Plugin Tools
Issue Type: Bug
Components: maven-plugin-annotations
Affects Versions: 3.3
Reporter: Tony Chemit
The warning says for example
{noformat}
@parameter name=${settings} @readonly
{noformat}
but the correct message is
{noformat}
@parameter default-value=${settings} @readonly
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPLUGIN-266) Incorrect warning comment about deprecated @component usage for maven objects
[
https://jira.codehaus.org/browse/MPLUGIN-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit updated MPLUGIN-266:
Assignee: Tony Chemit
Incorrect warning comment about deprecated @component usage for maven objects
-
Key: MPLUGIN-266
URL: https://jira.codehaus.org/browse/MPLUGIN-266
Project: Maven Plugin Tools
Issue Type: Bug
Components: maven-plugin-annotations
Affects Versions: 3.3
Reporter: Tony Chemit
Assignee: Tony Chemit
The warning says for example
{noformat}
@parameter name=${settings} @readonly
{noformat}
but the correct message is
{noformat}
@parameter default-value=${settings} @readonly
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPLUGIN-266) Incorrect warning comment about deprecated @component usage for maven objects
[
https://jira.codehaus.org/browse/MPLUGIN-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=347364#comment-347364
]
Tony Chemit commented on MPLUGIN-266:
-
Moreover, I am currently using java 5 annotations, so it is strange to get back
warnings in javadoc annotation style.
Incorrect warning comment about deprecated @component usage for maven objects
-
Key: MPLUGIN-266
URL: https://jira.codehaus.org/browse/MPLUGIN-266
Project: Maven Plugin Tools
Issue Type: Bug
Components: maven-plugin-annotations
Affects Versions: 3.3
Reporter: Tony Chemit
The warning says for example
{noformat}
@parameter name=${settings} @readonly
{noformat}
but the correct message is
{noformat}
@parameter default-value=${settings} @readonly
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPLUGIN-266) Incorrect warning comment about deprecated @component usage for maven objects
[
https://jira.codehaus.org/browse/MPLUGIN-266?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit closed MPLUGIN-266.
---
Resolution: Fixed
Fix Version/s: 3.4
Incorrect warning comment about deprecated @component usage for maven objects
-
Key: MPLUGIN-266
URL: https://jira.codehaus.org/browse/MPLUGIN-266
Project: Maven Plugin Tools
Issue Type: Bug
Components: maven-plugin-annotations
Affects Versions: 3.3
Reporter: Tony Chemit
Assignee: Tony Chemit
Fix For: 3.4
The warning says for example
{noformat}
@parameter name=${settings} @readonly
{noformat}
but the correct message is
{noformat}
@parameter default-value=${settings} @readonly
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPLUGIN-266) Incorrect warning comment about deprecated @component usage for maven objects
[
https://jira.codehaus.org/browse/MPLUGIN-266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=347371#comment-347371
]
Tony Chemit commented on MPLUGIN-266:
-
Done in [1599146|http://svn.apache.org/1599146]
Incorrect warning comment about deprecated @component usage for maven objects
-
Key: MPLUGIN-266
URL: https://jira.codehaus.org/browse/MPLUGIN-266
Project: Maven Plugin Tools
Issue Type: Bug
Components: maven-plugin-annotations
Affects Versions: 3.3
Reporter: Tony Chemit
Assignee: Tony Chemit
Fix For: 3.4
The warning says for example
{noformat}
@parameter name=${settings} @readonly
{noformat}
but the correct message is
{noformat}
@parameter default-value=${settings} @readonly
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHARED-322) Use maven-shared-utils 0.6
[ https://jira.codehaus.org/browse/MSHARED-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-322. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.3.2 Done in http://svn.apache.org/r1578834 Use maven-shared-utils 0.6 -- Key: MSHARED-322 URL: https://jira.codehaus.org/browse/MSHARED-322 Project: Maven Shared Components Issue Type: Task Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3.2 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-36) Use maven-shared-utils 0.6 and maven-jarsigner 1.3.2
[ https://jira.codehaus.org/browse/MJARSIGNER-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-36: -- Assignee: Tony Chemit Use maven-shared-utils 0.6 and maven-jarsigner 1.3.2 Key: MJARSIGNER-36 URL: https://jira.codehaus.org/browse/MJARSIGNER-36 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-36) Use maven-shared-utils 0.6 and maven-jarsigner 1.3.2
[ https://jira.codehaus.org/browse/MJARSIGNER-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=343116#comment-343116 ] Tony Chemit commented on MJARSIGNER-36: --- Done in Done in [r1578838|http://svn.apache.org/r1578838] Use maven-shared-utils 0.6 and maven-jarsigner 1.3.2 Key: MJARSIGNER-36 URL: https://jira.codehaus.org/browse/MJARSIGNER-36 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: 1.3.2 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-36) Use maven-shared-utils 0.6 and maven-jarsigner 1.3.2
[ https://jira.codehaus.org/browse/MJARSIGNER-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-36. - Resolution: Fixed Fix Version/s: 1.3.2 Use maven-shared-utils 0.6 and maven-jarsigner 1.3.2 Key: MJARSIGNER-36 URL: https://jira.codehaus.org/browse/MJARSIGNER-36 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: 1.3.2 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-316) Can not pass storetype nor storepass to a verify request
[ https://jira.codehaus.org/browse/MSHARED-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reopened MSHARED-316: - Can not pass storetype nor storepass to a verify request Key: MSHARED-316 URL: https://jira.codehaus.org/browse/MSHARED-316 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3.2 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-35) verbose mode shows keystore password in clear text
[ https://jira.codehaus.org/browse/MJARSIGNER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342583#comment-342583 ] Tony Chemit commented on MJARSIGNER-35: --- @S Yes it should also integrates the MJARSIGNER-34. I will then add -storepass, -storetype and -providerXXX but not -keypass, as I don't thing we need it, except if you explain me why? ;) verbose mode shows keystore password in clear text -- Key: MJARSIGNER-35 URL: https://jira.codehaus.org/browse/MJARSIGNER-35 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3.1 Reporter: Marco Speranza Assignee: Tony Chemit Fix For: 1.3.2 If is enabled verbose output, is printed out to the command line the keystore password in clear text. here is an example: [INFO] cmd.exe /X /C C:\Program Files\Java\jdk1.7.0_51\jre\..\bin\jarsigner.exe -verbose -keystore mc-keystore -storepass mypassword -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-34) The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
[
https://jira.codehaus.org/browse/MJARSIGNER-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit reopened MJARSIGNER-34:
---
The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
Key: MJARSIGNER-34
URL: https://jira.codehaus.org/browse/MJARSIGNER-34
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.3.1
Reporter: Christian Schulte
Assignee: Tony Chemit
Priority: Blocker
Fix For: 1.3.2
Upgrading the 'maven-jarsigner-plugin' from version 1.2 to version 1.3.1, the
plugin stops working. In version 1.2, the 'verify' goal did not pass
'-keystore' to 'jarsigner'. As of version 1.3, the 'verify' goal passes
'-keystore' to 'jarsigner' but does not pass '-storetype' which makes the
'verify' goal fail with:
jarsigner error: keystore load: Invalid keystore format
due to
{xml}
jarsigner.storetypepkcs12/jarsigner.storetype
{xml}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSHARED-316) Can not pass storetype nor storepass to a verify request
[ https://jira.codehaus.org/browse/MSHARED-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342587#comment-342587 ] Tony Chemit commented on MSHARED-316: - Done in [r1575435|http://svn.apache.org/r1575435] Can not pass storetype nor storepass to a verify request Key: MSHARED-316 URL: https://jira.codehaus.org/browse/MSHARED-316 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3.2 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-316) Can not pass storetype nor storepass to a verify request
[ https://jira.codehaus.org/browse/MSHARED-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-316. --- Resolution: Fixed Can not pass storetype nor storepass to a verify request Key: MSHARED-316 URL: https://jira.codehaus.org/browse/MSHARED-316 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3.2 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-34) The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
[
https://jira.codehaus.org/browse/MJARSIGNER-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342588#comment-342588
]
Tony Chemit commented on MJARSIGNER-34:
---
Done in [r1575440|http://svn.apache.org/r1575440]
The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
Key: MJARSIGNER-34
URL: https://jira.codehaus.org/browse/MJARSIGNER-34
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.3.1
Reporter: Christian Schulte
Assignee: Tony Chemit
Priority: Blocker
Fix For: 1.3.2
Upgrading the 'maven-jarsigner-plugin' from version 1.2 to version 1.3.1, the
plugin stops working. In version 1.2, the 'verify' goal did not pass
'-keystore' to 'jarsigner'. As of version 1.3, the 'verify' goal passes
'-keystore' to 'jarsigner' but does not pass '-storetype' which makes the
'verify' goal fail with:
jarsigner error: keystore load: Invalid keystore format
due to
{xml}
jarsigner.storetypepkcs12/jarsigner.storetype
{xml}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJARSIGNER-34) The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
[
https://jira.codehaus.org/browse/MJARSIGNER-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit closed MJARSIGNER-34.
-
Resolution: Fixed
The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
Key: MJARSIGNER-34
URL: https://jira.codehaus.org/browse/MJARSIGNER-34
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.3.1
Reporter: Christian Schulte
Assignee: Tony Chemit
Priority: Blocker
Fix For: 1.3.2
Upgrading the 'maven-jarsigner-plugin' from version 1.2 to version 1.3.1, the
plugin stops working. In version 1.2, the 'verify' goal did not pass
'-keystore' to 'jarsigner'. As of version 1.3, the 'verify' goal passes
'-keystore' to 'jarsigner' but does not pass '-storetype' which makes the
'verify' goal fail with:
jarsigner error: keystore load: Invalid keystore format
due to
{xml}
jarsigner.storetypepkcs12/jarsigner.storetype
{xml}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJARSIGNER-35) verbose mode shows keystore password in clear text
[ https://jira.codehaus.org/browse/MJARSIGNER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=342590#comment-342590 ] Tony Chemit commented on MJARSIGNER-35: --- I just deployed a new snapshot, feel free to test it. I will if everything ok, plan a new release next week. verbose mode shows keystore password in clear text -- Key: MJARSIGNER-35 URL: https://jira.codehaus.org/browse/MJARSIGNER-35 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3.1 Reporter: Marco Speranza Assignee: Tony Chemit Fix For: 1.3.2 If is enabled verbose output, is printed out to the command line the keystore password in clear text. here is an example: [INFO] cmd.exe /X /C C:\Program Files\Java\jdk1.7.0_51\jre\..\bin\jarsigner.exe -verbose -keystore mc-keystore -storepass mypassword -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-35) verbose mode shows keystore password in clear text
[ https://jira.codehaus.org/browse/MJARSIGNER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=341975#comment-341975 ] Tony Chemit commented on MJARSIGNER-35: --- You can use the snapshot repository http://repository.apache.org/content/groups/snapshots verbose mode shows keystore password in clear text -- Key: MJARSIGNER-35 URL: https://jira.codehaus.org/browse/MJARSIGNER-35 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3.1 Reporter: Marco Speranza Assignee: Tony Chemit Fix For: 1.3.2 If is enabled verbose output, is printed out to the command line the keystore password in clear text. here is an example: [INFO] cmd.exe /X /C C:\Program Files\Java\jdk1.7.0_51\jre\..\bin\jarsigner.exe -verbose -keystore mc-keystore -storepass mypassword -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-320) Be able to mask some arguments in the commandLine API
Tony Chemit created MSHARED-320: --- Summary: Be able to mask some arguments in the commandLine API Key: MSHARED-320 URL: https://jira.codehaus.org/browse/MSHARED-320 Project: Maven Shared Components Issue Type: Improvement Components: maven-shared-utils Affects Versions: maven-shared-utils-0.5 Reporter: Tony Chemit There is actually no way to mask some arguments passed to the CommandLine tool. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-320) Be able to mask some arguments in the commandLine API
[ https://jira.codehaus.org/browse/MSHARED-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-320: Assignee: Tony Chemit Be able to mask some arguments in the commandLine API - Key: MSHARED-320 URL: https://jira.codehaus.org/browse/MSHARED-320 Project: Maven Shared Components Issue Type: Improvement Components: maven-shared-utils Affects Versions: maven-shared-utils-0.5 Reporter: Tony Chemit Assignee: Tony Chemit There is actually no way to mask some arguments passed to the CommandLine tool. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-320) Be able to mask some arguments in the commandLine API
[ https://jira.codehaus.org/browse/MSHARED-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340783#comment-340783 ] Tony Chemit commented on MSHARED-320: - Done in [r1565593|http://svn.apache.org/r1565593] Be able to mask some arguments in the commandLine API - Key: MSHARED-320 URL: https://jira.codehaus.org/browse/MSHARED-320 Project: Maven Shared Components Issue Type: Improvement Components: maven-shared-utils Affects Versions: maven-shared-utils-0.5 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-shared-utils-0.6 There is actually no way to mask some arguments passed to the CommandLine tool. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-321) Mask passwords in logs
Tony Chemit created MSHARED-321: --- Summary: Mask passwords in logs Key: MSHARED-321 URL: https://jira.codehaus.org/browse/MSHARED-321 Project: Maven Shared Components Issue Type: Improvement Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-320) Be able to mask some arguments in the commandLine API
[ https://jira.codehaus.org/browse/MSHARED-320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-320. --- Resolution: Fixed Fix Version/s: maven-shared-utils-0.6 Be able to mask some arguments in the commandLine API - Key: MSHARED-320 URL: https://jira.codehaus.org/browse/MSHARED-320 Project: Maven Shared Components Issue Type: Improvement Components: maven-shared-utils Affects Versions: maven-shared-utils-0.5 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-shared-utils-0.6 There is actually no way to mask some arguments passed to the CommandLine tool. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-321) Mask passwords in logs
[ https://jira.codehaus.org/browse/MSHARED-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-321: Assignee: Tony Chemit Mask passwords in logs -- Key: MSHARED-321 URL: https://jira.codehaus.org/browse/MSHARED-321 Project: Maven Shared Components Issue Type: Improvement Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-322) Use maven-shared-utils 0.6
[ https://jira.codehaus.org/browse/MSHARED-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-322: Assignee: Tony Chemit Use maven-shared-utils 0.6 -- Key: MSHARED-322 URL: https://jira.codehaus.org/browse/MSHARED-322 Project: Maven Shared Components Issue Type: Task Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-322) Use maven-shared-utils 0.6
Tony Chemit created MSHARED-322: --- Summary: Use maven-shared-utils 0.6 Key: MSHARED-322 URL: https://jira.codehaus.org/browse/MSHARED-322 Project: Maven Shared Components Issue Type: Task Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-322) Use maven-shared-utils 0.6
[ https://jira.codehaus.org/browse/MSHARED-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340785#comment-340785 ] Tony Chemit commented on MSHARED-322: - Snapshot on r1565594. Use maven-shared-utils 0.6 -- Key: MSHARED-322 URL: https://jira.codehaus.org/browse/MSHARED-322 Project: Maven Shared Components Issue Type: Task Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-321) Mask passwords in logs
[ https://jira.codehaus.org/browse/MSHARED-321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340786#comment-340786 ] Tony Chemit commented on MSHARED-321: - Done in [r1565596|http://svn.apache.org/r1565596] Mask passwords in logs -- Key: MSHARED-321 URL: https://jira.codehaus.org/browse/MSHARED-321 Project: Maven Shared Components Issue Type: Improvement Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3.2 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSHARED-321) Mask passwords in logs
[ https://jira.codehaus.org/browse/MSHARED-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-321. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.3.2 Mask passwords in logs -- Key: MSHARED-321 URL: https://jira.codehaus.org/browse/MSHARED-321 Project: Maven Shared Components Issue Type: Improvement Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3.2 -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-35) verbose mode shows keystore password in clear text
[ https://jira.codehaus.org/browse/MJARSIGNER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-35: -- Assignee: Tony Chemit verbose mode shows keystore password in clear text -- Key: MJARSIGNER-35 URL: https://jira.codehaus.org/browse/MJARSIGNER-35 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3.1 Reporter: Marco Speranza Assignee: Tony Chemit If is enabled verbose output, is printed out to the command line the keystore password in clear text. here is an example: [INFO] cmd.exe /X /C C:\Program Files\Java\jdk1.7.0_51\jre\..\bin\jarsigner.exe -verbose -keystore mc-keystore -storepass mypassword -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-35) verbose mode shows keystore password in clear text
[ https://jira.codehaus.org/browse/MJARSIGNER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-35. - Resolution: Fixed Fix Version/s: 1.3.2 verbose mode shows keystore password in clear text -- Key: MJARSIGNER-35 URL: https://jira.codehaus.org/browse/MJARSIGNER-35 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3.1 Reporter: Marco Speranza Assignee: Tony Chemit Fix For: 1.3.2 If is enabled verbose output, is printed out to the command line the keystore password in clear text. here is an example: [INFO] cmd.exe /X /C C:\Program Files\Java\jdk1.7.0_51\jre\..\bin\jarsigner.exe -verbose -keystore mc-keystore -storepass mypassword -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-35) verbose mode shows keystore password in clear text
[ https://jira.codehaus.org/browse/MJARSIGNER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340787#comment-340787 ] Tony Chemit commented on MJARSIGNER-35: --- Use maven-shared-utils 0.6 snapshot [r1565599|http://svn.apache.org/r1565599] verbose mode shows keystore password in clear text -- Key: MJARSIGNER-35 URL: https://jira.codehaus.org/browse/MJARSIGNER-35 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3.1 Reporter: Marco Speranza Assignee: Tony Chemit Fix For: 1.3.2 If is enabled verbose output, is printed out to the command line the keystore password in clear text. here is an example: [INFO] cmd.exe /X /C C:\Program Files\Java\jdk1.7.0_51\jre\..\bin\jarsigner.exe -verbose -keystore mc-keystore -storepass mypassword -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-36) Use maven-shared-utils 0.6 and maven-jarsigner 1.3.2
Tony Chemit created MJARSIGNER-36: - Summary: Use maven-shared-utils 0.6 and maven-jarsigner 1.3.2 Key: MJARSIGNER-36 URL: https://jira.codehaus.org/browse/MJARSIGNER-36 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.3.1 Reporter: Tony Chemit -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJARSIGNER-35) verbose mode shows keystore password in clear text
[ https://jira.codehaus.org/browse/MJARSIGNER-35?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340788#comment-340788 ] Tony Chemit commented on MJARSIGNER-35: --- Thomas I just deployed a snapshot, feel free to test it. verbose mode shows keystore password in clear text -- Key: MJARSIGNER-35 URL: https://jira.codehaus.org/browse/MJARSIGNER-35 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3.1 Reporter: Marco Speranza Assignee: Tony Chemit Fix For: 1.3.2 If is enabled verbose output, is printed out to the command line the keystore password in clear text. here is an example: [INFO] cmd.exe /X /C C:\Program Files\Java\jdk1.7.0_51\jre\..\bin\jarsigner.exe -verbose -keystore mc-keystore -storepass mypassword -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MSKINS-91) Should use as possible https resources
Tony Chemit created MSKINS-91:
-
Summary: Should use as possible https resources
Key: MSKINS-91
URL: https://jira.codehaus.org/browse/MSKINS-91
Project: Maven Skins
Issue Type: Improvement
Components: Fluido Skin
Affects Versions: fluido-1.3.1
Reporter: Tony Chemit
When generating a maven site for a https target, there is some scripts called
from http, this is a security leak.
I see this possible url to change:
{noformat}
http://www.google.com/coop/cse/brand?form=search-form
http://github.com
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSKINS-91) Should use as possible https resources
[
https://jira.codehaus.org/browse/MSKINS-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit updated MSKINS-91:
--
Assignee: Tony Chemit
Should use as possible https resources
--
Key: MSKINS-91
URL: https://jira.codehaus.org/browse/MSKINS-91
Project: Maven Skins
Issue Type: Improvement
Components: Fluido Skin
Affects Versions: fluido-1.3.1
Reporter: Tony Chemit
Assignee: Tony Chemit
When generating a maven site for a https target, there is some scripts called
from http, this is a security leak.
I see this possible url to change:
{noformat}
http://www.google.com/coop/cse/brand?form=search-form
http://github.com
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSKINS-91) Should use as possible https resources
[
https://jira.codehaus.org/browse/MSKINS-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=340546#comment-340546
]
Tony Chemit commented on MSKINS-91:
---
Done in {{{rev1563746}}}
Should use as possible https resources
--
Key: MSKINS-91
URL: https://jira.codehaus.org/browse/MSKINS-91
Project: Maven Skins
Issue Type: Improvement
Components: Fluido Skin
Affects Versions: fluido-1.3.1
Reporter: Tony Chemit
Assignee: Tony Chemit
Fix For: fluido-1.4.0
When generating a maven site for a https target, there is some scripts called
from http, this is a security leak.
I see this possible url to change:
{noformat}
http://www.google.com/coop/cse/brand?form=search-form
http://github.com
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MSKINS-91) Should use as possible https resources
[
https://jira.codehaus.org/browse/MSKINS-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit closed MSKINS-91.
-
Resolution: Fixed
Fix Version/s: fluido-1.4.0
Should use as possible https resources
--
Key: MSKINS-91
URL: https://jira.codehaus.org/browse/MSKINS-91
Project: Maven Skins
Issue Type: Improvement
Components: Fluido Skin
Affects Versions: fluido-1.3.1
Reporter: Tony Chemit
Assignee: Tony Chemit
Fix For: fluido-1.4.0
When generating a maven site for a https target, there is some scripts called
from http, this is a security leak.
I see this possible url to change:
{noformat}
http://www.google.com/coop/cse/brand?form=search-form
http://github.com
{noformat}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJARSIGNER-30) IT failures with Jdk 8 (EA)
[
https://jira.codehaus.org/browse/MJARSIGNER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338499#comment-338499
]
Tony Chemit edited comment on MJARSIGNER-30 at 1/12/14 6:09 PM:
With jdk 1.8, when can not verify a jar then exit code is 1 (this is normal);
while with jdk 1.8, result code is 0.
IMHO, this is a bug from jdk 1.8: when a command fails, you can't have a result
code to 0.
We need to open/track this *regression*.
was (Author: tchemit):
With jdk 1.8, when can not verify a jar then exit code is 1 (this is
normal); while with jdk 1.8, result code is 0.
IMHO, this is a bug from jdk 1.8: when a command fails, you can't have a result
code to 0.
We nned to open/track this *regression*.
IT failures with Jdk 8 (EA)
---
Key: MJARSIGNER-30
URL: https://jira.codehaus.org/browse/MJARSIGNER-30
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.2
Reporter: Herve Boutemy
see
https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/modules
{noformat}[INFO] --- maven-invoker-plugin:1.7:verify (integration-test) @
maven-jarsigner-plugin ---
[INFO] -
[INFO] Build Summary:
[INFO] Passed: 7, Failed: 1, Errors: 0, Skipped: 0
[INFO] -
[ERROR] The following builds failed:
[ERROR] * verify-fail/pom.xml
[INFO] -{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-30) IT failures with Jdk 8 (EA)
[
https://jira.codehaus.org/browse/MJARSIGNER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338499#comment-338499
]
Tony Chemit commented on MJARSIGNER-30:
---
With jdk 1.8, when can not verify a jar then exit code is 1 (this is normal);
while with jdk 1.8, result code is 0.
IMHO, this is a bug from jdk 1.8: when a command fails, you can't have a result
code to 0.
We nned to open/track this *regression*.
IT failures with Jdk 8 (EA)
---
Key: MJARSIGNER-30
URL: https://jira.codehaus.org/browse/MJARSIGNER-30
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.2
Reporter: Herve Boutemy
see
https://builds.apache.org/view/M-R/view/Maven/job/maven-plugins-ITs-m3.1.x-with-maven-plugin-jdk-1.8/modules
{noformat}[INFO] --- maven-invoker-plugin:1.7:verify (integration-test) @
maven-jarsigner-plugin ---
[INFO] -
[INFO] Build Summary:
[INFO] Passed: 7, Failed: 1, Errors: 0, Skipped: 0
[INFO] -
[ERROR] The following builds failed:
[ERROR] * verify-fail/pom.xml
[INFO] -{noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-316) Can not pass storetype nor storepass to a verify request
Tony Chemit created MSHARED-316: --- Summary: Can not pass storetype nor storepass to a verify request Key: MSHARED-316 URL: https://jira.codehaus.org/browse/MSHARED-316 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-316) Can not pass storetype nor storepass to a verify request
[ https://jira.codehaus.org/browse/MSHARED-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-316. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.3.2 Assignee: Tony Chemit Can not pass storetype nor storepass to a verify request Key: MSHARED-316 URL: https://jira.codehaus.org/browse/MSHARED-316 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-34) The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
[
https://jira.codehaus.org/browse/MJARSIGNER-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit updated MJARSIGNER-34:
--
Assignee: Tony Chemit
The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
Key: MJARSIGNER-34
URL: https://jira.codehaus.org/browse/MJARSIGNER-34
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.3.1
Reporter: Christian Schulte
Assignee: Tony Chemit
Priority: Blocker
Upgrading the 'maven-jarsigner-plugin' from version 1.2 to version 1.3.1, the
plugin stops working. In version 1.2, the 'verify' goal did not pass
'-keystore' to 'jarsigner'. As of version 1.3, the 'verify' goal passes
'-keystore' to 'jarsigner' but does not pass '-storetype' which makes the
'verify' goal fail with:
jarsigner error: keystore load: Invalid keystore format
due to
{xml}
jarsigner.storetypepkcs12/jarsigner.storetype
{xml}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-316) Can not pass storetype nor storepass to a verify request
[ https://jira.codehaus.org/browse/MSHARED-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338381#comment-338381 ] Tony Chemit commented on MSHARED-316: - Done in [r1557255|http://svn.apache.org/r1557255] Can not pass storetype nor storepass to a verify request Key: MSHARED-316 URL: https://jira.codehaus.org/browse/MSHARED-316 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-34) The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
[
https://jira.codehaus.org/browse/MJARSIGNER-34?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338383#comment-338383
]
Tony Chemit commented on MJARSIGNER-34:
---
Dine in [r1557259|http://svn.apache.org/r1557259]
The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
Key: MJARSIGNER-34
URL: https://jira.codehaus.org/browse/MJARSIGNER-34
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.3.1
Reporter: Christian Schulte
Assignee: Tony Chemit
Priority: Blocker
Fix For: 1.3.2
Upgrading the 'maven-jarsigner-plugin' from version 1.2 to version 1.3.1, the
plugin stops working. In version 1.2, the 'verify' goal did not pass
'-keystore' to 'jarsigner'. As of version 1.3, the 'verify' goal passes
'-keystore' to 'jarsigner' but does not pass '-storetype' which makes the
'verify' goal fail with:
jarsigner error: keystore load: Invalid keystore format
due to
{xml}
jarsigner.storetypepkcs12/jarsigner.storetype
{xml}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-34) The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
[
https://jira.codehaus.org/browse/MJARSIGNER-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit closed MJARSIGNER-34.
-
Resolution: Fixed
Fix Version/s: 1.3.2
The 'verify' goal of the plugin is passing '-keystore' but not '-storetype'.
Key: MJARSIGNER-34
URL: https://jira.codehaus.org/browse/MJARSIGNER-34
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.3.1
Reporter: Christian Schulte
Assignee: Tony Chemit
Priority: Blocker
Fix For: 1.3.2
Upgrading the 'maven-jarsigner-plugin' from version 1.2 to version 1.3.1, the
plugin stops working. In version 1.2, the 'verify' goal did not pass
'-keystore' to 'jarsigner'. As of version 1.3, the 'verify' goal passes
'-keystore' to 'jarsigner' but does not pass '-storetype' which makes the
'verify' goal fail with:
jarsigner error: keystore load: Invalid keystore format
due to
{xml}
jarsigner.storetypepkcs12/jarsigner.storetype
{xml}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-315) Unsign jars are still not ok
Tony Chemit created MSHARED-315: --- Summary: Unsign jars are still not ok Key: MSHARED-315 URL: https://jira.codehaus.org/browse/MSHARED-315 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3 Reporter: Tony Chemit A typo came in code and the manifest file is not ok, main attributes are cleared instead of entries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-315) Unsign jars are still not ok
[ https://jira.codehaus.org/browse/MSHARED-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-315: Assignee: Tony Chemit Unsign jars are still not ok Key: MSHARED-315 URL: https://jira.codehaus.org/browse/MSHARED-315 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3 Reporter: Tony Chemit Assignee: Tony Chemit A typo came in code and the manifest file is not ok, main attributes are cleared instead of entries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-315) Unsign jars are still not ok
[ https://jira.codehaus.org/browse/MSHARED-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-315. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.3.1 Unsign jars are still not ok Key: MSHARED-315 URL: https://jira.codehaus.org/browse/MSHARED-315 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3.1 A typo came in code and the manifest file is not ok, main attributes are cleared instead of entries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-315) Unsign jars are still not ok
[ https://jira.codehaus.org/browse/MSHARED-315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=338059#comment-338059 ] Tony Chemit commented on MSHARED-315: - Fixed in [r1555198|http://svn.apache.org/r1555198] Unsign jars are still not ok Key: MSHARED-315 URL: https://jira.codehaus.org/browse/MSHARED-315 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.3 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3.1 A typo came in code and the manifest file is not ok, main attributes are cleared instead of entries. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-33) Sign already signed jar still does not work
Tony Chemit created MJARSIGNER-33: - Summary: Sign already signed jar still does not work Key: MJARSIGNER-33 URL: https://jira.codehaus.org/browse/MJARSIGNER-33 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3 Reporter: Tony Chemit See MSHARED-315. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-33) Sign already signed jar still does not work
[ https://jira.codehaus.org/browse/MJARSIGNER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-33: -- Assignee: Tony Chemit Sign already signed jar still does not work --- Key: MJARSIGNER-33 URL: https://jira.codehaus.org/browse/MJARSIGNER-33 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3 Reporter: Tony Chemit Assignee: Tony Chemit See MSHARED-315. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-33) Sign already signed jar still does not work
[ https://jira.codehaus.org/browse/MJARSIGNER-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-33. - Resolution: Fixed Fix Version/s: 1.3.1 Done in [r1555223|http://svn.apache.org/r1555223] Sign already signed jar still does not work --- Key: MJARSIGNER-33 URL: https://jira.codehaus.org/browse/MJARSIGNER-33 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.3 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: 1.3.1 See MSHARED-315. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-314) Unsign jar still have some signatures in the manisfest
Tony Chemit created MSHARED-314: --- Summary: Unsign jar still have some signatures in the manisfest Key: MSHARED-314 URL: https://jira.codehaus.org/browse/MSHARED-314 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.2 Reporter: Tony Chemit when unsigning a jar, we must remove of the signatures files from the META-INF package + remove any signing attributes (like SHA1-DIGEST ones). The problem occurs in fact when a jar was signed by jdk6, unsign it, then resign it with a jdk7. since the digest algorithm since jdk7 is no more the same, we still have some entry in the manifest which does not match the effective signing... the best way to remove this is just to clean the manisfest file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-314) Unsign jar still have some signatures in the manisfest
[ https://jira.codehaus.org/browse/MSHARED-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-314: Assignee: Tony Chemit Unsign jar still have some signatures in the manisfest -- Key: MSHARED-314 URL: https://jira.codehaus.org/browse/MSHARED-314 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.2 Reporter: Tony Chemit Assignee: Tony Chemit when unsigning a jar, we must remove of the signatures files from the META-INF package + remove any signing attributes (like SHA1-DIGEST ones). The problem occurs in fact when a jar was signed by jdk6, unsign it, then resign it with a jdk7. since the digest algorithm since jdk7 is no more the same, we still have some entry in the manifest which does not match the effective signing... the best way to remove this is just to clean the manisfest file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-21) jars signed using Java 7 have invalid SHA1 signature
[ https://jira.codehaus.org/browse/MJARSIGNER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=337896#comment-337896 ] Tony Chemit commented on MJARSIGNER-21: --- FMU, there is no need to specify the digest algo. Just cleaning the manifest while unsigning a jar befoire resign it should be sufficent. See MSHARE-314 jars signed using Java 7 have invalid SHA1 signature -- Key: MJARSIGNER-21 URL: https://jira.codehaus.org/browse/MJARSIGNER-21 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.2 Environment: Java 7, Maven 2.2.1 Reporter: Mike Calmus Assignee: Tony Chemit Priority: Critical Using the plugin with Java 6 works fine. When I use it with Java 7, my applet won't load because the SHA1 signatures are invalid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-314) Unsign jar still have some signatures in the manisfest
[ https://jira.codehaus.org/browse/MSHARED-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-314. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.3 Unsign jar still have some signatures in the manisfest -- Key: MSHARED-314 URL: https://jira.codehaus.org/browse/MSHARED-314 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.2 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3 when unsigning a jar, we must remove of the signatures files from the META-INF package + remove any signing attributes (like SHA1-DIGEST ones). The problem occurs in fact when a jar was signed by jdk6, unsign it, then resign it with a jdk7. since the digest algorithm since jdk7 is no more the same, we still have some entry in the manifest which does not match the effective signing... the best way to remove this is just to clean the manisfest file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-314) Unsign jar still have some signatures in the manisfest
[ https://jira.codehaus.org/browse/MSHARED-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=337897#comment-337897 ] Tony Chemit commented on MSHARED-314: - done in [r1553841|http://svn.apache.org/r1553841] Unsign jar still have some signatures in the manisfest -- Key: MSHARED-314 URL: https://jira.codehaus.org/browse/MSHARED-314 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.2 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3 when unsigning a jar, we must remove of the signatures files from the META-INF package + remove any signing attributes (like SHA1-DIGEST ones). The problem occurs in fact when a jar was signed by jdk6, unsign it, then resign it with a jdk7. since the digest algorithm since jdk7 is no more the same, we still have some entry in the manifest which does not match the effective signing... the best way to remove this is just to clean the manisfest file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-27) Use maven-jarsigner 1.3
[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-27: -- Description: To fix MJARSIGNER-21 Summary: Use maven-jarsigner 1.3 (was: Use maven-jarsigner 1.2) Use maven-jarsigner 1.3 --- Key: MJARSIGNER-27 URL: https://jira.codehaus.org/browse/MJARSIGNER-27 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit Assignee: Tony Chemit Priority: Trivial Fix For: 1.3 To fix MJARSIGNER-21 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-27) Use maven-jarsigner 1.3
[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reopened MJARSIGNER-27: --- Use maven-jarsigner 1.3 --- Key: MJARSIGNER-27 URL: https://jira.codehaus.org/browse/MJARSIGNER-27 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit Assignee: Tony Chemit Priority: Trivial Fix For: 1.3 To fix MJARSIGNER-21 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-21) jars signed using Java 7 have invalid SHA1 signature
[ https://jira.codehaus.org/browse/MJARSIGNER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=337896#comment-337896 ] Tony Chemit edited comment on MJARSIGNER-21 at 12/28/13 9:00 AM: - FMU, there is no need to specify the digest algo. Just cleaning the manifest while unsigning a jar befoire resign it should be sufficent. See MSHARED-314 was (Author: tchemit): FMU, there is no need to specify the digest algo. Just cleaning the manifest while unsigning a jar befoire resign it should be sufficent. See MSHARE-314 jars signed using Java 7 have invalid SHA1 signature -- Key: MJARSIGNER-21 URL: https://jira.codehaus.org/browse/MJARSIGNER-21 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.2 Environment: Java 7, Maven 2.2.1 Reporter: Mike Calmus Assignee: Tony Chemit Priority: Critical Using the plugin with Java 6 works fine. When I use it with Java 7, my applet won't load because the SHA1 signatures are invalid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-314) Unsign jar still have some signatures in the manisfest
[
https://jira.codehaus.org/browse/MSHARED-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=337898#comment-337898
]
Tony Chemit commented on MSHARED-314:
-
You can test with this artifact for example:
{noformat}
dependency
groupIdorg.swinglabs/groupId
artifactIdjxlayer/artifactId
version3.0.4/version
/dependency
{noformat}
Unsign jar still have some signatures in the manisfest
--
Key: MSHARED-314
URL: https://jira.codehaus.org/browse/MSHARED-314
Project: Maven Shared Components
Issue Type: Bug
Components: maven-jarsigner
Affects Versions: maven-jarsigner-1.2
Reporter: Tony Chemit
Assignee: Tony Chemit
Fix For: maven-jarsigner-1.3
when unsigning a jar, we must remove of the signatures files from the
META-INF package + remove any signing attributes (like SHA1-DIGEST ones).
The problem occurs in fact when a jar was signed by jdk6, unsign it, then
resign it with a jdk7.
since the digest algorithm since jdk7 is no more the same, we still have some
entry in the manifest which does not match the effective signing...
the best way to remove this is just to clean the manisfest file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-21) jars signed using Java 7 have invalid SHA1 signature
[ https://jira.codehaus.org/browse/MJARSIGNER-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-21. - Resolution: Fixed Fix Version/s: 1.3 Close since MSHARED-314 fix the problem. jars signed using Java 7 have invalid SHA1 signature -- Key: MJARSIGNER-21 URL: https://jira.codehaus.org/browse/MJARSIGNER-21 Project: Maven Jar Signer Plugin Issue Type: Bug Affects Versions: 1.2 Environment: Java 7, Maven 2.2.1 Reporter: Mike Calmus Assignee: Tony Chemit Priority: Critical Fix For: 1.3 Using the plugin with Java 6 works fine. When I use it with Java 7, my applet won't load because the SHA1 signatures are invalid. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-24) Use Password Encryption in pom.xml
[ https://jira.codehaus.org/browse/MJARSIGNER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reassigned MJARSIGNER-24: - Assignee: Olivier Lamy Use Password Encryption in pom.xml -- Key: MJARSIGNER-24 URL: https://jira.codehaus.org/browse/MJARSIGNER-24 Project: Maven Jar Signer Plugin Issue Type: New Feature Reporter: Zang MingJie Assignee: Olivier Lamy Attachments: jarsigner.patch, patch, securejarsigner.patch See http://maven.apache.org/guides/mini/guide-encryption.html Here is a patch for it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-24) Use Password Encryption in pom.xml
[ https://jira.codehaus.org/browse/MJARSIGNER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-24: -- Assignee: Tony Chemit (was: Olivier Lamy) Use Password Encryption in pom.xml -- Key: MJARSIGNER-24 URL: https://jira.codehaus.org/browse/MJARSIGNER-24 Project: Maven Jar Signer Plugin Issue Type: New Feature Reporter: Zang MingJie Assignee: Tony Chemit Attachments: jarsigner.patch, patch, securejarsigner.patch See http://maven.apache.org/guides/mini/guide-encryption.html Here is a patch for it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-32) Update requirements to maven 2.1.0
Tony Chemit created MJARSIGNER-32: - Summary: Update requirements to maven 2.1.0 Key: MJARSIGNER-32 URL: https://jira.codehaus.org/browse/MJARSIGNER-32 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit This is required to be able to use toolchain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-32) Update requirements to maven 2.1.0
[ https://jira.codehaus.org/browse/MJARSIGNER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-32: -- Assignee: Tony Chemit Update requirements to maven 2.1.0 -- Key: MJARSIGNER-32 URL: https://jira.codehaus.org/browse/MJARSIGNER-32 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit Assignee: Tony Chemit This is required to be able to use toolchain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-32) Update requirements to maven 2.1.0
[ https://jira.codehaus.org/browse/MJARSIGNER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-32. - Resolution: Fixed Fix Version/s: 1.3 Update requirements to maven 2.1.0 -- Key: MJARSIGNER-32 URL: https://jira.codehaus.org/browse/MJARSIGNER-32 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: 1.3 This is required to be able to use toolchain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-32) Update requirements to maven 2.1.0
[ https://jira.codehaus.org/browse/MJARSIGNER-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=337902#comment-337902 ] Tony Chemit commented on MJARSIGNER-32: --- Done in [r1553860|http://svn.apache.org/r1553860] Update requirements to maven 2.1.0 -- Key: MJARSIGNER-32 URL: https://jira.codehaus.org/browse/MJARSIGNER-32 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: 1.3 This is required to be able to use toolchain. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-24) Use Password Encryption in pom.xml
[ https://jira.codehaus.org/browse/MJARSIGNER-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-24. - Resolution: Fixed Fix Version/s: 1.3 Use Password Encryption in pom.xml -- Key: MJARSIGNER-24 URL: https://jira.codehaus.org/browse/MJARSIGNER-24 Project: Maven Jar Signer Plugin Issue Type: New Feature Reporter: Zang MingJie Assignee: Tony Chemit Fix For: 1.3 Attachments: jarsigner.patch, patch, securejarsigner.patch See http://maven.apache.org/guides/mini/guide-encryption.html Here is a patch for it -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-13) signing in multi-module project fails on windows
[
https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit updated MJARSIGNER-13:
--
Assignee: Tony Chemit
signing in multi-module project fails on windows
Key: MJARSIGNER-13
URL: https://jira.codehaus.org/browse/MJARSIGNER-13
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.2
Environment: Windows XP, android sdk
Reporter: Anna Gadomska
Assignee: Tony Chemit
Attachments: pom.xml
I got multi-module (6 modules) android project with .pom file and sign
profile defined. When I execute with 'sign' profile:
- in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution
(mv goal -rf) it signs another 3 modules and fails again. The reason for
failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig
failed.
- in Maven 2.2.1 - it doesn't work at all, even for first module; it returns
error code 1
However, I tried the same .pom - everything works perfectly in Linux
(Ubuntu).
I was afraid that it might be the issue with spaces, so I hardcoded the paths
- the error I got from maven than was:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project
MyProject: Failed executing 'cmd.exe /X /C
C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore
C:\tmp\debug.keystore -storepass '*' -keypass '*' xxx.jar
'*'debugkey' - exitcode 1 - [Help 1]
{noformat}
Attaching pom file which I am using.
Please help?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-13) signing in multi-module project fails on windows
[
https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tony Chemit closed MJARSIGNER-13.
-
Resolution: Fixed
Fix Version/s: 1.3
signing in multi-module project fails on windows
Key: MJARSIGNER-13
URL: https://jira.codehaus.org/browse/MJARSIGNER-13
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.2
Environment: Windows XP, android sdk
Reporter: Anna Gadomska
Assignee: Tony Chemit
Fix For: 1.3
Attachments: pom.xml
I got multi-module (6 modules) android project with .pom file and sign
profile defined. When I execute with 'sign' profile:
- in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution
(mv goal -rf) it signs another 3 modules and fails again. The reason for
failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig
failed.
- in Maven 2.2.1 - it doesn't work at all, even for first module; it returns
error code 1
However, I tried the same .pom - everything works perfectly in Linux
(Ubuntu).
I was afraid that it might be the issue with spaces, so I hardcoded the paths
- the error I got from maven than was:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project
MyProject: Failed executing 'cmd.exe /X /C
C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore
C:\tmp\debug.keystore -storepass '*' -keypass '*' xxx.jar
'*'debugkey' - exitcode 1 - [Help 1]
{noformat}
Attaching pom file which I am using.
Please help?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-13) signing in multi-module project fails on windows
[
https://jira.codehaus.org/browse/MJARSIGNER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=337905#comment-337905
]
Tony Chemit commented on MJARSIGNER-13:
---
Entry added in FAQ at [rev1553915|http://svn.apache.org/rev1553915]
signing in multi-module project fails on windows
Key: MJARSIGNER-13
URL: https://jira.codehaus.org/browse/MJARSIGNER-13
Project: Maven Jar Signer Plugin
Issue Type: Bug
Affects Versions: 1.2
Environment: Windows XP, android sdk
Reporter: Anna Gadomska
Assignee: Tony Chemit
Fix For: 1.3
Attachments: pom.xml
I got multi-module (6 modules) android project with .pom file and sign
profile defined. When I execute with 'sign' profile:
- in Maven 3.0.1 - it signs 3 modules and fails. when I resume the execution
(mv goal -rf) it signs another 3 modules and fails again. The reason for
failing is: [INFO] jarsigner: attempt to rename xxx.jar to xxx.jar.orig
failed.
- in Maven 2.2.1 - it doesn't work at all, even for first module; it returns
error code 1
However, I tried the same .pom - everything works perfectly in Linux
(Ubuntu).
I was afraid that it might be the issue with spaces, so I hardcoded the paths
- the error I got from maven than was:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jarsigner-plugin:1.2:sign (signing) on project
MyProject: Failed executing 'cmd.exe /X /C
C:\tools\JavaTMSEDevelopementKit\jre\..\bin\jarsigner.exe -verbose -keystore
C:\tmp\debug.keystore -storepass '*' -keypass '*' xxx.jar
'*'debugkey' - exitcode 1 - [Help 1]
{noformat}
Attaching pom file which I am using.
Please help?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-314) Unsigning a jar is not correct
[ https://jira.codehaus.org/browse/MSHARED-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-314: Summary: Unsigning a jar is not correct (was: Unsign jar still have some signatures in the manisfest) Unsigning a jar is not correct -- Key: MSHARED-314 URL: https://jira.codehaus.org/browse/MSHARED-314 Project: Maven Shared Components Issue Type: Bug Components: maven-jarsigner Affects Versions: maven-jarsigner-1.2 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.3 when unsigning a jar, we must remove of the signatures files from the META-INF package + remove any signing attributes (like SHA1-DIGEST ones). The problem occurs in fact when a jar was signed by jdk6, unsign it, then resign it with a jdk7. since the digest algorithm since jdk7 is no more the same, we still have some entry in the manifest which does not match the effective signing... the best way to remove this is just to clean the manisfest file. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-27) Use maven-jarsigner 1.3
[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-27. - Resolution: Fixed Use maven-jarsigner 1.3 --- Key: MJARSIGNER-27 URL: https://jira.codehaus.org/browse/MJARSIGNER-27 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit Assignee: Tony Chemit Priority: Trivial Fix For: 1.3 To fix MJARSIGNER-21 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-27) Use maven-jarsigner 1.3
[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=337906#comment-337906 ] Tony Chemit commented on MJARSIGNER-27: --- Done in [r1553922|http://svn.apache.org/r1553922] Use maven-jarsigner 1.3 --- Key: MJARSIGNER-27 URL: https://jira.codehaus.org/browse/MJARSIGNER-27 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit Assignee: Tony Chemit Priority: Trivial Fix For: 1.3 To fix MJARSIGNER-21 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MASSEMBLY-658) Assembly fails for multi-module project if webstart-maven-plugin is in use
[ https://jira.codehaus.org/browse/MASSEMBLY-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MASSEMBLY-658. - Resolution: Won't Fix Fix Version/s: 2.5 Assignee: Tony Chemit You are just using the *jnlp-inline* mojo which is an aggregator mojo, so does not match with your needs. Just use instead the *jnlp-single* mojo instead to make your example works. Assembly fails for multi-module project if webstart-maven-plugin is in use -- Key: MASSEMBLY-658 URL: https://jira.codehaus.org/browse/MASSEMBLY-658 Project: Maven Assembly Plugin Issue Type: Bug Components: dependencySet Affects Versions: 2.4 Environment: Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 13:51: 28+) Maven home: C:\dev\apache-maven-3.0.5\bin\.. Java version: 1.6.0_45, vendor: Sun Microsystems Inc. Java home: C:\Program Files\Java\jdk1.6.0_45\jre Default locale: en_GB, platform encoding: Cp1252 OS name: windows 7, version: 6.1, arch: amd64, family: windows Reporter: Robin Roos Assignee: Tony Chemit Fix For: 2.5 Attachments: npe-war-assebmbly.zip, output.log The mvn invocation I used is: mvn clean package I attach a simple test case of a multi-module project. If the acme-jnlp module is commented out in the parent POM then the project builds successfully. If the acme-jnlp module is not commented out, then the assembly of acme-dist fails because of a NullPointerException. acme-dist and acme-war to not rely on the artifacts generated by acme-jnlp. The mere fact that the plugin is executed causes the later module assembly to fail. Modules have the following purposes: acme-parent: parent project which contains the module acme-jnlp: create JNLP and ZIP files not used by any other modules acme-war: create a .WAR file acme-dist: use assembly plugin to create a .ZIP containing the .WAR acme-deploy: holds dependencies to other modules, but does nothing else -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-31) Update maven-shared-utils to 0.5
Tony Chemit created MJARSIGNER-31: - Summary: Update maven-shared-utils to 0.5 Key: MJARSIGNER-31 URL: https://jira.codehaus.org/browse/MJARSIGNER-31 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit Priority: Trivial -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-27) Use maven-jarsigner 1.2
[ https://jira.codehaus.org/browse/MJARSIGNER-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-27. - Resolution: Fixed Use maven-jarsigner 1.2 --- Key: MJARSIGNER-27 URL: https://jira.codehaus.org/browse/MJARSIGNER-27 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit Assignee: Tony Chemit Priority: Trivial Fix For: 1.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-31) Update maven-shared-utils to 0.5
[ https://jira.codehaus.org/browse/MJARSIGNER-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MJARSIGNER-31: -- Assignee: Tony Chemit Update maven-shared-utils to 0.5 Key: MJARSIGNER-31 URL: https://jira.codehaus.org/browse/MJARSIGNER-31 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit Assignee: Tony Chemit Priority: Trivial -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MJARSIGNER-31) Update maven-shared-utils to 0.5
[ https://jira.codehaus.org/browse/MJARSIGNER-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MJARSIGNER-31. - Resolution: Fixed Fix Version/s: 1.3 Update maven-shared-utils to 0.5 Key: MJARSIGNER-31 URL: https://jira.codehaus.org/browse/MJARSIGNER-31 Project: Maven Jar Signer Plugin Issue Type: Task Affects Versions: 1.2 Reporter: Tony Chemit Assignee: Tony Chemit Priority: Trivial Fix For: 1.3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-304) Create a API for java tool
[ https://jira.codehaus.org/browse/MSHARED-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reopened MSHARED-304: - Create a API for java tool -- Key: MSHARED-304 URL: https://jira.codehaus.org/browse/MSHARED-304 Project: Maven Shared Components Issue Type: New Feature Affects Versions: maven-shared-utils-0.4 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-shared-utils-0.5 While using the commandline API to invoke java tool (*jarsigner*, *keytool*, *javadoc*), we always write the same boilerplate code: - find the java tool executable location - build a new command line - invoke it and deal with invocation errors - ... Let's have a simple API for this! As a first improvement then let's add to it also the support for toolchain (asked in maven-jarsigner-plugin). I will put the code in package *org.apache.maven.shared.utils.cli.javatool*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-305) Use maven-shared-utils javatool API
[ https://jira.codehaus.org/browse/MSHARED-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reopened MSHARED-305: - Use maven-shared-utils javatool API --- Key: MSHARED-305 URL: https://jira.codehaus.org/browse/MSHARED-305 Project: Maven Shared Components Issue Type: Task Affects Versions: maven-jarsigner-1.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-305) Use maven-shared-utils javatool API
[ https://jira.codehaus.org/browse/MSHARED-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-305. --- Resolution: Fixed Use maven-shared-utils javatool API --- Key: MSHARED-305 URL: https://jira.codehaus.org/browse/MSHARED-305 Project: Maven Shared Components Issue Type: Task Affects Versions: maven-jarsigner-1.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-304) Create a API for java tool
[ https://jira.codehaus.org/browse/MSHARED-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-304. --- Resolution: Fixed Create a API for java tool -- Key: MSHARED-304 URL: https://jira.codehaus.org/browse/MSHARED-304 Project: Maven Shared Components Issue Type: New Feature Affects Versions: maven-shared-utils-0.4 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-shared-utils-0.5 While using the commandline API to invoke java tool (*jarsigner*, *keytool*, *javadoc*), we always write the same boilerplate code: - find the java tool executable location - build a new command line - invoke it and deal with invocation errors - ... Let's have a simple API for this! As a first improvement then let's add to it also the support for toolchain (asked in maven-jarsigner-plugin). I will put the code in package *org.apache.maven.shared.utils.cli.javatool*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-301) use plexus java 5 annotations instead of plexus javadoc tags
[ https://jira.codehaus.org/browse/MSHARED-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-301: Issue Type: Task (was: Bug) use plexus java 5 annotations instead of plexus javadoc tags Key: MSHARED-301 URL: https://jira.codehaus.org/browse/MSHARED-301 Project: Maven Shared Components Issue Type: Task Components: maven-jarsigner Affects Versions: maven-jarsigner-1.1 Reporter: Herve Boutemy Assignee: Tony Chemit Priority: Minor Fix For: maven-jarsigner-1.2 Java 5 annotations ease maintenance see http://plexus.codehaus.org/plexus-containers/plexus-component-annotations/ -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-304) Create a API for java tool
Tony Chemit created MSHARED-304: --- Summary: Create a API for java tool Key: MSHARED-304 URL: https://jira.codehaus.org/browse/MSHARED-304 Project: Maven Shared Components Issue Type: New Feature Affects Versions: maven-shared-utils-0.4 Reporter: Tony Chemit While using the commandline API to invoke java tool (*jarsigner*, *keytool*, *javadoc*), we always write the same boilerplate code: - find the java tool executable location - build a new command line - invoke it and deal with invocation errors - ... Let's have a simple API for this! As a first improvement then let's add to it also the support for toolchain (asked in maven-jarsigner-plugin). I will put the code in package *org.apache.maven.shared.utils.cli.javatool*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-304) Create a API for java tool
[ https://jira.codehaus.org/browse/MSHARED-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-304: Assignee: Tony Chemit Create a API for java tool -- Key: MSHARED-304 URL: https://jira.codehaus.org/browse/MSHARED-304 Project: Maven Shared Components Issue Type: New Feature Affects Versions: maven-shared-utils-0.4 Reporter: Tony Chemit Assignee: Tony Chemit While using the commandline API to invoke java tool (*jarsigner*, *keytool*, *javadoc*), we always write the same boilerplate code: - find the java tool executable location - build a new command line - invoke it and deal with invocation errors - ... Let's have a simple API for this! As a first improvement then let's add to it also the support for toolchain (asked in maven-jarsigner-plugin). I will put the code in package *org.apache.maven.shared.utils.cli.javatool*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-304) Create a API for java tool
[ https://jira.codehaus.org/browse/MSHARED-304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-304. --- Resolution: Fixed Fix Version/s: maven-shared-utils-0.5 Create a API for java tool -- Key: MSHARED-304 URL: https://jira.codehaus.org/browse/MSHARED-304 Project: Maven Shared Components Issue Type: New Feature Affects Versions: maven-shared-utils-0.4 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-shared-utils-0.5 While using the commandline API to invoke java tool (*jarsigner*, *keytool*, *javadoc*), we always write the same boilerplate code: - find the java tool executable location - build a new command line - invoke it and deal with invocation errors - ... Let's have a simple API for this! As a first improvement then let's add to it also the support for toolchain (asked in maven-jarsigner-plugin). I will put the code in package *org.apache.maven.shared.utils.cli.javatool*. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-305) Use maven-shared-utils javatool API
Tony Chemit created MSHARED-305: --- Summary: Use maven-shared-utils javatool API Key: MSHARED-305 URL: https://jira.codehaus.org/browse/MSHARED-305 Project: Maven Shared Components Issue Type: Task Affects Versions: maven-jarsigner-1.1 Reporter: Tony Chemit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-305) Use maven-shared-utils javatool API
[ https://jira.codehaus.org/browse/MSHARED-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit updated MSHARED-305: Assignee: Tony Chemit Use maven-shared-utils javatool API --- Key: MSHARED-305 URL: https://jira.codehaus.org/browse/MSHARED-305 Project: Maven Shared Components Issue Type: Task Affects Versions: maven-jarsigner-1.1 Reporter: Tony Chemit Assignee: Tony Chemit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-306) keystore and alias parameters can be used for both sign and verify jarsigner tool
Tony Chemit created MSHARED-306: --- Summary: keystore and alias parameters can be used for both sign and verify jarsigner tool Key: MSHARED-306 URL: https://jira.codehaus.org/browse/MSHARED-306 Project: Maven Shared Components Issue Type: Improvement Affects Versions: maven-jarsigner-1.1 Reporter: Tony Chemit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-306) keystore and alias parameters can be used for both sign and verify jarsigner tool
[ https://jira.codehaus.org/browse/MSHARED-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit reassigned MSHARED-306: --- Assignee: Tony Chemit keystore and alias parameters can be used for both sign and verify jarsigner tool - Key: MSHARED-306 URL: https://jira.codehaus.org/browse/MSHARED-306 Project: Maven Shared Components Issue Type: Improvement Affects Versions: maven-jarsigner-1.1 Reporter: Tony Chemit Assignee: Tony Chemit -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-305) Use maven-shared-utils javatool API
[ https://jira.codehaus.org/browse/MSHARED-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=335666#comment-335666 ] Tony Chemit commented on MSHARED-305: - To use maven-toolchain, we need now mavenVersion up to 2.1.0 (was 2.0.6). Use maven-shared-utils javatool API --- Key: MSHARED-305 URL: https://jira.codehaus.org/browse/MSHARED-305 Project: Maven Shared Components Issue Type: Task Affects Versions: maven-jarsigner-1.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MSHARED-305) Use maven-shared-utils javatool API
[ https://jira.codehaus.org/browse/MSHARED-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tony Chemit closed MSHARED-305. --- Resolution: Fixed Fix Version/s: maven-jarsigner-1.2 Use maven-shared-utils javatool API --- Key: MSHARED-305 URL: https://jira.codehaus.org/browse/MSHARED-305 Project: Maven Shared Components Issue Type: Task Affects Versions: maven-jarsigner-1.1 Reporter: Tony Chemit Assignee: Tony Chemit Fix For: maven-jarsigner-1.2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
