Brian Fox wrote:
So here's the problem I found. The release plugin configuration that
activates the release profile during perform is in the release profile
itself. This means that you would need to do mvn release:peform
-Prelease in order for it to work. I can't tell if you used -Prelease
when you did the build or not, but this is the only way I can see that
things might have gone wrong.
That configuration block should be moved outside of the profile into the
regular plugin management section. (i haven't checked the release docs
yet as it's clear they will need to be updated regardless).
Specifically, move this:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-release-plugin</artifactId>
<configuration>
<useReleaseProfile>false</useReleaseProfile>
<goals>deploy</goals>
<arguments>-Prelease</arguments>
</configuration>
</plugin>
I'll now work on that script to fix the signatures, i'm sure this will
be generally useful over time.
Hi Brian,
I saw you already proposed to update the apache parent pom to incorporate all
the required release configuration.
Based on that, I think we better wait with fixing and releasing a new version of our portals-pom, as we then can simply remove our
configurations instead.
For now, I guess we can continue referencing our currently released portals-pom for upcoming (sub project) releases as long as we use mvn
release:perform -Prelease, right?
And for the missing signatures, we'll wait for your script to fix those.
Many thanks for helping out on all this.
Regards,
Ate
Ate Douma wrote:
Brian Fox wrote:
Hi Ate, Vkumar,
The switch from the old static repository to Nexus shouldn't have
affected any part of the release:prepare or release:perform process
performed by Maven other than the actual url used in the
distributionManagement. The only steps that change are _after_ the
artifacts are made and signed and deployed, where you would close and
then later promote the repository.
So the question is, did the portals project produce the signatures
for previous releases, and if so, how?
No.
The releases of these portals/portals-pom and portals/applications-pom
projects using Nexus were the first (1.0).
Therefore, we assumed (maybe incorrectly) that by following all the
guidelines of setting up these poms and the releasing steps as
indicated, the signing of the artifacts would now also be done more or
less "automatically".
AFAIK, we literally followed all instructions, and after again
reviewing our poms I can't find anything different or wrong from the
examples given.
The maven release document isn't intended to be a master document on
how to setup a project from scratch to generate everything
correctly...but perhaps that is what is needed for new projects. I'll
have to look at your poms to figure out what might be wrong.
If you coould do that, much appreciated.
Another pair of eyes might detect something obvious we simply overlooked.
Signing the artifacts after the fact is definately more complicated
since the system isn't setup for direct manipulation of the artifacts
by committers. It should be possible via a script to gen and upload
the signatures though, so I'll work that out.
OK, great. Please keep us posted.
Regards,
Ate
Ate Douma wrote:
Hi Brian, Wendy,
Just looked at the released poms and there are no gpg signatures
indeed.
What I'm surprised about is how those are not "automatically"
generated when following the Nexus release instructions as described
here:
http://maven.apache.org/developers/release/releasing.html
Vivek has been following those instructions to the letter (we've
actually went to those together as this is the first time Portals
used Nexus for a release) and AFAIK our poms have all the required
plugin configurations needed as described, including the "release"
profile and the maven-gpg-plugin configuration.
So, 3 questions:
- is something missing from the release instructions (see above)
- or did we forget/overlook an essential step (please indicate which
and where)
- what is the practical quick solution to provide the gpg signatures
"after the fact" (using Nexus)
Regards,
Ate
Brian Fox wrote:
I know I need to make emails, it's actually in 1.3.2 I just need to
find a good time to upgrade. You can see the staging and promotion
events here:
https://repository.apache.org/service/local/feeds/systemChanges
On Mon, Apr 13, 2009 at 8:44 PM, Brian Fox <[email protected]
<mailto:[email protected]>> wrote:
It was vkumar....
On Mon, Apr 13, 2009 at 8:09 PM, Wendy Smoak <[email protected]
<mailto:[email protected]>> wrote:
The portals poms are missing signatures, but I can't tell who
released
them. -Wendy
On Mon, Apr 13, 2009 at 5:00 PM, <[email protected]
<mailto:[email protected]>> wrote:
> Repository changed
> ==================
>
> Repository:
/export/home/nexus/nexus-professional/sonatype-work/nexus/storage/releases
>
> Added
> -----
> [nexus] /org/apache/portals
> [nexus] /org/apache/portals/portals-pom
> [nexus] /org/apache/portals/portals-pom/1.0
> [nexus]
/org/apache/portals/portals-pom/1.0/portals-pom-1.0.pom
> [nexus]
/org/apache/portals/portals-pom/1.0/portals-pom-1.0.pom.sha1
> [nexus]
/org/apache/portals/portals-pom/1.0/portals-pom-1.0.pom.md5
> [nexus] /org/apache/portals/portals-pom/maven-metadata.xml
> [nexus]
/org/apache/portals/portals-pom/maven-metadata.xml.md5
> [nexus]
/org/apache/portals/portals-pom/maven-metadata.xml.sha1
> [nexus] /org/apache/portals/applications-pom
> [nexus] /org/apache/portals/applications-pom/1.0
> [nexus]
/org/apache/portals/applications-pom/1.0/applications-pom-1.0.pom.md5
> [nexus]
/org/apache/portals/applications-pom/1.0/applications-pom-1.0.pom.sha1
> [nexus]
/org/apache/portals/applications-pom/1.0/applications-pom-1.0.pom
> [nexus]
/org/apache/portals/applications-pom/maven-metadata.xml.sha1
> [nexus]
/org/apache/portals/applications-pom/maven-metadata.xml
> [nexus]
/org/apache/portals/applications-pom/maven-metadata.xml.md5
...
