This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 191662 - Polyglot Maven support
Summary: Polyglot Maven support
Status: REOPENED
Alias: None
Product: projects
Classification: Unclassified
Component: Maven (show other bugs)
Version: 8.2
Hardware: All All
: P3 normal with 1 vote (vote)
Assignee: Jesse Glick
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-05 10:18 UTC by hantsy
Modified: 2017-02-10 07:15 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description hantsy 2010-11-05 10:18:06 UTC 
Maven 3 support script language instead of the xml config...NetBeans must consider the features newly added in maven 3....

Build file (pom.groovy)

project {
  modelVersion '4.0.0'
  artifactId 'coc-comparison'
  groupId 'grId'
  version '1.0-SNAPSHOT'

  dependencies {
    dependency('commons-lang:commons-lang:2.5')
    dependency('junit:junit:4.8.2')
  }

  build {
    plugins {
      plugin {
        groupId 'org.apache.maven.plugins'
        artifactId 'maven-compiler-plugin'
        configuration {
          source '1.5'
          target '1.5'
        }
      }
    }
  }
}
Comment 1 Jesse Glick 2010-11-05 13:50:43 UTC 
It is likely that the IDE would be able to successfully read such a POM if the Polyglot support were integrated. It would not be able to *write* changes to it the way it does pom.xml, since a script is not necessarily fully declarative, so e.g. the Dependencies node would have no Add... action and all fields in the project's Properties dialog would have to be disabled. Semantic code completion in pom.groovy is also unlikely. So you would be able to open projects, and make textual edits to them - better than nothing but certainly inferior to the IDE's support for regular POMs.
Comment 2 hantsy 2010-11-05 16:26:52 UTC 
I think no need full implementation like pom.xml...but I think it is better to provide the following...
1. can read the script completely to resolve dependencies, plugins...etc
2. can execute target as normal maven.
3. provide code assistance in the specified "pom.groovy"(Code completion, Code generation, Error Marker, Hint).
Comment 3 Jesse Glick 2010-11-05 17:10:16 UTC 
#1 and #2 are probably doable without much work (assuming Polyglot is easy to embed). #3 is likely a lot of work and I would not expect anyone to want to work on it, unless Polyglot really gets widely adopted.
Comment 4 Jesse Glick 2011-10-31 17:45:56 UTC 
Have not heard any other requests for this; no plans to implement.
Comment 5 hantsy 2011-11-01 01:51:45 UTC 
Oh....the issue I wrote here is not a request ?
Comment 6 Jesse Glick 2011-11-10 00:26:10 UTC 
Any _other_ requests. Have not heard of it in wide use in the field.
Comment 7 hantsy 2011-11-10 02:15:03 UTC 
Ok, I agree ur point,
It is not used widely...

But I remembered I created another issue for requesting Gradle support( http://netbeans.org/bugzilla/show_bug.cgi?id=191664 )? It was closed directly?
It is widely used...why WANTNOT fix it.
Comment 8 wvreeven 2017-02-02 22:53:28 UTC 
We are many years later now and polyglot is more widely used that back when this issue was first opened. Will you please reconsider adding support for 1. and 2.? To remind you:
1. can read the script completely to resolve dependencies, plugins...etc
2. can execute target as normal maven.

Thanks very much in advance!
Comment 9 squib 2017-02-10 07:15:59 UTC 
Our company would also love to see maven polyglot support for Netbeans. In fact we had to switch to another ide for some projects just because Netbeans lack it.