Mike,
On Tue, May 13, 2008 at 1:25 AM, Mike Ahlers
<
mahlers@...> wrote:
> When looking at the libraries used, I see alot jars without versioning (sure
> you can investigate their manifest, but often those aren't correct, i.e.
> with luck you get the version). Some of the jars are alterered, that is,
> they contain patched files to support correct functionality (see saxon-8.8,
> they contain org.orbeon packages and zero saxon packages). And, some of
> these are renamed to reflect transitive dependencies which leads to more
> confusement.
>
> In my opinion, this is wrong. Upgrading becomes hard when you're not sure
> what version you are using.
If you have your own Java code, our recommendation is to use the
"separate deployment" method, so you don't have to worry to much about
what jars are used by Orbeon Forms. This way you can look at the
orbeon.war as one single package, and don't need to worry about the
version of each library we use. Or is it another problem that you
would like to solve?
Alex
--
Orbeon Forms - Web 2.0 Forms, open-source, for the Enterprise
Orbeon's Blog:
http://www.orbeon.com/blog/Personal Blog:
http://avernet.blogspot.com/Twitter -
http://twitter.com/avernet--
You receive this message as a subscriber of the
ops-users@... mailing list.
To unsubscribe: mailto:
ops-users-unsubscribe@...
For general help: mailto:
sympa@...?subject=help
OW2 mailing lists service home page:
http://www.ow2.org/wws
