coping with new version of ops.war

*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

The process has been simplified since 3.0, but it's true that you may
still have to think about what you are doing when upgrading ;-)

I can see two main scenarios:

o If you just work in the /apps/ directory (which is the ideal
   scenario), then you just have to migrate your apps under /apps/ to
   the new version. That's really easy.

o Now if you tend to modify all sorts of other files, including under
   /config/, web.xml, etc., then you can in addition to the above:

   o Be thorough and use a diff tool to merge the changes in the new
     version.

   o Or just remember what changes you made to those files and apply
     them to the new version. For example, if the only change you made
     was switching the theme stylesheet in the epilogue, they just
     reapply this change.

   o Or, hope for the best and just update WEB-INF/lib with the the new
     JARs ;-)

-Erik

Alex Sharaz wrote:
 > Hi,
 >
 > What’s probably a simple question:-
 >
 > Every time I update my copy of ops I have to reinstall all my apps and
 > associated .xml control files.
 >
 > When this was just 1 app it was fairly easy.
 >
 > However, the number of files I have to change is tarting to build up.
 >
 > How do other people cope with upgrading to newer releases?
 >
 > I know I can set up aliases for directories in my web.xml.
 >
 >
 >
 > Would that be the way to do it.?

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

So basically do what i'm doing now :-))
Alex

-----Original Message-----
From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
Sent: 06 February 2007 10:57
To: [hidden email]
Subject: Re: [ops-users] coping with new version of ops.war

The process has been simplified since 3.0, but it's true that you may
still have to think about what you are doing when upgrading ;-)

I can see two main scenarios:

o If you just work in the /apps/ directory (which is the ideal
   scenario), then you just have to migrate your apps under /apps/ to
   the new version. That's really easy.

o Now if you tend to modify all sorts of other files, including under
   /config/, web.xml, etc., then you can in addition to the above:

   o Be thorough and use a diff tool to merge the changes in the new
     version.

   o Or just remember what changes you made to those files and apply
     them to the new version. For example, if the only change you made
     was switching the theme stylesheet in the epilogue, they just
     reapply this change.

   o Or, hope for the best and just update WEB-INF/lib with the the new
     JARs ;-)

-Erik

Alex Sharaz wrote:
 > Hi,
 >
 > What's probably a simple question:-
 >
 > Every time I update my copy of ops I have to reinstall all my apps
and  > associated .xml control files.
 >
 > When this was just 1 app it was fairly easy.
 >
 > However, the number of files I have to change is tarting to build up.
 >
 > How do other people cope with upgrading to newer releases?
 >
 > I know I can set up aliases for directories in my web.xml.
 >
 >
 >
 > Would that be the way to do it.?

--
Orbeon Forms - Web Forms for the Enterprise Done the Right Way
http://www.orbeon.com/


*****************************************************************************************
To view the terms under which this email is distributed, please go to http://www.hull.ac.uk/legal/email_disclaimer.html
*****************************************************************************************

--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

Alex hi

We use ant, and pass it a property which points to a 'plain' unzip of
the Orbeon nightly build. Various ant tasks make use of these files (and
groups of files) during the build process, and where we need to modify a
file (web.xml for example), we use an XSLT transformation task to do it.

So far, this has worked pretty well to give us a clean split between our
own development stuff and the Orbeon framework ...

- Alex.

-------------------------------------
Alex Brown
Director

Griffin Brown Digital Publishing Ltd
Orwell House
Cowley Road
Cambridge
CB4 0PP
United Kingdom

t  +44 (0) 1223 425730
f  +44 (0) 1223 425384
w  http://www.griffinbrown.co.uk/
b  http://www.griffinbrown.co.uk/blog/
--------------------------------------


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws