« Return to Thread: httpbuilder + maven problem?
Re: httpbuilder + maven problem?
by Tom Nichols
::
Rate this Message:
FYI you can put the Xerces exclusion directly under the http-builder
entry, even though Xerces is not a direct dependency, i.e.
<dependency>
<groupId>org.codehaus.groovy.modules.http-builder</groupId>
<artifactId>http-builder</artifactId>
<version>0.5.0-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>xerces</groupId>
<artifactId>xercesImpl</artifactId>
</exclusion>
</exclusions>
</dependency>
In the next release, Xerces will be listed as a direct, 'provided'
dependency to http-builder. Since http-builder requires Java5, it's
probably safe to assume Xerces is already on the classpath. Most
app/servlet containers already provide a version of Xerces as well.
If not, users can opt to include it manually. But that would be the
exceptional case.
-Tom
On Wed, Jun 17, 2009 at 8:01 PM, Pete McKinstry<pete.mckinstry@...> wrote:
> So I figured this out. It died due to Xerces library version
> incompatibilities. I figured it out by excluding dependencies required by
> the httpbuilder library & then re-adding them 1 by 1. The culprit was the
> nekohtml jar which requires xerces & something about the version it pulled
> caused the test phase to crash. I added this section to my pom.xml & it
> works fine now.
>
> <dependency>
> <groupId>org.codehaus.groovy.modules.http-builder</groupId>
> <artifactId>http-builder</artifactId>
> <version>0.5.0-SNAPSHOT</version>
> <exclusions>
> <exclusion>
> <groupId>net.sourceforge.nekohtml</groupId>
> <artifactId>nekohtml</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
>
> <dependency>
> <groupId>net.sourceforge.nekohtml</groupId>
> <artifactId>nekohtml</artifactId>
> <version>1.9.9</version>
> <exclusions>
> <exclusion>
> <groupId>xerces</groupId>
> <artifactId>xercesImpl</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
>
> -pgm
>
>
> On Thu, Jun 11, 2009 at 1:46 PM, Pete McKinstry <pete.mckinstry@...>
> wrote:
>>
>> Tom,
>> Yes, I have other dependencies in the pom that don't cause a problem.
>> maven -X package does the same thing. Exits w/ no msg at all. Same output as
>> w/ maven -e -->
>> [DEBUG] Configuring mojo
>> 'org.grails:grails-maven-plugin:1.1-SNAPSHOT:maven-test' -->
>>
>> [DEBUG] (f) basedir = /home/petemc01/projects/hydra/portal
>> [DEBUG] (f) localRepository = [local] ->
>> file:///home/petemc01/.m2/repository
>>
>> [DEBUG] (f) nonInteractive = false
>> [DEBUG] (f) project = MavenProject:
>> com.nintendo.hydra:gportal:0.1-SNAPSHOT @
>> /home/petemc01/projects/hydra/portal/pom.xml
>> [DEBUG] (f) remoteRepositories = [[central] ->
>> http://myserver:8081/artifactory/repo, [snapshots] ->
>> http://myserver:8081/artifactory/repo, [jasig-m2] ->
>> http://developer.jasig.org/repo/content/repositories/m2,
>> [maven2-repository.dev.java.net] -> http://download.java.net/maven/2/,
>> [Codehaus Snapshots] -> http://snapshots.repository.codehaus.org]
>> [DEBUG] -- end configuration --
>> [INFO] [grails:maven-test {execution: default}]
>> [INFO] Using Grails 1.1.1
>> Running pre-compiled script
>> Authentication for svn repo at internalRepository discovery is required.
>> ...
>> [input] skipping input as property
>> user.svn.username.discovery.internalRepository has already been set.
>> [input] skipping input as property
>> user.svn.password.discovery.internalRepository has already been set.
>> Authentication for svn repo at internalRepository distribution is
>> required. ...
>> [input] skipping input as property
>> user.svn.username.distribution.internalRepository has already been set.
>> [input] skipping input as property
>> user.svn.password.distribution.internalRepository has already been set.
>> Configured HTTP proxy: proxy.xxxx.com:8080(petemc01)
>> [mkdir] Created dir:
>> /home/petemc01/projects/hydra/portal/test/reports/html
>> [mkdir] Created dir:
>> /home/petemc01/projects/hydra/portal/test/reports/plain
>> Starting unit tests ...
>> Running tests of type 'unit'
>> -------------------------------------------------------
>> Running 12 unit tests...
>> Running test MenuFiltersTests...
>> tiberius:~/projects/hydra/portal>
>>
>>
>> Weird, huh?
>> -pgm
>> Pete McKinstry
>>
>>
>> On Thu, Jun 11, 2009 at 10:09 AM, Tom Nichols <tmnichols@...> wrote:
>>>
>>> Can't imagine why HTTPBuilder in particular would be a problem... But
>>> I'm not familiar with the maven-grails plugin either. I'm assuming
>>> you have other dependencies in your POM as well that work fine. Try
>>> adding the -X flag to maven, you'll get more information on where
>>> exactly maven is dying.
>>>
>>>
>>> On Thu, Jun 11, 2009 at 12:49 PM, Pete
>>> McKinstry<pete.mckinstry@...> wrote:
>>> > I'm having trouble w/ the maven-grails plugin in combination w/ the
>>> > httpbuilder library. When I include the httpbuilder in my pom.xml,
>>> > maven
>>> > crashes right in the middle of the test phase. It compiles fine & then
>>> > fails
>>> > right @ the beginning of the test phase. No error msg, It just quits.
>>> > Like
>>> > this: (output using mvn -e package)
>>> > Starting unit tests ...
>>> > Running tests of type 'unit'
>>> > -------------------------------------------------------
>>> > Running 12 unit tests...
>>> > Running test MenuFiltersTests...
>>> > $
>>> > If I pass -Dmaven.test.skip=true then it completes fine (including
>>> > packaging
>>> > the war). I've tried using an older/released version of the httpbuilder
>>> > (i
>>> > was using 0.5.0-SNAPSHOT) w/o any change. Of course this all works fine
>>> > using grails directly. (grails war, etc...)
>>> > Any suggestions?
>>> > -pgm
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>> http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
entry, even though Xerces is not a direct dependency, i.e.
<dependency>
<groupId>org.codehaus.groovy.modules.http-builder</groupId>
<artifactId>http-builder</artifactId>
<version>0.5.0-SNAPSHOT</version>
<exclusions>
<exclusion>
<groupId>xerces</groupId>
<artifactId>xercesImpl</artifactId>
</exclusion>
</exclusions>
</dependency>
In the next release, Xerces will be listed as a direct, 'provided'
dependency to http-builder. Since http-builder requires Java5, it's
probably safe to assume Xerces is already on the classpath. Most
app/servlet containers already provide a version of Xerces as well.
If not, users can opt to include it manually. But that would be the
exceptional case.
-Tom
On Wed, Jun 17, 2009 at 8:01 PM, Pete McKinstry<pete.mckinstry@...> wrote:
> So I figured this out. It died due to Xerces library version
> incompatibilities. I figured it out by excluding dependencies required by
> the httpbuilder library & then re-adding them 1 by 1. The culprit was the
> nekohtml jar which requires xerces & something about the version it pulled
> caused the test phase to crash. I added this section to my pom.xml & it
> works fine now.
>
> <dependency>
> <groupId>org.codehaus.groovy.modules.http-builder</groupId>
> <artifactId>http-builder</artifactId>
> <version>0.5.0-SNAPSHOT</version>
> <exclusions>
> <exclusion>
> <groupId>net.sourceforge.nekohtml</groupId>
> <artifactId>nekohtml</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
>
> <dependency>
> <groupId>net.sourceforge.nekohtml</groupId>
> <artifactId>nekohtml</artifactId>
> <version>1.9.9</version>
> <exclusions>
> <exclusion>
> <groupId>xerces</groupId>
> <artifactId>xercesImpl</artifactId>
> </exclusion>
> </exclusions>
> </dependency>
>
> -pgm
>
>
> On Thu, Jun 11, 2009 at 1:46 PM, Pete McKinstry <pete.mckinstry@...>
> wrote:
>>
>> Tom,
>> Yes, I have other dependencies in the pom that don't cause a problem.
>> maven -X package does the same thing. Exits w/ no msg at all. Same output as
>> w/ maven -e -->
>> [DEBUG] Configuring mojo
>> 'org.grails:grails-maven-plugin:1.1-SNAPSHOT:maven-test' -->
>>
>> [DEBUG] (f) basedir = /home/petemc01/projects/hydra/portal
>> [DEBUG] (f) localRepository = [local] ->
>> file:///home/petemc01/.m2/repository
>>
>> [DEBUG] (f) nonInteractive = false
>> [DEBUG] (f) project = MavenProject:
>> com.nintendo.hydra:gportal:0.1-SNAPSHOT @
>> /home/petemc01/projects/hydra/portal/pom.xml
>> [DEBUG] (f) remoteRepositories = [[central] ->
>> http://myserver:8081/artifactory/repo, [snapshots] ->
>> http://myserver:8081/artifactory/repo, [jasig-m2] ->
>> http://developer.jasig.org/repo/content/repositories/m2,
>> [maven2-repository.dev.java.net] -> http://download.java.net/maven/2/,
>> [Codehaus Snapshots] -> http://snapshots.repository.codehaus.org]
>> [DEBUG] -- end configuration --
>> [INFO] [grails:maven-test {execution: default}]
>> [INFO] Using Grails 1.1.1
>> Running pre-compiled script
>> Authentication for svn repo at internalRepository discovery is required.
>> ...
>> [input] skipping input as property
>> user.svn.username.discovery.internalRepository has already been set.
>> [input] skipping input as property
>> user.svn.password.discovery.internalRepository has already been set.
>> Authentication for svn repo at internalRepository distribution is
>> required. ...
>> [input] skipping input as property
>> user.svn.username.distribution.internalRepository has already been set.
>> [input] skipping input as property
>> user.svn.password.distribution.internalRepository has already been set.
>> Configured HTTP proxy: proxy.xxxx.com:8080(petemc01)
>> [mkdir] Created dir:
>> /home/petemc01/projects/hydra/portal/test/reports/html
>> [mkdir] Created dir:
>> /home/petemc01/projects/hydra/portal/test/reports/plain
>> Starting unit tests ...
>> Running tests of type 'unit'
>> -------------------------------------------------------
>> Running 12 unit tests...
>> Running test MenuFiltersTests...
>> tiberius:~/projects/hydra/portal>
>>
>>
>> Weird, huh?
>> -pgm
>> Pete McKinstry
>>
>>
>> On Thu, Jun 11, 2009 at 10:09 AM, Tom Nichols <tmnichols@...> wrote:
>>>
>>> Can't imagine why HTTPBuilder in particular would be a problem... But
>>> I'm not familiar with the maven-grails plugin either. I'm assuming
>>> you have other dependencies in your POM as well that work fine. Try
>>> adding the -X flag to maven, you'll get more information on where
>>> exactly maven is dying.
>>>
>>>
>>> On Thu, Jun 11, 2009 at 12:49 PM, Pete
>>> McKinstry<pete.mckinstry@...> wrote:
>>> > I'm having trouble w/ the maven-grails plugin in combination w/ the
>>> > httpbuilder library. When I include the httpbuilder in my pom.xml,
>>> > maven
>>> > crashes right in the middle of the test phase. It compiles fine & then
>>> > fails
>>> > right @ the beginning of the test phase. No error msg, It just quits.
>>> > Like
>>> > this: (output using mvn -e package)
>>> > Starting unit tests ...
>>> > Running tests of type 'unit'
>>> > -------------------------------------------------------
>>> > Running 12 unit tests...
>>> > Running test MenuFiltersTests...
>>> > $
>>> > If I pass -Dmaven.test.skip=true then it completes fine (including
>>> > packaging
>>> > the war). I've tried using an older/released version of the httpbuilder
>>> > (i
>>> > was using 0.5.0-SNAPSHOT) w/o any change. Of course this all works fine
>>> > using grails directly. (grails war, etc...)
>>> > Any suggestions?
>>> > -pgm
>>> >
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe from this list, please visit:
>>>
>>> http://xircles.codehaus.org/manage_email
>>>
>>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
« Return to Thread: httpbuilder + maven problem?
| Free embeddable forum powered by Nabble | Forum Help |
