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 118363 - Add more options for multiple selected Projects
Summary: Add more options for multiple selected Projects
Status: RESOLVED DUPLICATE of bug 64991
Alias: None
Product: projects
Classification: Unclassified
Component: Generic Projects UI (show other bugs)
Version: 6.x
Hardware: All Windows XP
: P3 blocker (vote)
Assignee: Milan Kubec
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-10 14:03 UTC by tomzi
Modified: 2007-10-12 07:37 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 tomzi 2007-10-10 14:03:35 UTC
Please add support for

Build
Clean Build
Clean
Generate Javadoc
Custom->...
Reload Project
Show and Resolve Problems

when selecting multiple projects.
Comment 1 Jesse Glick 2007-10-10 14:08:18 UTC

*** This issue has been marked as a duplicate of 64991 ***
Comment 2 Milos Kleint 2007-10-10 14:23:59 UTC
from the selection of actions it seems maven projects are involved. So some of the actions could be probably implemented
on maven side (Reload). Some don't seem to make much sense to me (Custom) as the custom list is currently different for
each project.
Comment 3 tomzi 2007-10-12 07:18:26 UTC
yeah true, currently it is different, but there has also been a feature request to have custom goals, that can be added
that match all projects, eg. package, dependency:analyze. Maybe for this an additional flag could be added to the
Actions dialog (Eg. [x] Global). But this would be a seperate feature request.

It still could be possible that more than one project have similar custom goals.

Are the Build, Clean Build, Clean, Generate Javadoc, Show and Resolve Problem not also Maven specific goals?
Comment 4 tomzi 2007-10-12 07:20:54 UTC
Especially in the build process it would make sense to build handle it not completely arbitrary, since two projects
could depend upon each other....
Comment 5 Milos Kleint 2007-10-12 07:37:33 UTC
once global custom goals are implemented then it indeed makes sense.
for generic actions it's rightfully a duplicate. The build action needs to handle mixed setup (ant+maven+c+ruby selected
at once). For maven projects we should probably trigger a single reactor build instead of a separate build for each project.

BTW implemented for refresh project.