[
https://issues.apache.org/jira/browse/LUCENE-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246052#comment-13246052
]
Sami Siren commented on LUCENE-3946:
------------------------------------
FWIW I am running Fedora 16. I did:
{code}
yum install ant ant-junit apache-ivy
ant clean test
{code}
I see warnings like:
{code}
[ivy:retrieve] impossible to define new type: class not found:
org.apache.ivy.plugins.signer.bouncycastle.OpenPGPSignatureGenerator in [] nor
Ivy classloader
{code}
and:
{code}
[junit] WARNING: multiple versions of ant detected in path for junit
[junit]
jar:file:/usr/share/java/ant.jar!/org/apache/tools/ant/Project.class
[junit] and
jar:file:/usr/share/ant/lib/ant.jar!/org/apache/tools/ant/Project.class
{code}
But the build works and there are no test failures (3.x, r1309249);
> improve docs & ivy verification output to explain classpath problems and
> mention "--noconfig"
> ---------------------------------------------------------------------------------------------
>
> Key: LUCENE-3946
> URL: https://issues.apache.org/jira/browse/LUCENE-3946
> Project: Lucene - Java
> Issue Type: Task
> Affects Versions: 3.6
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 4.0
>
> Attachments: LUCENE-3946.patch
>
>
> offshoot of LUCENE-3930, where shawn reported...
> {quote}
> I can't get either branch_3x or trunk to build now, on a system that used to
> build branch_3x without complaint. It
> says that ivy is not available, even after doing "ant ivy-bootstrap" to
> download ivy into the home directory.
> Specifically I am trying to build solrj from trunk, but I can't even get
> "ant" in the root directory of the checkout
> to work. I'm on CentOS 6 with oracle jdk7 built using the city-fan.org
> SRPMs. Ant (1.7.1) and junit are installed
> from package repositories. Building a checkout of lucene_solr_3_5 on the
> same machine works fine.
> {quote}
> The root cause is that ant's global configs can be setup to ignore the users
> personal lib dir. suggested work arround is to run "ant --noconfig" but we
> should also try to give the user feedback in our failure about exactly what
> classpath ant is currently using (because apparently ${java.class.path} is
> not actually it)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
