The first panel of Library Wrapper Module Project Wizard uses JTextField for
multiple files of libraries. There should be better to use JList for this purpose.
| jar1 | Add Button
| jar2 | Remove button
Perhaps. However the wizard does not encourage multiple JAR selections anyway;
it is usually not the best approach. Leaving TBD.
UI specs tells:
Library holds the path to a JAR file which the user can select with Browse…
(filter: *.jar,*.zip). Multiple JARs may also be selected.
A error message:
At least one library.jar needs to be specied.
Ok we don't need to implement it. So don't allow multiple jar support.
In the current spec (and I hope impl), it's *possible* to have a multiselection,
but it's not intended to be the common case.
*** Issue 63589 has been marked as a duplicate of this issue. ***
RE: "it's *possible* to have a multiselection".
1. If JARs are in differrent folder multi selection is not possible in the
2. It is not obvious that the set of JAR file paths can be typed in the
Libraries text field. The paths should be separated using
IMHO if it is possible but dicouraged then support the requested UI but have a
warning and/or info label. Also a dialog could be shown which tells the
reasons why this practice of multiple jars in a single LWMP is discouraged
with instructions/links to instructions of better approach. The dialog could
have a check box - "Don't show this message again".
It really does not seem logical to not allow multiple jars and discourage it in
all situations. By that I mean, in many applications the developer may want to
select all jars and simple dependencies as one library. Hibernate for instance
or something like it...pick any library. The point being not all development
will be done to support the IDE or for "everyone" to use as a plug-in/module, so
anything to make building simple applications easier and faster with the
platform needs to be looked at. If we want to have more users and an easier
entry point for new users then we really should focus on little issues as this.
On the screen where the library selections occur we can add a very visible text
pane with the message about why this is discouraged in most cases, and explain
the point of having multiple versions of libraries etc. At least this way
supports all use cases instead of a more narrowed view.
Often jars *need* to be grouped and treated as a single logical unit and it doesn't make sense to split
them up (Wade mentions Hibernate which is a good example). If people take this one-jar-per-wrapper
dogma too far, it increases the frustration of managing inter-dependencies between library wrapper
@jglick and @sandipchitale, its important to take a step back and consider what a turn-off Library Wrapper
Modules are for newcomers to NetBeans module/platform development. This one-jar-per-wrapper hang-
up is a symptom of the NetBeans developer fraternity ignoring usability and adoption concerns. Please see
my Feb 11 '07 email to firstname.lastname@example.org titled "Library Wrapper Modules: A major obstacle for