Hi,
I have thought about a separate module to trigger the on-demand
installation. If we build the Tuscany source, it will help. But if an
application try to use the implementation.xquery, the build will fail
because the ant script won't be transitively invoked.
From the IP perspective, do you see any issues to host 3rd party jars in our
svn if the licenses are compatible with Apache and the owners are OK for the
hosting?
Thanks,
Raymond
----- Original Message -----
From: "ant elder" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, December 07, 2007 3:37 AM
Subject: Re: Missing Saxon 9.0.0.2 dependency
Ok running "ant -f build-saxon.xml" gets around it for me thanks. How
about
having a separate module just for the Ant install and have
databinding-saxon
depend on that module? That should work around the same module problem and
avoids us having to distribute jars from our svn.
...ant
On Dec 7, 2007 12:16 AM, Raymond Feng <[EMAIL PROTECTED]> wrote:
Hi,
I think now I understand what's going on. Even though we have the pom.xml
configured to run an ant script to download the saxon 9.0.0.2 and install
it
to the local maven repo, the build fails before the ant plugin is
triggered
because we have explicit dependencies on saxon declared on the same
module.
I think we need to put the jars into a remote repo. The short-term
workaround is to run the build-saxon.xml under databinding-saxon using
"ant -f build-saxon.xml".
Thanks,
Raymond
----- Original Message -----
From: "Raymond Feng" <[EMAIL PROTECTED]>
To: <[email protected]>; <[EMAIL PROTECTED]>
Sent: Thursday, December 06, 2007 8:38 AM
Subject: Re: Missing Saxon 9.0.0.2 dependency
> Hi,
>
> At this moment, I use an ant script to download the zip and install the
> jars to the local maven repo. It's integrated with the pom.xml so it
> should work with mvn in the source build. I realized that the binary
build
> will fail after that.
>
> I'm starting to improve the implementation.xquery based on the new APIs
> provided in saxon 9.0.0.2.
>
> There was a discussion with saxon team before. They are OK to get the
jars
> published into maven but they don't want to take the responsiblity. Can
we
> publish the jars (which are not in a public maven repo yet) in our svn
> repo as a maven repo as Geronimo is doing? See
> https://svn.apache.org/repos/asf/geronimo/server/tags/2.0.2/repository/.
>
> Thanks,
> Raymond
>
> ----- Original Message -----
> From: "ant elder" <[EMAIL PROTECTED]>
> To: "tuscany-dev" <[email protected]>
> Sent: Thursday, December 06, 2007 3:07 AM
> Subject: Missing Saxon 9.0.0.2 dependency
>
>
>> We've now a dependency on Saxon 9.0.0.2 but thats not in any Maven
>> repository we use so the build fails. Must we use Saxon 9.0.0.2 or
does
>> anyone know of a public repository we could get it from?
>>
>> ...ant
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
