[
https://issues.jboss.org/browse/GTNPORTAL-2595?page=com.atlassian.jira.pl...
]
Michal Vanco commented on GTNPORTAL-2595:
-----------------------------------------
Ouch, I revisited the scripts and in one job I was missing one line to remove previous
zip. It caused that the new content was added to previous build.
It's fixed now, thanks!
Rework deployment on AS7
------------------------
Key: GTNPORTAL-2595
URL:
https://issues.jboss.org/browse/GTNPORTAL-2595
Project: GateIn Portal
Issue Type: Enhancement
Affects Versions: 3.4.0.Final
Environment: JBoss AS7
Reporter: Marko Strukelj
Assignee: Marko Strukelj
Fix For: 3.5.0.Beta01
GateIn subsystem on AS7 should not perform deployment of portal container via
deployment-scanner. It should perform deployment of the necessary archives
programmatically at boot time.
In a new scheme gatein.ear is located at $JBOSS_HOME/gatein/gatein.ear.
Extension .ears and .wars are placed and discovered in $JBOSS_HOME/gatein/extensions/
directory. That includes custom portals, custom portal extensions, skins, and any user
archives that use GateIn kernel's configuration.xml to integrate with GateIn
services.
There is no $JBOSS_HOME/gatein/deployments any more.
Users can (hot)deploy their portlet applications via AS7 management, or by dropping them
in $JBOSS_HOME/standalone/deployments. If users want to integrate with GateIn's
services at kernel level via configuration.xml, they have to use
$JBOSS_HOME/gatein/extensions/ instead.
Another change is removal of secondary modules root. Modules that used to be in
$JBOSS_HOME/gatein/modules are now merged in $JBOSS_HOME/modules.
Also, in order to use internal AS7 API enhancements, we drop support for 7.1.0.Final.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira