lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "HowToContribute" by ShawnHeisey
Date Wed, 06 Jun 2018 03:20:02 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "HowToContribute" page has been changed by ShawnHeisey:
https://wiki.apache.org/solr/HowToContribute?action=diff&rev1=120&rev2=121

Comment:
Better information about how to use a downloaded ant on redhat & derivatives.

  NOTE: If your build hangs when building and especially on a "resolve" step, it's probably
because there are left over lock files in your ivy directory (often because you crtl-c'd during
a build). To fix this navigate to your .ivy2 directory and delete all of the "*.lck" files
in the tree. For *nix operating systems, issue a command similar to:
  {{{find . -name "*.lck" | xargs rm}}}
  
- /!\ The "ant" package that is part of recent versions of Redhat Linux (and other operating
systems derived from Redhat, like CentOS) has some problems with Lucene/Solr source code.
 On these systems, downloading ant from Apache's website and manually installing it is necessary.
+ /!\ The "ant" package that is part of recent versions of Redhat Linux (and other operating
systems derived from Redhat, like CentOS) has some problems with Lucene/Solr source code.
 On these systems, downloading ant from Apache's website is necessary.  If the broken package
is installed,
+ you can type 'export ANT_HOME=/path/to/ant' at the bash prompt to point at the downloaded
version.  There's no need to put the downloaded directory on your PATH, you can use the ant
executable provided by the broken package.  The presence of the ANT_HOME variable will ignore
the broken package and fully switch ant over to the downloaded version.
  
  == Exporting to a local repository ==
  When making larger scale (please, try to keep your patches as small as humanly possible)
changes, or when working in a team, you might want to be able to keep track of what you are
doing locally. One way of doing so is to clone the lucene-solr repository and create a local
branch to which you can commit all your work. Another way is using Github to create a fork
of apache/lucene-solr and use that to commit code either individually or as a team. Once you
are ready, you can send a pull request to lucene-solr after creating an issue on the lucene-solr
Jira and mentioning the jira issue number in the pull request.

Mime
View raw message