[
http://jira.codehaus.org/browse/MECLIPSE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=133045#action_133045
]
Joe Freeman commented on MECLIPSE-445:
--------------------------------------
It looks like the multi-level test cases are only validating the files at the
top level. project-34 in the test case suite should be failing because the
expected results in multymodule-1 do not match the generated files. A
.classpath is generated that is not in the expected directory and the generated
.project file does not match the one in the expected directory.
The test case should call compareDirectoryContent() on each sub-module.
> 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
>
>
> 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
