james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefano Bagnara <apa...@bago.org>
Subject Re: Release james-project 1.3 pom?
Date Sat, 08 Nov 2008 20:22:51 GMT
Robert Burrell Donkin ha scritto:
> On Sat, Nov 8, 2008 at 6:12 PM, Stefano Bagnara <apache@bago.org> wrote:
>> Robert Burrell Donkin ha scritto:
>>> currently, the mailet projects poms inherit:
>>>   <parent>
>>>     <groupId>org.apache.james</groupId>
>>>     <artifactId>james-project</artifactId>
>>>     <version>1.3-SNAPSHOT</version>
>>>     <relativePath>../james-project/project/pom.xml</relativePath>
>>>   </parent>
>>> this pom seems to be unreleased. i think this means we need to release
>>> it before we can cut releases for the mailets etc.
>>> is there any more work needed before james-project 1.3 pom can be released?
>>> -robert
>> We usually released parent poms as part of the project needing them.
>> IMHO there's no need to VOTE for a pom alone.
>> If it is working for the release of mailets then it is ok and it will be
>> released as 1.3 when we release mailet-api. If we need something more we
>> can release 1.4 in the next release that will need changes.
> ok
> i think that this means i need to:
> 1. update the pom version numbers in
> http://svn.apache.org/repos/asf/james/project/
> 2. tag into http://svn.apache.org/repos/asf/james/project/tags/
> 3. update the mailet-api pom.
> then cut the mailet API release
> is this correct?

Yes. If you use the maven release plugin it will do everything you need.
Otherwise also remember to put the -site.xml and pom files, md5 and
signatures in

I don't know how to update the maven-metadata.xml if not using the maven
deploy plugin.


To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message