[Bug 236262] Allow developer to specify the name of the cluster that a module should belong to

  • From:
  • To:
  • Subject: [Bug 236262] Allow developer to specify the name of the cluster that a module should belong to
  • Date: Tue, 15 Oct 2013 17:55:12 +0000
  • Auto-submitted: auto-generated

https://netbeans.org/bugzilla/show_bug.cgi?id=236262

--- Comment #2 from 

 ---
To see how the Maven process works:

1. Create a Maven-based NetBeans Platform Application project.
2. Create two new Maven-based NetBeans Module projects within the folder of 
the
parent.
3. Add both new modules as dependencies to the Application project.
4. For each of the module projects, now add a cluster property to the
nmb-maven-plugin configuration (different value for each):
     <configuration>
         <cluster>a</cluster>
     </configuration>
5. Build with dependencies the application project.

When the platform application is built, each of the modules appear in their 
own
cluster folder. Although the mechanism is very different, the output is 
similar
to how the IDE's modules are grouped into clusters when they are built.

The only way I can see to change the name of the output cluster in an 
Ant-based
project, is to change the name of the suite of which it is a part. But I want
to have a finer level of distinction to avoid having to have a great number of
suites (and suite chains) in our application.

Please let me know if I can provide more information. :)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.


[Bug 236262] Allow developer to specify the name of the cluster that a module should belong to

mkozeny 10/14/2013

<Possible follow-up(s)>

[Bug 236262] Allow developer to specify the name of the cluster that a module should belong to

mienamoo 10/15/2013

Project Features

About this Project

APIsupport was started in November 2009, is owned by Antonin Nebuzelsky, and has 43 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20131025.e7cbc9d). © 2013, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
 
 
Close
loading
Please Confirm
Close