You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repository@apache.org by Cameron McCormack <ca...@mcc.id.au> on 2007/12/04 05:10:47 UTC
Providing maven-metadata.xml files for Batik
My artifact and POM generation works well from my ant build file now.
This is what it generates:
http://mcc.id.au/temp/2007/maven/
When everything’s set, I’ll dump all of those batik-* directories in
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/xmlgraphics/.
Still a few questions to go, though.
First, do I need to upload maven-metadata.xml files for each of these
artifacts too? I notice that some projects have them (e.g.
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/james/james-project/maven-metadata.xml)
while others don’t (e.g. the file isn’t in
http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/xmlgraphics/fop/).
If I do need to provide such a file, where is there documentation on its
format? I couldn’t find any on http://maven.apache.org/.
Second, is there a minimum/maximum Java version that the artifacts must
be compiled with?
Third, should I do the relocation thing described in
http://maven.apache.org/guides/mini/guide-relocation.html? The old
Batik 1.6 artifacts are in http://repo1.maven.org/maven2/batik/, but
there’s no
http://people.apache.org/repo/m2-ibiblio-rsync-repository/batik/ since
these Batik 1.6 artifacts were uploaded by external people, presumably.
Should I create the m2-ibiblio-rsync-repository/batik directory so that
I can upload the minimal redirecting POMs for the old (and 1.7)
artifacts, or should I do that through a JIRA request to the maven
people?
Thanks again,
Cameron
--
Cameron McCormack, http://mcc.id.au/
xmpp:heycam@jabber.org ▪ ICQ 26955922 ▪ MSN cam@mcc.id.au
Re: Providing maven-metadata.xml files for Batik
Posted by Carlos Sanchez <ca...@apache.org>.
put it in the repo and let me know to copy to central. I will delete
it later after it's synced.
On Jan 9, 2008 11:47 AM, Cameron McCormack <ca...@mcc.id.au> wrote:
> Hi Carlos.
>
> Carlos Sanchez:
> > 1) not necessary, metadata is only required for version ranges
> > 2) not minimum jdk for maven, whatever the Batik project already does
> > 3) relocation is not required, although I would put a relocation pom
> > for the next version so users upgrading get a warning and dont
> > complain about "latest version is not in the repo"
>
> OK thanks, and well timed, since Batik has its release today. :)
> I've uploaded the artifacts to
> /repo/m2-ibiblio-rsync-repository/org/apache/xmlgraphics now. For the
> relcation POM, should I put that in the Apache repository, or send a
> JIRA request for someone to do this in repo1.maven.org?
>
> Thanks,
>
>
> Cameron
>
> --
> Cameron McCormack, http://mcc.id.au/
> xmpp:heycam@jabber.org ▪ ICQ 26955922 ▪ MSN cam@mcc.id.au
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
Re: Providing maven-metadata.xml files for Batik
Posted by Cameron McCormack <ca...@mcc.id.au>.
Hi Carlos.
Carlos Sanchez:
> 1) not necessary, metadata is only required for version ranges
> 2) not minimum jdk for maven, whatever the Batik project already does
> 3) relocation is not required, although I would put a relocation pom
> for the next version so users upgrading get a warning and dont
> complain about "latest version is not in the repo"
OK thanks, and well timed, since Batik has its release today. :)
I’ve uploaded the artifacts to
/repo/m2-ibiblio-rsync-repository/org/apache/xmlgraphics now. For the
relcation POM, should I put that in the Apache repository, or send a
JIRA request for someone to do this in repo1.maven.org?
Thanks,
Cameron
--
Cameron McCormack, http://mcc.id.au/
xmpp:heycam@jabber.org ▪ ICQ 26955922 ▪ MSN cam@mcc.id.au
Re: Providing maven-metadata.xml files for Batik
Posted by Carlos Sanchez <ca...@apache.org>.
1) not necessary, metadata is only required for version ranges
2) not minimum jdk for maven, whatever the Batik project already does
3) relocation is not required, although I would put a relocation pom
for the next version so users upgrading get a warning and dont
complain about "latest version is not in the repo"
On Dec 4, 2007 5:10 AM, Cameron McCormack <ca...@mcc.id.au> wrote:
> My artifact and POM generation works well from my ant build file now.
> This is what it generates:
>
> http://mcc.id.au/temp/2007/maven/
>
> When everything's set, I'll dump all of those batik-* directories in
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/xmlgraphics/.
>
> Still a few questions to go, though.
>
> First, do I need to upload maven-metadata.xml files for each of these
> artifacts too? I notice that some projects have them (e.g.
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/james/james-project/maven-metadata.xml)
> while others don't (e.g. the file isn't in
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/xmlgraphics/fop/).
> If I do need to provide such a file, where is there documentation on its
> format? I couldn't find any on http://maven.apache.org/.
>
> Second, is there a minimum/maximum Java version that the artifacts must
> be compiled with?
>
> Third, should I do the relocation thing described in
> http://maven.apache.org/guides/mini/guide-relocation.html? The old
> Batik 1.6 artifacts are in http://repo1.maven.org/maven2/batik/, but
> there's no
> http://people.apache.org/repo/m2-ibiblio-rsync-repository/batik/ since
> these Batik 1.6 artifacts were uploaded by external people, presumably.
> Should I create the m2-ibiblio-rsync-repository/batik directory so that
> I can upload the minimal redirecting POMs for the old (and 1.7)
> artifacts, or should I do that through a JIRA request to the maven
> people?
>
> Thanks again,
>
> Cameron
>
> --
> Cameron McCormack, http://mcc.id.au/
> xmpp:heycam@jabber.org ▪ ICQ 26955922 ▪ MSN cam@mcc.id.au
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride