I still have issue in compiling the ejb jar file. It simply fails to find all
the dependencies in the classpath.
Here is the plugin definition again.
<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.version}.jar</objectPath>
<verbose>true</verbose>
<debugging>true</debugging>
<nowarnings>false</nowarnings>
<lineNumbers>true</lineNumbers>
<keepGenerated>true</keepGenerated>
</configuration>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>appc</goal>
</goals>
</execution>
</executions>
</plugin>
All the required jars for appc are defined as 'compile' dependecies in the
pom. Still it gives me a NoClassDefFoundError for the required class files.
Scott Ryan-2 wrote:
>
> How did you make out with the appc mojo? I am updating the plugin to
> simplify it this weekend and will update the code with some code that was
> posted in JIRA. Let me know your status and I will send out a note on the
> weekend when the new code is available.
>
> 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: users@maven.apache.org
> 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-tf2465090s177.html#a7088731
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
