You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Michael O'Cleirigh (JIRA)" <ji...@apache.org> on 2010/12/31 22:31:45 UTC
[jira] Created: (WICKET-3294) Use Apache Nexus to stage releases
for voting and for release into maven central
Use Apache Nexus to stage releases for voting and for release into maven central
--------------------------------------------------------------------------------
Key: WICKET-3294
URL: https://issues.apache.org/jira/browse/WICKET-3294
Project: Wicket
Issue Type: Improvement
Components: site, wicket
Reporter: Michael O'Cleirigh
This issue from June 2010 was about deploying the 1.4.x-SNAPSHOT and 1.5-SNAPSHOT releases into the Apache Nexus Maven Repository: https://issues.apache.org/jira/browse/WICKET-2918
This issue is about switching from the current release method to use the staging facilities provided through https://repository.apache.org
There is an issue with the metadata contained in the maven central repository being out of date that this issue will hopefully resolve as a side effect: https://issues.sonatype.org/browse/MVNCENTRAL-28
This is the apache documentation for publishing maven artifacts through repository.apache.org:
http://www.apache.org/dev/publishing-maven-artifacts.html
According to it that page the distribution management section in the parent org.apache:apache:8 pom contains the details for staging. So what needs to happen is that the parent pom.xml is upgraded from version 7 to version 8 and that the release profiles are adjusted so that only the <site> entry is contained in the distribution management sections.
There are some settings mentioned that need to go into the deployers local ~/.m2/settings.xml but I am assuming that it is going to be close to what is used for the current release process.
Then when the deploy part the release is run the jar, javadoc and source artifacts will be signed and uploaded into a staging repository. You login to the repository.apache.org page and on the left hand side you should be able to see a 'Staging Repository' link and clicking it will show a table listing the staged repositories.
The url associated with each staged repository doesn't work for reading until it has been closed. So if you encounter a bug in the deployment part you can fix it and continue with any old artifacts just overwriting what was previously uploaded. Then within the nexus interface you right click on the row (not on the url part) and select 'close' from the options.
Once closed the url can be used for the release vote. If the vote fails the staged repository can be dropped. If the vote succeeds then the staged repository can be promoted into a real release. At least in oss.sonatype.org within 1 hour of the promotion the artifact will be synced into the central maven repository.
It should be possible to test out this improvement ahead of the next release by just deploying into a staged repository and then dropping it if everything is added properly.
I will attach the modified /trunk/pom.xml and /branches/wicket-1.4.x/pom.xml versions that should let this work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3294) Use Apache Nexus to stage releases
for voting and for release into maven central
Posted by "Michael O'Cleirigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael O'Cleirigh updated WICKET-3294:
---------------------------------------
Attachment: release.md-2.diff
Attached a new draft of the release documentation (release.m2-2.diff).
This version includes details on how the ~/.m2/settings should be configured to enable the upload permission when running mvn -Prelease deploy (which is called within the release.sh script).
> Use Apache Nexus to stage releases for voting and for release into maven central
> --------------------------------------------------------------------------------
>
> Key: WICKET-3294
> URL: https://issues.apache.org/jira/browse/WICKET-3294
> Project: Wicket
> Issue Type: Improvement
> Components: site, wicket
> Reporter: Michael O'Cleirigh
> Attachments: release.md-2.diff, release.md.diff, wicket-1.4.x-pom.xml.diff, wicket-1.5.x-pom.xml.diff
>
>
> This issue from June 2010 was about deploying the 1.4.x-SNAPSHOT and 1.5-SNAPSHOT releases into the Apache Nexus Maven Repository: https://issues.apache.org/jira/browse/WICKET-2918
> This issue is about switching from the current release method to use the staging facilities provided through https://repository.apache.org
> There is an issue with the metadata contained in the maven central repository being out of date that this issue will hopefully resolve as a side effect: https://issues.sonatype.org/browse/MVNCENTRAL-28
> This is the apache documentation for publishing maven artifacts through repository.apache.org:
> http://www.apache.org/dev/publishing-maven-artifacts.html
> According to it that page the distribution management section in the parent org.apache:apache:8 pom contains the details for staging. So what needs to happen is that the parent pom.xml is upgraded from version 7 to version 8 and that the release profiles are adjusted so that only the <site> entry is contained in the distribution management sections.
> There are some settings mentioned that need to go into the deployers local ~/.m2/settings.xml but I am assuming that it is going to be close to what is used for the current release process.
> Then when the deploy part the release is run the jar, javadoc and source artifacts will be signed and uploaded into a staging repository. You login to the repository.apache.org page and on the left hand side you should be able to see a 'Staging Repository' link and clicking it will show a table listing the staged repositories.
> The url associated with each staged repository doesn't work for reading until it has been closed. So if you encounter a bug in the deployment part you can fix it and continue with any old artifacts just overwriting what was previously uploaded. Then within the nexus interface you right click on the row (not on the url part) and select 'close' from the options.
> Once closed the url can be used for the release vote. If the vote fails the staged repository can be dropped. If the vote succeeds then the staged repository can be promoted into a real release. At least in oss.sonatype.org within 1 hour of the promotion the artifact will be synced into the central maven repository.
> It should be possible to test out this improvement ahead of the next release by just deploying into a staged repository and then dropping it if everything is added properly.
> I will attach the modified /trunk/pom.xml and /branches/wicket-1.4.x/pom.xml versions that should let this work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3294) Use Apache Nexus to stage releases
for voting and for release into maven central
Posted by "Michael O'Cleirigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael O'Cleirigh updated WICKET-3294:
---------------------------------------
Attachment: wicket-1.5.x-pom.xml.diff
wicket-1.4.x-pom.xml.diff
I checked out from svn the latest version for 1.4-SNAPSHOT and 1.5-SNAPSHOT. Then I made the modifications reflected in the attached diff's and then used the maven versions plugin like this to switch my working copy into a release version number:
mvn versions:set -DnewVersion=1.4.16
mvn versions:set -DnewVersion=1.5
Then I ran mvn -Prelease deploy and while I don't have access to write the repository being used was correct and the artifact signing looked correct aswell. I'm not sure how the release.sh scripts interact with the deployment process but I think if the pom's are modified as indicated in these diffs it will work to create the staging repository. The parent pom defines the release and snapshot repositories but not the site. If the <site> is not being used then I would recommend taking out the entire section from the release profile.
I reverted the version and created the diff's attached. Here is the output I see when building 1.5:
[INFO] Wicket Quickstart Archetype
[INFO] ------------------------------------------------------------------------
[INFO] Building Wicket Parent
[INFO] task-segment: [deploy]
[INFO] ------------------------------------------------------------------------
[INFO] Setting property: classpath.resource.loader.class => 'org.codehaus.plexus.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on => 'false'.
[INFO] Setting property: resource.loader => 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound => 'false'.
[INFO] [remote-resources:process {execution: default}]
[INFO] [bundle:manifest {execution: bundle-manifest}]
[WARNING] Ignoring project type pom - supportedProjectTypes = [jar, bundle]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[WARNING] DEPRECATED [aggregate]: since 2.5. Use the goals <code>javadoc:aggregate</code> and <code>javadoc:test-aggregate</code> instead.
[INFO] [javadoc:jar {execution: attach-javadocs}]
[INFO] Not executing Javadoc as the project is not a Java classpath-capable package
[INFO] Preparing source:jar
[WARNING] Removing: jar from forked lifecycle, to prevent recursive invocation.
[INFO] No goals needed for project - skipping
[INFO] [source:jar {execution: attach-sources}]
[INFO] [jar:test-jar {execution: default}]
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] [install:install {execution: default-install}]
[INFO] Installing /home/mike/wicket/trunk/pom.xml to /home/mike/.m2/repository/org/apache/wicket/wicket-parent/1.5/wicket-parent-1.5.pom
[INFO] Installing /home/mike/wicket/trunk/target/wicket-parent-1.5-tests.jar to /home/mike/.m2/repository/org/apache/wicket/wicket-parent/1.5/wicket-parent-1.5-tests.jar
[INFO] [gpg:sign {execution: sign-artifacts}]
GPG Passphrase: *********
[INFO] [deploy:deploy {execution: default-deploy}]
Uploading: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/wicket/wicket-parent/1.5/wicket-parent-1.5.pom
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error deploying artifact: Failed to transfer file: https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/wicket/wicket-parent/1.5/wicket-parent-1.5.pom. Return code is: 401
> Use Apache Nexus to stage releases for voting and for release into maven central
> --------------------------------------------------------------------------------
>
> Key: WICKET-3294
> URL: https://issues.apache.org/jira/browse/WICKET-3294
> Project: Wicket
> Issue Type: Improvement
> Components: site, wicket
> Reporter: Michael O'Cleirigh
> Attachments: wicket-1.4.x-pom.xml.diff, wicket-1.5.x-pom.xml.diff
>
>
> This issue from June 2010 was about deploying the 1.4.x-SNAPSHOT and 1.5-SNAPSHOT releases into the Apache Nexus Maven Repository: https://issues.apache.org/jira/browse/WICKET-2918
> This issue is about switching from the current release method to use the staging facilities provided through https://repository.apache.org
> There is an issue with the metadata contained in the maven central repository being out of date that this issue will hopefully resolve as a side effect: https://issues.sonatype.org/browse/MVNCENTRAL-28
> This is the apache documentation for publishing maven artifacts through repository.apache.org:
> http://www.apache.org/dev/publishing-maven-artifacts.html
> According to it that page the distribution management section in the parent org.apache:apache:8 pom contains the details for staging. So what needs to happen is that the parent pom.xml is upgraded from version 7 to version 8 and that the release profiles are adjusted so that only the <site> entry is contained in the distribution management sections.
> There are some settings mentioned that need to go into the deployers local ~/.m2/settings.xml but I am assuming that it is going to be close to what is used for the current release process.
> Then when the deploy part the release is run the jar, javadoc and source artifacts will be signed and uploaded into a staging repository. You login to the repository.apache.org page and on the left hand side you should be able to see a 'Staging Repository' link and clicking it will show a table listing the staged repositories.
> The url associated with each staged repository doesn't work for reading until it has been closed. So if you encounter a bug in the deployment part you can fix it and continue with any old artifacts just overwriting what was previously uploaded. Then within the nexus interface you right click on the row (not on the url part) and select 'close' from the options.
> Once closed the url can be used for the release vote. If the vote fails the staged repository can be dropped. If the vote succeeds then the staged repository can be promoted into a real release. At least in oss.sonatype.org within 1 hour of the promotion the artifact will be synced into the central maven repository.
> It should be possible to test out this improvement ahead of the next release by just deploying into a staged repository and then dropping it if everything is added properly.
> I will attach the modified /trunk/pom.xml and /branches/wicket-1.4.x/pom.xml versions that should let this work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (WICKET-3294) Use Apache Nexus to stage releases
for voting and for release into maven central
Posted by "Michael O'Cleirigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael O'Cleirigh updated WICKET-3294:
---------------------------------------
Attachment: release.md.diff
Attached is a modified version of the Markdown /contribute/release.md from the wicket site documentation.
I removed the staging and release sections and in its place put a section on the repository.apache.org. I also changed the ordering of the release steps and included the nexus release closing (for the vote) and release/drop (after the vote). If you defer from taging the release until it is actually accepted you can make it simple if you need to make changes to the release branch and restage the artifacts.
It would be better with actual screens of the nexus interface like I did for the wicketstuff-core release process here: https://github.com/wicketstuff/core/wiki/Wicket-Stuff-Core-Release-Process But I don't have the access to acquire them.
I can make adjustments if needed and resubmit the patch.
> Use Apache Nexus to stage releases for voting and for release into maven central
> --------------------------------------------------------------------------------
>
> Key: WICKET-3294
> URL: https://issues.apache.org/jira/browse/WICKET-3294
> Project: Wicket
> Issue Type: Improvement
> Components: site, wicket
> Reporter: Michael O'Cleirigh
> Attachments: release.md.diff, wicket-1.4.x-pom.xml.diff, wicket-1.5.x-pom.xml.diff
>
>
> This issue from June 2010 was about deploying the 1.4.x-SNAPSHOT and 1.5-SNAPSHOT releases into the Apache Nexus Maven Repository: https://issues.apache.org/jira/browse/WICKET-2918
> This issue is about switching from the current release method to use the staging facilities provided through https://repository.apache.org
> There is an issue with the metadata contained in the maven central repository being out of date that this issue will hopefully resolve as a side effect: https://issues.sonatype.org/browse/MVNCENTRAL-28
> This is the apache documentation for publishing maven artifacts through repository.apache.org:
> http://www.apache.org/dev/publishing-maven-artifacts.html
> According to it that page the distribution management section in the parent org.apache:apache:8 pom contains the details for staging. So what needs to happen is that the parent pom.xml is upgraded from version 7 to version 8 and that the release profiles are adjusted so that only the <site> entry is contained in the distribution management sections.
> There are some settings mentioned that need to go into the deployers local ~/.m2/settings.xml but I am assuming that it is going to be close to what is used for the current release process.
> Then when the deploy part the release is run the jar, javadoc and source artifacts will be signed and uploaded into a staging repository. You login to the repository.apache.org page and on the left hand side you should be able to see a 'Staging Repository' link and clicking it will show a table listing the staged repositories.
> The url associated with each staged repository doesn't work for reading until it has been closed. So if you encounter a bug in the deployment part you can fix it and continue with any old artifacts just overwriting what was previously uploaded. Then within the nexus interface you right click on the row (not on the url part) and select 'close' from the options.
> Once closed the url can be used for the release vote. If the vote fails the staged repository can be dropped. If the vote succeeds then the staged repository can be promoted into a real release. At least in oss.sonatype.org within 1 hour of the promotion the artifact will be synced into the central maven repository.
> It should be possible to test out this improvement ahead of the next release by just deploying into a staged repository and then dropping it if everything is added properly.
> I will attach the modified /trunk/pom.xml and /branches/wicket-1.4.x/pom.xml versions that should let this work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3294) Use Apache Nexus to stage releases
for voting and for release into maven central
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980839#action_12980839 ]
Igor Vaynberg commented on WICKET-3294:
---------------------------------------
does the below apply:
<martin-g> I guess you'll need to use maven-release-plugin ...
<martin-g> this may cause some troubles
<martin-g> versions:set will not change the scm urls, so you'll still need sed
<martin-g> I have't check latest patch from Mike though ..
<martin-g> only the second sed is needed
i will try to do a 1.5-rc1 tonight, so i will test the new procedure than.
> Use Apache Nexus to stage releases for voting and for release into maven central
> --------------------------------------------------------------------------------
>
> Key: WICKET-3294
> URL: https://issues.apache.org/jira/browse/WICKET-3294
> Project: Wicket
> Issue Type: Improvement
> Components: site, wicket
> Reporter: Michael O'Cleirigh
> Attachments: release.md-2.diff, release.md.diff, wicket-1.4.x-pom.xml.diff, wicket-1.5.x-pom.xml.diff
>
>
> This issue from June 2010 was about deploying the 1.4.x-SNAPSHOT and 1.5-SNAPSHOT releases into the Apache Nexus Maven Repository: https://issues.apache.org/jira/browse/WICKET-2918
> This issue is about switching from the current release method to use the staging facilities provided through https://repository.apache.org
> There is an issue with the metadata contained in the maven central repository being out of date that this issue will hopefully resolve as a side effect: https://issues.sonatype.org/browse/MVNCENTRAL-28
> This is the apache documentation for publishing maven artifacts through repository.apache.org:
> http://www.apache.org/dev/publishing-maven-artifacts.html
> According to it that page the distribution management section in the parent org.apache:apache:8 pom contains the details for staging. So what needs to happen is that the parent pom.xml is upgraded from version 7 to version 8 and that the release profiles are adjusted so that only the <site> entry is contained in the distribution management sections.
> There are some settings mentioned that need to go into the deployers local ~/.m2/settings.xml but I am assuming that it is going to be close to what is used for the current release process.
> Then when the deploy part the release is run the jar, javadoc and source artifacts will be signed and uploaded into a staging repository. You login to the repository.apache.org page and on the left hand side you should be able to see a 'Staging Repository' link and clicking it will show a table listing the staged repositories.
> The url associated with each staged repository doesn't work for reading until it has been closed. So if you encounter a bug in the deployment part you can fix it and continue with any old artifacts just overwriting what was previously uploaded. Then within the nexus interface you right click on the row (not on the url part) and select 'close' from the options.
> Once closed the url can be used for the release vote. If the vote fails the staged repository can be dropped. If the vote succeeds then the staged repository can be promoted into a real release. At least in oss.sonatype.org within 1 hour of the promotion the artifact will be synced into the central maven repository.
> It should be possible to test out this improvement ahead of the next release by just deploying into a staged repository and then dropping it if everything is added properly.
> I will attach the modified /trunk/pom.xml and /branches/wicket-1.4.x/pom.xml versions that should let this work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3294) Use Apache Nexus to stage releases
for voting and for release into maven central
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978591#action_12978591 ]
Hudson commented on WICKET-3294:
--------------------------------
Integrated in Apache Wicket 1.4.x #373 (See [https://hudson.apache.org/hudson/job/Apache%20Wicket%201.4.x/373/])
> Use Apache Nexus to stage releases for voting and for release into maven central
> --------------------------------------------------------------------------------
>
> Key: WICKET-3294
> URL: https://issues.apache.org/jira/browse/WICKET-3294
> Project: Wicket
> Issue Type: Improvement
> Components: site, wicket
> Reporter: Michael O'Cleirigh
> Attachments: wicket-1.4.x-pom.xml.diff, wicket-1.5.x-pom.xml.diff
>
>
> This issue from June 2010 was about deploying the 1.4.x-SNAPSHOT and 1.5-SNAPSHOT releases into the Apache Nexus Maven Repository: https://issues.apache.org/jira/browse/WICKET-2918
> This issue is about switching from the current release method to use the staging facilities provided through https://repository.apache.org
> There is an issue with the metadata contained in the maven central repository being out of date that this issue will hopefully resolve as a side effect: https://issues.sonatype.org/browse/MVNCENTRAL-28
> This is the apache documentation for publishing maven artifacts through repository.apache.org:
> http://www.apache.org/dev/publishing-maven-artifacts.html
> According to it that page the distribution management section in the parent org.apache:apache:8 pom contains the details for staging. So what needs to happen is that the parent pom.xml is upgraded from version 7 to version 8 and that the release profiles are adjusted so that only the <site> entry is contained in the distribution management sections.
> There are some settings mentioned that need to go into the deployers local ~/.m2/settings.xml but I am assuming that it is going to be close to what is used for the current release process.
> Then when the deploy part the release is run the jar, javadoc and source artifacts will be signed and uploaded into a staging repository. You login to the repository.apache.org page and on the left hand side you should be able to see a 'Staging Repository' link and clicking it will show a table listing the staged repositories.
> The url associated with each staged repository doesn't work for reading until it has been closed. So if you encounter a bug in the deployment part you can fix it and continue with any old artifacts just overwriting what was previously uploaded. Then within the nexus interface you right click on the row (not on the url part) and select 'close' from the options.
> Once closed the url can be used for the release vote. If the vote fails the staged repository can be dropped. If the vote succeeds then the staged repository can be promoted into a real release. At least in oss.sonatype.org within 1 hour of the promotion the artifact will be synced into the central maven repository.
> It should be possible to test out this improvement ahead of the next release by just deploying into a staged repository and then dropping it if everything is added properly.
> I will attach the modified /trunk/pom.xml and /branches/wicket-1.4.x/pom.xml versions that should let this work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3294) Use Apache Nexus to stage releases
for voting and for release into maven central
Posted by "Martin Grigorov (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978259#action_12978259 ]
Martin Grigorov commented on WICKET-3294:
-----------------------------------------
The patches are committed and a ticket to INFRA -> Nexus is created: https://issues.apache.org/jira/browse/INFRA-3342.
They will create a group in Nexus and remove the write permissions for 'wicket' (LDAP) group for PAO:/www/...
> Use Apache Nexus to stage releases for voting and for release into maven central
> --------------------------------------------------------------------------------
>
> Key: WICKET-3294
> URL: https://issues.apache.org/jira/browse/WICKET-3294
> Project: Wicket
> Issue Type: Improvement
> Components: site, wicket
> Reporter: Michael O'Cleirigh
> Attachments: wicket-1.4.x-pom.xml.diff, wicket-1.5.x-pom.xml.diff
>
>
> This issue from June 2010 was about deploying the 1.4.x-SNAPSHOT and 1.5-SNAPSHOT releases into the Apache Nexus Maven Repository: https://issues.apache.org/jira/browse/WICKET-2918
> This issue is about switching from the current release method to use the staging facilities provided through https://repository.apache.org
> There is an issue with the metadata contained in the maven central repository being out of date that this issue will hopefully resolve as a side effect: https://issues.sonatype.org/browse/MVNCENTRAL-28
> This is the apache documentation for publishing maven artifacts through repository.apache.org:
> http://www.apache.org/dev/publishing-maven-artifacts.html
> According to it that page the distribution management section in the parent org.apache:apache:8 pom contains the details for staging. So what needs to happen is that the parent pom.xml is upgraded from version 7 to version 8 and that the release profiles are adjusted so that only the <site> entry is contained in the distribution management sections.
> There are some settings mentioned that need to go into the deployers local ~/.m2/settings.xml but I am assuming that it is going to be close to what is used for the current release process.
> Then when the deploy part the release is run the jar, javadoc and source artifacts will be signed and uploaded into a staging repository. You login to the repository.apache.org page and on the left hand side you should be able to see a 'Staging Repository' link and clicking it will show a table listing the staged repositories.
> The url associated with each staged repository doesn't work for reading until it has been closed. So if you encounter a bug in the deployment part you can fix it and continue with any old artifacts just overwriting what was previously uploaded. Then within the nexus interface you right click on the row (not on the url part) and select 'close' from the options.
> Once closed the url can be used for the release vote. If the vote fails the staged repository can be dropped. If the vote succeeds then the staged repository can be promoted into a real release. At least in oss.sonatype.org within 1 hour of the promotion the artifact will be synced into the central maven repository.
> It should be possible to test out this improvement ahead of the next release by just deploying into a staged repository and then dropping it if everything is added properly.
> I will attach the modified /trunk/pom.xml and /branches/wicket-1.4.x/pom.xml versions that should let this work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3294) Use Apache Nexus to stage releases
for voting and for release into maven central
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980895#action_12980895 ]
Igor Vaynberg commented on WICKET-3294:
---------------------------------------
will do Michael, thanks for the help.
> Use Apache Nexus to stage releases for voting and for release into maven central
> --------------------------------------------------------------------------------
>
> Key: WICKET-3294
> URL: https://issues.apache.org/jira/browse/WICKET-3294
> Project: Wicket
> Issue Type: Improvement
> Components: site, wicket
> Reporter: Michael O'Cleirigh
> Attachments: release.md-2.diff, release.md.diff, wicket-1.4.x-pom.xml.diff, wicket-1.5.x-pom.xml.diff
>
>
> This issue from June 2010 was about deploying the 1.4.x-SNAPSHOT and 1.5-SNAPSHOT releases into the Apache Nexus Maven Repository: https://issues.apache.org/jira/browse/WICKET-2918
> This issue is about switching from the current release method to use the staging facilities provided through https://repository.apache.org
> There is an issue with the metadata contained in the maven central repository being out of date that this issue will hopefully resolve as a side effect: https://issues.sonatype.org/browse/MVNCENTRAL-28
> This is the apache documentation for publishing maven artifacts through repository.apache.org:
> http://www.apache.org/dev/publishing-maven-artifacts.html
> According to it that page the distribution management section in the parent org.apache:apache:8 pom contains the details for staging. So what needs to happen is that the parent pom.xml is upgraded from version 7 to version 8 and that the release profiles are adjusted so that only the <site> entry is contained in the distribution management sections.
> There are some settings mentioned that need to go into the deployers local ~/.m2/settings.xml but I am assuming that it is going to be close to what is used for the current release process.
> Then when the deploy part the release is run the jar, javadoc and source artifacts will be signed and uploaded into a staging repository. You login to the repository.apache.org page and on the left hand side you should be able to see a 'Staging Repository' link and clicking it will show a table listing the staged repositories.
> The url associated with each staged repository doesn't work for reading until it has been closed. So if you encounter a bug in the deployment part you can fix it and continue with any old artifacts just overwriting what was previously uploaded. Then within the nexus interface you right click on the row (not on the url part) and select 'close' from the options.
> Once closed the url can be used for the release vote. If the vote fails the staged repository can be dropped. If the vote succeeds then the staged repository can be promoted into a real release. At least in oss.sonatype.org within 1 hour of the promotion the artifact will be synced into the central maven repository.
> It should be possible to test out this improvement ahead of the next release by just deploying into a staged repository and then dropping it if everything is added properly.
> I will attach the modified /trunk/pom.xml and /branches/wicket-1.4.x/pom.xml versions that should let this work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-3294) Use Apache Nexus to stage releases
for voting and for release into maven central
Posted by "Michael O'Cleirigh (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980890#action_12980890 ]
Michael O'Cleirigh commented on WICKET-3294:
--------------------------------------------
You are right about still needing the second sed to fixup the scm urls. I missed this detail when adjusting the documentation.
You shouldn't have to use the maven-release-plugin. For wicketstuff-core I just run the mvn deploy manually and it works fine. I think the release.sh script should still work (it invokes the -Prelease profile which should cause the artifacts to be staged).
For testing you can mvn deploy artifacts into the staging location, login and close the repository and at this point if the artifacts are available it should work.
The first time we did a wicketstuff-core release there was an administrative setting required to be enabled to activate central sync up. Once you *release* the staged artifacts if they don't appear in central then you may need to get this switch toggled. I'm not sure if it applies to the Apache Nexus server or not. Here is the into about it in the oss.sonatype.org context: https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide#SonatypeOSSMavenRepositoryUsageGuide-9.ActivateCentralSync
Can you update the ticket if you have problems with the release steps?
> Use Apache Nexus to stage releases for voting and for release into maven central
> --------------------------------------------------------------------------------
>
> Key: WICKET-3294
> URL: https://issues.apache.org/jira/browse/WICKET-3294
> Project: Wicket
> Issue Type: Improvement
> Components: site, wicket
> Reporter: Michael O'Cleirigh
> Attachments: release.md-2.diff, release.md.diff, wicket-1.4.x-pom.xml.diff, wicket-1.5.x-pom.xml.diff
>
>
> This issue from June 2010 was about deploying the 1.4.x-SNAPSHOT and 1.5-SNAPSHOT releases into the Apache Nexus Maven Repository: https://issues.apache.org/jira/browse/WICKET-2918
> This issue is about switching from the current release method to use the staging facilities provided through https://repository.apache.org
> There is an issue with the metadata contained in the maven central repository being out of date that this issue will hopefully resolve as a side effect: https://issues.sonatype.org/browse/MVNCENTRAL-28
> This is the apache documentation for publishing maven artifacts through repository.apache.org:
> http://www.apache.org/dev/publishing-maven-artifacts.html
> According to it that page the distribution management section in the parent org.apache:apache:8 pom contains the details for staging. So what needs to happen is that the parent pom.xml is upgraded from version 7 to version 8 and that the release profiles are adjusted so that only the <site> entry is contained in the distribution management sections.
> There are some settings mentioned that need to go into the deployers local ~/.m2/settings.xml but I am assuming that it is going to be close to what is used for the current release process.
> Then when the deploy part the release is run the jar, javadoc and source artifacts will be signed and uploaded into a staging repository. You login to the repository.apache.org page and on the left hand side you should be able to see a 'Staging Repository' link and clicking it will show a table listing the staged repositories.
> The url associated with each staged repository doesn't work for reading until it has been closed. So if you encounter a bug in the deployment part you can fix it and continue with any old artifacts just overwriting what was previously uploaded. Then within the nexus interface you right click on the row (not on the url part) and select 'close' from the options.
> Once closed the url can be used for the release vote. If the vote fails the staged repository can be dropped. If the vote succeeds then the staged repository can be promoted into a real release. At least in oss.sonatype.org within 1 hour of the promotion the artifact will be synced into the central maven repository.
> It should be possible to test out this improvement ahead of the next release by just deploying into a staged repository and then dropping it if everything is added properly.
> I will attach the modified /trunk/pom.xml and /branches/wicket-1.4.x/pom.xml versions that should let this work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-3294) Use Apache Nexus to stage releases
for voting and for release into maven central
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-3294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-3294.
-----------------------------------
Resolution: Fixed
Assignee: Igor Vaynberg
thanks for your help Michael, 1.5-rc1 is in staging repo as we speak. cheers.
> Use Apache Nexus to stage releases for voting and for release into maven central
> --------------------------------------------------------------------------------
>
> Key: WICKET-3294
> URL: https://issues.apache.org/jira/browse/WICKET-3294
> Project: Wicket
> Issue Type: Improvement
> Components: site, wicket
> Reporter: Michael O'Cleirigh
> Assignee: Igor Vaynberg
> Attachments: release.md-2.diff, release.md.diff, wicket-1.4.x-pom.xml.diff, wicket-1.5.x-pom.xml.diff
>
>
> This issue from June 2010 was about deploying the 1.4.x-SNAPSHOT and 1.5-SNAPSHOT releases into the Apache Nexus Maven Repository: https://issues.apache.org/jira/browse/WICKET-2918
> This issue is about switching from the current release method to use the staging facilities provided through https://repository.apache.org
> There is an issue with the metadata contained in the maven central repository being out of date that this issue will hopefully resolve as a side effect: https://issues.sonatype.org/browse/MVNCENTRAL-28
> This is the apache documentation for publishing maven artifacts through repository.apache.org:
> http://www.apache.org/dev/publishing-maven-artifacts.html
> According to it that page the distribution management section in the parent org.apache:apache:8 pom contains the details for staging. So what needs to happen is that the parent pom.xml is upgraded from version 7 to version 8 and that the release profiles are adjusted so that only the <site> entry is contained in the distribution management sections.
> There are some settings mentioned that need to go into the deployers local ~/.m2/settings.xml but I am assuming that it is going to be close to what is used for the current release process.
> Then when the deploy part the release is run the jar, javadoc and source artifacts will be signed and uploaded into a staging repository. You login to the repository.apache.org page and on the left hand side you should be able to see a 'Staging Repository' link and clicking it will show a table listing the staged repositories.
> The url associated with each staged repository doesn't work for reading until it has been closed. So if you encounter a bug in the deployment part you can fix it and continue with any old artifacts just overwriting what was previously uploaded. Then within the nexus interface you right click on the row (not on the url part) and select 'close' from the options.
> Once closed the url can be used for the release vote. If the vote fails the staged repository can be dropped. If the vote succeeds then the staged repository can be promoted into a real release. At least in oss.sonatype.org within 1 hour of the promotion the artifact will be synced into the central maven repository.
> It should be possible to test out this improvement ahead of the next release by just deploying into a staged repository and then dropping it if everything is added properly.
> I will attach the modified /trunk/pom.xml and /branches/wicket-1.4.x/pom.xml versions that should let this work.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.