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 198137 - Support for team project configuration scripts
Summary: Support for team project configuration scripts
Status: NEW
Alias: None
Product: connecteddeveloper
Classification: Unclassified
Component: Kenai (show other bugs)
Version: 7.0
Hardware: All All
: P1 normal (vote)
Assignee: issues@connecteddeveloper
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-27 13:54 UTC by Jan Becicka
Modified: 2012-10-18 09:58 UTC (History)
2 users (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 Jan Becicka 2011-04-27 13:54:49 UTC
Real projects usually uses several server side services:
* Bugtracking (bugzilla, etc..)
* Versioning (SVN, Hg, etc..)
* Hudson
* Chat

All these services are supported by the IDE, but there should be some way, how to configure all these services via one script (downloaded from url, or stored locally). It will be useful to have decalarative way how to define connection between all those services, which belongs to my project.
Comment 1 Jan Becicka 2011-04-27 14:10:16 UTC
Kenai support can be reused. Format of configurations scripts could be json for instance. See https://netbeans.org/api/projects/java/features.json
Comment 2 Antonin Nebuzelsky 2011-04-27 16:39:24 UTC
Several questions:

* will the user need to do two steps - opening the project and pointing the IDE to the config script? seems like the config should rather be included in the project

* the JSON format is nice because we already have the code which understands it, but on the other hand it is not too readable for the user - how will the users create and later update the config?

* maven already has a standard way of specifying some (most?) of these properties in a project
Comment 3 Tomas Stupka 2011-04-27 17:14:08 UTC
> * maven already has a standard way of specifying some (most?) of these
> properties in a project
one more potential provider for the suggested service. together with the kenai suport and the vcs - bugtracking integration which both already have their own mechanisms have to store at least some of the mentioned information.
Comment 4 Jan Becicka 2011-04-28 06:30:14 UTC
Re tonda #1:
included in which project? For instance netbeans IDE has hundreds of projects. And it will be also useful to be able to work with projects, which are not open in the IDE. For instance we are experimenting with server-side "go to type" which will be able to work with types, which are not open in the IDE

re tonda #2:
JSON is just suggestion. I'm not sure. Anyway these config files will be created by project admin only once. And I don't think, that it is necessary to have advanced editor for it.