No problem, it would be great to have someone else working on subclipse.
Here is how we work for now :
1) you subscribe to mailing lists
2) you get the sources from the good branch (trunk for eclipse 2.1
subclipse-3 for eclipse 3.0
Both depends on svnClientAdapter which is at
3) try to compile it and make it work. Ask questions on mailing list if
4) try to understand how it works. I think junit tests in
"subclipse/test" project can help you.
(there are not many tests yet though). Ask questions on mailing list if
5) post a patch
6) if your patch is good and if you ask, we can then make you a committer
You can modify svnClientAdapter too but make sure that all tests still
pass (the tests for svnClientAdapter need svnant and are at
: they are quite complete and test both svnant and svnClientAdapter)
> Within my division we have elected to start using Subversion as our
> source control system. A large majority of our team will be using
> Eclipse and some of us have already been using our old source control
> system, CVS, from within Eclipse.
> I recently took a brief look at your plugin and while it appears to be
> progressing along quite nicely, there were some areas that you were
> pushing towards to be able to get to your 1.0 release.
> I was wondering if you would appreciate any further development aid?
> While I work for Novell, this would only be a personal commitment.
> If you could provide some current docs on your current branches and
> any 'how-to' docs on setting up a development sandbox, that would
> certainly help me get a foothold into your project and, if nothing
> else is required by you guys, allow me to plod around and able to
> retrieve your latest checkins and build from source creating my own
> Thanks for your time.
Received on Wed Jun 9 07:21:57 2004