[
https://jira.jboss.org/jira/browse/JOPR-98?page=com.atlassian.jira.plugin...
]
Jay Shaughnessy commented on JOPR-98:
-------------------------------------
Heiko, you are correct that the the vhost setting unpackWARs="true" is not
overridden during the deploy. And it does force us to ignore the deploy
explode/unexploded property. Understanding this I do have the following in the property
description:
"If yes then explode the WAR file into the Tomcat deploy directory. If no leave as
a .war file (for no, unpackWARs=false is required on this virtual host)."
I decided to include the property only in that it can be used when unpackWARs=false. In
this case the vHost is happy to run either directory or archive deployments, so it seemed
the property was useful.
I agree it's subtle but I don't think it's a bug and I think the property
description is sufficient. If you think we should do something more aggressive, like
disable or hide the property in this case then perhaps we can reopen this as an
enhancement.
Also, we do allow the unpackWARs setting to be configured by the plugin, in the VHost
resource config.
Thanks, -Jay
TC5: Selecting deloy non-exploded still deploys the webapp exploded
--------------------------------------------------------------------
Key: JOPR-98
URL:
https://jira.jboss.org/jira/browse/JOPR-98
Project: Jopr
Issue Type: Bug
Components: Plugin - Tomcat
Affects Versions: 2.2
Reporter: Heiko W. Rupp
Assignee: Jay Shaughnessy
Create a new war child application of a tomcat vhost and select "deploy
non-exploded" from the properties page. Deploy will succeed.
Then go tot tomcat webapps/ and see the application deployed as exploded.
--
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