Also, you mention the 9.2 release. As we're using WLS 8.1.3 will we miss out on 
this fix?

/jonas 

-----Ursprungligt meddelande-----
Från: Manu [mailto:[EMAIL PROTECTED] 
Skickat: den 2 november 2006 10:27
Till: Maven Users List
Ämne: Re: [M2]weblogic:appc classpath issue

Can you also tell to WHICH maven repository you will publish it ?
Thank you very much for your efforts.

2006/11/2, Dmystery <[EMAIL PROTECTED]>:
>
>
> Thanks Scott. It would be great if you can push the latest snapshot to the
> repository now.
>
>
> Scott Ryan-2 wrote:
> >
> > I have refactored the 2.8.0 plugin to fix that problem.  I have changed
> > some
> > of the parameters and since the website can only support one version of
> > the
> > plugin I need to add a page to describe the new settings for the 2.8.0
> > plugin.  I will be pushing the latest snapshot up to the repository once
> I
> > have completed that documentation.  This fixes the classpath issue both
> in
> > appc and the client gen mojos.  I have not updated the 2.9.0 version as
> > the
> > 9.2 release broke all the apis I was using so i need to refactor to use
> > the
> > new API's.
> >
> > Let me know if you would prefer I push up the 2.8.0 version now and just
> > post the changes on a note to the user list.
> >
> > Scott Ryan
> > Chief Technology Officer
> > Soaring Eagle L.L.C.
> > [EMAIL PROTECTED]
> > www.soaringeagleco.com
> > (303) 263-3044
> >
> > -----Original Message-----
> > From: Manu [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, October 31, 2006 12:07 PM
> > To: Maven Users List
> > Subject: Re: [M2]weblogic:appc classpath issue
> >
> >
> > Hi,
> >
> > I have the same problem. I need to explicitly set the entire <classpath>
> > by
> > hand to have it worked. In other words, I'm defining another time all
> the
> > dependencies that already are in the pom. The plugin does not seem to
> take
> > into account the dependencies.
> >
> > By the way, i'm using version 2.8.0-SNAPSHOT
> >
> > Thxs
> > Manu
> >
> > 2006/10/31, Dmystery <[EMAIL PROTECTED]>:
> >>
> >>
> >> Alos, looking at AppcMojo.class file, i dont see any default classpath
> >> being
> >> set. Here is the stack trace when i try to run the plugin.
> >>
> >> [INFO]  Detailed Appc settings information AppcMojo[basicClientJar =
> >> false
> >> classpath = null
> >> compiler = null
> >> debugging = true
> >> deprecation = false
> >> forceGeneration = false
> >> idl = false
> >> idlDirectory = null
> >> idlFactrories = false
> >> idlMethodSignatures = null
> >> idlNoAbstractInterfaces = true
> >> idlNoValueTypes = true
> >> idlOrbix = false
> >> idlOverwrite = false
> >> idlVerbose = false
> >> idlVisiBroker = false
> >> iiop = false
> >> iiopDirectory = null
> >> javaOptions = null
> >> keepGenerated = true
> >> lineNumbers = true
> >> nowarnings = false
> >> objectPath =
> >> D:\Castle-maven\castle\server\server-ejb\target/castle-server-ejb-
> >> 1.0.jar
> >> optimization = false
> >> outputFile = null
> >> verbose = true
> >> version = false]
> >> [INFO]  Argument List for Appc settings [-lineNumbers, -keepgenerated,
> >> -g,
> >> -verb
> >> ose,
> >> D:\Castle-maven\castle\server\server-ejb\target/castle-
> server-ejb-1.0.jar]
> >> [appc] Created working directory:
> >> C:\DOCUME~1\DEEP_M~1.INF\LOCALS~1\Temp\appcgen
> >>
> >> [J2EE:160119]Appc is unable to process the file
> >> 'D:\Castle-maven\castle\server\s
> >> erver-ejb\target\castle-server-ejb-1.0.jar'. The following error
> >> occurred:
> >> java.lang.NoClassDefFoundError: cadvf2/server/AbstractEJB ---->This is
> a
> >> compile dependency in the POM
> >>         at java.lang.ClassLoader.defineClass0(Native Method)
> >>         at java.lang.ClassLoader.defineClass(ClassLoader.java:502)
> >>         at
> >> java.security.SecureClassLoader.defineClass(SecureClassLoader.java:12
> >> 3)
> >>         at
> >> weblogic.utils.classloaders.GenericClassLoader.findLocalClass(Generic
> >> ClassLoader.java:480)
> >>         at
> >> weblogic.utils.classloaders.GenericClassLoader.findClass(GenericClass
> >> Loader.java:182)
> >>         at java.lang.ClassLoader.loadClass(ClassLoader.java:299)
> >>         at java.lang.ClassLoader.loadClass(ClassLoader.java:292)
> >>         at java.lang.ClassLoader.loadClass(ClassLoader.java:255)
> >>         at
> >> weblogic.utils.classloaders.GenericClassLoader.loadClass(GenericClass
> >> Loader.java:224)
> >>         at
> >> weblogic.ejb20.deployer.BeanInfoImpl.loadClass(BeanInfoImpl.java:343)
> >>
> >>         at
> >> weblogic.ejb20.deployer.BeanInfoImpl.<init>(BeanInfoImpl.java:192)
> >>         at
> >> weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.<init>(ClientDrivenB
> >> eanInfoImpl.java:179)
> >>         at
> >> weblogic.ejb20.deployer.SessionBeanInfoImpl.<init>(SessionBeanInfoImp
> >> l.java:74)
> >>         at
> >> weblogic.ejb20.deployer.BeanInfoImpl.createBeanInfoImpl(BeanInfoImpl.
> >> java:367)
> >>         at
> >> weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.initializeBeanInfos(M
> >> BeanDeploymentInfoImpl.java:548)
> >>         at
> >> weblogic.ejb20.deployer.MBeanDeploymentInfoImpl.<init>(MBeanDeploymen
> >> tInfoImpl.java:232)
> >>         at weblogic.ejb20.ejbc.EJBCompiler.setupEJB(EJBCompiler.java
> :155)
> >>         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java
> >> :415)
> >>         at weblogic.ejb20.ejbc.EJBCompiler.compileEJB(EJBCompiler.java
> >> :387)
> >>         at weblogic.appc.compileEJB(appc.java:802)
> >>         at weblogic.appc.compileEJB(appc.java:776)
> >>         at weblogic.appc.compileInput(appc.java:463)
> >>         at weblogic.appc.runBody(appc.java:184)
> >>         at weblogic.utils.compiler.Tool.run(Tool.java:192)
> >>         at weblogic.utils.compiler.Tool.run(Tool.java:147)
> >>         at weblogic.appc.main(appc.java:1030)
> >>         at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java
> :276)
> >>         at
> >> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> >> nManager.java:412)
> >>         at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> >> ultLifecycleExecutor.java:534)
> >>         at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> >> fecycle(DefaultLifecycleExecutor.java:475)
> >>         at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> >> ltLifecycleExecutor.java:454)
> >>         at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> >> dleFailures(DefaultLifecycleExecutor.java:306)
> >>         at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> >> ts(DefaultLifecycleExecutor.java:273)
> >>         at
> >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> >> fecycleExecutor.java:140)
> >>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java
> :322)
> >>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> >>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
> >>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> >>         at
> >> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> >> java:39)
> >>         at
> >> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> >> sorImpl.java:25)
> >>         at java.lang.reflect.Method.invoke(Method.java:324)
> >>         at
> >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >>         at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >>         at
> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >>
> >>         at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >>
> >> Dmystery wrote:
> >> >
> >> > 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: [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-tf2465090s177.html
> > #a7089129
> >> Sent from the Maven - Users mailing list archive at Nabble.com.
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> > --
> > Manu (:-Þ)
> >
> >
> > ---------------------------------------------------------------------
> > 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#a7127475
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Manu (:-Þ)

****************************************************************************
This e-mail has been scanned for viruses by http://www.virus112.se
****************************************************************************
****************************************************************************
Detta e-mail har blivit undersökt av http://www.virus112.se
****************************************************************************

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to