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 190555 - UI to edit NB version of Maven NB Platform App project
Summary: UI to edit NB version of Maven NB Platform App project
Status: NEW
Alias: None
Product: apisupport
Classification: Unclassified
Component: Maven (show other bugs)
Version: 7.0
Hardware: All All
: P3 normal (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-23 10:20 UTC by Antonin Nebuzelsky
Modified: 2012-08-23 12:28 UTC (History)
0 users

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 Antonin Nebuzelsky 2010-09-23 10:20:32 UTC 
POM project which serves as a parent of the "nbm-application" project and "nbm" projects defines netbeans.version property for the group of related projects.

Daily builds point to a version of the archetype which has netbeans.version set to SNAPSHOT, in released IDE versions the referenced archetype version has it set to the IDE's version of archetypes, e.g. RELEASE691.

The user may want to build his RCP app against a different version of Platform.

The user can edit <netbeans.version> in the POM project's pom.xml.

It would be nice if the users find this property in UI in the "nbm-application" project's properties dialog box.
Comment 1 Milos Kleint 2012-08-23 12:28:38 UTC 
unfortunately the property usage, naming and location are just a convenience defined by the archetype. the actual projects can have the property defined elsewhere, not use a property at all or have different name for the property. 

another assumption that might not be always true is that any given application has just one nbm-application project. But I know that some people have multiple ones. Then changing one application would change the version for all of them (as most likely the parent pom would be changed, not the actual application project.