On Tue, May 26, 2009 at 2:19 AM, Hans Dockter <[email protected]> wrote:

>
> On May 25, 2009, at 7:54 PM, Luke Taylor wrote:
>
>  You can use the ant support, for example:
>>
>> task getJython << {
>>   ant.get(src: '
>> http://downloads.sourceforge.net/jython/jython_installer-2.5rc2.jar',
>> dest: 'jython-installer.jar')
>> }
>>
>
> Alternatively you could use the Gradle dependency management.
>
> configurations {
>        jython
> }
>
> dependencies {
>        jython "jython:jython_installer:2.5rc2"
> }
>
> repositories {
>        add(new org.apache.ivy.plugins.resolver.URLResolver()) {
>              name = "python_sf" // For non standard resolvers the name is
> required
>              addArtifactPattern("http://downloads.sourceforge.net/
> [organisation]/[artifact]-[revision].[ext]")
>        }
> }
>
> task resolve << {
>        println configurations.jython.resolve()
> }
>
> This will of course also cache the jython jar automatically.
>
> In the future we will provide our own domain objects for repositories. ATM
> you have to use the native Ivy ones.


Very cool, that's what I'm actually just tinkering with.

What I'm currently toying with is the following workflow

( is this an 'init' task?)
    - create dependency on jython (jython.jar and jython-lib.jar, or
together?)
    - create an adhoc resolver for Ivy that downloads the Jython Jar if the
appropriate version is not found

    - run on top of jython (delegate) from here
    - create zc.buildout (setuptools) execution point
    - execute zc.buildout (dependencies) to download eggs into local cache
(build dir?)
    - bind from gradle to buildout
    (zc.buildout can be under the covers (assemble the config))
    - if requested explicitly, bind the script points to tasks (prefixed
with taskname-), so they can be executed.


this eventually would end in a Jython plugin. If you give me some pointers,
I'd actually try to tackle this.

What I have in mind eventually is to have something similar like the Buildr
hack from Daniel Spiewak, to support interactive shells with the full
dependency path.

I'm in coding mood, but I'm in unknown terrain. Any pointers appreciated...

[1]
http://www.codecommit.com/blog/java/hacking-buildr-interactive-shell-support
[2] http://github.com/djspiewak/buildr/tree/interactive-shell


>
> - Hans
>
> --
> Hans Dockter
> Gradle Project Manager
> http://www.gradle.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>   http://xircles.codehaus.org/manage_email
>
>
>

Reply via email to