[
https://issues.apache.org/jira/browse/LUCENE-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246223#comment-13246223
]
Shawn Heisey commented on LUCENE-3946:
--------------------------------------
The broken ant in CentOS 6.2:
Apache Ant version 1.7.1 compiled on August 24 2010
I don't have a real RHEL 6.x to check this on, it's probably a different date.
Downloading, installing, and using ant 1.7.1 fixed it for me. I can actually
still call the /usr/bin/ant script in the regular path, but explicitly setting
ANT_HOME overrides what it actually uses. When I first found this problem, I
did install the apache-ivy package, then when that didn't work, I noticed the
ivy-bootstrap option.
Trying some of the workarounds mentioned resulted in an error:
ncindex@bigindy5 /index/src/trunk/solr $ ant --noconfig resolve
Error: Could not find or load main class org.apache.tools.ant.launch.Launcher
> 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]
