[
https://issues.apache.org/jira/browse/LUCENE-3946?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13246534#comment-13246534
]
Hoss Man commented on LUCENE-3946:
----------------------------------
I added some starter text to
http://wiki.apache.org/lucene-java/HowToContribute#antivy
I also went ahead and commited the existing patch as is, minus the classpath
stuff, to the trunk: r1309511.
Anyone object to merging this back to 3.6?
--
bq. Commenting out "rpm_mode=true" in ant.conf made it work with just "ant
test" as the command.
Shawn: can you try reverting your change to /etc/ant.conf and instead add
"rpm_mode=false" to a new $HOME/.ant/ant.conf file and see if that works just
as well? ... if so we should add it to the wiki as a suggestion
> 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
> Reporter: Hoss Man
> Assignee: Hoss Man
> Fix For: 3.6, 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]
