Just a warning: *don't* use the trunk version 2.2-SNAPSHOT right now.
We're in the process of rewriting the trunk maven-2 configuration completely,
and the archetype artifacts don't even exists anymore in the trunk
(temporarily).
If you want to work from the head of development still in line with the current
documentation you should use the 2.1.3-dev branch instead.
As soon as the 2.2-SNAPSHOT trunk is in a usable state again, we'll let you all
know :)
Regards,
Ate
Steve - old wrote:
I ran into this as well. Perhaps there is an easier answer, but here is
what I found:
If you have ever done a jetspeed build from source the archetypes will
be in your maven repository - you just need to match the versions. For
example, I found
~/.m2/repository/org/apache/portals/jetspeed-2/portal-archetype/portal-archetype-2.2-SNAPSHOT.jar
So, in my case, the version is "2.2-SNAPSHOT". So in my mvn command I
would use:
... -DarchetypeVersion=2.2-SNAPSHOT ...
Steve B.
Johan Wasserman wrote:
Downloading:
http://repo1.maven.org/maven2/org/apache/portals/jetspeed-2/portal-
archetype/2.1-dev/portal-archetype-2.1-dev.jar
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error creating from archetype
Embedded error: Archetype does not exist: Unable to download the
artifact from a
ny repository
I checked the URL, I cannot find the portal-archetype directory
----- Original Message ----
From: David Sean Taylor <[EMAIL PROTECTED]>
To: Jetspeed Users List <jetspeed-user@portals.apache.org>
Sent: Wednesday, August 22, 2007 1:58:03 AM
Subject: Re: Stripping the tutorial
On Aug 21, 2007, at 11:58 AM, Johan Wasserman wrote:
Ok, two issues:
when I go to http://www.mydomain.com it tries to find http://
www.mydomain.com/jetspeed
when I go to http://www.mydomain.com/portal it goes to http://
www.mydomain.com/portal/portal
I want to be able to go to http://www.mydomain.com and hit http://
www.mydomain.com/portal
and when I hit http://mydomain.com/portal it must remain there, and
not add the additional /portal
I don't really want to change anything after I built and installed
using the tutorial mentioned in this thread, so if these things can
be configured before building and installing it'd be great.
The domain part of the URL (http://www.mydomain.com) is configured
outside of Jetspeed
The "/jetspeed" part is configured by you (in the tutorial)
automatically
You can change this in the tutorial by modifying the name of your
project when create your project as described here:
http://portals.apache.org/tutorials/jetspeed-2/01/genapp.html
Say if you wanted a portal with a context named "myproject"
cd \JetspeedTraining\workspace
mvn archetype:create -DarchetypeGroupId=org.apache.portals.jetspeed-2
-DarchetypeArtifactId=portal-archetype
-DarchetypeVersion=2.1-dev
-DgroupId=org.apache.portals.tutorials
-DartifactId=myproject
-Dversion=1.0
You can also change these settings in a deployed system
cd webapps
mv jetspeed/ myproject/
rm jetspeed.war
cd ../conf/Catalina/localhost
mv jetspeed.xml myproject.xml
vi myproject.xml
replace
<Context path="/jetspeed" docBase="jetspeed" crossContext="true">
with
<Context path="/myproject" docBase="myproject" crossContext="true">
The "/portal" part (as in /jetspeed/portal) is currently not
configurable, although I think it could be with a few code changes
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
____________________________________________________________________________________
Boardwalk for $500? In 2007? Ha! Play Monopoly Here and Now (it's
updated for today's economy) at Yahoo! Games.
http://get.games.yahoo.com/proddesc?gamekey=monopolyherenow
---------------------------------------------------------------------
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]
