MavenPlan69

(Difference between revisions)
(Maven 3 support)
Line 1: Line 1:
-
= Maven plan for next release (6.9?) DRAFT =
+
=Maven plan for next release=
-
+
 
-
___TOC___
+
'''STILL ONLY DRAFT'''
==Maven 3 support==
==Maven 3 support==
 +
* '''the priority'''
* rewrite project support to use Maven 3
* rewrite project support to use Maven 3
 +
:* [http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes Maven 3.x Compatibility Notes]
-
http://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes
+
==Code generators==
 +
 
 +
* '''maybe features'''
 +
* enrich "Insert Code" for pom.xml, allow generate scala support, webstart support, osgi bundles, self executable jar etc. (project code generators now exists on Kenai, need to move to nb distro along with scala when possible)
==Assembly & release support==
==Assembly & release support==
 +
* '''maybe features'''
* assembly plugin support, simple creation of self-contained executable jar
* assembly plugin support, simple creation of self-contained executable jar
* UI for release plugin
* UI for release plugin
Line 17: Line 23:
==Connected developer==
==Connected developer==
 +
* '''nice to have'''
* integration with bugtracking UI - use bug tracking system type and URL from Maven POM
* integration with bugtracking UI - use bug tracking system type and URL from Maven POM
* integration with hudson module (initial state already in 6.7) - configure hudson plugins based on maven plugin configuration -
* integration with hudson module (initial state already in 6.7) - configure hudson plugins based on maven plugin configuration -
* more integration with CI - propagate the results of hudson builds back to the UI (test coverage, pmd, findbugs, ...)
* more integration with CI - propagate the results of hudson builds back to the UI (test coverage, pmd, findbugs, ...)
-
 
-
==Code generators==
 
-
 
-
* enrich "Insert Code" for pom.xml, allow generate scala support, webstart support, osgi bundles, self executable jar etc. (project code generators now exists on Kenai, need to move to nb distro along with scala when possible)
 
==UI - Artifact Viewer==
==UI - Artifact Viewer==
 +
* '''nice to have'''
* rearrange description parts - http://www.netbeans.org/issues/show_bug.cgi?id=164973
* rearrange description parts - http://www.netbeans.org/issues/show_bug.cgi?id=164973
* improve graphs layout (e.g. tree layout without gaps)
* improve graphs layout (e.g. tree layout without gaps)
Line 33: Line 37:
==Code coverage/quality==
==Code coverage/quality==
 +
* '''nice to have'''
* allow code coverage integration to work with maven based projects
* allow code coverage integration to work with maven based projects
* reuse the maven plugin (cobertura,clover,emma) configuration in the IDE
* reuse the maven plugin (cobertura,clover,emma) configuration in the IDE
Line 38: Line 43:
==Other==
==Other==
 +
 +
* '''out of scope now'''
* custom UI for renaming, deleting, copying and moving Maven projects
* custom UI for renaming, deleting, copying and moving Maven projects
-
* webservices designer from ant projects to work in maven ('''mkuchtiak''')
+
* webservices designer from ant projects to work in maven
* migration support from Ant to Maven
* migration support from Ant to Maven
-
* global (re)definition of action mappings (e.g. run) - [http://www.netbeans.org/issues/show_bug.cgi?id=162764 #162764] - important for features we don't directly support and for making global changes according to user preferences (skip test execution on Build, perform a clean before running Test etc) ('''milos/dafe for ui help''')
+
* global (re)definition of action mappings (e.g. run) - [http://www.netbeans.org/issues/show_bug.cgi?id=162764 #162764] - important for features we don't directly support and for making global changes according to user preferences (skip test execution on Build, perform a clean before running Test etc)
 +
 
 +
* ''Turns out to be more complex than anticipated.  In general the decision process (what definition gets used) gets more complicated and unclear to the user. Especially for cases with IDE settings changed from one version to another.''
 +
 
 +
==LINKS==
-
'''Turns out to be more complex than anticipated.  In general the decision process (what definition gets used) gets more complicated and unclear to the user. Especially for cases with IDE settings changed from one version to another.'''
+
''For reference: [MavenPlan68]''

Revision as of 17:24, 4 December 2009

Contents

Maven plan for next release

STILL ONLY DRAFT

Maven 3 support

  • the priority
  • rewrite project support to use Maven 3

Code generators

  • maybe features
  • enrich "Insert Code" for pom.xml, allow generate scala support, webstart support, osgi bundles, self executable jar etc. (project code generators now exists on Kenai, need to move to nb distro along with scala when possible)

Assembly & release support

  • maybe features
  • assembly plugin support, simple creation of self-contained executable jar
  • UI for release plugin
  • webstart support

Connected developer

  • nice to have
  • integration with bugtracking UI - use bug tracking system type and URL from Maven POM
  • integration with hudson module (initial state already in 6.7) - configure hudson plugins based on maven plugin configuration -
  • more integration with CI - propagate the results of hudson builds back to the UI (test coverage, pmd, findbugs, ...)

UI - Artifact Viewer

Code coverage/quality

  • nice to have
  • allow code coverage integration to work with maven based projects
  • reuse the maven plugin (cobertura,clover,emma) configuration in the IDE
  • interaction with Sonar servers, see some hints about Sonar API

Other

  • out of scope now
  • custom UI for renaming, deleting, copying and moving Maven projects
  • webservices designer from ant projects to work in maven
  • migration support from Ant to Maven
  • global (re)definition of action mappings (e.g. run) - #162764 - important for features we don't directly support and for making global changes according to user preferences (skip test execution on Build, perform a clean before running Test etc)
  • Turns out to be more complex than anticipated. In general the decision process (what definition gets used) gets more complicated and unclear to the user. Especially for cases with IDE settings changed from one version to another.

LINKS

For reference: [MavenPlan68]

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