portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ate Douma <...@douma.nu>
Subject Re: [jira] Commented: (JS2-319) Maven-plugin still too much dependent on hardcoded project configuration
Date Sat, 06 Aug 2005 08:50:48 GMT
David Sean Taylor wrote:
> Ate Douma (JIRA) wrote:
> 
>>     [ 
>> http://issues.apache.org/jira/browse/JS2-319?page=comments#action_12317649 
>> ]
> 
> Is the procedure to run j2:portal.genapp every time after I do a maven 
> clean?
No, it depends on how you configure the following plugin properties:
  # where the filtered tomcat/context.xml is stored
      org.apache.jetspeed.portal.conf.dir=target/portal-conf
   # where the generated and static sql scripts are stored
     org.apache.jetspeed.portal.sql.dir=target/portal-sql
   # where the hsql test.script and/or production.script db is created
      org.apache.jetspeed.portal.db.dir=target/portal-db
   # target for the (static) portal webapp
     org.apache.jetspeed.portal.webapp.dir=target/${org.apache.jetspeed.portal.artifactId}
   # target for the filtered ojb config and jetspeed.properties
     org.apache.jetspeed.portal.target.dir=target/${org.apache.jetspeed.portal.artifactId}

The above configuration is used for the jetspeed build itself, and as result genapp
stores the resources under ${basedir}/target.

But, you are free to redefine these in build.properties as you want.
You can store the generated sources even outside your project if you need.
Then, just add something like a war:webapp postgoal to merge the generated resources with
the target war file.
The idea behind the above default configuration is that you can check in (most of) your custom
project and indeed rerun portal.genapp after a maven clean or a clean checkout.

Note also: portal.genapp is nothing more than a wrapper around several sub goals
each of which uses one of the above properties.
So, you could decide to keep/generate the webapp src with your project src tree (like we have
in jetspeed itself)
and only store the others under ${basedir}/target.
Then, you should integrate those portal.genapp subgoals minus the portal.copy.webapp in your
normal
application development.

I think its flexible enough for most integrator wishes ;-)

> It appears that way, if true, could you clarify as to why that is 
> necessary and if genapp should be a part of normal application 
> development for an integrator. I see genapp as being a one time thing, 
> but maybe I just have a preconcieved idea of what genapp is.
> 
> 
> Thanks,
> 
> David
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
> 
> 
> 
> 
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message