I can run wlcompile just fine when I don't use the setWLSenv.cmd from
Weblogic. However, I can't deploy using WLDeploy unless I run setWLSenv.cmd.
The problem is that after I run setWLSenv.cmd and then try to complie I get
a NullPointerException. This error only occurs when I try to referenence
the POM file on the classpath as follows:
<artifact:dependencies pathId="dependency.classpath" verbose="false">
<pom refid="maven.project" />
</artifact:dependencies>
<wlcompile srcdir="${src.dir}" destdir="${dest.dir}">
<classpath>
<path refid="dependency.classpath"/>
</classpath>
<javac debug="true"/>
</wlcompile>
If I remvove the refid to a Maven POM it will compile just fine, but without
the dependent files of course. I'm certain it's a classpath conflict of
some sort. Has anyone else had a similar issue?
--
View this message in context:
http://www.nabble.com/-m2--Weblogic-classpath-issue-with-Maven-Antlib-t1826705.html#a4982840
Sent from the Maven - Users forum at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
