Re: [swordfish-dev] <no subject>

[Renat Zubairov <renat.zubairov@xxxxxxxxx>]

Title: Re: [swordfish-dev] <no subject>

Hello Jürgen,

I would assume we can safely remove the com.sun.xml.bind bundle, just run the build and system tests before commit (Swordfish Tooling system tests are also running on Mac OS). In the tooling the unit and system test coverage is good enough to assume that if your changes will break something you will know about it directly after build and system test.

BTW this is generally a good practice to do a local build before the check-in. The Swordfish Tooling team invested considerable amount of time in the portable and reproducible build which is very easy to run on many different platforms. There is also a wiki page on how to do it:

http://code.google.com/p/swordfish-tooling/wiki/HowToBuild

Please remember by running build locally before the check-in you would minimize the number of broken continuous integration builds.

Renat 


On 01.09.09 09:09, "Jürgen Kindler" <juergen.kindler@xxxxxxxxx> wrote:

> Hi all,
>
> while aligning the bundle versions with tooling I found that some bundles ( javax.xml.bind.swordfish.tooling, javax.xml.stream.swordfish.tooling ) embed jar files that are available as bundles from Orbit.
>
> For now I don’t want to patch those bundles, but I will add a task in the uncommitted task list to remove the embedded jar files. They should finally be done in the same way as Velocity is integrated.
>  
> I also wonder what is the purpose of com.sun.xml.bind.tooling as it refers to Fragment-Host: com.sun.xml.bind which cannot be found during the build and thus results in a warning: 
> [eclipse.buildScript]     Host plug-in com.sun.xml.bind_0.0.0 has not been found.
> As I do not see any traces of this fragment in successfully built versions I would like to know if it can be taken out of the build !?!???
>
> Kind regards
>   Jürgen