Relationship between dependencies.groovy and BuildConfig.groovy

View: New views
4 Messages — Rating Filter:   Alert me  

Relationship between dependencies.groovy and BuildConfig.groovy

by Jean Barmash :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
Hello,

With 1.2 adding more rigorous dependency resolution, I am confused between the roles for plugin's dependencies.groovy and BuildConfig.groovy. 

Is dependencies.groovy only for plugins, and BuildConfig only for apps?    I run a bunch of custom plugins inline (i.e. in .\plugins dir), and want to switch between using them as plugins, and using them as applications.   So I've been maintaining almost identical files for each one of them for each plugin, which is clearly not DRY.   

I wonder if one of these files is extra though and if there is a way to reference one file from the other perhaps.


Jean 

Re: Relationship between dependencies.groovy and BuildConfig.groovy

by Graeme Rocher-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

dependencies.groovy should never be used/edited and is created from a
plugin projects BuildConfig.groovy during the package-plugin target

Cheers

On Sun, Nov 8, 2009 at 3:07 PM, Jean Barmash <barmash@...> wrote:

> Hello,
> With 1.2 adding more rigorous dependency resolution, I am confused between
> the roles for plugin's dependencies.groovy and BuildConfig.groovy.
> Is dependencies.groovy only for plugins, and BuildConfig only for apps?    I
> run a bunch of custom plugins inline (i.e. in .\plugins dir), and want to
> switch between using them as plugins, and using them as applications.   So
> I've been maintaining almost identical files for each one of them for each
> plugin, which is clearly not DRY.
> I wonder if one of these files is extra though and if there is a way to
> reference one file from the other perhaps.
>
> Jean



--
Graeme Rocher
Head of Grails Development
SpringSource - A Division of VMware
http://www.springsource.com

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

    http://xircles.codehaus.org/manage_email



Re: Relationship between dependencies.groovy and BuildConfig.groovy

by Jean Barmash :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.
Thanks.  If I have a local custom plugin (projectdir/plugins directory, location specified in projects's BuildConfig.groovy), do I need to run package-plugin every time its dependencies change?   Or is there a special handling for those plugins?

Jean


From: Graeme Rocher <graeme.rocher@...>
To: user@...
Sent: Sun, November 8, 2009 9:26:12 AM
Subject: Re: [grails-user] Relationship between dependencies.groovy and BuildConfig.groovy

dependencies.groovy should never be used/edited and is created from a
plugin projects BuildConfig.groovy during the package-plugin target

Cheers

On Sun, Nov 8, 2009 at 3:07 PM, Jean Barmash <barmash@...> wrote:

> Hello,
> With 1.2 adding more rigorous dependency resolution, I am confused between
> the roles for plugin's dependencies.groovy and BuildConfig.groovy.
> Is dependencies.groovy only for plugins, and BuildConfig only for apps?    I
> run a bunch of custom plugins inline (i.e. in .\plugins dir), and want to
> switch between using them as plugins, and using them as applications.   So
> I've been maintaining almost identical files for each one of them for each
> plugin, which is clearly not DRY.
> I wonder if one of these files is extra though and if there is a way to
> reference one file from the other perhaps.
>
> Jean



--
Graeme Rocher
Head of Grails Development
SpringSource - A Division of VMware
http://www.springsource.com

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

    http://xircles.codehaus.org/manage_email



Re: Relationship between dependencies.groovy and BuildConfig.groovy

by Graeme Rocher-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

There is special handling

Cheers

On Sun, Nov 8, 2009 at 3:50 PM, Jean Barmash <barmash@...> wrote:

> Thanks.  If I have a local custom plugin (projectdir/plugins directory,
> location specified in projects's BuildConfig.groovy), do I need to run
> package-plugin every time its dependencies change?   Or is there a special
> handling for those plugins?
> Jean
> ________________________________
> From: Graeme Rocher <graeme.rocher@...>
> To: user@...
> Sent: Sun, November 8, 2009 9:26:12 AM
> Subject: Re: [grails-user] Relationship between dependencies.groovy and
> BuildConfig.groovy
>
> dependencies.groovy should never be used/edited and is created from a
> plugin projects BuildConfig.groovy during the package-plugin target
>
> Cheers
>
> On Sun, Nov 8, 2009 at 3:07 PM, Jean Barmash <barmash@...> wrote:
>> Hello,
>> With 1.2 adding more rigorous dependency resolution, I am confused between
>> the roles for plugin's dependencies.groovy and BuildConfig.groovy.
>> Is dependencies.groovy only for plugins, and BuildConfig only for apps?
>>  I
>> run a bunch of custom plugins inline (i.e. in .\plugins dir), and want to
>> switch between using them as plugins, and using them as applications.   So
>> I've been maintaining almost identical files for each one of them for each
>> plugin, which is clearly not DRY.
>> I wonder if one of these files is extra though and if there is a way to
>> reference one file from the other perhaps.
>>
>> Jean
>
>
>
> --
> Graeme Rocher
> Head of Grails Development
> SpringSource - A Division of VMware
> http://www.springsource.com
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>



--
Graeme Rocher
Head of Grails Development
SpringSource - A Division of VMware
http://www.springsource.com

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

    http://xircles.codehaus.org/manage_email