On 16/03/10 3:31 PM, Geronimo M. H. wrote:
Hello,
thank you for your support.
...
repositories {
add(new org.apache.ivy.plugins.resolver.FileSystemResolver()) {
name = 'local'
addArtifactPattern(new File('common/3rdParty').getAbsolutePath()
+ '/([organization]/)[module]/[artifact](-[revision])
(-[classified]).
[ext]')
}
}
Ok, I got a bit further with this too, but I did not find a way to
specify a module-name. I guess, the organisation is mapped to the
group-id and artifact is the name ...
You specify the name in the dependency:
dependencies {
compile group: 'group', name: 'module', version: 'version'
compile 'group:module:version' // the short form
}
We map group -> ivy organization, name -> ivy module, version -> ivy
revision
So this is my misunderstanding, as I thought, the module would be different
from the artifact in the ivy-pattern. May be, I should make the module-part
optional.
One library I was not able to bring into play, so I had to rename its
directory.
What was it's name? what sort of error message did you get?
I have different paths:
/jgoodies/binding/binding-2.0.6.jar
which worked with the ivy pattern and
/Project-X/ProjectX.jar
which did not work with the ivy pattern from above.
In what way did it not work? Do you have some error messages? Stack traces?
It already does this. If you add a project dependency to the compile
configuration, for example, then the compileJava task will depend on the
jar task from the other project.
What did you see that made you think that the dependencies were not
being added?
Ok - then I beg your pardon.
I'll gonna remove all duplicated dependencies and try again.
You generally need to drain the child process' output stream, as well as
the error stream, to stop the child process from hanging. This is a
standard Java Process behaviour, and nothing really to do with Gradle.
You might have a look at http://groovy.codehaus.org/groovy-jdk/ to see
some of the extra methods which Groovy adds to Process to make it easier
to work with.
Thanks for that link.
I think the biggest point of my misunderstanding is sourced from the late
binding of the closures. I think, I'll have to do some groovy exercises
outside of gradle ...
Do you have any advices on how to write the dependencies for the toplevel
project of the mixed project?
Could you explain in a bit more detail what you're trying to achieve?
--
Adam Murdoch
Gradle Developer
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
