geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben Liang <ben.liang.j...@gmail.com>
Subject Build Error:Embedded error: Cannot deploy the requested application module because no deploy er is able to handle it.
Date Tue, 02 Feb 2010 05:27:15 GMT
Hi all,

I am trying build geronimo trunk but I got build error which is caused by
deploy error:


[INFO] Started deployer:
org.apache.geronimo.configs/connector-deployer-1_6/3.0-
SNAPSHOT/car
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] could not package plugin

Embedded error: Cannot deploy the requested application module because no
deploy
er is able to handle it.  This can happen if you have omitted the J2EE
deploymen
t descriptor, disabled a deployer module, or if, for example, you are trying
to
deploy an EJB module on a minimal Geronimo server that does not have EJB
support
 installed.
(planFile=D:\g30\plugins\system-database\system-database\target\wor
k\plan.xml, moduleFile=C:\Documents and
Settings\Administrator\.m2\repository\or
g\tranql\tranql-connector-derby-embed-xa\1.5\tranql-connector-derby-embed-xa-1.5
.rar)
[INFO]
------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: could not package
plugin

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:703)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:540)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:519)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:371)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:332)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:181)
        at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
        at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
        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:597)
        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.MojoExecutionException: could not package
plu
gin
        at
org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.
java:246)
        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:483)
        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:678)
        ... 16 more
Caused by: org.apache.geronimo.common.DeploymentException: Cannot deploy the
req
uested application module because no deployer is able to handle it.  This
can ha
ppen if you have omitted the J2EE deployment descriptor, disabled a deployer
mod
ule, or if, for example, you are trying to deploy an EJB module on a minimal
Ger
onimo server that does not have EJB support installed.
(planFile=D:\g30\plugins
\system-database\system-database\target\work\plan.xml,
moduleFile=C:\Documents a
nd
Settings\Administrator\.m2\repository\org\tranql\tranql-connector-derby-embed
-xa\1.5\tranql-connector-derby-embed-xa-1.5.rar)
        at org.apache.geronimo.deployment.Deployer.deploy(Deployer.java:238)
        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:597)
        at
org.apache.geronimo.gbean.runtime.ReflectionMethodInvoker.invoke(Refl
ectionMethodInvoker.java:34)
        at
org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperatio
n.java:131)
        at
org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.
java:856)
        at
org.apache.geronimo.kernel.basic.BasicKernel.invoke(BasicKernel.java:
245)
        at
org.apache.geronimo.mavenplugins.car.PackageMojo.invokeDeployer(Packa
geMojo.java:558)
        at
org.apache.geronimo.mavenplugins.car.PackageMojo.buildPackage(Package
Mojo.java:376)
        at
org.apache.geronimo.mavenplugins.car.PackageMojo.execute(PackageMojo.
java:243)
        ... 18 more
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 12 minutes 13 seconds
[INFO] Finished at: Tue Feb 02 13:15:04 CST 2010

pls help me to figure out why does it happen?

-- 
Best Regards
Ben Liang

Mime
View raw message