commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michael Heuer <>
Subject Re: [PARENT] release of pom packaging project fails jar plugin
Date Wed, 25 Apr 2012 16:54:17 GMT
On Wed, Apr 25, 2012 at 4:03 AM, sebb <> wrote:
> On 25 April 2012 07:48, Jörg Schaible <> 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.

I checked the newer documentation referenced in this thread

and found this:

For Commons Parent, you can do:

$ mvn clean gpg:sign deploy -Ptest-deploy

I didn't see any explicit documentation about the actual release of
Parent to the Nexus staging directory, so I assume it is just

$ mvn gpg:sign deploy


>> - 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?
>> vfs is a multi-project

If I run

$ mvn clean deploy -Prelease -Ptest-deploy

on a fresh checkout of commons-vfs2-project it fails with

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] Commons VFS ....................................... FAILURE [1:20.632s]
[INFO] Commons VFS Core .................................. SKIPPED
[INFO] Commons VFS Examples .............................. SKIPPED
[INFO] Commons VFS Distribution .......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:23.425s
[INFO] Finished at: Wed Apr 25 11:48:18 CDT 2012
[INFO] Final Memory: 15M/81M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-assembly-plugin:2.2.1:single (default)
on project commons-vfs2-project: Error reading assemblies: No assembly
descriptors found. -> [Help 1]


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message