You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildr.apache.org by "Kristof Jozsa (JIRA)" <ji...@apache.org> on 2010/07/07 10:24:49 UTC
[jira] Created: (BUILDR-465) Eclipse project names should be
customizable
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
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.
[jira] Commented: (BUILDR-465) Eclipse project names should be
customizable
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12911015#action_12911015 ]
Hudson commented on BUILDR-465:
-------------------------------
Integrated in Buildr-ci-build #122 (See [https://hudson.apache.org/hudson/job/Buildr-ci-build/122/])
BUILDR-465 Eclipse project names should be customizable
BUILDR-509 Option to generate non-prefixed Eclipse project names
> 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
> Assignee: Alex Boisvert
> Fix For: 1.4.2
>
> 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.
[jira] Updated: (BUILDR-465) Eclipse project names should be
customizable
Posted by "Kristof Jozsa (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Resolved: (BUILDR-465) Eclipse project names should be
customizable
Posted by "Alex Boisvert (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BUILDR-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Boisvert resolved BUILDR-465.
----------------------------------
Assignee: Alex Boisvert
Fix Version/s: 1.4.2
Resolution: Fixed
Patch applied. Thanks Kristof!
Sending CHANGELOG
Sending lib/buildr/ide/eclipse.rb
Sending spec/ide/eclipse_spec.rb
Transmitting file data ...
Committed revision 998463.
> 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
> Assignee: Alex Boisvert
> Fix For: 1.4.2
>
> 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.