Justin Teems | 3 May 18:41 2013

Installation troubles.

Hi folks,

I'm having trouble getting Ivy installed properly on my system. I've 
followed the instructions here 
http://ant.apache.org/ivy/history/2.2.0/install.html,

* Downloaded the tarball
* placed ivy-2.3.0.jar in /usr/share/ant/lib/

When I run ant from the $HOME/ivy/src/example/hello-ivy directory, I get 
the following:

Buildfile: build.xml

resolve:

BUILD FAILED
/home/jteems/src/repos/build/apache-ivy-2.3.0/src/example/hello-ivy/build.xml:38: 
Problem: failed to create task or type antlib:org.apache.ivy.ant:retrieve
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.
No types or tasks have been defined in this namespace yet

This appears to be an antlib declaration.
Action: Check that the implementing library exists in one of:
         -/usr/share/ant/lib
         -/home/jteems/.ant/lib
         -a directory added on the command line with the -lib argument
(Continue reading)

Justin Teems | 3 May 19:08 2013

Installation Troubles...

Hi folks,

I'm having trouble getting Ivy installed properly on my system. I've 
followed the instructions here 
http://ant.apache.org/ivy/history/2.2.0/install.html,

* Downloaded the tarball
* placed ivy-2.3.0.jar in /usr/share/ant/lib/

When I run ant from the $HOME/ivy/src/example/hello-ivy directory, I get 
the following:

Buildfile: build.xml

resolve:

BUILD FAILED
/home/jteems/src/repos/build/apache-ivy-2.3.0/src/example/hello-ivy/build.xml:38: 
Problem: failed to create task or type antlib:org.apache.ivy.ant:retrieve
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any <presetdef>/<macrodef> declarations have taken place.
No types or tasks have been defined in this namespace yet

This appears to be an antlib declaration.
Action: Check that the implementing library exists in one of:
         -/usr/share/ant/lib
         -/home/jteems/.ant/lib
         -a directory added on the command line with the -lib argument
(Continue reading)

Zachary Bedell | 2 May 17:25 2013

Multiple release "streams" for different JDK's?

Greetings all,

We're in the process of migrating our enterprise between Java versions.  We're at 6 presently and are moving
to either 7 or 8, depending on time frame, Oracle's release schedule, etc.

We have a number of in-house libraries which we compile and publish to our private Ivy repository.  We'll
need to compile those libs with the new JDK version going forward, but for an extended period of time we'll
also need to maintain versions compiled with JDK 6 so that our many projects can migrate as their schedules
permit.  Until we're able to fully retire Java 6 (likely at least a year), we'll end up with something like
the following for every build of our libraries:

ourOrg#ourLib;DEV-12345 (JRE 6 version)
ourOrg#ourLib;DEV-12345 (JRE 7 version)

(Where the 12345 is currently the SVN rev the build was created from.)

I'm not sure how best to model the JRE version into Ivy's view of our artifacts.  It's not valid to consider the
JRE 7 version an "upgrade" to the 6 version, so it's not something that would increment or otherwise
contribute to the version number.  Especially, we wouldn't want projects using floating revisions
(latest.integration) to switch from one JRE version to the other without explicit action taken by the developer.

I'm leery of renaming the modules (ourLib-7) for several reasons.  First, I expect the dependency tree
would be horribly broken as we have interlocking dependencies between our in-house libraries, and
changing them all recursively would be a nightmare.  Additionally while the -7 case is the exception for
the time being, it would eventually become the norm, and I'd prefer not to have a vestigial -7 stuck on the
release names forever (or have to undertake a second module name change to remove the -7).

We're not currently using Ivy's branch tracking feature for anything, and I'm curious if this might be an
appropriate use case for it.  While ultimately the two versions are built of the same source tree (so not a
branch in the SCM sense), I think it might work for projects desiring the JRE-7 builds to apply a branch to
(Continue reading)

Carsten.Pfeiffer | 29 Apr 18:10 2013
Picon

deliver overwriting the source ivy.xml

Hi,

Is there a way to prevent the <deliver> (<publish>) task from overwriting 
the source ivy.xml file?

I have a bunch of project directories like this

projectx
  - src
  - dist
  - ivy.xml

Now when I publish these projects, the original ivy.xml is being 
overwritten with the resolved version:
[ivy:publish]   delivering ivy file to 
/home/carsten/projects/projectx/ivy.xml

How can I keep my original version untouched and let Ivy deliver somewhere 
else? Or do I have to copy the ivy.xml
to a temporary location (i.e. dist directory) and let it deliver/publish 
from there?

Thanks
Carsten
 
Rodrigue ... | 28 Mar 06:11 2013

Mailing list still alive?

Hi

I just want to know whether this mailing list is still alive.

Since my registration last week I didn't receive any emails; Maybe I did
something wrong during the registration process.

Thank you

Rodrigue
Rodrigue ... | 25 Mar 11:48 2013

problem with ivyDE in newer version of eclipse

Hi all,

my projects are all using an ivysettings file located on a server protected
with http-authentication. This means that credentials are needed to get
access on both ivysettings and artifacts.

For the newest version of both ivy and ivyDE, I experienced the following
results:

With eclipse JUNO SR1, ivyDE prompts a dialog to request the user's
credentials. After that everything work properly on the Ubuntu Platform,
and didn't on the Microsoft windows platform (Not able to parse the
ivysettings.xml).

Beginning with eclipse JUNO SR2, the dialog to ask for the credentials is
no more prompted by ivyDE, therefore the ivysettings file couldn't be
downloaded.

Am I doing something wrong, or we are facing here a known bug?

Any help will be appreciated.

Thanks
Rodrigue ... | 22 Mar 19:08 2013

problem with ivyDE in newer version of eclipse

Hi all,

my projects are all using an ivysettings file located on a server protected
with http-authentication. This means that credentials are needed to get
access on both ivysettings and artifacts.

For the newest version of both ivy and ivyDE, I experienced the following
results:

With eclipse JUNO SR1, ivyDE prompts a dialog to request the user's
credentials. After that everything work properly on the Ubuntu Platform,
and didn't on the Microsoft windows platform (Not able to parse the
ivysettings.xml).

Beginning with eclipse JUNO SR2, the dialog to ask for the credentials is
no more prompted by ivyDE, therefore the ivysettings file couldn't be
downloaded.

Am I doing something wrong, or we are facing here a known bug?

Any help will be appreciated.

Thanks
Rodrigue
Carsten.Pfeiffer | 20 Mar 16:01 2013
Picon

AUTO: Carsten Pfeiffer ist außer Haus (returning 25.03.2013)


I am out of the office until 25.03.2013.

In dringenden Fällen, kontaktieren Sie bitte
Erwin<punkt>Tratar<at>gebit<punkt>de oder
Tom<punkt>Krauss<at>gebit<punkt>de.

Note: This is an automated response to your message  "Replace transitive
dependency specific version with another version" sent on 20.03.2013
15:21:51.

This is the only notification you will receive while this person is away.

Jean-Noël Rouvignac | 20 Mar 15:21 2013

Replace transitive dependency specific version with another version

Hello,

I have a little problem with Ivy for which I have not been able to find a solution.
it all comes from the fact I can only use java 6 compatible jars, yet some of the jars down below have different compatibilities.


grizzly 2.3-rc6 (java 6 compatible) depends on javax.servlet-api 3.1-b05 (not java 6 compatible), so I want to use javax.servlet-api 3.1-b02 (java 6 compatible) to circumvent the compatibility issues.
Despite numerous attempts, I have not been able to make this happen.

I have tried to use global excludes, dependency excludes, matcher, version matchers, but Ivy  always manages to download the wrong version of javax.servlet-api.


I have used the attached files to reproduce this problem.
Does anybody have an idea on how I can modify the files to make it work the way I want?


Many thanks,
Jean-Noel
Attachment (build.xml): text/xml, 1677 bytes
Attachment (ivy.xml): text/xml, 644 bytes
Attachment (ivysettings.xml): text/xml, 312 bytes
Hans Lund | 15 Mar 14:43 2013

ivy:publish on ivy-2.3.0

Hi 

After upgrading from ivy-2.2.0 to ivy-2.3.0 I'm running into problems with ivy:publish.

The problem is that after the upgrade, the revisions in the published ivy.xml no longer is the same as the
ones resolved.
Of cause this only happens in conjunction with conflict resolving (and perhaps only when using latest
strategies) not really tested that.
The effect is that  trying to compile the published artifact source artifact can't compile, using the
published ivy - but can using my source ivy.

I'm not sure if this is a bug or change of behavior eg:

Does publish use a configuration and do an internal resolve? or does it use latest resolve ? Has that changed.

Best Regards
Hans Lund  

Tim Enderling | 7 Mar 13:00 2013
Picon

Multiple dependency-elements for the same module/organization

Hi,

is there anything in Ivy that forbids/discourages double declarations like this? (A short test
indicates, that Ivy seems ok with that.) 

...
<dependencies>
    <dependency org="com.acme" name="module" rev="1.0.0" conf="compile"/>
    <dependency org="com.acme" name="module" rev="1.0.0" conf="runtime"/>
    <dependency org="com.acme" name="module" rev="1.0.0" conf="runtime"/>
    <dependency org="com.acme" name="module" rev="1.0.1" conf="runtime"/>
</dependencies>
...

Background: I'd like to generate some dependencies at build time and don't want to dive into the details of
merging a possibly existing declaration with the generated ones.

Best Regards,
Tim Enderling


Gmane