Mark Phippard wrote:
>> 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.
CC'ing there.
> 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?
That is pretty much it. User can choose to install that feature if
he'll have Mylar plugins (or install it with the mylar plugins). We can
also do some cross linking in update sites on both ends. See some update
manager screenshot at
http://www.polarion.org/index.php?page=mylar&project=subversive
So, how do we approach this? Are you ok with taking a patch or a
plugin tarball and have some Mylar plugins checked out into your own
workspace?
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Tue Nov 28 19:25:19 2006