MavenReleaseRCPHowto

(Difference between revisions)
(Questions)
(Maven related RCP and IDE release steps)
Line 3: Line 3:
=Maven related RCP and IDE release steps=
=Maven related RCP and IDE release steps=
-
Following document summarizes set of steps that needs to be taken by various parties along with each release of NetBeans IDE. Goals of actions described further are primarily:
+
Following document summarizes set of steps that needs to be taken by various parties along with each "release" of NetBeans IDE. "Release" means either Beta, Release Candidate or FCS in this document. Goals of actions described further are primarily:
* Released IDE uses latest available released(=non-snapshot) archetypes from http://repository.codehaus.org/org/codehaus/mojo/archetypes/
* Released IDE uses latest available released(=non-snapshot) archetypes from http://repository.codehaus.org/org/codehaus/mojo/archetypes/
Line 11: Line 11:
As a result creating of all types of Maven projects should work properly with correctly generated non-snapshot dependencies.
As a result creating of all types of Maven projects should work properly with correctly generated non-snapshot dependencies.
-
==HowTo steps==
+
==HowTo steps, time ordered==
# ''Development:'' If there were updates to nbm-maven-plugin, then release it. Requires committer access to codehaus svn (http://xircles.codehaus.org/projects/mojo/repo/primary/repo)
# ''Development:'' If there were updates to nbm-maven-plugin, then release it. Requires committer access to codehaus svn (http://xircles.codehaus.org/projects/mojo/repo/primary/repo)
Line 17: Line 17:
# ''Development & RE:'' Archetype release owner and RE must agree on exact version strings for artifacts that *will be* released on bits.netbeans.org/maven2
# ''Development & RE:'' Archetype release owner and RE must agree on exact version strings for artifacts that *will be* released on bits.netbeans.org/maven2
# ''Development:'' Archetype release owner updates archetypes with agreed version info from previous step and releases new versions of archetypes into http://repository.codehaus.org/org/codehaus/mojo/archetypes/
# ''Development:'' Archetype release owner updates archetypes with agreed version info from previous step and releases new versions of archetypes into http://repository.codehaus.org/org/codehaus/mojo/archetypes/
-
# ''Development:'' Throughout the IDE sources update the references (mostly version strings) to the archetypes released in previous step. '''Warning: Starting from this point, IDE will use non-existing dependencies, so the newly created Maven projects won't build until next step is done. QA needs to be notified.''' '''Are there any other references in IDE sources?''' '''Timing of this change? - before/after high resistance? before/after some clone?'''  
+
# ''Development:'' Throughout the IDE sources update the references (version strings) to the archetypes released in previous step. Timing of the change is after clone (beta or release), as part of branding changes. '''Warning: Starting from this time-point, IDE will use non-existing dependencies, so the newly created Maven projects won't build until next step is done. QA needs to be notified.'''  
-
# ''RE:'' Release non-snapshot NB module artifacts with version strings agreed with Development. After release, newly created projects in IDE should be OK again.
+
# ''RE:'' Release non-snapshot NB module artifacts with version strings agreed with Development. After release, newly created projects in IDE should be OK again, so it's desirable to complete this item soon after previous step.
-
# ''Development & RE:'' Increase SNAPSHOT version of artifacts (archetypes, module artifacts) in dev builds after release. '''Questions: How to do that, and when to do such change?'''
+
=Questions=
=Questions=

Revision as of 12:32, 29 March 2010

Contents


Maven related RCP and IDE release steps

Following document summarizes set of steps that needs to be taken by various parties along with each "release" of NetBeans IDE. "Release" means either Beta, Release Candidate or FCS in this document. Goals of actions described further are primarily:

As a result creating of all types of Maven projects should work properly with correctly generated non-snapshot dependencies.

HowTo steps, time ordered

  1. Development: If there were updates to nbm-maven-plugin, then release it. Requires committer access to codehaus svn (http://xircles.codehaus.org/projects/mojo/repo/primary/repo)
  2. Special for 6.9: Release new version of maven compiler plugin - (http://jira.codehaus.org/browse/MCOMPILER-75, http://jira.codehaus.org/browse/MCOMPILER-98) external dependency on maven team, as it requires committer access to compiler plugin
  3. Development & RE: Archetype release owner and RE must agree on exact version strings for artifacts that *will be* released on bits.netbeans.org/maven2
  4. Development: Archetype release owner updates archetypes with agreed version info from previous step and releases new versions of archetypes into http://repository.codehaus.org/org/codehaus/mojo/archetypes/
  5. Development: Throughout the IDE sources update the references (version strings) to the archetypes released in previous step. Timing of the change is after clone (beta or release), as part of branding changes. Warning: Starting from this time-point, IDE will use non-existing dependencies, so the newly created Maven projects won't build until next step is done. QA needs to be notified.
  6. RE: Release non-snapshot NB module artifacts with version strings agreed with Development. After release, newly created projects in IDE should be OK again, so it's desirable to complete this item soon after previous step.

Questions

  • Archetypes should be released each individually or as a group?
  • How would example input into "mvn release:prepare" look?
  • Should beta use snapshot or non-snapshot artifacts?
  • How should look version string of released NB module artifacts? "RELEASE69"?

Links

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo