Excellent. This looks like the guidance that I was seeking.
I have a little trouble parsing your item 3. Can you clarify this?
Are you going to add your ant tasks to the wiki or someplace where we
can have a look at them.
Ron
Aaron Evans wrote:
Ron Wheeler <rwheeler <at> artifact-software.com> writes:
It seems to me that I should be able to use build.properties to get
what I need to get mysql working. I do not want to make any changes to
stuff under $CATALINA_HOME/conf.
I want the buld/install (Maven/Ant goals) to take stuff from my Eclipse
workspace, reconfigure all the configuration files and put it where it
belongs at run-time.
I am hoping that I can find a clear description of how to structure and
configure a working Eclipse application development environment that
does allow me to separate the application from the tool(Jetspeed) so
that I can replace the version of Jetspeed without having to worry that
I will lose key parts of my application in the process. I would like to
run a few standard Maven goals to rebuild and deploy my portal as the
graphic artist and I add new layouts and portlets.
I find it difficult to believe that no one has figured this out already
and documented it. I am hoping that the problem is that I am not yet
smart enough or perceptive enough to find this document and everyone
developing Jetspeed applications already has this all figured out.
Ron
Ron,
I built jetspeed off a M4-SNAPSHOT a while back and have gotten it to build ok
and use mysql. Now perhaps something has changed since now and then and a bug
has been introduced.
But basically, yes, you do the config changes in build.properties as described
here:
http://portals.apache.org/jetspeed-2/database.html
Make sure you have the mysql drivers and they are in the place that you
configure in your build.properties using the properties (further down in
the document):
org.apache.jetspeed.test.jdbc.drivers.path
org.apache.jetspeed.production.jdbc.drivers.path
This can be anywhere on the filesystem, including within your eclipse project.
I think maven needs the drivers in order to run the db setup scripts.
Also, copy the drivers to $CATALINA_HOME\common\endorsed.
As far as setting up an eclipse project for jetspeed, what I have done
is:
1. setup a new eclipse project (type simple) called portal.
TIP: use a workspace where there are no spaces in the path or your builds
will fail.
2. Build the portal to the project directory by setting the property in
build.properties:
org.apache.jetspeed.portal.home
3. I then setup a directory in that project called customizations where I
create additional resources or manage any jetspeed resources I need to change.
I have an ant task that installs all the customizations in the appropriate
spots in the generated jetspeed portal files within the project.
4. I can now run war:install and j2:quickStart to build the war file and deploy
it to tomcat.
But, whenever I want to update my jetspeed project from source, I can
re-run j2:portal.genapp, then apply my customizations using my ant tasks in
eclipse and then run war:install and j2:quickStart.
5. I have also created *separate* eclipse projects for my portal applications.
I build those using ant. I also have ant tasks to hot deploy them to
$CATALINA_HOME/webapps/portal/WEB-INF/deploy and to also add them to the
corresponding deploy directory within the jetspeed portal.
I hope this is helpful.
aaron
---------------------------------------------------------------------
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]
