[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [stp-dev] takin' a look at the core model code
- From: Naci Dai <naci.dai@xxxxxxxxxxxxx>
- Date: Wed, 05 Apr 2006 07:40:45 +0300
- Delivered-to: firstname.lastname@example.org
- User-agent: Thunderbird 1.5 (Windows/20051201)
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 (org.eclipse.stp.sca.**??)
Suggest org.eclipse.stp.core as a base, then subpackage from there
com.ibm.ccl.soa.core --> org.eclipse.stp.core.assembly
com.ibm.ccl.soa.core.sca --> org.eclipse.stp.core.assembly.model
com.ibm.ccl.soa.internal.core --> org.eclipse.stp.core.assembly.internal
Is the 'internal' in the right place here? Put '.tests' on the end
for the tests of course.
-We also added two top level assembly projects to drive the builds
and represent the subproject (we called it org.eclipse.stp.sca and
org.eclipse.stp.sca.sdk 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