[OT] Version control system

[bryan hunt]

Hi there,

First post. Sorry if I step on anyone's toe's with the following
project related query (more of a developer question, but there doesn't
seem to be an appropriate list).

I've been dabbling with MyBatis/IBatis since about 2003. I mainly
followed the Hibernate/JPA road but find myself in the position of re-
investigating the framework.

I've found that working with Scala is a bit awkward, I want to wrap
all optional parameters in Option[<paramType>]. This causes some
weirdness with TypeMappers as it isn't aware of Scala types... But I
digress..

Anyhow, I notice there is some experimental stuff going on in @
http://www.mybatis.org/scala

My first instinct in this situation, specifically where available
artifacts are all Release Candidates (RC{1..2}), is to clone the
repository and Maven build it on my own machine, then it's trivial to
send patches, fix stuff locally, etc.

But you guys are using Subversion, what gives? This is 2012, the world
and it's dog have been using distributed version systems (Git,
Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
I'm talking Joe the Developer.

Are there any plans to move over to a decent Version Control System?

Best Regards,

Bryan Hunt

[bryan hunt]

On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt <[hidden email]> wrote:

> Anyhow, I notice there is some experimental stuff going on in @
> http://www.mybatis.org/scala
>
> My first instinct in this situation, specifically where available
> artifacts are all Release Candidates (RC{1..2}), is to clone the
> repository and Maven build it on my own machine, then it's trivial to
> send patches, fix stuff locally, etc.
>
> But you guys are using Subversion, what gives? This is 2012, the world
> and it's dog have been using distributed version systems (Git,
> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
> I'm talking Joe the Developer.
>
> Are there any plans to move over to a decent Version Control System?
>
> Best Regards,
>
> Bryan Hunt

Got it building in Eclipse now, file paths must match package names,
will keep updating my version as I fix bugs, feel free to pull in any
changes which are usefull to you.

https://bitbucket.org/sentimental/mybatis-scala-copy/changesets

[Frank Martínez]

Hi Bryan,

I am glad you are interested in the Scala port. I am the main developer.

You can checkout the development version with any svn client.

Tell me if I can help you in any way.

Cheers,

Frank.

On Tue, Feb 28, 2012 at 9:58 AM, Bryan Hunt <[hidden email]> wrote:

> On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt <[hidden email]> wrote:
>> Anyhow, I notice there is some experimental stuff going on in @
>> http://www.mybatis.org/scala
>>
>> My first instinct in this situation, specifically where available
>> artifacts are all Release Candidates (RC{1..2}), is to clone the
>> repository and Maven build it on my own machine, then it's trivial to
>> send patches, fix stuff locally, etc.
>>
>> But you guys are using Subversion, what gives? This is 2012, the world
>> and it's dog have been using distributed version systems (Git,
>> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
>> I'm talking Joe the Developer.
>>
>> Are there any plans to move over to a decent Version Control System?
>>
>> Best Regards,
>>
>> Bryan Hunt
>
> Got it building in Eclipse now, file paths must match package names,
> will keep updating my version as I fix bugs, feel free to pull in any
> changes which are usefull to you.
>
> https://bitbucket.org/sentimental/mybatis-scala-copy/changesets
>

--
Frank D. Martínez M.

[Tim]

Way to answer his question Frank.

Bryan this is a topic that was discussed recently by the dev team.

Basically (and I know this is not a satisfactory answer.. trust me I was pushing for git ;)) the resulting decision was..

If it ain't broke, don't fix it.

For a user of the framework they won't notice.

For a occasional hacker of the framework they are minorly inconvenienced.

For a committer on the system, it makes me extremely annoyed.

To be fair though, I wouldn't have cared if I never used git before.

But having experienced both sides (as well as the occasional mercurial) I sympathize with your OT question.

On Tue, Feb 28, 2012 at 2:34 PM, Frank Martínez <[hidden email]> wrote:

Hi Bryan,

I am glad you are interested in the Scala port. I am the main developer.

You can checkout the development version with any svn client.

Tell me if I can help you in any way.

Cheers,

Frank.

On Tue, Feb 28, 2012 at 9:58 AM, Bryan Hunt <[hidden email]> wrote:
> On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt <[hidden email]> wrote:
>> Anyhow, I notice there is some experimental stuff going on in @
>> http://www.mybatis.org/scala
>>
>> My first instinct in this situation, specifically where available
>> artifacts are all Release Candidates (RC{1..2}), is to clone the
>> repository and Maven build it on my own machine, then it's trivial to
>> send patches, fix stuff locally, etc.
>>
>> But you guys are using Subversion, what gives? This is 2012, the world
>> and it's dog have been using distributed version systems (Git,
>> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
>> I'm talking Joe the Developer.
>>
>> Are there any plans to move over to a decent Version Control System?
>>
>> Best Regards,
>>
>> Bryan Hunt
>
> Got it building in Eclipse now, file paths must match package names,
> will keep updating my version as I fix bugs, feel free to pull in any
> changes which are usefull to you.
>
> https://bitbucket.org/sentimental/mybatis-scala-copy/changesets
>

--
Frank D. Martínez M.

[Eduardo Macarron]

Hi Bryan,

Switching to Git looks like a good idea. That should facilitate
contributions and that is really important.

But, we are using one repository for quite a few projects. Maybe I am
wrong but I suppose we should move them to other googlecode projects
if we use Git.

2012/2/28 Frank Martínez <[hidden email]>:

> Hi Bryan,
>
> I am glad you are interested in the Scala port. I am the main developer.
>
> You can checkout the development version with any svn client.
>
> Tell me if I can help you in any way.
>
> Cheers,
>
> Frank.
>
> On Tue, Feb 28, 2012 at 9:58 AM, Bryan Hunt <[hidden email]> wrote:
>> On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt <[hidden email]> wrote:
>>> Anyhow, I notice there is some experimental stuff going on in @
>>> http://www.mybatis.org/scala
>>>
>>> My first instinct in this situation, specifically where available
>>> artifacts are all Release Candidates (RC{1..2}), is to clone the
>>> repository and Maven build it on my own machine, then it's trivial to
>>> send patches, fix stuff locally, etc.
>>>
>>> But you guys are using Subversion, what gives? This is 2012, the world
>>> and it's dog have been using distributed version systems (Git,
>>> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
>>> I'm talking Joe the Developer.
>>>
>>> Are there any plans to move over to a decent Version Control System?
>>>
>>> Best Regards,
>>>
>>> Bryan Hunt
>>
>> Got it building in Eclipse now, file paths must match package names,
>> will keep updating my version as I fix bugs, feel free to pull in any
>> changes which are usefull to you.
>>
>> https://bitbucket.org/sentimental/mybatis-scala-copy/changesets
>>
>
>
>
> --
> Frank D. Martínez M.

[Frank Martínez]

Hi Bryan,

I miss your previous mail. I will take a look at your changes and suggestions.

Thanks for your interest in the project.

Best regards,

Frank.

On Tue, Feb 28, 2012 at 3:34 PM, Frank Martínez <[hidden email]> wrote:

> Hi Bryan,
>
> I am glad you are interested in the Scala port. I am the main developer.
>
> You can checkout the development version with any svn client.
>
> Tell me if I can help you in any way.
>
> Cheers,
>
> Frank.
>
> On Tue, Feb 28, 2012 at 9:58 AM, Bryan Hunt <[hidden email]> wrote:
>> On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt <[hidden email]> wrote:
>>> Anyhow, I notice there is some experimental stuff going on in @
>>> http://www.mybatis.org/scala
>>>
>>> My first instinct in this situation, specifically where available
>>> artifacts are all Release Candidates (RC{1..2}), is to clone the
>>> repository and Maven build it on my own machine, then it's trivial to
>>> send patches, fix stuff locally, etc.
>>>
>>> But you guys are using Subversion, what gives? This is 2012, the world
>>> and it's dog have been using distributed version systems (Git,
>>> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
>>> I'm talking Joe the Developer.
>>>
>>> Are there any plans to move over to a decent Version Control System?
>>>
>>> Best Regards,
>>>
>>> Bryan Hunt
>>
>> Got it building in Eclipse now, file paths must match package names,
>> will keep updating my version as I fix bugs, feel free to pull in any
>> changes which are usefull to you.
>>
>> https://bitbucket.org/sentimental/mybatis-scala-copy/changesets
>>
>
>
>
> --
> Frank D. Martínez M.

--
Frank D. Martínez M.

[Frank Martínez]

+1 for GIT

On Tue, Feb 28, 2012 at 3:49 PM, Frank Martínez <[hidden email]> wrote:

> Hi Bryan,
>
> I miss your previous mail. I will take a look at your changes and suggestions.
>
> Thanks for your interest in the project.
>
> Best regards,
>
> Frank.
>
> On Tue, Feb 28, 2012 at 3:34 PM, Frank Martínez <[hidden email]> wrote:
>> Hi Bryan,
>>
>> I am glad you are interested in the Scala port. I am the main developer.
>>
>> You can checkout the development version with any svn client.
>>
>> Tell me if I can help you in any way.
>>
>> Cheers,
>>
>> Frank.
>>
>> On Tue, Feb 28, 2012 at 9:58 AM, Bryan Hunt <[hidden email]> wrote:
>>> On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt <[hidden email]> wrote:
>>>> Anyhow, I notice there is some experimental stuff going on in @
>>>> http://www.mybatis.org/scala
>>>>
>>>> My first instinct in this situation, specifically where available
>>>> artifacts are all Release Candidates (RC{1..2}), is to clone the
>>>> repository and Maven build it on my own machine, then it's trivial to
>>>> send patches, fix stuff locally, etc.
>>>>
>>>> But you guys are using Subversion, what gives? This is 2012, the world
>>>> and it's dog have been using distributed version systems (Git,
>>>> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
>>>> I'm talking Joe the Developer.
>>>>
>>>> Are there any plans to move over to a decent Version Control System?
>>>>
>>>> Best Regards,
>>>>
>>>> Bryan Hunt
>>>
>>> Got it building in Eclipse now, file paths must match package names,
>>> will keep updating my version as I fix bugs, feel free to pull in any
>>> changes which are usefull to you.
>>>
>>> https://bitbucket.org/sentimental/mybatis-scala-copy/changesets
>>>
>>
>>
>>
>> --
>> Frank D. Martínez M.
>
>
>
> --
> Frank D. Martínez M.

--
Frank D. Martínez M.

[richard.myhome]

On Feb 28, 2012, at 2:58 PM, Frank Martínez <[hidden email]> wrote:

> +1 for GIT
>
> On Tue, Feb 28, 2012 at 3:49 PM, Frank Martínez <[hidden email]> wrote:
>> Hi Bryan,
>>
>> I miss your previous mail. I will take a look at your changes and suggestions.
>>
>> Thanks for your interest in the project.
>>
>> Best regards,
>>
>> Frank.
>>
>> On Tue, Feb 28, 2012 at 3:34 PM, Frank Martínez <[hidden email]> wrote:
>>> Hi Bryan,
>>>
>>> I am glad you are interested in the Scala port. I am the main developer.
>>>
>>> You can checkout the development version with any svn client.
>>>
>>> Tell me if I can help you in any way.
>>>
>>> Cheers,
>>>
>>> Frank.
>>>
>>> On Tue, Feb 28, 2012 at 9:58 AM, Bryan Hunt <[hidden email]> wrote:
>>>> On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt <[hidden email]> wrote:
>>>>> Anyhow, I notice there is some experimental stuff going on in @
>>>>> http://www.mybatis.org/scala
>>>>>
>>>>> My first instinct in this situation, specifically where available
>>>>> artifacts are all Release Candidates (RC{1..2}), is to clone the
>>>>> repository and Maven build it on my own machine, then it's trivial to
>>>>> send patches, fix stuff locally, etc.
>>>>>
>>>>> But you guys are using Subversion, what gives? This is 2012, the world
>>>>> and it's dog have been using distributed version systems (Git,
>>>>> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
>>>>> I'm talking Joe the Developer.
>>>>>
>>>>> Are there any plans to move over to a decent Version Control System?
>>>>>
>>>>> Best Regards,
>>>>>
>>>>> Bryan Hunt
>>>>
>>>> Got it building in Eclipse now, file paths must match package names,
>>>> will keep updating my version as I fix bugs, feel free to pull in any
>>>> changes which are usefull to you.
>>>>
>>>> https://bitbucket.org/sentimental/mybatis-scala-copy/changesets
>>>>
>>>
>>>
>>>
>>> --
>>> Frank D. Martínez M.
>>
>>
>>
>> --
>> Frank D. Martínez M.
>
>
>
> --
> Frank D. Martínez M.

[Tim]

Eduardo, please check the email from the dev list. Googlecode supports git. The talk about moving off googlecode was something else entirely.

On Tue, Feb 28, 2012 at 2:45 PM, Eduardo Macarron <[hidden email]> wrote:

Hi Bryan,

Switching to Git looks like a good idea. That should facilitate
contributions and that is really important.

But, we are using one repository for quite a few projects. Maybe I am
wrong but I suppose we should move them to other googlecode projects
if we use Git.

2012/2/28 Frank Martínez <[hidden email]>:

> Hi Bryan,
>
> I am glad you are interested in the Scala port. I am the main developer.
>
> You can checkout the development version with any svn client.
>
> Tell me if I can help you in any way.
>
> Cheers,
>
> Frank.
>
> On Tue, Feb 28, 2012 at 9:58 AM, Bryan Hunt <[hidden email]> wrote:
>> On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt <[hidden email]> wrote:
>>> Anyhow, I notice there is some experimental stuff going on in @
>>> http://www.mybatis.org/scala
>>>
>>> My first instinct in this situation, specifically where available
>>> artifacts are all Release Candidates (RC{1..2}), is to clone the
>>> repository and Maven build it on my own machine, then it's trivial to
>>> send patches, fix stuff locally, etc.
>>>
>>> But you guys are using Subversion, what gives? This is 2012, the world
>>> and it's dog have been using distributed version systems (Git,
>>> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
>>> I'm talking Joe the Developer.
>>>
>>> Are there any plans to move over to a decent Version Control System?
>>>
>>> Best Regards,
>>>
>>> Bryan Hunt
>>
>> Got it building in Eclipse now, file paths must match package names,
>> will keep updating my version as I fix bugs, feel free to pull in any
>> changes which are usefull to you.
>>
>> https://bitbucket.org/sentimental/mybatis-scala-copy/changesets
>>
>
>
>
> --
> Frank D. Martínez M.

[Eduardo Macarron]

Hi Tim. I know. The problem I see is that (again, I may be wrong) but
a git repo is meant to be used for one project. But we have a lot so
maybe we should create a googlecode proyect for each sub-project. Or
does google code let uses create more than one repo for one google
code project?

2012/2/28 Tim <[hidden email]>:

> Eduardo, please check the email from the dev list. Googlecode supports git.
> The talk about moving off googlecode was something else entirely.
>
>
> On Tue, Feb 28, 2012 at 2:45 PM, Eduardo Macarron
> <[hidden email]> wrote:
>>
>> Hi Bryan,
>>
>> Switching to Git looks like a good idea. That should facilitate
>> contributions and that is really important.
>>
>> But, we are using one repository for quite a few projects. Maybe I am
>> wrong but I suppose we should move them to other googlecode projects
>> if we use Git.
>>
>> 2012/2/28 Frank Martínez <[hidden email]>:
>> > Hi Bryan,
>> >
>> > I am glad you are interested in the Scala port. I am the main developer.
>> >
>> > You can checkout the development version with any svn client.
>> >
>> > Tell me if I can help you in any way.
>> >
>> > Cheers,
>> >
>> > Frank.
>> >
>> > On Tue, Feb 28, 2012 at 9:58 AM, Bryan Hunt
>> > <[hidden email]> wrote:
>> >> On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt
>> >> <[hidden email]> wrote:
>> >>> Anyhow, I notice there is some experimental stuff going on in @
>> >>> http://www.mybatis.org/scala
>> >>>
>> >>> My first instinct in this situation, specifically where available
>> >>> artifacts are all Release Candidates (RC{1..2}), is to clone the
>> >>> repository and Maven build it on my own machine, then it's trivial to
>> >>> send patches, fix stuff locally, etc.
>> >>>
>> >>> But you guys are using Subversion, what gives? This is 2012, the world
>> >>> and it's dog have been using distributed version systems (Git,
>> >>> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
>> >>> I'm talking Joe the Developer.
>> >>>
>> >>> Are there any plans to move over to a decent Version Control System?
>> >>>
>> >>> Best Regards,
>> >>>
>> >>> Bryan Hunt
>> >>
>> >> Got it building in Eclipse now, file paths must match package names,
>> >> will keep updating my version as I fix bugs, feel free to pull in any
>> >> changes which are usefull to you.
>> >>
>> >> https://bitbucket.org/sentimental/mybatis-scala-copy/changesets
>> >>
>> >
>> >
>> >
>> > --
>> > Frank D. Martínez M.
>
>

[Tim]

oh sorry I remember that conversation now.

On Tue, Feb 28, 2012 at 3:12 PM, Eduardo Macarron <[hidden email]> wrote:

Hi Tim. I know. The problem I see is that (again, I may be wrong) but
a git repo is meant to be used for one project. But we have a lot so
maybe we should create a googlecode proyect for each sub-project. Or
does google code let uses create more than one repo for one google
code project?

2012/2/28 Tim <[hidden email]>:

> Eduardo, please check the email from the dev list. Googlecode supports git.
> The talk about moving off googlecode was something else entirely.
>
>
> On Tue, Feb 28, 2012 at 2:45 PM, Eduardo Macarron
> <[hidden email]> wrote:
>>
>> Hi Bryan,
>>
>> Switching to Git looks like a good idea. That should facilitate
>> contributions and that is really important.
>>
>> But, we are using one repository for quite a few projects. Maybe I am
>> wrong but I suppose we should move them to other googlecode projects
>> if we use Git.
>>
>> 2012/2/28 Frank Martínez <[hidden email]>:
>> > Hi Bryan,
>> >
>> > I am glad you are interested in the Scala port. I am the main developer.
>> >
>> > You can checkout the development version with any svn client.
>> >
>> > Tell me if I can help you in any way.
>> >
>> > Cheers,
>> >
>> > Frank.
>> >
>> > On Tue, Feb 28, 2012 at 9:58 AM, Bryan Hunt
>> > <[hidden email]> wrote:
>> >> On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt
>> >> <[hidden email]> wrote:
>> >>> Anyhow, I notice there is some experimental stuff going on in @
>> >>> http://www.mybatis.org/scala
>> >>>
>> >>> My first instinct in this situation, specifically where available
>> >>> artifacts are all Release Candidates (RC{1..2}), is to clone the
>> >>> repository and Maven build it on my own machine, then it's trivial to
>> >>> send patches, fix stuff locally, etc.
>> >>>
>> >>> But you guys are using Subversion, what gives? This is 2012, the world
>> >>> and it's dog have been using distributed version systems (Git,
>> >>> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
>> >>> I'm talking Joe the Developer.
>> >>>
>> >>> Are there any plans to move over to a decent Version Control System?
>> >>>
>> >>> Best Regards,
>> >>>
>> >>> Bryan Hunt
>> >>
>> >> Got it building in Eclipse now, file paths must match package names,
>> >> will keep updating my version as I fix bugs, feel free to pull in any
>> >> changes which are usefull to you.
>> >>
>> >> https://bitbucket.org/sentimental/mybatis-scala-copy/changesets
>> >>
>> >
>> >
>> >
>> > --
>> > Frank D. Martínez M.
>
>

[Eduardo Macarron]

Tim... I am lost :) what conversation?

2012/2/28 Tim <[hidden email]>:

> oh sorry I remember that conversation now.
>
>
> On Tue, Feb 28, 2012 at 3:12 PM, Eduardo Macarron
> <[hidden email]> wrote:
>>
>> Hi Tim. I know. The problem I see is that (again, I may be wrong) but
>> a git repo is meant to be used for one project. But we have a lot so
>> maybe we should create a googlecode proyect for each sub-project. Or
>> does google code let uses create more than one repo for one google
>> code project?
>>
>> 2012/2/28 Tim <[hidden email]>:
>> > Eduardo, please check the email from the dev list. Googlecode supports
>> > git.
>> > The talk about moving off googlecode was something else entirely.
>> >
>> >
>> > On Tue, Feb 28, 2012 at 2:45 PM, Eduardo Macarron
>> > <[hidden email]> wrote:
>> >>
>> >> Hi Bryan,
>> >>
>> >> Switching to Git looks like a good idea. That should facilitate
>> >> contributions and that is really important.
>> >>
>> >> But, we are using one repository for quite a few projects. Maybe I am
>> >> wrong but I suppose we should move them to other googlecode projects
>> >> if we use Git.
>> >>
>> >> 2012/2/28 Frank Martínez <[hidden email]>:
>> >> > Hi Bryan,
>> >> >
>> >> > I am glad you are interested in the Scala port. I am the main
>> >> > developer.
>> >> >
>> >> > You can checkout the development version with any svn client.
>> >> >
>> >> > Tell me if I can help you in any way.
>> >> >
>> >> > Cheers,
>> >> >
>> >> > Frank.
>> >> >
>> >> > On Tue, Feb 28, 2012 at 9:58 AM, Bryan Hunt
>> >> > <[hidden email]> wrote:
>> >> >> On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt
>> >> >> <[hidden email]> wrote:
>> >> >>> Anyhow, I notice there is some experimental stuff going on in @
>> >> >>> http://www.mybatis.org/scala
>> >> >>>
>> >> >>> My first instinct in this situation, specifically where available
>> >> >>> artifacts are all Release Candidates (RC{1..2}), is to clone the
>> >> >>> repository and Maven build it on my own machine, then it's trivial
>> >> >>> to
>> >> >>> send patches, fix stuff locally, etc.
>> >> >>>
>> >> >>> But you guys are using Subversion, what gives? This is 2012, the
>> >> >>> world
>> >> >>> and it's dog have been using distributed version systems (Git,
>> >> >>> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking
>> >> >>> elite,
>> >> >>> I'm talking Joe the Developer.
>> >> >>>
>> >> >>> Are there any plans to move over to a decent Version Control
>> >> >>> System?
>> >> >>>
>> >> >>> Best Regards,
>> >> >>>
>> >> >>> Bryan Hunt
>> >> >>
>> >> >> Got it building in Eclipse now, file paths must match package names,
>> >> >> will keep updating my version as I fix bugs, feel free to pull in
>> >> >> any
>> >> >> changes which are usefull to you.
>> >> >>
>> >> >> https://bitbucket.org/sentimental/mybatis-scala-copy/changesets
>> >> >>
>> >> >
>> >> >
>> >> >
>> >> > --
>> >> > Frank D. Martínez M.
>> >
>> >
>
>

[bryan hunt]

Frank.
 
You're welcome. I've got to wrap up my current project so I'm just using the regular MyBatis Java code for the time-being.

However, I intend to spend a bit of time playing with your project too.

It should be easier now for someone to  get started with it under Scala-IDE.
 
Some things I'm interested in:

Scala Type aware TypeHandler's:

TypeHandler's for persisting Scala classes with exotic properties, for example:

Option[Language], where Language has a single String value  which is to be stored in the database as an INTEGER.
 
In general:
Wrapping properties in Option so they bind to None when a null value is retrieved from the database.

Best Regards,

Bryan Hunt

[Dridi Boukelmoune]

Git is just a VCS, it doesn't matter what you put inside a repo.
You can use it for several projects, it's not an issue.

Google Code supports git but I don't think it has support for puul
request like at github's.

By the way I recommend git :)

Dridi

http://www.zenika.com/

On 28 fév, 22:12, Eduardo Macarron <[hidden email]> wrote:

> Hi Tim. I know. The problem I see is that (again, I may be wrong) but
> a git repo is meant to be used for one project. But we have a lot so
> maybe we should create a googlecode proyect for each sub-project. Or
> does google code let uses create more than one repo for one google
> code project?
>
> 2012/2/28 Tim <[hidden email]>:
>
>
>
>
>
>
>
> > Eduardo, please check the email from the dev list. Googlecode supports git.
> > The talk about moving off googlecode was something else entirely.
>
> > On Tue, Feb 28, 2012 at 2:45 PM, Eduardo Macarron
> > <[hidden email]> wrote:
>
> >> Hi Bryan,
>
> >> Switching to Git looks like a good idea. That should facilitate
> >> contributions and that is really important.
>
> >> But, we are using one repository for quite a few projects. Maybe I am
> >> wrong but I suppose we should move them to other googlecode projects
> >> if we use Git.
>
> >> 2012/2/28 Frank Martínez <[hidden email]>:
> >> > Hi Bryan,
>
> >> > I am glad you are interested in the Scala port. I am the main developer.
>
> >> > You can checkout the development version with any svn client.
>
> >> > Tell me if I can help you in any way.
>
> >> > Cheers,
>
> >> > Frank.
>
> >> > On Tue, Feb 28, 2012 at 9:58 AM, Bryan Hunt
> >> > <[hidden email]> wrote:
> >> >> On Tue, 28 Feb 2012 02:28:41 -0800 (PST), bryan hunt
> >> >> <[hidden email]> wrote:
> >> >>> Anyhow, I notice there is some experimental stuff going on in @
> >> >>>http://www.mybatis.org/scala
>
> >> >>> My first instinct in this situation, specifically where available
> >> >>> artifacts are all Release Candidates (RC{1..2}), is to clone the
> >> >>> repository and Maven build it on my own machine, then it's trivial to
> >> >>> send patches, fix stuff locally, etc.
>
> >> >>> But you guys are using Subversion, what gives? This is 2012, the world
> >> >>> and it's dog have been using distributed version systems (Git,
> >> >>> Mercurial, Darks, Bazaar ) since at least 2009. I'm not talking elite,
> >> >>> I'm talking Joe the Developer.
>
> >> >>> Are there any plans to move over to a decent Version Control System?
>
> >> >>> Best Regards,
>
> >> >>> Bryan Hunt
>
> >> >> Got it building in Eclipse now, file paths must match package names,
> >> >> will keep updating my version as I fix bugs, feel free to pull in any
> >> >> changes which are usefull to you.
>
> >> >>https://bitbucket.org/sentimental/mybatis-scala-copy/changesets
>
> >> > --
> >> > Frank D. Martínez M.

[Eduardo Macarron]

Sorry for my ignorace. I do not use Git on a daily basis so I may be wrong.

There is just one SVN repo in mybatis Google Code project but have a
look at this paths:

http://mybatis.googlecode.com/svn/trunk/
http://mybatis.googlecode.com/svn/tags/
http://mybatis.googlecode.com/svn/branches/

http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/trunk/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/tags/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/branches/

http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/trunk/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/tags/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/branches/

When I migrated the SVN to a local Git repo the migration tool created
a master branch for:
http://mybatis.googlecode.com/svn/trunk/

branches for:
http://mybatis.googlecode.com/svn/branches/

and tags for:
http://mybatis.googlecode.com/svn/tags/

But tags/trunks for the sub-projects were lost.

No suprise here. Git simply works in a different way.

Google code provides one Git repo for each Google Code project. That
is why I meant that moving from SVN -> Git will imply moving from one
Google Code project to many or... going elsewhere.

Let me know if I am wrong. (very likely indeed)

[Dridi Boukelmoune]

I didn't check the directory structure of the repo.

Indeed it's not that easy to move to git given your "multiple-repo" svn repo.
With git you can only clone a full copy of the repo, not a subdirectory as svn can do.

I assume you have multiple repos to have a clean history for each project (without noise comming from other projects).

Two obvious choices for migration:
1- Use one repo for all projects and lose history
2- Create N repo and have the sub-projects as separate git submodules of the main project

Anyway, you can also have a clean history with a single repo, git alows to specify a path for a lot of commands.
Example : git log -- path/to/mybatis-spring

For submodules I would highly recommend github for hosting.
It has very nice cross-project browsing when using submodules.

Dridi

http://www.zenika.com/

Le jeudi 1 mars 2012 08:54:06 UTC+1, Eduardo a écrit :

Sorry for my ignorace. I do not use Git on a daily basis so I may be wrong.

There is just one SVN repo in mybatis Google Code project but have a
look at this paths:

http://mybatis.googlecode.com/svn/trunk/
http://mybatis.googlecode.com/svn/tags/
http://mybatis.googlecode.com/svn/branches/

http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/trunk/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/tags/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/branches/

http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/trunk/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/tags/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/branches/

When I migrated the SVN to a local Git repo the migration tool created
a master branch for:
http://mybatis.googlecode.com/svn/trunk/

branches for:
http://mybatis.googlecode.com/svn/branches/

and tags for:
http://mybatis.googlecode.com/svn/tags/

But tags/trunks for the sub-projects were lost.

No suprise here. Git simply works in a different way.

Google code provides one Git repo for each Google Code project. That
is why I meant that moving from SVN -> Git will imply moving from one
Google Code project to many or... going elsewhere.

Let me know if I am wrong. (very likely indeed)

Le jeudi 1 mars 2012 08:54:06 UTC+1, Eduardo a écrit :

Sorry for my ignorace. I do not use Git on a daily basis so I may be wrong.

There is just one SVN repo in mybatis Google Code project but have a
look at this paths:

http://mybatis.googlecode.com/svn/trunk/
http://mybatis.googlecode.com/svn/tags/
http://mybatis.googlecode.com/svn/branches/

http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/trunk/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/tags/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/branches/

http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/trunk/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/tags/
http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/branches/

When I migrated the SVN to a local Git repo the migration tool created
a master branch for:
http://mybatis.googlecode.com/svn/trunk/

branches for:
http://mybatis.googlecode.com/svn/branches/

and tags for:
http://mybatis.googlecode.com/svn/tags/

But tags/trunks for the sub-projects were lost.

No suprise here. Git simply works in a different way.

Google code provides one Git repo for each Google Code project. That
is why I meant that moving from SVN -> Git will imply moving from one
Google Code project to many or... going elsewhere.

Let me know if I am wrong. (very likely indeed)

[Eduardo Macarron]

Hi Dridi, this is really valuable information. Thank you!

2012/3/2 Dridi Boukelmoune <[hidden email]>:

> I didn't check the directory structure of the repo.
>
> Indeed it's not that easy to move to git given your "multiple-repo" svn
> repo.
> With git you can only clone a full copy of the repo, not a subdirectory as
> svn can do.
>
> I assume you have multiple repos to have a clean history for each project
> (without noise comming from other projects).
>
> Two obvious choices for migration:
> 1- Use one repo for all projects and lose history
> 2- Create N repo and have the sub-projects as separate git submodules of the
> main project
>
> Anyway, you can also have a clean history with a single repo, git alows to
> specify a path for a lot of commands.
> Example : git log -- path/to/mybatis-spring
>
> For submodules I would highly recommend github for hosting.
> It has very nice cross-project browsing when using submodules.
>
> Dridi
>
> http://www.zenika.com/
>
> Le jeudi 1 mars 2012 08:54:06 UTC+1, Eduardo a écrit :
>>
>> Sorry for my ignorace. I do not use Git on a daily basis so I may be
>> wrong.
>>
>> There is just one SVN repo in mybatis Google Code project but have a
>> look at this paths:
>>
>> http://mybatis.googlecode.com/svn/trunk/
>> http://mybatis.googlecode.com/svn/tags/
>> http://mybatis.googlecode.com/svn/branches/
>>
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/trunk/
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/tags/
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/branches/
>>
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/trunk/
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/tags/
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/branches/
>>
>> When I migrated the SVN to a local Git repo the migration tool created
>> a master branch for:
>> http://mybatis.googlecode.com/svn/trunk/
>>
>> branches for:
>> http://mybatis.googlecode.com/svn/branches/
>>
>> and tags for:
>> http://mybatis.googlecode.com/svn/tags/
>>
>> But tags/trunks for the sub-projects were lost.
>>
>> No suprise here. Git simply works in a different way.
>>
>> Google code provides one Git repo for each Google Code project. That
>> is why I meant that moving from SVN -> Git will imply moving from one
>> Google Code project to many or... going elsewhere.
>>
>> Let me know if I am wrong. (very likely indeed)
>
>
> Le jeudi 1 mars 2012 08:54:06 UTC+1, Eduardo a écrit :
>>
>> Sorry for my ignorace. I do not use Git on a daily basis so I may be
>> wrong.
>>
>> There is just one SVN repo in mybatis Google Code project but have a
>> look at this paths:
>>
>> http://mybatis.googlecode.com/svn/trunk/
>> http://mybatis.googlecode.com/svn/tags/
>> http://mybatis.googlecode.com/svn/branches/
>>
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/trunk/
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/tags/
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-guice/branches/
>>
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/trunk/
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/tags/
>> http://mybatis.googlecode.com/svn/sub-projects/mybatis-spring/branches/
>>
>> When I migrated the SVN to a local Git repo the migration tool created
>> a master branch for:
>> http://mybatis.googlecode.com/svn/trunk/
>>
>> branches for:
>> http://mybatis.googlecode.com/svn/branches/
>>
>> and tags for:
>> http://mybatis.googlecode.com/svn/tags/
>>
>> But tags/trunks for the sub-projects were lost.
>>
>> No suprise here. Git simply works in a different way.
>>
>> Google code provides one Git repo for each Google Code project. That
>> is why I meant that moving from SVN -> Git will imply moving from one
>> Google Code project to many or... going elsewhere.
>>
>> Let me know if I am wrong. (very likely indeed)