Hello Cameron, I am a user of Batik that uses Maven2. Please let me know how I might help...
I am still using the 1.6 poms in my project, listed individually because the transitive dependencies are broken in those versions: http://dishevelled.svn.sourceforge.net/viewvc/dishevelled/trunk/iconbundle/pom.xml The 1.6-1 versions uploaded in an attempt to fix the problem are not much better -- they pull in an incredible list of (what seem to be) unnecessary dependencies, such that the list of exclusions turns out to be longer than the original list of dependencies. michael Cameron McCormack wrote: > Hi Carlos. > > Carlos Sanchez: > > The best person that will help you is a user of Batik that uses Maven, Lars? > > see some comments inline > > Cameron McCormack: > > > First, should I keep the groupId as "batik"? It seems inconsistent with > > > those for FOP and Commons, which are using "org.apache.xmlgraphics". > > > Would it be problematic to change this? > > > > not too problematic, just a bit annoying for some users, but it should > > be done at some point > > groupId should probably be org.apache.xmlgraphics.batik > > OK. Does that mean the groupId for FOP and XML Graphics Commons is > wrong? (It says <groupId>org.apache.xmlgraphics</groupId> in the POM > file for both.) > > > > Second, how do I deal with the issue of the mutual dependency between > > > FOP and Batik? The Batik 1.7 release will depend on Fop 0.93, but in > > > http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/xmlgraphics/fop/0.93/fop-0.93.pom > > > it says that FOP 0.93 depends on the 1.6-1 versions of the various Batik > > > artifacts. Is that what the <exclusions> element in the POM file is > > > used for? > > > > is it a real dependency or it's just that the fop pom is messed up? > > yes, you can depend in fop and add an exclusion for batik there > > It is a real dependency. In fact FOP can work with Batik 1.7, since > we???ve maintained compatibility, but I suppose the dependency on the > exact 1.6-1 version prevents this from working nicely. I???ll do as you > say then and have an exclusion to prevent Batik 1.6-1 from coming in. > > > > Third, since Batik relies on a patched version of Rhino, I won't be able > > > to add a dependency on js-1.6R5.jar artifact. Do I need to create a > > > special artifact that contains the patched Rhino, e.g. a > > > batik-js-1.7.jar? > > > > or you could put a js-1.6R5patched.jar under > > org.apache.xmlgraphics.batik group with its own pom. Make sure in the > > description you state clearly that it's a patched version to avoid > > confusion > > OK cool. > > > > > > > Fourth, once the release has been made, does the release manager just > > > upload the artifacts to > > > http://people.apache.org/repo/m2-ibiblio-rsync-repository/ themselves? > > > > if you don't use maven2 to build I'd put them in > > http://people.apache.org/repo/m1-ibiblio-rsync-repository/org.apache.xmlgraphics.batik > > /jars and /poms > > What???s the difference? Artifacts in the m1-??? directory can be used by > both Maven 1 and 2, but those in the m2-??? directory can only be used by > Maven 2? (/me is a bit clueless about the difference between Maven 1 > and 2). > > Thanks, > > Cameron > > -- > Cameron McCormack, http://mcc.id.au/ > xmpp:[EMAIL PROTECTED] ??? ICQ 26955922 ??? MSN [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
