hmm

"Even for developers it could be nice not to have to rename their
dependencies from version to version..."

i exactly think the opposite...for dev it seems obvious for me (i'll
explain later) but for production it seems far more important.

The point is IMO you can update any jar if you don't know the version (i
think we agree on it) and the easier way for anyone to see it is to check
the name (instead of extracting the jar). Last reason i'm not very
motivated is on production/staging servers you sometimes don't have unzip
and you rarely have jar commands.

Note: if i understand you build a custom tomee? if yes you can do so with
tomee maven plugin easily.

To remove libs use:

<libs><lib>remove:prefix-</lib></libs>

*Romain Manni-Bucau*
*Twitter: @rmannibucau <https://twitter.com/rmannibucau>*
*Blog: **http://rmannibucau.wordpress.com/*<http://rmannibucau.wordpress.com/>
*LinkedIn: **http://fr.linkedin.com/in/rmannibucau*
*Github: https://github.com/rmannibucau*



2013/2/6 Alex The Rocker <[email protected]>

> Hello,
>
> Currently, the JAR files in TomEE distributions (in lib/ directory) include
> the JAR's version number in the JAR file name ; which is kind of redundant
> with MANIFEST.MF content of these JAR files.
>
> Problem with our product now embedding TomEE is that after "GA", we deliver
> service pack with potentially newer TomEE version (for security fixes at
> least).
>
> But with JAR files names changing massively from a TomEE version to
> another, and our dumb fixpack installer unable to remove files, we end up
> with version mixes: after a fix pack is installed with never TomEE version,
> we have a mix of old JAR file and newer one.
>
> I guess this mix can cause a wide mess, unless the newer JAR are referred
> to, for example in a CLASSPATH part of the newer TomEE.
>
> But i'm not sure. I have the feeling that Tomcat was more friendly with
> dumb service pack installers that can't delete file, and has not verion of
> its JAR files naming.
>
> Could TomEE have versionless JAR files naming?
>
> Even for developers it could be nice not to have to rename their
> dependencies from version to version...
>
> Alex.
>

Reply via email to