Thanks for all the help so far David. And apologies in advance for the
length of this message.
-----------------------------------------------------------
build.properties:
# general properties
portal.name = jetexpress
# installation properties
installer.src.jar = /Jetspeed/installers/jetspeed-2.2-dev-installer.jar
installer.target = ./target
installer.dst.jar = jetexpress-installer.jar
# development deployment properties
app.server.home = /Jetspeed/server
-------------------------------------------------------------------
I'm not using a directory structure including JetspeedTraining.
Everything is in a directory call Jetspeed on C:
Directory Structure is as follows:
*C:\Jetspeed*
>installers
>jetspeed-2.2-dev-installer.jar
>resources
>applications
>express-demo
>src
>WebContent
>.DS_Store
>decorations
>pages
>seed-data
* >server*
>bin
>common
>conf
>database
>logs
>server
>shared
>temp
* >webapps
>j2-admin
>jetexpress
>jetspeed-portlets
>ROOT
>j2-admin.war
>jetspeed-portlets.war *
>work
* >workspace * *
* / >express-demo
>src
>WebContent
/ >jetexpress
*>build.xml*
>build.properties
>.DS_Store
>dist
>src
>target
* >webapps
>express-demo.war
>jetspeed-portlets.war*
The express-demo directory is, I believe, created by this line in the
build.xml: /<copy todir="../express-demo/" overwrite="true">/ which puts
the express-demo directory at least one level too high as the
create.installer build target never looks there.
Regards,
David Dyer
David Sean Taylor wrote:
Hi David,
Sounds like the PAs are not being deployed to the right place.
Could you send to this list:
1. your build.properties
2. directory listing of /JetspeedTraining/workspace/jetexpress/webapps
3. directory listing of /JetspeedTraining/servers/webapps
or anything else you think is relevant
On Apr 26, 2007, at 4:47 PM, David Dyer wrote:
Thanks David. I'm moving forward now. I've actually managed to build
the jetexpress portal.
On the first build/deployment all the portlets except the login
contain error messages similar to this:
"Failed to retrieve Portlet Definition for express-
demo::WelcomeJetExpressAccess Denied.Failed to retrieve Portlet
Definition for express-demo::WelcomeJetExpressFailed to retrieve
Portlet Definition for express-demo::WelcomeJetExpressFailed to
retrieve Portlet Definition for express-
demo::WelcomeJetExpressFailed to retrieve Portlet Definition for
express-demo::WelcomeJetExpressFailed to retrieve Portlet Definition
for express-demo::WelcomeJetExpress"
So, I assume that this is because they haven't been deployed yet.
I shut down tomcat, cd'd to /Jetspeed/workspace/jetexpress and ran
the copy-portlet-resources, copy-page-resources, copy-decoration-
resources Ant targets. The copy-portlet-resources creates a
subdirectory under workspace called "express-demo" at the same
level as "jetexpress". However none of the targets in the
create.install actually pick up it's contents. Should the location
of express-demo in the workspace be somewhere inside "jetexpress"?
Do we need to add a target to the build file?
I've also tried the delta and deploy.webapps targets and then
rebuilding the installer doing the java -jar and restarting tomcat.
Any advice?
David
David Dyer wrote:
Thanks for the comments David.
I tried downloading the Ant build package from the link you
provided but I'm getting a 404.
Regards,
David
David Sean Taylor wrote:
On Apr 25, 2007, at 1:19 AM, David Dyer wrote:
David Sean Taylor wrote:
"Have you copied in the .setttings.xml to your ".m2" directory
as described here:
http://portals.apache.org/tutorials/jetspeed-2/01/first-steps.html
It will correctly setup the remote repos and copy resources into
here
<localRepository>/JetspeedTraining/maven/repository</
localRepository> "
Yes, the .m2/settings.xml under my user profile directory is
configured, the only difference being the location of Tomcat,
since I already had an installation.
"From that point on, its hit or miss with downloading the files,
keep trying if it fails "
More like miss and miss. It looks to me that at some point
http:// repo1.maven.org/ got restructured and some of the content
is missing from there. It IS, however, at http://
www.bluesunrise.com/, so what I'm thinking is there must be a
reference in the xml somewhere defining which repository to use.
Well you can always try this approach, (but Im sure you have seen
it already on this mailing list)
Download the entire maven repo from here:
http://www.bluesunrise.com/maven2/repository.zip
Be honest I can't even remember if that is a 2.1-dev or 2.1
repository
Just in case you are wiling to try a new approach, I've also added
a new Ant build here. I really prefer to support this one even
though it has no docs:
http://www.bluesunrise.com/tutorials/ant/jetexpress.zip
Unzip it into /Jetspeed/workspace/jetexpress and take a look at
the build.properties
# general properties
portal.name = jetexpress
# installation properties
installer.src.jar = /Jetspeed/installers/jetspeed-2.2-dev-
installer.jar
installer.target = ./target
installer.dst.jar = jetexpress-installer.jar
# development deployment properties
app.server.home = /Jetspeed/server
Note that the location of everything is configurable in the
build.properties for your project
The app.server.home needs to be the same place where you install
your custom jetspeed into
You should also DL the installer which is used as a template for
the build here (required):
http://www.bluesunrise.com/tutorials/ant/jetspeed-2.2-dev-
installer.jar
(Note that the installer includes Tomcat)
The Ant goals available include:
create.installer -- create your own custom installer
delta - deploy decorators and pages
deploy.webapps - deploy the sample webapps included
The resources are here:
http://www.bluesunrise.com/tutorials/ant/resources.zip
After running create.installer
You can cd dist and run the ant installer from there
java -jar jetexpress-installer.jar
remember to install into the same place as app.server.home
this installs the jetexpress portal -- start up the portal just
like any jetspeed portal
cd /Jetspeed/server/bin
./startup.sh
then nav to http://localhost:8080/jetexpress/portal
The next step is to "customize" your portal with your own pages,
decorators, new webapps
You can recreate an installer at anytime based on your changes to
the custom project
So the lesson is to recreate the installer using the resources to
show how to "customize" your portal
Run the three goals to copy in the portal resources:
<!-- Tutorial Resources -->
<target name='copy-portlet-resources'>
<target name='copy-page-resources'>
<target name='copy-decoration-resources'>
(note where the resources dir is expected under /Jetspeed/
resources -- that should probably be configurable...)
you can then build your installer again and re-install
note that there are dev goals for deploying to the running portal
without re-installing of course
the tutorial would also show how to deploy portlet applications
live with eclipse...
I know this isn't the greatest docs, but I prefer to write a good
tutorial then a one-off like this
hope that helps and sorry you had such a bad maven-2 experience
-------------------------------------------------------------------- -
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: jetspeed-user-
[EMAIL PROTECTED]
--
David Dyer
Artifact Software Inc.
[EMAIL PROTECTED]
(514) 995-2830
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.467 / Virus Database: 269.6.2/781 - Release Date: 30/04/2007 9:14 AM
--
David Dyer
Artifact Software Inc.
[EMAIL PROTECTED]
(514) 995-2830
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
