That won't fix the problem. The top down mvn eclipse:eclipse will add tuscany-base-runtime as a PROJECT dependency to many itest projects. We see errors all over the place.
I suggest that we move back to base-runtime-pom as the maven dependency. Raymond Feng Sent from my iPhone On Dec 8, 2010, at 12:33 AM, ant elder <[email protected]> wrote: > > > On Wed, Dec 8, 2010 at 12:15 AM, Luciano Resende <[email protected]> wrote: > On Tue, Dec 7, 2010 at 11:33 AM, Luciano Resende <[email protected]> wrote: > > On Tue, Dec 7, 2010 at 1:41 AM, ant elder <[email protected]> wrote: > >> It turns out that there are two in the distribution/aggregations folder, > >> base-runtime-nodep is the really old one from the old shades folder and it > >> could be deleted now, and theres base-runtime-aggregation which is like the > >> base-runtime plus it also includes all its dependencies. > >> > >> I think which should consider if we really need any of those > >> distribution\aggregations ones now after all the other changes we've done. > >> The base + extension approach that we have now along with the which-jars, > >> manifest and Ant build xml all work well enough so i'm not sure we need to > >> keep the old aggregations. One aggregation we might want later is once we > >> get the distributed domain going again an aggregate jar that you can use to > >> get a working SCA client. Thats probably base + sca binding impl + all > >> their > >> dependencies. > >> > > > > I think shaded jars should be separate from modules, to avoid confusion. > > > > Also, if you load the projects in the Eclipse PDE, nothing works > anymore with the following error on every single project. > > A cycle was detected in the build path of project > 'tuscany-assembly-xml' tuscany-assembly-xml Build path Build > Path > Problem > > > > If you don't want to use the base-runtime then just don't load it into PDE > and everything should all work fine. > > ...ant > >
