Revision as of 12:32, 29 March 2010 by Dsimonek (Talk | contribs)


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 (
  2. Special for 6.9: Release new version of maven compiler plugin - (, 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
  4. Development: Archetype release owner updates archetypes with agreed version info from previous step and releases new versions of archetypes into
  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.


  • 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"?


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