Reboot required for new jars in /lib?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Reboot required for new jars in /lib?

barnesjd
I've noticed that if I add a jar to my application's lib directory, I have to reboot my PC for the classes to resolve.  This occurred while trying to use the postgresql driver jar.  I tried restarting the app, restarting grails, and cleaning the app.  Only an OS reboot fixed it.

My environment:
Grails 2.0.1
Java 1.7.0_02-b13
Windows 7 Home Premium, SP1
Postgresql 9.1

Is this expected behavior?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Reboot required for new jars in /lib?

Octavian Covalschi
no, it's not an expected behavior

what happens if you use install-dependency script? and restart grails/app

example: grails install-dependency mysql:mysql-connector-java:5.1.16 --dir=lib

http://grails.org/doc/2.0.x/ref/Command%20Line/install-dependency.html 

On Wed, Feb 22, 2012 at 4:53 PM, barnesjd <[hidden email]> wrote:
I've noticed that if I add a jar to my application's lib directory, I have to
reboot my PC for the classes to resolve.  This occurred while trying to use
the postgresql driver jar.  I tried restarting the app, restarting grails,
and cleaning the app.  Only an OS reboot fixed it.

My environment:
Grails 2.0.1
Java 1.7.0_02-b13
Windows 7 Home Premium, SP1
Postgresql 9.1

Is this expected behavior?

--
View this message in context: http://grails.1312388.n4.nabble.com/Reboot-required-for-new-jars-in-lib-tp4412083p4412083.html
Sent from the Grails - user mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Reboot required for new jars in /lib?

robelsner
In reply to this post by barnesjd

Not at all.  I run windows7 pro, but grails 1.3.7 and jvm6.  I will try your config here in a bit.  You should double check it isn't getting odd permissions and that you can see it from the command prompt without elevated privs

Do you use the command prompt or some other shell?

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Reboot required for new jars in /lib?

Jason Davis
doing

example: grails install-dependency mysql:mysql-connector-java:5.1.16 --dir=lib

does not address the lib dir problem. Just skirts around it.

On Wed, Feb 22, 2012 at 4:07 PM, Rob Elsner <[hidden email]> wrote:
> Not at all.  I run windows7 pro, but grails 1.3.7 and jvm6.  I will try your
> config here in a bit.  You should double check it isn't getting odd
> permissions and that you can see it from the command prompt without elevated
> privs
>
> Do you use the command prompt or some other shell?

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Reboot required for new jars in /lib?

barnesjd
Ok, I didn't know that I was supposed to use that install-dependency command.  I thought I could just copy the jars into the lib directory.  Other than avoiding a reboot, why does it need a command rather than just dropping it off like I did?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Reboot required for new jars in /lib?

Steven Grossman
Loading...