In this scenario, I'd probably not try to fight maven and split this into two modules - api and implementation. Even in a pure java project I'm tempted to keep them separate (esp. with the OSGi stuff I'm doing, it looks like this would solve more of our reloading issues). As the plugin stands currently, you -could- bind clojure:compile with a limited set of namespaces to say the generate-sources phase (I really wish maven had a of before/after compile phase, and also bind it to the normal compile phase. That would get you the functionality you want in a single module, it's not very pretty to hijack the generate-sources phase like that thou.
-- Pull me down under... On Wed, Aug 26, 2009 at 12:03 AM, Laurent PETIT <laurent.pe...@gmail.com>wrote: > * first compile all the "pure gen-class/gen-interface" namespaces (the > only dependencies these namespaces can have are towards other "pure > gen-class/gen-interface" namespaces, and third-party namespaces java maven > artifacts declared in the pom. > > * then compile the java source files normally. > > * then compile the rest of the clojure files, whose dependencies towards > project's specific java artifacts will succesfully be found. > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
