[api-changes] [Bug 210465] Distinguish required projects from submodules

  • From:
  • To:
  • Subject: [api-changes] [Bug 210465] Distinguish required projects from submodules
  • Date: Mon, 18 Mar 2013 14:10:25 +0000
  • Auto-submitted: auto-generated

http://netbeans.org/bugzilla/show_bug.cgi?id=210465

--- Comment #14 from Jesse Glick 
< >
 2013-03-18 14:10:25 UTC ---
(In reply to comment #13)
> in the open project dialog

As in comment #0 point (a), I advocate removing any functionality of this kind
from the Open Project dialog: it should open the selected project(s) and
nothing else.

> the workflow for opening multiple related maven projects should be to open
> just the parent pom + open required.

Open Submodules

>> It is relevant for Ant-based EARs which have submodules but
>> no required projects. Same for Ant-based NBM suites.
> 
> it wasn't causing problem there.

The particular problem you mentioned of course does not exist with these
project types, but they still suffer from the lack of an API to specifically
open either submodules, or dependencies.

> have an API method that either does the default behaviour of FOQ + SFBQ
> processing (with most likely selectable scope) or depends on the newly
> introduced ProjectDependencyProvider in the project where we add scope to 
> the
> interface as well.

Seems fine.

> PDP needs to be internally recursive because in maven projects
> I cannot recursively go down into dependencies of dependencies and get
> PDP. the root project in the chain can have overrides on versions.

Makes sense then that the API/SPI should have a 'boolean transitive' flag.

> subproject provider would stay in current form, with adjusted/simplified
> maven implementation

So what would the new meaning of SubprojectProvider actually be? And how do 
you
deal with the compatibility implications for code calling it on Maven projects
with certain expectations?

> my problem with SubmoduleProvider is it's apparent maven-ness, one cannot
> really define it without referencing maven

Why? “Gets a list of all projects physically contained or aggregated by this
one.” Seems perfectly sensible for EAR or suite projects, not to mention an
Android project with accompanying test project, etc.

> the 2 other cases you mention were fairly happy with SubprojectProvider.

Not really. For example comment #0 item (d): this project group kind in its
current implementation is useless for NBM suite projects, because adding a
source association to an NB platform could suddenly cause source dependencies
to appear in the project list, when all you really wanted was the suite and 
its
modules. The situation there seems quite analogous to Maven.

-- 
Configure bugmail: http://netbeans.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

[api-changes] [Bug 210465] Distinguish required projects from submodules

mkleint 03/15/2013

<Possible follow-up(s)>

[api-changes] [Bug 210465] Distinguish required projects from submodules

jglick 03/15/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

mkleint 03/15/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

jglick 03/15/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

mkleint 03/15/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

mkleint 03/15/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

jglick 03/15/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

mkleint 03/18/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

jglick 03/18/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

mkleint 03/19/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

jtulach 03/20/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

mkleint 03/20/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

mkleint 03/20/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

mkleint 03/20/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

jglick 03/20/2013

[api-changes] [Bug 210465] Distinguish required projects from submodules

mkleint 03/20/2013

Project Features

About this Project

www was started in November 2009, is owned by jpirek, and has 21 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20140418.2d69abc). © 2013, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
 
 
Close
loading
Please Confirm
Close