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 124814 - FAST: Import / export utility required for grouping projects
Summary: FAST: Import / export utility required for grouping projects
Status: NEW
Alias: None
Product: soa
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: All All
: P2 blocker (vote)
Assignee: Venkat Chellasamy
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-01-07 15:14 UTC by lpolycarpou
Modified: 2012-12-17 19:04 UTC (History)
1 user (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description lpolycarpou 2008-01-07 15:14:59 UTC
Moving projects from one NB instance to another is not intuitive.  No import/export utility for grouping projects.  What
is required is a full export capability of modern EE, classic (including repository based) & JBI projects.  This could
be done individually per project or at the composite application level which would export across all the dependent
projects.  Even if customers are using source control features for this, this will be required for simplifying the bug
logging / support analysis of customer issues.
Comment 1 Sergey Lunegov 2008-01-18 12:01:27 UTC
Not sure this is specific to comp app project.
Comment 2 lpolycarpou 2008-01-20 01:59:48 UTC
Either am I. However, the comp app is currently the only place that links all of the related JBI, Modern EE and CAPS
Classic project JARs thus containing some references back to the containing projects.
Comment 3 Venkat Chellasamy 2008-02-19 19:47:41 UTC
Currently NB does not provide say way to combine project types [EE, JBI, repository based] and do export/import of the same.
we will consider this as an enhancement request to composite application project system post NB6.1 release
Comment 4 markiewb 2012-12-17 18:52:54 UTC
Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue doesn't get lost.
Comment 5 markiewb 2012-12-17 19:04:42 UTC
Set target-milestone of open issue to TBD (was < 7.3, f.e. 6.8), so the issue
doesn't get lost. This time the target milestone is really set.