Re: Jetspeed2-M2 genapp

2005-04-14 Thread Robert Young
I haven't seen any good documentation on how to build a clean jetspeed
portal without the demo portlets. I am wanting to start developing
against J2 M2 and I would like a clean start.  Can somebody point me
in the right direction?

Thanks.

On 4/5/05, Rene Medellin [EMAIL PROTECTED] wrote:
 I didn't see a maven goal in J2-M2 similar to the old
 jetspeed:genapp from J1.5.
 
 I'm trying to generate a stripped-down WAR file that
 will contain only the bare minimum for me to start
 adding my own custom portlets (i.e. minus all the demo
 eye-candy). Anyone got any suggestions?
 
 I reckon just deleting all the portlet warfiles from
 WEB-INF/deploy won't be enough.
 
 Cheers,
 
 - Rene Medellin
 NYC, USA
 
 __
 Do you Yahoo!?
 Yahoo! Personals - Better first dates. More second dates.
 http://personals.yahoo.com
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Jetspeed2-M2 genapp

2005-04-14 Thread Robert Young
So what is the difference in the following goals?

I am making a guess here.

QuickStart: Build with demo portlets and layouts?

MiniStart:  Build without demo portlets, but with layouts and all
necessary database data to deploy your own portlets?

BasicStart:  ?

On 4/14/05, David Sean Taylor [EMAIL PROTECTED] wrote:
 Rene Medellin wrote:
  Yup. Could really use some guidance on that. (Have not
  heard anything on this since the original post)
 
  I think if someone could outline what all the minimal
  pieces are then maybe some of us could take a shot at
  writing the jetspeed2:genapp Maven goal. But the new
  distribution structure is so complex, it's hard to
  know where to begin.
 
 A jetspeed2:genapp goal would be great!
 For custom builds, take the following steps:
 
 1. Start with a basic Jetspeed 2 deployment, such as the M2 distributable
 
 2. create a new project with maven's genapp or eclipse
 
 3. add some goals to this project to:
 - build and deploy my portlet app(s)
 - deploy my custom decorators and layouts
 - replace the default PSML with custom PSML
 - replace the jetspeed assembled components with my own
 
 I think that incorporating these kinds of goals into a standard plugin
 would be very useful.
 
 Note, there are now a number of goals in the base build that we can
 leverage:
 
  goal name=quickStart
  description=Creates the production DB and calls portal/maven
 fullDeploy
  j:set var=deployType value=fullDeploy/
  attainGoal name=doStart/
  /goal
 
  goal name=nodbQuickStart
  description=Don't create a new production DB but call
 portal/maven fullDeploy
  j:set var=deployType value=nodbfullDeploy/
  j:set var=recreateDB value=false/
  attainGoal name=doStart/
  /goal
 
  goal name=minStart
  description=Creates the production DB and calls portal/maven
 minDeploy
  j:set var=deployType value=minDeploy/
  attainGoal name=doStart/
  /goal
 
  goal name=nodbMinStart
  description=Don't create a new production DB but call
 portal/maven minDeploy
  j:set var=deployType value=nodbMinDeploy/
  j:set var=recreateDB value=false/
  attainGoal name=doStart/
  /goal
 
  goal name=basicStart
  description=Creates the production DB and calls portal/maven
 basicDeploy
  j:set var=deployType value=minDeploy/
  attainGoal name=doStart/
  /goal
 
  goal name=nodbBasicStart
  description=Don't create a new production DB but call
 portal/maven nodbBasicDeploy
  j:set var=deployType value=nodbBasicDeploy/
  j:set var=recreateDB value=false/
  attainGoal name=doStart/
  /goal
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]