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 197971 - libraries in library manager do not reflect glassfish instance building against
Summary: libraries in library manager do not reflect glassfish instance building against
Status: RESOLVED FIXED
Alias: None
Product: serverplugins
Classification: Unclassified
Component: GlassFish (show other bugs)
Version: 7.0
Hardware: PC Windows 7 x64
: P3 normal (vote)
Assignee: TomasKraus
URL:
Keywords:
: 198029 (view as bug list)
Depends on: 196466 196127
Blocks:
  Show dependency tree
 
Reported: 2011-04-21 22:07 UTC by emiddio
Modified: 2013-04-03 15:07 UTC (History)
4 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description emiddio 2011-04-21 22:07:36 UTC 
i have glassfish 3.1b37 and gfv3.1 instances;
also have glassfish V2.x -- gfv2ur2, gfv211 instances.
also have glassfish v3.0.1 gfv301 instance;

all registered with netbeans ide 7.0

some of my projects require jersey 1.5 version -- which is part of gfv3.1x,
and not part of glassfish v3.01;

I usually like to build my projects against gfv3.01 -- but when i choose
a library to add to my web project -- for example restlib_gfv3ee6,
or Javae-EE-Glassfish-V3 -- the location of the jar files is not related to
the app-server version chosen for my project -- currently netbeans is always
using my gfv31b37 instance location jarfiles -- that instance appears
last in my server instance list in netbeans.

apparantly i will have to use the default jar file list for these 2 libraries
as a template to build "custom" libraries associated with different
glassfish version install instances.

also -- if i remove or add a new gfv3.x server -- its unpredictable what
netbeans will then use for the 2 library names mentioned in this report.
Comment 1 David Konecny 2011-05-19 21:33:38 UTC 
(In reply to comment #0)
> some of my projects require jersey 1.5 version -- which is part of gfv3.1x,
> and not part of glassfish v3.01;

What do you think about this issue Vince? My opinion is that if content of restlib_gfv3ee6 or Javae-EE-Glassfish-V3 library is different in different versions of GlassFish then two (or more) different libraries should be setup by GlassFish. Overriding content of single library by latest version of GF(?) or by latest installed version of GF(?) is quite unpredictable.
Comment 2 Vince Kraemer 2011-05-19 21:58:00 UTC 
dkonecny: been there (create multiple libraries). done that. told "don't do that" (reverted to a single library).

This reads similar to issue 196127...

I am waiting to hear what the plan is for issue 196466 and how that will affect the serverplugins.
Comment 3 David Konecny 2011-05-20 02:11:17 UTC 
restlib library issue will be resolve by issue 196127. I'm not sure about second library.
Comment 4 Denis Anisimov 2011-05-22 14:28:59 UTC 
I believe David meant issue #196468 and issue #196469.

So the REST jars now are added based on library registered by GF or
as a list of jars ( not in the library ) if library doesn't match.

The problem actually is pretty much the same as I've reported here : 
issue #196127.

But I agree with Vince : restlib_gfv3ee6 library will go away when we resolve
the issue #196466. Current issue will just disappear .
Comment 5 Vince Kraemer 2012-05-25 03:56:06 UTC 
*** Bug 198029 has been marked as a duplicate of this bug. ***
Comment 6 TomasKraus 2013-04-03 15:07:04 UTC 
Currently library name contains GlassFish server display name as part of it's own display name so it's possible to use more Jersey libraries from more GlassFish servers.

I'm closing this issue because it was already resolved in NetBeans 7.3.1