portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Roger Ruttimann <roger.ruttim...@earthlink.net>
Subject Re: Some mean-spirited whining about the build...
Date Sun, 01 Jan 2006 22:14:05 GMT
David Jencks wrote:

> I thought I'd have some fun looking at how to do the geronimo  
> security integration, so I started out by trying to build jetspeed  
> and get it running on something.  Here are a few comments that might  
> help out other new users.
>
> The documentation uniformly claims that hslqldb is the default db,  
> but the build appears to use derby.  This makes me distrust  
> everything the documentation says.
>
> The build forces me to  set a bunch of parameters relating to where  
> tomcat is, but AFAICT they are never used in the main build. After I  
> set them and run maven allBuild, my tomcat install is unchanged.  I'm  
> not sure why someone who wants to run jetspeed on say jetty should be  
> forced to set a lot of parameters that are tomcat specific.  Perhaps  
> the only checks for these parameters being set could be when the part  
> of the plugin that uses them is executed?

We should clearly separate build and deployment properties so that a 
build can be run without having tomcat (jetty in the future) available 
on the build machine.
Since we plan to update the build procedure we should keep that in mind.

In addition a build (checkout) should run without any settings in the 
~/build.properties file.

>
> The maven plugin seems to require quite a few dependencies that are  
> not listed as maven dependencies.  The plugin expects them to be in
>
>  ~/.maven/repository/org.apache.portals.bridges/wars
>
> but on cvs.apache.org they are in
>
> http://cvs.apache.org/repository/org.apache.portals.bridges/
>
> which definitely seems like a mistake to me.
>
> I also wonder why the maven plugin has so many portlet apps to deploy  
> hardcoded into it.  This seems contrary to the purpose of a plugin to  
> me.  Another design choice might be to have a plugin goal to iterate  
> through the dependencies in the project.xml and deploy specially  
> marked dependencies.  Then you could have a couple of example  
> projects using the plugin that deployed the full or min set of  
> portlet apps.  Although I'm not yet familiar with what the plugin is  
> supposed to do I think this might provide a useful prototype for  
> people to build other portals off of.
>
> Many thanks,
> david jencks
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
> For additional commands, e-mail: jetspeed-dev-help@portals.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org


Mime
View raw message