Webstart Maven Plugin using jarsigner with proxy

[Sverre Moe]

How can I provide Java properties to Maven webstart plugin to be used
when calling Jarsigner?

<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>webstart-maven-plugin</artifactId>
<configuration>
<sign>
<keystore>${keystore}</keystore>
<storepass>${storepass}</storepass>
<storetype>${storetype}</storetype>
<alias>${sign.alias}</alias>
<tsaLocation>${tsa}</tsaLocation>
</sign>
</configuration>
</plugin>

While using the maven-jarsigner-plugin I am able to supply properties
for my Proxy.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jarsigner-plugin</artifactId>
<configuration>
<arguments>
<argument>-J-Dhttps.proxyHost=proxy.company.com</argument>
<argument>-J-Dhttps.proxyPort=3128</argument>
<argument>-tsa</argument>
<argument>${tsa}</argument>
</arguments>
</configuration>
</plugin>

I cannot find any similar settings for the maven webstart plugin.

Would not need to do this in my pom.xml if Jarsigner could use the
default Java proxy settings I have configured in Java Control Panel
Network Settings.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@maven.apache.org
For additional commands, e-mail: users-***@maven.apache.org

[Martin Gainty]

Date: Tue, 6 Oct 2015 13:33:40 +0200
Subject: Webstart Maven Plugin using jarsigner with proxy
How can I provide Java properties to Maven webstart plugin to be used
when calling Jarsigner?
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>webstart-maven-plugin</artifactId>
<configuration>
<sign>
<keystore>${keystore}</keystore>
<storepass>${storepass}</storepass>
<storetype>${storetype}</storetype>
<alias>${sign.alias}</alias>
<tsaLocation>${tsa}</tsaLocation>
</sign>
</configuration>
</plugin>

MG>2 step process supply authentication credentials via configuration
http://www.mojohaus.org/keytool/keytool-maven-plugin/
<configuration>
<changeKeyPassword>newKeyPassword</changeKeyPassword>
<changeStorePassword>newStorePassword</changeStorePassword>
</configuration>
NB:Some codehaus artifacts are still being transferred here so you should download everything you need (including source) asap
MG>

MG>once keytool-maven-plugin packages your keystore file to a known location.. then call maven-jarsigner-plugin
https://maven.apache.org/plugins/maven-jarsigner-plugin/sign-mojo.html
<configuration>
<keystore> (supply keystore from known location)</keystore>
<tsa> (support location of timestamp authority)</tsa>
<arguments>
<argument>-J-Dhttps.proxyHost=proxy.company.com</argument>
<argument>-J-Dhttps.proxyPort=3128</argument>
</arguments>
</configuration>
MG>

While using the maven-jarsigner-plugin I am able to supply properties
for my Proxy.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jarsigner-plugin</artifactId>
<configuration>
<arguments>
<argument>-J-Dhttps.proxyHost=proxy.company.com</argument>
<argument>-J-Dhttps.proxyPort=3128</argument>
<argument>-tsa</argument>
<argument>${tsa}</argument>
</arguments>
</configuration>
</plugin>
I cannot find any similar settings for the maven webstart plugin.
Would not need to do this in my pom.xml if Jarsigner could use the
default Java proxy settings I have configured in Java Control Panel
Network Settings.
---------------------------------------------------------------------

[Martin Gainty]

Date: Tue, 6 Oct 2015 13:33:40 +0200
Subject: Webstart Maven Plugin using jarsigner with proxy
How can I provide Java properties to Maven webstart plugin to be used
when calling Jarsigner?
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>webstart-maven-plugin</artifactId>
<configuration>
<sign>
<keystore>${keystore}</keystore>
<storepass>${storepass}</storepass>
<storetype>${storetype}</storetype>
<alias>${sign.alias}</alias>
<tsaLocation>${tsa}</tsaLocation>
</sign>
</configuration>
</plugin>

MG>2 step process supply authentication credentials via configuration
http://www.mojohaus.org/keytool/keytool-maven-plugin/
<configuration>
<changeKeyPassword>newKeyPassword</changeKeyPassword>
<changeStorePassword>newStorePassword</changeStorePassword>
</configuration>
NB:Some codehaus artifacts are still being transferred here so you should download everything you need (including source) asap
MG>

MG>once keytool-maven-plugin packages your keystore file to a known location.. then call maven-jarsigner-plugin
https://maven.apache.org/plugins/maven-jarsigner-plugin/sign-mojo.html
<configuration>
<keystore> (supply keystore from known location)</keystore>
<tsa> (support location of timestamp authority)</tsa>
<arguments>
<argument>-J-Dhttps.proxyHost=proxy.company.com</argument>
<argument>-J-Dhttps.proxyPort=3128</argument>
</arguments>
</configuration>
MG>

While using the maven-jarsigner-plugin I am able to supply properties
for my Proxy.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jarsigner-plugin</artifactId>
<configuration>
<arguments>
<argument>-J-Dhttps.proxyHost=proxy.company.com</argument>
<argument>-J-Dhttps.proxyPort=3128</argument>
<argument>-tsa</argument>
<argument>${tsa}</argument>
</arguments>
</configuration>
</plugin>
I cannot find any similar settings for the maven webstart plugin.
Would not need to do this in my pom.xml if Jarsigner could use the
default Java proxy settings I have configured in Java Control Panel
Network Settings.
---------------------------------------------------------------------

[Sverre Moe]

I am already using both maven-keytool-plugin and
maven-jarsigner-plugin. Providing jarsigner proxy with
maven-jarsigner-plugin is not what I have problem with. I am also
using webstart-maven-plugin where I cannot find a way to set the proxy
to use. From what I can see there looks to be no way of configuring
extra jarsigner arguments using webstart-maven-plugin.

As a hack I have renamed /usr/java/latest/bin/jarsigner, created a new
script called jarsigner that calls the renamed jarsigner with the
proxy arguments. Not pretty, but it works as temporary patch.

This would be much easier if the tool jarsigner could use the
configured Java proxy settings.

Post by Martin Gainty

Date: Tue, 6 Oct 2015 13:33:40 +0200
Subject: Webstart Maven Plugin using jarsigner with proxy
How can I provide Java properties to Maven webstart plugin to be used
when calling Jarsigner?
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>webstart-maven-plugin</artifactId>
<configuration>
<sign>
<keystore>${keystore}</keystore>
<storepass>${storepass}</storepass>
<storetype>${storetype}</storetype>
<alias>${sign.alias}</alias>
<tsaLocation>${tsa}</tsaLocation>
</sign>
</configuration>
</plugin>

MG>2 step process supply authentication credentials via configuration
http://www.mojohaus.org/keytool/keytool-maven-plugin/
<configuration>
<changeKeyPassword>newKeyPassword</changeKeyPassword>
<changeStorePassword>newStorePassword</changeStorePassword>
</configuration>
NB:Some codehaus artifacts are still being transferred here so you should download everything you need (including source) asap
MG>
MG>once keytool-maven-plugin packages your keystore file to a known location.. then call maven-jarsigner-plugin
https://maven.apache.org/plugins/maven-jarsigner-plugin/sign-mojo.html
<configuration>
<keystore> (supply keystore from known location)</keystore>
<tsa> (support location of timestamp authority)</tsa>
<arguments>
<argument>-J-Dhttps.proxyHost=proxy.company.com</argument>
<argument>-J-Dhttps.proxyPort=3128</argument>
</arguments>
</configuration>
MG>

While using the maven-jarsigner-plugin I am able to supply properties
for my Proxy.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jarsigner-plugin</artifactId>
<configuration>
<arguments>
<argument>-J-Dhttps.proxyHost=proxy.company.com</argument>
<argument>-J-Dhttps.proxyPort=3128</argument>
<argument>-tsa</argument>
<argument>${tsa}</argument>
</arguments>
</configuration>
</plugin>
I cannot find any similar settings for the maven webstart plugin.
Would not need to do this in my pom.xml if Jarsigner could use the
default Java proxy settings I have configured in Java Control Panel
Network Settings.
---------------------------------------------------------------------

---------------------------------------------------------------------
To unsubscribe, e-mail: users-***@maven.apache.org
For additional commands, e-mail: users-***@maven.apache.org

[Martin Gainty]

-submit maven-jarsigner-plugin accomodation for proxy params in configuration request to ***@maven.apache.org

-submit your testcase and patch for accomodating 'proxy arguments within configuration' for maven-jarsigner-plugin to
https://issues.apache.org/jira/browse/MJARSIGNER/?selectedTab=com.atlassian.jira.jira-projects-plugin:summary-panel

Michael Osipov is the lead..if for any reason he is busy Im sure someone will implement this by month end
Nota Bene:maven-jarsigner-plugin proxy configuration changes will probably be voted on when RC is cut

Thanks Moe
Martin

Date: Tue, 6 Oct 2015 20:40:29 +0200
Subject: Re: Webstart Maven Plugin using jarsigner with proxy
I am already using both maven-keytool-plugin and
maven-jarsigner-plugin. Providing jarsigner proxy with
maven-jarsigner-plugin is not what I have problem with. I am also
using webstart-maven-plugin where I cannot find a way to set the proxy
to use. From what I can see there looks to be no way of configuring
extra jarsigner arguments using webstart-maven-plugin.
As a hack I have renamed /usr/java/latest/bin/jarsigner, created a new
script called jarsigner that calls the renamed jarsigner with the
proxy arguments. Not pretty, but it works as temporary patch.
This would be much easier if the tool jarsigner could use the
configured Java proxy settings.

Post by Martin Gainty

Date: Tue, 6 Oct 2015 13:33:40 +0200
Subject: Webstart Maven Plugin using jarsigner with proxy
How can I provide Java properties to Maven webstart plugin to be used
when calling Jarsigner?
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>webstart-maven-plugin</artifactId>
<configuration>
<sign>
<keystore>${keystore}</keystore>
<storepass>${storepass}</storepass>
<storetype>${storetype}</storetype>
<alias>${sign.alias}</alias>
<tsaLocation>${tsa}</tsaLocation>
</sign>
</configuration>
</plugin>

MG>2 step process supply authentication credentials via configuration
http://www.mojohaus.org/keytool/keytool-maven-plugin/
<configuration>
<changeKeyPassword>newKeyPassword</changeKeyPassword>
<changeStorePassword>newStorePassword</changeStorePassword>
</configuration>
NB:Some codehaus artifacts are still being transferred here so you should download everything you need (including source) asap
MG>
MG>once keytool-maven-plugin packages your keystore file to a known location.. then call maven-jarsigner-plugin
https://maven.apache.org/plugins/maven-jarsigner-plugin/sign-mojo.html
<configuration>
<keystore> (supply keystore from known location)</keystore>
<tsa> (support location of timestamp authority)</tsa>
<arguments>
<argument>-J-Dhttps.proxyHost=proxy.company.com</argument>
<argument>-J-Dhttps.proxyPort=3128</argument>
</arguments>
</configuration>
MG>

While using the maven-jarsigner-plugin I am able to supply properties
for my Proxy.
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jarsigner-plugin</artifactId>
<configuration>
<arguments>
<argument>-J-Dhttps.proxyHost=proxy.company.com</argument>
<argument>-J-Dhttps.proxyPort=3128</argument>
<argument>-tsa</argument>
<argument>${tsa}</argument>
</arguments>
</configuration>
</plugin>
I cannot find any similar settings for the maven webstart plugin.
Would not need to do this in my pom.xml if Jarsigner could use the
default Java proxy settings I have configured in Java Control Panel
Network Settings.
---------------------------------------------------------------------

---------------------------------------------------------------------