[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mylyn-builds-dev] Question about subclassing BuildPlan
|
Simply extending classes won't work since the EMF generated factories etc. would always create instances of the base classes. In theory you could extend the model (builds.ecore) but it is not designed to be directly extensible at the moment. We could consider adding support for that but this would require a number of changes to the persistence mechanism, e.g. to make it robust if extended packages are not available.
Can you file a bug and describe what you need? We should be able to add a key-value map as an interim solution to store the required properties.
Steffen
On Mon, Aug 22, 2011 at 3:52 PM, Kiu Leung
<kleung@xxxxxxxxxx> wrote:
Hi all,
I am trying to write connector for Red Hat's in-house build system called koji.
I noticed that Mylyn Builds' Build and BuildPlan are pretty solid, but there is
a minor problem for me to make the resubmission of a task (corresponds to the run
build function) - as I am mapping both koji builds and koji tasks to Build, I have
difficulty to map those two IDs to the Build object. To solve that, I wonder if I can
subclass Build with an extra field to store the actual koji package object,
implement Cloneable to provide clone() for every koji classes and have my customer version
of createWorkingCopy() for the BuildServerBehavior subclass of the koji connector?
You kind advice is appreciated, thank you!
Yours sincerely,
Ken Leung
_______________________________________________
mylyn-builds-dev mailing list
mylyn-builds-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/mylyn-builds-dev
--
Steffen Pingel
Committer,
http://eclipse.org/mylynSenior Developer,
http://tasktop.com
