On 4/1/08, Bruno Lowagie <[EMAIL PROTECTED]> wrote: > Daniele Dellafiore wrote: > > Hi. > > > > iText > 2.0.6 depends upon: > > > > <dependency> > > <groupId>bouncycastle</groupId> > > <artifactId>bcmail-jdk14</artifactId> > > <version>138</version> > > </dependency> > > > Yes. We are using version 138 of the BC jars. > Honestly: we are!
that's good, this is one of the benefit of maven 2. > > > and another package that is not available from maven2 main repository > > so the maven task cannot execute properly, eclipse plugin is generated > > with errors and so on. > > > Why are you posting this here and not on the BC mailing list? > This is off-topic on the iText mailing list. I am used to use maven 2 too and I maintain the build that for me means that I upload on a public repo artifacts that I use for my project and that are not in maven repo. I am sorry but I simply disagree with you here: No one never ever asked BC developer to use maven and no one never asked you to use BC. You, iText developer, are using both maven and BC so it is your responsibility to keep everything working, If you think that this is not the case, that's ok for me but keep in mind that from 2.0.7 on, iText maven distribution is *broken*, so it is your problem, not BC. Why the BC developer should in any way care about maven? Just because a project that depend on them is using this? I can *for sure* ask BC guys to upload the artifact, and you can too of course, but this is of no relevance on the matter here. > We build the Maven bundle using scripts. Our POM template > doesn't even contain the Maven version, just a placeholder > that is replaced automatically with the BC version we are using. > > We do an effort to upload this maven bundle; we make sure the > latest iText version is available on Maven. We do this because > people using maven 'demand' this. But it stops there. > Maybe you are the anonymous person who posted a link to > "how to ask for an artifact to be uploaded to central maven repo" > on the following page: > > https://sourceforge.net/tracker/?func=detail&atid=115255&aid=1897290&group_id=15255 yes... I thought I were logged in sf... > We KNOW how to upload an artifact to maven. HOW ELSE would the > latest version of iText be present in the maven repo??? my message is for the guy who asked for the fix and you said: "ask the other guys" like you are doing with me now. I point that out for him cause you didn't. > But > we are NOT going to change our POM manually and we are NOT going > to move back 2 BC versions. IT IS NOT OUR JOB TO DO SO. > We did our part of the job. It's up to others to do their part. > > We don't use maven; actually I've followed a three day course on > maven, tried it in some projects and decided it brought more pain > than pleasure. Many people may disagree with me, but what I don't > like is people saying we don't listen to the demands of users. > > We provided the maven bundle as a favor. If you don't like that; > don't complain and MOST CERTAINLY: please don't blame us for > problems that aren't ours. > > I fail to see where "sender: nobody" found the audacity to post > a link to explain us how to upload an artifact. If he really needs > the latest BC version in maven, can't he upload it himself??? > Why should we do it. I can only repeat: we do our part of the job!!! > > best regards, > Bruno Hey, Bruno, not a nice day? I am sorry but, why all this mess? This is an open source project, we can say that everything here is a favor so why are you so angry about the matter? It is open source, a nice answer is: "hey, I know, but I do not like maven that much, why do not you just help this out if you really care?" I can and I will, not a problem at all, but the way you discuss about the matter is disappointing. But, and this is important, I will not eventually fix this maven problem "by myself as a user", I am doing this as a contribute to an open source project cause I think that this OS project have an issue with maven. Like it or not, if you provide a maven package, and it *is* buggy, this is an issue. Do not want to fix? No problem AT ALL Bruno, I will do what I can to help cause it is open source and iText is great but, come on, do not get upset just cause I pointed the issue out. This said, I think that the official repo policy is really, really complicated but anyway, I will try to make something for this problem. -- Daniele Dellafiore http://blog.ildella.net/ ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ iText-questions mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/itext-questions Do you like iText? Buy the iText book: http://www.1t3xt.com/docs/book.php Or leave a tip: https://tipit.to/itexttipjar
