Artifact Content
Not logged in

Artifact 95d85164f82e259da5d1ba542378c0d03efe3856:

Wiki page [fosclipse-core] by jan.nijtmans 2012-11-13 14:22:25.
D 2012-11-13T14:22:25.459
L fosclipse-core
P 95199050b7d883534812a0fe20137cef26ead56b
U jan.nijtmans
W 1976

<p>This project is meant to be become the "official" Fossil
plugin for Eclipse. It depends on many people cooperating,
so please drop me a [mailto:nijtmans at users dot sf dot net|mail] if you are interested to participate
in any way: designing, coding, documenting, testing, whatever....</p>

<p>At this moment, the Fosclipse plugin is guaranteed not to work.
So only clone this repository when you know what you are doing.
(As soon as things start to get working, this WIKI page will be
modified to say so)</p>


<p>The first design decision is: "Take all design rules from Subclipse,
except when there is a good reason to do otherwise". The reason for
this is: Subclipse is one of the best scm plugins available. Its project
lead (Mark Phippard) clearly knows what he is doing. The Fossil model
in autosync mode looks a lot like the Subversion model.<p>

<p>Whenever deviating from Subclipse's design decision, the modified
design rule and the reason must always be documented on this WIKI.<p>

<p>There will be at least 5 Fosclipse plugins, 3 of which will be
interesting for the public, 2 for developers only. In Eclipse, each
project is checked out separately, so we need a different Fossil
repository for each of those:
   <ul>[|core]: Core functionality (This repository)</ul>
   <ul>[|feature]: Used in plugin-generation</ul>
   <ul>[|tests]: (Unit-)tests</ul>
   <ul>[|ui]: The UI part of the plugin</ul>
   <ul>[|update-site]: Starts to be interesting when things are starting to get working</ul>

<p>To be continued...</p>
Z b77a94f6746908b16103a0f198d82cc7