Closed GoogleCodeExporter closed 9 years ago
GoogleCodeExporter
commented
9 years ago I think I understand: it seems that, right now, the "Leinigen Dependencies
Classpath Container" is not marked as "exported to other projects". I'll try to
fix that in the sources.
In the mean time, you can try to fix this manually for your projects via the
java build path > Order and Export Tab.Original comment by laurent....@gmail.com on 8 Oct 2012 at 8:43
GoogleCodeExporter
commented
9 years ago Original comment by laurent....@gmail.com on 8 Oct 2012 at 8:57
GoogleCodeExporter
commented
9 years ago I tried the export feature, it worked halfway after doing a project
cleanup/rebuild.
When I expand the Leiningen Dependencies node in
project explorer in the master project, I see all of them now.
However, now it fails saying that some Joda class is not found. The class is
visible
in the Leiningen Dependencies node when I expand the Joda jar file.
In the repl, I have the same restricted set of dependencies as reported in this
issue.
Anything else I should try ?
Original comment by lprefont...@softaddicts.ca on 8 Oct 2012 at 9:43
GoogleCodeExporter
commented
9 years ago I investigated a bit. When I clean and rebuild projects in CCW, I get only .clj
files in the classes folder.
The external build via lein generates only class files (all project files
specify
AOT and no sources in the targets).
The failure occurs after a rebuild from ccw, the compiler attempts to compile
the
.clj file which references Joda and does not find Joda in the class path of the
REPL.
There are no errors reported by the internal rebuild. However an external build
followed by a refresh in project explorer generates a few errors regarding
the global state of the projects but no details are provided as to what
triggered
it.
This is the best I can find to illustrate the behaviour difference between a CCW
internal build and an external lein build.
When I examine the list of dependencies in the REPL, I found that some
libs in a few of the dependent project is present while others are absent.
Kind of weird. I would have expected none of these to show up.
The list is complete in the Leiningen dependencies node in the project explorer
of the master project, including joda which does not show up at compile time
in the class path.
I doubled check the export flag and it set on the lein dependency node
in all the projects on which the master project depends. This seems to
corroborate
what I see in the Leiningen dependencies node.
Is there a way I can investigate further down in Eclipse or is the problem
considered solved even if my manual attempts failed ?
Thank you,
Original comment by lprefont...@softaddicts.ca on 10 Oct 2012 at 1:54
GoogleCodeExporter
commented
9 years ago Another update.
I parsed the HIGIEBUSSupervisor.container to create a copy script,
dumped all the dependencies in a folder, added all the jars to the classpath
of the master project except the ones generated by the sub-targets
(HIGIEBUSxxx.jar).
A noticeable improvement of the internal build, no compiler errors on a clj
file,
it seems to find the java classes it missed before.
However we have some gen-class directives that do not trigger a .class file
generation. So these are missing and the compiler eventually fails with a
missing
java class (from the genclass directive).
The class path in the REPL looks ok if I compare it to the master project
leiningen dependencies node in project explorer.
From now on I will use an external lein build but will be able to run the
master project main in the REPL.
Thank you,
Eventually the compiler fails.Original comment by lprefont...@softaddicts.ca on 10 Oct 2012 at 3:21
GoogleCodeExporter
commented
9 years ago Wow, seems like a really nasty nasty bug we're facing :-(. Reopening the issue.
Will have to work harder on this one ...Original comment by laurent....@gmail.com on 10 Oct 2012 at 7:56
GoogleCodeExporter
commented
9 years ago Original comment by laurent....@gmail.com on 10 Nov 2012 at 9:44
GoogleCodeExporter
commented
9 years ago Original comment by laurent....@gmail.com on 15 Nov 2012 at 10:29
GoogleCodeExporter
commented
9 years ago Sorry to not have been able to work on this.
Too old report, please reopen or submit a new one if the issue still occurs
with latest versions.Original comment by laurent....@gmail.com on 22 May 2014 at 7:44
Original issue reported on code.google.com by
lprefont...@softaddicts.caon 8 Oct 2012 at 7:55Attachments: