Hi Xavier,
Can I provide any more info on this? Have you had a chance to look to
see what might be going on?
Thanks,
Neil
On Mar 9, 2008, at 12:48 PM, Neil Lott wrote:
Here are the ant files with the -d turned on and I removed the quite
mode on resolve.
The issue this time is with the joda-time dependency. Somehow I
cleared out my cache since the last time and now the oracle
dependency has been recognized in the test module.
Neil
On Mar 9, 2008, at 12:04 PM, Xavier Hanin wrote:
I can't help without your debug logs... BTW disable the quiet mode on
resolve to get as much logs as possible.
Xavier
2008/3/8 Neil Lott <[EMAIL PROTECTED]>:
Hi Xavier,
I tried this again and its not working. I added one dependency to
the
server module in the ivy.xml for oracle and my test module described
in ivytest.xml depends on the server and the new oracle dependency
jar
isn't being retrieved for the test. I've also included the xml
files
from each of my configured repositories.
Here's how I'm retrieve and resolving
<macrodef name="ivy-init">
<attribute name="ivy.file"/>
<attribute name="ivy.lib.dir"/>
<sequential>
<ivy:resolve file="@{ivy.file}" log="quiet"/>
<ivy:retrieve pattern="@{ivy.lib.dir}/[conf]/
[artifact]-
[revision].[ext]" symlink="true"/>
</sequential>
</macrodef>
Thank you for your help!
Neil
On Mar 8, 2008, at 2:25 AM, Xavier Hanin wrote:
On Fri, Mar 7, 2008 at 6:36 PM, Neil Lott
<[EMAIL PROTECTED]> wrote:
To clarify, I'm publishing the server artifact using the same
revision
-- here's my publish:
<ivy:publish artifactspattern="@{jar-dir}/[artifact]-[revision].
[ext]"
resolver="@{resolver}"
forcedeliver="true"
overwrite="true"
haltonmissing="false"/>
So since the revision number doesn't change on my artifact do I
need
to do something else to have the resolver recognized its changed?
You should just need checkmodified="true" (for Ivy to pick up
changes in
your published ivy file) and ensure the revision is changing (for
Ivy to
pick up changes in your artifacts). If it doesn't work, check your
debug
log, and post them here if you don't understand what's happening.
Xavier
Neil
On Mar 7, 2008, at 10:21 AM, Neil Lott wrote:
Hi Xavier,
I cleared out everything from ivy and recompiled all my modules
and
it picked up the new dependency.
However, I tried adding a new dependency in my server module
and my
test module isn't picking it up.
Here's my settings:
<ivysettings>
<settings defaultResolver="chained" checkUpToDate="true" />
<resolvers>
<chain name="chained">
<filesystem name="local" checkmodified="true">
<ivy pattern="${ivy.local.repository.dir
}/[organisation]/[module]/
[revision]/[module]-[revision].[ext]"/>
<artifact pattern="${ivy.local.repository.dir}/
[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"/>
</filesystem>
<filesystem name="shared" checkmodified="true">
<ivy pattern="${server.root
}/ivy/repository/[organisation]/
[module]/[revision]/[module]-[revision].[ext]"/>
<artifact pattern="${server.root}/ivy/repository/
[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"/>
</filesystem>
</chain>
</resolvers>
</ivysettings>
Neil
On Mar 7, 2008, at 7:05 AM, Xavier Hanin wrote:
On Fri, Mar 7, 2008 at 1:19 AM, Neil Lott
<[EMAIL PROTECTED]> wrote:
I have to modules
Here's my server module:
<ivy-module version="2.0">
<info organisation="${organization.name}" module="$
{server.jar.prefix}"/>
<configurations>
<conf name="server"/>
</configurations>
<publications>
<artifact name="${server.jar.prefix}" type="jar"
conf="server" ext="jar"/>
</publications>
<dependencies>
<dependency org="apache" name="mina" rev="$
{apache.mina.version}" conf="server->default"/>
<dependency org="logback" name="logback-core" rev="$
{logback.version}" conf="server->default"/>
<dependency org="logback" name="logback-classic" rev="$
{logback.version}" conf="server->default"/>
<dependency org="slf4j" name="slf4j" rev="${slf4j.version}"
conf="server->default"/>
<dependency org="apache" name="commons-configuration" rev="$
{commons.configuration.version}" conf="server->default"/>
<dependency org="spring" name="spring" rev="$
{spring.version}"
conf="server->default"/>
<dependency org="spring" name="spring-commons-
collections"
rev="$
{spring.version}" conf="server->default"/>
<dependency org="spring" name="spring-commons-dbcp"
rev="$
{spring.version}" conf="server->default"/>
<dependency org="spring" name="spring-commons-lang" rev="$
{spring.version}" conf="server->default"/>
<dependency org="spring" name="spring-commons-logging"
rev="$
{spring.version}" conf="server->default"/>
<dependency org="spring" name="spring-commons-pool"
rev="$
{spring.version}" conf="server->default"/>
<dependency org="spring" name="spring-ibatis" rev="$
{spring.version}" conf="server->default"/>
<dependency org="spring" name="spring-jta" rev="$
{spring.version}" conf="server->default"/>
<dependency org="spring" name="spring-quartz" rev="$
{spring.version}" conf="server->default"/>
<dependency org="jacorb" name="jacorb" rev="$
{jacorb.version}"
conf="server->default"/>
<dependency org="jacorb" name="jacorb" rev="$
{jacorb.version}"
conf="server->default"/>
<dependency org="jacorb" name="avalon-framework" rev="$
{avalon.framework.version}" conf="server->default"/>
<dependency org="jacorb" name="logkit" rev="$
{logkit.version}"
conf="server->default"/>
<dependency org="jacorb" name="antlr" rev="${antlr.version}"
conf="server->default"/>
</dependencies>
</ivy-module>
Here's my test module that test's the above
<ivy-module version="2.0">
<info organisation="${organization.name}" module="$
{ant.project.name}-test"/>
<configurations>
<conf name="test"/>
</configurations>
<dependencies>
<dependency org="twc" name="ondemandx" rev="${mas.version}"
conf="test->server"/>
<dependency org="jtestr" name="jtestr" rev="$
{jtestr.version}"
conf="test->default"/>
<dependency org="testng" name="testng" rev="$
{testng.version}"
conf="test->default"/>
</dependencies>
</ivy-module>
I just added the last five lines to the server module with the
jacorb
dependencies. These are getting picked up by the server, but
when I
run the resolve for my test module, they don't get picked
up. Any
ideas?
Maybe Ivy doesn't pick up the new metadata. Have you published a
new version
of your server module, or just updated the metdata? In the
latter
case, you
should use checkModified="true". See "Cache and Change
Management"
on main
concepts page.
Xavier
Neil
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://ant.apache.org/ivy/
http://www.xoocode.org/
