Hi Karsten, Thanks for explaining what's happening behind the scenes. I am glad to know that I was on the right track with thinking that this approach should work. Is there a JIRA for this so I can watch its progress?
Thanks! --Polly Karsten Thoms wrote: > > Hi Polly, > > yes, I spent already some time digging into this issue. You are right, > best approach would be to configure the generator dependencies as > dependencies in the plugin configuration. When you do this, all those > dependencies are put on the classpath during plugin execution as expected. > What happens now is that oAW's type system has problems to resolve the > types correctly. I could not figure out what is causing this. > > I am planning to solve this issue. This will have to be solved within > Xpand, so some upcoming Xpand version will have this fix. I am expecting > that it takes me 2 whole days to solve it. It is quite tedious to debug > into this part, and I already spent several hours when I looked into this > the last time. This is quite huge effort and at the moment I do not have > time for this. > > Kind regards, > ~Karsten > > ----- Original Message ----- > From: "polly.c.chang" <polly.c.ch...@gmail.com> > To: fornax-developer@lists.sourceforge.net > Sent: Wednesday, November 11, 2009 11:24:59 PM (GMT+0100) Europe/Berlin > Subject: [Fornax-developer] [Sculptor] Generator dependency > > > Hi, > > I've wondered about this problem for a while now, and I cannot figure out > a > way to solve this. > > To generate code in my user project, the user project has to declare a > dependency to the "generator" jar, which transitively brings in > dependencies > like the "metamodel" and "dsl" jars and EMF, oAW, HybridLabs, Jalopy, > Antlr, > etc. There are a whole bunch of jars that come in via transitive > dependencies. The problem is that these jars are always on the classpath. > So when I create wars or other projects depend on my project, these jars > always go with them. Yes, there are usually ways to exclude these jars in > each of those scenarios, but I have to hunt down every usage and put the > fix > there. It would be nice if there was a way for these jars to be available > only when we generate code. Because after that happens, they are not used > anymore. > > I tried changing the scope of the dependencies or making them optional, > but > then I get ClassNotFoundExceptions when I try to generate. So it seems > that > most of the jars are required for generation. It would be too much work > (and error-prone) to figure out exactly which ones are really needed at > runtime. Plus it doesn't really solve the problem. > > I also tried defining the dependency to the "generator" jar in the > "fornax-oaw-m2-plugin" plugin "dependency" section instead of directly in > my > user project. I figured that this seems logical. The "generator" is > needed > only by the plugin when it runs. But alas, that does not work either. > There are no errors, but nothing generates. I get: > > [org.fornax.toolsupport.maven2.MojoWorkflowRunner] : > -------------------------------------------------------------------------------------- > [org.fornax.toolsupport.maven2.MojoWorkflowRunner] : openArchitectureWare > v4.3.1 > [org.fornax.toolsupport.maven2.MojoWorkflowRunner] : (c) 2005-2008 > openarchitectureware.org and contributors > [org.fornax.toolsupport.maven2.MojoWorkflowRunner] : > -------------------------------------------------------------------------------------- > [org.fornax.toolsupport.maven2.MojoWorkflowRunner] : running workflow: > workflow.oaw > [org.fornax.toolsupport.maven2.MojoWorkflowRunner] : > [org.fornax.toolsupport.maven2.MojoWorkflowRunner] : workflow completed in > 0ms! > > Can someone tell me why this approach doesn't work and how I might get it > to > work? > > If this approach won't work, how can I get the "generator" and its > transitive dependencies off my user project's classpath? > > Thanks! > --Polly > -- > View this message in context: > http://old.nabble.com/-Sculptor--Generator-dependency-tp26309409s17564p26309409.html > Sent from the Fornax-Platform mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Fornax-developer mailing list > Fornax-developer@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fornax-developer > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 > 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________ > Fornax-developer mailing list > Fornax-developer@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fornax-developer > > -- View this message in context: http://old.nabble.com/-Sculptor--Generator-dependency-tp26309409s17564p26322200.html Sent from the Fornax-Platform mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Fornax-developer mailing list Fornax-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fornax-developer
