Well, its related to the NTLM support in HttpClient. A few tests fail,
but I would suspect any NTLM use in 1.3 would fail similarly. Most of
the httpclient guys have been working on 1.4 (I did the release build in
1.4) and the gump builds don't fail so I guess its using 1.4 as well.
I've brou
Yeah. Linux jdk 1.3. Sun's.
Hen
On Sun, 26 Jan 2003 [EMAIL PROTECTED] wrote:
> Hen is this jdk1.3?
>
> HttpClient has failed building for me on 1.3 for some months now.
> --
> dIon Gillard, Multitask Consulting
> Blog: http://www.freeroller.net/page/dion/Weblog
> Work: http://www.mult
a7 to build
> stuff.(xdoc
> > task doe's not work in current cvs)
> >
> > - Original Message -
> > From: <[EMAIL PROTECTED]>
> > To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
> > Sent: Sunday, January 26, 2003 2:53
er I build maven, possible I do something wrong.
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Sunday, January 26, 2003 3:19 PM
Subject: Re: help building commons with maven
> The xdoc tasks work fine f
We care!
[EMAIL PROTECTED] wrote:
Henri Yandell <[EMAIL PROTECTED]> wrote on 25/01/2003 05:33:50 AM:
On Fri, 24 Jan 2003, Craig R. McClanahan wrote:
I'm not a Maven guru, but it's not clear to me that the maven.xml and
project.xml files for all of the Commons projects have been kept u
gt;
> Sent: Sunday, January 26, 2003 2:53 PM
> Subject: Re: help building commons with maven
>
>
> > It's not possible to change the cvs access mechanism for b7.
> >
> > It was hardwired to use the CVS directory information on your machine.
> >
> >
6, 2003 2:53 PM
Subject: Re: help building commons with maven
> It's not possible to change the cvs access mechanism for b7.
>
> It was hardwired to use the CVS directory information on your machine.
>
> b8 uses the details specified in project.xml.
> --
>
ers List" <[EMAIL PROTECTED]>
Sent: Sunday, January 26, 2003 2:29 PM
Subject: Re: help building commons with maven
> - Original Message -
> From: "Juozas Baliuka" <[EMAIL PROTECTED]>
> To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]&
It's not possible to change the cvs access mechanism for b7.
It was hardwired to use the CVS directory information on your machine.
b8 uses the details specified in project.xml.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multi
- Original Message -
From: "Juozas Baliuka" <[EMAIL PROTECTED]>
To: "Jakarta Commons Developers List" <[EMAIL PROTECTED]>
Sent: Sunday, January 26, 2003 1:11 PM
Subject: Re: help building commons with maven
>
>
> > If you care, let me
> If you care, let me know, and I'll work with you on getting the
> descriptors up to date when b8 is released.
I have problems to generate reports with beta7, I have tried cvs version
and it works, It seems it doe's not uses
ssh to connect to cvs server.
Is it possible to set some parameter on
Hen is this jdk1.3?
HttpClient has failed building for me on 1.3 for some months now.
--
dIon Gillard, Multitask Consulting
Blog: http://www.freeroller.net/page/dion/Weblog
Work: http://www.multitask.com.au
Henri Yandell <[EMAIL PROTECTED]> wrote on 25/01/2003 04:13:18 PM:
>
>
> On
Henri Yandell <[EMAIL PROTECTED]> wrote on 25/01/2003 05:33:50 AM:
>
>
> On Fri, 24 Jan 2003, Craig R. McClanahan wrote:
>
> >
> >
> >
> > I'm not a Maven guru, but it's not clear to me that the maven.xml and
> > project.xml files for all of the Commons projects have been kept up to
> > date (o
A few more questions:
Where does the nice navigation bar on the left come from? There is one
string I want to change (HTTP Client to HttpClient) and a few entries
that should be removed (like Contributors which is redundant compared to
Project Info -> Project Team). There are a few other thin
On Sat, 25 Jan 2003, Jeffrey Dever wrote:
> Yea, worked for me too. I have been making some changes in there, so
> you need a clean checkout. (does maven do a checkout of the source
> files, or just compiles what is already checkout and is local?)
Maven will build whatever is on your local di
Yea, worked for me too. I have been making some changes in there, so
you need a clean checkout. (does maven do a checkout of the source
files, or just compiles what is already checkout and is local?)
-jsd
Martin Cooper wrote:
On Sat, 25 Jan 2003, Henri Yandell wrote:
On Fri, 24 Jan 2003,
On Sat, 25 Jan 2003, Jeffrey Dever wrote:
> I re-downloaded it and reinstalled in another location. Now it "just
> works". Not sure what the root cause was, will investigate later. Too
> busy with updating the httpclient xdocs to worry and am just happy I can
> maven build.
Maven is very coo
On Sat, 25 Jan 2003, Henri Yandell wrote:
>
>
> On Fri, 24 Jan 2003, Martin Cooper wrote:
>
> >
> >
> > On Fri, 24 Jan 2003, 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; m
On Fri, 24 Jan 2003, Martin Cooper wrote:
>
>
> On Fri, 24 Jan 2003, 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
>
> I just tried building HttpClient and it built and unit
I re-downloaded it and reinstalled in another location. Now it "just
works". Not sure what the root cause was, will investigate later. Too
busy with updating the httpclient xdocs to worry and am just happy I can
maven build.
-jsd
Martin Cooper wrote:
On Fri, 24 Jan 2003, Henri Yandell wrot
On Fri, 24 Jan 2003, 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?
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
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:
> glob="*/project.xml" ignoreFailu
There is definately somthing wrong with my environment. When I run that
i get:
build:
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..
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 charac
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
Of course, ibiblio.org/maven being down yet again does not help.
Hen
On Fri, 24 Jan 2003, 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 anothe
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 va
On Fri, 24 Jan 2003, Craig R. McClanahan wrote:
>
>
>
> I'm not a Maven guru, but it's not clear to me that the maven.xml and
> project.xml files for all of the Commons projects have been kept up to
> date (or even created in the first place), particularly for those
> projects that started out w
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 corre
On Fri, 24 Jan 2003, Jeffrey Dever wrote:
> Date: Fri, 24 Jan 2003 13:02:50 -0500
> From: Jeffrey Dever <[EMAIL PROTECTED]>
> Reply-To: Jakarta Commons Developers List <[EMAIL PROTECTED]>
> To: Jakarta Commons Developers List <[EMAIL PROTECTED]>
> Subject: Re:
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
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 2
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 httpclie
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.
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-
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 outpu
37 matches
Mail list logo
