Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [stp-dev] takin' a look at the core model code

Hi Oisin,

sdk stands for software development kit. This is a packaging feature which includes the sources. SDK are useful for adopters and developers so that they have the sources readily available. So we will have a runtime zip (all binaries) and an sdk zip (runtime+sources).

I will also suggest that we drop "assembly" in the feature chain as the top level features of each project is already doing that.

tests and internal are fine.

- Builds are ready and tested we are waiting for the current code to be renamed and promoted to CVS to start builds.

-Have you decided about the name conversion for the contibuted plugins? i.e (**??)

Suggest org.eclipse.stp.core as a base, then subpackage from there
to -->  org.eclipse.stp.core.assembly -->   org.eclipse.stp.core.assembly.model --> org.eclipse.stp.core.assembly.internal --> org.eclipse.stp.core.assembly.internal.model

Is the 'internal' in the right place here?  Put '.tests' on the end
for the tests of course. --> org.eclipse.stp.core.assembly.infrastructure

-We also added two top level assembly projects to drive the builds and represent the subproject (we called it and for lack of anything else). Any ideas?



what's the sdk indicate here Naci?

- Finally test plugin IDs and project names do not match. Minor point but worth fixing during the conversion.

Yup I think so.

stp-dev mailing list

Back to the top