[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [ve-dev] Understanding this huge pile of code... ;-)
|
> That explains it. In development, you need to use the source from CVS.
> The source code from the SDK is not sufficient to reconstruct a
> runnable image. That is because it doesn't know how to build the
> remote VM jars. If you pull the code from CVS, there are control files
> that are pulled to allow access to the development images of the
> remote VM jars.
I ran into this too, so one for the "newbie to VE" FAQ for sure
>
> The SDK for VE is only for developers who want to add new plugins that
> extends or references our code. That way they can see the source of
> any classes they use or extend. They should never load the source code
> from the SDK. Any development of our code should be done with the CVS
> source.
Coincidentally, getting started on the VE sources involves a pretty
steep learning curve (even steeper if your Eclipse knowledge is not
already at expert level). Is there, or do you recommend, a high level
architecture document, that could explain the architectural concepts of
the VE plug-in - from a high level of course.
phil
--
Phil Muldoon <pmuldoon@xxxxxxxxxx>
Red Hat, Inc.
