[
http://jira.codehaus.org/browse/MECLIPSE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Freeman updated MECLIPSE-445:
---------------------------------
Attachment: MECLIPSE-445.zip
The modified SpringBeanWriter can now find spring config files using the
project root as the starting point for the search rather than the current
working directory. The MyEclipse test case has been changed log each test to
it's own file in the same way the rad and Eclipse tests do. There is also a
test case that shows that this works. The eclipse-plugin testing framework
does not recurse down to sub projects/modules when comparing results so the
test results must be compared manually.
> myeclipse target doesn't generate spring bean files for hierarchical projects.
> ------------------------------------------------------------------------------
>
> Key: MECLIPSE-445
> URL: http://jira.codehaus.org/browse/MECLIPSE-445
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: MyEclipse support
> Affects Versions: 2.5.1
> Reporter: Joe Freeman
> Assignee: Arnaud Heritier
> Fix For: 2.5.2
>
> Attachments: MECLIPSE-445.zip
>
>
> The spring bean file creation code doesn't works only when the current
> working directory is the same as the project directory. This means it works
> fine for single level projects. We have an n-deep hierarchy of projects
> where we run the eclipse:eclipse and eclipse:myeclipse targets from the top.
> In this situation, the cwd doesn't change as it traverses the hierarchy so
> absolute paths must be used for navigation and then trimmed when the actual
> fiile references are put in the spring beans file. I have a patch for this
> but don't yet have a standalone test case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
