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.
I would like to register a new library, but the New Library dialog does not accepts name with space insisde. But there are some deafult libraries with space in name like "Absolut Layout" installed.
Invalid, because of ANT?
Yes, the display name can contain spaces but the system name not, because of Ant. The issue is related to: http://www.netbeans.org/issues/show_bug.cgi?id=43601 (Renaming of library = the same problem)
*** Issue 55179 has been marked as a duplicate of this issue. ***
If this is because of Ant, why doesn't the display name become whatever I type, and the underlying library name just use underscores instead? This is really frustrating especially considering that the default set of 10 libraries or so use spaces. (I swear there was a newer bug for this)
"If this is because of Ant, why doesn't the display name become whatever I type, and the underlying library name just use underscores instead?" - well that's just what the fix would consist of. The main reason we didn't do it this way to begin with is that there is the possibility of confusion later in the Resolve Broken References dialog - a different user resolving your "Hello Library" would actually see "Hello_Library". But that is probably much less of a problem than this.
Yes, the resolve broken references was the reason why we decided that ant name == library name in the NB 4.0. It is trivial to change it, but it requires an API change in the LibraryImplementation which has no getter/setter for display name.
*** Issue 76656 has been marked as a duplicate of this issue. ***
*** Issue 61628 has been marked as a duplicate of this issue. ***
*** Issue 84146 has been marked as a duplicate of this issue. ***
*** Issue 85640 has been marked as a duplicate of this issue. ***
Number of duplicaes is rising, so I do with the priority.
*** Issue 89307 has been marked as a duplicate of this issue. ***
*** Issue 87965 has been marked as a duplicate of this issue. ***
*** Issue 88419 has been marked as a duplicate of this issue. ***
Folks, that's a shame... A P2 with 9 (!!) duplicates being open for 2.5 years. Shouldn't you just fix it?
I agree with ksorokin. Tonda, do you plan this for NB 6.0 ?
> do you plan this for NB 6.0 ? Yes, I agree this should be fixed. I talked to Tomas. He will do this soon.
*** Issue 92101 has been marked as a duplicate of this issue. ***
*** Issue 93079 has been marked as a duplicate of this issue. ***
Clearly was not done for M6. Target milestone?
Also see issue #89306.
*** Issue 105220 has been marked as a duplicate of this issue. ***
*** Issue 104888 has been marked as a duplicate of this issue. ***
*** Issue 115601 has been marked as a duplicate of this issue. ***
13 duplicates, with the related issues(one a P1), it goes up to 15. I assume this won't make to NB 6.0, as it didn't for the other previous five major releases. Is this really just a matter of adding a get/setDisplayName and adapting the UI and XMLs?
Mainly it's an incompatible SPI change.
*** Issue 117590 has been marked as a duplicate of this issue. ***
*** Issue 125627 has been marked as a duplicate of this issue. ***
*** Issue 133477 has been marked as a duplicate of this issue. ***
So, what are the changes for this 5 year old bug to be fixed in 7.0? It's a popular bug.
*** Issue 166374 has been marked as a duplicate of this issue. ***
OK, is someone actually going to fix this? Please reevaluate as the TM is obsolete.
*** Issue 172126 has been marked as a duplicate of this issue. ***
Should be fixed into next version as it has very duplicates. Requires an API change.
Created attachment 92070 [details] Screenshot with other incorrect characters (non-space) Some characters in other locales (ru_RU, e.g.) are incorrect too.
Scheduled for NB 6.9 (http://wiki.netbeans.org/EditorPlan69)
Guys, I don't know, but if you cannot fix a thing like that within 7 years, what can you say ? Using NetBeans for 11 years now it makes me feel desperate a bit to still see these stains on the face of NetBeans being totally neglected... OK, how about this: not because, but despite the mindset of its maintainers NetBeans manages to be a great product... With the unwelcome fact in mind that a shortcoming like this has existed for years and years the press releases published following the tenet of "the importance of working backwards" sound a bit "flamboyant". Just lifting the carpet and dusting away all the dirt there would be enough to make for a great release 8.0.
In reply to comment #37. There were always more important fixes and features with much more significant impact.
(In reply to comment #38) > In reply to comment #37. > There were always more important fixes and features with much more significant > impact. For example the Maven work, which is a better way of handling libraries, anyway. If you ask me, they should do away with that legacy project stuff and focus on Maven exclusively.
(In reply to comment #39) > anyway. If you ask me, they should do away with that legacy project stuff and > focus on Maven exclusively. No, definitively not. Maven is too much overload for smaller projects.
The Ant based project is not legacy. Lot's of people prefer Ant to Maven. See NB statistics: http://statistics.netbeans.org/analytics/graph/projecttypes.jsp I will try to do this as soon as possible before other requests come.
(In reply to comment #40) > No, definitively not. Maven is too much overload for smaller projects. Spoken like someone who has never used Maven. It is much simpler for smaller projects because there is virtually no configuration.
Sorry, there are a lot of us who have absolutely no interest in a project ruled by Mavenocracy.
I have tried Maven myself and for smaller projects without a lot of dependencies the standard Ant way is much easier. For instance, it takes some time (at least for the Maven newbie) to find out, how to integrate a simple jar dependency into your project. You have to install it in your local repository first to be able to reference it (you could always edit the pom, but that's 100% against Maven style). So you have to go through mvn:install... If, after two or three years or so, one of my internal customer approaches me and says, ok, have you worked this or that project I always say, there have been more important things, then they say, yes, I understand that, but 3 years and never had time ? Come on !
This is not the appropriate place for this conversation, so I shouldn't have brought it up. But your last comment suggests that you do have some misconceptions about how Maven works. Of course you can and should edit the POM to add your dependencies, and I'm not sure how you got it to work without doing so. Also, you only need to manually install a dep locally if the dep is not in any remote repository. In any case, there are much better alternatives, such as creating your own repository.
Fixed jet-main ac7d98ff7208
Integrated into 'main-golden' Changeset: http://hg.netbeans.org/main-golden/rev/ac7d98ff7208 User: Tomas Zezula <tzezula@netbeans.org> Log: #46863:Permit library names to contain spaces
*** Bug 199997 has been marked as a duplicate of this bug. ***
*** Bug 43601 has been marked as a duplicate of this bug. ***
*** Bug 185275 has been marked as a duplicate of this bug. ***