Mind sending me a pom and general layout of your project structure? There could be two solutions: 1- Move things into a multi-module project where your model.scala exists in one module and the other code in another module or 2 - We make sure the goal->phase bindings are appropriate for what you want to do.
-Josh On Mon, Mar 2, 2009 at 6:42 PM, Meredith Gregory <lgreg.mered...@gmail.com>wrote: > Lifted, > > i've got all the classes i generate making a class to a Model object > derived from the nice work that Derek did on the JPA demo. Now, here's the > rub. For some reason it's compiling the generated classes before tackling > the compilation of the model object. So... the compilation craps out. i've > been working around this by generating the classes, compiling the project > (without the classes) then moving them into place in the model directory and > compiling the project again. What's the pretty way to enforce this > sequentialization in maven. i really want these classes compiled *after*the > Model.scala file is compiled. i'd like not to say much more than this > ordering constraint to maven -- if at all possible. > > Best wishes, > > --greg > > -- > L.G. Meredith > Managing Partner > Biosimilarity LLC > 806 55th St NE > Seattle, WA 98105 > > +1 206.650.3740 > > http://biosimilarity.blogspot.com > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
