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 Mon, 30 Oct 2017 22:00:41 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=115&rev2=116

Comment:
Added note about ant on redhat.  Simplified mentions of required JDK versions to Java 8.

  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.
  
  == 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.
@@ -128, +129 @@

   * New unit tests should be provided to demonstrate bugs and fixes (http://www.junit.org).
  
  == Notes for Eclipse ==
- To get correct classpath, formatting, encoding, and project settings in Eclipse, simply
run {{{ant eclipse}}} and then reload the project in Eclipse.  Be sure that you are using
an appropriate version of the Java JDK.  For branch_5x, the minimum version is Java 7 (1.7.x),
for trunk (working towards 6.0), the minimum version is Java 8 (1.8.x).
+ To get correct classpath, formatting, encoding, and project settings in Eclipse, simply
run {{{ant eclipse}}} and then reload the project in Eclipse.  Be sure that you are using
an appropriate version of the Java JDK.  Solr has required Java 8 (1.8.x) since version 6.0.
  
  == Generating a patch ==
  A "patch file" is the conventional contribution mechanism.  It bundles up everything that
is being added, removed, or changed in your contribution.  You can instead do a GitHub pull
request, which is documented elsewhere on this apge; nevertheless most of this section is
still applicable.

Mime
View raw message