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 06:48:03 GMT
Michael Heuer wrote:

> Jörg Schaible wrote:
>> Michael Heuer wrote:
>>
>>> I'm forwarding this message originally sent to users@maven that
>>> received no response.  Perhaps dev@commons is more appropriate.
>>
>> why do you think, that extending from Apache Commons parent is a good
>> thing? This parent is crafted so that it fits exactly our (Apache
>> Commons) needs. It is considered internal and is not designed to work for
>> all cases (especially outside its environment).
>>
>> Said that, if you provide patches for this POM that have no side-effects
>> for all our components, we might consider to apply them, but don't expect
>> that someone is maintaining/developing this parent POM like any other
>> Commons component.
>>
>> IMHO, you're better off if you copy the interesting parts into a shared
>> parent of your own.
> 
> Thank you for the response, Jörg.
> 
> That is what I have done, copy the interesting bits from the commons
> and Apache parents into our internal parent.  We're not extending from
> either.
> 
> I'm not seeing how the commons parent with its release profiles can
> work for pom packaging projects (such as the parent project or
> multimodule projects).  When commons-parent is released, are none of
> the release profiles enabled (rc, release, apache-release)?

- rc: the one we use
- release: automatically activated by M2 (IIRC)
- apache-release: outdated?

> Are any
> of the commons projects currently multimodule builds?

http://wiki.apache.org/commons/CreatingReleases

vfs is a multi-project

- 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