[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-dev] Subclipse headless packaging?

From: Thomas Hallgren <thomas_at_tada.se>
Date: 2007-01-25 17:03:01 CET

Hi Roy,
Yes, that's an option too but as far as I know it will force us to make
our features explicitly appoint a specific version of the subclipse core
bundle. Hence, we must track when you upgrade to a new version and
publish a new feature every time that happens. With very few external
dependencies that is of course a possibility, but as those dependencies
increase, it will be a burden that we really would like to avoid.

Using features and "required" plugins, we can a more lax dependency
requirement policy and document that certain features have prerequisites
on other features from other vendors.

Kind Regards,
Thomas Hallgren

Roy Paterson wrote:
> There are other options - your feature could reference the subclipse
> core plugin using an <archive> tag in the site.xml file.
>
> Roy
>
> Thomas Hallgren wrote:
>> Hi,
>> Buckminster has a headless tool that is capable of configuring itself
>> from remote update sites (it make use of the Eclipse update manager
>> in a headless way). Now I'm facing the following problem:
>>
>> Buckminster has a org.eclipse.buckminster.svn plugin. It is dependent
>> on the org.tigris.subversion.subclipse.core. Particular care has been
>> taken not to introduce any UI dependencies in order to keep
>> everything mean and lean for headless execution. I really appreciate
>> the separation that's been done in subclipse in this respect.
>>
>> We also have an org.eclipse.buckminster.svn.headless.feature. It
>> imports all needed headless eclipse platform plugins and our svn
>> plugin. It also expresses a requirement on the
>> org.tigris.subversion.subclipse.core (i.e. it must be installed prior
>> to installing our headless svn feature). My problem is, using a
>> headless installer, how can I get hold of that? You don't make a
>> headless feature available and I don't get passed the point where the
>> installer informs me that I must install all the UI components before
>> installing your feature.
>>
>> I see two solutions to this problem:
>> 1. We make the subclipse core plugin available at eclipse.org and
>> include it in our feature. I'm not sure we can do that. Would
>> Subclipse allow it? Will Eclipse allow it? Also, doing that would
>> impose the burden of maintining updates for this plugin. A burden
>> that you already must carry.
>> 2. You could publish a new feature that only included the headless
>> parts of subclipse.
>>
>> Needless to say, I think solution #2 would be much better.
>>
>> What do you think?
>>
>> Kind Regards,
>> Thomas Hallgren
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
>> For additional commands, e-mail: dev-help@subclipse.tigris.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: dev-help@subclipse.tigris.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: dev-help@subclipse.tigris.org
Received on Thu Jan 25 17:03:14 2007

This is an archived mail posted to the Subclipse Dev mailing list.