You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hc.apache.org by Bindul Bhowmik <bi...@gmail.com> on 2006/03/19 03:52:29 UTC
[http-core] Wrong pom.xml
Hello,
I checked out the http-core component to my workspace, and XML
validation tool tells me that the pom.xml does not validate against
the maven POM schema.
(schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd").
I have corrected the pom.xml and am attaching the diff. If it is all
right, someone with commit access might want to commit it to the
repository.
The pom.xml for the httpcomponents also did not validate. The patch
for that is also attached to this email.
I was travelling over the past week, so am lagging behind the emails
on the list and am not sure which is the issue tracking tool for http
components. Neither Bugzilla nor Jira have HttpComponents listed. Are
we still using the HttpClient Bugzilla module for issue tracking?
Regards,
Bindul
Re: [http-core] Wrong pom.xml
Posted by Bindul Bhowmik <bi...@gmail.com>.
On 3/21/06, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Sun, 2006-03-19 at 17:11 -0700, Bindul Bhowmik wrote:
> > On 3/19/06, Oleg Kalnichevski <ol...@apache.org> wrote:
> > > Bindul Bhowmik wrote:
> > > > On 3/19/06, Oleg Kalnichevski <ol...@apache.org> wrote:
>
> ...
>
> > > Can you reproduce the problem? As far as I can tell this does seem to be
> > > a bug in Maven.
> >
> > I could reproduce it. But then resolved the problem. The test resource
> > element requires the directory
> > (/project/build/testResources/testResource/directory) element.
> > Strange, the XSD does not mandate this element, but the code fails to
> > validate this.
> >
> > I have created another patch with this fix. It succeeds to compile and
> > run all the tests on my machine.
> >
>
> Patch checked in. Many thanks, Bindul
>
> > BTW, are both 'testSourceDirectory' and 'testResources' required? The
> > same number of tests run on my machine with 'testSourceDirectory'
> > commented.
> >
>
> No idea. However, with 'testSourceDirectory' removed maven seems no
> longer able to find unit tests
>
>
> > No, I am not. But did not see the change coming into my workspace (on
> > SVN update) for quite some time.
> >
> > I apologize if I am taking up too much of your time. Beginners hiccups I guess.
> >
>
> No worries at all. I really appreciate your taking interest in
> HttpComponents.
Thank you. I am using http-client for a couple of years now, and am
lurking on the list for over a year now. I had some spare time, and
something I could contribute... just pitched in. :-)
>
> Cheers,
>
> Oleg
>
>
> > Thanks Oleg.
> >
> > Bindul
> > >
> > > Oleg
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
> > >
> > >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: [http-core] Wrong pom.xml
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Sun, 2006-03-19 at 17:11 -0700, Bindul Bhowmik wrote:
> On 3/19/06, Oleg Kalnichevski <ol...@apache.org> wrote:
> > Bindul Bhowmik wrote:
> > > On 3/19/06, Oleg Kalnichevski <ol...@apache.org> wrote:
...
> > Can you reproduce the problem? As far as I can tell this does seem to be
> > a bug in Maven.
>
> I could reproduce it. But then resolved the problem. The test resource
> element requires the directory
> (/project/build/testResources/testResource/directory) element.
> Strange, the XSD does not mandate this element, but the code fails to
> validate this.
>
> I have created another patch with this fix. It succeeds to compile and
> run all the tests on my machine.
>
Patch checked in. Many thanks, Bindul
> BTW, are both 'testSourceDirectory' and 'testResources' required? The
> same number of tests run on my machine with 'testSourceDirectory'
> commented.
>
No idea. However, with 'testSourceDirectory' removed maven seems no
longer able to find unit tests
> No, I am not. But did not see the change coming into my workspace (on
> SVN update) for quite some time.
>
> I apologize if I am taking up too much of your time. Beginners hiccups I guess.
>
No worries at all. I really appreciate your taking interest in
HttpComponents.
Cheers,
Oleg
> Thanks Oleg.
>
> Bindul
> >
> > Oleg
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
> >
> >
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: [http-core] Wrong pom.xml
Posted by Bindul Bhowmik <bi...@gmail.com>.
On 3/19/06, Oleg Kalnichevski <ol...@apache.org> wrote:
> Bindul Bhowmik wrote:
> > On 3/19/06, Oleg Kalnichevski <ol...@apache.org> wrote:
> >
> >> On Sat, 2006-03-18 at 19:52 -0700, Bindul Bhowmik wrote:
> >>
> >>> Hello,
> >>>
> >>> I checked out the http-core component to my workspace, and XML
> >>> validation tool tells me that the pom.xml does not validate against
> >>> the maven POM schema.
> >>> (schemaLocation="http://maven.apache.org/POM/4.0.0
> >>> http://maven.apache.org/maven-v4_0_0.xsd").
> >>>
> >>> I have corrected the pom.xml and am attaching the diff. If it is all
> >>> right, someone with commit access might want to commit it to the
> >>> repository.
> >>>
> >>>
> >> Hi Bindul
> >>
> >> For some reason Maven2 stopped working for me after applying the patch.
> >>
> >> oleg@dld810:~/src/apache.org/jakarta/httpcomponents/http-core$ mvn clean
> >> [INFO] Scanning for projects...
> >> [INFO]
> >> ----------------------------------------------------------------------------
> >> [ERROR] FATAL ERROR
> >> [INFO]
> >> ----------------------------------------------------------------------------
> >> [INFO] Error building POM (may not be this project's POM).
> >>
> >>
> >> Project ID: org.apache.jakarta.httpcomponents:http-core
> >> POM
> >> Location: /home/oleg/src/apache.org/jakarta/httpcomponents/http-core/pom.xml
> >> Validation Messages:
> >>
> >> [0] 'build.testResources.testResource.directory' is missing.
> >>
> >>
> >> Reason: Failed to validate POM
> >>
> >>
> >> [INFO]
> >> ----------------------------------------------------------------------------
> >> [INFO] Trace
> >> org.apache.maven.reactor.MavenExecutionException: Failed to validate POM
> >> at
> >> org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> >> at
> >> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
> >> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> >> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> >> 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:585)
> >> at
> >> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> >> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> >> at
> >> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> >> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> >> Caused by: org.apache.maven.project.InvalidProjectModelException: Failed
> >> to validate POM
> >> at
> >> org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:781)
> >> at
> >> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:631)
> >> at
> >> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:303)
> >> at
> >> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274)
> >> at
> >> org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
> >> at
> >> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
> >> at
> >> org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
> >> ... 11 more
> >> [INFO]
> >> ----------------------------------------------------------------------------
> >> [INFO] Total time: < 1 second
> >> [INFO] Finished at: Sun Mar 19 13:03:12 CET 2006
> >> [INFO] Final Memory: 1M/2M
> >>
> >> The http-core pom.xml is indeed invalid according to the schema but
> >> Maven 2.0.2 does not seem to mind
> >>
> >
> > Probably need to open an issue with Maven?
> >
> >
>
> Can you reproduce the problem? As far as I can tell this does seem to be
> a bug in Maven.
I could reproduce it. But then resolved the problem. The test resource
element requires the directory
(/project/build/testResources/testResource/directory) element.
Strange, the XSD does not mandate this element, but the code fails to
validate this.
I have created another patch with this fix. It succeeds to compile and
run all the tests on my machine.
BTW, are both 'testSourceDirectory' and 'testResources' required? The
same number of tests run on my machine with 'testSourceDirectory'
commented.
>
> >>> The pom.xml for the httpcomponents also did not validate. The patch
> >>> for that is also attached to this email.
> >>>
> >>>
> >> Patch applied
> >>
> >
> > Thanks. But, did not see a commit.
> >
> >
>
> Are you subscribed to httpclient-commits@jakarta.apache.org?
No, I am not. But did not see the change coming into my workspace (on
SVN update) for quite some time.
I apologize if I am taking up too much of your time. Beginners hiccups I guess.
Thanks Oleg.
Bindul
>
> Oleg
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
>
>
Re: [http-core] Wrong pom.xml
Posted by Oleg Kalnichevski <ol...@apache.org>.
Bindul Bhowmik wrote:
> On 3/19/06, Oleg Kalnichevski <ol...@apache.org> wrote:
>
>> On Sat, 2006-03-18 at 19:52 -0700, Bindul Bhowmik wrote:
>>
>>> Hello,
>>>
>>> I checked out the http-core component to my workspace, and XML
>>> validation tool tells me that the pom.xml does not validate against
>>> the maven POM schema.
>>> (schemaLocation="http://maven.apache.org/POM/4.0.0
>>> http://maven.apache.org/maven-v4_0_0.xsd").
>>>
>>> I have corrected the pom.xml and am attaching the diff. If it is all
>>> right, someone with commit access might want to commit it to the
>>> repository.
>>>
>>>
>> Hi Bindul
>>
>> For some reason Maven2 stopped working for me after applying the patch.
>>
>> oleg@dld810:~/src/apache.org/jakarta/httpcomponents/http-core$ mvn clean
>> [INFO] Scanning for projects...
>> [INFO]
>> ----------------------------------------------------------------------------
>> [ERROR] FATAL ERROR
>> [INFO]
>> ----------------------------------------------------------------------------
>> [INFO] Error building POM (may not be this project's POM).
>>
>>
>> Project ID: org.apache.jakarta.httpcomponents:http-core
>> POM
>> Location: /home/oleg/src/apache.org/jakarta/httpcomponents/http-core/pom.xml
>> Validation Messages:
>>
>> [0] 'build.testResources.testResource.directory' is missing.
>>
>>
>> Reason: Failed to validate POM
>>
>>
>> [INFO]
>> ----------------------------------------------------------------------------
>> [INFO] Trace
>> org.apache.maven.reactor.MavenExecutionException: Failed to validate POM
>> at
>> org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
>> at
>> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
>> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
>> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
>> 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:585)
>> at
>> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
>> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
>> at
>> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>> Caused by: org.apache.maven.project.InvalidProjectModelException: Failed
>> to validate POM
>> at
>> org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:781)
>> at
>> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:631)
>> at
>> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:303)
>> at
>> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274)
>> at
>> org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
>> at
>> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
>> at
>> org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
>> ... 11 more
>> [INFO]
>> ----------------------------------------------------------------------------
>> [INFO] Total time: < 1 second
>> [INFO] Finished at: Sun Mar 19 13:03:12 CET 2006
>> [INFO] Final Memory: 1M/2M
>>
>> The http-core pom.xml is indeed invalid according to the schema but
>> Maven 2.0.2 does not seem to mind
>>
>
> Probably need to open an issue with Maven?
>
>
Can you reproduce the problem? As far as I can tell this does seem to be
a bug in Maven.
>>> The pom.xml for the httpcomponents also did not validate. The patch
>>> for that is also attached to this email.
>>>
>>>
>> Patch applied
>>
>
> Thanks. But, did not see a commit.
>
>
Are you subscribed to httpclient-commits@jakarta.apache.org?
Oleg
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: [http-core] Wrong pom.xml
Posted by Bindul Bhowmik <bi...@gmail.com>.
On 3/19/06, Oleg Kalnichevski <ol...@apache.org> wrote:
> On Sat, 2006-03-18 at 19:52 -0700, Bindul Bhowmik wrote:
> > Hello,
> >
> > I checked out the http-core component to my workspace, and XML
> > validation tool tells me that the pom.xml does not validate against
> > the maven POM schema.
> > (schemaLocation="http://maven.apache.org/POM/4.0.0
> > http://maven.apache.org/maven-v4_0_0.xsd").
> >
> > I have corrected the pom.xml and am attaching the diff. If it is all
> > right, someone with commit access might want to commit it to the
> > repository.
> >
>
> Hi Bindul
>
> For some reason Maven2 stopped working for me after applying the patch.
>
> oleg@dld810:~/src/apache.org/jakarta/httpcomponents/http-core$ mvn clean
> [INFO] Scanning for projects...
> [INFO]
> ----------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Error building POM (may not be this project's POM).
>
>
> Project ID: org.apache.jakarta.httpcomponents:http-core
> POM
> Location: /home/oleg/src/apache.org/jakarta/httpcomponents/http-core/pom.xml
> Validation Messages:
>
> [0] 'build.testResources.testResource.directory' is missing.
>
>
> Reason: Failed to validate POM
>
>
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Failed to validate POM
> at
> org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> 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:585)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.project.InvalidProjectModelException: Failed
> to validate POM
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:781)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:631)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:303)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274)
> at
> org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
> at
> org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
> ... 11 more
> [INFO]
> ----------------------------------------------------------------------------
> [INFO] Total time: < 1 second
> [INFO] Finished at: Sun Mar 19 13:03:12 CET 2006
> [INFO] Final Memory: 1M/2M
>
> The http-core pom.xml is indeed invalid according to the schema but
> Maven 2.0.2 does not seem to mind
Probably need to open an issue with Maven?
>
> > The pom.xml for the httpcomponents also did not validate. The patch
> > for that is also attached to this email.
> >
>
> Patch applied
Thanks. But, did not see a commit.
>
>
> > I was travelling over the past week, so am lagging behind the emails
> > on the list and am not sure which is the issue tracking tool for http
> > components. Neither Bugzilla nor Jira have HttpComponents listed. Are
> > we still using the HttpClient Bugzilla module for issue tracking?
> >
>
> I am in the process of setting up issue tracking for HttpComponents in
> Jira. It will take probably a few more days (or weeks). Meanwhile just
> use HttpClient project in Bugzilla to report HttpCore related bugs.
>
Sure, thanks,
Bindul
> Cheers
>
> Oleg
>
>
>
> > Regards,
> > Bindul
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
Re: [http-core] Wrong pom.xml
Posted by Oleg Kalnichevski <ol...@apache.org>.
On Sat, 2006-03-18 at 19:52 -0700, Bindul Bhowmik wrote:
> Hello,
>
> I checked out the http-core component to my workspace, and XML
> validation tool tells me that the pom.xml does not validate against
> the maven POM schema.
> (schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd").
>
> I have corrected the pom.xml and am attaching the diff. If it is all
> right, someone with commit access might want to commit it to the
> repository.
>
Hi Bindul
For some reason Maven2 stopped working for me after applying the patch.
oleg@dld810:~/src/apache.org/jakarta/httpcomponents/http-core$ mvn clean
[INFO] Scanning for projects...
[INFO]
----------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
----------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).
Project ID: org.apache.jakarta.httpcomponents:http-core
POM
Location: /home/oleg/src/apache.org/jakarta/httpcomponents/http-core/pom.xml
Validation Messages:
[0] 'build.testResources.testResource.directory' is missing.
Reason: Failed to validate POM
[INFO]
----------------------------------------------------------------------------
[INFO] Trace
org.apache.maven.reactor.MavenExecutionException: Failed to validate POM
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:278)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
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:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.project.InvalidProjectModelException: Failed
to validate POM
at
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:781)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:631)
at
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:303)
at
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:274)
at
org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:515)
at
org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:447)
at
org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:351)
... 11 more
[INFO]
----------------------------------------------------------------------------
[INFO] Total time: < 1 second
[INFO] Finished at: Sun Mar 19 13:03:12 CET 2006
[INFO] Final Memory: 1M/2M
The http-core pom.xml is indeed invalid according to the schema but
Maven 2.0.2 does not seem to mind
> The pom.xml for the httpcomponents also did not validate. The patch
> for that is also attached to this email.
>
Patch applied
> I was travelling over the past week, so am lagging behind the emails
> on the list and am not sure which is the issue tracking tool for http
> components. Neither Bugzilla nor Jira have HttpComponents listed. Are
> we still using the HttpClient Bugzilla module for issue tracking?
>
I am in the process of setting up issue tracking for HttpComponents in
Jira. It will take probably a few more days (or weeks). Meanwhile just
use HttpClient project in Bugzilla to report HttpCore related bugs.
Cheers
Oleg
> Regards,
> Bindul
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: httpclient-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: httpclient-dev-help@jakarta.apache.org