[
https://issues.jboss.org/browse/JBIDE-9711?page=com.atlassian.jira.plugin...
]
Libor Zoubek updated JBIDE-9711:
--------------------------------
Fix Version/s: 3.3.0.M4
(was: 3.3.0.M3)
Steps to Reproduce:
In order to reproduce, I believe (haven't tried) you can :
- create an AS7 server
- delete the temp deployment folder
- try to deploy a OSGI bundle (see
https://docs.jboss.org/author/display/AS7/Helloworld+OSGi+quickstart)
was:
In order to reproduce, I believe (haven't tried) you can :
- create an AS7 server
- delete the temp deployment folder
- try to deploy a webapp + its utility project jarred in WEB-INF/lib
Affects Version/s: 3.3.0.M3
(was: 3.3.0.M2)
Environment: JBossTools 3.3.0.M3-H18 (was: JBossAS Tools
2.3.0.v20110617-0009-H467-M2)
AS7 Adapter : Deployment of OSGI projects fails if the temporary
folder doesn't exist
-------------------------------------------------------------------------------------
Key: JBIDE-9711
URL:
https://issues.jboss.org/browse/JBIDE-9711
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Environment: JBossTools 3.3.0.M3-H18
Reporter: Libor Zoubek
Assignee: Rob Stryker
Fix For: 3.3.0.M4
I noticed that, in the context of JBIDE-9133, for the existing -broken- AS7 server
instances the utility projects were not zipped to the deployment area.
On the other hand, creating a new server instance fixed the issue.
So it seems the temporary folder is only created at the same time as the server instance.
It's an issue in the sense that you can not guarantee the temporary folder will exist
at deployment time (could have been deleted by the user ...).
Solution is to call tempdir.mkdirs() right before the actual deployment occurs.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira