You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org> on 2005/08/27 04:11:06 UTC
[jira] Updated: (GERONIMO-470) Online deployer locks module file
[ http://issues.apache.org/jira/browse/GERONIMO-470?page=all ]
Aaron Mulder updated GERONIMO-470:
----------------------------------
Fix Version: 1.0
Environment:
If that's all that's being done, could replace this with opening a JarFile on the JAR, getting the stream from that, and then closing the JarFile after the reading is done.
> Online deployer locks module file
> ---------------------------------
>
> Key: GERONIMO-470
> URL: http://issues.apache.org/jira/browse/GERONIMO-470
> Project: Geronimo
> Type: Bug
> Components: deployment
> Reporter: Jeremy Boynes
> Fix For: 1.0
>
> If I distribute a war file using the maven plugin and the online deployer, the server locks the input file. The means that a second build of my app fails as maven cannot delete the old war.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira