You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Eric Pugh (Updated) (JIRA)" <ji...@apache.org> on 2012/01/19 14:34:39 UTC
[jira] [Updated] (SOLR-3051) Solr 3.1 "ant eclipse" doesn't create
.project.
[ https://issues.apache.org/jira/browse/SOLR-3051?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eric Pugh updated SOLR-3051:
----------------------------
Attachment: dot.project
fix_eclipse.patch
Patch file and missing dot.project.
> Solr 3.1 "ant eclipse" doesn't create .project.
> -----------------------------------------------
>
> Key: SOLR-3051
> URL: https://issues.apache.org/jira/browse/SOLR-3051
> Project: Solr
> Issue Type: Bug
> Components: Build
> Affects Versions: 3.1
> Reporter: Eric Pugh
> Priority: Minor
> Attachments: dot.project, fix_eclipse.patch
>
>
> I know this is pretty small potatoes, but I went to apply a patch to some 3.1 code, and ran "ant eclipse", but my project didn't import cleanly. I had checked it out from the 3.1 branch in SVN. I checked and the eclipse .project file is missing.
> Not sure what the policy of updates to already released versions is when it's this minor? I'm tossing a patch file out here for 3.1.
> One thought I had is can we "version" the project name in the eclipse file when we branch? I typically have a couple of versions of Solr checked out, and I have to manually tweak them to have them all loaded in Eclipse. If this sounds like something that we want to add to the build, I can attach a ticket.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
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