2:57 p.m.
Hi,
CDI TCK project moved to GitHub - see https://github.com/jboss/cditck.
FishEye and JIRA (https://issues.jboss.org/browse/CDITCK) configurations
arealready changed. Since this was the last Weld subproject to migrate
from svn, Weld svn repo will be made readonly - see ticket
https://engineering.redhat.com/rt3/Ticket/Display.html?id=117363. QA
Jenkins jobs are not updated yet.
If anyone encounters problems related to this migration, please let me know.
Martin
--
Martin Kouba
JBoss Quality Assurance Engineer
E-mail: mkouba(a)redhat.com
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic
11:52 p.m.
Awesome work, and great timing (since I was just telling people here at
#oscon that it's on github)!
- Dan Allen
Sent from my Android-powered phone:
An open platform for carriers, consumers and developers
On Jul 27, 2011 5:57 AM, "Martin Kouba" <mkouba(a)redhat.com> wrote:
Hi,
CDI TCK project moved to GitHub - see https://github.com/jboss/cditck.
FishEye and JIRA (https://issues.jboss.org/browse/CDITCK) configurations
arealready changed. Since this was the last Weld subproject to migrate
from svn, Weld svn repo will be made readonly - see ticket
https://engineering.redhat.com/rt3/Ticket/Display.html?id=117363. QA
Jenkins jobs are not updated yet.
If anyone encounters problems related to this migration, please let me
know.
Martin
--
Martin Kouba
JBoss Quality Assurance Engineer
E-mail: mkouba(a)redhat.com
Web: www.cz.redhat.com
Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic
12:04 a.m.
Shouldn't it include a README (at least) and a LICENSE file so people know
how to use it and can use it?
On Wed, Jul 27, 2011 at 15:52, Dan Allen <dan.j.allen(a)gmail.com> wrote:
Awesome work, and great timing (since I was just telling people here
at
#oscon that it's on github)!
- Dan Allen
Sent from my Android-powered phone:
An open platform for carriers, consumers and developers
On Jul 27, 2011 5:57 AM, "Martin Kouba" <mkouba(a)redhat.com> wrote:
> Hi,
> CDI TCK project moved to GitHub - see https://github.com/jboss/cditck.
> FishEye and JIRA (https://issues.jboss.org/browse/CDITCK) configurations
> arealready changed. Since this was the last Weld subproject to migrate
> from svn, Weld svn repo will be made readonly - see ticket
> https://engineering.redhat.com/rt3/Ticket/Display.html?id=117363. QA
> Jenkins jobs are not updated yet.
>
> If anyone encounters problems related to this migration, please let me
know.
>
> Martin
>
> --
> Martin Kouba
> JBoss Quality Assurance Engineer
> E-mail: mkouba(a)redhat.com
> Web: www.cz.redhat.com
> Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic
>
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
11:39 a.m.
Not quite. What you are looking at here is a development view, not the released zip, which
contains a readme and the license file. What would be useful would a quick readme pointing
people to do the docs so if they do stumble on this they can get a link.
On 27 Jul 2011, at 23:04, Jason Porter wrote:
Shouldn't it include a README (at least) and a LICENSE file so
people know how to use it and can use it?
On Wed, Jul 27, 2011 at 15:52, Dan Allen <dan.j.allen(a)gmail.com> wrote:
Awesome work, and great timing (since I was just telling people here at #oscon that
it's on github)!
- Dan Allen
Sent from my Android-powered phone:
An open platform for carriers, consumers and developers
On Jul 27, 2011 5:57 AM, "Martin Kouba" <mkouba(a)redhat.com> wrote:
> Hi,
> CDI TCK project moved to GitHub - see https://github.com/jboss/cditck.
> FishEye and JIRA (https://issues.jboss.org/browse/CDITCK) configurations
> arealready changed. Since this was the last Weld subproject to migrate
> from svn, Weld svn repo will be made readonly - see ticket
> https://engineering.redhat.com/rt3/Ticket/Display.html?id=117363. QA
> Jenkins jobs are not updated yet.
>
> If anyone encounters problems related to this migration, please let me know.
>
> Martin
>
> --
> Martin Kouba
> JBoss Quality Assurance Engineer
> E-mail: mkouba(a)redhat.com
> Web: www.cz.redhat.com
> Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic
>
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
4:50 p.m.
Right. I knew that. What you suggested Pete would be fine, just something the person who
comes across it on GitHub or wants to add a test can read and quickly understand what it
is and how to contribute.
Sent from my iPhone
On Jul 28, 2011, at 3:39, Pete Muir <pmuir(a)redhat.com> wrote:
Not quite. What you are looking at here is a development view, not
the released zip, which contains a readme and the license file. What would be useful would
a quick readme pointing people to do the docs so if they do stumble on this they can get a
link.
On 27 Jul 2011, at 23:04, Jason Porter wrote:
> Shouldn't it include a README (at least) and a LICENSE file so people know how to
use it and can use it?
>
> On Wed, Jul 27, 2011 at 15:52, Dan Allen <dan.j.allen(a)gmail.com> wrote:
> Awesome work, and great timing (since I was just telling people here at #oscon that
it's on github)!
>
> - Dan Allen
>
> Sent from my Android-powered phone:
> An open platform for carriers, consumers and developers
>
> On Jul 27, 2011 5:57 AM, "Martin Kouba" <mkouba(a)redhat.com> wrote:
>> Hi,
>> CDI TCK project moved to GitHub - see https://github.com/jboss/cditck.
>> FishEye and JIRA (https://issues.jboss.org/browse/CDITCK) configurations
>> arealready changed. Since this was the last Weld subproject to migrate
>> from svn, Weld svn repo will be made readonly - see ticket
>> https://engineering.redhat.com/rt3/Ticket/Display.html?id=117363. QA
>> Jenkins jobs are not updated yet.
>>
>> If anyone encounters problems related to this migration, please let me know.
>>
>> Martin
>>
>> --
>> Martin Kouba
>> JBoss Quality Assurance Engineer
>> E-mail: mkouba(a)redhat.com
>> Web: www.cz.redhat.com
>> Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic
>>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
>
>
>
> --
> Jason Porter
> http://lightguard-jp.blogspot.com
> http://twitter.com/lightguardjp
>
> Software Engineer
> Open Source Advocate
> Author of Seam Catch - Next Generation Java Exception Handling
>
> PGP key id: 926CCFF5
> PGP key available at: keyserver.net, pgp.mit.edu
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
4:58 p.m.
Suggest you file a CDITCK issue in JIRA.
We already have extensive docs on the TCK, so we can just link to them.
On 28 Jul 2011, at 15:50, Jason Porter wrote:
Right. I knew that. What you suggested Pete would be fine, just
something the person who comes across it on GitHub or wants to add a test can read and
quickly understand what it is and how to contribute.
Sent from my iPhone
On Jul 28, 2011, at 3:39, Pete Muir <pmuir(a)redhat.com> wrote:
> Not quite. What you are looking at here is a development view, not the released zip,
which contains a readme and the license file. What would be useful would a quick readme
pointing people to do the docs so if they do stumble on this they can get a link.
>
> On 27 Jul 2011, at 23:04, Jason Porter wrote:
>
>> Shouldn't it include a README (at least) and a LICENSE file so people know
how to use it and can use it?
>>
>> On Wed, Jul 27, 2011 at 15:52, Dan Allen <dan.j.allen(a)gmail.com> wrote:
>> Awesome work, and great timing (since I was just telling people here at #oscon
that it's on github)!
>>
>> - Dan Allen
>>
>> Sent from my Android-powered phone:
>> An open platform for carriers, consumers and developers
>>
>> On Jul 27, 2011 5:57 AM, "Martin Kouba" <mkouba(a)redhat.com>
wrote:
>>> Hi,
>>> CDI TCK project moved to GitHub - see https://github.com/jboss/cditck.
>>> FishEye and JIRA (https://issues.jboss.org/browse/CDITCK) configurations
>>> arealready changed. Since this was the last Weld subproject to migrate
>>> from svn, Weld svn repo will be made readonly - see ticket
>>> https://engineering.redhat.com/rt3/Ticket/Display.html?id=117363. QA
>>> Jenkins jobs are not updated yet.
>>>
>>> If anyone encounters problems related to this migration, please let me know.
>>>
>>> Martin
>>>
>>> --
>>> Martin Kouba
>>> JBoss Quality Assurance Engineer
>>> E-mail: mkouba(a)redhat.com
>>> Web: www.cz.redhat.com
>>> Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic
>>>
>>
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>
>>
>>
>> --
>> Jason Porter
>> http://lightguard-jp.blogspot.com
>> http://twitter.com/lightguardjp
>>
>> Software Engineer
>> Open Source Advocate
>> Author of Seam Catch - Next Generation Java Exception Handling
>>
>> PGP key id: 926CCFF5
>> PGP key available at: keyserver.net, pgp.mit.edu
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/weld-dev
>
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
9:45 p.m.
Right, my intention was to link to them from the readme, nothing more
complicated than that.
- Dan Allen
Sent from my Android-powered phone:
An open platform for carriers, consumers and developers
On Jul 28, 2011 7:59 AM, "Pete Muir" <pmuir(a)redhat.com> wrote:
Suggest you file a CDITCK issue in JIRA.
We already have extensive docs on the TCK, so we can just link to them.
On 28 Jul 2011, at 15:50, Jason Porter wrote:
> Right. I knew that. What you suggested Pete would be fine, just something
the
person who comes across it on GitHub or wants to add a test can read and
quickly understand what it is and how to contribute.
>
> Sent from my iPhone
>
> On Jul 28, 2011, at 3:39, Pete Muir <pmuir(a)redhat.com> wrote:
>
>> Not quite. What you are looking at here is a development view, not the
released zip, which contains a readme and the license file. What would be
useful would a quick readme pointing people to do the docs so if they do
stumble on this they can get a link.
>>
>> On 27 Jul 2011, at 23:04, Jason Porter wrote:
>>
>>> Shouldn't it include a README (at least) and a LICENSE file so people
know how to use it and can use it?
>>>
>>> On Wed, Jul 27, 2011 at 15:52, Dan Allen <dan.j.allen(a)gmail.com>
wrote:
>>> Awesome work, and great timing (since I was just telling people here at
#oscon that it's on github)!
>>>
>>> - Dan Allen
>>>
>>> Sent from my Android-powered phone:
>>> An open platform for carriers, consumers and developers
>>>
>>> On Jul 27, 2011 5:57 AM, "Martin Kouba" <mkouba(a)redhat.com>
wrote:
>>>> Hi,
>>>> CDI TCK project moved to GitHub - see https://github.com/jboss/cditck.
>>>> FishEye and JIRA
(https://issues.jboss.org/browse/CDITCK)
configurations
>>>> arealready changed. Since this was the last Weld
subproject to migrate
>>>> from svn, Weld svn repo will be made readonly - see
ticket
>>>> https://engineering.redhat.com/rt3/Ticket/Display.html?id=117363. QA
>>>> Jenkins jobs are not updated yet.
>>>>
>>>> If anyone encounters problems related to this migration, please let me
know.
>>>>
>>>> Martin
>>>>
>>>> --
>>>> Martin Kouba
>>>> JBoss Quality Assurance Engineer
>>>> E-mail: mkouba(a)redhat.com
>>>> Web: www.cz.redhat.com
>>>> Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic
>>>>
>>>
>>> _______________________________________________
>>> weld-dev mailing list
>>> weld-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>>
>>>
>>>
>>> --
>>> Jason Porter
>>> http://lightguard-jp.blogspot.com
>>> http://twitter.com/lightguardjp
>>>
>>> Software Engineer
>>> Open Source Advocate
>>> Author of Seam Catch - Next Generation Java Exception Handling
>>>
>>> PGP key id: 926CCFF5
>>> PGP key available at: keyserver.net, pgp.mit.edu
>>> _______________________________________________
>>> weld-dev mailing list
>>> weld-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
9:56 p.m.
Done https://issues.jboss.org/browse/CDITCK-227
On Thu, Jul 28, 2011 at 13:45, Dan Allen <dan.j.allen(a)gmail.com> wrote:
Right, my intention was to link to them from the readme, nothing
more
complicated than that.
- Dan Allen
Sent from my Android-powered phone:
An open platform for carriers, consumers and developers
On Jul 28, 2011 7:59 AM, "Pete Muir" <pmuir(a)redhat.com> wrote:
> Suggest you file a CDITCK issue in JIRA.
>
> We already have extensive docs on the TCK, so we can just link to them.
>
> On 28 Jul 2011, at 15:50, Jason Porter wrote:
>
>> Right. I knew that. What you suggested Pete would be fine, just
something the person who comes across it on GitHub or wants to add a test
can read and quickly understand what it is and how to contribute.
>>
>> Sent from my iPhone
>>
>> On Jul 28, 2011, at 3:39, Pete Muir <pmuir(a)redhat.com> wrote:
>>
>>> Not quite. What you are looking at here is a development view, not the
released zip, which contains a readme and the license file. What would be
useful would a quick readme pointing people to do the docs so if they do
stumble on this they can get a link.
>>>
>>> On 27 Jul 2011, at 23:04, Jason Porter wrote:
>>>
>>>> Shouldn't it include a README (at least) and a LICENSE file so
people
know how to use it and can use it?
>>>>
>>>> On Wed, Jul 27, 2011 at 15:52, Dan Allen <dan.j.allen(a)gmail.com>
wrote:
>>>> Awesome work, and great timing (since I was just telling people here
at #oscon that it's on github)!
>>>>
>>>> - Dan Allen
>>>>
>>>> Sent from my Android-powered phone:
>>>> An open platform for carriers, consumers and developers
>>>>
>>>> On Jul 27, 2011 5:57 AM, "Martin Kouba"
<mkouba(a)redhat.com> wrote:
>>>>> Hi,
>>>>> CDI TCK project moved to GitHub - see
https://github.com/jboss/cditck.
>>>>> FishEye and JIRA (https://issues.jboss.org/browse/CDITCK)
configurations
>>>>> arealready changed. Since this was the last Weld subproject to
migrate
>>>>> from svn, Weld svn repo will be made readonly - see ticket
>>>>> https://engineering.redhat.com/rt3/Ticket/Display.html?id=117363.
QA
>>>>> Jenkins jobs are not updated yet.
>>>>>
>>>>> If anyone encounters problems related to this migration, please let
me know.
>>>>>
>>>>> Martin
>>>>>
>>>>> --
>>>>> Martin Kouba
>>>>> JBoss Quality Assurance Engineer
>>>>> E-mail: mkouba(a)redhat.com
>>>>> Web: www.cz.redhat.com
>>>>> Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech Republic
>>>>>
>>>>
>>>> _______________________________________________
>>>> weld-dev mailing list
>>>> weld-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>>>
>>>>
>>>>
>>>> --
>>>> Jason Porter
>>>> http://lightguard-jp.blogspot.com
>>>> http://twitter.com/lightguardjp
>>>>
>>>> Software Engineer
>>>> Open Source Advocate
>>>> Author of Seam Catch - Next Generation Java Exception Handling
>>>>
>>>> PGP key id: 926CCFF5
>>>> PGP key available at: keyserver.net, pgp.mit.edu
>>>> _______________________________________________
>>>> weld-dev mailing list
>>>> weld-dev(a)lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>>
>>
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/weld-dev
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/weld-dev
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net, pgp.mit.edu
10:43 a.m.
I added basic README that points to TCK Reference Guide - check it out.
Martin
Dne 28.7.2011 21:56, Jason Porter napsal(a):
Done https://issues.jboss.org/browse/CDITCK-227
On Thu, Jul 28, 2011 at 13:45, Dan Allen <dan.j.allen(a)gmail.com
<mailto:dan.j.allen@gmail.com>> wrote:
Right, my intention was to link to them from the readme, nothing
more complicated than that.
- Dan Allen
Sent from my Android-powered phone:
An open platform for carriers, consumers and developers
On Jul 28, 2011 7:59 AM, "Pete Muir" <pmuir(a)redhat.com
<mailto:pmuir@redhat.com>> wrote:
> Suggest you file a CDITCK issue in JIRA.
>
> We already have extensive docs on the TCK, so we can just link
to them.
>
> On 28 Jul 2011, at 15:50, Jason Porter wrote:
>
>> Right. I knew that. What you suggested Pete would be fine, just
something the person who comes across it on GitHub or wants to add
a test can read and quickly understand what it is and how to
contribute.
>>
>> Sent from my iPhone
>>
>> On Jul 28, 2011, at 3:39, Pete Muir <pmuir(a)redhat.com
<mailto:pmuir@redhat.com>> wrote:
>>
>>> Not quite. What you are looking at here is a development view,
not the released zip, which contains a readme and the license
file. What would be useful would a quick readme pointing people to
do the docs so if they do stumble on this they can get a link.
>>>
>>> On 27 Jul 2011, at 23:04, Jason Porter wrote:
>>>
>>>> Shouldn't it include a README (at least) and a LICENSE file
so people know how to use it and can use it?
>>>>
>>>> On Wed, Jul 27, 2011 at 15:52, Dan Allen
<dan.j.allen(a)gmail.com <mailto:dan.j.allen@gmail.com>> wrote:
>>>> Awesome work, and great timing (since I was just telling
people here at #oscon that it's on github)!
>>>>
>>>> - Dan Allen
>>>>
>>>> Sent from my Android-powered phone:
>>>> An open platform for carriers, consumers and developers
>>>>
>>>> On Jul 27, 2011 5:57 AM, "Martin Kouba"
<mkouba(a)redhat.com
<mailto:mkouba@redhat.com>> wrote:
>>>>> Hi,
>>>>> CDI TCK project moved to GitHub - see
https://github.com/jboss/cditck.
>>>>> FishEye and JIRA (https://issues.jboss.org/browse/CDITCK)
configurations
>>>>> arealready changed. Since this was the last Weld subproject
to migrate
>>>>> from svn, Weld svn repo will be made readonly - see ticket
>>>>>
https://engineering.redhat.com/rt3/Ticket/Display.html?id=117363. QA
>>>>> Jenkins jobs are not updated yet.
>>>>>
>>>>> If anyone encounters problems related to this migration,
please let me know.
>>>>>
>>>>> Martin
>>>>>
>>>>> --
>>>>> Martin Kouba
>>>>> JBoss Quality Assurance Engineer
>>>>> E-mail: mkouba(a)redhat.com <mailto:mkouba@redhat.com>
>>>>> Web: www.cz.redhat.com <http://www.cz.redhat.com>
>>>>> Red Hat Czech s.r.o., Purkyňova 99/71, 612 45, Brno, Czech
Republic
>>>>>
>>>>
>>>> _______________________________________________
>>>> weld-dev mailing list
>>>> weld-dev(a)lists.jboss.org <mailto:weld-dev@lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>>>
>>>>
>>>>
>>>> --
>>>> Jason Porter
>>>> http://lightguard-jp.blogspot.com
>>>> http://twitter.com/lightguardjp
>>>>
>>>> Software Engineer
>>>> Open Source Advocate
>>>> Author of Seam Catch - Next Generation Java Exception Handling
>>>>
>>>> PGP key id: 926CCFF5
>>>> PGP key available at: keyserver.net <http://keyserver.net>;,
pgp.mit.edu <http://pgp.mit.edu>
>>>> _______________________________________________
>>>> weld-dev mailing list
>>>> weld-dev(a)lists.jboss.org <mailto:weld-dev@lists.jboss.org>
>>>> https://lists.jboss.org/mailman/listinfo/weld-dev
>>>
>>
>> _______________________________________________
>> weld-dev mailing list
>> weld-dev(a)lists.jboss.org <mailto:weld-dev@lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/weld-dev
>
>
> _______________________________________________
> weld-dev mailing list
> weld-dev(a)lists.jboss.org <mailto:weld-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/weld-dev
--
Jason Porter
http://lightguard-jp.blogspot.com
http://twitter.com/lightguardjp
Software Engineer
Open Source Advocate
Author of Seam Catch - Next Generation Java Exception Handling
PGP key id: 926CCFF5
PGP key available at: keyserver.net <http://keyserver.net>;,
pgp.mit.edu <http://pgp.mit.edu>
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
12:28 a.m.
On Fri, Jul 29, 2011 at 01:43, Martin Kouba <mkouba(a)redhat.com> wrote:
**
I added basic README that points to TCK Reference Guide - check it out.
Good start. I revised the sentence to be more specific about what the guide
contains.
If it's not too late, I would prefer for the repository to be named cdi-tck
rather than cditck. The hyphenated form is more consistent with how we've
been naming repositories and it makes it easier to see the two words (and
hence recognize it as a TCK). Anyone have a problem with that change?
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
1:01 p.m.
Done.
On 29 Jul 2011, at 23:28, Dan Allen wrote:
On Fri, Jul 29, 2011 at 01:43, Martin Kouba <mkouba(a)redhat.com>
wrote:
I added basic README that points to TCK Reference Guide - check it out.
Good start. I revised the sentence to be more specific about what the guide contains.
If it's not too late, I would prefer for the repository to be named cdi-tck rather
than cditck. The hyphenated form is more consistent with how we've been naming
repositories and it makes it easier to see the two words (and hence recognize it as a
TCK). Anyone have a problem with that change?
-Dan
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev
4645
days inactive
4650
days old
10 comments
4 participants
participants (4)
-
Dan Allen -
Jason Porter -
Martin Kouba -
Pete Muir