• nbm-maven-plugin
    • examine m3 and see if the nb runtime vs. maven compile dependency problem could be eliminated.

From nbm-maven-plugin docs There are important differences between Maven's dependency mechanism and NetBeans runtime dependencies. Maven's dependencies are transitive, so at compile time you get not only direct dependencies you declared, but also dependencies of dependencies etc. In Netbeans, the module dependencies are non-transitive by nature, you have to explicitly declare all at runtime. Additionally next to module dependencies there are also library jars attached and shipped with the module's main artifact. In the Netbeans terminology there is a special sort of modules called "Library Wrappers". These library wrappers add the libraries on the module's classpath and allow other modules to depend on the libraries within the IDE's runtime.

    • webstart
      • not only generate jnlp files, but also have them versionable and provide servlet/webapp
      • re-signing of already signed binaries
    • OS platform dependent content??
    • annotations use in modules. how?
    • compiling against public packages only?
  • Adding new modules to Platform App
    • Problem: Currently user has to know that she should use nbm-module archetype, has to know where to place it, define module in parent POM project and don't forget to add dependency to nbm-application project.
    • Solution: Action "Add module" in popup menu on "Modules" node of main POM App project, which will run wizard for nbm-module archetype, build new module afterwards and add it as module to POM and as dependency to nbm-application project.
  • Adding dependency on NB API module to Platform App module
    • Problem: For defining dependency on 3-rd party libraries, "Add dependency" dialog is perfect. However for defining dependency on NB API module, it is too generic and it's not evident that "Add dependency" dialog can even be used for this task.
    • Solution: Implement special version of "Add dependency" dialog that would search only NB specific repository (bits.netbeans.org) and will have different labels - similar to Ant version of dialog. Users will access such dialog through action "Add module dependency" on Libraries node.
  • Defining public packages of a module
    • Problem: Currently no UI for marking package as public, user has to google for documentation to find out solution - right configuration of nbm-plugin in pom.xml.
    • Solution: Copy Ant project "API Versioning" to Maven project properties.
  • Selecting modules in the nbm-application
    • Problem: No UI for selecting modules to be included with nbm-application
    • Solution: Use UI provided under "Libraries" section of Ant platform App suite.
  • generic : have means of figuring out that API A needs also addition of API B and C on module's CP.
  • Running application, speeding up edit&compile&debug cycle
    • Compile on save
    • jrebel
    • reload single module in running app.
  • Only show public packages in binary dependencies in the IDE's editor
  • documentation

Also see Jesse's Maven NBM comments (with inline comments from Miloš).

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