You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Leif Mortenson <le...@tanukisoftware.com> on 2003/07/15 06:24:24 UTC
Conflicts in sourceresolve
For the past couple months, I have been getting the following conflicts
whenever I do
an update on avalon-excalibur. I assumed that it was a work in progress
and would
be resolved. But the problem never went away. It is being caused because the
meta information files are being modified by the build and also checked
in by other
users. Because the files are checked in as binary files, CVS is unable
to do a
clean merge and detect that they have not actually changed. Do these
files really
need to be in CVS? If so, then the build should probably be modified so
that CVS
versions are used rather than locally built versions.
Also, all of these files appear to be valid text files. Is there any
reason why they could
not be checked in as text files?
Cheers,
Leif
cvs server: Updating sourceresolve/examples
cvs server: Updating sourceresolve/src
cvs server: Updating sourceresolve/src/conf
cvs server: Updating sourceresolve/src/fortress.meta
cvs update: move away sourceresolve/src/fortress.meta/services.list; it
is in the way
C sourceresolve/src/fortress.meta/services.list
cvs server: Updating sourceresolve/src/fortress.meta/META-INF
cvs server: Updating sourceresolve/src/fortress.meta/META-INF/services
cvs update: move away
sourceresolve/src/fortress.meta/META-INF/services/org.apache.excalibur.source.SourceFactory;
it is in the way
C
sourceresolve/src/fortress.meta/META-INF/services/org.apache.excalibur.source.SourceFactory
cvs update: move away
sourceresolve/src/fortress.meta/META-INF/services/org.apache.excalibur.source.SourceResolver;
it is in the way
C
sourceresolve/src/fortress.meta/META-INF/services/org.apache.excalibur.source.SourceResolver
cvs server: Updating sourceresolve/src/fortress.meta/org
cvs server: Updating sourceresolve/src/fortress.meta/org/apache
cvs server: Updating sourceresolve/src/fortress.meta/org/apache/excalibur
cvs server: Updating
sourceresolve/src/fortress.meta/org/apache/excalibur/source
cvs server: Updating
sourceresolve/src/fortress.meta/org/apache/excalibur/source/impl
cvs update: move away
sourceresolve/src/fortress.meta/org/apache/excalibur/source/impl/FileSourceFactory.meta;
it is in the way
C
sourceresolve/src/fortress.meta/org/apache/excalibur/source/impl/FileSourceFactory.meta
cvs update: move away
sourceresolve/src/fortress.meta/org/apache/excalibur/source/impl/ResourceSourceFactory.meta;
it is in the way
C
sourceresolve/src/fortress.meta/org/apache/excalibur/source/impl/ResourceSourceFactory.meta
U
sourceresolve/src/fortress.meta/org/apache/excalibur/source/impl/SourceResolverImpl.deps
cvs update: move away
sourceresolve/src/fortress.meta/org/apache/excalibur/source/impl/SourceResolverImpl.meta;
it is in the way
C
sourceresolve/src/fortress.meta/org/apache/excalibur/source/impl/SourceResolverImpl.meta
cvs update: move away
sourceresolve/src/fortress.meta/org/apache/excalibur/source/impl/URLSourceFactory.meta;
it is in the way
C
sourceresolve/src/fortress.meta/org/apache/excalibur/source/impl/URLSourceFactory.meta
cvs server: Updating sourceresolve/src/java
cvs server: Updating sourceresolve/src/java/org
cvs server: Updating sourceresolve/src/java/org/apache
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Conflicts in sourceresolve
Posted by Leif Mortenson <le...@tanukisoftware.com>.
peter@realityforge.org wrote:
>>Ok, then maybe this isn't completely me being stupid then. :-) (Maybe)
>>I have been trying to get Avalon-framework and Fortress to build and have
>>
>>
>not
>
>
>>had much success since it was Mavenized.
>>...
>>Any ideas where to proceed?
>>
>>
>
>sorry - I just reverted to hacking the ant scripts ;)
>
Sigh... I was afraid of that.... :-P
Any idea when the build in CVS will be fixed. It has been like this for
a while...
Cheers,
Leif
Re: Conflicts in sourceresolve
Posted by pe...@realityforge.org.
> Ok, then maybe this isn't completely me being stupid then. :-) (Maybe)
> I have been trying to get Avalon-framework and Fortress to build and have
not
> had much success since it was Mavenized.
> ...
> Any ideas where to proceed?
sorry - I just reverted to hacking the ant scripts ;)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Conflicts in sourceresolve
Posted by Paul Hammant <Pa...@ThoughtWorks.net>.
Leif,
> I have downloaded and installed Maven 1.0b9 and from what I can tell
> it is working
> correctly.
I'm using a per-10 HEAd version from a few weeks ago and get the same.
- Paul
--
http://www.thoughtworks.com -> The art of heavy lifting.
Home for many Agile practicing, Open Source activists...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Build directions (was Re: Conflicts in sourceresolve)
Posted by Leif Mortenson <le...@tanukisoftware.com>.
Ok, I finally got framework and fortress to build again. The problem is
that
Version 1.0b9 of Maven does not work. After upgrading to 1.0b10 things
started working. Wish I had tried that earlier. :-/
Cheers,
Leif
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Build directions (was Re: Conflicts in sourceresolve)
Posted by Leif Mortenson <le...@tanukisoftware.com>.
Thank you. I had not seen the "jar" and "test" goals.
However, I tried "maven jar" in the framework directory and get the
following:
---
avalon:version-override:
[echo]
overriding version; setting to: 4.1.5-RC2
avalon:init:
avalon:compile-api:
[javac] Compiling 1 source file to
C:\Jakarta\avalon\framework\target\api
avalon:compile-impl:
[javac] Compiling 1 source file to
C:\Jakarta\avalon\framework\target\impl
avalon:custom-compile:
[copy] Copying 1 file to C:\Jakarta\avalon\framework\target\classes
[copy] Copying 1 file to C:\Jakarta\avalon\framework\target\classes
INTERNAL ERROR
Reference made to goal 'java:compile' which has no definition.
---
Running "maven jar" in the avalon/fortress/tools directory produces:
---
avalon:version-override:
[echo]
overriding version; setting to: 1.1-dev
INTERNAL ERROR
Reference made to goal 'java:compile' which has no definition.
---
I am using Maven 1.0b9 Is that what you are using or is there a need to
upgrade to 1.0b10?
Sorry for all the questions.
Leif
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Build directions (was Re: Conflicts in sourceresolve)
Posted by Berin Loritsch <bl...@apache.org>.
Leif Mortenson wrote:
>
> 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.
Hmmm... I type
$maven test
or
$maven jar
and it builds ok for me.
>
> 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?
"test" or "jar"
The reactor is only for projects that have a set of "subprojects
>
> 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.
> ---
The "avalon-buildsystem" "module" is the buildsystem directory structure
in the main ${avalon} repository.
>
> 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.
We need to change the default target.
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Conflicts in sourceresolve
Posted by Leif Mortenson <le...@tanukisoftware.com>.
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: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Conflicts in sourceresolve
Posted by Berin Loritsch <bl...@apache.org>.
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.
Leif Mortenson wrote:
> Ok, then maybe this isn't completely me being stupid then. :-) (Maybe)
> I have been trying to get Avalon-framework and Fortress to build and
> have not
> had much success since it was Mavenized.
>
> I have downloaded and installed Maven 1.0b9 and from what I can tell it
> is working
> correctly.
> Running "maven" from within the avalon/buildsystem directory I get a
> rather long
> document... From within that there is a note about downloading and
> installing the
> maven-forrest-plugin. Did that and put it into the maven plugins directory.
>
> When I then run "maven avalon:jars", I get the following output:
> ---
> <snip>
> Starting the reactor...
> Our processing order:
> Avalon Build System
> Avalon-Framework
> +----------------------------------------
> | Excalibur is building jar: Avalon Build System
> | Memory: 2M/3M
> +----------------------------------------
>
> BUILD FAILED
> Goal [java:compile] has no action definition.
> Total time: 10 seconds
> ---
>
> The README.txt file in the avalon root dir mentions that I also need to
> install
> the avalon-buildsystem module. This may be a cause of my problems, but I
> can't seem to locate where to download it from.
>
> Any ideas where to proceed?
>
> Thanks in advance,
> Leif
>
> peter@realityforge.org wrote:
>
>>>There are also some problems with the new Mavenization of Framework and
>>>the knock on consequences for Excalibur. Many default.properties files
>>>name a relative target directory for the framework jar, but the jar does
>>>not exist. Not a problem for users who remain in IDEs.
>>>
>>>
>>
>>yep - Large chunks of excalibur have not been building for a bit.
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
>>For additional commands, e-mail: dev-help@avalon.apache.org
>>
>>
>>
>>
--
"They that give up essential liberty to obtain a little temporary safety
deserve neither liberty nor safety."
- Benjamin Franklin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Conflicts in sourceresolve
Posted by Leif Mortenson <le...@tanukisoftware.com>.
Ok, then maybe this isn't completely me being stupid then. :-) (Maybe)
I have been trying to get Avalon-framework and Fortress to build and
have not
had much success since it was Mavenized.
I have downloaded and installed Maven 1.0b9 and from what I can tell it
is working
correctly.
Running "maven" from within the avalon/buildsystem directory I get a
rather long
document... From within that there is a note about downloading and
installing the
maven-forrest-plugin. Did that and put it into the maven plugins directory.
When I then run "maven avalon:jars", I get the following output:
---
<snip>
Starting the reactor...
Our processing order:
Avalon Build System
Avalon-Framework
+----------------------------------------
| Excalibur is building jar: Avalon Build System
| Memory: 2M/3M
+----------------------------------------
BUILD FAILED
Goal [java:compile] has no action definition.
Total time: 10 seconds
---
The README.txt file in the avalon root dir mentions that I also need to
install
the avalon-buildsystem module. This may be a cause of my problems, but I
can't seem to locate where to download it from.
Any ideas where to proceed?
Thanks in advance,
Leif
peter@realityforge.org wrote:
>>There are also some problems with the new Mavenization of Framework and
>>the knock on consequences for Excalibur. Many default.properties files
>>name a relative target directory for the framework jar, but the jar does
>>not exist. Not a problem for users who remain in IDEs.
>>
>>
>
>yep - Large chunks of excalibur have not been building for a bit.
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
>For additional commands, e-mail: dev-help@avalon.apache.org
>
>
>
>
Re: Conflicts in sourceresolve
Posted by pe...@realityforge.org.
> There are also some problems with the new Mavenization of Framework and
> the knock on consequences for Excalibur. Many default.properties files
> name a relative target directory for the framework jar, but the jar does
> not exist. Not a problem for users who remain in IDEs.
yep - Large chunks of excalibur have not been building for a bit.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Conflicts in sourceresolve
Posted by Paul Hammant <Pa...@ThoughtWorks.net>.
There are also some problems with the new Mavenization of Framework and
the knock on consequences for Excalibur. Many default.properties files
name a relative target directory for the framework jar, but the jar does
not exist. Not a problem for users who remain in IDEs.
- Paul
>For the past couple months, I have been getting the following conflicts
>whenever I do
>an update on avalon-excalibur.
>
>
--
http://www.thoughtworks.com -> The art of heavy lifting.
Home for many Agile practicing, Open Source activists...
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org