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

D.K. | 5 Mar 23:22 2013
Picon

Ivy symlink creation under Windoozer(XP)

Hi,

There is a fixed issue record, related to Cygwin symlinks - 
https://issues.apache.org/jira/browse/IVY-1165, saying that symlinks 
under windows are not supported properly. So Ivy doesn't establish them, 
but copies jars instead.

But would be nice to have creation of symbolic links under Windoozer(XP) 
customizable, to be able to use e.g. Masatoshi Kimura's

<http://schinagl.priv.at/nt/hardlinkshellext/hardlinkshellext.html#symboliclinksforwindowsxp> 
symbolic link driver(and accompanying ln.exe command line tool).
These symlinks are handled by file system filter driver, so other 
programs(e.g. javac.exe) believe they're accessing file the link points 
to. And hard links under windows are also possible at least since 
win2000 (called "junction points"|, fsutil hardlink create| ${lnk} ${file}).

Thanks,
Dmitriy
Jean-Louis Boudart | 5 Mar 08:00 2013
Picon

Fwd: [ANNOUNCE] Apache EasyAnt 0.9-incubating released

The Apache EasyAnt project is pleased to announce its 0.9-incubating
release.

Apache Easyant is a toolbox focusing on easing project build processes.
It's based on Apache Ant and Apache Ivy, and allows for maximum flexibily,
improved integration in existing build systems and provides conventions and
guidelines.

Our goals are :

   - to leverage popularity and flexibility of Ant.
   - to integrate Apache Ivy, such that the build system combines a
   ready-to-use dependency manager.
   - to simplify standard build types, such as building web applications,
   JARs etc, by providing ready to use builds.
   - to provide conventions and guidelines.
   - to make plugging-in of fresh functionalities as easy as writing Ant
   scripts.

To still remain adaptable,

   - Though EasyAnt comes with a lot of conventions, we never lock you in.
   - EasyAnt allows you to easily extend existing modules or create and use
   your own modules.
   - EasyAnt makes migration from Ant very simple. Your legacy Ant scripts
   could still be leveraged using EasyAnt.

Key features of this 0.9-incubating release are :

   - dynamic project lifecycle to remain even more flexible (get rid of
   phases in favor of extension point)
   - enhanced multimodule support
   - enhanced exception handling
   - support for offline mode
   - new command line switches and related api to list and describe
   targets, properties, extensionPoints and even parameters (path, filesets)
   - plugin dependencies can be overridden in module descriptors
   - a set of new ant tasks to make plugin writer life easier
   - a lighter distribution with only core plugins/buildtypes
   - online repository for others plugins/buildtypes/skeletons
   - upgrade to Apache Ant 1.8.4 and Apache Ivy 2.3.0
   - numerous bug fixes as documented in Jira and in the release notes

This is the first EasyAnt release under Apache Software Foundation.

You can download this 0.9-incubating release at:
http://incubator.apache.org/easyant/download.cgi

Issues should be reported to:
https://issues.apache.org/jira/browse/EASYANT

More information can be found on the website:
http://incubator.apache.org/easyant/

Regards,
--

-- 
Jean Louis Boudart
Matt Spaulding | 27 Feb 19:53 2013
Picon

Using classifiers with the install task

Hi,

I'm trying to use the ant install task to install a module with a
classifier. When pulling the module in as a dependency, I use the following
in my ivy.xml:

    <dependency org="net.sf.json-lib" name="json-lib" rev="2.2.2"
        transitive="false" force="true">
        <artifact name="json-lib" type="jar" ext="jar"
m:classifier="jdk15"/>
    </dependency>

And this works fine for dependency retrieval, but what is the equivalent
when using the install task? I know the install task does not understand
the artifact tag. Also, I've tried the following which does not work either:

<ivy:install organisation="net.sf.json-lib" module="json-lib"
revision="2.2.2" m:classifier="jdk15" from="${from.repo}" to="${to.repo}"/>

Any help is appreciated!

Regards,
Matt
Edwin Park | 22 Feb 23:30 2013

Classifiers not working with embedded ivy:resolve dependencies

Hi,

I noticed that when using the new <ivy:resolve> child elements that were introduced in 2.3, classifier
resolution no longer works. For example:

build.xml:

<ivy:resolve>
  <dependency org="org.zeromq" name="jzmq" rev="2.1.0">
    <artifact name="jzmq" type="source" ext="jar" m:classifier="sources"/>
  </dependency>
</ivy:resolve>

ivysettings.xml:

<ivysettings>
  <settings defaultResolver="nexus" />
  <resolvers>
    <ibiblio name="nexus" m2compatible="true"
      root="http://nexus.local:8082/nexus/content/groups/all"
      pattern="[organisation]/[module]/[revision]/[artifact]-[revision](-[m:classifier]).[ext]">
    </ibiblio>
  </resolvers>
</ivysettings>

What winds up happening is that the *binary* jar is getting downloaded and placed in the sources directory,
instead of the source jar. It essentially seems like the classifier parameter is not passed along to the resolver.

The workaround is to not use the dependency child elements and revert to using an external ivy.xml again.

Edwin

Lewis John Mcgibbney | 22 Feb 22:56 2013
Picon

rev="latest.integration" not new enough

Hi Everyone,

I have an issue where I wish to use the most recent snapshot from here [0]
when sourcing the dependencies for another project.
If you look at [0] you'll see that there are various SNAPSHOT's available.
I wish to pull the 'very' latest one e.g. an irtifact which looks like this
gora-cassandra-0.3-20130222.081353-236.jar<https://repository.apache.org/content/repositories/snapshots/org/apache/gora/gora-cassandra/0.3-SNAPSHOT/gora-cassandra-0.3-20130222.081353-236.jar>
Simply put, these are nightly build artifacts and are the result of work we
are doing elsewhere. We wish to use these in the upstream application.
I've therefore configured the following

*ivysettings.xml*
------------------
<property name="snapshot.apache.org"
    value="https://repository.apache.org/content/repositories/snapshots/"
    override="false"/>
  <property name="maven2.pattern"
    value="[organisation]/[module]/[revision]/[module]-[revision]"/>
  <property name="maven2.pattern.ext"
    value="${maven2.pattern}.[ext]"/>
...
<resolvers>
    <ibiblio name="maven2"
      root="${repo.maven.org}"
      pattern="${maven2.pattern.ext}"
      m2compatible="true"
      />
    <ibiblio name="apache-snapshot"
      root="${snapshot.apache.org}"
      pattern="${maven2.pattern.ext}"
      m2compatible="true"
      />
...
<chain name="external-and-snapshots">
      <resolver ref="maven2"/>
      <resolver ref="apache-snapshot"/>
      <resolver ref="sonatype"/>
    </chain>
...
<module organisation="org.apache.gora" name=".*"
resolver="external-and-snapshots"/>

*ivy.xml*
---------
dependency org="org.apache.gora" name="gora-cassandra"
rev="latest.integration" conf="*->default" />

*PROBLEMS*

1) My first problem is that when I look at the latest.integration version
of the above SNAPSHOT in my ~/.ivy2/cache, I see that it is actually not
the latest.integration revision as the artifact pattern does not reflect
the latest one.

I observe the artifact
<info organisation="org.apache.gora" module="gora-cassandra"
revision="0.3-SNAPSHOT" status="integration" publication="20120723224854">
when what I want is
<info organisation="org.apache.gora" module="gora-cassandra"
revision="0.3-SNAPSHOT-20130222.081353-236" status="integration"
publication="${yesterday_evening}">

Does this therefore suggest that I need to change the pattern value for Ivy
to specifically fetch the most recent SNAPSHOT as desired?

2) I get the following rather unsavoury output when I try to compile

[ivy:resolve] :::: WARNINGS
[ivy:resolve]         module not found:
me.prettyprint#hector-core;working <at> CEE279Law3-Linux
[ivy:resolve]     ==== local: tried
[ivy:resolve]
/home/law/.ivy2/local/me.prettyprint/hector-core/working <at> CEE279Law3-Linux
/ivys/ivy.xml
[ivy:resolve]       -- artifact
me.prettyprint#hector-core;working <at> CEE279Law3-Linux!hector-core.jar:
[ivy:resolve]
/home/law/.ivy2/local/me.prettyprint/hector-core/working <at> CEE279Law3-Linux
/jars/hector-core.jar
[ivy:resolve]     ==== maven2: tried
[ivy:resolve]
http://repo1.maven.org/maven2/me/prettyprint/hector-core/working <at> CEE279Law3-Linux/hector-core-working-d/F0BIhpj9LHLNLUs9Uo7fVggsSHAxu7 <at> public.gmane.org
[ivy:resolve]       -- artifact
me.prettyprint#hector-core;working <at> CEE279Law3-Linux!hector-core.jar:
[ivy:resolve]
http://repo1.maven.org/maven2/me/prettyprint/hector-core/working <at> CEE279Law3-Linux/hector-core-working-d/F0BIhpj9LHLNLUs9Uo7X4FKtcOg5+q <at> public.gmane.org
[ivy:resolve]     ==== sonatype: tried
[ivy:resolve]
http://oss.sonatype.org/content/repositories/releases/me/prettyprint/hector-core/working <at> CEE279Law3-Linux/hector-core-working-d/F0BIhpj9LHLNLUs9Uo7fVggsSHAxu7 <at> public.gmane.org
[ivy:resolve]       -- artifact
me.prettyprint#hector-core;working <at> CEE279Law3-Linux!hector-core.jar:
[ivy:resolve]
http://oss.sonatype.org/content/repositories/releases/me/prettyprint/hector-core/working <at> CEE279Law3-Linux/hector-core-working-d/F0BIhpj9LHLNLUs9Uo7X4FKtcOg5+q <at> public.gmane.org
[ivy:resolve]         ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]         ::          UNRESOLVED DEPENDENCIES         ::
[ivy:resolve]         ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]         :: me.prettyprint#hector-core;working <at> CEE279Law3-Linux:
not found
[ivy:resolve]         ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:resolve]
[ivy:resolve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS

Can someone therefore advise if my ivy.xml conf value is appropriate in
order to fetch all of the depedencies for the SNAPSHOT which I grab above?

[0]
https://repository.apache.org/content/repositories/snapshots/org/apache/gora/gora-cassandra/0.3-SNAPSHOT/

Thank you so much to anyone able to give me a hand on this one. It os
greatly appreciated.
Looking forward to meeting with anyone heading to ApacheCon in Portland
next week... Oh and I'll certainly be up for buying beers for anyone who
can help me out ;)
Best
Lewis

--

-- 
*Lewis*
Richard | 18 Feb 19:10 2013

Using Maven Repo

Hi,
 
I'm working in an environment where I use both Ant / Ivy and Maven.
 
I don't want to have a separate Maven repository and Ivy cache with all of the libs duplicated on my machine.
 
I've configured Caches like this
 <
    ivyPattern="[organisation]/[module]/[revision]/ivy-[revision].xml"
    artifactPattern="[organisation]/[module]/[revision]/[artifact]-[revision].[ext]"/>
 
which is nearly what I want. The issue is that spring for example is stored in org.springframework folder
rather than org/springframework folders.
 
Can anyone point out where I'm going wrong?
 
Many thanks.
 
Ric.cachesdefaultCacheDir="Path_to/.m2/repository" 

Gmane