ok, that's a good point; we'll leave it at xmlgraphics-commons then; we can
reconsider whether we want to add a 'xmlgraphics-' prefix to batik and fop
when we are ready to transition to maven on the latter
On Tue, Feb 23, 2016 at 11:27 AM, Simon Steiner
wrote:
> Hi,
Hi,
http://central.maven.org/maven2/org/apache/xmlgraphics/xmlgraphics-commons/2.1/xmlgraphics-commons-2.1.pom
currently its "xmlgraphics-commons"
someone upgrading shouldn’t have to change artifact id in their config.
Thanks
-Original Message-
From: Glenn Adams
I guess I could also go for this:
- xmlgraphics-commons
- batik
- fop
However, I like consistency more so I prefer the other way.
Like Glenn, I think that 'commons-xmlgraphics' makes it more like it's from of
the commons.apache.org team.
That said, I don't have a lot of energy here, so I'm
Hi folks,
I'm thinking it'd be best to have consistency and use the prefix
'xmlgraphics-' for all project JAR files:
- xmlgraphics-commons
- xmlgraphics-batik
- xmlgraphics-fop
I don't have a lot of energy behind this, but I do like consistency.
IOW, I'm +0 for the naming convention and +1
Hi Glenn,
I just checked some other Apache projects that use maven. Here is a
short list of their artifactIds:
Jackrabbit:
* jackrabbit-api
* jackrabbit-jcr-commons
* jackrabbit-core
etc.
Apache Commons:
* commons-codec
* commons-fileupload
etc.
PDFBox:
* pdfbox
* fontbox
* jempbox
etc.
If we
Hi Glenn,
Your original proposal made sense to me, and is in keeping with Maven
conventions. However, Matthias does have a point about commons artifact
getting mixed up with the commons project. Although the groupId should
help when working in a pure Maven environment.
On 22/02/2016 21:37,
Hi,
+1
great job, Glenn
2016-02-21 8:00 GMT+01:00 Glenn Adams :
> I would like to start a vote on merging
> from xmlgraphics/commons/branches/maven to trunk. Please respond by
> Wednesday, 02/24, 1700Z. Lack of a response will be interpreted as +0.
>
> In addition to adding a