[
https://issues.apache.org/jira/browse/DAFFODIL-2454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276418#comment-17276418
]
Mike Beckerle commented on DAFFODIL-2454:
-----------------------------------------
I have discovered that in recreating an entirely new scalaIDE project, the
updateEclipseClasspaths tool doesn't seem to insert the necessary dependency of
all projects on the daffodil-macro-lib project.
If you manually edit the build path of each daffodil sub-project to add a
project dependency on daffodil-macro-lib. Then the projects will compile.
We need to fix the updateEclipseClasspaths functionality to insure it inserts
this project-to-project dependency, because it does not seem to be discovered
by sbt eclipse otherwise.
> Not able to Compile or Daffodil/stage daffodil 3.0.0
> ----------------------------------------------------
>
> Key: DAFFODIL-2454
> URL: https://issues.apache.org/jira/browse/DAFFODIL-2454
> Project: Daffodil
> Issue Type: Bug
> Components: Infrastructure
> Affects Versions: 3.0.0, 2.7.0
> Reporter: Susmita
> Assignee: Mike Beckerle
> Priority: Major
> Attachments: Stage error_07.docx
>
>
> Hi Steve,
> We were using daffodil 2.2.0, we want to upgrade the daffodil and do few
> changes to fix a bug and compile the project.
> we were able to do the compilation of version 2.2.0 and use it as required.
> The latest version 3.0.0 we are not able to do so.
> Used scala – : "scala-SDK-4.7.0-vfinal-2.12-win32" scala 2.11.
> Please Guide, what are the prerequisite and the steps to do the modification
> in version 3.0.0 and do the compilation and daffodil/stage successfully.
> Thanks & Regards
> Susmita
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
