Carlos Sanchez wrote on Tuesday, September 19, 2006 4:37 PM: > The repo is mantained in a no guarantees, free time basis, so your > request to get this solved asap because my client needs it doesn't fit > here. There are companies out there that provide commercial support > around maven and will be able to help you in a more commercial > fashion. I'm not gonna say names but i'm sure somebody in the list can > point you in the right direction ;) > > That said, the repo contains artifacts built by the project, we don't > rebuild anything, we just take whatever they distribute. If you really > really need to make use of the classpath entry in the manifest (I > haven't seen many situations in which that is required) it's becuause > you are using the jars outside of the repo, so I suggest you as simple > solution that when you copy/move the jars you rename them to make use > of the name more convenient for you. > > As people said poms already in the repo can't be changed, anyway that > won't help you with the classpath manifest problem, but you can > contribute pom improvements that can be taken into account in next > versions.
Thanks for stating the obvious :) - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
