I figured someone else had already started down that road.  I will take a
look and maybe see how I can fit that in.  I think it is definitely a
plugin worth investing in.  I thought of doing something as well but,
plugins aren't at the top of list of projects usually :).  This might be
good because it is something I can slowly iterate on.  I actually think
this is something a future version of Gradle should support because this is
going to be a sore spot in the future once we get awesome easy to manage
build scripts.

Jas

On Tue, May 22, 2012 at 12:49 PM, Robert Fischer <
[email protected]> wrote:

> I've got the DepNamePlugin which I was planning on spinning out into
> its own plugin and refining. For the moment, it's packaged into my
> gradle-plugins. It was intended to solve this bit of annoyance.
>
> https://github.com/RobertFischer/gradle-plugins
>
> ~~ Robert.
>
>
> On Tue, May 22, 2012 at 10:41 AM, Jason Hatton <[email protected]>
> wrote:
> > I guess I sent this by accident.  I hadn't finished my example on how to
> > share lists of dependences see the completed version here:
> >
> >
> >
> > On Tue, May 22, 2012 at 10:38 AM, Jason Hatton <[email protected]>
> wrote:
> >>
> >> I am curious about what others are doing in their projects to store
> common
> >> configuration values.  Please give feedback on your approaches and I
> welcome
> >> opinions on the approaches I am sharing here.
> >>
> >> ...
> >
> >
> >>
> >> capability.  I am considering something like below in either a
> >> gradle.properties or some sort of initializing gradle script.
> >>
> >> SPRING_API =  [[group: 'org.springframework', name: 'spring-context',
> >> version: "$SPRING_VERSION"],
> >>                          [group: 'org.springframework', name:
> >> 'spring-jdbc', version: "$SPRING_VERSION"]]
> >>
> >> Then it would be possible to do:
> >>
> >> dependencies {
> >>         compile { SPRING_API }
> >>
> >> }
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

Reply via email to