Berin Loritsch wrote:

Dude, Maven is like ANT.  If you type $ant in the wrong directory you
will get the same type of problem.

Go to the ${avalon.home}/framework directory before you type $maven.

The avalon/buildsystem is the part that is designed to be reused around
the whole system.

I tried that. If I go into framework and type "maven", I get the long message that tells me
about the "maven avalon:jars" target. However when I try that, I get the following:
---
Starting the reactor...


BUILD FAILED
.\project-common.xml (The system cannot find the file specified)
Total time:  4 seconds
---

If I try running in the fortress directory I get the following error: This seems like a
bug in maven caused by the lack of a maven.xml file:
---
java.lang.NullPointerException
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:362)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
at org.apache.maven.cli.App.doMain(App.java:524)
at org.apache.maven.cli.App.main(App.java:1080)
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:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
Total time: 1 seconds
---


Going into the "fortress/tools" tools directory and running "maven", I once
again get the large message telling me about the "maven avalon:jars" target.
Running this I get the following:
---
Starting the reactor...
WARN: Exception: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
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.collections.BeanMap.get(Unknown Source)
at org.apache.maven.MavenUtils.mergeBeans(MavenUtils.java:433)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:230)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:160)
at org.apache.maven.MavenUtils.getProjects(MavenUtils.java:305)
at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:311)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
at org.apache.maven.cli.App.doMain(App.java:524)
at org.apache.maven.cli.App.main(App.java:1080)
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:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
Caused by: java.lang.NullPointerException
at java.util.TreeMap.compare(TreeMap.java:1081)
at java.util.TreeMap.put(TreeMap.java:459)
at java.util.TreeSet.add(TreeSet.java:205)
at org.apache.maven.project.Project.getDependentProjectIds(Project.java:666)
... 26 more
WARN: Exception: java.lang.reflect.InvocationTargetException
java.lang.reflect.InvocationTargetException
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.collections.BeanMap.get(Unknown Source)
at org.apache.commons.collections.BeanMap.put(Unknown Source)
at org.apache.maven.MavenUtils.mergeBeans(MavenUtils.java:438)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:230)
at org.apache.maven.MavenUtils.getProject(MavenUtils.java:160)
at org.apache.maven.MavenUtils.getProjects(MavenUtils.java:305)
at org.apache.maven.jelly.tags.maven.ReactorTag.doTag(ReactorTag.java:311)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:279)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
at org.apache.commons.jelly.TagSupport.invokeBody(TagSupport.java:233)
at com.werken.werkz.jelly.GoalTag$1.performAction(GoalTag.java:116)
at com.werken.werkz.Goal.fire(Goal.java:639)
at com.werken.werkz.Goal.attain(Goal.java:575)
at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:394)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:357)
at org.apache.maven.cli.App.doMain(App.java:524)
at org.apache.maven.cli.App.main(App.java:1080)
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:543)
at com.werken.forehead.Forehead.main(Forehead.java:573)
Caused by: java.lang.NullPointerException
at java.util.TreeMap.compare(TreeMap.java:1081)
at java.util.TreeMap.put(TreeMap.java:459)
at java.util.TreeSet.add(TreeSet.java:205)
at org.apache.maven.project.Project.getDependentProjectIds(Project.java:666)
... 27 more


BUILD FAILED
java.lang.NullPointerException
Total time:  6 seconds
---

Rather than assume that the build was broken, I attempted to ask for any
ideas as to what is >>I<< was doing wrong. Of the above messages, only
one is a nice ant like descriptive message. Ant that only tells me that it can
not find the .\project-common.xml file. This file does not exist in the
framework directory which lead me to believe that I should not be running
maven from that directory.


You are obviously not getting these problems, so for starters, what is the
exact build target that you are running to get fortress and framework to
build?

As a note, the README.TXT file in the avalon root includes the following:
---
The avalon buildfiles use a common buildsystem which utilizes maven and
forrest. You will need to download and install maven, the
maven-forrest-plugin, and the avalon-buildsystem module. After doing so,
change into the buildsystem directory and type `maven avalon:info` to
get yourself started.
---

As I said earlier, I was not able to locate the avalon-buildsystem module so
have not installed that. Is that maybe my problem? Running
"maven avalon:info" simply tells me about the "maven avalon:jars" target.
Running that in the buildsystem directory produces the error that I originally
posted about.


Cheers,
Leif



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to