Re: 3rd party dependencies

[Rajini Sivaram <ra...@googlemail.com>]

On 8/29/08, Raymond Feng <en...@gmail.com> wrote:

> Hi, Rajini.
>
> Can you point out (in JIRAs) what OSGi manifest headers are not good from
> SDO/DAS jars? We should fix them.


SDO manifests use Require-Bundle to pull in EMF and other dependencies,
which in turn introduce a dependency on the Eclipse/Equinox runtime. And it
does not do versioning. At this point, we can replace Require-Bundle with
Import-Package, I would prefer to wait until we have a proper versioning
story in SCA before fixing the SDO manifests. The versioning restrictions
that we impose on SCA (very narrow import version ranges) might not be
suitable for SDO where users may already have dependencies on different
versions of EMF etc.



> Thanks,
> Raymond
>
> From: Rajini Sivaram
> Sent: Friday, August 29, 2008 1:18 AM
> To: user@tuscany.apache.org
> Subject: Re: 3rd party dependencies
>
>
>
>
>
> On 8/28/08, Raymond Feng <en...@gmail.com> wrote:
> Did you have a successful build with tuscany-versioned? In my case, it
> failed in the middle when it processes jruby-complete-1.0.jar (which has an
> invalid pom.xml). I had to fix the tuscany-maven-bundle plugin to ignore the
> error to get a successful build. After that, I only see the ones with
> org.apache.tuscany.sca.3rdparty prefixes.
>
> There is a problem with jruby-complete and maven-2.0.9. You should be able
> to build with any of the older versions of maven. I think the issue has been
> resolved in maven, but there hasn't been a release since.
>
>
> For the sdo/das jars, I can fix the plugin to recognize these artifacts as
> tuscany bundles.
>
> sdo and das jars are deliberately built with the 3rdparty prefix. I had
> added the 3rd party prefix to denote jars which have been modified by the
> Tuscany build, to distinguish them from jars which are downloaded off maven
> repositories. Since the manifest files in sdo and das have to be modified by
> the tuscany-sca build, these have also been built with the 3rd party prefix.
> I think we should retain the prefix until we can get sdo and das to build
> with manifests that can be reused for SCA.
>
>
>
>
> Thanks,
> Raymond
> --------------------------------------------------
> From: <Da...@empolis.com>
> Sent: Thursday, August 28, 2008 6:48 AM
> To: <tu...@ws.apache.org>
> Subject: 3rd party dependencies
>
>
>
> Hi all,
>
> is there somewhere a list with all 3rd party dependencies, their version
> and license model and what they are used for in Tuscany ?
> This would be really helpful for eclipse legal process. It could also
> help us to solve conflicts in OSGi environment when integrating Tuscany
> to our software (e.g when having requirements for the same lib in
> different versions). It could also help figure out what Tuscany jars are
> needed for certain use cases and which 3rd party libs are required
> therefore (for minimizing the list of dependencies).
> If there is no such list, would it be possible to provide on in the wiki
> ?
>
>
>
> Another Question: If I build OSGi bundles in sca\itest\osgi-tuscany, all
> 3rd party bundles are created twice in
> sca\itest\osgi-tuscany\tuscany-versioned\target\classes. On has the
> original name, the other uses the prefix
> "org.apache.tuscany.sca.3rdparty.". I compared the ones created for
> xerces and could not find any differences (besides different format in
> Manifest.mf).
>
> The number of jars is slightly different, as the ones with prefix also
> contains these, which do not seem to be real 3rd party libs
>
> org.apache.tuscany.das.tuscany-das-rdb_1.0.0.SNAPSHOT.jar
> org.apache.tuscany.sdo.lib_1.1.1.jar
> org.apache.tuscany.sdo.spec_1.1.1.jar
> org.apache.tuscany.sdo.tuscany-sdo-impl_1.1.1.jar
> org.apache.tuscany.sdo.tuscany-sdo-tools_1.1.0.incubating.jar
>
> So why are the other bundles available twice and why are some Tuscany
> libs handled as 3rd party ?
>
>
> Bye,
> Daniel
>
>
>
>
>
>
> --
> Thank you...
>
> Regards,
>
> Rajini
>



-- 
Thank you...

Regards,

Rajini