Didn't we just graduate with Nebula?
On Thu, Jan 10, 2013 at 11:11 PM, SCHNEKENBURGER Remi 211865 < [email protected]> wrote: > Thanks for your clear and fast answer, Wayne. **** > > We already had the issue with a dependency on XWT (e4 subproject), but XWT > did not already have an official release. If I do understand well, as soon > as there is an official release of the project, present in the simultaneous > release train or not, we can include the project output in our downloads > without problem. **** > > ** ** > > We are also in incubation phase, so our downloads already indicates we are > incubation project.**** > > ** ** > > Cheers,**** > > Rémi**** > > ** ** > > -------------------------------------------------------**** > > ** ** > > Rémi SCHNEKENBURGER**** > > +33 (0)1 69 08 48 48**** > > CEA Saclay Nano-INNOV**** > > Institut CARNOT CEA LIST**** > > ** ** > > [image: Description : PapyrusLogo_SmallFormat]www.eclipse.org/papyrus**** > > ** ** > > *De :* [email protected] [mailto: > [email protected]] *De la part de* Wayne Beaton > *Envoyé :* jeudi 10 janvier 2013 22:59 > *À :* [email protected] > *Objet :* Re: [cross-project-issues-dev] Using a project from Nebula in > the Kepler simultaneous release train**** > > ** ** > > An Eclipse project is free to incorporate the output of other Eclipse > projects in their downloads. You should not be copying their code into your > repository, however. > > Note that you *do not* require CQs (piggybacks or otherwise) for any third > party libraries that your project inherits from another project. That is, > you only need a CQ for third-party code that your project makes direct use > of. Please ask if you need further clarification. > > The only issue is that Nebula is in incubation. If a project's downloads > incorporates components from an incubating project, then the downloads need > to be appropriately labelled using the Incubation Branding guidelines. > > HTH, > > Wayne > > On 01/10/2013 03:56 PM, SCHNEKENBURGER Remi 211865 wrote: **** > > Hi all, **** > > **** > > The Papyrus project is currently interested in using the Nattable[1] > component of the Nebula project. **** > > **** > > I wonder if we can depend on Nattable, while being in the simultaneous > release train Kepler. Nebula has its own release train schedule, and is not > part of the Kepler simultaneous release. It already has an official > release, the version 0.9.0. If it is possible to use it, do we have to > create a new CQ, as for Orbit dependencies, or can we use it as-is, without > any extra action to perform? **** > > **** > > Cheers, > > **** > > Rémi **** > > **** > > **** > > **** > > [1] http://www.eclipse.org/nattable/ **** > > **** > > ------------------------------------------------------- **** > > **** > > Rémi SCHNEKENBURGER **** > > +33 (0)1 69 08 48 48 **** > > CEA Saclay Nano-INNOV **** > > Institut CARNOT CEA LIST **** > > **** > > [image: Description : PapyrusLogo_SmallFormat]www.eclipse.org/papyrus **** > > **** > > ** ** > > ** ** > > _______________________________________________**** > > cross-project-issues-dev mailing list**** > > [email protected]**** > > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev**** > > ** ** > > -- > Wayne Beaton > The Eclipse Foundation > Twitter: @waynebeaton > Explore Eclipse Projects <http://www.eclipse.org/projects> > [image: EclipseCon 2013] <http://www.eclipsecon.org/2013>**** > > _______________________________________________ > cross-project-issues-dev mailing list > [email protected] > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev > >
<<image002.png>>
<<image001.png>>
_______________________________________________ cross-project-issues-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
