[
https://issues.apache.org/jira/browse/LUCENE-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hoss Man updated LUCENE-3946:
-----------------------------
Attachment: LUCENE-3946.patch
patch that updates the ivy-availability-check to include:
* a mention of --noconfig
* a link to the wiki (where we'd need to add some content)
* an echo of the classpath
...i'm using ${java.class.path} here because from what i can tell doing testing
with "-nouserlib" that's the right classpath to look at -- but i'm a little
worried based on Shawn's comment in LUCENE-3930 that when he added an echo of
${java.class.path} he did in fact see the ~/.ant/lib jar in there.
I'm hoping Shawn and McCandless (who also mentioned being able to reproduce
this with a stock Fedora install of ant) can verify that they get
consistent/useful behavior when running things like...
* "ant --noconfig resolve" (should work for anyone using default ant)
* "ant resolve" (should work for most, but expect to fail on these fedora
systems because of packaged /etc/ant.conf, but our failure message should show
a classpath that clearly indicates ~/.ant/lib/ivy.jar isn't in there)
* "ant --noconfig resolve" (should work for anyone)
* "ant -nouserlib resolve" (should fail for anyone, our failure message should
show a classpath that clearly indicates ~/.ant/lib/ivy.jar isn't in there)
> 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]
