[
https://issues.apache.org/jira/browse/LUCENE-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Heisey resolved LUCENE-5043.
----------------------------------
Resolution: Fixed
Jenkins never sent me any direct email, and the jenkins maven failures that I
saw looked like the failures that have been happening for quite some time now,
so I have backported this to 4x, commit r1490726.
> Eclipse project name change - autogenerated
> -------------------------------------------
>
> Key: LUCENE-5043
> URL: https://issues.apache.org/jira/browse/LUCENE-5043
> Project: Lucene - Core
> Issue Type: Improvement
> Components: general/build
> Affects Versions: 4.3
> Reporter: Shawn Heisey
> Assignee: Shawn Heisey
> Priority: Minor
> Fix For: 5.0, 4.4
>
> Attachments: LUCENE-5043.patch, LUCENE-5043.patch
>
>
> The eclipse project name (created by 'ant eclipse') for most of the 4.x
> versions comes up as "lucene_solr_branch_4x" ... which causes a few problems.
> Recently I needed to take a look at a particular class in Solr 4.2.1, 4.3.0,
> and branch_4x. I couldn't load all three projects into Eclipse at the same
> time, because they have the same project name. Even if I could have, it
> would have been very confusing. I would like to improve this situation for
> the future.
> I have a couple of ideas right up front, both of which seem like reasonable
> ways to go:
> 1) Use the directory name, similar to what IntelliJ Idea does.
> 2) Use the "fakeReleaseVersion" property in the central build.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
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]
