That is what i thought. I should not a classpath. Most of my dependencies are with compile scope and yes i have an ejb jar file that i'm trying to compile. i cannot send u the exact snippet as i'm on a vacation :). Will get in touch next week.
thanks. Scott Ryan-2 wrote: > > You should not need a classpath as that is included for the clientgen part > of the plugin. The mojo should recognize the proper classpath from the > plugin dependencies. Are all your dependencies set to the default scope > or > are some set to some other scope like provided etc? Let me try the latest > plugin against my test suite tonight and give you some more feedback. > Just > to clarify you have an ejb jar file you are trying to appc? I have had > success with that. if you could send me a snippet of the issues you see > when you try with out the classpath that would help a lot. i will try to > get you an answer back this evening unless someone else on the list has an > answer before that. > > Scott Ryan > Chief Technology Officer > Soaring Eagle L.L.C. > [EMAIL PROTECTED] > www.soaringeagleco.com > (303) 263-3044 > > -----Original Message----- > From: Dmystery [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 18, 2006 2:39 AM > To: [email protected] > Subject: [M2]weblogic:appc classpath issue > > > > I'm using weblogic-maven-plugin to compile my ejb.jar. Here is the plugin > definition. > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>weblogic-maven-plugin</artifactId> > <version>2.8.0-SNAPSHOT</version> > <configuration> > > <objectPath>${project.build.directory}/${project.artifactId}-${project.versi > on}.jar</objectPath> > <verbose>true</verbose> > <debugging>true</debugging> > <nowarnings>false</nowarnings> > <lineNumbers>true</lineNumbers> > <keepGenerated>true</keepGenerated> > <classpath>${project.runtimeClasspathElements}</classpath> > </configuration> > <executions> > <execution> > <phase>package</phase> > <goals> > <goal>appc</goal> > </goals> > </execution> > </executions> > </plugin> > > The ${project.runtimeClasspathElements} is a string like [somedir\jar1, > somedir\jar2]. Because of this the plugin throws a > org.codehaus.plexus.component.configurator.ComponentConfigurationException > : > Invalid parameter supplied while setting '[somedir\jar1, somedir\jar2]' > > Are we supposed to provide <classpath></classpath> in the first place? or > will it consider ${project.runtimeClasspathElements} as the default > classpath? (I guess not). > > If i remove the <classpath></classpath> from the plugin definition (as it > is > optional), it fails to find some of the classes that it needs to compile > the > ejb.jar even though they are defined as dependencies in the project. > > Let me know if i'm doing something wrong. > -- > View this message in context: > http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a68 > 71847 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/-M2-weblogic%3Aappc-classpath-issue-tf2465090.html#a6929932 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
