FlexPMD maven plugin no longer useable with Maven due to imcompatible binaries?

I am using Maven 2.2.1 with FlexPMD 1.2 and Flexmojos 3.7.1, with the maven-site-plugin 3.0
I get the following error:
[INFO] [site:site {execution: default-site}]
[FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a linkage
error (java.lang.AbstractMethodError) and may be out-of-date. Check the realms:
[FATAL ERROR] Plugin realm = app0.child-container[org.apache.maven.plugins:maven
-site-plugin:3.0]
urls[0] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/plugins/mav
en-site-plugin/3.0/maven-site-plugin-3.0.jar
urls[1] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/reporting/m
aven-reporting-exec/1.0.1/maven-reporting-exec-1.0.1.jar
urls[2] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus/plexus-u
tils/1.5.10/plexus-utils-1.5.10.jar
urls[3] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/maven-setti
ngs-builder/3.0/maven-settings-builder-3.0.jar
urls[4] = file:/C:/dreammachine/cache/m2/repository/org/apache/velocity/velocity
/1.5/velocity-1.5.jar
urls[5] = file:/C:/dreammachine/cache/m2/repository/commons-collections/commons-
collections/3.2.1/commons-collections-3.2.1.jar
urls[6] = file:/C:/dreammachine/cache/m2/repository/commons-lang/commons-lang/2.
5/commons-lang-2.5.jar
urls[7] = file:/C:/dreammachine/cache/m2/repository/oro/oro/2.0.8/oro-2.0.8.jar
urls[8] = file:/C:/dreammachine/cache/m2/repository/velocity/velocity/1.5/veloci
ty-1.5.jar
urls[9] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/doxia/doxia
-core/1.2/doxia-core-1.2.jar
urls[10] = file:/C:/dreammachine/cache/m2/repository/xerces/xercesImpl/2.9.1/xer
cesImpl-2.9.1.jar
urls[11] = file:/C:/dreammachine/cache/m2/repository/xml-apis/xml-apis/1.3.04/xm
l-apis-1.3.04.jar
urls[12] = file:/C:/dreammachine/cache/m2/repository/org/apache/httpcomponents/h
ttpclient/4.0.2/httpclient-4.0.2.jar
urls[13] = file:/C:/dreammachine/cache/m2/repository/org/apache/httpcomponents/h
ttpcore/4.0.1/httpcore-4.0.1.jar
urls[14] = file:/C:/dreammachine/cache/m2/repository/commons-codec/commons-codec
/1.3/commons-codec-1.3.jar
urls[15] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/doxia/doxi
a-module-xhtml/1.2/doxia-module-xhtml-1.2.jar
urls[16] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/doxia/doxi
a-module-apt/1.2/doxia-module-apt-1.2.jar
urls[17] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/doxia/doxi
a-module-xdoc/1.2/doxia-module-xdoc-1.2.jar
urls[18] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/doxia/doxi
a-module-fml/1.2/doxia-module-fml-1.2.jar
urls[19] = file:/C:/dreammachine/cache/m2/repository/javax/servlet/servlet-api/2
.5/servlet-api-2.5.jar
urls[20] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/doxia/doxi
a-decoration-model/1.2/doxia-decoration-model-1.2.jar
urls[21] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/doxia/doxi
a-site-renderer/1.2/doxia-site-renderer-1.2.jar
urls[22] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus/plexus-
i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
urls[23] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus/plexus-
velocity/1.1.8/plexus-velocity-1.1.8.jar
urls[24] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/shared/mav
en-doxia-tools/1.4/maven-doxia-tools-1.4.jar
urls[25] = file:/C:/dreammachine/cache/m2/repository/commons-io/commons-io/1.4/c
ommons-io-1.4.jar
urls[26] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus/plexus-
archiver/1.0/plexus-archiver-1.0.jar
urls[27] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus/plexus-
io/1.0/plexus-io-1.0.jar
urls[28] = file:/C:/dreammachine/cache/m2/repository/org/mortbay/jetty/jetty/6.1
.25/jetty-6.1.25.jar
urls[29] = file:/C:/dreammachine/cache/m2/repository/org/mortbay/jetty/jetty-uti
l/6.1.25/jetty-util-6.1.25.jar
urls[30] = file:/C:/dreammachine/cache/m2/repository/org/mortbay/jetty/servlet-a
pi/2.5-20081211/servlet-api-2.5-20081211.jar
[FATAL ERROR] Container realm = plexus.core
urls[0] = file:/C:/dreammachine/tools/m2/lib/maven-2.2.1-uber.jar
[INFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO] ------------------------------------------------------------------------
[INFO] null
[INFO] ------------------------------------------------------------------------
[INFO] Trace
java.lang.AbstractMethodError
        at org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getReports(Ab
stractSiteRenderingMojo.java:246)
        at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:121)
        at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:490)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:694)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:556)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:535)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:387)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:348)
        at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
If I revert to maven-site-plugin 2.1 this issue disappears, but I then get the error reported here:
https://issues.sonatype.org/browse/FLEXMOJOS-310?page=com.atlassian.jira.plugin.system.iss uetabpanels:comment-tabpanel#issue-tabs
If I migrate to maven 3.0.3 with maven-site-plugin 3.0 I get the following error:
[INFO] configuring report plugin com.adobe.ac:flex-pmd-maven-plugin:1.2
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:31.730s
[INFO] Finished at: Tue Sep 27 17:21:49 BST 2011
[INFO] Final Memory: 21M/243M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0:si
te (default-site) on project cafe-parsley: Execution default-site of goal org.ap
ache.maven.plugins:maven-site-plugin:3.0:site failed: An API incompatibility was
encountered while executing org.apache.maven.plugins:maven-site-plugin:3.0:site
: java.lang.AbstractMethodError: null
[ERROR] -----------------------------------------------------
[ERROR] realm =    plugin>org.apache.maven.plugins:maven-site-plugin:3.0
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/plu
gins/maven-site-plugin/3.0/maven-site-plugin-3.0.jar
[ERROR] urls[1] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/rep
orting/maven-reporting-exec/1.0.1/maven-reporting-exec-1.0.1.jar
[ERROR] urls[2] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/rep
orting/maven-reporting-api/3.0/maven-reporting-api-3.0.jar
[ERROR] urls[3] = file:/C:/dreammachine/cache/m2/repository/org/apache/velocity/
velocity/1.5/velocity-1.5.jar
[ERROR] urls[4] = file:/C:/dreammachine/cache/m2/repository/oro/oro/2.0.8/oro-2.
0.8.jar
[ERROR] urls[5] = file:/C:/dreammachine/cache/m2/repository/velocity/velocity/1.
5/velocity-1.5.jar
[ERROR] urls[6] = file:/C:/dreammachine/cache/m2/repository/org/sonatype/aether/
aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[7] = file:/C:/dreammachine/cache/m2/repository/org/sonatype/sisu/si
su-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[8] = file:/C:/dreammachine/cache/m2/repository/org/sonatype/sisu/si
su-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[9] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus/
plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[10] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus
/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
[ERROR] urls[11] = file:/C:/dreammachine/cache/m2/repository/org/sonatype/plexus
/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[12] = file:/C:/dreammachine/cache/m2/repository/org/sonatype/plexus
/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[13] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/do
xia/doxia-sink-api/1.2/doxia-sink-api-1.2.jar
[ERROR] urls[14] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/do
xia/doxia-logging-api/1.2/doxia-logging-api-1.2.jar
[ERROR] urls[15] = file:/C:/dreammachine/cache/m2/repository/junit/junit/3.8.1/j
unit-3.8.1.jar
[ERROR] urls[16] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/do
xia/doxia-core/1.2/doxia-core-1.2.jar
[ERROR] urls[17] = file:/C:/dreammachine/cache/m2/repository/xerces/xercesImpl/2
.9.1/xercesImpl-2.9.1.jar
[ERROR] urls[18] = file:/C:/dreammachine/cache/m2/repository/xml-apis/xml-apis/1
.3.04/xml-apis-1.3.04.jar
[ERROR] urls[19] = file:/C:/dreammachine/cache/m2/repository/org/apache/httpcomp
onents/httpclient/4.0.2/httpclient-4.0.2.jar
[ERROR] urls[20] = file:/C:/dreammachine/cache/m2/repository/org/apache/httpcomp
onents/httpcore/4.0.1/httpcore-4.0.1.jar
[ERROR] urls[21] = file:/C:/dreammachine/cache/m2/repository/commons-codec/commo
ns-codec/1.3/commons-codec-1.3.jar
[ERROR] urls[22] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/do
xia/doxia-module-xhtml/1.2/doxia-module-xhtml-1.2.jar
[ERROR] urls[23] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/do
xia/doxia-module-apt/1.2/doxia-module-apt-1.2.jar
[ERROR] urls[24] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/do
xia/doxia-module-xdoc/1.2/doxia-module-xdoc-1.2.jar
[ERROR] urls[25] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/do
xia/doxia-module-fml/1.2/doxia-module-fml-1.2.jar
[ERROR] urls[26] = file:/C:/dreammachine/cache/m2/repository/javax/servlet/servl
et-api/2.5/servlet-api-2.5.jar
[ERROR] urls[27] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/do
xia/doxia-decoration-model/1.2/doxia-decoration-model-1.2.jar
[ERROR] urls[28] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/do
xia/doxia-site-renderer/1.2/doxia-site-renderer-1.2.jar
[ERROR] urls[29] = file:/C:/dreammachine/cache/m2/repository/commons-collections
/commons-collections/3.2.1/commons-collections-3.2.1.jar
[ERROR] urls[30] = file:/C:/dreammachine/cache/m2/repository/org/apache/maven/sh
ared/maven-doxia-tools/1.4/maven-doxia-tools-1.4.jar
[ERROR] urls[31] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus
/plexus-archiver/1.0/plexus-archiver-1.0.jar
[ERROR] urls[32] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus
/plexus-io/1.0/plexus-io-1.0.jar
[ERROR] urls[33] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus
/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
[ERROR] urls[34] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus
/plexus-velocity/1.1.8/plexus-velocity-1.1.8.jar
[ERROR] urls[35] = file:/C:/dreammachine/cache/m2/repository/org/codehaus/plexus
/plexus-utils/1.5.10/plexus-utils-1.5.10.jar
[ERROR] urls[36] = file:/C:/dreammachine/cache/m2/repository/org/mortbay/jetty/j
etty/6.1.25/jetty-6.1.25.jar
[ERROR] urls[37] = file:/C:/dreammachine/cache/m2/repository/org/mortbay/jetty/s
ervlet-api/2.5-20081211/servlet-api-2.5-20081211.jar
[ERROR] urls[38] = file:/C:/dreammachine/cache/m2/repository/org/mortbay/jetty/j
etty-util/6.1.25/jetty-util-6.1.25.jar
[ERROR] urls[39] = file:/C:/dreammachine/cache/m2/repository/commons-lang/common
s-lang/2.5/commons-lang-2.5.jar
[ERROR] urls[40] = file:/C:/dreammachine/cache/m2/repository/commons-io/commons-
io/1.4/commons-io-1.4.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[project>com.jpmorgan.ib.arch
itecture.deia.app:cafe-parsley:1.0-SNAPSHOT, parent: ClassRealm[maven.api, paren
t: null]]]
[ERROR]
[ERROR] -----------------------------------------------------
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/PluginContaine
Thus it seems FlexPMD can no longer be used with Maven due to some sort of binary incompatibility issue...
Does anyone know how to resolve this issue?

Hooray, I got to the bottom of issue.
Basically the flex PMD maven plugin is broken at version 1.2 with more recent version of maven-site-plugin. This is because of a new abstract method introduced to the class AbstractMavenReport - canGenerateReport();
This method isn't implemented in the FlexPmdMojo and FlexPmdReportMojo classes on the SVN trunk or in flexPMD 1.2 and was causing >mvn site to fail as outlined above. Add implementations of this method, returning true in both classes and the plugin works again!
Note the method also needs to be added to the relevant Mojo and ReportMojo classes for the FlexMetrics and CPD maven plugins to get them working too.
Flex PMD commiters - please release a new version of the project to resolve this showstopper!

Similar Messages

Maven plugin

hi,
while mvn compile following error is ocuring.can anyone give me any clue.
[INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not exist or no valid version could be found
Thanks&Regards
Nirmal kumar Ghosh

Andy-
The "schematool" goal is not yet working (I think not anyway!) ... the Kodo
2.5 "schematool" process seems to have been renamed "mappingtool" in 3.0,
and with what I came up with using "mappingtool", Kodo was mapping 2
classes (base class, and a derived class) into a single DB table for some
reason ... is this to be expected in 3.0 ? [I was kind of expecting it to
represent my tables as it did in 2.5 ... one for base class and one for
derived class]This is dependant on the type of class mapping you are using:
http://solarmetric.com/Software/Documentation/3.0.0RC1/docs/manual.html#ref_guide_mapping_classmapping
In article <bl72ca$pjc$[email protected]>, Andy Jefferson wrote:
Abe White wrote:
I've put a version 1.0.0 of the Maven plugin for Kodo (works with Kodo
v2.5.2) up on the maven plugins site (http://maven-plugins.sf.net).
Thanks! I just realized I still have an email from you in my inbox...
did I ever respond?No ... I thought you were ignoring me :-)
Anyway, now that Kodo 3 is at RC status it should be
stable enought o build Maven plugins for, if you're so inclined... :) If
not I'm sure we'll get around to it eventually.I've actually got the "enhance" and "version" goals working for 3.0.
The "schematool" goal is not yet working (I think not anyway!) ... the Kodo
2.5 "schematool" process seems to have been renamed "mappingtool" in 3.0,
and with what I came up with using "mappingtool", Kodo was mapping 2
classes (base class, and a derived class) into a single DB table for some
reason ... is this to be expected in 3.0 ? [I was kind of expecting it to
represent my tables as it did in 2.5 ... one for base class and one for
derived class]--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Maven plugin v1.0.0

I've put a version 1.0.0 of the Maven plugin for Kodo (works with Kodo
v2.5.2) up on the maven plugins site (http://maven-plugins.sf.net).
Andy

Andy-
The "schematool" goal is not yet working (I think not anyway!) ... the Kodo
2.5 "schematool" process seems to have been renamed "mappingtool" in 3.0,
and with what I came up with using "mappingtool", Kodo was mapping 2
classes (base class, and a derived class) into a single DB table for some
reason ... is this to be expected in 3.0 ? [I was kind of expecting it to
represent my tables as it did in 2.5 ... one for base class and one for
derived class]This is dependant on the type of class mapping you are using:
http://solarmetric.com/Software/Documentation/3.0.0RC1/docs/manual.html#ref_guide_mapping_classmapping
In article <bl72ca$pjc$[email protected]>, Andy Jefferson wrote:
Abe White wrote:
I've put a version 1.0.0 of the Maven plugin for Kodo (works with Kodo
v2.5.2) up on the maven plugins site (http://maven-plugins.sf.net).
Thanks! I just realized I still have an email from you in my inbox...
did I ever respond?No ... I thought you were ignoring me :-)
Anyway, now that Kodo 3 is at RC status it should be
stable enought o build Maven plugins for, if you're so inclined... :) If
not I'm sure we'll get around to it eventually.I've actually got the "enhance" and "version" goals working for 3.0.
The "schematool" goal is not yet working (I think not anyway!) ... the Kodo
2.5 "schematool" process seems to have been renamed "mappingtool" in 3.0,
and with what I came up with using "mappingtool", Kodo was mapping 2
classes (base class, and a derived class) into a single DB table for some
reason ... is this to be expected in 3.0 ? [I was kind of expecting it to
represent my tables as it did in 2.5 ... one for base class and one for
derived class]--
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

Problem with the weblogic-maven-plugin

I am in the process of converting from ant to maven, but I am having a problem with the weblogic-maven-plugin. Has anyone used this plugin successfully? Here is the error I am receiving even though I have a dependency on the xbean.jar in my pom, and it is in my local repo.
java.lang.NoClassDefFoundError: com/bea/xml/XmlException
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescript
orManager(AbstractDescriptorLoader2.java:301)
at weblogic.application.descriptor.AbstractDescriptorLoader2.getDescript
orBeanFromReader(AbstractDescriptorLoader2.java:749)
at weblogic.application.descriptor.AbstractDescriptorLoader2.createDescr
iptorBean(AbstractDescriptorLoader2.java:376)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescrip
torBeanWithoutPlan(AbstractDescriptorLoader2.java:720)
at weblogic.application.descriptor.AbstractDescriptorLoader2.loadDescrip
torBean(AbstractDescriptorLoader2.java:729)
at weblogic.servlet.internal.WebAppDescriptor.getWebAppBean(WebAppDescri
ptor.java:134)
at weblogic.servlet.jsp.JspcInvoker.parseDescriptors(JspcInvoker.java:27
6)
at weblogic.servlet.jsp.JspcInvoker.compile(JspcInvoker.java:187)
at weblogic.application.compiler.AppcUtils.compileWAR(AppcUtils.java:353
at weblogic.application.compiler.WARCompiler.compile(WARCompiler.java:78
at weblogic.application.compiler.flow.AppCompilerFlow.compileInput(AppCo
mpilerFlow.java:118)
at weblogic.application.compiler.flow.AppCompilerFlow.compile(AppCompile
rFlow.java:43)
at weblogic.application.compiler.FlowDriver$FlowStateChange.next(FlowDri
ver.java:69)
at weblogic.application.utils.StateMachineDriver.nextState(StateMachineD
river.java:26)
at weblogic.application.compiler.FlowDriver.nextState(FlowDriver.java:36
at weblogic.application.compiler.FlowDriver.run(FlowDriver.java:26)
at weblogic.application.compiler.Appc.runBody(Appc.java:163)
at weblogic.utils.compiler.Tool.run(Tool.java:158)
at weblogic.utils.compiler.Tool.run(Tool.java:115)
at weblogic.application.compiler.Appc.main(Appc.java:174)
at weblogic.appc.main(appc.java:14)
at jrockit.reflect.InitialMethodInvoker.invoke(Ljava.lang.Object;[Ljava.
lang.Object;)Ljava.lang.Object;(Unknown Source)
at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;
I)Ljava.lang.Object;(Unknown Source)
at weblogic.ant.taskdefs.j2ee.CompilerTask.invokeMain(CompilerTask.java:
290)
at weblogic.ant.taskdefs.j2ee.Appc.privateExecute(Appc.java:250)
at weblogic.ant.taskdefs.j2ee.Appc.execute(Appc.java:159)
at org.codehaus.mojo.weblogic.AppcMojo.execute(AppcMojo.java:180)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:534)

Here is what you need to get the maven-weblogic-plugin appc goal to work:
<project>
<build>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>weblogic-maven-plugin</artifactId>
<version>2.9.0-SNAPSHOT</version>
<configuration>
<inputArtifactPath>${basedir}/../../jar/broker.war</inputArtifactPath>
<verbose>true</verbose>
</configuration>
<executions>
<execution>
<phase>package</phase>
<goals>
<goal>appc</goal>
</goals>
<inherited>false</inherited>
<configuration>
<verbose>false</verbose>
<debug>false</debug>
<projectPackaging>war</projectPackaging>
</configuration>
</execution>
</executions>
<dependencies>
<dependency>
<groupId>com.sun</groupId>
<artifactId>tools</artifactId>
<version>1.5.0</version>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>wlxbean</artifactId>
<version>9.2</version>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>xbean</artifactId>
<version>9.2</version>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>weblogic-container-binding</artifactId>
<version>9.2</version>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>wlw-util</artifactId>
<version>9.2</version>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>javelinx</artifactId>
<version>9.2</version>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>wlw-langx</artifactId>
<version>9.2</version>
</dependency>
<dependency>
<groupId>weblogic</groupId>
<artifactId>bcel</artifactId>
<version>5.1</version>
</dependency>
</plugin>
</build>
<dependencies>
<dependency>
<groupId>weblogic</groupId>
<artifactId>wlw-langx</artifactId>
<version>9.2</version>
</dependency>
</dependencies>
<project>
You need to install/deploy all of the above dependencies manually into your repo.

Prevent css compilation with JavaFX maven plugin?

I'm using zonski's JavaFX plugin for Maven (https://github.com/zonski/javafx-maven-plugin) to build a self-contained executable jar file. It works fine, except that some of the css styles I created failed to be applied. When I opened the jar file in a file browser, I noticed that my css file had been replaced with a bss file containing bytecode. When I manually deleted this file from my jar and replaced it with the original css file, everything worked fine and all my styles were correctly applied.
I've also noticed that when I just do a normal maven build (ie, not using the JavaFX plugin), the css file remains a css file, so this behavior appears to be specific to zonski's plugin. Does anybody know if there's a way to turn this off? I'd prefer to just keep it as a css file in the first place if possible, rather than have to fix it manually.
Thanks,
Ian

You can throw the -nocss2bin switch at javafxpackager.
I would be interested in knowing what styles didn't apply from the binary css format but did from the ascii format. There should be no reason that the styles wouldn't be applied from the binary format. That they are not indicates to me that there is a bug lurking there. Would you mind filing a bug on https://javafx-jira.kenai.com?

Maven Plugin classpaths

Any Maven gurus out there? (I can't send to the maven user mailing list at the moment for apparently DNS related reasons)
In the interests of automating a build, I'm currently trying to hack
the hibernate3-maven-plugin mojo so that it will accept a necessary
configuration file from a JAR brought in as a dependency.
The JAR contains a resource (hibernate.cfg.xml) in its root package,
but no matter how I try, I can't seem to get the JAR to be on the
plugin's classpath.
The following (brutish) code should output the path to the file
resource within the JAR when running. My code is definitely being
invoked within the Maven task (changes to the system out are visible
in Maven's generated output when running).
final URL url = ClassLoader.getSystemResource("hibernate.cfg.xml");
System.out.println("URL: "+url);Running within the Maven task the output is always
URL: nullRunning as a testcase class with the dependency JAR on the classpath
the output is something like:
URL:
jar:file:/C:/dev/apps/myapp-core/target/
myapp-core-1.0-SNAPSHOT.jar!/hibernate.cfg.xmlSo it seems clear cut that this is a classpath problem. Presumably I'm
trying to get the JAR onto the plugin's classpath in the wrong manner
- how should I be doing this? Or is there some reason it can't be
done? Or am I doing something else equally stupid wrong instead?
Relevant trimmed snippet of the pom follows:
       <plugins>
           <plugin>
               <groupId>org.codehaus.mojo</groupId>
               <artifactId>hibernate3-maven-plugin</artifactId>
               <version>2.0-alpha-3-SNAPSHOT</version>
               <dependencies>
                   <dependency>
                       <groupId>my.group.id</groupId>
                       <artifactId>myapp-core</artifactId>
                       <version>1.0-SNAPSHOT</version>
                   </dependency>
               </dependencies>
               <configuration>
                   <components> ... </components>
                   <executions> ... <execution>
                   <componentProperties>
                       <configurationfile>
                           hibernate.cfg.xml
                       </configurationfile>
                   ... etc.

I met a friend and M2 guru for beers last night, and presented the question to him. Unfortunately, our local brewpub serves 22 oz mugs, and I had four of them (not driving), so the details of his explanation are long gone. I do recall him saying that plugins do have their own classloader (which makes sense).
But that's not the reason I'm replying :-)
Assuming that the plugins combine the dependency classpath with their own classpath (which your experiments seem to indicate), then getting the context classloader is the right approach. Supposedly, it's how you should always get a classloader, particularly in a J2EE container, but I've never found a good explanation of why.

Deploy maven artifact using the wls-maven-plugin (12.1.1.0)

I am trying to use the wls maven plugin to deploy an artifact located in my local repository.
According to the documentation ( http://docs.oracle.com/cd/E24329_01/web.1211/e24368/maven.htm#autoId6 ) this can be done by specifying the maven coordinates in the source parameter. Again according to the doc it should be specified as groupId:artifactID:packaging:classifier:version.
I tried this but as was not working I decompiled the wls-maven-plugin jar where I first of all discoverd that what should be passed is groupId:artifactID:version instead of the full one.
The next problem is the regular expression used to detect this:
if (this.source.matches("\\S:\\S:\\S")) {As you can see this will only detect one character long groupID, artifactID and version (obviously this has never been tested ...).
Can the source code of this plugin be found somewhere so I can fix it myself, can oracle fix this quickly, ... what are my options here?
Thanks

My first question regards step number 2...
2. Extract the contents of the supplemental zip (eg: extract into /home/myhome/mywls )
wls12120 directory will be automatically created during extraction.
The file name is wls12120_dev_supplemental.zip .
When I put this file in the mywls directory and Extract All ( using Windows Explorer, if that matters ),
the directory created is actually named " wls12120_dev_supplemental " and it has 1 sub-directory named " wls12120 ".
So, is there something wrong with Step 2's text ?
Is there something wrong with how I interpreted Step 2's text ?
Is the actual directory and sub-directory I see being created the successful response / result ? Or did this step fail ?

Using WLSTInterpreter with Maven

I'm try to write an maven plugin for WLST, I'm using the following path to include weblogic in my classpath to avoid the weblogic.home error. No matter how do i set it, still get the same error '
java.lang.RuntimeException: error in finding weblogic.Home', but If i passed as property from the command line I'm getting a different error 'ImportError: no module named weblogic'
Looks like a bug.
I'm using ALSB weblogic 9.2
<dependency>
<groupId>bea</groupId>
<artifactId>weblogic</artifactId>
<version>9.2</version>
<systemPath>${env.WL_HOME}/server/lib/weblogic.jar</systemPath>
<scope>system</scope>
</dependency>

bdkjones wrote:
I would recommend an inverter to convert the 12 volt battery to alternating current.
I would not run my Mac off of a third party power adaptor. The Apple-provided AC adaptor provides current and voltage leveling functions that a third-party adaptor (especially a cheap one) may lack. Computer components are very sensitive to even small changes in voltage and current, so I wouldn't gamble with low-quality power supplies.
Not only that, but MagSafe is not a feature other third party manufacturer may have, it might actually damage your system if the magnet is too powerful. I think you have better luck using an UPS instead.

Maven2 and axistools-maven-plugin - strange error

Hi all,
I am using maven2 for the build proccess and I get this strange error message while compiling.
=========
[INFO] Scanning for projects...
[INFO] ----------------------------------------------------------------------------
[INFO] Building Maven Quick Start Archetype
[INFO] task-segment: [compile]
[INFO] ----------------------------------------------------------------------------
[INFO] ----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ----------------------------------------------------------------------------
[INFO] The plugin 'org.codehaus.mojo:axistools-maven-plugin' does not exist or no valid version could be found
[INFO] ----------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Mon Jan 30 08:45:42 GMT+02:00 2006
[INFO] Final Memory: 1M/3M
[INFO] ----------------------------------------------------------------------------
=========
The plugin defined in pom.xml is:
==========
               <plugin>
                    <groupId>org.codehaus.mojo</groupId>
                    <artifactId>axistools-maven-plugin</artifactId>
                    <configuration>               <fileNStoPkg>${srcdir}/properties/namespaces2packages.properties</fileNStoPkg>
                         <serverSide>true</serverSide>
                    </configuration>
                    <executions>
                         <execution>
                              <goals>
                                   <goal>wsdl2java</goal>
                              </goals>
                         </execution>
                    </executions>
               </plugin>
==========
Any ideas guys?

Sorry, forgot to paste the trace. Here it is now:
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: The plugin 'org.codehaus.mojo:axistools-maven-plugin' does not e
xist or no valid version could be found
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1203)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1139)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:
948)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:450)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.jav
a:303)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:270)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:139)
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:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.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)
Caused by: org.apache.maven.plugin.version.PluginVersionNotFoundException: The plugin 'org.codehaus.mojo:axistools-maven
-plugin' does not exist or no valid version could be found
at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.
java:225)
at org.apache.maven.plugin.version.DefaultPluginVersionManager.resolvePluginVersion(DefaultPluginVersionManager.
java:87)
at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:177)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1174)
... 17 more
[INFO] ----------------------------------------------------------------------------

Failed to build javax.mail.jar (Java Mail 1.4.4) with Maven-2.2.1

Hi,
I am building javax.mail.jar using with the source of "JavaMail 1.4.4 source code", downloaded from http://kenai.com/projects/javamail/downloads , we have some customized changes in few source java files (regarding IMAP and response) of this source, otherwise no changes we have done in this source for building mail jar with maven.
I was using Maven 2.2.1 - successfully downloaded repository on my systems when I had Java 1.6. Then I have moved to java 7 but it failed, on roll back changes I was unable to download repositories as I had downloaded at earlier stage.
System has set JAVA_HOME of Java Home directory
[ERROR] BUILD ERROR
[INFO] ----------------------------------------------------------------------
[INFO] Internal error in the plugin manager executing goal 'com.sun.enterprise:osgiversion-maven-plugin:0.4.11:compute-osgi-version': Unable to load the mojo 'com.sun.enterprise:osgiversion-maven-plugin:0.4.11:compute-osgi-version' in the plugin 'com.sun.enterprise:osgiversion-maven-plugin'. A required class is missing: Lorg/apache/maven/shared/osgi/Maven2OsgiConverter;
org.apache.maven.shared.osgi.Maven2OsgiConverter
[INFO] ----------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionExcep tion: Internal error in the plugin manager executing goal 'com.sun.enterprise:osgiversion-maven-plugin:0.4.11:compute-osgi-version': Unable to load the mojo 'com.sun.enterprise:osgiversion-maven-plugin:0.4.11:compute-osgi-version' in the plugin 'com.sun.enterprise:osgiversion-maven-plugin'. A required class is missing: Lorg/apache/maven/shared/osgi/Maven2OsgiConverter;
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoals(DefaultLifecycleExecutor.java:698)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoalWithLifecycle(DefaultLifecycleExecuto r.java:556)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoal(DefaultLifecycleExecutor.java:535)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoalAndHandleFailures(DefaultLifecycleExe cutor.java:387)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeTaskSegments(DefaultLifecycleExecutor.jav a:348)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMav en.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven .java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:3 62)
at org.apache.maven.cli.compat.CompatibleMain.main(Co mpatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nativ e Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Native MethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(De legatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(L auncher.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.ja va:375)
Caused by: org.apache.maven.plugin.PluginManagerException: Unable to load the mojo 'com.sun.enterprise:osgiversion-maven-plugin:0.4.11:compute-osgi-version' in the plugin 'com.sun.enterprise:osgiversion-maven-plugin'. A required class is missing: Lorg/apache/maven/shared/osgi/Maven2OsgiConverter;
at org.apache.maven.plugin.DefaultPluginManager.getCo nfiguredMojo(DefaultPluginManager.java:679)
at org.apache.maven.plugin.DefaultPluginManager.execu teMojo(DefaultPluginManager.java:468)
at org.apache.maven.lifecycle.DefaultLifecycleExecuto r.executeGoals(DefaultLifecycleExecutor.java:694)
... 17 more
Caused by: java.lang.NoClassDefFoundError: Lorg/apache/maven/shared/osgi/Maven2OsgiConverter;
at java.lang.Class.getDeclaredFields0(Native Method)
at java.lang.Class.privateGetDeclaredFields(Class.jav a:2291)
at java.lang.Class.getDeclaredField(Class.java:1880)
at hidden.org.codehaus.plexus.util.ReflectionUtils.ge tFieldByNameIncludingSuperclasses(ReflectionUtils. java:47)
at org.codehaus.plexus.component.composition.FieldCom ponentComposer.getFieldByName(FieldComponentCompos er.java:212)
at org.codehaus.plexus.component.composition.FieldCom ponentComposer.findMatchingField(FieldComponentCom poser.java:171)
at org.codehaus.plexus.component.composition.FieldCom ponentComposer.assembleComponent(FieldComponentCom poser.java:62)
at org.codehaus.plexus.component.composition.DefaultC omponentComposerManager.assembleComponent(DefaultC omponentComposerManager.java:68)
at org.codehaus.plexus.DefaultPlexusContainer.compose Component(DefaultPlexusContainer.java:1486)
at org.codehaus.plexus.personality.plexus.lifecycle.p hase.CompositionPhase.execute(CompositionPhase.jav a:29)
at org.codehaus.plexus.lifecycle.AbstractLifecycleHan dler.start(AbstractLifecycleHandler.java:101)
at org.codehaus.plexus.component.manager.AbstractComp onentManager.startComponentLifecycle(AbstractCompo nentManager.java:105)
at org.codehaus.plexus.component.manager.AbstractComp onentManager.createComponentInstance(AbstractCompo nentManager.java:95)
at org.codehaus.plexus.component.manager.PerLookupCom ponentManager.getComponent(PerLookupComponentManag er.java:48)
at org.codehaus.plexus.DefaultPlexusContainer.lookup( DefaultPlexusContainer.java:331)
at org.codehaus.plexus.DefaultPlexusContainer.lookup( DefaultPlexusContainer.java:440)
at org.apache.maven.plugin.DefaultPluginManager.getCo nfiguredMojo(DefaultPluginManager.java:652)
... 19 more
Caused by: java.lang.ClassNotFoundException: org.apache.maven.shared.osgi.Maven2OsgiConverter
at java.net.URLClassLoader$1.run(URLClassLoader.java: 200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.j ava:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:3 07)
at org.codehaus.classworlds.RealmClassLoader.loadClas sDirect(RealmClassLoader.java:195)
at org.codehaus.classworlds.DefaultClassRealm.loadCla ss(DefaultClassRealm.java:255)
at org.codehaus.classworlds.DefaultClassRealm.loadCla ss(DefaultClassRealm.java:274)
at org.codehaus.classworlds.RealmClassLoader.loadClas s(RealmClassLoader.java:214)
at java.lang.ClassLoader.loadClass(ClassLoader.java:2 52)
at java.lang.ClassLoader.loadClassInternal(ClassLoade r.java:320)
... 36 more
[INFO] ----------------------------------------------------------------------
[INFO] Total time: 29 minutes 36 seconds
[INFO] Finished at: Fri Dec 21 13:07:49 IST 2012
[INFO] Final Memory: 13M/23M
[INFO] ----------------------------------------------------------------------
Complete log output of downloading process can be seen here - http://neelamsharma.s3.amazonaws.com/Maven_Result-2.2.1.txt
I am removing local repository ".m2" folder from my user each time before restart build. I have tried to download on different OS but it always stuck at same error.
Can anybody please let me know what settings are changed that I need to update ? Or which repositories need to remove to get rid of this error?

Looks like there is some sun plugin being used there. Might be that you need the java.net nexus repository so maven can fetch plugin dependencies from it.

Failed to build Java Mail API 1.4.5 with maven-3.0.4

Hi,
I am trying to build Java Mail 1.4.5 with Maven-3.0.4 using default settings of maven.
It is getting failed to build due to following errors -
[ERROR] COMPILATION ERROR :
[INFO] -----------------------------------------------------------
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[210,37] cannot find symbol
symbol : variable Version
location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[369,47] cannot find symbol
symbol : variable Version
location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[913,29] cannot find symbol
symbol : variable Version
location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[916,29] cannot find symbol
symbol : variable Version
location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[919,29] cannot find symbol
symbol : variable Version
location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[922,29] cannot find symbol
symbol : variable Version
location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[925,29] cannot find symbol
symbol : variable Version
location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[928,29] cannot find symbol
symbol : variable Version
location: class javax.mail.Session
[INFO] 8 errors
[INFO] -----------------------------------------------------------
[INFO] ----------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ----------------------------------------------------------------------
[INFO] Total time: 1:51.197s
[INFO] Finished at: Tue Jan 08 13:06:01 IST 2013
[INFO] Final Memory: 12M/67M
[INFO] ----------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.
3.2:compile (default-compile) on project javax.mail: Compilation failure: Compil
ation failure:
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[210,37] cannot find symbol
[ERROR] symbol : variable Version
[ERROR] location: class javax.mail.Session
[ERROR]\Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[369,47] cannot find symbol
[ERROR] symbol : variable Version
[ERROR] location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[913,29] cannot find symbol
[ERROR] symbol : variable Version
[ERROR] location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[916,29] cannot find symbol
[ERROR] symbol : variable Version
[ERROR] location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[919,29] cannot find symbol
[ERROR] symbol : variable Version
[ERROR] location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[922,29] cannot find symbol
[ERROR] symbol : variable Version
[ERROR] location: class javax.mail.Session
[ERROR]\Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[925,29] cannot find symbol
[ERROR] symbol : variable Version
[ERROR] location: class javax.mail.Session
[ERROR] \Workarea\mySourceData\src\Mail\mail\src\main\java\javax\mail\Session.java:[928,29] cannot find symbol
[ERROR] symbol : variable Version
[ERROR] location: class javax.mail.Session
[ERROR] -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal o
rg.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (default-compile) on
project javax.mail: Compilation failure
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:153)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:145)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:84)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProje
ct(LifecycleModuleBuilder.java:59)
at org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBu
ild(LifecycleStarter.java:183)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute(Lifecycl
eStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:57)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Laun
cher.java:290)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.jav
a:230)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(La
uncher.java:409)
at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:
352)
Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation fail
ure
at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompiler
Mojo.java:656)
at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:128)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(Default
BuildPluginManager.java:101)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor
.java:209)
... 19 more
[ERROR]
[ERROR]
[ERROR] For more information about the errors and possible solutions, please rea
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExceptionSame issue I am facing when I am trying to build Java Mail with netbeans - 7.2.1, it getting failed with same version issue in Session.java class.
How can I set this Version in Session.java class to get rid of this error?
If we can use nexus repository then please let me know how to set this.
Thanks,
Neelam Sharma

I answered this question here:
http://stackoverflow.com/questions/14217596/failed-to-build-java-mail-api-1-4-5-with-maven-3-0-4/14288418#14288418

Maven Plugin - Developer Preview

JDeveloper Team,
We have not had another developer preview for maven plugin in a while. After playing with the initial version, a lot of us had reported many suggestions and enhancements. Particularly, the ability to directly open a POM file at the project level and workspace level, automatically including the libraries etc. We would like to hear any update on this. Please let us know.
Thank you,
Bala Raman.

We certainly appreciated all of the feedback. During the development process, we had to make some changes to the Maven extension to make it work with the next major JDeveloper release (codename "Sherman"). Therefore, we're unable to release any additional previews of the extension until that next major release is ready, at which point the Maven extension will finally be ready too.
-- Brian

Build problem with Maven

Hi.
I have upgraded from 1.5 APT to the 1.6 method of doing compile time annotations, and I am runing into a problem trying to build a jar containing my annotations processor.
I get the error from maven (mvn package)
[INFO] Compilation failure
error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider annotations.processing.processors.CodeAnnotationProcessor not found
I have the following directory structure
src
--main
----java
------annotations
--------processing
----------processors
------------CodeAnnotationProcessor.java
----------annotations
------------CodeAnnotation.java
----resources
------META-INF
--------service
----------javax.annotation.processing.Processor
I build this with the following with maven
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
    <modelVersion>4.0.0</modelVersion>
    <groupId>mygroup</groupId>
    <artifactId>annotations-processor</artifactId>
    <packaging>jar</packaging>
    <version>1.0.0</version>
    <name>annotations-processor</name>
    <url>http://maven.apache.org</url>
    <dependencies>
        <dependency>
            <groupId>com.sun</groupId>
            <artifactId>tools</artifactId>
            <version>1.4.2</version>
            <scope>system</scope>
            <systemPath>C:/Java/jdk1.6.0_10/lib/tools.jar</systemPath>
        </dependency>
    </dependencies>
    <build>
        <plugins>
            <plugin>
                <artifactId>maven-compiler-plugin</artifactId>
                <configuration>
                    <source>1.6</source>
                    <target>1.6</target>
                </configuration>
            </plugin>
        </plugins>
    </build>
</project>The javax.annotation.processing.Processor file contains
annotations.processing.processors.CodeAnnotationProcessorAny my
package annotations.processing.processors;
import javax.annotation.processing.AbstractProcessor;
import javax.annotation.processing.RoundEnvironment;
import javax.annotation.processing.SupportedSourceVersion;
import javax.annotation.processing.SupportedAnnotationTypes;
import javax.lang.model.element.TypeElement;
import javax.lang.model.SourceVersion;
import java.util.Set;
@SupportedAnnotationTypes(
        "annotations.processing.annotations.CodeAnnotation")
@SupportedSourceVersion(SourceVersion.RELEASE_6)
public class CodeAnnotationProcessor extends AbstractProcessor {
    public boolean process(Set<? extends TypeElement> annotations,
                           RoundEnvironment roundEnv) {
        return true;
}And my CodeAnnotation is as follows
package annotations.processing.annotations;
import java.lang.annotation.Target;
import java.lang.annotation.ElementType;
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
@Target(ElementType.TYPE)
@Retention(RetentionPolicy.SOURCE)
public @interface CodeAnnotation {
}

Milesy wrote:
Hi.
I have upgraded from 1.5 APT to the 1.6 method of doing compile time annotations, and I am runing into a problem trying to build a jar containing my annotations processor.
I get the error from maven (mvn package)
[INFO] Compilation failure
error: Bad service configuration file, or exception thrown while constructing Processor object: javax.annotation.processing.Processor: Provider annotations.processing.processors.CodeAnnotationProcessor not foundFor me it worked when I used the settings
<plugins>
<plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-compiler-plugin</artifactId>
      <configuration>
        <source>1.6</source>
        <target>1.6</target>
        <fork>true</fork>
        <executable>${java.home}/../bin/javac</executable>
        <compilerArgument>-proc:none</compilerArgument>
      </configuration>
    </plugin>
</plugins>
...Forking the compiler is perhaps not the best option, but its just for the annotation processor.

Passing keyStore to weblogic-maven-plugin (WLS 12.1.3) via command line

Hello
I currently try to pass a keyStore (or trustStore) to the weblogic-maven-plugin
The WLS 12.1.3 server uses a self-signed certificate. I imported it into cacerts (within the JRE). This way I can use the plugin to deploy an ear file (over t3s:).
What I want to do is allow Jenkins CI servers to do the same. But using the default cacaerts included in the JRE fails (SSLHAndshake). And none of the -D parameters for the keystore seem to be picked up by the weblogic-maven-plugin?
(like "-Djavax.net.ssl.keyStore=...")
Is there a way to let the plugin know what keyStore it should use?
I also tried using the properties-maven-plugin to set these system properties. But it seems the weblogic-maven-plugin runs in its own world...
Any hints would be great!
Thanks!

There is a solution at Stackoverflow: http://stackoverflow.com/questions/6224787/weblogic-maven-plugin-with-ssl-problem

Good strategies for building ATG EAR with Maven?

It's been a while since I've looked at this. is there a clean set of choices for building an ATG-based EAR using Maven? Is the best we can do to use the antrun plugin, or is there a cleaner integration with Maven to do this? Is there reasonable documentation someone can point me to that details the strategies?

Yes while using Maven, chances are that we may end up using the Ant task for invoking ATG's runAssembler inside pom to build the EAR. While using the Ant task within Maven helps us accomplishing the task but we tend to loose the power of Maven that way. It would be better if we either use Ant for the whole stuff or just Maven without mixing them.
There is ATG DUST(Dynamo Unit and System Tests) framework for building JUnit tests for ATG applications which uses Maven.
http://atgdust.sourceforge.net/first-test.html
But I think DUST uses Maven just to build the JARs and does not uses ATG's assembler.
I have never tried it but you may want to take a look at this Maven plugin which seems to be capable of generating ATG based EAR.
http://jira.codehaus.org/browse/MOJO-1116
Although it seem to be not updated off late. The plugin page mentions ATG 7.1 while the latest ATG offering is 10.1.1 But I guess it might work with a recent ATG version also (may be with some tweaks) as I don't think there would have been any major changes in the way ATG's runAssembler works and generates ATG EAR.

FlexPMD maven plugin no longer useable with Maven due to imcompatible binaries?

Similar Messages

Maybe you are looking for