You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Michael Heuer <he...@gmail.com> on 2012/04/24 18:27:09 UTC
[PARENT] release of pom packaging project fails jar plugin
Hello,
I'm forwarding this message originally sent to users@maven that
received no response. Perhaps dev@commons is more appropriate.
---------- Forwarded message ----------
To: users@maven.apache.org
Hello,
We have adapted the Commons parent pom (and by extension the Apache
parent pom) with some changes for our internal parent pom. We are
running into an issue with a combination of maven release plugin +
maven bundle plugin + maven jar plugin for pom packaging projects. Is
this the right mailing list for this question?
E.g.
$ mvn -Prelease install
[INFO] ------------------------------------------------------------------------
[INFO] Building parent 1-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-bundle-plugin:2.3.7:manifest (bundle-manifest) @ parent ---
[WARNING] Ignoring project type pom - supportedProjectTypes = [jar, bundle]
[INFO]
[INFO] >>> maven-source-plugin:2.1.2:jar (create-source-jar) @ parent >>>
[INFO]
[INFO] <<< maven-source-plugin:2.1.2:jar (create-source-jar) @ parent <<<
[INFO]
[INFO] --- maven-source-plugin:2.1.2:jar (create-source-jar) @ parent ---
[INFO]
[INFO] >>> maven-source-plugin:2.1.2:test-jar (create-source-jar) @ parent >>>
[INFO]
[INFO] <<< maven-source-plugin:2.1.2:test-jar (create-source-jar) @ parent <<<
[INFO]
[INFO] --- maven-source-plugin:2.1.2:test-jar (create-source-jar) @ parent ---
[INFO]
[INFO] --- maven-jar-plugin:2.4:test-jar (default) @ parent ---
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:2.4:test-jar (default) on
project parent: Error assembling JAR: Manifest file:
/xxx/parent/target/osgi/MANIFEST.MF does not exist. -> [Help 1]
First, source and test jars shouldn't be created for a pom packaging
project, and second, the jar plugin shouldn't fail if the manifest
generated by the bundle plugin isn't present.
michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by sebb <se...@gmail.com>.
On 25 April 2012 14:08, Jörg Schaible <Jo...@scalaris.com> wrote:
> sebb wrote:
>
>> On 25 April 2012 11:18, Jörg Schaible <Jo...@scalaris.com> wrote:
>>> Hi Sebb,
>>>
>>> sebb wrote:
>>>
>>>> On 25 April 2012 07:48, Jörg Schaible <Jo...@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 ... ;-)
>>
>> I don't use the release plugin, because I don't like the way it messes
>> with trunk.
>
> You mean the two commits for the "final" POM and its immediate update?
>
>> I prefer to create the tag from clean trunk checkout + version updates.
>> Much safer that way.
>
> The plugin takes care for all the version updates ... seems we have
> different preferences here :)
The advantage of the manual method is that there is no need to revert
trunk if the RC fails.
The SVN commit messages are also cleaner IMO.
> [snip]
>
> - Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by Jörg Schaible <Jo...@scalaris.com>.
sebb wrote:
> On 25 April 2012 11:18, Jörg Schaible <Jo...@scalaris.com> wrote:
>> Hi Sebb,
>>
>> sebb wrote:
>>
>>> On 25 April 2012 07:48, Jörg Schaible <Jo...@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 ... ;-)
>
> I don't use the release plugin, because I don't like the way it messes
> with trunk.
You mean the two commits for the "final" POM and its immediate update?
> I prefer to create the tag from clean trunk checkout + version updates.
> Much safer that way.
The plugin takes care for all the version updates ... seems we have
different preferences here :)
[snip]
- Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by sebb <se...@gmail.com>.
On 25 April 2012 11:18, Jörg Schaible <Jo...@scalaris.com> wrote:
> Hi Sebb,
>
> sebb wrote:
>
>> On 25 April 2012 07:48, Jörg Schaible <Jo...@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 ... ;-)
I don't use the release plugin, because I don't like the way it messes
with trunk.
I prefer to create the tag from clean trunk checkout + version updates.
Much safer that way.
>> 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
Yes.
> Cheers,
> Jörg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by Jörg Schaible <Jo...@scalaris.com>.
Hi Sebb,
sebb wrote:
> On 25 April 2012 07:48, Jörg Schaible <Jo...@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
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by Michael Heuer <he...@gmail.com>.
On Wed, Apr 25, 2012 at 11:57 AM, sebb <se...@gmail.com> wrote:
> On 25 April 2012 17:54, Michael Heuer <he...@gmail.com> wrote:
>> On Wed, Apr 25, 2012 at 4:03 AM, sebb <se...@gmail.com> wrote:
>>> On 25 April 2012 07:48, Jörg Schaible <Jo...@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.
>>
>> I checked the newer documentation referenced in this thread
>>
>> http://wiki.apache.org/commons/UsingNexus
>> http://www.apache.org/dev/publishing-maven-artifacts.html
>>
>> 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
>>
>
> Yes
>
>>
>>
>>>> - 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
>>
>> 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]
>> [INFO] Commons VFS ....................................... FAILURE [1:20.632s]
>> [INFO] Commons VFS Core .................................. SKIPPED
>> [INFO] Commons VFS Examples .............................. SKIPPED
>> [INFO] Commons VFS Distribution .......................... SKIPPED
>> [INFO] ------------------------------------------------------------------------
>> [INFO] BUILD FAILURE
>> [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]
>
> As the error message says - there are no assembly descriptors for the
> parent POM.
Right, if I provide an assembly descriptor on the command line, the
local deploy works fine.
I found this in commons-vfs2-project/pom.xml, which addresses the
original problem I reported (jar plugin fails due to missing osgi
manifest for pom packaging project)
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-antrun-plugin</artifactId>
<executions>
<execution>
<id>vfs-jar-manifest</id>
<phase>generate-sources</phase>
<goals>
<goal>run</goal>
</goals>
<configuration>
<target>
<mkdir dir="${project.build.directory}/osgi" />
<touch file="${project.build.directory}/osgi/MANIFEST.MF" />
</target>
</configuration>
</execution>
michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by sebb <se...@gmail.com>.
On 25 April 2012 17:54, Michael Heuer <he...@gmail.com> wrote:
> On Wed, Apr 25, 2012 at 4:03 AM, sebb <se...@gmail.com> wrote:
>> On 25 April 2012 07:48, Jörg Schaible <Jo...@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.
>
> I checked the newer documentation referenced in this thread
>
> http://wiki.apache.org/commons/UsingNexus
> http://www.apache.org/dev/publishing-maven-artifacts.html
>
> 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
>
Yes
>
>
>>> - 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
>
> 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]
> [INFO] Commons VFS ....................................... FAILURE [1:20.632s]
> [INFO] Commons VFS Core .................................. SKIPPED
> [INFO] Commons VFS Examples .............................. SKIPPED
> [INFO] Commons VFS Distribution .......................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [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]
As the error message says - there are no assembly descriptors for the
parent POM.
> michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by Ralph Goers <rg...@apache.org>.
For testing I've run mvn -P release clean install. The deploy happens when I use the prepare and perform goals of the release plugin.
Ralph
Sent from my iPad
On Apr 25, 2012, at 9:54 AM, Michael Heuer <he...@gmail.com> wrote:
> On Wed, Apr 25, 2012 at 4:03 AM, sebb <se...@gmail.com> wrote:
>> On 25 April 2012 07:48, Jörg Schaible <Jo...@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.
>
> I checked the newer documentation referenced in this thread
>
> http://wiki.apache.org/commons/UsingNexus
> http://www.apache.org/dev/publishing-maven-artifacts.html
>
> 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?
>>>
>>> http://wiki.apache.org/commons/CreatingReleases
>>>
>>> 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]
> [INFO] Commons VFS ....................................... FAILURE [1:20.632s]
> [INFO] Commons VFS Core .................................. SKIPPED
> [INFO] Commons VFS Examples .............................. SKIPPED
> [INFO] Commons VFS Distribution .......................... SKIPPED
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD FAILURE
> [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]
>
> michael
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by Michael Heuer <he...@gmail.com>.
On Wed, Apr 25, 2012 at 4:03 AM, sebb <se...@gmail.com> wrote:
> On 25 April 2012 07:48, Jörg Schaible <Jo...@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.
I checked the newer documentation referenced in this thread
http://wiki.apache.org/commons/UsingNexus
http://www.apache.org/dev/publishing-maven-artifacts.html
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?
>>
>> http://wiki.apache.org/commons/CreatingReleases
>>
>> 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]
[INFO] Commons VFS ....................................... FAILURE [1:20.632s]
[INFO] Commons VFS Core .................................. SKIPPED
[INFO] Commons VFS Examples .............................. SKIPPED
[INFO] Commons VFS Distribution .......................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[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]
michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by Gary Gregory <ga...@gmail.com>.
On Apr 25, 2012, at 6:19, "Jörg Schaible" <Jo...@scalaris.com> wrote:
> Hi Sebb,
>
> sebb wrote:
>
>> On 25 April 2012 07:48, Jörg Schaible <Jo...@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?
No, I use http://wiki.apache.org/commons/UsingNexus
Gary
>
> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by sebb <se...@gmail.com>.
On 25 April 2012 07:48, Jörg Schaible <Jo...@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-unsubscribe@commons.apache.org
> For additional commands, e-mail: dev-help@commons.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by Jörg Schaible <Jo...@scalaris.com>.
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
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by Michael Heuer <he...@gmail.com>.
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)? Are any
of the commons projects currently multimodule builds?
michael
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org
Re: [PARENT] release of pom packaging project fails jar plugin
Posted by Jörg Schaible <jo...@gmx.de>.
Hi Michael,
Michael Heuer wrote:
> Hello,
>
> 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.
Regards,
Jörg
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org