On 25 April 2012 07:48, Jörg Schaible <joerg.schai...@scalaris.com> wrote:
> 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

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.

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

> - apache-release: outdated?

This is the one in the ASF pom; IIRC it clashes with our requirements.

>> 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-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

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

Reply via email to