You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Shawn Heisey (JIRA)" <ji...@apache.org> on 2013/06/06 18:39:19 UTC
[jira] [Commented] (LUCENE-5043) Eclipse project name change -
autogenerated
[ https://issues.apache.org/jira/browse/LUCENE-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13677213#comment-13677213 ]
Shawn Heisey commented on LUCENE-5043:
--------------------------------------
The first option has an advantage over the second - you could have multiple copies of the same version (such as trunk) imported into eclipse at the same time. It would be easier to work on more than one issue without juggling projects. For that reason, I would prefer that option.
I did wonder what happens if you change a project name outside of eclipse, so I tried editing .project. Eclipse doesn't notice the change, even if you shut it down and restart it. I don't think that will be a disadvantage for option 1, because the only way the project name would change is if you move the project or rename the directory, in which case you'd have to re-import it into eclipse anyway.
> 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
>
>
> 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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org