Current State of CEDET in Emacs tree and standalone

--===============4544833332269432373==
Content-Type: multipart/alternative; boundary="000000000000bd1c7b0570a4d627"

--000000000000bd1c7b0570a4d627
Content-Type: text/plain; charset="UTF-8"

Hi all!

In a quest to add some improvements to CEDET/Semantic I came across the
fact of the splintered codebases people are potentially working on.

We have the CEDET project on SourceForge with changes going beyond the
initial import into emacs.
And then there is the version shipped with Emacs.

When comparing the code basis one of the most immediate things that struck
me, was the availability of tests and that there was even rudimentary unit
testing employed, This is not the case for the code in Emacs tree.

Are there efforts to import the code from Sourceforge anew into the emacs
tree or is it intended to remain there as it pertains to features not
intended to be shipped with Emacs?

If possible I'd like to use the existing unit-test infrastructure in the
emacs tree to add validation to the changes that I'm making and since as I
understand it, there's otherwise existing development effort still going
into the code shipped with emacs I'd prefer  to not double my efforts and
have to make it shippable/maintainable in 2 places.

Any and all explanations of the current situation would be very welcome.

Kind regards,

Andreas Marschke.

--000000000000bd1c7b0570a4d627
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi all!<div><br></div><div>In a quest to add some improvem=
ents to CEDET/Semantic I came across the fact of the splintered codebases p=
eople are potentially working on.</div><div><br></div><div>We have the CEDE=
T project on SourceForge with changes going beyond the initial import into =
emacs.=C2=A0</div><div>And then there is the version shipped with Emacs.</d=
iv><div><br></div><div>When comparing the code basis one of the most immedi=
ate things that struck me, was the availability of tests and that there was=
 even rudimentary unit testing employed, This is not the case for the code =
in Emacs tree.</div><div><br></div><div>Are there efforts to import the cod=
e from Sourceforge anew into the emacs tree or is it intended to remain the=
re as it pertains to features not intended to be shipped with Emacs?</div><=
div><br></div><div>If possible I&#39;d like to use the existing unit-test i=
nfrastructure in the emacs tree to add validation to the changes that I&#39=
;m making and since as I understand it, there&#39;s otherwise existing deve=
lopment effort still going into the code shipped with emacs I&#39;d prefer=
=C2=A0 to not double my efforts and have to make it shippable/maintainable =
in 2 places.</div><div><br></div><div>Any and all explanations of the curre=
nt situation would be very welcome.</div><div><br></div><div>Kind regards,<=
/div><div><br></div><div>Andreas Marschke.=C2=A0=C2=A0</div></div>

--000000000000bd1c7b0570a4d627--


--===============4544833332269432373==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
--===============4544833332269432373==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
cedet-semantic mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cedet-semantic

--===============4544833332269432373==--