I reply on the user list as this topic belong there.
On Jun 2, 2008, at 8:30 PM, JerodLass wrote:
I have a project (rather, a set of projects) in the structure:
-Dprojectcategory
-Dproject1
-Dsrc
-Dmain
..
..
..
-Dproject2
-Dsrc
-Dmain
..
..
..
-Dcommon-files
-Dlib
..
..
I'm trying to build these projects using gradle (just project1 for
now, but
you may hear more from me later), and I need to resolve
dependencies on the
jars in common-files/lib, which do not all have versioning
information.
What would be the best way to go about this?
Options:
-The ClientModule resolver doesn't seem to be doing much at all
-Default build-resolver checks [group]/[name]/[version]/[type] for
the jar.
Remapping this to a specific directory or adding it to a classpath
somewhere
may work.
-The flatDirResolver can get to the directory and find a jar with a
specified version number, but for non-versioned jars it blanks
because of a
concatenated -.
dependencies {
addFlatDirResolver('common', new File(rootDir, 'common-files/
lib')).addArtifactPattern('[artifact].[ext]')
}
This should do the job. I had no time to try this out though.
The addFlatDirResolver return an Ivy object of type
FileSystemResolver. addArtifactPattern is a method of this type.
- Hans
Any thoughts on this issue would be much appreciated.
--
View this message in context: http://www.nabble.com/dependency-
resolving-tp17607356p17607356.html
Sent from the gradle-dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
--
Hans Dockter
Gradle Project lead
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
