Nabble - seam-dev

Re: Overriding annotated types and the SPI

2009-11-25T05:52:25Z

BTW if you can write me a test for weld core tests (just copy the one in org.jboss.weld.tests.extensions) then I can probably fix much quicker :-)

On 25 Nov 2009, at 13:47, Pete Muir wrote:

> I'm still ploughing through email backlog, exhaustion, housework, paperwork, and other tasks ;-) but I am hopeful that Thanksgiving will give me time to catch up and I can start fixing bugs in Weld this week.
>
> On 23 Nov 2009, at 22:29, Stuart Douglas wrote:
>
>> I have managed to work around this by storing a Set of every java class I have registered and the vetoing the bean when it comes up bean discovery. Any idea when this will be fixed? I could work around it properly by generating a new class using javassist for every bean I add with the SPI, however I would rather not go down that route.
>>
>> Stuart
>> ________________________________________
>> From: Pete Muir [pmuir@...]
>> Sent: Tuesday, 24 November 2009 4:04 AM
>> To: Gavin King
>> Cc: Stuart Douglas; seam-dev@...
>> Subject: Re: [seam-dev] Overriding annotated types and the SPI
>>
>> Yes, this is a bug for sure :-)
>>
>> https://jira.jboss.org/jira/browse/WELD-309
>>
>> On 23 Nov 2009, at 16:52, Gavin King wrote:
>>
>>> Pete, there are allowed to be two AnnotatedTypes for the same Java class.
>>>
>>> On Mon, Nov 23, 2009 at 8:17 AM, Pete Muir <pmuir@...> wrote:
>>>> I guess what you are seeing is bug in Weld, whereby we need to adjust quite what makes two annotated types equal so that you see both the one you added, and the new one, rather than only getting one or the other. Even with this fix, you would have an error, as you now have two identical classes which Weld will discover beans for. You need to veto the built in annotated type (otherwise you end up *adding* an existing annotated type, not replacing it).
>>>>
>>>> On 23 Nov 2009, at 07:37, Stuart Douglas wrote:
>>>>
>>>>> I am trying to register an additional bean. It works perfectly when the class is not in a bean deployment archive, however if QualifiedBean2 is in a bean deployment archive then it stops working. The bean itself does not have any annotations.
>>>>>
>>>>> Stuart
>>>>>
>>>>>
>>>>> ________________________________________
>>>>> From: Gavin King [gavin.king@...]
>>>>> Sent: Monday, 23 November 2009 6:29 PM
>>>>> To: Stuart Douglas
>>>>> Cc: seam-dev@...
>>>>> Subject: Re: [seam-dev] Overriding annotated types and the SPI
>>>>>
>>>>> Are you trying to:
>>>>>
>>>>> (a) *override* the bean that the container creates, or
>>>>> (b) are you trying to register additional beans?
>>>>>
>>>>> If (a), you would need to call veto() on the AnnotatedType created by
>>>>> the container.
>>>>>
>>>>> On Mon, Nov 23, 2009 at 1:19 AM, Stuart Douglas
>>>>> <stuart@...> wrote:
>>>>>> I have been working on my XML configuration extension and have been making good progress, however I have run into some behavior that I cannot explain.
>>>>>> At the moment in my XML file I can do this:
>>>>>>
>>>>>>
>>>>>> <test:OtherQualifier>
>>>>>> <Qualifier/>
>>>>>> </test:OtherQualifier>
>>>>>>
>>>>>> <test:QualifiedBean2>
>>>>>> <test:OtherQualifier value1="BB" value2="2"/>
>>>>>> </test:QualifiedBean2>
>>>>>>
>>>>>> <test:QualifierTestBean>
>>>>>> <test:bean2>
>>>>>> <test:OtherQualifier value1="BB" value2="2"/>
>>>>>> <Inject/>
>>>>>> </test:bean2>
>>>>>> </test:QualifierTestBean>
>>>>>>
>>>>>> When my extension sees this it creates two AnnotatedTypes and a Qualifier and registers them in the BeforeBeanDiscovery event. This all works fine, QualifiedBean2 gets injected into QualifierTestBean and life is good.
>>>>>> However if QualifiedBean2 is deployed inside a Bean archive things suddenly go pear shaped, all of a sudden the container seems to forget about the qualifier on QualifiedBean2 and it stops working. Does anyone have any idea what could be causing this? It looks like the bean deployment process is overriding my user supplied type level metadata.
>>>>>>
>>>>>> Thanks,
>>>>>>
>>>>>> Stuart
>>>>>> _______________________________________________
>>>>>> seam-dev mailing list
>>>>>> seam-dev@...
>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Gavin King
>>>>> gavin.king@...
>>>>> http://in.relation.to/Bloggers/Gavin
>>>>> http://hibernate.org
>>>>> http://seamframework.org
>>>>>
>>>>> _______________________________________________
>>>>> seam-dev mailing list
>>>>> seam-dev@...
>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Gavin King
>>> gavin.king@...
>>> http://in.relation.to/Bloggers/Gavin
>>> http://hibernate.org
>>> http://seamframework.org
>>
>

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Seam 3 examples release cycle

2009-11-25T05:48:31Z

Yes, I came to the same conclusion as Dan. BTW no reason you can't tag and release a beta of the example when you get your update in.

On 24 Nov 2009, at 20:13, Dan Allen wrote:

> Yep, this parallels the problem with docs, which we decided belong in the module.
>
> It's possible we could still have broader examples that go into a shared examples directory and only update on a full Seam release, then have local examples for modules that can be updated more often. Actually, this option is good because we can verify backward compatibility in the general examples while still having the flexibility to demonstrate more specific features in the module-local examples.
>
> -Dan
>
> On Tue, Nov 24, 2009 at 12:00 PM, Shane Bryzak <sbryzak@...> wrote:
> I can foresee a potential issue with the release cycle for examples,
> especially if we go down the path that we discussed during the meeting
> where we consolidate examples into more complex apps that demonstrate
> multiple Seam features. For example, let's say that we release a
> production version of Seam 3.0.0 that contains (among other things):
>
> Seam Security 3.0.0
> Seam examples 3.0.0
>
> Now let's say I add some new feature into security and decide to do a
> release of Seam Security 3.0.1. If I have accordingly updated the
> security examples with the new feature, does that mean that I need to do
> a simultaneous release of Seam examples 3.0.1? Also, what if other
> sub-project leads have in the meantime added new features to their
> modules and their examples are in an incomplete state? As you can see
> this becomes a problem.
>
> One possible solution is to remove the examples branch altogether and
> include the examples within the related module instead. This prevents
> us though from creating multi-feature examples, as they will be bound to
> the sub-project lifecycle. One other option is to only release
> examples during a major Seam release, however this is less desirable in
> the case where we release a module with complex new features that really
> need to be demonstrated.
>
> IMHO out of these two options the first one seems the lesser of two
> evils, however I'm wondering what you guys think.
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
>
> --
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://www.google.com/profiles/dan.j.allen
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Overriding annotated types and the SPI

2009-11-25T05:47:24Z

I'm still ploughing through email backlog, exhaustion, housework, paperwork, and other tasks ;-) but I am hopeful that Thanksgiving will give me time to catch up and I can start fixing bugs in Weld this week.

On 23 Nov 2009, at 22:29, Stuart Douglas wrote:

> I have managed to work around this by storing a Set of every java class I have registered and the vetoing the bean when it comes up bean discovery. Any idea when this will be fixed? I could work around it properly by generating a new class using javassist for every bean I add with the SPI, however I would rather not go down that route.
>
> Stuart
> ________________________________________
> From: Pete Muir [pmuir@...]
> Sent: Tuesday, 24 November 2009 4:04 AM
> To: Gavin King
> Cc: Stuart Douglas; seam-dev@...
> Subject: Re: [seam-dev] Overriding annotated types and the SPI
>
> Yes, this is a bug for sure :-)
>
> https://jira.jboss.org/jira/browse/WELD-309
>
> On 23 Nov 2009, at 16:52, Gavin King wrote:
>
>> Pete, there are allowed to be two AnnotatedTypes for the same Java class.
>>
>> On Mon, Nov 23, 2009 at 8:17 AM, Pete Muir <pmuir@...> wrote:
>>> I guess what you are seeing is bug in Weld, whereby we need to adjust quite what makes two annotated types equal so that you see both the one you added, and the new one, rather than only getting one or the other. Even with this fix, you would have an error, as you now have two identical classes which Weld will discover beans for. You need to veto the built in annotated type (otherwise you end up *adding* an existing annotated type, not replacing it).
>>>
>>> On 23 Nov 2009, at 07:37, Stuart Douglas wrote:
>>>
>>>> I am trying to register an additional bean. It works perfectly when the class is not in a bean deployment archive, however if QualifiedBean2 is in a bean deployment archive then it stops working. The bean itself does not have any annotations.
>>>>
>>>> Stuart
>>>>
>>>>
>>>> ________________________________________
>>>> From: Gavin King [gavin.king@...]
>>>> Sent: Monday, 23 November 2009 6:29 PM
>>>> To: Stuart Douglas
>>>> Cc: seam-dev@...
>>>> Subject: Re: [seam-dev] Overriding annotated types and the SPI
>>>>
>>>> Are you trying to:
>>>>
>>>> (a) *override* the bean that the container creates, or
>>>> (b) are you trying to register additional beans?
>>>>
>>>> If (a), you would need to call veto() on the AnnotatedType created by
>>>> the container.
>>>>
>>>> On Mon, Nov 23, 2009 at 1:19 AM, Stuart Douglas
>>>> <stuart@...> wrote:
>>>>> I have been working on my XML configuration extension and have been making good progress, however I have run into some behavior that I cannot explain.
>>>>> At the moment in my XML file I can do this:
>>>>>
>>>>>
>>>>> <test:OtherQualifier>
>>>>> <Qualifier/>
>>>>> </test:OtherQualifier>
>>>>>
>>>>> <test:QualifiedBean2>
>>>>> <test:OtherQualifier value1="BB" value2="2"/>
>>>>> </test:QualifiedBean2>
>>>>>
>>>>> <test:QualifierTestBean>
>>>>> <test:bean2>
>>>>> <test:OtherQualifier value1="BB" value2="2"/>
>>>>> <Inject/>
>>>>> </test:bean2>
>>>>> </test:QualifierTestBean>
>>>>>
>>>>> When my extension sees this it creates two AnnotatedTypes and a Qualifier and registers them in the BeforeBeanDiscovery event. This all works fine, QualifiedBean2 gets injected into QualifierTestBean and life is good.
>>>>> However if QualifiedBean2 is deployed inside a Bean archive things suddenly go pear shaped, all of a sudden the container seems to forget about the qualifier on QualifiedBean2 and it stops working. Does anyone have any idea what could be causing this? It looks like the bean deployment process is overriding my user supplied type level metadata.
>>>>>
>>>>> Thanks,
>>>>>
>>>>> Stuart
>>>>> _______________________________________________
>>>>> seam-dev mailing list
>>>>> seam-dev@...
>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Gavin King
>>>> gavin.king@...
>>>> http://in.relation.to/Bloggers/Gavin
>>>> http://hibernate.org
>>>> http://seamframework.org
>>>>
>>>> _______________________________________________
>>>> seam-dev mailing list
>>>> seam-dev@...
>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>
>>
>>
>> --
>> Gavin King
>> gavin.king@...
>> http://in.relation.to/Bloggers/Gavin
>> http://hibernate.org
>> http://seamframework.org
>

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Mercurial vs GIT

2009-11-25T05:21:10Z

I've imported Weld core trunk into both GitHub http://github.com/pmuir/weld-test and BitBucket: http://bitbucket.org/pmuir/weld-test/ for people to play with.

Both these repos will be dropped once we make a decision, so treat them as playgrounds only!

Pete

On 25 Nov 2009, at 13:07, Mark Struberg wrote:

> Another strong point for using GIT is the Gerrit source review system.
> It makes contributing patches easier, and much more: it makes _applying_ those contributions even easier.
>
> LieGrue,
> strub
>
> --- Pete Muir <pmuir@...> schrieb am Mi, 25.11.2009:
>
>> Von: Pete Muir <pmuir@...>
>> Betreff: Re: [seam-dev] Mercurial vs GIT
>> An: "Daniel Roth" <daniel@...>
>> CC: "seam-dev@..." <seam-dev@...>
>> Datum: Mittwoch, 25. November 2009, 13:43
>> I can certainly see that a DVCS might
>> not be a good fit for closed source / in company software
>> development. All the work an engineer on the project does is
>> likely to make it into the project at some point (even if
>> heavily refactored), and they are unlikely to want to share
>> it with many other people before it goes into VCS.
>>
>> However if you consider Seam, then there are often cases
>> where someone is maintaining a patch for months or even
>> years against trunk which they want to easily share with
>> other users. As we move towards to a more modular approach,
>> this becomes even more apparent - you might want to develop
>> a module outside the Seam master, and share it with the
>> community. At some point we might add it to the master. I
>> believe a DVCS is ideally suited to this.
>>
>> Pete
>>
>> On 24 Nov 2009, at 22:22, Daniel Roth wrote:
>>
>>> 1) I have not tried GIT...
>>> 2) Comparing Mercurial and SVN, for me, is like
>> comparing an nightmare and ease of use.
>>>
>>> There is a Mercurial plugin for Eclipse, but it's
>> really no good. We experienced some bugs at work with it
>> (DivideByZero), submitted a patch but... Still nothing has
>> happened... I've tried meld, kdiff3 and the tortoise thingy
>> for windows, but still I always end up with command line
>> because things don't work. Also there is really no good way
>> of branching. Named branches is a MESS so even the hg team
>> thinks it's better to crete to different clones and then
>> manually merge them. (See their manual)
>>>
>>> One other thing I'd like to say is that having a
>> distr. repo may sound really fancy, but it's rarely needed.
>> Although being spread over different offices all over the
>> world, that feature is never really needed at my work. And
>> the really really really few times it is, you could just as
>> well make an ordinary patch, and give it to the other
>> person. However, there have been many times when hours has
>> been wasted when trying to resolve issues when two people
>> have worked in our root repo at the same time.
>>>
>>> Just my 10 öre...
>>>
>>> Daniel
>>>
>>>
>>> On Tue, Nov 24, 2009 at 11:00 PM, Stuart Douglas
>> <stuart@...>
>> wrote:
>>> As I understand it GIT support on windows is not good,
>> and also just having a quick google around it looks like the
>> tooling support is not very mature either. Also the commands
>> are different to subversions commands so there is quite a
>> steep learning curve.
>>> I like bazaar, it uses the same commands as
>> subversion, works on all platforms and has eclipse and
>> windows support. It also has launchpad, which is the bzr
>> equivalent of github.
>>>
>>> Stuart
>>> ________________________________________
>>> From: seam-dev-bounces@...
>> [seam-dev-bounces@...]
>> On Behalf Of Francisco Jose Peredo [franciscoperedo@...]
>>> Sent: Wednesday, 25 November 2009 1:17 AM
>>> To: seam-dev@...
>>> Cc: weld-dev@...
>>> Subject: Re: [seam-dev] Mercurial vs GIT
>>>
>>> I have not tried GIT, but from what I have read it is
>> pretty complicated
>>> to learn to use...
>>> OTOH I have tried Mercurial, which is also
>> distributed, and found it
>>> confortable... apparently the
>>> way it deals with its distribute nature is easier for
>> subversion users
>>> to understand...
>>> AFAIK Netbeans source code is in Mercurial, also
>> OpenJDK... So it seems
>>> to work
>>> well with large code bases... and there are plugins
>> for Netbeans,
>>> Eclipse and the Tortoise Hg
>>> project is advanced and usable...
>>> Google Code offers free Mercurial hosting...
>>> Why not Mercurial?
>>>
>>>
>>>
>>> Pete Muir escribió:
>>>> A quick item we discussed at the f2f meeting was
>> whether to switch to
>>>> GIT for our SCM, rather than SVN.
>>>>
>>>> This would give us a IMO a system well suited to
>> our distribued dev
>>>> model, it would also make it much easier for
>> others to sandbox PEs and
>>>> then contribute them back to us.
>>>>
>>>> The proposal is to use Github to host.
>>>>
>>>> The team members at devoxx were in favour, but
>> what do others think?
>>>>
>>>> Pete
>>>>
>>>> --
>>>> Pete Muir
>>>> http://in.relation.to/Bloggers/Pete
>>>> _______________________________________________
>>>> seam-dev mailing list
>>>> seam-dev@...
>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>>
>>>>
>>>
>>>
>>> --
>>> Dirección Informática de Servicios Financieros
>>> Dirección General de Modernización e Innovación
>> Gubernamental
>>> Secretaría de Administración y Finanzas
>>> Paseo de la Sierra 435 col. Reforma
>>> C.P. 86086, Villahermosa, Tabasco.
>>> Tel. 52 + 993 + 310 40 00 Ext. 7127
>>> http://saf.tabasco.gob.mx/
>>>
>>> IMPORTANTE: Esta transmisión electrónica, incluyendo
>> sus anexos, archivos insertados o "attachments", puede
>> constituir información confidencial o reservada, en los
>> términos de la Ley de Acceso a la Información Pública del
>> Estado de Tabasco, y estar protegida por el derecho
>> fundamental a la privacidad. Se prohibe el uso de esta
>> información por cualquier persona distinta al receptor
>> intencional o previsto. Si usted ha recibibido esta
>> transmisión electrónica por error, por favor responda
>> inmediatamente al emisor y borre esta información de su
>> sistema. El uso, diseminación, distribución o
>> reproducción de esta transmisión electrónica por
>> receptores no intencionados o no previstos por el emisor, no
>> está autorizada y puede considerarse ilícita en los
>> términos de la legislación penal y civil vigente.
>>>
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev@...
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev@...
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>>
>>> --
>>> Daniel Roth
>>> M.Sc. Computer Science
>>> daniel@...
>>> www.danielroth.se
>>> +46 736 36 29 46
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev@...
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>>
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>
> __________________________________________________
> Do You Yahoo!?
> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.
> http://mail.yahoo.com

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Mercurial vs GIT

2009-11-25T05:07:35Z

Another strong point for using GIT is the Gerrit source review system.
It makes contributing patches easier, and much more: it makes _applying_ those contributions even easier.

LieGrue,
strub

--- Pete Muir <pmuir@...> schrieb am Mi, 25.11.2009:

> Von: Pete Muir <pmuir@...>
> Betreff: Re: [seam-dev] Mercurial vs GIT
> An: "Daniel Roth" <daniel@...>
> CC: "seam-dev@..." <seam-dev@...>
> Datum: Mittwoch, 25. November 2009, 13:43
> I can certainly see that a DVCS might
> not be a good fit for closed source / in company software
> development. All the work an engineer on the project does is
> likely to make it into the project at some point (even if
> heavily refactored), and they are unlikely to want to share
> it with many other people before it goes into VCS.
>
> However if you consider Seam, then there are often cases
> where someone is maintaining a patch for months or even
> years against trunk which they want to easily share with
> other users. As we move towards to a more modular approach,
> this becomes even more apparent - you might want to develop
> a module outside the Seam master, and share it with the
> community. At some point we might add it to the master. I
> believe a DVCS is ideally suited to this.
>
> Pete
>
> On 24 Nov 2009, at 22:22, Daniel Roth wrote:
>
> > 1) I have not tried GIT...
> > 2) Comparing Mercurial and SVN, for me, is like
> comparing an nightmare and ease of use.
> >
> > There is a Mercurial plugin for Eclipse, but it's
> really no good. We experienced some bugs at work with it
> (DivideByZero), submitted a patch but... Still nothing has
> happened... I've tried meld, kdiff3 and the tortoise thingy
> for windows, but still I always end up with command line
> because things don't work. Also there is really no good way
> of branching. Named branches is a MESS so even the hg team
> thinks it's better to crete to different clones and then
> manually merge them. (See their manual)
> >
> > One other thing I'd like to say is that having a
> distr. repo may sound really fancy, but it's rarely needed.
> Although being spread over different offices all over the
> world, that feature is never really needed at my work. And
> the really really really few times it is, you could just as
> well make an ordinary patch, and give it to the other
> person. However, there have been many times when hours has
> been wasted when trying to resolve issues when two people
> have worked in our root repo at the same time.
> >
> > Just my 10 öre...
> >
> > Daniel
> >
> >
> > On Tue, Nov 24, 2009 at 11:00 PM, Stuart Douglas
> <stuart@...>
> wrote:
> > As I understand it GIT support on windows is not good,
> and also just having a quick google around it looks like the
> tooling support is not very mature either. Also the commands
> are different to subversions commands so there is quite a
> steep learning curve.
> > I like bazaar, it uses the same commands as
> subversion, works on all platforms and has eclipse and
> windows support. It also has launchpad, which is the bzr
> equivalent of github.
> >
> > Stuart
> > ________________________________________
> > From: seam-dev-bounces@...
> [seam-dev-bounces@...]
> On Behalf Of Francisco Jose Peredo [franciscoperedo@...]
> > Sent: Wednesday, 25 November 2009 1:17 AM
> > To: seam-dev@...
> > Cc: weld-dev@...
> > Subject: Re: [seam-dev] Mercurial vs GIT
> >
> > I have not tried GIT, but from what I have read it is
> pretty complicated
> > to learn to use...
> > OTOH I have tried Mercurial, which is also
> distributed, and found it
> > confortable... apparently the
> > way it deals with its distribute nature is easier for
> subversion users
> > to understand...
> > AFAIK Netbeans source code is in Mercurial, also
> OpenJDK... So it seems
> > to work
> > well with large code bases... and there are plugins
> for Netbeans,
> > Eclipse and the Tortoise Hg
> > project is advanced and usable...
> > Google Code offers free Mercurial hosting...
> > Why not Mercurial?
> >
> >
> >
> > Pete Muir escribió:
> > > A quick item we discussed at the f2f meeting was
> whether to switch to
> > > GIT for our SCM, rather than SVN.
> > >
> > > This would give us a IMO a system well suited to
> our distribued dev
> > > model, it would also make it much easier for
> others to sandbox PEs and
> > > then contribute them back to us.
> > >
> > > The proposal is to use Github to host.
> > >
> > > The team members at devoxx were in favour, but
> what do others think?
> > >
> > > Pete
> > >
> > > --
> > > Pete Muir
> > > http://in.relation.to/Bloggers/Pete
> > > _______________________________________________
> > > seam-dev mailing list
> > > seam-dev@...
> > > https://lists.jboss.org/mailman/listinfo/seam-dev
> > >
> > >
> >
> >
> > --
> > Dirección Informática de Servicios Financieros
> > Dirección General de Modernización e Innovación
> Gubernamental
> > Secretaría de Administración y Finanzas
> > Paseo de la Sierra 435 col. Reforma
> > C.P. 86086, Villahermosa, Tabasco.
> > Tel. 52 + 993 + 310 40 00 Ext. 7127
> > http://saf.tabasco.gob.mx/
> >
> > IMPORTANTE: Esta transmisión electrónica, incluyendo
> sus anexos, archivos insertados o "attachments", puede
> constituir información confidencial o reservada, en los
> términos de la Ley de Acceso a la Información Pública del
> Estado de Tabasco, y estar protegida por el derecho
> fundamental a la privacidad. Se prohibe el uso de esta
> información por cualquier persona distinta al receptor
> intencional o previsto. Si usted ha recibibido esta
> transmisión electrónica por error, por favor responda
> inmediatamente al emisor y borre esta información de su
> sistema. El uso, diseminación, distribución o
> reproducción de esta transmisión electrónica por
> receptores no intencionados o no previstos por el emisor, no
> está autorizada y puede considerarse ilícita en los
> términos de la legislación penal y civil vigente.
> >
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev@...
> > https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev@...
> > https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> >
> >
> > --
> > Daniel Roth
> > M.Sc. Computer Science
> > daniel@...
> > www.danielroth.se
> > +46 736 36 29 46
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev@...
> > https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>

__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.
http://mail.yahoo.com

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Mercurial vs GIT

2009-11-25T04:43:58Z

I can certainly see that a DVCS might not be a good fit for closed source / in company software development. All the work an engineer on the project does is likely to make it into the project at some point (even if heavily refactored), and they are unlikely to want to share it with many other people before it goes into VCS.

However if you consider Seam, then there are often cases where someone is maintaining a patch for months or even years against trunk which they want to easily share with other users. As we move towards to a more modular approach, this becomes even more apparent - you might want to develop a module outside the Seam master, and share it with the community. At some point we might add it to the master. I believe a DVCS is ideally suited to this.

Pete

On 24 Nov 2009, at 22:22, Daniel Roth wrote:

> 1) I have not tried GIT...
> 2) Comparing Mercurial and SVN, for me, is like comparing an nightmare and ease of use.
>
> There is a Mercurial plugin for Eclipse, but it's really no good. We experienced some bugs at work with it (DivideByZero), submitted a patch but... Still nothing has happened... I've tried meld, kdiff3 and the tortoise thingy for windows, but still I always end up with command line because things don't work. Also there is really no good way of branching. Named branches is a MESS so even the hg team thinks it's better to crete to different clones and then manually merge them. (See their manual)
>
> One other thing I'd like to say is that having a distr. repo may sound really fancy, but it's rarely needed. Although being spread over different offices all over the world, that feature is never really needed at my work. And the really really really few times it is, you could just as well make an ordinary patch, and give it to the other person. However, there have been many times when hours has been wasted when trying to resolve issues when two people have worked in our root repo at the same time.
>
> Just my 10 öre...
>
> Daniel
>
>
> On Tue, Nov 24, 2009 at 11:00 PM, Stuart Douglas <stuart@...> wrote:
> As I understand it GIT support on windows is not good, and also just having a quick google around it looks like the tooling support is not very mature either. Also the commands are different to subversions commands so there is quite a steep learning curve.
> I like bazaar, it uses the same commands as subversion, works on all platforms and has eclipse and windows support. It also has launchpad, which is the bzr equivalent of github.
>
> Stuart
> ________________________________________
> From: seam-dev-bounces@... [seam-dev-bounces@...] On Behalf Of Francisco Jose Peredo [franciscoperedo@...]
> Sent: Wednesday, 25 November 2009 1:17 AM
> To: seam-dev@...
> Cc: weld-dev@...
> Subject: Re: [seam-dev] Mercurial vs GIT
>
> I have not tried GIT, but from what I have read it is pretty complicated
> to learn to use...
> OTOH I have tried Mercurial, which is also distributed, and found it
> confortable... apparently the
> way it deals with its distribute nature is easier for subversion users
> to understand...
> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it seems
> to work
> well with large code bases... and there are plugins for Netbeans,
> Eclipse and the Tortoise Hg
> project is advanced and usable...
> Google Code offers free Mercurial hosting...
> Why not Mercurial?
>
>
>
> Pete Muir escribió:
> > A quick item we discussed at the f2f meeting was whether to switch to
> > GIT for our SCM, rather than SVN.
> >
> > This would give us a IMO a system well suited to our distribued dev
> > model, it would also make it much easier for others to sandbox PEs and
> > then contribute them back to us.
> >
> > The proposal is to use Github to host.
> >
> > The team members at devoxx were in favour, but what do others think?
> >
> > Pete
> >
> > --
> > Pete Muir
> > http://in.relation.to/Bloggers/Pete
> > _______________________________________________
> > seam-dev mailing list
> > seam-dev@...
> > https://lists.jboss.org/mailman/listinfo/seam-dev
> >
> >
>
>
> --
> Dirección Informática de Servicios Financieros
> Dirección General de Modernización e Innovación Gubernamental
> Secretaría de Administración y Finanzas
> Paseo de la Sierra 435 col. Reforma
> C.P. 86086, Villahermosa, Tabasco.
> Tel. 52 + 993 + 310 40 00 Ext. 7127
> http://saf.tabasco.gob.mx/
>
> IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
>
> --
> Daniel Roth
> M.Sc. Computer Science
> daniel@...
> www.danielroth.se
> +46 736 36 29 46
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-25T04:30:43Z

FYI

Jira Git Support: https://plugins.atlassian.com/plugin/details/4984

FishEye Git Support: http://jira.atlassian.com/browse/FE-337

2009/11/25 Pete Muir <pmuir@...>

On 24 Nov 2009, at 18:34, lightguard.jp@gmail.com wrote:
> I've looked at both and the one major difference is the branching model in hg. Many people have coined it "broken" but those may all be in the past. As far as tooling goes I think you'll find decent support either way. Would Fisheye and JIRA still be used or would the services of the host be used instead? That may also be something to consider.

We would continue to use JIRA. I guess we wouldn't use fisheye anymore.

_______________________________________________
weld-dev mailing list
weld-dev@...
https://lists.jboss.org/mailman/listinfo/weld-dev

--
--
Aslak Knutsen; +47 952 38 791; fax +47 22 33 60 24
Kongens gate 14; Boks 805 Sentrum, 0104 Oslo;
http://www.conduct.no; mailto:aslak@...

Conduct AS - Professional Open Source Services
- Red Hat/JBoss Premier System Integrator
- Pentaho Preferred Integration Partner
- Atlassian Technology Partner

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-25T04:17:23Z

On 24 Nov 2009, at 18:34, lightguard.jp@... wrote:
> I've looked at both and the one major difference is the branching model in hg. Many people have coined it "broken" but those may all be in the past. As far as tooling goes I think you'll find decent support either way. Would Fisheye and JIRA still be used or would the services of the host be used instead? That may also be something to consider.

We would continue to use JIRA. I guess we wouldn't use fisheye anymore.
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-25T03:49:14Z

Hi,
if you like to quote Linux, remember the linux kernel is not using
Bitkeeper anymore, they developed GIT with the requirements of the
kernel source control in mind, they use GIT since some time now.
I don't mean to say it's easy nor general purpose, but for sure it's
being well tested by all kernel developers.

regards,
Sanne

2009/11/25 Arbi Sookazian <asookazian@...>:

> http://www.youtube.com/watch?v=4XpnKHJAok8
>
> Linus Torvalds: "If you like using CVS, you should be in a mental
> institution, somewhere else."
>
> @ 08:30
>
> he likes bitkeeper (commercial) and doesn't like SVN.
>
> On Tue, Nov 24, 2009 at 7:25 PM, Boscarine, Steven
> <Steven.Boscarine@...> wrote:
>>
>> +1 vote for Git
>> I've seen a lot of Git momentum locally.
>>
>> ________________________________________
>> From: weld-dev-bounces@... [weld-dev-bounces@...]
>> On Behalf Of Mark Struberg [struberg@...]
>> Sent: Tuesday, November 24, 2009 1:07 PM
>> To: Jason Lee; Pete Muir
>> Cc: Francisco Jose Peredo; seam-dev@...;
>> weld-dev@...
>> Subject: Re: [weld-dev] [seam-dev] Mercurial vs GIT
>>
>> Hi!
>>
>> While both hg and Git provide pretty the same functionality, there is a
>> huge difference in the supported tooling set.
>>
>> .) maven will (most probably) move to Git. Most of maven folks already use
>> Git internally.
>> .) there is a native Java Git client called JGit. There will be a jgit
>> provider for maven in the not too distant future. Thus we don't need to care
>> about OS issues!
>> .) hg is written in Python. Windows users will need to install Python. For
>> git you don't have to install anything. The JGit jar will simply be a
>> dependency of maven-scm.
>> .) There are native plugins for Eclipse (written by Shawn Spearce),
>> NetBeans (written by Jonas Fonesca) and Idea (provided by Intellij).
>>
>> And the main reason for my personally: Im an old bearded Unix guy :)
>>
>> Btw, there is also a migration scenario from SVN to Git. It is even
>> possible to let Git play being a SVN server, so you can access a Git repo
>> with a SVN client.
>>
>> LieGrue,
>> strub
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev@...
>> https://lists.jboss.org/mailman/listinfo/weld-dev
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev@...
> https://lists.jboss.org/mailman/listinfo/weld-dev
>

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T20:29:11Z

http://www.youtube.com/watch?v=4XpnKHJAok8

Linus Torvalds: "If you like using CVS, you should be in a mental institution, somewhere else."

@ 08:30

he likes bitkeeper (commercial) and doesn't like SVN.

On Tue, Nov 24, 2009 at 7:25 PM, Boscarine, Steven <Steven.Boscarine@...> wrote:

+1 vote for Git
I've seen a lot of Git momentum locally.

________________________________________
From: weld-dev-bounces@... [weld-dev-bounces@...] On Behalf Of Mark Struberg [struberg@...]
Sent: Tuesday, November 24, 2009 1:07 PM
To: Jason Lee; Pete Muir
Cc: Francisco Jose Peredo; seam-dev@...; weld-dev@...
Subject: Re: [weld-dev] [seam-dev] Mercurial vs GIT

Hi!

While both hg and Git provide pretty the same functionality, there is a huge difference in the supported tooling set.

.) maven will (most probably) move to Git. Most of maven folks already use Git internally.
.) there is a native Java Git client called JGit. There will be a jgit provider for maven in the not too distant future. Thus we don't need to care about OS issues!
.) hg is written in Python. Windows users will need to install Python. For git you don't have to install anything. The JGit jar will simply be a dependency of maven-scm.
.) There are native plugins for Eclipse (written by Shawn Spearce), NetBeans (written by Jonas Fonesca) and Idea (provided by Intellij).

And the main reason for my personally: Im an old bearded Unix guy :)

Btw, there is also a migration scenario from SVN to Git. It is even possible to let Git play being a SVN server, so you can access a Git repo with a SVN client.

LieGrue,
strub

_______________________________________________
weld-dev mailing list
weld-dev@...
https://lists.jboss.org/mailman/listinfo/weld-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T19:25:08Z

+1 vote for Git
I've seen a lot of Git momentum locally.

________________________________________
From: weld-dev-bounces@... [weld-dev-bounces@...] On Behalf Of Mark Struberg [struberg@...]
Sent: Tuesday, November 24, 2009 1:07 PM
To: Jason Lee; Pete Muir
Cc: Francisco Jose Peredo; seam-dev@...; weld-dev@...
Subject: Re: [weld-dev] [seam-dev] Mercurial vs GIT

Hi!

While both hg and Git provide pretty the same functionality, there is a huge difference in the supported tooling set.

.) maven will (most probably) move to Git. Most of maven folks already use Git internally.
.) there is a native Java Git client called JGit. There will be a jgit provider for maven in the not too distant future. Thus we don't need to care about OS issues!
.) hg is written in Python. Windows users will need to install Python. For git you don't have to install anything. The JGit jar will simply be a dependency of maven-scm.
.) There are native plugins for Eclipse (written by Shawn Spearce), NetBeans (written by Jonas Fonesca) and Idea (provided by Intellij).

And the main reason for my personally: Im an old bearded Unix guy :)

Btw, there is also a migration scenario from SVN to Git. It is even possible to let Git play being a SVN server, so you can access a Git repo with a SVN client.

LieGrue,
strub
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Mercurial vs GIT

2009-11-24T14:27:10Z

Forgot to say. There is a hg plugin for JIRA, but it's not really maintained ...

http://confluence.atlassian.com/display/JIRAEXT/Mercurial+Plugin

On Tue, Nov 24, 2009 at 11:22 PM, Daniel Roth <daniel@...> wrote:

1) I have not tried GIT...
2) Comparing Mercurial and SVN, for me, is like comparing an nightmare and ease of use.

There is a Mercurial plugin for Eclipse, but it's really no good. We experienced some bugs at work with it (DivideByZero), submitted a patch but... Still nothing has happened... I've tried meld, kdiff3 and the tortoise thingy for windows, but still I always end up with command line because things don't work. Also there is really no good way of branching. Named branches is a MESS so even the hg team thinks it's better to crete to different clones and then manually merge them. (See their manual)

One other thing I'd like to say is that having a distr. repo may sound really fancy, but it's rarely needed. Although being spread over different offices all over the world, that feature is never really needed at my work. And the really really really few times it is, you could just as well make an ordinary patch, and give it to the other person. However, there have been many times when hours has been wasted when trying to resolve issues when two people have worked in our root repo at the same time.

Just my 10 öre...

Daniel

On Tue, Nov 24, 2009 at 11:00 PM, Stuart Douglas <stuart@...> wrote:

As I understand it GIT support on windows is not good, and also just having a quick google around it looks like the tooling support is not very mature either. Also the commands are different to subversions commands so there is quite a steep learning curve.
I like bazaar, it uses the same commands as subversion, works on all platforms and has eclipse and windows support. It also has launchpad, which is the bzr equivalent of github.

Stuart
________________________________________
From: seam-dev-bounces@... [seam-dev-bounces@...] On Behalf Of Francisco Jose Peredo [franciscoperedo@...]
Sent: Wednesday, 25 November 2009 1:17 AM
To: seam-dev@...
Cc: weld-dev@...
Subject: Re: [seam-dev] Mercurial vs GIT

I have not tried GIT, but from what I have read it is pretty complicated
to learn to use...
OTOH I have tried Mercurial, which is also distributed, and found it
confortable... apparently the
way it deals with its distribute nature is easier for subversion users
to understand...
AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it seems
to work
well with large code bases... and there are plugins for Netbeans,
Eclipse and the Tortoise Hg
project is advanced and usable...
Google Code offers free Mercurial hosting...
Why not Mercurial?

Pete Muir escribió:
> A quick item we discussed at the f2f meeting was whether to switch to
> GIT for our SCM, rather than SVN.
>
> This would give us a IMO a system well suited to our distribued dev
> model, it would also make it much easier for others to sandbox PEs and
> then contribute them back to us.
>
> The proposal is to use Github to host.
>
> The team members at devoxx were in favour, but what do others think?
>
> Pete
>
> --
> Pete Muir
> http://in.relation.to/Bloggers/Pete
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>

--
Dirección Informática de Servicios Financieros
Dirección General de Modernización e Innovación Gubernamental
Secretaría de Administración y Finanzas
Paseo de la Sierra 435 col. Reforma
C.P. 86086, Villahermosa, Tabasco.
Tel. 52 + 993 + 310 40 00 Ext. 7127
http://saf.tabasco.gob.mx/

IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

--
Daniel Roth
M.Sc. Computer Science
daniel@...
www.danielroth.se
+46 736 36 29 46

--
Daniel Roth
M.Sc. Computer Science
daniel@...
www.danielroth.se
+46 736 36 29 46

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Mercurial vs GIT

2009-11-24T14:22:09Z

1) I have not tried GIT...
2) Comparing Mercurial and SVN, for me, is like comparing an nightmare and ease of use.

There is a Mercurial plugin for Eclipse, but it's really no good. We experienced some bugs at work with it (DivideByZero), submitted a patch but... Still nothing has happened... I've tried meld, kdiff3 and the tortoise thingy for windows, but still I always end up with command line because things don't work. Also there is really no good way of branching. Named branches is a MESS so even the hg team thinks it's better to crete to different clones and then manually merge them. (See their manual)

One other thing I'd like to say is that having a distr. repo may sound really fancy, but it's rarely needed. Although being spread over different offices all over the world, that feature is never really needed at my work. And the really really really few times it is, you could just as well make an ordinary patch, and give it to the other person. However, there have been many times when hours has been wasted when trying to resolve issues when two people have worked in our root repo at the same time.

Just my 10 öre...

Daniel

On Tue, Nov 24, 2009 at 11:00 PM, Stuart Douglas <stuart@...> wrote:

As I understand it GIT support on windows is not good, and also just having a quick google around it looks like the tooling support is not very mature either. Also the commands are different to subversions commands so there is quite a steep learning curve.
I like bazaar, it uses the same commands as subversion, works on all platforms and has eclipse and windows support. It also has launchpad, which is the bzr equivalent of github.

Stuart
________________________________________
From: seam-dev-bounces@... [seam-dev-bounces@...] On Behalf Of Francisco Jose Peredo [franciscoperedo@...]
Sent: Wednesday, 25 November 2009 1:17 AM
To: seam-dev@...
Cc: weld-dev@...
Subject: Re: [seam-dev] Mercurial vs GIT

I have not tried GIT, but from what I have read it is pretty complicated
to learn to use...
OTOH I have tried Mercurial, which is also distributed, and found it
confortable... apparently the
way it deals with its distribute nature is easier for subversion users
to understand...
AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it seems
to work
well with large code bases... and there are plugins for Netbeans,
Eclipse and the Tortoise Hg
project is advanced and usable...
Google Code offers free Mercurial hosting...
Why not Mercurial?

Pete Muir escribió:
> A quick item we discussed at the f2f meeting was whether to switch to
> GIT for our SCM, rather than SVN.
>
> This would give us a IMO a system well suited to our distribued dev
> model, it would also make it much easier for others to sandbox PEs and
> then contribute them back to us.
>
> The proposal is to use Github to host.
>
> The team members at devoxx were in favour, but what do others think?
>
> Pete
>
> --
> Pete Muir
> http://in.relation.to/Bloggers/Pete
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>

--
Dirección Informática de Servicios Financieros
Dirección General de Modernización e Innovación Gubernamental
Secretaría de Administración y Finanzas
Paseo de la Sierra 435 col. Reforma
C.P. 86086, Villahermosa, Tabasco.
Tel. 52 + 993 + 310 40 00 Ext. 7127
http://saf.tabasco.gob.mx/

IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Mercurial vs GIT vs Bazaar

2009-11-24T14:13:52Z

Yes, TortoiseBzr. It also has native subversion support, you can use it as a client for existing subversion repositories.

Stuart
________________________________________
From: seam-dev-bounces@... [seam-dev-bounces@...] On Behalf Of Francisco Jose Peredo [franciscoperedo@...]
Sent: Wednesday, 25 November 2009 9:07 AM
To: seam-dev@...
Subject: Re: [seam-dev] Mercurial vs GIT vs Bazaar

Stuart Douglas escribió:

As I understand it GIT support on windows is not good, and also just having a quick google around it looks like the tooling support is not very mature either. Also the commands are different to subversions commands so there is quite a steep learning curve.
I like bazaar, it uses the same commands as subversion, works on all platforms and has eclipse and windows support. It also has launchpad, which is the bzr equivalent of github.

Does Bazaar it have something like TortoiseHq or TortoiseGit ?

Stuart
________________________________________
From: seam-dev-bounces@...<mailto:seam-dev-bounces@...> [seam-dev-bounces@...<mailto:seam-dev-bounces@...>] On Behalf Of Francisco Jose Peredo [franciscoperedo@...<mailto:franciscoperedo@...>]
Sent: Wednesday, 25 November 2009 1:17 AM
To: seam-dev@...<mailto:seam-dev@...>
Cc: weld-dev@...<mailto:weld-dev@...>
Subject: Re: [seam-dev] Mercurial vs GIT

I have not tried GIT, but from what I have read it is pretty complicated
to learn to use...
OTOH I have tried Mercurial, which is also distributed, and found it
confortable... apparently the
way it deals with its distribute nature is easier for subversion users
to understand...
AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it seems
to work
well with large code bases... and there are plugins for Netbeans,
Eclipse and the Tortoise Hg
project is advanced and usable...
Google Code offers free Mercurial hosting...
Why not Mercurial?

Pete Muir escribió:

A quick item we discussed at the f2f meeting was whether to switch to
GIT for our SCM, rather than SVN.

This would give us a IMO a system well suited to our distribued dev
model, it would also make it much easier for others to sandbox PEs and
then contribute them back to us.

The proposal is to use Github to host.

The team members at devoxx were in favour, but what do others think?

Pete

--
Pete Muir
http://in.relation.to/Bloggers/Pete
_______________________________________________
seam-dev mailing list
seam-dev@...<mailto:seam-dev@...>
https://lists.jboss.org/mailman/listinfo/seam-dev

--
Dirección Informática de Servicios Financieros
Dirección General de Modernización e Innovación Gubernamental
Secretaría de Administración y Finanzas
Paseo de la Sierra 435 col. Reforma
C.P. 86086, Villahermosa, Tabasco.
Tel. 52 + 993 + 310 40 00 Ext. 7127
http://saf.tabasco.gob.mx/

IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.

_______________________________________________
seam-dev mailing list
seam-dev@...<mailto:seam-dev@...>
https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...<mailto:seam-dev@...>
https://lists.jboss.org/mailman/listinfo/seam-dev

--
Dirección Informática de Servicios Financieros
Dirección General de Modernización e Innovación Gubernamental
Secretaría de Administración y Finanzas
Paseo de la Sierra 435 col. Reforma
C.P. 86086, Villahermosa, Tabasco.
Tel. 52 + 993 + 310 40 00 Ext. 7127
http://saf.tabasco.gob.mx/

IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Mercurial vs GIT vs Bazaar

2009-11-24T14:07:50Z

Stuart Douglas escribió:

As I understand it GIT support on windows is not good, and also just having a quick google around it looks like the tooling support is not very mature either. Also the commands are different to subversions commands so there is quite a steep learning curve. 
I like bazaar, it uses the same commands as subversion, works on all platforms and has eclipse and windows support. It also has launchpad, which is the bzr equivalent of github.

Does Bazaar it have something like TortoiseHq or TortoiseGit ?

Stuart
________________________________________
From: seam-dev-bounces@... [seam-dev-bounces@...] On Behalf Of Francisco Jose Peredo [franciscoperedo@...]
Sent: Wednesday, 25 November 2009 1:17 AM
To: seam-dev@...
Cc: weld-dev@...
Subject: Re: [seam-dev] Mercurial vs GIT

I have not tried GIT, but from what I have read it is pretty complicated
to learn to use...
OTOH I have tried Mercurial, which is also distributed, and found it
confortable... apparently the
way it deals with its distribute nature is easier for subversion users
to understand...
AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it seems
to work
well with large code bases... and there are plugins for Netbeans,
Eclipse and the Tortoise Hg
project is advanced and usable...
Google Code offers free Mercurial hosting...
Why not Mercurial?

Pete Muir escribió:

A quick item we discussed at the f2f meeting was whether to switch to
GIT for our SCM, rather than SVN.

This would give us a IMO a system well suited to our distribued dev
model, it would also make it much easier for others to sandbox PEs and
then contribute them back to us.

The proposal is to use Github to host.

The team members at devoxx were in favour, but what do others think?

Pete

--
Pete Muir
http://in.relation.to/Bloggers/Pete
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev



--
Dirección Informática de Servicios Financieros
Dirección General de Modernización e Innovación Gubernamental
Secretaría de Administración y Finanzas
Paseo de la Sierra 435 col. Reforma
C.P. 86086, Villahermosa, Tabasco.
Tel. 52 + 993 + 310 40 00 Ext. 7127
http://saf.tabasco.gob.mx/

IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

-- 
Dirección Informática de Servicios Financieros
Dirección General de Modernización e Innovación Gubernamental
Secretaría de Administración y Finanzas
Paseo de la Sierra 435 col. Reforma
C.P. 86086, Villahermosa, Tabasco.
Tel. 52 + 993 + 310 40 00 Ext. 7127
http://saf.tabasco.gob.mx/

IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Mercurial vs GIT

2009-11-24T14:00:39Z

As I understand it GIT support on windows is not good, and also just having a quick google around it looks like the tooling support is not very mature either. Also the commands are different to subversions commands so there is quite a steep learning curve.
I like bazaar, it uses the same commands as subversion, works on all platforms and has eclipse and windows support. It also has launchpad, which is the bzr equivalent of github.

Stuart
________________________________________
From: seam-dev-bounces@... [seam-dev-bounces@...] On Behalf Of Francisco Jose Peredo [franciscoperedo@...]
Sent: Wednesday, 25 November 2009 1:17 AM
To: seam-dev@...
Cc: weld-dev@...
Subject: Re: [seam-dev] Mercurial vs GIT

I have not tried GIT, but from what I have read it is pretty complicated
to learn to use...
OTOH I have tried Mercurial, which is also distributed, and found it
confortable... apparently the
way it deals with its distribute nature is easier for subversion users
to understand...
AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it seems
to work
well with large code bases... and there are plugins for Netbeans,
Eclipse and the Tortoise Hg
project is advanced and usable...
Google Code offers free Mercurial hosting...
Why not Mercurial?

Pete Muir escribió:

> A quick item we discussed at the f2f meeting was whether to switch to
> GIT for our SCM, rather than SVN.
>
> This would give us a IMO a system well suited to our distribued dev
> model, it would also make it much easier for others to sandbox PEs and
> then contribute them back to us.
>
> The proposal is to use Github to host.
>
> The team members at devoxx were in favour, but what do others think?
>
> Pete
>
> --
> Pete Muir
> http://in.relation.to/Bloggers/Pete
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>

--
Dirección Informática de Servicios Financieros
Dirección General de Modernización e Innovación Gubernamental
Secretaría de Administración y Finanzas
Paseo de la Sierra 435 col. Reforma
C.P. 86086, Villahermosa, Tabasco.
Tel. 52 + 993 + 310 40 00 Ext. 7127
http://saf.tabasco.gob.mx/

IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Seam 3 examples release cycle

2009-11-24T12:13:51Z

Yep, this parallels the problem with docs, which we decided belong in the module.

It's possible we could still have broader examples that go into a shared examples directory and only update on a full Seam release, then have local examples for modules that can be updated more often. Actually, this option is good because we can verify backward compatibility in the general examples while still having the flexibility to demonstrate more specific features in the module-local examples.

-Dan

On Tue, Nov 24, 2009 at 12:00 PM, Shane Bryzak <sbryzak@...> wrote:

I can foresee a potential issue with the release cycle for examples,
especially if we go down the path that we discussed during the meeting
where we consolidate examples into more complex apps that demonstrate
multiple Seam features. For example, let's say that we release a
production version of Seam 3.0.0 that contains (among other things):

Seam Security 3.0.0
Seam examples 3.0.0

Now let's say I add some new feature into security and decide to do a
release of Seam Security 3.0.1. If I have accordingly updated the
security examples with the new feature, does that mean that I need to do
a simultaneous release of Seam examples 3.0.1? Also, what if other
sub-project leads have in the meantime added new features to their
modules and their examples are in an incomplete state? As you can see
this becomes a problem.

One possible solution is to remove the examples branch altogether and
include the examples within the related module instead. This prevents
us though from creating multi-feature examples, as they will be bound to
the sub-project lifecycle. One other option is to only release
examples during a major Seam release, however this is less desirable in
the case where we release a module with complex new features that really
need to be demonstrated.

IMHO out of these two options the first one seems the lesser of two
evils, however I'm wondering what you guys think.
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T11:33:02Z

On Nov 24, 2009, at 9:41 AM, Dan Allen wrote:

We all agreed to use git over svn, but to be honest, mercurial wasn't considered. I've used both as well. But in my short exposure, I really didn't see a difference. What makes git so attractive is that github.com explains so well how to use it.

I supposed we could consider mercurcial if there was a nice out of the box hosting option like github.com. If not, git will likely win because of that.

I've done projects with both, and I think git, once you get over the learning curve, is much easier to work with and get things done. With mercurial, I always feel like I am fighting the system to make it work. With git, the only struggle is learning the right commands, and then once you do everything just works perfectly. I think the git staging model is really nice, and I git stash can't be beat. If you are working with a lot of branches or want to work on a lot of separate issues at one time (develop features, fixes or support issues separately in parallel) git is so much more pleasant. Mercurial isn't bad by any means, but git just gets more things right, IMHO.

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T10:34:21Z

On Tue, Nov 24, 2009 at 09:07, Ashish Tonse <ashish.tonse@...> wrote:

> +1 for git/github.
> Echoing what others have said, I think github is ultimately what makes git
> the most attractive, all things considered. Github makes it incredibly easy
> to fork and propose pushes.
> Google code seems to be better suited for smaller projects, even though
> google uses it for their even larger projects. For an open source project
> with outside contributors, it's essential to have a good "hub" - and github
> serves that purpose extremely well.
> Just my 15 cents (inflation).
> Ashish
> PS: I'm tempted to further splinter this debate by proposing Bazaar :) (with
> Ubuntu's launchpad)
>
> On Tue, Nov 24, 2009 at 10:49 AM, Francisco Jose Peredo
> <franciscoperedo@...> wrote:
>>
>> A nice out of the box hosting option for Mercurial? I think I mentioned
>> GoogleCode... or there are many options to choose:
>>
>> http://mercurial.selenic.com/wiki/MercurialHosting
>>
>> Dan Allen escribió:
>>
>> We all agreed to use git over svn, but to be honest, mercurial wasn't
>> considered. I've used both as well. But in my short exposure, I really
>> didn't see a difference. What makes git so attractive is that github.com
>> explains so well how to use it.
>>
>> I supposed we could consider mercurcial if there was a nice out of the box
>> hosting option like github.com. If not, git will likely win because of that.
>>
>> -Dan
>>
>> On Tue, Nov 24, 2009 at 9:33 AM, Pete Muir <pmuir@...> wrote:
>>>
>>> I have seen a reasonable amount of GIT, and have liked what I saw, as
>>> have most of the other core team who have spoken up on this issue.
>>>
>>> Sell us Mercurial :-)
>>>
>>> On 24 Nov 2009, at 14:22, Francisco Jose Peredo wrote:
>>>
>>> > An interesting comparision?:
>>> >
>>> > http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
>>> >
>>> >
>>> > Francisco Jose Peredo escribió:
>>> >> I have not tried GIT, but from what I have read it is pretty
>>> >> complicated to learn to use...
>>> >> OTOH I have tried Mercurial, which is also distributed, and found it
>>> >> confortable... apparently the
>>> >> way it deals with its distribute nature is easier for subversion users
>>> >> to understand...
>>> >> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it
>>> >> seems to work
>>> >> well with large code bases... and there are plugins for Netbeans,
>>> >> Eclipse and the Tortoise Hg
>>> >> project is advanced and usable...
>>> >> Google Code offers free Mercurial hosting...
>>> >> Why not Mercurial?
>>> >>
>>> >>
>>> >>
>>> >> Pete Muir escribió:
>>> >>> A quick item we discussed at the f2f meeting was whether to switch to
>>> >>> GIT for our SCM, rather than SVN.
>>> >>>
>>> >>> This would give us a IMO a system well suited to our distribued dev
>>> >>> model, it would also make it much easier for others to sandbox PEs
>>> >>> and
>>> >>> then contribute them back to us.
>>> >>>
>>> >>> The proposal is to use Github to host.
>>> >>>
>>> >>> The team members at devoxx were in favour, but what do others think?
>>> >>>
>>> >>> Pete
>>> >>>
>>> >>> --
>>> >>> Pete Muir
>>> >>> http://in.relation.to/Bloggers/Pete
>>> >>> _______________________________________________
>>> >>> seam-dev mailing list
>>> >>> seam-dev@...
>>> >>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>> >>>
>>> >>>
>>> >>
>>> >>
>>> >
>>> >
>>> > --
>>> > Dirección Informática de Servicios Financieros
>>> > Dirección General de Modernización e Innovación Gubernamental
>>> > Secretaría de Administración y Finanzas
>>> > Paseo de la Sierra 435 col. Reforma
>>> > C.P. 86086, Villahermosa, Tabasco.
>>> > Tel. 52 + 993 + 310 40 00 Ext. 7127
>>> > http://saf.tabasco.gob.mx/
>>> >
>>> > IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos,
>>> > archivos insertados o "attachments", puede constituir información
>>> > confidencial o reservada, en los términos de la Ley de Acceso a la
>>> > Información Pública del Estado de Tabasco, y estar protegida por el derecho
>>> > fundamental a la privacidad. Se prohibe el uso de esta información por
>>> > cualquier persona distinta al receptor intencional o previsto. Si usted ha
>>> > recibibido esta transmisión electrónica por error, por favor responda
>>> > inmediatamente al emisor y borre esta información de su sistema. El uso,
>>> > diseminación, distribución o reproducción de esta transmisión electrónica
>>> > por receptores no intencionados o no previstos por el emisor, no está
>>> > autorizada y puede considerarse ilícita en los términos de la legislación
>>> > penal y civil vigente.
>>> >
>>> > _______________________________________________
>>> > seam-dev mailing list
>>> > seam-dev@...
>>> > https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>> _______________________________________________
>>> weld-dev mailing list
>>> weld-dev@...
>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>
>>
>>
>> --
>> Dan Allen
>> Senior Software Engineer, Red Hat | Author of Seam in Action
>> Registered Linux User #231597
>>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>> http://www.google.com/profiles/dan.j.allen
>>
>>
>> --
>> Dirección Informática de Servicios Financieros
>> Dirección General de Modernización e Innovación Gubernamental
>> Secretaría de Administración y Finanzas
>> Paseo de la Sierra 435 col. Reforma
>> C.P. 86086, Villahermosa, Tabasco.
>> Tel. 52 + 993 + 310 40 00 Ext. 7127
>> http://saf.tabasco.gob.mx/
>>
>> IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos
>> insertados o "attachments", puede constituir información confidencial o
>> reservada, en los términos de la Ley de Acceso a la Información Pública del
>> Estado de Tabasco, y estar protegida por el derecho fundamental a la
>> privacidad. Se prohibe el uso de esta información por cualquier persona
>> distinta al receptor intencional o previsto. Si usted ha recibibido esta
>> transmisión electrónica por error, por favor responda inmediatamente al
>> emisor y borre esta información de su sistema. El uso, diseminación,
>> distribución o reproducción de esta transmisión electrónica por receptores
>> no intencionados o no previstos por el emisor, no está autorizada y puede
>> considerarse ilícita en los términos de la legislación penal y civil
>> vigente.
>>
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>

I've looked at both and the one major difference is the branching model in hg. Many people have coined it "broken" but those may all be in the past. As far as tooling goes I think you'll find decent support either way. Would Fisheye and JIRA still be used or would the services of the host be used instead? That may also be something to consider.

--
Jason Porter
Real Programmers think better when playing Adventure or Rogue.

PGP key id: 926CCFF5
PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5
PGP key available at: keyserver.net, pgp.mit.edu

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

signature.asc (285 bytes) Download Attachment

Re: [weld-dev] GIT

2009-11-24T10:24:26Z

On Tue, Nov 24, 2009 at 05:42, Dan Allen <dan.j.allen@...> wrote:

> On Sat, Nov 21, 2009 at 10:50 AM, Pete Muir <pmuir@...> wrote:
>>
>> On 21 Nov 2009, at 14:15, Steven Boscarine wrote:
>>
>> > Works for me, personally.
>> >
>> > As an outsider, it's obviously more friendly for non-JBoss employees
>> > like me to contribute. I am still waiting on someone to tag those Weld
>> > Maven archetypes I submitted so I can commit to trunk for review without
>> > worrying about breaking anything. With git, that wouldn't be an issue.
>>
>> You are welcome to tag whenever you want :-)
>>
>> But I agree, GIT supports distributed development much better.
>
> +1
>
> I think this is amongst the most compelling reasons, perhaps even the most
> compelling. It was so simple for me to get involved with the
> maven-cli-plugin because it was hosted with git, and I want that same
> experience for developers getting involved with Seam and Weld.
>
> -Dan
>
> --
> Dan Allen
> Senior Software Engineer, Red Hat | Author of Seam in Action
> Registered Linux User #231597
>
> http://mojavelinux.com
> http://mojavelinux.com/seaminaction
> http://www.google.com/profiles/dan.j.allen
>
> _______________________________________________
> weld-dev mailing list
> weld-dev@...
> https://lists.jboss.org/mailman/listinfo/weld-dev
>

+1
Moving to Git is a great idea.

--
Jason Porter
Real Programmers think better when playing Adventure or Rogue.

PGP key id: 926CCFF5
PGP fingerprint: 64C2 C078 13A9 5B23 7738 F7E5 1046 C39B 926C CFF5
PGP key available at: keyserver.net, pgp.mit.edu

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

signature.asc (285 bytes) Download Attachment

Re: [weld-dev] Reorg of SVN

2009-11-24T10:14:47Z

I did this for Weld http://www.seamframework.org/Weld/WeldSVNStructure

Comments?

On 24 Nov 2009, at 13:57, Pete Muir wrote:

> All,
>
> I am working through Weld SVN right now, and will then move onto Seam SVN, reorganizing SVN to better fit the module structure we have been discussing here recently. I'll post some links to wiki pages describing the structure once I am done.
>
> Pete
> _______________________________________________
> weld-dev mailing list
> weld-dev@...
> https://lists.jboss.org/mailman/listinfo/weld-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T10:07:30Z

Hi!

While both hg and Git provide pretty the same functionality, there is a huge difference in the supported tooling set.

.) maven will (most probably) move to Git. Most of maven folks already use Git internally.
.) there is a native Java Git client called JGit. There will be a jgit provider for maven in the not too distant future. Thus we don't need to care about OS issues!
.) hg is written in Python. Windows users will need to install Python. For git you don't have to install anything. The JGit jar will simply be a dependency of maven-scm.
.) There are native plugins for Eclipse (written by Shawn Spearce), NetBeans (written by Jonas Fonesca) and Idea (provided by Intellij).

And the main reason for my personally: Im an old bearded Unix guy :)

Btw, there is also a migration scenario from SVN to Git. It is even possible to let Git play being a SVN server, so you can access a Git repo with a SVN client.

LieGrue,
strub

--- Pete Muir <pmuir@...> schrieb am Di, 24.11.2009:

> Von: Pete Muir <pmuir@...>
> Betreff: Re: [weld-dev] [seam-dev] Mercurial vs GIT
> An: "Jason Lee" <jason@...>
> CC: "Francisco Jose Peredo" <franciscoperedo@...>, "seam-dev@..." <seam-dev@...>, "weld-dev@..." <weld-dev@...>
> Datum: Dienstag, 24. November 2009, 17:35
> I also just created a bitbucket
> account, which seems to offer everything that github does.
>
> Francisco's article makes good reading, and especially as
> we are all used to SVN, SVN compatible commands are a good
> idea ;-)
>
> Finally, migration to Mercurial looks possible from SVN,
> and tool support looks fine.
>
> On 24 Nov 2009, at 16:23, Jason Lee wrote:
>
> > Some time ago, I had to decide between git and hg for
> my personal projects. I opted to go with hg because I
> felt the docs were better (http://hgbook.red-bean.com/, for example) and the
> Windows support for hg was much better at the time (luckily,
> that's no longer an issue for me, as I'm not using Windows
> ATM :). For what it's worth, some people at my local
> JUG use git and have complained about the inconsistency
> between one command and another. I can neither confirm
> nor deny, as I've never used git in anger. I am,
> though, quite happy with Mercurial. Also, for what
> it's worth, it's my understanding that GlassFish (in
> addition to NetBeans, OpenJDK, etc) will be moving to hg at
> some point, so there are major projects on both systems.
> >
> > With regard to hosting, I'm using kenai.com for
> Mojarra Scales and FacesTester, and I've been really happy
> with it. I get a nice wiki, hg (or git or svn or cvs),
> and JIRA. I realize there may be concerns with kenai
> of various sorts, so, if that's not an option, bitbucket.org
> is one option for hosting projects. The Mercurial
> maintains a fairly lengthy list here: http://mercurial.selenic.com/wiki/MercurialHosting
> >
> > On Nov 24, 2009, at 9:41 AM, Dan Allen wrote:
> >
> >> We all agreed to use git over svn, but to be
> honest, mercurial wasn't considered. I've used both as well.
> But in my short exposure, I really didn't see a difference.
> What makes git so attractive is that github.com explains so
> well how to use it.
> >>
> >> I supposed we could consider mercurcial if there
> was a nice out of the box hosting option like github.com. If
> not, git will likely win because of that.
> >>
> >> -Dan
> >>
> >> On Tue, Nov 24, 2009 at 9:33 AM, Pete Muir <pmuir@...>
> wrote:
> >> I have seen a reasonable amount of GIT, and have
> liked what I saw, as have most of the other core team who
> have spoken up on this issue.
> >>
> >> Sell us Mercurial :-)
> >>
> >> On 24 Nov 2009, at 14:22, Francisco Jose Peredo
> wrote:
> >>
> >> > An interesting comparision?:
> >> >
> >> > http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
> >> >
> >> >
> >> > Francisco Jose Peredo escribió:
> >> >> I have not tried GIT, but from what I
> have read it is pretty
> >> >> complicated to learn to use...
> >> >> OTOH I have tried Mercurial, which is
> also distributed, and found it
> >> >> confortable... apparently the
> >> >> way it deals with its distribute nature
> is easier for subversion users
> >> >> to understand...
> >> >> AFAIK Netbeans source code is in
> Mercurial, also OpenJDK... So it
> >> >> seems to work
> >> >> well with large code bases... and there
> are plugins for Netbeans,
> >> >> Eclipse and the Tortoise Hg
> >> >> project is advanced and usable...
> >> >> Google Code offers free Mercurial
> hosting...
> >> >> Why not Mercurial?
> >> >>
> >> >>
> >> >>
> >> >> Pete Muir escribió:
> >> >>> A quick item we discussed at the f2f
> meeting was whether to switch to
> >> >>> GIT for our SCM, rather than SVN.
> >> >>>
> >> >>> This would give us a IMO a system
> well suited to our distribued dev
> >> >>> model, it would also make it much
> easier for others to sandbox PEs and
> >> >>> then contribute them back to us.
> >> >>>
> >> >>> The proposal is to use Github to
> host.
> >> >>>
> >> >>> The team members at devoxx were in
> favour, but what do others think?
> >> >>>
> >> >>> Pete
> >> >>>
> >> >>> --
> >> >>> Pete Muir
> >> >>> http://in.relation.to/Bloggers/Pete
> >> >>>
> _______________________________________________
> >> >>> seam-dev mailing list
> >> >>> seam-dev@...
> >> >>> https://lists.jboss.org/mailman/listinfo/seam-dev
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >
> >> >
> >> > --
> >> > Dirección Informática de Servicios
> Financieros
> >> > Dirección General de Modernización e
> Innovación Gubernamental
> >> > Secretaría de Administración y Finanzas
> >> > Paseo de la Sierra 435 col. Reforma
> >> > C.P. 86086, Villahermosa, Tabasco.
> >> > Tel. 52 + 993 + 310 40 00 Ext. 7127
> >> > http://saf.tabasco.gob.mx/
> >> >
> >> > IMPORTANTE: Esta transmisión electrónica,
> incluyendo sus anexos, archivos insertados o "attachments",
> puede constituir información confidencial o reservada, en
> los términos de la Ley de Acceso a la Información Pública
> del Estado de Tabasco, y estar protegida por el derecho
> fundamental a la privacidad. Se prohibe el uso de esta
> información por cualquier persona distinta al receptor
> intencional o previsto. Si usted ha recibibido esta
> transmisión electrónica por error, por favor responda
> inmediatamente al emisor y borre esta información de su
> sistema. El uso, diseminación, distribución o
> reproducción de esta transmisión electrónica por
> receptores no intencionados o no previstos por el emisor, no
> está autorizada y puede considerarse ilícita en los
> términos de la legislación penal y civil vigente.
> >> >
> >> >
> _______________________________________________
> >> > seam-dev mailing list
> >> > seam-dev@...
> >> > https://lists.jboss.org/mailman/listinfo/seam-dev
> >>
> >>
> >> _______________________________________________
> >> weld-dev mailing list
> >> weld-dev@...
> >> https://lists.jboss.org/mailman/listinfo/weld-dev
> >>
> >>
> >>
> >> --
> >> Dan Allen
> >> Senior Software Engineer, Red Hat | Author of Seam
> in Action
> >> Registered Linux User #231597
> >>
> >> http://mojavelinux.com
> >> http://mojavelinux.com/seaminaction
> >> http://www.google.com/profiles/dan.j.allen
> >> _______________________________________________
> >> weld-dev mailing list
> >> weld-dev@...
> >> https://lists.jboss.org/mailman/listinfo/weld-dev
> >
> > Jason Lee, SCJP
> > President, Oklahoma City Java Users Group
> > Senior Java Developer, Sun Microsystems
> > http://blogs.steeplesoft.com
> >
> > _______________________________________________
> > weld-dev mailing list
> > weld-dev@...
> > https://lists.jboss.org/mailman/listinfo/weld-dev
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev@...
> https://lists.jboss.org/mailman/listinfo/weld-dev
>

Seam 3 examples release cycle

2009-11-24T09:00:40Z

I can foresee a potential issue with the release cycle for examples,
especially if we go down the path that we discussed during the meeting
where we consolidate examples into more complex apps that demonstrate
multiple Seam features. For example, let's say that we release a
production version of Seam 3.0.0 that contains (among other things):

Seam Security 3.0.0
Seam examples 3.0.0

Now let's say I add some new feature into security and decide to do a
release of Seam Security 3.0.1. If I have accordingly updated the
security examples with the new feature, does that mean that I need to do
a simultaneous release of Seam examples 3.0.1? Also, what if other
sub-project leads have in the meantime added new features to their
modules and their examples are in an incomplete state? As you can see
this becomes a problem.

One possible solution is to remove the examples branch altogether and
include the examples within the related module instead. This prevents
us though from creating multi-feature examples, as they will be bound to
the sub-project lifecycle. One other option is to only release
examples during a major Seam release, however this is less desirable in
the case where we release a module with complex new features that really
need to be demonstrated.

IMHO out of these two options the first one seems the lesser of two
evils, however I'm wondering what you guys think.
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T08:41:04Z

On Tue, Nov 24, 2009 at 11:35 AM, Pete Muir <pmuir@...> wrote:

I also just created a bitbucket account, which seems to offer everything that github does.

Francisco's article makes good reading, and especially as we are all used to SVN, SVN compatible commands are a good idea ;-)

Finally, migration to Mercurial looks possible from SVN, and tool support looks fine.

No complains here. I'm happy to get this feedback from the community and active users of the tool.

-Dan

Re: [weld-dev] Mercurial vs GIT

2009-11-24T08:35:28Z

I also just created a bitbucket account, which seems to offer everything that github does.

Francisco's article makes good reading, and especially as we are all used to SVN, SVN compatible commands are a good idea ;-)

Finally, migration to Mercurial looks possible from SVN, and tool support looks fine.

On 24 Nov 2009, at 16:23, Jason Lee wrote:

> Some time ago, I had to decide between git and hg for my personal projects. I opted to go with hg because I felt the docs were better (http://hgbook.red-bean.com/, for example) and the Windows support for hg was much better at the time (luckily, that's no longer an issue for me, as I'm not using Windows ATM :). For what it's worth, some people at my local JUG use git and have complained about the inconsistency between one command and another. I can neither confirm nor deny, as I've never used git in anger. I am, though, quite happy with Mercurial. Also, for what it's worth, it's my understanding that GlassFish (in addition to NetBeans, OpenJDK, etc) will be moving to hg at some point, so there are major projects on both systems.
>
> With regard to hosting, I'm using kenai.com for Mojarra Scales and FacesTester, and I've been really happy with it. I get a nice wiki, hg (or git or svn or cvs), and JIRA. I realize there may be concerns with kenai of various sorts, so, if that's not an option, bitbucket.org is one option for hosting projects. The Mercurial maintains a fairly lengthy list here: http://mercurial.selenic.com/wiki/MercurialHosting
>
> On Nov 24, 2009, at 9:41 AM, Dan Allen wrote:
>
>> We all agreed to use git over svn, but to be honest, mercurial wasn't considered. I've used both as well. But in my short exposure, I really didn't see a difference. What makes git so attractive is that github.com explains so well how to use it.
>>
>> I supposed we could consider mercurcial if there was a nice out of the box hosting option like github.com. If not, git will likely win because of that.
>>
>> -Dan
>>
>> On Tue, Nov 24, 2009 at 9:33 AM, Pete Muir <pmuir@...> wrote:
>> I have seen a reasonable amount of GIT, and have liked what I saw, as have most of the other core team who have spoken up on this issue.
>>
>> Sell us Mercurial :-)
>>
>> On 24 Nov 2009, at 14:22, Francisco Jose Peredo wrote:
>>
>> > An interesting comparision?:
>> >
>> > http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
>> >
>> >
>> > Francisco Jose Peredo escribió:
>> >> I have not tried GIT, but from what I have read it is pretty
>> >> complicated to learn to use...
>> >> OTOH I have tried Mercurial, which is also distributed, and found it
>> >> confortable... apparently the
>> >> way it deals with its distribute nature is easier for subversion users
>> >> to understand...
>> >> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it
>> >> seems to work
>> >> well with large code bases... and there are plugins for Netbeans,
>> >> Eclipse and the Tortoise Hg
>> >> project is advanced and usable...
>> >> Google Code offers free Mercurial hosting...
>> >> Why not Mercurial?
>> >>
>> >>
>> >>
>> >> Pete Muir escribió:
>> >>> A quick item we discussed at the f2f meeting was whether to switch to
>> >>> GIT for our SCM, rather than SVN.
>> >>>
>> >>> This would give us a IMO a system well suited to our distribued dev
>> >>> model, it would also make it much easier for others to sandbox PEs and
>> >>> then contribute them back to us.
>> >>>
>> >>> The proposal is to use Github to host.
>> >>>
>> >>> The team members at devoxx were in favour, but what do others think?
>> >>>
>> >>> Pete
>> >>>
>> >>> --
>> >>> Pete Muir
>> >>> http://in.relation.to/Bloggers/Pete
>> >>> _______________________________________________
>> >>> seam-dev mailing list
>> >>> seam-dev@...
>> >>> https://lists.jboss.org/mailman/listinfo/seam-dev
>> >>>
>> >>>
>> >>
>> >>
>> >
>> >
>> > --
>> > Dirección Informática de Servicios Financieros
>> > Dirección General de Modernización e Innovación Gubernamental
>> > Secretaría de Administración y Finanzas
>> > Paseo de la Sierra 435 col. Reforma
>> > C.P. 86086, Villahermosa, Tabasco.
>> > Tel. 52 + 993 + 310 40 00 Ext. 7127
>> > http://saf.tabasco.gob.mx/
>> >
>> > IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.
>> >
>> > _______________________________________________
>> > seam-dev mailing list
>> > seam-dev@...
>> > https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>>
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev@...
>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>
>>
>>
>> --
>> Dan Allen
>> Senior Software Engineer, Red Hat | Author of Seam in Action
>> Registered Linux User #231597
>>
>> http://mojavelinux.com
>> http://mojavelinux.com/seaminaction
>> http://www.google.com/profiles/dan.j.allen
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev@...
>> https://lists.jboss.org/mailman/listinfo/weld-dev
>
> Jason Lee, SCJP
> President, Oklahoma City Java Users Group
> Senior Java Developer, Sun Microsystems
> http://blogs.steeplesoft.com
>
> _______________________________________________
> weld-dev mailing list
> weld-dev@...
> https://lists.jboss.org/mailman/listinfo/weld-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T08:23:55Z

Some time ago, I had to decide between git and hg for my personal projects. I opted to go with hg because I felt the docs were better (http://hgbook.red-bean.com/, for example) and the Windows support for hg was much better at the time (luckily, that's no longer an issue for me, as I'm not using Windows ATM :). For what it's worth, some people at my local JUG use git and have complained about the inconsistency between one command and another. I can neither confirm nor deny, as I've never used git in anger. I am, though, quite happy with Mercurial. Also, for what it's worth, it's my understanding that GlassFish (in addition to NetBeans, OpenJDK, etc) will be moving to hg at some point, so there are major projects on both systems.

With regard to hosting, I'm using kenai.com for Mojarra Scales and FacesTester, and I've been really happy with it. I get a nice wiki, hg (or git or svn or cvs), and JIRA. I realize there may be concerns with kenai of various sorts, so, if that's not an option, bitbucket.org is one option for hosting projects. The Mercurial maintains a fairly lengthy list here: http://mercurial.selenic.com/wiki/MercurialHosting

On Nov 24, 2009, at 9:41 AM, Dan Allen wrote:

We all agreed to use git over svn, but to be honest, mercurial wasn't considered. I've used both as well. But in my short exposure, I really didn't see a difference. What makes git so attractive is that github.com explains so well how to use it.

I supposed we could consider mercurcial if there was a nice out of the box hosting option like github.com. If not, git will likely win because of that.

-Dan

On Tue, Nov 24, 2009 at 9:33 AM, Pete Muir <pmuir@...> wrote:
I have seen a reasonable amount of GIT, and have liked what I saw, as have most of the other core team who have spoken up on this issue.

Sell us Mercurial :-)

On 24 Nov 2009, at 14:22, Francisco Jose Peredo wrote:

> An interesting comparision?:
>
> http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
>
>
> Francisco Jose Peredo escribió:
>> I have not tried GIT, but from what I have read it is pretty
>> complicated to learn to use...
>> OTOH I have tried Mercurial, which is also distributed, and found it
>> confortable... apparently the
>> way it deals with its distribute nature is easier for subversion users
>> to understand...
>> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it
>> seems to work
>> well with large code bases... and there are plugins for Netbeans,
>> Eclipse and the Tortoise Hg
>> project is advanced and usable...
>> Google Code offers free Mercurial hosting...
>> Why not Mercurial?
>>
>>
>>
>> Pete Muir escribió:
>>> A quick item we discussed at the f2f meeting was whether to switch to
>>> GIT for our SCM, rather than SVN.
>>>
>>> This would give us a IMO a system well suited to our distribued dev
>>> model, it would also make it much easier for others to sandbox PEs and
>>> then contribute them back to us.
>>>
>>> The proposal is to use Github to host.
>>>
>>> The team members at devoxx were in favour, but what do others think?
>>>
>>> Pete
>>>
>>> --
>>> Pete Muir
>>> http://in.relation.to/Bloggers/Pete
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev@...
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>
>>
>
>
> --
> Dirección Informática de Servicios Financieros
> Dirección General de Modernización e Innovación Gubernamental
> Secretaría de Administración y Finanzas
> Paseo de la Sierra 435 col. Reforma
> C.P. 86086, Villahermosa, Tabasco.
> Tel. 52 + 993 + 310 40 00 Ext. 7127
> http://saf.tabasco.gob.mx/
>
> IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
weld-dev mailing list
weld-dev@...
https://lists.jboss.org/mailman/listinfo/weld-dev

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
_______________________________________________
weld-dev mailing list
weld-dev@...
https://lists.jboss.org/mailman/listinfo/weld-dev

Jason Lee, SCJP

President, Oklahoma City Java Users Group

Senior Java Developer, Sun Microsystems

http://blogs.steeplesoft.com

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T08:22:41Z

Ah, cool. Looks like there are some github clones.

-Dan

On Tue, Nov 24, 2009 at 10:49 AM, Francisco Jose Peredo <franciscoperedo@...> wrote:

A nice out of the box hosting option for Mercurial? I think I mentioned GoogleCode... or there are many options to choose:

http://mercurial.selenic.com/wiki/MercurialHosting

Dan Allen escribió:
We all agreed to use git over svn, but to be honest, mercurial wasn't considered. I've used both as well. But in my short exposure, I really didn't see a difference. What makes git so attractive is that github.com explains so well how to use it.

I supposed we could consider mercurcial if there was a nice out of the box hosting option like github.com. If not, git will likely win because of that.

-Dan

On Tue, Nov 24, 2009 at 9:33 AM, Pete Muir <pmuir@...> wrote:

I have seen a reasonable amount of GIT, and have liked what I saw, as have most of the other core team who have spoken up on this issue.

Sell us Mercurial :-)

On 24 Nov 2009, at 14:22, Francisco Jose Peredo wrote:

> An interesting comparision?:
>
> http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
>
>
> Francisco Jose Peredo escribió:
>> I have not tried GIT, but from what I have read it is pretty
>> complicated to learn to use...
>> OTOH I have tried Mercurial, which is also distributed, and found it
>> confortable... apparently the
>> way it deals with its distribute nature is easier for subversion users
>> to understand...
>> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it
>> seems to work
>> well with large code bases... and there are plugins for Netbeans,
>> Eclipse and the Tortoise Hg
>> project is advanced and usable...
>> Google Code offers free Mercurial hosting...
>> Why not Mercurial?
>>
>>
>>
>> Pete Muir escribió:
>>> A quick item we discussed at the f2f meeting was whether to switch to
>>> GIT for our SCM, rather than SVN.
>>>
>>> This would give us a IMO a system well suited to our distribued dev
>>> model, it would also make it much easier for others to sandbox PEs and
>>> then contribute them back to us.
>>>
>>> The proposal is to use Github to host.
>>>
>>> The team members at devoxx were in favour, but what do others think?
>>>
>>> Pete
>>>
>>> --
>>> Pete Muir
>>> http://in.relation.to/Bloggers/Pete
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev@...
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>
>>
>
>
> --
> Dirección Informática de Servicios Financieros
> Dirección General de Modernización e Innovación Gubernamental
> Secretaría de Administración y Finanzas
> Paseo de la Sierra 435 col. Reforma
> C.P. 86086, Villahermosa, Tabasco.
> Tel. 52 + 993 + 310 40 00 Ext. 7127
> http://saf.tabasco.gob.mx/
>
> IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
weld-dev mailing list
weld-dev@...
https://lists.jboss.org/mailman/listinfo/weld-dev

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
-- 
Dirección Informática de Servicios Financieros
Dirección General de Modernización e Innovación Gubernamental
Secretaría de Administración y Finanzas
Paseo de la Sierra 435 col. Reforma
C.P. 86086, Villahermosa, Tabasco.
Tel. 52 + 993 + 310 40 00 Ext. 7127
http://saf.tabasco.gob.mx/

IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T08:08:31Z

It definitely seems like we should seriously reevaluate any decision
that bearded unix guys would be likely to agree with.

Sent from my iPhone

On Nov 24, 2009, at 10:38 AM, Emmanuel Bernard
<emmanuel@...> wrote:

> See my old thread on thecore about how geeky git is compared to
> mercurial. Basically Mercurial is natural to SVN users. GIT is natural
> to bearded unix people.
> That being said, GIT is quite popular and the tools tend to follow.
>
> On 24 nov. 09, at 15:33, Pete Muir wrote:
>
>> I have seen a reasonable amount of GIT, and have liked what I saw,
>> as have most of the other core team who have spoken up on this issue.
>>
>> Sell us Mercurial :-)
>>
>> On 24 Nov 2009, at 14:22, Francisco Jose Peredo wrote:
>>
>>> An interesting comparision?:
>>>
>>> http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
>>>
>>>
>>> Francisco Jose Peredo escribió:
>>>> I have not tried GIT, but from what I have read it is pretty
>>>> complicated to learn to use...
>>>> OTOH I have tried Mercurial, which is also distributed, and found
>>>> it
>>>> confortable... apparently the
>>>> way it deals with its distribute nature is easier for subversion
>>>> users
>>>> to understand...
>>>> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it
>>>> seems to work
>>>> well with large code bases... and there are plugins for Netbeans,
>>>> Eclipse and the Tortoise Hg
>>>> project is advanced and usable...
>>>> Google Code offers free Mercurial hosting...
>>>> Why not Mercurial?
>>>>
>>>>
>>>>
>>>> Pete Muir escribió:
>>>>> A quick item we discussed at the f2f meeting was whether to
>>>>> switch to
>>>>> GIT for our SCM, rather than SVN.
>>>>>
>>>>> This would give us a IMO a system well suited to our distribued
>>>>> dev
>>>>> model, it would also make it much easier for others to sandbox
>>>>> PEs and
>>>>> then contribute them back to us.
>>>>>
>>>>> The proposal is to use Github to host.
>>>>>
>>>>> The team members at devoxx were in favour, but what do others
>>>>> think?
>>>>>
>>>>> Pete
>>>>>
>>>>> --
>>>>> Pete Muir
>>>>> http://in.relation.to/Bloggers/Pete
>>>>> _______________________________________________
>>>>> seam-dev mailing list
>>>>> seam-dev@...
>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Dirección Informática de Servicios Financieros
>>> Dirección General de Modernización e Innovación Gubernamental
>>> Secretaría de Administración y Finanzas
>>> Paseo de la Sierra 435 col. Reforma
>>> C.P. 86086, Villahermosa, Tabasco.
>>> Tel. 52 + 993 + 310 40 00 Ext. 7127
>>> http://saf.tabasco.gob.mx/
>>>
>>> IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos,
>>> archivos insertados o "attachments", puede constituir información
>>> confidencial o reservada, en los términos de la Ley de Acceso a la
>>> Información Pública del Estado de Tabasco, y estar protegida po
>>> r el
>>> derecho fundamental a la privacidad. Se prohibe el uso de esta
>>> información por cualquier persona distinta al receptor intencional
>>> o previsto. Si usted ha recibibido esta transmisión electrónica
>>> por
>>> error, por favor responda inmediatamente al emisor y borre esta
>>> información de su sistema. El uso, diseminación, distribución o
>>> reproducción de esta transmisión electrónica por receptores no
>>> intencionados o no previstos por el emisor, no está autorizada y
>>> puede considerarse ilícita en los términos de la legislación p
>>> enal
>>> y civil vigente.
>>>
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev@...
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>>
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev@...
>> https://lists.jboss.org/mailman/listinfo/weld-dev
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev@...
> https://lists.jboss.org/mailman/listinfo/weld-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T08:07:49Z

+1 for git/github.

Echoing what others have said, I think github is ultimately what makes git the most attractive, all things considered. Github makes it incredibly easy to fork and propose pushes.

Google code seems to be better suited for smaller projects, even though google uses it for their even larger projects. For an open source project with outside contributors, it's essential to have a good "hub" - and github serves that purpose extremely well.

Just my 15 cents (inflation).

Ashish

PS: I'm tempted to further splinter this debate by proposing Bazaar :) (with Ubuntu's launchpad)

On Tue, Nov 24, 2009 at 10:49 AM, Francisco Jose Peredo <franciscoperedo@...> wrote:

A nice out of the box hosting option for Mercurial? I think I mentioned GoogleCode... or there are many options to choose:

http://mercurial.selenic.com/wiki/MercurialHosting

Dan Allen escribió:
We all agreed to use git over svn, but to be honest, mercurial wasn't considered. I've used both as well. But in my short exposure, I really didn't see a difference. What makes git so attractive is that github.com explains so well how to use it.

I supposed we could consider mercurcial if there was a nice out of the box hosting option like github.com. If not, git will likely win because of that.

-Dan

On Tue, Nov 24, 2009 at 9:33 AM, Pete Muir <pmuir@...> wrote:

I have seen a reasonable amount of GIT, and have liked what I saw, as have most of the other core team who have spoken up on this issue.

Sell us Mercurial :-)

On 24 Nov 2009, at 14:22, Francisco Jose Peredo wrote:

> An interesting comparision?:
>
> http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
>
>
> Francisco Jose Peredo escribió:
>> I have not tried GIT, but from what I have read it is pretty
>> complicated to learn to use...
>> OTOH I have tried Mercurial, which is also distributed, and found it
>> confortable... apparently the
>> way it deals with its distribute nature is easier for subversion users
>> to understand...
>> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it
>> seems to work
>> well with large code bases... and there are plugins for Netbeans,
>> Eclipse and the Tortoise Hg
>> project is advanced and usable...
>> Google Code offers free Mercurial hosting...
>> Why not Mercurial?
>>
>>
>>
>> Pete Muir escribió:
>>> A quick item we discussed at the f2f meeting was whether to switch to
>>> GIT for our SCM, rather than SVN.
>>>
>>> This would give us a IMO a system well suited to our distribued dev
>>> model, it would also make it much easier for others to sandbox PEs and
>>> then contribute them back to us.
>>>
>>> The proposal is to use Github to host.
>>>
>>> The team members at devoxx were in favour, but what do others think?
>>>
>>> Pete
>>>
>>> --
>>> Pete Muir
>>> http://in.relation.to/Bloggers/Pete
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev@...
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>
>>
>
>
> --
> Dirección Informática de Servicios Financieros
> Dirección General de Modernización e Innovación Gubernamental
> Secretaría de Administración y Finanzas
> Paseo de la Sierra 435 col. Reforma
> C.P. 86086, Villahermosa, Tabasco.
> Tel. 52 + 993 + 310 40 00 Ext. 7127
> http://saf.tabasco.gob.mx/
>
> IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
weld-dev mailing list
weld-dev@...
https://lists.jboss.org/mailman/listinfo/weld-dev

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen
-- 
Dirección Informática de Servicios Financieros
Dirección General de Modernización e Innovación Gubernamental
Secretaría de Administración y Finanzas
Paseo de la Sierra 435 col. Reforma
C.P. 86086, Villahermosa, Tabasco.
Tel. 52 + 993 + 310 40 00 Ext. 7127
http://saf.tabasco.gob.mx/

IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.
_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T07:49:26Z

A nice out of the box hosting option for Mercurial? I think I mentioned GoogleCode... or there are many options to choose:

http://mercurial.selenic.com/wiki/MercurialHosting

Dan Allen escribió:

We all agreed to use git over svn, but to be honest, mercurial wasn't considered. I've used both as well. But in my short exposure, I really didn't see a difference. What makes git so attractive is that github.com explains so well how to use it.

I supposed we could consider mercurcial if there was a nice out of the box hosting option like github.com. If not, git will likely win because of that.

-Dan

On Tue, Nov 24, 2009 at 9:33 AM, Pete Muir <pmuir@...> wrote:

I have seen a reasonable amount of GIT, and have liked what I saw, as have most of the other core team who have spoken up on this issue.

Sell us Mercurial :-)

On 24 Nov 2009, at 14:22, Francisco Jose Peredo wrote:

> An interesting comparision?:
>
> http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
>
>
> Francisco Jose Peredo escribió:
>> I have not tried GIT, but from what I have read it is pretty
>> complicated to learn to use...
>> OTOH I have tried Mercurial, which is also distributed, and found it
>> confortable... apparently the
>> way it deals with its distribute nature is easier for subversion users
>> to understand...
>> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it
>> seems to work
>> well with large code bases... and there are plugins for Netbeans,
>> Eclipse and the Tortoise Hg
>> project is advanced and usable...
>> Google Code offers free Mercurial hosting...
>> Why not Mercurial?
>>
>>
>>
>> Pete Muir escribió:
>>> A quick item we discussed at the f2f meeting was whether to switch to
>>> GIT for our SCM, rather than SVN.
>>>
>>> This would give us a IMO a system well suited to our distribued dev
>>> model, it would also make it much easier for others to sandbox PEs and
>>> then contribute them back to us.
>>>
>>> The proposal is to use Github to host.
>>>
>>> The team members at devoxx were in favour, but what do others think?
>>>
>>> Pete
>>>
>>> --
>>> Pete Muir
>>> http://in.relation.to/Bloggers/Pete
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev@...
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>
>>
>
>
> --
> Dirección Informática de Servicios Financieros
> Dirección General de Modernización e Innovación Gubernamental
> Secretaría de Administración y Finanzas
> Paseo de la Sierra 435 col. Reforma
> C.P. 86086, Villahermosa, Tabasco.
> Tel. 52 + 993 + 310 40 00 Ext. 7127
> http://saf.tabasco.gob.mx/
>
> IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
weld-dev mailing list
weld-dev@...
https://lists.jboss.org/mailman/listinfo/weld-dev

--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen

-- 
Dirección Informática de Servicios Financieros
Dirección General de Modernización e Innovación Gubernamental
Secretaría de Administración y Finanzas
Paseo de la Sierra 435 col. Reforma
C.P. 86086, Villahermosa, Tabasco.
Tel. 52 + 993 + 310 40 00 Ext. 7127
http://saf.tabasco.gob.mx/

IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T07:41:59Z

We all agreed to use git over svn, but to be honest, mercurial wasn't considered. I've used both as well. But in my short exposure, I really didn't see a difference. What makes git so attractive is that github.com explains so well how to use it.

I supposed we could consider mercurcial if there was a nice out of the box hosting option like github.com. If not, git will likely win because of that.

-Dan

On Tue, Nov 24, 2009 at 9:33 AM, Pete Muir <pmuir@...> wrote:

I have seen a reasonable amount of GIT, and have liked what I saw, as have most of the other core team who have spoken up on this issue.

Sell us Mercurial :-)

On 24 Nov 2009, at 14:22, Francisco Jose Peredo wrote:

> An interesting comparision?:
>
> http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
>
>
> Francisco Jose Peredo escribió:
>> I have not tried GIT, but from what I have read it is pretty
>> complicated to learn to use...
>> OTOH I have tried Mercurial, which is also distributed, and found it
>> confortable... apparently the
>> way it deals with its distribute nature is easier for subversion users
>> to understand...
>> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it
>> seems to work
>> well with large code bases... and there are plugins for Netbeans,
>> Eclipse and the Tortoise Hg
>> project is advanced and usable...
>> Google Code offers free Mercurial hosting...
>> Why not Mercurial?
>>
>>
>>
>> Pete Muir escribió:
>>> A quick item we discussed at the f2f meeting was whether to switch to
>>> GIT for our SCM, rather than SVN.
>>>
>>> This would give us a IMO a system well suited to our distribued dev
>>> model, it would also make it much easier for others to sandbox PEs and
>>> then contribute them back to us.
>>>
>>> The proposal is to use Github to host.
>>>
>>> The team members at devoxx were in favour, but what do others think?
>>>
>>> Pete
>>>
>>> --
>>> Pete Muir
>>> http://in.relation.to/Bloggers/Pete
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev@...
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>
>>
>
>
> --
> Dirección Informática de Servicios Financieros
> Dirección General de Modernización e Innovación Gubernamental
> Secretaría de Administración y Finanzas
> Paseo de la Sierra 435 col. Reforma
> C.P. 86086, Villahermosa, Tabasco.
> Tel. 52 + 993 + 310 40 00 Ext. 7127
> http://saf.tabasco.gob.mx/
>
> IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
weld-dev mailing list
weld-dev@...
https://lists.jboss.org/mailman/listinfo/weld-dev

Re: [weld-dev] Mercurial vs GIT

2009-11-24T07:38:25Z

See my old thread on thecore about how geeky git is compared to
mercurial. Basically Mercurial is natural to SVN users. GIT is natural
to bearded unix people.
That being said, GIT is quite popular and the tools tend to follow.

On 24 nov. 09, at 15:33, Pete Muir wrote:

> I have seen a reasonable amount of GIT, and have liked what I saw,
> as have most of the other core team who have spoken up on this issue.
>
> Sell us Mercurial :-)
>
> On 24 Nov 2009, at 14:22, Francisco Jose Peredo wrote:
>
>> An interesting comparision?:
>>
>> http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
>>
>>
>> Francisco Jose Peredo escribió:
>>> I have not tried GIT, but from what I have read it is pretty
>>> complicated to learn to use...
>>> OTOH I have tried Mercurial, which is also distributed, and found it
>>> confortable... apparently the
>>> way it deals with its distribute nature is easier for subversion
>>> users
>>> to understand...
>>> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it
>>> seems to work
>>> well with large code bases... and there are plugins for Netbeans,
>>> Eclipse and the Tortoise Hg
>>> project is advanced and usable...
>>> Google Code offers free Mercurial hosting...
>>> Why not Mercurial?
>>>
>>>
>>>
>>> Pete Muir escribió:
>>>> A quick item we discussed at the f2f meeting was whether to
>>>> switch to
>>>> GIT for our SCM, rather than SVN.
>>>>
>>>> This would give us a IMO a system well suited to our distribued dev
>>>> model, it would also make it much easier for others to sandbox
>>>> PEs and
>>>> then contribute them back to us.
>>>>
>>>> The proposal is to use Github to host.
>>>>
>>>> The team members at devoxx were in favour, but what do others
>>>> think?
>>>>
>>>> Pete
>>>>
>>>> --
>>>> Pete Muir
>>>> http://in.relation.to/Bloggers/Pete
>>>> _______________________________________________
>>>> seam-dev mailing list
>>>> seam-dev@...
>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>>
>>>>
>>>
>>>
>>
>>
>> --
>> Dirección Informática de Servicios Financieros
>> Dirección General de Modernización e Innovación Gubernamental
>> Secretaría de Administración y Finanzas
>> Paseo de la Sierra 435 col. Reforma
>> C.P. 86086, Villahermosa, Tabasco.
>> Tel. 52 + 993 + 310 40 00 Ext. 7127
>> http://saf.tabasco.gob.mx/
>>
>> IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos,
>> archivos insertados o "attachments", puede constituir información
>> confidencial o reservada, en los términos de la Ley de Acceso a la
>> Información Pública del Estado de Tabasco, y estar protegida por el
>> derecho fundamental a la privacidad. Se prohibe el uso de esta
>> información por cualquier persona distinta al receptor intencional
>> o previsto. Si usted ha recibibido esta transmisión electrónica por
>> error, por favor responda inmediatamente al emisor y borre esta
>> información de su sistema. El uso, diseminación, distribución o
>> reproducción de esta transmisión electrónica por receptores no
>> intencionados o no previstos por el emisor, no está autorizada y
>> puede considerarse ilícita en los términos de la legislación penal
>> y civil vigente.
>>
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev@...
> https://lists.jboss.org/mailman/listinfo/weld-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Mercurial vs GIT

2009-11-24T06:33:37Z

I have seen a reasonable amount of GIT, and have liked what I saw, as have most of the other core team who have spoken up on this issue.

Sell us Mercurial :-)

On 24 Nov 2009, at 14:22, Francisco Jose Peredo wrote:

> An interesting comparision?:
>
> http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/
>
>
> Francisco Jose Peredo escribió:
>> I have not tried GIT, but from what I have read it is pretty
>> complicated to learn to use...
>> OTOH I have tried Mercurial, which is also distributed, and found it
>> confortable... apparently the
>> way it deals with its distribute nature is easier for subversion users
>> to understand...
>> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it
>> seems to work
>> well with large code bases... and there are plugins for Netbeans,
>> Eclipse and the Tortoise Hg
>> project is advanced and usable...
>> Google Code offers free Mercurial hosting...
>> Why not Mercurial?
>>
>>
>>
>> Pete Muir escribió:
>>> A quick item we discussed at the f2f meeting was whether to switch to
>>> GIT for our SCM, rather than SVN.
>>>
>>> This would give us a IMO a system well suited to our distribued dev
>>> model, it would also make it much easier for others to sandbox PEs and
>>> then contribute them back to us.
>>>
>>> The proposal is to use Github to host.
>>>
>>> The team members at devoxx were in favour, but what do others think?
>>>
>>> Pete
>>>
>>> --
>>> Pete Muir
>>> http://in.relation.to/Bloggers/Pete
>>> _______________________________________________
>>> seam-dev mailing list
>>> seam-dev@...
>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>>
>>>
>>
>>
>
>
> --
> Dirección Informática de Servicios Financieros
> Dirección General de Modernización e Innovación Gubernamental
> Secretaría de Administración y Finanzas
> Paseo de la Sierra 435 col. Reforma
> C.P. 86086, Villahermosa, Tabasco.
> Tel. 52 + 993 + 310 40 00 Ext. 7127
> http://saf.tabasco.gob.mx/
>
> IMPORTANTE: Esta transmisión electrónica, incluyendo sus anexos, archivos insertados o "attachments", puede constituir información confidencial o reservada, en los términos de la Ley de Acceso a la Información Pública del Estado de Tabasco, y estar protegida por el derecho fundamental a la privacidad. Se prohibe el uso de esta información por cualquier persona distinta al receptor intencional o previsto. Si usted ha recibibido esta transmisión electrónica por error, por favor responda inmediatamente al emisor y borre esta información de su sistema. El uso, diseminación, distribución o reproducción de esta transmisión electrónica por receptores no intencionados o no previstos por el emisor, no está autorizada y puede considerarse ilícita en los términos de la legislación penal y civil vigente.
>
> _______________________________________________
> seam-dev mailing list
> seam-dev@...
> https://lists.jboss.org/mailman/listinfo/seam-dev

_______________________________________________
seam-dev mailing list
seam-dev@...
https://lists.jboss.org/mailman/listinfo/seam-dev

Re: Mercurial vs GIT

2009-11-24T06:22:37Z

An interesting comparision?:

http://importantshock.wordpress.com/2008/08/07/git-vs-mercurial/

Francisco Jose Peredo escribió:

> I have not tried GIT, but from what I have read it is pretty
> complicated to learn to use...
> OTOH I have tried Mercurial, which is also distributed, and found it
> confortable... apparently the
> way it deals with its distribute nature is easier for subversion users
> to understand...
> AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it
> seems to work
> well with large code bases... and there are plugins for Netbeans,
> Eclipse and the Tortoise Hg
> project is advanced and usable...
> Google Code offers free Mercurial hosting...
> Why not Mercurial?
>
>
>
> Pete Muir escribió:
>> A quick item we discussed at the f2f meeting was whether to switch to
>> GIT for our SCM, rather than SVN.
>>
>> This would give us a IMO a system well suited to our distribued dev
>> model, it would also make it much easier for others to sandbox PEs and
>> then contribute them back to us.
>>
>> The proposal is to use Github to host.
>>
>> The team members at devoxx were in favour, but what do others think?
>>
>> Pete
>>
>> --
>> Pete Muir
>> http://in.relation.to/Bloggers/Pete
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev@...
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>
>>
>
>

Re: Mercurial vs GIT

2009-11-24T06:17:12Z

I have not tried GIT, but from what I have read it is pretty complicated
to learn to use...
OTOH I have tried Mercurial, which is also distributed, and found it
confortable... apparently the
way it deals with its distribute nature is easier for subversion users
to understand...
AFAIK Netbeans source code is in Mercurial, also OpenJDK... So it seems
to work
well with large code bases... and there are plugins for Netbeans,
Eclipse and the Tortoise Hg
project is advanced and usable...
Google Code offers free Mercurial hosting...
Why not Mercurial?

Pete Muir escribió: