[
http://jira.codehaus.org/browse/MWEBSTART-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99250
]
JAmes Atwill commented on MWEBSTART-28:
---------------------------------------
We've experienced the same issue on Linux with our Bamboo server having its
build-dir on NFS. Our nfs options are:
rw,v3,rsize=32768,wsize=32768,hard,tcp,nolock,proto=tcp,timeo=600,retrans=2
Symlinking to a local disk seems to fix the issue.
> result of setLastModified not checked after signing jars
> --------------------------------------------------------
>
> Key: MWEBSTART-28
> URL: http://jira.codehaus.org/browse/MWEBSTART-28
> Project: Maven 2.x Webstart Plugin
> Issue Type: Bug
> Environment: Solaris 10
> Reporter: Ken Geis
> Fix For: 1.0-alpha-2
>
>
> I get the following:
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failure to run the plugin:
> Embedded error: the number of signed artifacts differ from the number of
> modified artifacts. Implementation error
> ---------------------
> My jars do not get signed, and it's apparently because the timestamp on them
> has not been set. The method signJars(..) calls
> jarFiles[i].setLastModified( lastModified );
> but it does not check the result of that call. I'm guessing that on Solaris
> 10, I am prevented from setting the modified date on a file.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list please visit:
http://xircles.codehaus.org/manage_email
