Hi Nikko,

Thanks for giving me the opportunity to try this. I'm getting this error,

I built j2 using m2 using the command 'mvn -P tomcat'

I used the same command as you to build the custom portal,

mvn archetype:create -DarchetypeGroupId=org.apache.portals.jetspeed-2
-DarchetypeArtifactId=portal-archetype -DarchetypeVersion=2.1-dev
-DgroupId=myportalgroup -DartifactId=myportal -Dversion=1.0

Then I tried to build it using 'mvn -o'

It is failing in appservers/tomcat-build.xml on the ant task deploy
and the error is,

/tmp/etc/conf/tomcat not found

I changed line 116 to,

<fileset dir="${basedir}/myportal/etc/conf/tomcat">

I'm not sure why basedir not set to app-servers.

Check out this guide,
http://wiki.apache.org/portals/Jetspeed2/Maven2BuildSupport

You don't need a properties file. You need to copy the
settings.xml.sample from the j2 source to ~/.m2 (your home directory
contains a .m2 directory).

Then modify it to reflect your tomcat installation.

After the above modification I was able to build the custom portal
using the command 'mvn -o' This deployed it to tomcat.

Philip

On 9/26/06, Nikko Gaerlan <[EMAIL PROTECTED]> wrote:
hi lists..

does Jetspeed 2.1-dev Maven2 Custom Portal Generation work?


after executing this line..

*mvn archetype:create -DarchetypeGroupId=org.apache.portals.jetspeed-2
 -DarchetypeArtifactId=portal-archetype -DarchetypeVersion=2.1-dev
 -DgroupId=myportalgroup -DartifactId=myportal -Dversion=1.0*
it seems fine and no problems..

when I deploy it using mvn -P tomcat..

error..

i need more detailed instructions..

does the two additional archetypes optional or required?

i'm completely lost here..

sorry for being such a noob..

or you may suggest me to use maven1 build instead?..

thanks in advance..




--
Philip Donaghy
donaghy.blogspot.com del.icio.us/donaghy/philip
Skype: philipmarkdonaghy
Office: +33 5 56 60 88 02
Mobile: +33 6 20 83 22 62

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

Reply via email to