Re: Maven changes to EXPath Packaging and EXPath HTTP Client for Java

Hi,

The Saxon version is declared in expath-parent/pom.xml, and is 9.4.0.7.

Since it is inherited, it has not to be declared in pkg-saxon/pom.xml.

Claudius


On Sat, Oct 26, 2013 at 7:42 PM, Michael Sokolov <
msokolov@safaribooksonline.com> wrote:

> Hi Florent, I did some perfunctory checking, nothing in depth.  I was able
> to check  out and build the maven branch.  One thing that I found confusing
> is that the dependency for Saxon does not declare a specific version.  In
> pkg-saxon/pom.xml, we have:
>
>        <dependency>
>             <groupId>net.sf.saxon</**groupId>
>             <artifactId>Saxon-HE</**artifactId>
>         </dependency>
>
> but no explicit <version> tag
>
>   Usually (I think?) this causes Maven to grab the latest released
> version, which is not really good practice since the dependency can change
> out from underneath you and break your project. However looking more
> closely I see it is actually using Saxon HE 9.4.0.8 (I think).  I'm not
> sure why that is (I would have expected a Saxon 9.5 version).  Probably not
> an issue: just something I don't understand.  But I would like to use Saxon
> 9.5, so it would be nice to see what changes would be needed for that, but
> I'm not sure how to update the dependency.
>
> -Mike
>
> On 10/23/13 3:23 AM, Florent Georges wrote:
>
>>    Hi,
>>
>>    Thanks to Adam, we have now some support for Maven in the EXPath
>> Packaging and HTTP Client implementations for Java.  This also adds
>> some streaming facility to the HTTP Client:
>>
>>      https://github.com/fgeorges/**expath-pkg-java/<https://github.com/fgeorges/expath-pkg-java/>
>>      https://github.com/fgeorges/**expath-http-client-java/<https://github.com/fgeorges/expath-http-client-java/>
>>
>>    Unfortunately, those changes were so huge and about so different
>> things (moving to Maven, adding streaming, changing lots of files
>> without any functional changes except formatting the code differently,
>> etc.), that it was very hard to merge them and resolve the conflicts.
>> So I pushed them in their own branch (resp. "maven" and "maven-and-
>> streaming"), can I then ask anyone involved in those projects to test
>> and review them before merging to master?
>>
>>    The Maven part is also not documented.  Can anyone have a look at it
>> and suggets changes to the following files (that I have created, but
>> as I don't know anything about Maven, I can't fill the blanks myself):
>>
>>      https://github.com/fgeorges/**expath-pkg-java/blob/maven/**
>> doc/development.md<https://github.com/fgeorges/expath-pkg-java/blob/maven/doc/development.md>
>>      https://github.com/fgeorges/**expath-http-client-java/blob/**
>> maven-and-streaming/doc/**development.md<https://github.com/fgeorges/expath-http-client-java/blob/maven-and-streaming/doc/development.md>
>>
>>    Regards,
>>
>>
>
>


-- 
http://kuberam.ro
http://kuberam.ro/art