Thanks Stuart for your reply. This was one of those mails where I looked at the problem with a fresh pair of eyes after sending and immediately saw the problem. It was in fact picking up my generated code fine, it's just the generated code was done into the wrong package and was a genuine compilation error.
Thanks again. Best, Adrian. On Tue, May 19, 2009 at 12:42 PM, Stuart McCulloch <mccu...@gmail.com>wrote: > 2009/5/19 Adrian Skehill <adrian.skeh...@gmail.com> > >> Hi guys, >> >> Wondering if anybody has come across this before. >> >> I'm setting up a pom that uses hibernates hbm2java to generate some java >> code into target/hibernate3/generated-sources and then need to compile these >> together with the java code located in src/main/java. >> >> It looks liks pax:compile is only picking up the stuff in src/main/java >> and doesn't know that it also has to compile the generated code. Is there a >> way that I can also get it to compile the generated code in the target >> directory? >> > > pax:compile just extends the normal compiler:compile goal, so I'd have > thought this should work > > try moving the "<extensions>true</extensions>" setting in "poms/pom.xml" > from the pax-plugin > to the bundle-plugin configuration - this will switch things back to the > standard Maven compiler > > if this works then feel free to raise a JIRA issue to add support for > additional source directories > > if it still doesn't work then that suggests there's something else going on > with your configuration > > Many Thanks, >> Adrian. >> >> _______________________________________________ >> general mailing list >> general@lists.ops4j.org >> http://lists.ops4j.org/mailman/listinfo/general >> > > -- > Cheers, Stuart > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > >
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
