Revision as of 10:21, 29 March 2010 by Dsimonek (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)


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:

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

HowTo steps

  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 (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?
  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.
  7. 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?


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