[gatein-issues] [JBoss JIRA] (GTNPORTAL-2595) Rework deployment on AS7

Michal Vanco (JIRA) jira-events at lists.jboss.org
Wed Sep 26 04:00:35 EDT 2012


    [ https://issues.jboss.org/browse/GTNPORTAL-2595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12721699#comment-12721699 ] 

Michal Vanco commented on GTNPORTAL-2595:
-----------------------------------------

Hi Marko,
looking at daily job at jenkins which makes:
mvn clean install -DskipTests -Dservers.dir=$SERVERS_DIR -Dgatein.dev=jbossas712 (gatein master build with AS 7.1.2.Final)

I see in the result build:
 - $JBOSS_HOME/gatein/gatein.ear - ok
 - $JBOSS_HOME/gatein/extensions/* - ok
 - $JBOSS_HOME/gatein/deployments/* - not ok - this folder should be gone I think, it also includes all the apps:
gatein.ear                   gatein-sample-extension.ear.dodeploy  gatein-sample-skin.war           gatein-wsrp-integration.ear.dodeploy
gatein.ear.dodeploy          gatein-sample-portal.ear              gatein-sample-skin.war.dodeploy
gatein-sample-extension.ear  gatein-sample-portal.ear.dodeploy     gatein-wsrp-integration.ear

And there seems to be some mess at gatein/modules/org/gatein/lib/main
 - there are duplicated libs with different versions, e.g. exo.core.component.* 2.4.6-GA + 2.5.0.Beta01, exo.jcr.component.* 1.14.6-GA + 1.15.0-Beta01, exo.kernel.* 2.3.6-GA-JBAS7 + 2.4.0-Beta01, exo.ws.* 2.2.6-GA.jar + 2.3.0-Beta01, picketlink-idm-* 1.3.2.CR02 + 1.4.0.M01

There are only correct versions of components at module.xml, but why are older versions present as well?
Thanks for update
                
> 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


More information about the gatein-issues mailing list