You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Jason Trust <jt...@ctpartners.com> on 2004/04/27 21:06:52 UTC
upgrading to 1.5
I have reviewed the changes between 1.4 and 1.5, and although there are
real benefits, I am not sure it outweighs the effort to get the current
implementation upgraded. Has anyone gone through an assessment of
upgrading and determined the benefits were worth doing so, or not doing
so. I am just interested in others approach to this process.
Also, now that 1.5 builds using maven, I am not sure of the
ramifications of this to our developer build process. I have eclipse
setup so that an ant build can be performed which will build Jetspeed
from source and integrate our "implementation" specific changes and then
deploy to tomcat. How does the introduction of maven change this? I
read from the readme.txt that the ant build has been deprecated.
I have run maven builds before, but never really looked under the
covers, and wondered how others were approaching this process.
Any thoughts?
Jason Trust
Re: upgrading to 1.5
Posted by "Henry S. Isidro" <hi...@exist.com>.
Jason Trust wrote:
>Also, now that 1.5 builds using maven, I am not sure of the
>ramifications of this to our developer build process. I have eclipse
>setup so that an ant build can be performed which will build Jetspeed
>from source and integrate our "implementation" specific changes and then
>deploy to tomcat. How does the introduction of maven change this? I
>read from the readme.txt that the ant build has been deprecated.
>
>
>
>I have run maven builds before, but never really looked under the
>covers, and wondered how others were approaching this process.
>
>
jetspeed has a plugin for maven that integrates a jetspeed war with any
customizations...check it out
here...http://portals.apache.org/jetspeed-1/plugin/
--
Henry S. Isidro
Software Engineer
Exist Software Labs
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
Re: upgrading to 1.5
Posted by Guillaume Lasnier <gu...@mac.com>.
Check out this project which provides an Eclispe plugin for Maven :
http://mevenide.sourceforge.net/
It manages synchronization bewteen project definitions in both worlds
(Maven and Eclipse) and integration to run Maven within Eclipse.
Le 27 avr. 04, à 21:06, Jason Trust a écrit :
> I have reviewed the changes between 1.4 and 1.5, and although there are
> real benefits, I am not sure it outweighs the effort to get the current
> implementation upgraded. Has anyone gone through an assessment of
> upgrading and determined the benefits were worth doing so, or not doing
> so. I am just interested in others approach to this process.
>
>
>
> Also, now that 1.5 builds using maven, I am not sure of the
> ramifications of this to our developer build process. I have eclipse
> setup so that an ant build can be performed which will build Jetspeed
> from source and integrate our "implementation" specific changes and
> then
> deploy to tomcat. How does the introduction of maven change this? I
> read from the readme.txt that the ant build has been deprecated.
>
>
>
> I have run maven builds before, but never really looked under the
> covers, and wondered how others were approaching this process.
>
>
>
> Any thoughts?
>
>
>
> Jason Trust
>
>
--
Guillaume Lasnier
mailto:guiliguili@mac.com