MavenPlan69

(Difference between revisions)
(Created page with '== Maven plan for next release (6.9?) DRAFT == ___TOC___ ====Maven 3 support==== * rewrite project support to use Maven 3 ====Assembly & release support==== * assembly plug…')
Line 1: Line 1:
-
== Maven plan for next release (6.9?) DRAFT ==
+
= Maven plan for next release (6.9?) DRAFT =
   
   
___TOC___
___TOC___
-
====Maven 3 support====
+
==Maven 3 support==
* rewrite project support to use Maven 3
* rewrite project support to use Maven 3
-
====Assembly & release support====
+
==Assembly & release support==
* assembly plugin support, simple creation of self-contained executable jar
* assembly plugin support, simple creation of self-contained executable jar
Line 13: Line 13:
* webstart support
* webstart support
-
====Connected developer====
+
==Connected developer==
* 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
Line 19: Line 19:
* 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====
+
==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)
* 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==
* 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
Line 29: Line 29:
* simple visual POM "generator" - generate sections, not full editor
* simple visual POM "generator" - generate sections, not full editor
-
====Code coverage/quality====
+
==Code coverage/quality==
* allow code coverage integration to work with maven based projects
* allow code coverage integration to work with maven based projects
Line 35: Line 35:
* interaction with Sonar servers, see some hints about [[SonarAPIImplHints| Sonar API ]]  
* interaction with Sonar servers, see some hints about [[SonarAPIImplHints| Sonar API ]]  
-
====Other====
+
==Other==
* custom UI for renaming, deleting, copying and moving Maven projects
* custom UI for renaming, deleting, copying and moving Maven projects

Revision as of 11:56, 10 November 2009

Maven plan for next release (6.9?) DRAFT

_

Contents

_

Maven 3 support

  • rewrite project support to use Maven 3

Assembly & release support

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

Connected developer

  • 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, ...)

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

Code coverage/quality

  • 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

  • custom UI for renaming, deleting, copying and moving Maven projects
  • webservices designer from ant projects to work in maven (mkuchtiak)
  • 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) (milos/dafe for ui help)

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.

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