Quantcast

Grails 2.1 Unable to resolve class from 3rd party jar in lib directory

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

Grails 2.1 Unable to resolve class from 3rd party jar in lib directory

qiang
Hi all,

After I put a 3rd party jar in lib directory of a brand new Grails 2.1
application,  in a controller class,
I use import statement to import  a class in that jar, then run-app
with the following error:

D:\work\helloworld\grails-app\controllers\helloworld\HelloController.groovy: 4:
unable to resolve class com.sap.mw.jco.About
 @ line 4, column 1.
   import com.sap.mw.jco.About
   ^

Is this a bug or feature of Grails 2.1?

---------------------------------------------------------------------
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: Grails 2.1 Unable to resolve class from 3rd party jar in lib directory

Graeme Rocher-2
Run grails refresh-dependencies first

-- 
Graeme Rocher

On Sunday, July 22, 2012 at 11:48 AM, qiang wrote:

Hi all,

After I put a 3rd party jar in lib directory of a brand new Grails 2.1
application, in a controller class,
I use import statement to import a class in that jar, then run-app
with the following error:

D:\work\helloworld\grails-app\controllers\helloworld\HelloController.groovy: 4:
unable to resolve class com.sap.mw.jco.About
@ line 4, column 1.
import com.sap.mw.jco.About
^

Is this a bug or feature of Grails 2.1?

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


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

Re: Grails 2.1 Unable to resolve class from 3rd party jar in lib directory

qiang
Thansk, It works!

But I think the Grails Reference Guide need some more explanation
about this in Section 4.3:

"If you can't use Ivy then just put the JAR in your project's lib directory."

2012/7/23 Graeme Rocher <[hidden email]>:

> Run grails refresh-dependencies first
>
> --
> Graeme Rocher
>
> On Sunday, July 22, 2012 at 11:48 AM, qiang wrote:
>
> Hi all,
>
> After I put a 3rd party jar in lib directory of a brand new Grails 2.1
> application, in a controller class,
> I use import statement to import a class in that jar, then run-app
> with the following error:
>
> D:\work\helloworld\grails-app\controllers\helloworld\HelloController.groovy:
> 4:
> unable to resolve class com.sap.mw.jco.About
> @ line 4, column 1.
> import com.sap.mw.jco.About
> ^
>
> Is this a bug or feature of Grails 2.1?
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
> http://xircles.codehaus.org/manage_email
>
>

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

    http://xircles.codehaus.org/manage_email


Loading...