[ 
https://issues.apache.org/jira/browse/LUCENE-6174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Dawid Weiss updated LUCENE-6174:
--------------------------------
    Attachment: LUCENE-6174.patch

I think this can be hardcoded in {{dot.classpath.xsl}} (to be 1.7 in branch_5x 
and 1.8 in trunk).

This declaration declares an "execution environment" which one can then define 
in Eclipse settings to be any available 1.8-compatible JVM:
{code}
  <classpathentry kind="con" 
path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.8"/>
{code}

> Improve "ant eclipse" to select right JRE for building
> ------------------------------------------------------
>
>                 Key: LUCENE-6174
>                 URL: https://issues.apache.org/jira/browse/LUCENE-6174
>             Project: Lucene - Core
>          Issue Type: Improvement
>          Components: general/build
>            Reporter: Uwe Schindler
>            Assignee: Uwe Schindler
>         Attachments: LUCENE-6174.patch
>
>
> Whenever I run "ant eclipse" the setting choosing the right JVM is lost and 
> has to be reassigned in the project properties.
> In fact the classpath generator writes a new classpath file (as it should), 
> but this onl ycontains the "default" entry:
> {code:xml}
> <classpathentry kind="con" path="org.eclipse.jdt.launching.JRE_CONTAINER"/>
> {code}
> Instead it should preserve something like:
> {code:xml}
> <classpathentry kind="con" 
> path="org.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/jdk1.8.0_25"/>
> {code}
> We can either path this by a Ant property via command line or user can do 
> this with "lucene/build.properties" or per user. An alternative would be to 
> generate the name "jdk1.8.0_25" by guessing from ANT's "java.home". If this 
> name does not exist in eclipse it would produce an error and user would need 
> to add the correct JDK.
> I currently have the problem that my Eclipse uses Java 7 by default and 
> whenever I rebuild the eclipse project, the change to Java 8 in trunk is gone.
> When this is fixed, I could easily/automatically have the "right" JDK used by 
> eclipse for trunk (Java 8) and branch_5x (Java 7).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to