rpmbuild vs apache-ivy
 

Hi,

I use Apache Solr4 on my organization, and plan pack it on a RPM and
share with the Community.


Sorry if my question is dumb, but I already read FAQs, docs, Google, and
can't solve it alone...


I did a specfile to build it, but the build.xml uses apache-ivy to
resolve deps, and it automatically tries to download required libraries.
I've put "BuildRequires" clauses on specfile, but I don't know how to made

to Ivy use installed libraries instead of download them.

An example: build needs
apache-commons-codec-1.6. This package are installed, and contains the
following files:

/usr/share/doc/apache-commons-codec-1.6
/usr/share/doc/apache-commons-codec-1.6/LICENSE.txt
/usr/share/doc/apache-commons-codec-1.6/NOTICE.txt
/usr/share/doc/apache-commons-codec-1.6/RELEASE-NOTES.txt
/usr/share/java/apache-commons-codec.jar
/usr/share/java/commons-codec.jar
/usr/share/maven-fragments/apache-commons-codec
/usr/share/maven-poms/JPP-commons-codec.pom

But when I try call "ant dist" from rpmbuild it fails with this message:

(...)
resolve:
[ivy:retrieve]
[ivy:retrieve] :: problems summary ::
[ivy:retrieve] :::: WARNINGS
[ivy:retrieve] module not found: commons-codec#commons-codec;1.6
[ivy:retrieve] ==== local: tried
[ivy:retrieve]
/home/fabiano/.ivy2/local/commons-codec/commons-codec/1.6/ivys/ivy.xml
[ivy:retrieve] -- artifact
commons-codec#commons-codec;1.6!commons-codec.jar:
[ivy:retrieve]
/home/fabiano/.ivy2/local/commons-codec/commons-codec/1.6/jars/commons-codec.jar

[ivy:retrieve] ==== shared: tried
[ivy:retrieve]
/home/fabiano/.ivy2/shared/commons-codec/commons-codec/1.6/ivys/ivy.xml
[ivy:retrieve] -- artifact
commons-codec#commons-codec;1.6!commons-codec.jar:
[ivy:retrieve]
/home/fabiano/.ivy2/shared/commons-codec/commons-codec/1.6/jars/commons-codec.jar

[ivy:retrieve] ==== public: tried
[ivy:retrieve]
http://repo1.maven.org/maven2/commons-codec/commons-codec/1.6/commons-codec-1.6.pom
[ivy:retrieve] -- artifact
commons-codec#commons-codec;1.6!commons-codec.jar:
[ivy:retrieve]
http://repo1.maven.org/maven2/commons-codec/commons-codec/1.6/commons-codec-1.6.jar

[ivy:retrieve] ==== sonatype-releases: tried
[ivy:retrieve]
http://oss.sonatype.org/content/repositories/releases/commons-codec/commons-codec/1.6/commons-codec-1.6.pom
[ivy:retrieve] -- artifact
commons-codec#commons-codec;1.6!commons-codec.jar:
[ivy:retrieve]
http://oss.sonatype.org/content/repositories/releases/commons-codec/commons-codec/1.6/commons-codec-1.6.jar

[ivy:retrieve] ==== working-chinese-mirror: tried
[ivy:retrieve]
http://mirror.netcologne.de/maven2/commons-codec/commons-codec/1.6/commons-codec-1.6.pom
[ivy:retrieve] -- artifact
commons-codec#commons-codec;1.6!commons-codec.jar:
[ivy:retrieve]
http://mirror.netcologne.de/maven2/commons-codec/commons-codec/1.6/commons-codec-1.6.jar

[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve] :: UNRESOLVED DEPENDENCIES ::
[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve] :: commons-codec#commons-codec;1.6: not found
[ivy:retrieve] ::::::::::::::::::::::::::::::::::::::::::::::
[ivy:retrieve] :::: ERRORS
[ivy:retrieve] Server access Error: Connection timed out
url=http://repo1.maven.org/maven2/commons-codec/commons-codec/1.6/commons-codec-1.6.pom
[ivy:retrieve] Server access Error: Connection timed out
url=http://repo1.maven.org/maven2/commons-codec/commons-codec/1.6/commons-codec-1.6.jar
[ivy:retrieve] Server access Error: Connection timed out
url=http://oss.sonatype.org/content/repositories/releases/commons-codec/commons-codec/1.6/commons-codec-1.6.pom
[ivy:retrieve] Server access Error: Connection timed out
url=http://oss.sonatype.org/content/repositories/releases/commons-codec/commons-codec/1.6/commons-codec-1.6.jar
[ivy:retrieve] Server access Error: Connection timed out
url=http://mirror.netcologne.de/maven2/commons-codec/commons-codec/1.6/commons-codec-1.6.pom
[ivy:retrieve] Server access Error: Connection timed out
url=http://mirror.netcologne.de/maven2/commons-codec/commons-codec/1.6/commons-codec-1.6.jar

[ivy:retrieve]
[ivy:retrieve] :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS

BUILD FAILED
/home/fabiano/rpmbuild/BUILD/branch_4x/solr/common-build.xml:320: The
following error occurred while executing this line:
/home/fabiano/rpmbuild/BUILD/branch_4x/lucene/module-build.xml:208: The
following error occurred while executing this line:
/home/fabiano/rpmbuild/BUILD/branch_4x/lucene/common-build.xml:287:
impossible to resolve dependencies:

resolve failed - see output for details

--
Fabiano Martins
Unidade de Aplicativos e Internet
Divisão de Informática
MPRS

--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel

rpmbuild vs apache-ivy
 

Forgot to send to java-devel as well, sorry for the double email
Fabiano.

Quoting Fabiano Martins (2012-06-26 18:51:23)
> Hi,
>
> I use Apache Solr4 on my organization, and plan pack it on a RPM and
> share with the Community.
>
> Sorry if my question is dumb, but I already read FAQs, docs, Google, and
> can't solve it alone...
>
> I did a specfile to build it, but the build.xml uses apache-ivy to
> resolve deps, and it automatically tries to download required libraries.
> I've put "BuildRequires" clauses on specfile, but I don't know how to made
> to Ivy use installed libraries instead of download them.
>
> [snip]
> But when I try call "ant dist" from rpmbuild it fails with this message:
> [snip]

Basically, your fastest/easiest bet is to look at packages that already
use apache-ivy and see how they deal with it:

$ repoquery --repoid=rawhide-source --archlist=src --whatrequires apache-ivy
ant-contrib-0:1.0-0.16.b3.fc17.src
groovy-0:1.8.6-4.fc18.src
ironjacamar-0:1.0.9-3.fc18.src
papaki-0:1.0.0-0.1.Beta3.fc18.src

So have a look at those spec files to get an idea. Ivy mostly just looks
at a certain cache location to see if a required file is there and if
so, uses it.

You seem to be in "a bit" different timezone, but quite a lot of java
folks are on #fedora-java @ freenode (IRC) during EMEA business hours.
You might have luck outside that time as well though if you have
specific questions.

--
Stanislav Ochotnicky <sochotnicky@redhat.com>
Software Engineer - Base Operating Systems Brno

PGP: 7B087241
Red Hat Inc. http://cz.redhat.com
--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel

rpmbuild vs apache-ivy
 

Thank you a lot: I'll study these examples.

Em 28-06-2012 05:43, Stanislav Ochotnicky escreveu:

Forgot to send to java-devel as well, sorry for the double email
Fabiano.

Quoting Fabiano Martins (2012-06-26 18:51:23)

Hi,

I use Apache Solr4 on my organization, and plan pack it on a RPM and
share with the Community.

Sorry if my question is dumb, but I already read FAQs, docs, Google, and
can't solve it alone...

I did a specfile to build it, but the build.xml uses apache-ivy to
resolve deps, and it automatically tries to download required libraries.
I've put "BuildRequires" clauses on specfile, but I don't know how to made
to Ivy use installed libraries instead of download them.

[snip]
But when I try call "ant dist" from rpmbuild it fails with this message:
[snip]

Basically, your fastest/easiest bet is to look at packages that already
use apache-ivy and see how they deal with it:

$ repoquery --repoid=rawhide-source --archlist=src --whatrequires apache-ivy
ant-contrib-0:1.0-0.16.b3.fc17.src
groovy-0:1.8.6-4.fc18.src
ironjacamar-0:1.0.9-3.fc18.src
papaki-0:1.0.0-0.1.Beta3.fc18.src

So have a look at those spec files to get an idea. Ivy mostly just looks
at a certain cache location to see if a required file is there and if
so, uses it.

You seem to be in "a bit" different timezone, but quite a lot of java
folks are on #fedora-java @ freenode (IRC) during EMEA business hours.
You might have luck outside that time as well though if you have
specific questions.



--
Fabiano Martins
Unidade de Aplicativos e Internet
Divisão de Informática
MPRS

--
java-devel mailing list
java-devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/java-devel