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 65016 - new cvs system also commits library information. this is somehow bad
Summary: new cvs system also commits library information. this is somehow bad
Status: RESOLVED DUPLICATE of bug 44035
Alias: None
Product: projects
Classification: Unclassified
Component: Libraries (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Zezula
Depends on:
Reported: 2005-09-23 17:12 UTC by drscott
Modified: 2006-01-22 16:54 UTC (History)
1 user (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description drscott 2005-09-23 17:12:21 UTC
Think of two (or more) independly working developers. They all use library 'foo'
and made an corresponding entry in their library manager. But all of them use a
slightly different name (Foo, foo, libfoo....), because theiy do not work
together at the moment.
Now they have to start to work together on a project which depends on 'foo'. One
developer imports the project to a repository, all the others then check it out.
All of them will now get this 'reference problems' warning, which is good.
But now they are forced to create a new library in the library manager to fit
the name. Now think of more shared projects with more different names. This will
end in an situation where a developer will have many entries for the same
library. This is an maintanance nightmare. (Think of a new version of
foo_1-3.jar: You have to adapt every single definition).

Even worse: One developer doesn't care and does not resolve the problem, but
remove the conflicting library (foo) and replace it with his one (FoolishFoo).
Then he commits the change... Nightmare reloaded?

Possible solutions:
* no library information is commited at all (maybe configurable)
* library information is commited, but the manager is able to use aliases
(FoolishFoo => foo) (This would be a nice solution in the 'resolve problem'
process: The user does not create a complete new library, but specifies an
already existing one. An alias will be created and used. Problem solved. Only
one real library definition)
* Any other solutions?
Comment 1 Jesse Glick 2006-01-22 16:54:11 UTC
Not technically a dupe, but effectively that is what is being requested.

*** This issue has been marked as a duplicate of 44035 ***