You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Antoine Toulme (JIRA)" <ji...@apache.org> on 2010/01/15 05:42:54 UTC
[jira] Updated: (BUILDR-361) Improve the eclipse task for projects
for which no natures are found
[ https://issues.apache.org/jira/browse/BUILDR-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antoine Toulme updated BUILDR-361:
----------------------------------
Summary: Improve the eclipse task for projects for which no natures are found (was: Improve the eclipse task for projects for which no natures is found)
Editing the issue... adding a thought too, this won't work well in one case: I don't think we want to generate a .project file for project that have children projects. For those projects, I would disable the .project creation right away.
> Improve the eclipse task for projects for which no natures are found
> --------------------------------------------------------------------
>
> Key: BUILDR-361
> URL: https://issues.apache.org/jira/browse/BUILDR-361
> Project: Buildr
> Issue Type: Improvement
> Components: IDE
> Affects Versions: 1.3.5
> Reporter: Antoine Toulme
> Fix For: 1.4
>
> Attachments: buildr-361
>
>
> If no nature is found, that doesn't mean the project cannot be an eclipse project.
> Right now, if the nature cannot be derived from the compile language, no .project file is created.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.