Grails 2.0.2, Unable to install downloaded plugins

[Sandro Martini]

Hi all,
just tried with some Grails webapps updated to 2.0.2 (and even with a new one, created from scratch with Grails-2.0.2), to install a plugin downloaded (for example copying its zip in root of the webapp folder), but I get always the same error (see bottom). I have not changed default repositories, ande even deleted completely my .grails and ivy-cache folders.
I'm on Windows.

The strange thing is that this is the same with my plugins (that has all required jars in main maven repository, and even in maven local repository), but even with others (for example just tried with the latest grails-codenarc-0.17.zip downloaded today.

Suggestions ?

Thank you very much,
Sandro

test>cls && grails install-plugin grails-codenarc-0.17.zip

| Environment set to development.....
:: problems summary ::
:::: WARNINGS
                ::::::::::::::::::::::::::::::::::::::::::::::

                ::          UNRESOLVED DEPENDENCIES         ::

                ::::::::::::::::::::::::::::::::::::::::::::::

                :: org.grails.plugins#codenarc;0.17: java.lang.NullPointerException at org.apache.ivy.plugins.resolver.AbstractResolver.initRepositoryCacheManagerFromSettings(AbstractResolver.java:396)

                ::::::::::::::::::::::::::::::::::::::::::::::


| Error Could not resolve all dependencies for plugin codenarc

[Sandro Martini]

Sorry, a quick note:
with Grails 2.0.1 all was working good ...

And last, for all plugins that are available online I know that as a workaround i could use that version, but mine are only local so that could be the only option for me.

And my plugins in "inline" mode (tested with a dedicated grails-2.0.x, now 2.0.2 webapp) works :-) .

Thanks again,
Sandro

[Sandro Martini]

Hi all,
some news/comment on this ?

I have just seen this issue (that seems related):
http://jira.grails.org/browse/GRAILS-8499

As a workaround I solved now (but with 2.0.3, no more on 2.0.2 now deleted in all my dev environments) adding a reference to the plugin in BuildConfig.groovy .

Thank you very much,
Sandro

[bobbywarner]

The "grails" command is run from the root of a project.  You said you put the plugin zip in the web-app folder.  So, you simply need to add the folder to the install-plugin command.

Instead of "grails install-plugin grails-codenarc-0.17.zip"  I think it would be "grails install-plugin web-app/grails-codenarc-0.17.zip"

I would not recommend using the install-plugin command though.  I would instead recommend listing your plugins in BuildConfig.groovy.

http://grails.org/doc/latest/guide/conf.html#pluginDependencies


Hope that helps!
Bobby

[bobbywarner]

I didn't see your last message before I sent mine.  Sounds like you already got it working by using BuildConfig. Great!

Yes, as you pointed out, there still is that issue with installing local zip plugins.


Thanks,
Bobby

[Sandro Martini]

Hi Bobby,
thank you very much for your help ... I found a workaround so it's good for me, but I think that 2.0.2 (maybe even 2.0.3) could have something broken inside on this, ny trouble here was to make you aware of this.

And last, if it would be better to not use anymore the install-plugin command, why not make it deprecated (in documentation, and maybe even with a messsage in Grails Console) ?
Maybe could help to avoid confusion ...

Thank you again for your help,
Sandro

[bobbywarner]

In Grails 2.1, it will in fact show an error if you try to use install-plugin in interactive mode.  You will still be able to use install-plugin in non-interactive mode though.

https://github.com/grails/grails-core/commit/15b5ab6cd6d3e4c60f2a618e5abde8688d0c109b

I agree that the docs should recommend listing in BuildConfig as opposed to install-plugin.  So, I updated the docs from "can" to "should" in the plugin dependencies section.  Let me know if this looks good or if you think it should be even more explicit.

https://github.com/pledbrook/grails-doc/commit/12d16abe696d6dd973f436a8ba4c06be99e9c861


Thanks,
Bobby

[Joe Little]

Actually installing local zipped plugins that one creates does not work, with the same NPE. Is there an existing JIRA for this... I'm not finding it.

So, it would appear that likely 2.0.1 is the only working edition for private plugins.

On Apr 4, 2012, at 5:44 AM, bobbywarner <[hidden email]> wrote:

> In Grails 2.1, it will in fact show an error if you try to use install-plugin
> in interactive mode.  You will still be able to use install-plugin in
> non-interactive mode though.
>
> https://github.com/grails/grails-core/commit/15b5ab6cd6d3e4c60f2a618e5abde8688d0c109b
>
> I agree that the docs should recommend listing in BuildConfig as opposed to
> install-plugin.  So, I updated the docs from "can" to "should" in the plugin
> dependencies section.  Let me know if this looks good or if you think it
> should be even more explicit.
>
> https://github.com/pledbrook/grails-doc/commit/12d16abe696d6dd973f436a8ba4c06be99e9c861
>
>
> Thanks,
> Bobby
>
> --
> View this message in context: http://grails.1312388.n4.nabble.com/Grails-2-0-2-Unable-to-install-downloaded-plugins-tp4528413p4532321.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
>
>

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

    http://xircles.codehaus.org/manage_email

[Joe Little]

To all, I have a JIRA up (6009) up for this issue. Seems like only
published plugins now work with grails until this is fixed

On Sat, Apr 7, 2012 at 10:05 PM, Joe Little <[hidden email]> wrote:

> Actually installing local zipped plugins that one creates does not work, with the same NPE. Is there an existing JIRA for this... I'm not finding it.
>
> So, it would appear that likely 2.0.1 is the only working edition for private plugins.
>
> On Apr 4, 2012, at 5:44 AM, bobbywarner <[hidden email]> wrote:
>
>> In Grails 2.1, it will in fact show an error if you try to use install-plugin
>> in interactive mode.  You will still be able to use install-plugin in
>> non-interactive mode though.
>>
>> https://github.com/grails/grails-core/commit/15b5ab6cd6d3e4c60f2a618e5abde8688d0c109b
>>
>> I agree that the docs should recommend listing in BuildConfig as opposed to
>> install-plugin.  So, I updated the docs from "can" to "should" in the plugin
>> dependencies section.  Let me know if this looks good or if you think it
>> should be even more explicit.
>>
>> https://github.com/pledbrook/grails-doc/commit/12d16abe696d6dd973f436a8ba4c06be99e9c861
>>
>>
>> Thanks,
>> Bobby
>>
>> --
>> View this message in context: http://grails.1312388.n4.nabble.com/Grails-2-0-2-Unable-to-install-downloaded-plugins-tp4528413p4532321.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
>>
>>

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

    http://xircles.codehaus.org/manage_email

[Joe Little]

Oops, the JIRA was 9006:

http://jira.grails.org/browse/GRAILS-9006

On Mon, Apr 9, 2012 at 2:59 PM, Joe Little <[hidden email]> wrote:

> To all, I have a JIRA up (6009) up for this issue. Seems like only
> published plugins now work with grails until this is fixed
>
> On Sat, Apr 7, 2012 at 10:05 PM, Joe Little <[hidden email]> wrote:
>> Actually installing local zipped plugins that one creates does not work, with the same NPE. Is there an existing JIRA for this... I'm not finding it.
>>
>> So, it would appear that likely 2.0.1 is the only working edition for private plugins.
>>
>> On Apr 4, 2012, at 5:44 AM, bobbywarner <[hidden email]> wrote:
>>
>>> In Grails 2.1, it will in fact show an error if you try to use install-plugin
>>> in interactive mode.  You will still be able to use install-plugin in
>>> non-interactive mode though.
>>>
>>> https://github.com/grails/grails-core/commit/15b5ab6cd6d3e4c60f2a618e5abde8688d0c109b
>>>
>>> I agree that the docs should recommend listing in BuildConfig as opposed to
>>> install-plugin.  So, I updated the docs from "can" to "should" in the plugin
>>> dependencies section.  Let me know if this looks good or if you think it
>>> should be even more explicit.
>>>
>>> https://github.com/pledbrook/grails-doc/commit/12d16abe696d6dd973f436a8ba4c06be99e9c861
>>>
>>>
>>> Thanks,
>>> Bobby
>>>
>>> --
>>> View this message in context: http://grails.1312388.n4.nabble.com/Grails-2-0-2-Unable-to-install-downloaded-plugins-tp4528413p4532321.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
>>>
>>>

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

    http://xircles.codehaus.org/manage_email

[Ian Roberts]

On 09/04/2012 22:59, Joe Little wrote:
> To all, I have a JIRA up (6009) up for this issue. Seems like only
> published plugins now work with grails until this is fixed

You may be able to work around it by specifying a flatDir repository in
your BuildConfig, dropping the plugin zips in there and using the
dependency mechanism to install them:

repositories {
  flatDir name:'local-plugins', dir:'/data/grails-plugins'
}

// package-plugin and then copy grails-foo-1.2.3.zip to
// /data/grails-plugins/foo-1.2.3.zip (without the "grails-")

plugins {
  compile ':foo:1.2.3'
}

(I've not checked the flatDir syntax, you may want to refer to the docs
to be sure)

Ian

--
Ian Roberts               | Department of Computer Science
[hidden email]  | University of Sheffield, UK

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

    http://xircles.codehaus.org/manage_email

[Joe Little]

I was about to get a variant of this working, using the relative 'lib'
directory, and placing my plugins with the prepended grails- name
removed from the plugin zip file name. What's with the generating of
plugins with the grails-* prepend anyways?

However, I'm hitting an altogether different issue with gorm dynamic
finders not being created for plugins with domains:

| Running Grails application
| Error 2012-04-10 10:02:44,697 [pool-7-thread-1] ERROR
context.GrailsContextLoader  - Error executing bootstraps:
groovy.lang.MissingMethodException: No signature of method: static
edu.stanford.ee.degreemgmt.ImportFile.findByShortName() is applicable
for argument types: (java.lang.String) values:
[gradDegProgSumStudPlan]
Message: groovy.lang.MissingMethodException: No signature of method:
static edu.stanford.ee.degreemgmt.ImportFile.findByShortName() is
applicable for argument types: (java.lang.String) values:
[gradDegProgSumStudPlan]
   Line | Method
->> 300 | evaluateEnvironmentSpecificBlock in grails.util.Environment
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|   293 | executeForEnvironment            in     ''
|   269 | executeForCurrentEnvironment . . in     ''
|   303 | innerRun                         in
java.util.concurrent.FutureTask$Sync
|   138 | run . . . . . . . . . . . . . .  in java.util.concurrent.FutureTask
|   886 | runTask                          in
java.util.concurrent.ThreadPoolExecutor$Worker
|   908 | run . . . . . . . . . . . . . .  in     ''
^   680 | run                              in java.lang.Thread

Caused by MissingMethodException: No signature of method: static
edu.stanford.ee.degreemgmt.ImportFile.findByShortName() is applicable
for argument types: (java.lang.String) values:
[gradDegProgSumStudPlan]
->>   6 | createInitialDataIfRequired      in
edu.stanford.ee.degreemgmt.DataBootstrapService
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
|    10 | doCall                           in BootStrap$_closure1
|   300 | evaluateEnvironmentSpecificBlock in grails.util.Environment
|   293 | executeForEnvironment            in     ''
|   269 | executeForCurrentEnvironment . . in     ''
|   303 | innerRun                         in
java.util.concurrent.FutureTask$Sync
|   138 | run . . . . . . . . . . . . . .  in java.util.concurrent.FutureTask
|   886 | runTask                          in
java.util.concurrent.ThreadPoolExecutor$Worker
|   908 | run . . . . . . . . . . . . . .  in     ''
^   680 | run                              in java.lang.Thread

Am I missing something here?

On Tue, Apr 10, 2012 at 2:46 AM, Ian Roberts <[hidden email]> wrote:

> On 09/04/2012 22:59, Joe Little wrote:
>> To all, I have a JIRA up (6009) up for this issue. Seems like only
>> published plugins now work with grails until this is fixed
>
> You may be able to work around it by specifying a flatDir repository in
> your BuildConfig, dropping the plugin zips in there and using the
> dependency mechanism to install them:
>
> repositories {
>  flatDir name:'local-plugins', dir:'/data/grails-plugins'
> }
>
> // package-plugin and then copy grails-foo-1.2.3.zip to
> // /data/grails-plugins/foo-1.2.3.zip (without the "grails-")
>
> plugins {
>  compile ':foo:1.2.3'
> }
>
> (I've not checked the flatDir syntax, you may want to refer to the docs
> to be sure)
>
> Ian
>
> --
> Ian Roberts               | Department of Computer Science
> [hidden email]  | University of Sheffield, UK
>
> ---------------------------------------------------------------------
> 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

[Joe Little]

grails clean mostly worked. Joda-time now messing with me. However,
wanted to report that the workaround does indeed work.

On Tue, Apr 10, 2012 at 10:10 AM, Joe Little <[hidden email]> wrote:

> I was about to get a variant of this working, using the relative 'lib'
> directory, and placing my plugins with the prepended grails- name
> removed from the plugin zip file name. What's with the generating of
> plugins with the grails-* prepend anyways?
>
> However, I'm hitting an altogether different issue with gorm dynamic
> finders not being created for plugins with domains:
>
> | Running Grails application
> | Error 2012-04-10 10:02:44,697 [pool-7-thread-1] ERROR
> context.GrailsContextLoader  - Error executing bootstraps:
> groovy.lang.MissingMethodException: No signature of method: static
> edu.stanford.ee.degreemgmt.ImportFile.findByShortName() is applicable
> for argument types: (java.lang.String) values:
> [gradDegProgSumStudPlan]
> Message: groovy.lang.MissingMethodException: No signature of method:
> static edu.stanford.ee.degreemgmt.ImportFile.findByShortName() is
> applicable for argument types: (java.lang.String) values:
> [gradDegProgSumStudPlan]
>   Line | Method
> ->> 300 | evaluateEnvironmentSpecificBlock in grails.util.Environment
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> |   293 | executeForEnvironment            in     ''
> |   269 | executeForCurrentEnvironment . . in     ''
> |   303 | innerRun                         in
> java.util.concurrent.FutureTask$Sync
> |   138 | run . . . . . . . . . . . . . .  in java.util.concurrent.FutureTask
> |   886 | runTask                          in
> java.util.concurrent.ThreadPoolExecutor$Worker
> |   908 | run . . . . . . . . . . . . . .  in     ''
> ^   680 | run                              in java.lang.Thread
>
> Caused by MissingMethodException: No signature of method: static
> edu.stanford.ee.degreemgmt.ImportFile.findByShortName() is applicable
> for argument types: (java.lang.String) values:
> [gradDegProgSumStudPlan]
> ->>   6 | createInitialDataIfRequired      in
> edu.stanford.ee.degreemgmt.DataBootstrapService
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> |    10 | doCall                           in BootStrap$_closure1
> |   300 | evaluateEnvironmentSpecificBlock in grails.util.Environment
> |   293 | executeForEnvironment            in     ''
> |   269 | executeForCurrentEnvironment . . in     ''
> |   303 | innerRun                         in
> java.util.concurrent.FutureTask$Sync
> |   138 | run . . . . . . . . . . . . . .  in java.util.concurrent.FutureTask
> |   886 | runTask                          in
> java.util.concurrent.ThreadPoolExecutor$Worker
> |   908 | run . . . . . . . . . . . . . .  in     ''
> ^   680 | run                              in java.lang.Thread
>
> Am I missing something here?
>
> On Tue, Apr 10, 2012 at 2:46 AM, Ian Roberts <[hidden email]> wrote:
>> On 09/04/2012 22:59, Joe Little wrote:
>>> To all, I have a JIRA up (6009) up for this issue. Seems like only
>>> published plugins now work with grails until this is fixed
>>
>> You may be able to work around it by specifying a flatDir repository in
>> your BuildConfig, dropping the plugin zips in there and using the
>> dependency mechanism to install them:
>>
>> repositories {
>>  flatDir name:'local-plugins', dir:'/data/grails-plugins'
>> }
>>
>> // package-plugin and then copy grails-foo-1.2.3.zip to
>> // /data/grails-plugins/foo-1.2.3.zip (without the "grails-")
>>
>> plugins {
>>  compile ':foo:1.2.3'
>> }
>>
>> (I've not checked the flatDir syntax, you may want to refer to the docs
>> to be sure)
>>
>> Ian
>>
>> --
>> Ian Roberts               | Department of Computer Science
>> [hidden email]  | University of Sheffield, UK
>>
>> ---------------------------------------------------------------------
>> 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