Hi, I add the same problem....
It was because the packaging target of the pom was 'ear' and the target directory of weblogic-maven-plugin was the same as the project ear target.... To resolve this, I changed the packaging target of the pom to 'pom': so the ear is only build by the weblogic-maven-plugin.... Gerald Reinhart Hussein Badakhchani-2 wrote: > > Hello, > > In case anyone is interested I have posted some instructions for > installing and using the Maven WebLogic Plug in on my blog. > > http://dev2dev.bea.com/blog/hoos/archive/2007/09/using_appc_with.html > > I am new to Maven and thus my implementation may not be optimal. For > instance I found that I had to describe the dependencies twice in my > pom.xml file, is this a standard thing in Maven or have I missed > something? > > Also I found that Maven includes all the jars used to precompile JSPs into > the final package, so I end up with files like weblogic.jar being > deployed. I would like to know what options there are for filtering such > files as the inclusion of the files violates our packaging specifications. > > Many thanks, > Hoos > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Using-Maven-WebLogic-Plug-in-tf4406565s177.html#a12776607 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
