Re: Publish artifacts to Maven central

I am afraid you have to run once for each version. One way is to add one
maven pom file for the project and one profile for each version. The real
work can be delegated to existing ant job via maven ant plugin.

__________________________

Shijun Kong

On 10/30/12 11:53 AM, "Stephen Nelson" <stephen(at)eccostudio(dot)com> wrote:

>On Fri, Oct 26, 2012 at 7:54 AM, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
>wrote:
>> It really would. I've had it on my to-do for ages, but I haven't done
>> much with Ant and I was concerned about getting the build right for the
>> different versions.
>>
>
>Yeah, I finding that to be the slightly more involved part. To get
>accepted to Maven Central I think you need to supply a jar with
>javadoc and one with the sources. Looking at the current build there's
>different source code included depending on the JDBC version you're
>building for.
>
>The question I have is should this current build script handle the
>building of both versions, or will the script itself be called twice -
>once for each JDBC version? It could be done either way I think, but I
>guess this will need to hook into the other automated build discussion
>happening on another thread so that things work together.
>
>> --
>> Craig Ringer
>>
>>
>
>--
>Stephen Nelson
>
>
>--
>Sent via pgsql-jdbc mailing list (pgsql-jdbc(at)postgresql(dot)org)
>To make changes to your subscription:
>http://www.postgresql.org/mailpref/pgsql-jdbc

This email message and any attachments may contain legally privileged or confidential information intended solely for the use of the individual or entity to whom it is addressed. If the reader of this message is not the intended recipient, you are hereby notified that any reading, dissemination, distribution or copying of this message or its attachments is strictly prohibited. If you have received this message in error, please notify us immediately by telephone, fax or email and delete the message and all attachments to the message. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Investor Analytics LLC.