[
https://jira.jboss.org/jira/browse/JBAS-6590?page=com.atlassian.jira.plug...
]
Max Rydahl Andersen commented on JBAS-6590:
-------------------------------------------
I haven't confirmed this myself yet, but if this is true that is a major regression
compared to what we rely on in tooling too...interested to hear what causes it ?
JBoss AS 5 copies exploded ear to tmp directory
-----------------------------------------------
Key: JBAS-6590
URL:
https://jira.jboss.org/jira/browse/JBAS-6590
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Deployers
Affects Versions: JBossAS-5.0.1.GA
Environment: JBoss AS 5.0.1.GA
JDK 1.5
Mac OS X 10.5.6
Reporter: Kenneth Christensen
Assignee: Ales Justin
Priority: Critical
Attachments: ear.jpg, tmp-ear.jpg
I have an explode ear file (directory) - see attached file: ear.jpg
When I deploy the exploded ear file to JBoss AS 4.2.3 and later want to update a xhtml
file in the exploded ear by my ANT script everything works fine (i.e. I can refresh my
browser and see the changes without redeployment of the ear or war):
<!-- Target: deploy.xhtml.to.jboss -->
<target name="deploy.xhtml.to.jboss" description="Deploy xhtml
files to JBoss" if="deployed">
<copy
todir="${jboss.deploy.dir}/${jboss.context.path}/${war.file.name}/xhtml">
<fileset dir="${view.dir}/xhtml" includes="**/*"/>
</copy>
</target>
Because the exploded ear file is not copied to JBoss tmp dir.
But JBoss AS 5 always makes a copy of my exploded ear file and copies it to the tmp dir
where it's the current 'working copy/version' used by JBoss AS - see attached
file: tmp-ear.jpg
My ANT task will not work anymore because the 'working copy/version' used by
JBoss AS now is in the tmp dir and not in the deploy dir.
I really don't want to 'touch' web.xml (or other meta files) to trigger a
full redeployment when I need to make changes to my web files (xhtml, css, javascript,
images etc.).
Could we please have the 'old' behaviour from JBoss AS 4.2.X implemented into
JBoss AS 5 - or is there a workaround to above problem?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira