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.
On 9/19/06, Markus KARG <[EMAIL PROTECTED]> wrote:
Dan,
what you write sounds good, we will set up our own repository and put
our own fop-0.20.5 on it. On the other hand, its not nice to have a
"private" fop while there is global repository already hosting one. The
fix cannot be done ONLY by fixing the pom, because fop is dependent on
other apache projects that have the same fault (register in
repo1.maven.org with JARs that are not in sync with their POMs), so
supplying our locally implemented fix will not a globally working
solution. Remember, we are Maven starters and so we do not have to
knowledge to solve this problem on our own all alone. But if the authors
of that other projects will help us, we can coordinate work to make it
work finally. Unfortunately it seems, they do NOT want to help us (at
least for now) :-(
Markus
dan tran schrieb:
> If you rely on your customer to build your product, it is best to
> have your own repo to
> solve this kind of crisis. Have maven to search artifact first before
> going to central
>
> In the mean time, It seems you can fix the problem by fixing the pom
> right?
> why not submit it back?
>
> -D
>
> On 9/19/06, *Markus KARG* <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
wrote:
>
>
>
> Bruno Aranda schrieb:
>
> > Well, probably the development community of the Apache Fop
> project can
> > help you. Check the project site [1].
>
>
>
> I have asked them.
> They don't know.
> They even didn't know that FOP is available on that repository.
> So someone just put it up there without their knowledge!
>
>
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
