You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Markus KARG <ka...@quipsy.de> on 2006/09/19 12:30:01 UTC
Who is the maintainer of the fop:fop project found on repo1.maven.org?
I need to find out the maintainer of the fop:fop project on repo1.maven.org.
There is a severe bug in the published JAR that prevents referencing
this project from own projects.
Please either fix the bug or tell me the name of the maintainer so I can
ask him to fix it!
As there is no JIRA group for that project, I also cannot file a JIRA issue.
It's all about the fop plugin (groupId: fop, artifactId: fop). The
current version is 0.20.5. That version's pom.xml found on
repo1.maven.org contains a dependency on "xml-apis-1.0.b2.jar"
(xml-apis, version 1.0.b2), which should result in "Class-Path:
xml-apis-1.0.b2.jar" to be written in the main artifact "fop-0.20.5.jar".
Actually the "fop-0.20.5.jar" found on repo1.maven.org doesn't contain
"Class-Path: xml-apis-1.0.b2.jar" but "Class-Path: xml-apis.jar" which
results in a class path resolving problem at run time in any project
using FOP 0.20.5!
The same problem not only happens with "xml-apis" but with nearly ALL
dependencies of fop-0.20.5 (e. g. also with "batik")!
This has to be fixed ASAP to make those projects work!
The fix is quite easy, just modify the Class-Path: entry or do "mvn
clean deploy" to push another copy to repo1.maven.org.
The problem is really urgent since we need this and we do not have write
access to that folder on of repo1.maven.org.
Thanks
Markus
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
You want me to submit a new pom.xml for fop-0.20.5 to that JIRA group?
And how do you verify that I didn't do another bug?
I mean, ain't there some kind of quality assurance of repo contents?
dan tran schrieb:
> And submit it back to http://jira.codehaus.org/browse/MEV
>
> -D
>
> On 9/19/06, Busch, Hendrik (LNG-MUE) <he...@lexisnexis.de> wrote:
>
>>
>> Hi,
>>
>> >>> This has to be fixed ASAP to make those projects work!
>> >>> The fix is quite easy, just modify the Class-Path: entry or do "mvn
>> >>> clean deploy" to push another copy to repo1.maven.org.
>> >>>
>> >>> The problem is really urgent since we need this and we do not have
>> write
>> >>> access to that folder on of repo1.maven.org.
>>
>> If this is a really urgent matter I suggest that you fix that problem on
>> your own side. Just apply the fix you suggested to the jar file from
>> repo1 and install it to your local repository server (or your local .m2
>> directory if you happen to have no own server) using a a special version
>> number and reference this newly installed artifact version in your
>> projects.
>>
>> --
>> Mit freundlichen Gr��en / Kind regards
>>
>> Hendrik Busch - Stellv. Leiter der Softwareentwicklung
>>
>> LexisNexis Deutschland GmbH
>> http://www.lexisnexis.de
>> Feldstiege 100
>> D-48161 M�nster
>> phone +49 (0) 2533-9300-455
>> fax +49 (0) 02533-9300-50
>> hendrik.busch@lexisnexis.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by dan tran <da...@gmail.com>.
And submit it back to http://jira.codehaus.org/browse/MEV
-D
On 9/19/06, Busch, Hendrik (LNG-MUE) <he...@lexisnexis.de> wrote:
>
> Hi,
>
> >>> This has to be fixed ASAP to make those projects work!
> >>> The fix is quite easy, just modify the Class-Path: entry or do "mvn
> >>> clean deploy" to push another copy to repo1.maven.org.
> >>>
> >>> The problem is really urgent since we need this and we do not have
> write
> >>> access to that folder on of repo1.maven.org.
>
> If this is a really urgent matter I suggest that you fix that problem on
> your own side. Just apply the fix you suggested to the jar file from
> repo1 and install it to your local repository server (or your local .m2
> directory if you happen to have no own server) using a a special version
> number and reference this newly installed artifact version in your
> projects.
>
> --
> Mit freundlichen Grüßen / Kind regards
>
> Hendrik Busch - Stellv. Leiter der Softwareentwicklung
>
> LexisNexis Deutschland GmbH
> http://www.lexisnexis.de
> Feldstiege 100
> D-48161 Münster
> phone +49 (0) 2533-9300-455
> fax +49 (0) 02533-9300-50
> hendrik.busch@lexisnexis.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
Busch, Hendrik (LNG-MUE) schrieb:
> Hi,
>
>>>> This has to be fixed ASAP to make those projects work!
>>>> The fix is quite easy, just modify the Class-Path: entry or do "mvn
>>>> clean deploy" to push another copy to repo1.maven.org.
>>>>
>>>> The problem is really urgent since we need this and we do not have
>>>> write
>>>> access to that folder on of repo1.maven.org.
>>>
>
> If this is a really urgent matter I suggest that you fix that problem
> on your own side. Just apply the fix you suggested to the jar file
> from repo1 and install it to your local repository server (or your
> local .m2 directory if you happen to have no own server) using a a
> special version number and reference this newly installed artifact
> version in your projects.
>
Yes this is urgent and we fixed it on our side meanwhile, but our
customers rely on beeing able to build our products using Maven and so
there is no help currently but to tell them "The stuff on the Maven
repository is broken". :-(
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by "Busch, Hendrik (LNG-MUE)" <he...@lexisnexis.de>.
Hi,
>>> This has to be fixed ASAP to make those projects work!
>>> The fix is quite easy, just modify the Class-Path: entry or do "mvn
>>> clean deploy" to push another copy to repo1.maven.org.
>>>
>>> The problem is really urgent since we need this and we do not have write
>>> access to that folder on of repo1.maven.org.
If this is a really urgent matter I suggest that you fix that problem on
your own side. Just apply the fix you suggested to the jar file from
repo1 and install it to your local repository server (or your local .m2
directory if you happen to have no own server) using a a special version
number and reference this newly installed artifact version in your projects.
--
Mit freundlichen Grüßen / Kind regards
Hendrik Busch - Stellv. Leiter der Softwareentwicklung
LexisNexis Deutschland GmbH
http://www.lexisnexis.de
Feldstiege 100
D-48161 Münster
phone +49 (0) 2533-9300-455
fax +49 (0) 02533-9300-50
hendrik.busch@lexisnexis.de
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Geoffrey De Smet <ge...@gmail.com>.
Markus KARG wrote, On 2006-09-19 3:37 PM:
>
>
> 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!
>
That's the case for a good number of projects (those that don't use
maven and don't use maven's ant tasks).
The poms of these projects usually have a lot more bugs then those done
by the developers themselves. Don't be afraid to make fop-0.20.5.markus1
in your repo that fixes bugs in those poms (and send the fixed poms to
their dev list).
Meanwhile vote for the fop issue to get decent poms in the repo. The
system works: the most voted issue for spring (decent poms in the repo)
will be fixed for spring 2.0. The will even switch their build to maven2
after 2.0 :)
BTW: Once something is deployed to the repo, it shouldn't be changed,
unless it ends with "-SNAPSHOT" (due to local repo caching). So there
isn't really a way to fix 0.20.5's pom, without changing the version number.
All in all, you're poking the wrong mailing list :)
--
With kind regards,
Geoffrey De Smet
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
Carlos Sanchez schrieb:
> 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.
>
Once more, I didn't ask anyone to fix it, I asked for the name of the
author of that pom file to help him fixing it.
Maybe you didn't get me wrong here. I will also spent my free time to do
that, as you do. But I want to spent my spare time to create quality.
repo1.maven.org is a special place because every mvn installation knows
it and such we all have to care not to put things up there that do not work.
Is it so hard to take a bit care before pushing a JAR into it? If it is,
here is my offer: Do not upload it before I have spend my free time to
check its quality.
No problem, I will do.
Markus
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Carlos Sanchez <ca...@apache.org>.
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 <ka...@quipsy.de> 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* <karg@quipsy.de <ma...@quipsy.de>> 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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
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* <karg@quipsy.de <ma...@quipsy.de>> 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!
>
>
>
>
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by dan tran <da...@gmail.com>.
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 <ka...@quipsy.de> 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!
>
>
>
>
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
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!
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Bruno Aranda <br...@gmail.com>.
Well, probably the development community of the Apache Fop project can
help you. Check the project site [1].
Cheers,
Bruno
[1] http://xmlgraphics.apache.org/fop/
On 9/19/06, Markus KARG <ka...@quipsy.de> wrote:
> Carlos,
>
> actually the repo MUST be changes since the jar IS WRONG.
>
> So if there is no maintainer and no JIRA: WHOM TO TELL ABOUT THE BUG NOW ?
>
> Markus
>
> Carlos Sanchez schrieb:
>
> > I don't think the repo needs to be changed to meet your requirements.
> > And it's a collective effort, there's no mantainer.
> >
> > On 9/19/06, Markus KARG <ka...@quipsy.de> wrote:
> >
> >> I need to find out the maintainer of the fop:fop project on
> >> repo1.maven.org.
> >> There is a severe bug in the published JAR that prevents referencing
> >> this project from own projects.
> >>
> >> Please either fix the bug or tell me the name of the maintainer so I can
> >> ask him to fix it!
> >>
> >> As there is no JIRA group for that project, I also cannot file a JIRA
> >> issue.
> >>
> >> It's all about the fop plugin (groupId: fop, artifactId: fop). The
> >> current version is 0.20.5. That version's pom.xml found on
> >> repo1.maven.org contains a dependency on "xml-apis-1.0.b2.jar"
> >> (xml-apis, version 1.0.b2), which should result in "Class-Path:
> >> xml-apis-1.0.b2.jar" to be written in the main artifact
> >> "fop-0.20.5.jar".
> >> Actually the "fop-0.20.5.jar" found on repo1.maven.org doesn't contain
> >> "Class-Path: xml-apis-1.0.b2.jar" but "Class-Path: xml-apis.jar" which
> >> results in a class path resolving problem at run time in any project
> >> using FOP 0.20.5!
> >>
> >> The same problem not only happens with "xml-apis" but with nearly ALL
> >> dependencies of fop-0.20.5 (e. g. also with "batik")!
> >>
> >> This has to be fixed ASAP to make those projects work!
> >> The fix is quite easy, just modify the Class-Path: entry or do "mvn
> >> clean deploy" to push another copy to repo1.maven.org.
> >>
> >> The problem is really urgent since we need this and we do not have write
> >> access to that folder on of repo1.maven.org.
> >>
> >> Thanks
> >> Markus
> >>
> >>
> >>
> >
> >
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Bruno Aranda <br...@gmail.com>.
A released jar cannot be modified. A bug can be fixed, but in the next
version/bugfix of the artifact (and maybe you could provide such a
fixed artifact). All this is a community effort where everyone can
participate. It is not right to change anything in a released
artifact, because you are never sure that the bug you are fixing will
cause other bugs...
Bruno
On 9/20/06, Markus KARG <ka...@quipsy.de> wrote:
> So the policy is "A bug cannot be fixed"?!
>
> Jochen Wiedmann schrieb:
>
> > Markus KARG wrote:
> >
> >> If Carlos is able to upload it while I seem not to be, he actually is
> >> in the role of the maintainer.
> >> Where am I going wrong with that assumption?
> >
> >
> > Your assumption is, that he is able to change files in the repository.
> > The answer is he isn't. Ok, he may be able to do that technically, but
> > the policy is clearly that already released files are left unchanged -
> > forever.
> >
> >
> > Jochen
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
Well, since I am in the business of QA for ten years now, believe me,
there can be a better one:
The bug was detected after months by incident.
A good QA would have detected it before publishing the release.
Also there still is no fix, since I am a beginner with Maven and a
beginner with FOP. Actually I do not know well both, I just wanted to
use FOP in my own project and found the bug. Now you require me to learn
a lot about Maven, Ibiblio and FOP's INTERNALS(!) to get this fixed.
Actually I like contributing fixes once I am qualified to do that. But
for now I think there must be better ways than learning for FOP
internals just to get fixed a bug that was neither done by FOP not by
the Maven team nor by me -- identify the causer and make him fix HIS bug.
So do you still think there couldn't be a better QA?
Bruno Aranda schrieb:
> The community itself is the community control. See your case. It is
> the user that reports if something fails, and maybe suggests/provides
> a patch or has the patience to let other do it. Here, there is no such
> a master-slave relationship where someone tells the changes and others
> do. If you need something, you can do it yourself. All the
> users/experts around here are the QA. And I assure you that it cannot
> be a better QA...
>
> Bruno
>
> On 9/20/06, Markus KARG <ka...@quipsy.de> wrote:
>
>> So since bugs once released cannot get fixed without changing the
>> version (what is problematic with FOP as we have discussed today), this
>> is one more reason for not let anybody upload things without doing
>> quality control. :-)
>>
>> Wayne Fay schrieb:
>>
>> > Yes, this is the point of the discussion. Please search this mail list
>> > (Nabble etc) and Maven Dev to see the entire history of this issue.
>> >
>> > Increment version by one, upload it, and allow Maven to find the
>> > updated version the next time your build runs, it will automatically
>> > find and use it.
>> >
>> > Wayne
>> >
>> > On 9/20/06, Markus KARG <ka...@quipsy.de> wrote:
>> >
>> >> So the policy is "A bug cannot be fixed"?!
>> >>
>> >> Jochen Wiedmann schrieb:
>> >>
>> >> > Markus KARG wrote:
>> >> >
>> >> >> If Carlos is able to upload it while I seem not to be, he
>> actually is
>> >> >> in the role of the maintainer.
>> >> >> Where am I going wrong with that assumption?
>> >> >
>> >> >
>> >> > Your assumption is, that he is able to change files in the
>> repository.
>> >> > The answer is he isn't. Ok, he may be able to do that
>> technically, but
>> >> > the policy is clearly that already released files are left
>> unchanged -
>> >> > forever.
>> >> >
>> >> >
>> >> > Jochen
>> >> >
>> >> >
>> >> >
>> ---------------------------------------------------------------------
>> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> >> > For additional commands, e-mail: users-help@maven.apache.org
>> >> >
>> >>
>> >>
>> >>
>> >>
>>
>>
>>
>>
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Bruno Aranda <br...@gmail.com>.
The community itself is the community control. See your case. It is
the user that reports if something fails, and maybe suggests/provides
a patch or has the patience to let other do it. Here, there is no such
a master-slave relationship where someone tells the changes and others
do. If you need something, you can do it yourself. All the
users/experts around here are the QA. And I assure you that it cannot
be a better QA...
Bruno
On 9/20/06, Markus KARG <ka...@quipsy.de> wrote:
> So since bugs once released cannot get fixed without changing the
> version (what is problematic with FOP as we have discussed today), this
> is one more reason for not let anybody upload things without doing
> quality control. :-)
>
> Wayne Fay schrieb:
>
> > Yes, this is the point of the discussion. Please search this mail list
> > (Nabble etc) and Maven Dev to see the entire history of this issue.
> >
> > Increment version by one, upload it, and allow Maven to find the
> > updated version the next time your build runs, it will automatically
> > find and use it.
> >
> > Wayne
> >
> > On 9/20/06, Markus KARG <ka...@quipsy.de> wrote:
> >
> >> So the policy is "A bug cannot be fixed"?!
> >>
> >> Jochen Wiedmann schrieb:
> >>
> >> > Markus KARG wrote:
> >> >
> >> >> If Carlos is able to upload it while I seem not to be, he actually is
> >> >> in the role of the maintainer.
> >> >> Where am I going wrong with that assumption?
> >> >
> >> >
> >> > Your assumption is, that he is able to change files in the repository.
> >> > The answer is he isn't. Ok, he may be able to do that technically, but
> >> > the policy is clearly that already released files are left unchanged -
> >> > forever.
> >> >
> >> >
> >> > Jochen
> >> >
> >> >
> >> > ---------------------------------------------------------------------
> >> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> > For additional commands, e-mail: users-help@maven.apache.org
> >> >
> >>
> >>
> >>
> >>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
So since bugs once released cannot get fixed without changing the
version (what is problematic with FOP as we have discussed today), this
is one more reason for not let anybody upload things without doing
quality control. :-)
Wayne Fay schrieb:
> Yes, this is the point of the discussion. Please search this mail list
> (Nabble etc) and Maven Dev to see the entire history of this issue.
>
> Increment version by one, upload it, and allow Maven to find the
> updated version the next time your build runs, it will automatically
> find and use it.
>
> Wayne
>
> On 9/20/06, Markus KARG <ka...@quipsy.de> wrote:
>
>> So the policy is "A bug cannot be fixed"?!
>>
>> Jochen Wiedmann schrieb:
>>
>> > Markus KARG wrote:
>> >
>> >> If Carlos is able to upload it while I seem not to be, he actually is
>> >> in the role of the maintainer.
>> >> Where am I going wrong with that assumption?
>> >
>> >
>> > Your assumption is, that he is able to change files in the repository.
>> > The answer is he isn't. Ok, he may be able to do that technically, but
>> > the policy is clearly that already released files are left unchanged -
>> > forever.
>> >
>> >
>> > Jochen
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>>
>>
>>
>>
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Wayne Fay <wa...@gmail.com>.
Yes, this is the point of the discussion. Please search this mail list
(Nabble etc) and Maven Dev to see the entire history of this issue.
Increment version by one, upload it, and allow Maven to find the
updated version the next time your build runs, it will automatically
find and use it.
Wayne
On 9/20/06, Markus KARG <ka...@quipsy.de> wrote:
> So the policy is "A bug cannot be fixed"?!
>
> Jochen Wiedmann schrieb:
>
> > Markus KARG wrote:
> >
> >> If Carlos is able to upload it while I seem not to be, he actually is
> >> in the role of the maintainer.
> >> Where am I going wrong with that assumption?
> >
> >
> > Your assumption is, that he is able to change files in the repository.
> > The answer is he isn't. Ok, he may be able to do that technically, but
> > the policy is clearly that already released files are left unchanged -
> > forever.
> >
> >
> > Jochen
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Jochen Wiedmann <jo...@gmail.com>.
Barrie Treloar wrote:
> The problem that Jorg points out is still outstanding is what naming
> conventions should be used to indicate that this fixes a problem with
> an already released version of the artifact.
There is no problem.
If the artifact is actually modified, then it's a different release. In
other words, one needs a new version number. Note, that the version
number might be something like "0.20.5-fix1" or whatever.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
I expected that if the bug is not in the release but the release itself,
then the release can be undone.
All car manufacturers do that. If there is a severe bug that is likely
to kill lots of people, then they take back thousands of cars to fix the
problem on the vendor's cost.
I don't see that this beeing not possible with something volatile than
software.
Jochen Wiedmann schrieb:
> Markus KARG wrote:
>
>> So the policy is "A bug cannot be fixed"?!
>
>
> The policy is "A bug can be fixed in the next version". What else did
> you expect?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Jochen Wiedmann <jo...@gmail.com>.
Markus KARG wrote:
> So the policy is "A bug cannot be fixed"?!
The policy is "A bug can be fixed in the next version". What else did
you expect?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
So the policy is "A bug cannot be fixed"?!
Jochen Wiedmann schrieb:
> Markus KARG wrote:
>
>> If Carlos is able to upload it while I seem not to be, he actually is
>> in the role of the maintainer.
>> Where am I going wrong with that assumption?
>
>
> Your assumption is, that he is able to change files in the repository.
> The answer is he isn't. Ok, he may be able to do that technically, but
> the policy is clearly that already released files are left unchanged -
> forever.
>
>
> Jochen
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Jochen Wiedmann <jo...@gmail.com>.
Markus KARG wrote:
> If Carlos is able to upload it while I seem not to be, he actually is in
> the role of the maintainer.
> Where am I going wrong with that assumption?
Your assumption is, that he is able to change files in the repository.
The answer is he isn't. Ok, he may be able to do that technically, but
the policy is clearly that already released files are left unchanged -
forever.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
Barrie Treloar schrieb:
>
> Carlos did tell you who maintains it and the answer is no one.
>
> Carlos is just one of the people who will upload your pom and artifact
> if you follow the instructions on the web site.
>
> So you are able to make the necessary changes and get it fixed.
>
> The problem that Jorg points out is still outstanding is what naming
> conventions should be used to indicate that this fixes a problem with
> an already released version of the artifact.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
If Carlos is able to upload it while I seem not to be, he actually is in
the role of the maintainer.
Where am I going wrong with that assumption?
Markus
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Barrie Treloar <ba...@gmail.com>.
On 9/20/06, Markus KARG <ka...@quipsy.de> wrote:
>
> > i.e. No on maintains the FOP available in the repo.
> > It is there as a convenience only.
> >
> > I might also suggest you adjust your attitude.
>
> Sorry for beeing rude and thank you for telling me.
> It wasn't my intention.
>
> But see, I just want to know who is the guy that has write access to the
> FOP's pom.xml.
> After two days I get told "Carlos", while Carlos actually wasn't able to
> tell me that directly in his first email.
> Isn't it ironic to discuss two days (over 20 emails) instead of just
> writing "Hi, I'm Carlos, it's me whom you have to send the fixed pom.xml"?
> Don't you think you would be a bit rude then, too?
Carlos did tell you who maintains it and the answer is no one.
Carlos is just one of the people who will upload your pom and artifact
if you follow the instructions on the web site.
So you are able to make the necessary changes and get it fixed.
The problem that Jorg points out is still outstanding is what naming
conventions should be used to indicate that this fixes a problem with
an already released version of the artifact.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
> i.e. No on maintains the FOP available in the repo.
> It is there as a convenience only.
>
> I might also suggest you adjust your attitude.
Sorry for beeing rude and thank you for telling me.
It wasn't my intention.
But see, I just want to know who is the guy that has write access to the
FOP's pom.xml.
After two days I get told "Carlos", while Carlos actually wasn't able to
tell me that directly in his first email.
Isn't it ironic to discuss two days (over 20 emails) instead of just
writing "Hi, I'm Carlos, it's me whom you have to send the fixed pom.xml"?
Don't you think you would be a bit rude then, too?
Markus
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Barrie Treloar <ba...@gmail.com>.
Markus writes:
> That's why I am asking for the name of the maintainer, so that I can ask
> him to do that...
As Carlos said in another email:
> 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.
i.e. No on maintains the FOP available in the repo.
It is there as a convenience only.
I might also suggest you adjust your attitude.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
Wayne Fay schrieb:
> As previously mentioned, it is quite honestly not possible to "fix"
> that specific version of the pom. For a very brief period of time,
> Maven was allowing changes to poms but then realized this was a bad
> idea. So instead the proper way to fix issues like this is to actually
> release a new version of the Maven artifact including an updated pom.
That's why I am asking for the name of the maintainer, so that I can ask
him to do that...
>
> As for the question "who is the maintainer of this pom" -- unless the
> FOP team has specifically taken over the Maven artifact for their
> project, **anyone** can be the maintainer. This means you, or me, or
> any one else interested enough in Maven and FOP to actually do the
> work and submit the Maven Upload JIRA.
So anyone can just put up some buggy JARs into that repository.
Do you think this to be beneficial for the overall quality of the
content...?
>
> In this case, I would suggest the following, as you appear to be very
> well versed in this particular artifact and it sounds like the FOP
> team does not currently maintain the pom file...
Not only not currently. THEY HAVE NEITHER WRITTEN IT. THE FOP TEAM DOES
NOT AT ALL KNOW OF ITS PURE EXISTENCE.
Clear now? ;-)
>
> Download the FOP source code (or binary if you won't compile it) for
> version 0.20.5
> Download the pom.xml for version 0.20.5
> Alter the pom.xml as needed and bump version to 0.20.5.1
> Compile the source code if needed and package the JAR
> Create the Maven artifact bundle using the new 0.20.5.1 pom
> (Install this artifact in your local repo and make sure it works like
> you expect by using it in your project, check the Class-Path etc)
> Create a new Maven JIRA for this new version and attach your new
> bundle to the issue
> Wait for feedback from Carlos et al and hope you didn't screw anything
> up; if so, adjust your bundle as requested and re-upload
> Once accepted, the new artifact will appear in Central
So actually Carlos is the maintainer?
That's all I liked to know actually.
So I'll look into doing that.
> This is your best approach (imo) to get this updated FOP artifact
> installed in the Maven Repo. Unless of course someone else has a
> better suggestion...
>
> You asked about "quality control" previously... The assumption is that
> the people contributing builds to Maven are competent enough to create
> proper builds with reasonable pom.xml files etc. Ideally every Java
> project will eventually take over as maintainers of the Maven artifact
> but this is not required, nor is it entirely reasonable to expect it
> to ever occur.
You need to know that our company is deeply involved into the business
of quality assurance.
So what you write is wrong. Nobody can rely on others to be good enough.
You need to control quality EVER.
As a proof, see the FOP project. Nobody knows where the author of that
buggy pom.xml was, and it needed a two days discussion on how to fix it.
That's not quality assurance, that's pure random.
This is acceptable for any repository, but not for that one that is
listed automatically with every installation of Maven 2.0.4.
> While there is some checking and testing before artifacts are
> installed into Central, in general, its not reasonable to expect the
> handful of Maven Repo maintainers to know everything about every
> project, so instead they simply trust the community and provide a way
> to "easily" update the artifacts, so when problems appear, the
> community can "easily" take care of it. Maven automatically looks for
> updates to artifacts, so new versions are pulled down and used as they
> are made available.
Well, in case of FOP this trust doesn't seem to work...
Markus
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Wayne Fay <wa...@gmail.com>.
As previously mentioned, it is quite honestly not possible to "fix"
that specific version of the pom. For a very brief period of time,
Maven was allowing changes to poms but then realized this was a bad
idea. So instead the proper way to fix issues like this is to actually
release a new version of the Maven artifact including an updated pom.
As for the question "who is the maintainer of this pom" -- unless the
FOP team has specifically taken over the Maven artifact for their
project, **anyone** can be the maintainer. This means you, or me, or
any one else interested enough in Maven and FOP to actually do the
work and submit the Maven Upload JIRA.
In this case, I would suggest the following, as you appear to be very
well versed in this particular artifact and it sounds like the FOP
team does not currently maintain the pom file...
Download the FOP source code (or binary if you won't compile it) for
version 0.20.5
Download the pom.xml for version 0.20.5
Alter the pom.xml as needed and bump version to 0.20.5.1
Compile the source code if needed and package the JAR
Create the Maven artifact bundle using the new 0.20.5.1 pom
(Install this artifact in your local repo and make sure it works like
you expect by using it in your project, check the Class-Path etc)
Create a new Maven JIRA for this new version and attach your new
bundle to the issue
Wait for feedback from Carlos et al and hope you didn't screw anything
up; if so, adjust your bundle as requested and re-upload
Once accepted, the new artifact will appear in Central
This is your best approach (imo) to get this updated FOP artifact
installed in the Maven Repo. Unless of course someone else has a
better suggestion...
You asked about "quality control" previously... The assumption is that
the people contributing builds to Maven are competent enough to create
proper builds with reasonable pom.xml files etc. Ideally every Java
project will eventually take over as maintainers of the Maven artifact
but this is not required, nor is it entirely reasonable to expect it
to ever occur.
While there is some checking and testing before artifacts are
installed into Central, in general, its not reasonable to expect the
handful of Maven Repo maintainers to know everything about every
project, so instead they simply trust the community and provide a way
to "easily" update the artifacts, so when problems appear, the
community can "easily" take care of it. Maven automatically looks for
updates to artifacts, so new versions are pulled down and used as they
are made available.
Wayne
On 9/20/06, Markus KARG <ka...@quipsy.de> wrote:
>
> this thread is not about local repositories or Sun JARs, it is solely
> about a bug I WANT TO FIX IN REPO1.MAVEN.ORG IN ONLY THE FOP PROJECT.
> Not more. Not less. So do you know the author of the fop:fop pom.xml
> file so that I can tell him of the bug, or don't you? Sorry, but
> meanwhile this thread is used by anyone to discuss anything...
>
> Markus
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
>it's a common situation that you have to maintain a local repository,
>maybe company wide and using a proxy to mirror repo1's contents.
>So better you get used to it.
>Just think about all those proprietary libs which can't be provided by
>repo1 for licensing reasons. Examples are all Sun jars or the Oracle
>jdbc driver. You have to install all of them on your own in your own
>repo. So why not do the same with fop:fop?
>
>
Stefan,
this thread is not about local repositories or Sun JARs, it is solely
about a bug I WANT TO FIX IN REPO1.MAVEN.ORG IN ONLY THE FOP PROJECT.
Not more. Not less. So do you know the author of the fop:fop pom.xml
file so that I can tell him of the bug, or don't you? Sorry, but
meanwhile this thread is used by anyone to discuss anything...
Markus
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Stefan Prange <St...@gmx.de>.
Markus KARG wrote:
> What sense does it make to have jar and pom.xml found in the
> repo that in fact are not in sync and cannot be used at all?
Hi Markus,
it's a common situation that you have to maintain a local repository,
maybe company wide and using a proxy to mirror repo1's contents.
So better you get used to it.
Just think about all those proprietary libs which can't be provided by
repo1 for licensing reasons. Examples are all Sun jars or the Oracle
jdbc driver. You have to install all of them on your own in your own
repo. So why not do the same with fop:fop?
Just my 2 € cents ;-)
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
(1) I cannot take care of in my application since I don't know where to
get the dependencies from. The idea behind Maven and Class-Path is that
the user doesn't need to care about.
(2) Why not just correcting the Class-Path in the JAR or the pom.xml? As
you put the the project in the project, you are responsible for doing it
correctly. What sense does it make to have jar and pom.xml found in the
repo that in fact are not in sync and cannot be used at all?
Markus
Carlos Sanchez schrieb:
> We don't build the jars, we just put them in the repo. If they build
> agains a jar that being the same has a different name we can't do
> anything about it. You are the one that in your application have to
> take care of it.
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Carlos Sanchez <ca...@apache.org>.
We don't build the jars, we just put them in the repo. If they build
agains a jar that being the same has a different name we can't do
anything about it. You are the one that in your application have to
take care of it.
On 9/19/06, Markus KARG <ka...@quipsy.de> wrote:
> Carlos,
>
> actually the repo MUST be changes since the jar IS WRONG.
>
> So if there is no maintainer and no JIRA: WHOM TO TELL ABOUT THE BUG NOW ?
>
> Markus
>
> Carlos Sanchez schrieb:
>
> > I don't think the repo needs to be changed to meet your requirements.
> > And it's a collective effort, there's no mantainer.
> >
> > On 9/19/06, Markus KARG <ka...@quipsy.de> wrote:
> >
> >> I need to find out the maintainer of the fop:fop project on
> >> repo1.maven.org.
> >> There is a severe bug in the published JAR that prevents referencing
> >> this project from own projects.
> >>
> >> Please either fix the bug or tell me the name of the maintainer so I can
> >> ask him to fix it!
> >>
> >> As there is no JIRA group for that project, I also cannot file a JIRA
> >> issue.
> >>
> >> It's all about the fop plugin (groupId: fop, artifactId: fop). The
> >> current version is 0.20.5. That version's pom.xml found on
> >> repo1.maven.org contains a dependency on "xml-apis-1.0.b2.jar"
> >> (xml-apis, version 1.0.b2), which should result in "Class-Path:
> >> xml-apis-1.0.b2.jar" to be written in the main artifact
> >> "fop-0.20.5.jar".
> >> Actually the "fop-0.20.5.jar" found on repo1.maven.org doesn't contain
> >> "Class-Path: xml-apis-1.0.b2.jar" but "Class-Path: xml-apis.jar" which
> >> results in a class path resolving problem at run time in any project
> >> using FOP 0.20.5!
> >>
> >> The same problem not only happens with "xml-apis" but with nearly ALL
> >> dependencies of fop-0.20.5 (e. g. also with "batik")!
> >>
> >> This has to be fixed ASAP to make those projects work!
> >> The fix is quite easy, just modify the Class-Path: entry or do "mvn
> >> clean deploy" to push another copy to repo1.maven.org.
> >>
> >> The problem is really urgent since we need this and we do not have write
> >> access to that folder on of repo1.maven.org.
> >>
> >> Thanks
> >> Markus
> >>
> >>
> >>
> >
> >
>
>
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Markus KARG <ka...@quipsy.de>.
Carlos,
actually the repo MUST be changes since the jar IS WRONG.
So if there is no maintainer and no JIRA: WHOM TO TELL ABOUT THE BUG NOW ?
Markus
Carlos Sanchez schrieb:
> I don't think the repo needs to be changed to meet your requirements.
> And it's a collective effort, there's no mantainer.
>
> On 9/19/06, Markus KARG <ka...@quipsy.de> wrote:
>
>> I need to find out the maintainer of the fop:fop project on
>> repo1.maven.org.
>> There is a severe bug in the published JAR that prevents referencing
>> this project from own projects.
>>
>> Please either fix the bug or tell me the name of the maintainer so I can
>> ask him to fix it!
>>
>> As there is no JIRA group for that project, I also cannot file a JIRA
>> issue.
>>
>> It's all about the fop plugin (groupId: fop, artifactId: fop). The
>> current version is 0.20.5. That version's pom.xml found on
>> repo1.maven.org contains a dependency on "xml-apis-1.0.b2.jar"
>> (xml-apis, version 1.0.b2), which should result in "Class-Path:
>> xml-apis-1.0.b2.jar" to be written in the main artifact
>> "fop-0.20.5.jar".
>> Actually the "fop-0.20.5.jar" found on repo1.maven.org doesn't contain
>> "Class-Path: xml-apis-1.0.b2.jar" but "Class-Path: xml-apis.jar" which
>> results in a class path resolving problem at run time in any project
>> using FOP 0.20.5!
>>
>> The same problem not only happens with "xml-apis" but with nearly ALL
>> dependencies of fop-0.20.5 (e. g. also with "batik")!
>>
>> This has to be fixed ASAP to make those projects work!
>> The fix is quite easy, just modify the Class-Path: entry or do "mvn
>> clean deploy" to push another copy to repo1.maven.org.
>>
>> The problem is really urgent since we need this and we do not have write
>> access to that folder on of repo1.maven.org.
>>
>> Thanks
>> Markus
>>
>>
>>
>
>
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Posted by Carlos Sanchez <ca...@apache.org>.
I don't think the repo needs to be changed to meet your requirements.
And it's a collective effort, there's no mantainer.
On 9/19/06, Markus KARG <ka...@quipsy.de> wrote:
> I need to find out the maintainer of the fop:fop project on repo1.maven.org.
> There is a severe bug in the published JAR that prevents referencing
> this project from own projects.
>
> Please either fix the bug or tell me the name of the maintainer so I can
> ask him to fix it!
>
> As there is no JIRA group for that project, I also cannot file a JIRA issue.
>
> It's all about the fop plugin (groupId: fop, artifactId: fop). The
> current version is 0.20.5. That version's pom.xml found on
> repo1.maven.org contains a dependency on "xml-apis-1.0.b2.jar"
> (xml-apis, version 1.0.b2), which should result in "Class-Path:
> xml-apis-1.0.b2.jar" to be written in the main artifact "fop-0.20.5.jar".
> Actually the "fop-0.20.5.jar" found on repo1.maven.org doesn't contain
> "Class-Path: xml-apis-1.0.b2.jar" but "Class-Path: xml-apis.jar" which
> results in a class path resolving problem at run time in any project
> using FOP 0.20.5!
>
> The same problem not only happens with "xml-apis" but with nearly ALL
> dependencies of fop-0.20.5 (e. g. also with "batik")!
>
> This has to be fixed ASAP to make those projects work!
> The fix is quite easy, just modify the Class-Path: entry or do "mvn
> clean deploy" to push another copy to repo1.maven.org.
>
> The problem is really urgent since we need this and we do not have write
> access to that folder on of repo1.maven.org.
>
> Thanks
> Markus
>
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org