Re: [Exist-development] Proposal - Project Migration

[Adam R. <ad...@ex...>]

>> I propose that after 2.0 release -
>>
>> 1) I upgrade our SourceForge project to the latest software platform
>> version on SourceForge. This gives us some shiny new features and
>> options but will change the URL or our source repos.
>
>
> Oh? missed this news, do  you have an URL regarding?

I think you can only see this if you are a project admin, see the
attached screenshot.

>> 2) We migrate from Subversion to Git (still on SourceForge), there is
>> a tool for doing this -
>> git://github.com/jcoglan/svn2git.git
>
>
> Looks like the way to go (is HTTP supported on sf.net?), but...... to limit
> the overall size of the github repo (stored locally), we probably must split
> [if possible] the database from the applications like tamboti? Or am I wrong
> here?

Yes. There are many things in trunk that should not be there. eXide,
Tamboti, examples, webapps, docs, etc. These all need to become
modules. Ideally some of these would have their own git repo's under
the eXist project. However, SF dont yet support multiple repo's by the
looks of it. GitHub do support multiple repo's, but I think we have
too much invested in SF, e.g. mailing lists, bug tracker etc.


>> 3) I shift the project layout of trunk to follow a standard project
>> layout and update the Ant build to work with this.
>> This will make our planned move to Maven much easier and allow me to
>> carry on that work.
>
> good idea, I volunteer to help you here (talk offline).

Great :-)

> I have some additional ideas, which can be implemented easily, making the
> migration to maven more easy......

Okay sounds good.

Also, a good Maven layout to study is probably that of the Hibernate
project https://repository.jboss.org/nexus/content/groups/public/org/hibernate/

I think the Spring project also follow a similar layout.


-- 
Adam Retter

eXist Developer
{ United Kingdom }
ad...@ex...
irc://irc.freenode.net/existdb