[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [dsdp-ercp-dev] Re: New structure proposal for eRCP CVS
|
I was reluctant about the ecore name as well for the same reason but I
thought core was too generic. What about ercp-ecore ? I would not vote
for equinox as well since ercp-ecore is more than equinox and eRCP stack
can always run on different OSGi engines.
Taking the equinox directly is not such a bad idea. We can fetch the
binaries in the build scripts directly from equinox downloads.
http://download.eclipse.org/eclipse/equinox/drops/R-3.3.1-200709211145/index.php
--
Gorkem
Remy Chi Jian Suen wrote:
I don't really like the name of 'ecore' as that's a name that's used
in EMF. I would propose something more straightforward like "core" or
"equinox".
Isn't the Equinox code actually unmodified? Is there a reason why that
code is duplicated in eRCP's CVS repository?
Regards,
Rem
On 10/12/07, Gorkem Ercan <gercan@xxxxxxx> wrote:
For some reason my diagram for the structure did not go thorough. I am
resending as an image now.
Gorkem Ercan wrote:
I think our CVS directory structure started to be very crowded, and
soon Nokia will be putting in the S60 implementation, it will get even
more crowded and will be harder to find anything for newcomers.
I would like to propose the below structure for our CVS. On the top
level, our components and the examples, and divide eSWT further to
specific implementations. Please comment on this new structure.
--
Gorkem
_______________________________________________
dsdp-ercp-dev mailing list
dsdp-ercp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-ercp-dev
_______________________________________________
dsdp-ercp-dev mailing list
dsdp-ercp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/dsdp-ercp-dev
