commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Schaible <Joerg.Schai...@scalaris.com>
Subject Re: [PARENT] release of pom packaging project fails jar plugin
Date Wed, 25 Apr 2012 10:18:45 GMT
Hi Sebb,

sebb wrote:

> On 25 April 2012 07:48, Jörg Schaible <Joerg.Schaible@scalaris.com> wrote:

[snip]

>> - rc: the one we use
> 
> That was the one we used for creating RCs prior to Nexus.
> 
>> - release: automatically activated by M2 (IIRC)
> 
> This is the one I normally use.
> 
> I think rc and release are fairly similar.

Well, the profile "release" is activated by the plugin as default, see 
(default) configuration of the release plugin. As long as no-one overwrites 
the setting ... ;-)

> However, I'm not sure either can be used for releasing the parent POM.

"release" (resp. the configured ones) should be active nevertheless, you may 
add more using -P option.

>> - apache-release: outdated?
> 
> This is the one in the ASF pom; IIRC it clashes with our requirements.

OK.

>>> Are any
>>> of the commons projects currently multimodule builds?
>>
>> http://wiki.apache.org/commons/CreatingReleases

We should finalize it. Gary, did you follow now that steps?

And we must update or drop http://commons.apache.org/releases/index.html

Cheers,
Jörg


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


Mime
View raw message