Grails

Building an application with an inline plugin fails to resolve dependency

Details

  • Type: Bug Bug
  • Status: Open Open
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 1.4-M1
  • Fix Version/s: 2.3-M2
  • Component/s: Build System
  • Labels:
    None

Description

After upgrading from 1.3.7 to 1.4 my applications that now share a common plugin constantly fail to build when using an inplace plugin.
The resulting error is that the plugin is not found when it clearly is in the defined path for the inplace plugin

grails.plugin.location.'myplugin'="../common/plugins/myplugin"

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Samuel Doyle added a comment -

In addition to the inline plugin there was also dependency on this defined in the plugins, this wasn't a problem in 1.3.7 but is now in 1.4.0.
I suppose this issue can be closed bit it means either removing or commenting out the dependency in the plugin section.

Show
Samuel Doyle added a comment - In addition to the inline plugin there was also dependency on this defined in the plugins, this wasn't a problem in 1.3.7 but is now in 1.4.0. I suppose this issue can be closed bit it means either removing or commenting out the dependency in the plugin section.
Hide
Permalink
Graeme Rocher added a comment -

Could you attach an example that reproduces the issue? we have some functional tests that verify inline plugins work so it must be something specific

Show
Graeme Rocher added a comment - Could you attach an example that reproduces the issue? we have some functional tests that verify inline plugins work so it must be something specific
Hide
Permalink
Angelo Alfano added a comment -

I have the same issue with 2.0.M1 (OSX 10.7.1) even with brand new 2.0 app and plugin, I attach an example

Show
Angelo Alfano added a comment - I have the same issue with 2.0.M1 (OSX 10.7.1) even with brand new 2.0 app and plugin, I attach an example
Hide
Permalink
Graeme Rocher added a comment -

I'm not sure I understand the issue. You are defining the plugin twice. Once in the plugins section and once as an inline plugin. If you remove the former declaration:

//        compile ":test-plg:0.1"

Then everything works as expected

Show
Graeme Rocher added a comment - I'm not sure I understand the issue. You are defining the plugin twice. Once in the plugins section and once as an inline plugin. If you remove the former declaration: // compile ":test-plg:0.1" Then everything works as expected
Hide
Permalink
Stéphane Maldini added a comment -

Status ?

Show
Stéphane Maldini added a comment - Status ?
Hide
Permalink
Graeme Rocher added a comment -

Stephane - as I said I don't regard this as a bug since if the plugin is inline you shouldn't define it in your plugins { } block

Show
Graeme Rocher added a comment - Stephane - as I said I don't regard this as a bug since if the plugin is inline you shouldn't define it in your plugins { } block

People

  • Assignee:
    Graeme Rocher
    Reporter:
    Samuel Doyle
Vote (3)
Watch (4)

Dates

  • Created:
    Updated:
    Last Reviewed: