geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Mulder <ammul...@alumni.princeton.edu>
Subject Re: Building the geronimo servers using the packaging and assembly plugins
Date Mon, 21 Nov 2005 22:02:04 GMT
I get a stack dump in the build of the maven-deployment-plugin, but it
doesn't cause the build to stop:

Caught exception evaluating:
org.apache.commons.jexl.ExpressionImpl@d89088. Reason:
java.lang.NullPointerException
java.lang.NullPointerException
        at java.io.File.<init>(File.java:180)
        at org.apache.maven.project.Project.parentBasedir(Project.java:342)
        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.apache.commons.jexl.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:268)
        at org.apache.commons.jexl.parser.ASTMethod.execute(ASTMethod.java:61)
        at org.apache.commons.jexl.parser.ASTReference.execute(ASTReference.java:68)
        at org.apache.commons.jexl.parser.ASTReference.value(ASTReference.java:50)
        at org.apache.commons.jexl.ExpressionImpl.evaluate(ExpressionImpl.java:86)
        at org.apache.commons.jelly.expression.jexl.JexlExpression.evaluate(JexlExpression.java:69)
        at org.apache.commons.jelly.tags.core.SetTag.doTag(SetTag.java:84)
        at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)
        at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
        at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:186)
        at org.apache.maven.werkz.jelly.ProjectTag.doTag(ProjectTag.java:128)
        at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)
        at org.apache.maven.plugin.PluginManager.runScript(PluginManager.java:1169)
        at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:669)
        at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
        at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:368)
        at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)
        at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
        at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78)
        at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:109)
        at org.apache.maven.werkz.Goal.fire(Goal.java:656)
        at org.apache.maven.werkz.Goal.attain(Goal.java:592)
        at org.apache.maven.werkz.WerkzProject.attainGoal(WerkzProject.java:210)
        at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:114)
        at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)
        at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
        at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78)
        at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:109)
        at org.apache.maven.werkz.Goal.fire(Goal.java:656)
        at org.apache.maven.werkz.Goal.attain(Goal.java:592)
        at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:693)
        at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
        at org.apache.maven.cli.App.doMain(App.java:511)
        at org.apache.maven.cli.App.main(App.java:1258)
        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 com.werken.forehead.Forehead.run(Forehead.java:551)
        at com.werken.forehead.Forehead.main(Forehead.java:581)

The during config building, I get this:

+----------------------------------------
| Executing multiproject:install-callback System Configuration for the
J2EE Server
| Memory: 8M/12M
+----------------------------------------
DEPRECATED: the default goal should be specified in the <build>
section of project.xml instead of maven.xml
DEPRECATED: the default goal should be specified in the <build>
section of project.xml instead of maven.xml

build:end:

You are working offline so the build will continue, but
geronimo-packaging-plugin-1.0-SNAPSHOT.jar may be out of date!
You are working offline so the build will continue, but
geronimo-gbean-deployer-1.0-SNAPSHOT.car may be out of date!
build:start:

multiproject:install-callback:
    [echo] Running car:install for System Configuration for the J2EE Server

BUILD FAILED
File...... /Users/ammulder/.maven/cache/maven-multiproject-plugin-1.4.1/plugin.jelly
Element... maven:reactor
Line...... 218
Column.... -1
Unable to obtain goal [multiproject:install-callback] --
/Users/ammulder/.maven/cache/geronimo-packaging-plugin-1.0-SNAPSHOT/plugin.jelly:66:-1:
<car:package> org.apache.geronimo.plugin.packaging.PackageBuilder
Total time   : 8 seconds
Finished at  : Monday, November 21, 2005 5:00:59 PM EST

Aaron

On 11/21/05, David Jencks <david_jencks@yahoo.com> wrote:
> I've been working on building the geronimo server with the packaging
> and assembly plugins.  There are a few loose ends but I believe the
> resulting servers work.  The build process is not yet completely
> automated, so here is an outline of what to do.
>
> Please try it out and report problems.
>
> 1. build geronimo + openejb using maven -o, maven -o m:rebuild, or some
> such.  You can stop the build when you get to the assembly module, and
> certainly when you get to itests.
>
> 2. build the plugins explicitly:
> cd plugins
> maven -o multiproject:install
> cd ..
>
> 3. build the configs:
> cd configs
> maven -o multiproject:install
> cd ..
>
> This step uses the packaging plugin to build all the configurations we
> need for both jetty and tomcat servers, and installs them in your local
> maven repo as .car files.
>
> 4. build the servers:
> cd assemblies
> cd j2ee-jetty-server
> maven -o clean default
>
> cd ../j2ee-tomcat-server
> maven -o clean default
>
> ------------------------------------
>
> Warning:
> The configIds of these configurations are incompatible with the
> configIds used by the previous assembly.  If you deploy anything on
> these servers and you specify a parentId or an import you will have to
> modify them.
>
> I have not tried to deploy any applications to either of these servers,
> but the welcome and console apps seem to work fine.
>
> Known limitations:
> The database for the juddi server is not yet constructed
> The j2ee schema files are not yet included in the server
>
> I've had some problems with the console on tomcat, but I think the
> version in svn currently works.  I'm trying to finish up some changes
> on my machine and check in the "next version" of tomcat directory
> setup.
>
> Thanks!
> david jencks
>
>

Mime
View raw message