You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openwebbeans.apache.org by Gurkan Erdogdu <gu...@yahoo.com> on 2009/01/21 08:29:29 UTC
Re: additional usage of GIT for experimental features[TCK Related]
>MS: I will create a Jira and attach the TCK suite via patch in the meantime.
>>KM:Personally, I'd commit the changes
Sorry! But I do not still understand why we import the TCK related codes into our SVN. Every time the TCK code is updated by the JBoss, do we sync. with it?
I only know that TCK is necessary to show the specification compatibility.
Kevan : do we have to integrate the TCK related codes into our SVN? or more explicitly, how do we use the TCK in the future to express the specification compatibility ?
What have you done in the Geronimo?
Thanks a lot ;
/Gurkan
________________________________
From: Kevan Miller <ke...@gmail.com>
To: openwebbeans-dev@incubator.apache.org
Sent: Tuesday, January 20, 2009 8:38:16 PM
Subject: Re: additional usage of GIT for experimental features
On Jan 20, 2009, at 7:07 AM, Mark Struberg wrote:
> Hi!
>
> As I already tried to expain: it was never ment to use git for productive changes - think about it more like a blog full with code ;)
Understood. However, there are other ways of accomplishing this. Which would probably be more acceptable...
1) create an openwebbeans/sandbox in svn
2) generate a patch and post to the jira
3) discuss your intentions/proposed changes (which you've done), and commit them in trunk. The community should be reviewing all changes. It's not necessarily bad to discover disagreements, post-commit. These disagreements can be resolved.
At Apache, all committers have earned the necessary karma to be fully trusted. IIUC, this is un-Git like (at least it doesn't match my understanding of the social norms in Git usage). We may be able to work out acceptable usage of Git. I want to be sure we're avoiding "private" communications about code and some usages of Git might lead to the potential for private conversations. BTW, I'm certainly not implying that this is your (or anybody else's) intent...
>
>
> Back to the issue: how do we cope with the TCK code? Should I check it in to SVN? It will compile, but cannot run due to API incompatibilities between us and RI. But as long as we do not add the <module> in the parent pom it will at least not break the build.
Guess we could add the JBoss snapshot repo to our builds... This would cause problems during releases and as the TCK changes.
>
> I will create a Jira and attach the TCK suite via patch in the meantime.
Personally, I'd commit the changes
>
> I saw Jukka will organise a GIT session on the ApacheCon EU. Maybe we'll find some time there...
Sounds good. I'm hoping that I can attend, this year...
--kevan
Re: additional usage of GIT for experimental features[TCK Related]
Posted by Gurkan Erdogdu <gu...@yahoo.com>.
Ok Mark. Thanks for clearing.
When will you check in the TCK integration code into our repo? So I would like to try it :)
/Gurkan
________________________________
From: Mark Struberg <st...@yahoo.de>
To: openwebbeans-dev@incubator.apache.org
Sent: Wednesday, January 21, 2009 12:50:15 PM
Subject: Re: additional usage of GIT for experimental features[TCK Related]
I don't know how TCKs are handled, but I usually require them to be executed and pass before a release is done.
And please do not confuse the JBoss TCK implementation with our OpenWebBeans Tck _Integration_. I will only checkin the TCK Integration code and not the TCKs themselfs. The code written by JBoss guys are only referenced via maven dependencies. This is SNAPSHOT version currently [1], but they will have to release a tagged version shortly after the Spec is final.
LieGrue,
strub
[1] so for executing the TCK tests currently one has to also run:
$> svn co http://anonsvn.jboss.org/repos/webbeans/tck/trunk tck
$> mvn clean install
--- Gurkan Erdogdu <gu...@yahoo.com> schrieb am Mi, 21.1.2009:
> Von: Gurkan Erdogdu <gu...@yahoo.com>
> Betreff: Re: additional usage of GIT for experimental features[TCK Related]
> An: openwebbeans-dev@incubator.apache.org
> Datum: Mittwoch, 21. Januar 2009, 8:29
> >MS: I will create a Jira and attach the TCK suite via
> patch in the meantime.
>
> >>KM:Personally, I'd commit the changes
>
> Sorry! But I do not still understand why we import the TCK
> related codes into our SVN. Every time the TCK code is
> updated by the JBoss, do we sync. with it?
>
> I only know that TCK is necessary to show the specification
> compatibility.
>
> Kevan : do we have to integrate the TCK related codes into
> our SVN? or more explicitly, how do we use the TCK in the
> future to express the specification compatibility ?
> What have you done in the Geronimo?
>
>
> Thanks a lot ;
>
> /Gurkan
>
>
> ________________________________
> From: Kevan Miller <ke...@gmail.com>
> To: openwebbeans-dev@incubator.apache.org
> Sent: Tuesday, January 20, 2009 8:38:16 PM
> Subject: Re: additional usage of GIT for experimental
> features
>
>
> On Jan 20, 2009, at 7:07 AM, Mark Struberg wrote:
>
> > Hi!
> >
> > As I already tried to expain: it was never ment to use
> git for productive changes - think about it more like a blog
> full with code ;)
>
> Understood. However, there are other ways of accomplishing
> this. Which would probably be more acceptable...
>
> 1) create an openwebbeans/sandbox in svn
> 2) generate a patch and post to the jira
> 3) discuss your intentions/proposed changes (which
> you've done), and commit them in trunk. The community
> should be reviewing all changes. It's not necessarily
> bad to discover disagreements, post-commit. These
> disagreements can be resolved.
>
> At Apache, all committers have earned the necessary karma
> to be fully trusted. IIUC, this is un-Git like (at least it
> doesn't match my understanding of the social norms in
> Git usage). We may be able to work out acceptable usage of
> Git. I want to be sure we're avoiding
> "private" communications about code and some
> usages of Git might lead to the potential for private
> conversations. BTW, I'm certainly not implying that this
> is your (or anybody else's) intent...
>
> >
> >
> > Back to the issue: how do we cope with the TCK code?
> Should I check it in to SVN? It will compile, but cannot run
> due to API incompatibilities between us and RI. But as long
> as we do not add the <module> in the parent pom it
> will at least not break the build.
>
> Guess we could add the JBoss snapshot repo to our builds...
> This would cause problems during releases and as the TCK
> changes.
>
> >
> > I will create a Jira and attach the TCK suite via
> patch in the meantime.
>
> Personally, I'd commit the changes
>
> >
> > I saw Jukka will organise a GIT session on the
> ApacheCon EU. Maybe we'll find some time there...
>
> Sounds good. I'm hoping that I can attend, this year...
>
> --kevan
Re: additional usage of GIT for experimental features[TCK Related]
Posted by Kevan Miller <ke...@gmail.com>.
On Jan 21, 2009, at 5:50 AM, Mark Struberg wrote:
> I don't know how TCKs are handled, but I usually require them to be
> executed and pass before a release is done.
>
>
> And please do not confuse the JBoss TCK implementation with our
> OpenWebBeans Tck _Integration_. I will only checkin the TCK
> Integration code and not the TCKs themselfs. The code written by
> JBoss guys are only referenced via maven dependencies. This is
> SNAPSHOT version currently [1], but they will have to release a
> tagged version shortly after the Spec is final.
Once the spec goes final, the JCP will make the TCK available. We'd
obtain the "official" TCK from the JCP. The ASF has a JCP site (http://apache.org/jcp/
), mailing list, and a process for obtaining official TCK's from the
JCP.
Since the WebBeans TCK is being implemented in the open with an ASL
license, we're able to obtain a snapshot of the TCK prior to the spec
going final. Until the spec goes final, TCK results are meaningless.
We can't make any claims regarding compliance. It is, however, a
useful testing tool...
>
>
> [1] so for executing the TCK tests currently one has to also run:
> $> svn co http://anonsvn.jboss.org/repos/webbeans/tck/trunk tck
> $> mvn clean install
This sounds pretty good to me...
--kevan
Re: additional usage of GIT for experimental features[TCK Related]
Posted by Mark Struberg <st...@yahoo.de>.
I don't know how TCKs are handled, but I usually require them to be executed and pass before a release is done.
And please do not confuse the JBoss TCK implementation with our OpenWebBeans Tck _Integration_. I will only checkin the TCK Integration code and not the TCKs themselfs. The code written by JBoss guys are only referenced via maven dependencies. This is SNAPSHOT version currently [1], but they will have to release a tagged version shortly after the Spec is final.
LieGrue,
strub
[1] so for executing the TCK tests currently one has to also run:
$> svn co http://anonsvn.jboss.org/repos/webbeans/tck/trunk tck
$> mvn clean install
--- Gurkan Erdogdu <gu...@yahoo.com> schrieb am Mi, 21.1.2009:
> Von: Gurkan Erdogdu <gu...@yahoo.com>
> Betreff: Re: additional usage of GIT for experimental features[TCK Related]
> An: openwebbeans-dev@incubator.apache.org
> Datum: Mittwoch, 21. Januar 2009, 8:29
> >MS: I will create a Jira and attach the TCK suite via
> patch in the meantime.
>
> >>KM:Personally, I'd commit the changes
>
> Sorry! But I do not still understand why we import the TCK
> related codes into our SVN. Every time the TCK code is
> updated by the JBoss, do we sync. with it?
>
> I only know that TCK is necessary to show the specification
> compatibility.
>
> Kevan : do we have to integrate the TCK related codes into
> our SVN? or more explicitly, how do we use the TCK in the
> future to express the specification compatibility ?
> What have you done in the Geronimo?
>
>
> Thanks a lot ;
>
> /Gurkan
>
>
> ________________________________
> From: Kevan Miller <ke...@gmail.com>
> To: openwebbeans-dev@incubator.apache.org
> Sent: Tuesday, January 20, 2009 8:38:16 PM
> Subject: Re: additional usage of GIT for experimental
> features
>
>
> On Jan 20, 2009, at 7:07 AM, Mark Struberg wrote:
>
> > Hi!
> >
> > As I already tried to expain: it was never ment to use
> git for productive changes - think about it more like a blog
> full with code ;)
>
> Understood. However, there are other ways of accomplishing
> this. Which would probably be more acceptable...
>
> 1) create an openwebbeans/sandbox in svn
> 2) generate a patch and post to the jira
> 3) discuss your intentions/proposed changes (which
> you've done), and commit them in trunk. The community
> should be reviewing all changes. It's not necessarily
> bad to discover disagreements, post-commit. These
> disagreements can be resolved.
>
> At Apache, all committers have earned the necessary karma
> to be fully trusted. IIUC, this is un-Git like (at least it
> doesn't match my understanding of the social norms in
> Git usage). We may be able to work out acceptable usage of
> Git. I want to be sure we're avoiding
> "private" communications about code and some
> usages of Git might lead to the potential for private
> conversations. BTW, I'm certainly not implying that this
> is your (or anybody else's) intent...
>
> >
> >
> > Back to the issue: how do we cope with the TCK code?
> Should I check it in to SVN? It will compile, but cannot run
> due to API incompatibilities between us and RI. But as long
> as we do not add the <module> in the parent pom it
> will at least not break the build.
>
> Guess we could add the JBoss snapshot repo to our builds...
> This would cause problems during releases and as the TCK
> changes.
>
> >
> > I will create a Jira and attach the TCK suite via
> patch in the meantime.
>
> Personally, I'd commit the changes
>
> >
> > I saw Jukka will organise a GIT session on the
> ApacheCon EU. Maybe we'll find some time there...
>
> Sounds good. I'm hoping that I can attend, this year...
>
> --kevan