Hi Jerod,
On Jul 15, 2009, at 5:28 PM, JerodLass wrote:
Is there a way to prioritize the repository searching for
dependencies? Most
jars that the project I'm building needs are in a project flatDir
repository, but since I'm building outside of websphere and using
websphere
jars, I also added a few dependencies to jars that can be found in
another
local flatDir repository. Unfortunately, there are two different
jars of
the same name and I need the project's jar, which isn't the one being
grabbed. This isn't how I would like the build to be designed, but
it looks
to be what I'm stuck with.
How can I make sure it looks at the project repository first? It's
not as
simple as reversing the order of their declarations because they are
declared in different places.
Apologies for the late reply.
It is possible to solve this with Gradle. Have a look at the
ResolverContainer javadoc (repositories is an instance of
ResolverContainer). The only problem is that the convenience methods
flatDir, mavenCentral, etc. ..., do not provide arguments to make use
of the positioning API of the ResolverContainer. You may file a Jira
for this.
- Hans
--
Hans Dockter
Gradle Project Manager
http://www.gradle.org
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
