[
https://issues.apache.org/jira/browse/BUILDR-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristof Jozsa updated BUILDR-465:
---------------------------------
Attachment: eclipsenames.patch
Patch attached with:
- added project.eclipse.name property which defaults to project.id
- project.eclipse.name is used for .project and .classpath generation
- specs covering updated functionality
> Eclipse project names should be customizable
> --------------------------------------------
>
> Key: BUILDR-465
> URL: https://issues.apache.org/jira/browse/BUILDR-465
> Project: Buildr
> Issue Type: Improvement
> Components: IDE
> Reporter: Kristof Jozsa
> Attachments: eclipsenames.patch
>
>
> Buildr-generated Eclipse project descriptors enforce a
> "ParentProject-Subproject" naming convention for each subproject when
> generating .classpath files with dependent subprojects. This might not fit
> everyone (including myself), so:
> - the buildfile should be able to specify the eclipse project name explicitly
> for each specified project, and/or
> - there should be an option to use a non-prefixed project name
> Personally I think the first option is more flexible but both could work. The
> .classpath generation part which is involved in the issue is around line 334
> in eclipse.rb in the current buildr gem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
