Doing that now ... thanks.
Martin van den Bemt wrote:
Looks like your xml is treated as text..
You better move this thread to maven-dev or maven-user.. :)
Mvgr,
Martin
On Fri, 2003-01-24 at 19:54, Jeffrey Dever wrote:
There is definately somthing wrong with my environment. When I run that
i get:
build:
<reactor:execute banner="Building" goals="clean,jar:install"
glob="*/project.xml" ignoreFailures="true"
basedir="/home/jsdever/cvs-commit/jakarta-commons"></reactor:execute>
BUILD SUCCESSFUL
Total time: 31 seconds
But it was completely unsuccessful, other than downloading the dependancies.
Henri Yandell wrote:
By the way, building commons itself seems to give:
[ERROR] File...... /usr/local/javalib/maven-1.0-beta-7/plugins/maven-reactor-plugin-1.0/plugin.jelly
[ERROR] Element... reactor:reactor
[ERROR] Line...... 32
[ERROR] Column.... 9
[ERROR] The content of elements must consist of well-formed character data or markup.
Hen
On 24 Jan 2003, Martin van den Bemt wrote:
Probably. Never looked at a solution though (using maven head from
31/12/2002 on windows and the latest maven-head on linux afaik).
If I have time i'll see if maven head is usable for commons..
Mvgr,
Martin
On Fri, 2003-01-24 at 19:34, Henri Yandell wrote:
So what you're saying is that a new maven user cannot build, but an old
maven user can? Because us old users of maven have the snapshots, but the
new ones do not?
So another way to solve it would be via a zipped patch the new user could
overlay on their maven-home?
Hen
On 24 Jan 2003, Martin van den Bemt wrote:
There are known problems with the b7 installation if you do that at
present (as far as I understood), since maven is depending on snapshots
and the snapshots are not currently anymore working on the b7 one..
So maybe you going to have to use maven-head because of that.
If I am wrong, please correct me :)
Mvgr,
Martin
On Fri, 2003-01-24 at 19:27, Henri Yandell wrote:
I've done a cvs update on commons, and have successfully built [well it
fails on a test] httpclient with just: cd httpclient; maven
So something weird is up.
Maybe your b7 is damaged? You could try reinstalling and see if that fixes
it? [yes, I've been using Windows all week!]
Hopefully a 3rd person can give it a try so we can see which one of us has
the weird setup.
Hen
On Fri, 24 Jan 2003, Jeffrey Dever wrote:
b7
$MAVEN_HOME is set correctly and $MAVEN_HOME/bin is in my path. I'm
perplexed.
-jsd
Henri Yandell wrote:
java:jar is afaik, the default goal to run. it's basically 'compile'.
logging and lang both work for me. I'm on the latest stable maven, b7.
What verison are you on?
On Fri, 24 Jan 2003, Jeffrey Dever wrote:
I have tried running maven in a commons subdirectory, such as logging
and httpclient. maven does go away and download the dependancies, but
then reports:
[ERROR] BUILD FAILED
[ERROR] Goal "java:jar" does not exist in this project.
Total time: 14 seconds
I don't see where this goal is defined. Its not in the project.xml for
the particular project or commons, and does not appear to come from the
common maven.xml file either.
-jsd
Henri Yandell wrote:
If you go into a particular component and type 'maven', it should build
that project. I tend to use maven and maven site.
However, how you do the big build of all components at the same time, I'm
also clueless on.
Hen
On Fri, 24 Jan 2003, Jeffrey Dever wrote:
In my local checkout of jakarta-commons, when I run *maven -g* I only
the follwoing non documented goals:
build
build:start
deploy-front-end-site
site
site-front-end
When I run *maven build:start* I get:
BUILD SUCCESSFUL
Total time: 14 seconds
But in reality it did nothing, no other output, no generated files.
None of the other targets to anything useful either. I have tried with
mavenb5 and b7 running on a linux box.
How do we build commons with maven? How do I build a particular
component withing commons? I couldn't find any instructions on this.
-jsd
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
