Compile error reporting

42 views
Skip to first unread message

Vladimir Tsichevski

unread,
Apr 2, 2013, 4:37:23 PM4/2/13
to clojured...@googlegroups.com
Hi,

I do the following:

  1. Clean the project, this deletes all previously compiled classes
  2. Run As the project as Clojure application, this starts the build process
After that I do not know if my project was successfully compiled or not.

How can I detect if any errors prevented my project from being compiled?

Regards,
Vladimir

Vladimir Tsichevski

unread,
May 1, 2013, 4:00:21 AM5/1/13
to clojured...@googlegroups.com
Still no any answer/suggestion?

Petr Gladkikh

unread,
May 7, 2013, 3:42:22 AM5/7/13
to clojured...@googlegroups.com
Just noticed that this question is without answer for so long, this is disturbing.

It seems that currently it is assumed that you load CLJ files in REPL and so verifying that they can be compiled (there is also "compile file in REPL" command). Java files will be compiled automatically. If there are any compilation errors thwy will be added to normal problems view in Eclipse "Window/Show view/Problems" 

However there are options to check classes with leiningen (there is now a shortcut to invoke it directly from Eclipse)

To check all files by compiling them use "lein compile :all" (see "lein help compile" for details) this will print any compilation errors.
(Brief description of "lein compile" may be misleading since by default it compiles only namespaces marked for AOT compilation.)
May also be helpful:
"lein jar" - as a "side effect" compiles all clj files to class files and will show any errors if there are any
"lein check" - inspects source and will give more warnings - however note that it may ignore some compilation errors that happen in default namespace (ones that occur before any ns declaration in the file)

 


Still no any answer/suggestion?
--
You received this message because you are subscribed to the Google Groups "counterclockwise-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to clojuredev-use...@googlegroups.com.
To post to this group, send email to clojured...@googlegroups.com.
Visit this group at http://groups.google.com/group/clojuredev-users?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
 
 



--
Petr Gladkikh

Vladimir Tsichevski

unread,
May 13, 2013, 5:07:51 AM5/13/13
to clojured...@googlegroups.com
Hi Petr,

thank you for the reply.


On Tuesday, May 7, 2013 11:42:22 AM UTC+4, Petr wrote:
Just noticed that this question is without answer for so long, this is disturbing.

It seems that currently it is assumed that you load CLJ files in REPL and so verifying that they can be compiled (there is also "compile file in REPL" command). Java files will be compiled automatically. If there are any compilation errors thwy will be added to normal problems view in Eclipse "Window/Show view/Problems" 
I never see clojure-related messages in the Problems view. Whatever I do.

However there are options to check classes with leiningen (there is now a shortcut to invoke it directly from Eclipse)
I have problem setting up lein for my configuration.  My setup includes a dozen interconnected Eclipse projects, some of them are Java/Clojure mix. CCW can "Compile file in REPL" every individual Clojure file, but that is all I can do.

To check all files by compiling them use "lein compile :all" (see "lein help compile" for details) this will print any compilation errors.
(Brief description of "lein compile" may be misleading since by default it compiles only namespaces marked for AOT compilation.)
May also be helpful:
"lein jar" - as a "side effect" compiles all clj files to class files and will show any errors if there are any
"lein check" - inspects source and will give more warnings - however note that it may ignore some compilation errors that happen in default namespace (ones that occur before any ns declaration in the file)

 

Regards,
Vladimir
Reply all
Reply to author
Forward
0 new messages