Eugene Kuleshov wrote:
Mark,
Apparently my patch introduced build time dependency on Subclipse
classes which is not acceptable for Mylar. So, we now wonder if you
can take a contribution of a new (optional) Subclipse feature, that
will have dependency on Mylar?
This feature will be responsible for managing Mylar's change sets and
linking Subclipse's own artifacts (change sets, files and history
entries) with tasks in Mylar. Basically there is two classes that need
to be packaged into a separate feature that will have dependencies on
Mylar and Subclipse will get a build time dependency on Mylar. I and
Mik can contribute this code, but we'll need your help to integrate it
with Subclipse's build.
What do you think?
I am fine with it. I did not post to mylar-dev as I am not subscribed
and the last message was bounced back to me.
What does this mean exactly? I assume we would host a second feature on
our update site that contains the code and the user would have to
install that feature?
Mark