gemini-dev http://dev.eclipse.org/mhonarc/lists/gemini-dev/maillist.html gemini-dev en-us Sat, 18 May 2013 14:50:05 GMT Sat, 18 May 2013 14:50:05 GMT http://blogs.law.harvard.edu/tech/rss MHonArc RSS 2.0 RCFile webmaster@eclipse.org (Webmaster) webmaster@eclipse.org (Webmaster) gemini-dev http://www.eclipse.org/eclipse.org-common/themes/Phoenix/images/eclipse_home_header.jpg http://dev.eclipse.org/mhonarc/lists/gemini-dev/maillist.html [gemini-dev] Different jpa persistence bundles in same transaction http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00912.html Hi, i now, that jpa entities from a persistent bundle must not become used in a entity manager from a different bundle. So i try to figure out a way to persist entities from different persistent bundles in the same transaction. Even if they are using diff... Hi,

i now, that jpa entities from a persistent bundle must not become used in a entity manager from a different bundle.


So i try to figure out a way to persist entities from different persistent bundles in the same transaction. Even if they are using different entity manager.
Eg:

txn.begin
modul1.persist(someBean)
module2.persist(someBean)
txn.rollback // will rollback modul1 and module2


1) Would OSGi JTA specification handle that stuff properly?
2) Can i use gemini JPA and apache aries JTA together?


Thanks a lot for your answers.


 
-- 
Mit besten Grüßen
Florian Pirchner
Fohlenweg 22
2301 Probstdorf
Tel: +43 650 7772338
florian.pirchner@xxxxxxxxx
]]> Sat, 18 May 2013 14:42:32 GMT http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00912.html florian.pirchner@xxxxxxx (Florian Pirchner) [gemini-dev] Apologies for missing the next call http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00911.html Unfortunately, I will not be able to attend the call on May, 21. - Juergen Unfortunately, I will not be able to attend the call on May, 21. - Juergen ]]> Fri, 17 May 2013 20:46:29 GMT http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00911.html juergen.kissner@xxxxxxx (Kissner, Juergen) Re: [gemini-dev] Clover / JaCoCo http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00910.html Thanks. I think the requirements are (a) to be able to extract code coverage metrics easily, and (b) to be able to find out easily which lines of code are not exercised by the tests. (b) is extremely useful if the coverage falls below the required value.If... Thanks. I think the requirements are (a) to be able to extract code coverage metrics easily, and (b) to be able to find out easily which lines of code are not exercised by the tests. (b) is extremely useful if the coverage falls below the required value.

If JaCoCo satisfies these, then fine. (Clover does.)

Regards,
Glyn



On 9 May 2013, at 13:52, Olaf Otto <olaf@xxxxxxx> wrote:

Hi Glyn

The main reason I'd prefer JaCoCo is that it is completely open source,
hosted on github and published under EPL 1.0
(https://github.com/jacoco/jacoco/blob/master/LICENSE.md), thus I believe it
is a better fit for this project.

Regards,
Olaf

-----Original Message-----
From: gemini-dev-bounces@xxxxxxxxxxx [mailto:gemini-dev-bounces@xxxxxxxxxxx]
On Behalf Of gemini-dev-request@xxxxxxxxxxx
Sent: Donnerstag, 9. Mai 2013 14:27
To: gemini-dev@xxxxxxxxxxx
Subject: gemini-dev Digest, Vol 39, Issue 2

Send gemini-dev mailing list submissions to
gemini-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/gemini-dev
or, via email, send a message with subject or body 'help' to
gemini-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
gemini-dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than
"Re: Contents of gemini-dev digest..."


Today's Topics:

  1. Gemini Naming 1.0.2.RELEASE is now available (Violeta Georgieva)
  2. Re: gemini-dev Digest, Vol 39, Issue 1 (Olaf Otto)
  3. Re: gemini-dev Digest, Vol 39, Issue 1 (Glyn Normington)


----------------------------------------------------------------------

Message: 1
Date: Thu, 9 May 2013 09:31:10 +0300
From: Violeta Georgieva <milesg78@xxxxxxxxx>
To: Gemini and sub-projects developer discussions
<gemini-dev@xxxxxxxxxxx>
Subject: [gemini-dev] Gemini Naming 1.0.2.RELEASE is now available
Message-ID:
<CAFmzfTUkjTynoHcGS3-F5cGPmBmesJ6GqyCLEfXfT48hLdXGPg@xxxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi,

Gemini Naming has shipped its 1.0.2.RELEASE. The artifacts are available for
download [1]. This release contains fix for BZ407399 [2].

The official documentation can be found here [3].

Regards
Violeta

[1] http://eclipse.org/gemini/naming/download.php
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=407399
[3] http://eclipse.org/gemini/naming/documentation.php
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130509/61f
d27d1/attachment.html>

------------------------------

Message: 2
Date: Thu, 9 May 2013 13:57:38 +0200
From: "Olaf Otto" <olaf@xxxxxxx>
To: <gemini-dev@xxxxxxxxxxx>
Subject: Re: [gemini-dev] gemini-dev Digest, Vol 39, Issue 1
Message-ID: <000901ce4cac$6762fef0$3628fcd0$@x100.de>
Content-Type: text/plain; charset="us-ascii"

Hi Glyn

I am about half way through all the testcases of the gemini core. I will
make the first commit once I am through with all of them to avoid
inhomogeneous testing state in a branch actively under development. However,
I just committed the POM with the new dependencies - I am quite sure these
shall suffice for the refactorings. Regarding test coverage: I found that an
old version of clover was once used to measure code coverage. It is my
intention to compare both coverage and execution time of the tests with the
initial test coverage figures to prevent a drop of test coverage - how about
switching to JaCoCo (http://www.eclemma.org/jacoco/)? The alternative could
be to request an open source license for clover from Atlassian, but I'd
prefer the former solution.


Regards,
Olaf

-----Original Message-----
From: gemini-dev-bounces@xxxxxxxxxxx [mailto:gemini-dev-bounces@xxxxxxxxxxx]
On Behalf Of gemini-dev-request@xxxxxxxxxxx
Sent: Dienstag, 7. Mai 2013 18:00
To: gemini-dev@xxxxxxxxxxx
Subject: gemini-dev Digest, Vol 39, Issue 1

Send gemini-dev mailing list submissions to
gemini-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/gemini-dev
or, via email, send a message with subject or body 'help' to
gemini-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
gemini-dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than
"Re: Contents of gemini-dev digest..."


Today's Topics:

  1. Re: Gemini Blueprint 2.0.0 schedule (Glyn Normington)


----------------------------------------------------------------------

Message: 1
Date: Tue, 7 May 2013 10:18:16 +0100
From: Glyn Normington <gnormington@xxxxxxxxxxxxx>
To: Gemini and sub-projects developer discussions
<gemini-dev@xxxxxxxxxxx>
Subject: Re: [gemini-dev] Gemini Blueprint 2.0.0 schedule
Message-ID: <4B7F11F3-5F4A-442E-979B-1A69BB96F2C1@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi Olaf

Any progress on this? The end of May isn't as far off as it was...

Regards,
Glyn


On 4 Apr 2013, at 21:41, Olaf Otto <olaf@xxxxxxx> wrote:

Hi all,

First of all, I'd like to say I'm happy to be on board soon. The
gemini-blueprint project is one of the most valuable open source additions
to the projects I'm involved with and I am looking forward to (hopefully)
help advancing it.

Regarding the test improvements: End of May 2013 seems feasible.
Adding
new dependencies for testing is likely to be the first thing I'll do, thus
getting the CQs done timely should not be an issue. Presumably, those
dependencies are exclusively required for testing (i.e. "works-with" [1]).

I will soon proceed by posting an example of the test conventions and
code
style I'd like to use to see if everyone agrees.

Regards,
Olaf

[1]
http://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Depend
encies

On 04/04/2013 06:00 PM, gemini-dev-request@xxxxxxxxxxx wrote:
Date: Thu, 4 Apr 2013 13:34:10 +0100
From: Glyn Normington <gnormington@xxxxxxxxxx>
To: "gemini-dev@xxxxxxxxxxx developer discussions"
<gemini-dev@xxxxxxxxxxx>
Subject: [gemini-dev] Gemini Blueprint 2.0.0 schedule
Message-ID: <DB79ABD8-8DCD-4866-B193-E392A404109F@xxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

I'm currently aiming for the end of June for Gemini Blueprint 2.0.0
([1])
so that it is available to replace 2.0.0.M01 in the Virgo 3.7.0 line which
is also currently planned to ship in June.

Olaf Otto, who should become a GB committer within about a week, is
proposing some improvements to testing which may involve additional
dependencies and therefore CQs. I'd like to understand whether the
improvements can be made by, say, the end of May 2013 so that I can include
them in the 2.0 release. If not, I may go ahead and prepare the 2.0.0
docuware now and we can add the new test stuff in 2.1.0.

Olaf: would you care to comment please?

Regards,
Glyn
[1] http://projects.eclipse.org/projects/rt.gemini.blueprint

-------------- next part -------------- An HTML attachment was
scrubbed...
URL:
<https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130
404/02306ba1/attachment.html>

------------------------------

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130507/60b
4c4a1/attachment.html>

------------------------------

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev


End of gemini-dev Digest, Vol 39, Issue 1
*****************************************



------------------------------

Message: 3
Date: Thu, 9 May 2013 13:25:52 +0100
From: Glyn Normington <gnormington@xxxxxxxxxxxxx>
To: Gemini and sub-projects developer discussions
<gemini-dev@xxxxxxxxxxx>
Subject: Re: [gemini-dev] gemini-dev Digest, Vol 39, Issue 1
Message-ID: <69D33051-B0DF-4ED5-8FE8-8B3EDD74AACF@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

Thanks Olaf.

Why do you prefer JaCoCo? I'm not averse to using it, but I'd like to
understand.

Some background about how Clover could be used on Hudson:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=331221

Regards,
Glyn




On 9 May 2013, at 12:57, Olaf Otto <olaf@xxxxxxx> wrote:

Hi Glyn

I am about half way through all the testcases of the gemini core. I
will make the first commit once I am through with all of them to avoid
inhomogeneous testing state in a branch actively under development.
However, I just committed the POM with the new dependencies - I am
quite sure these shall suffice for the refactorings. Regarding test
coverage: I found that an old version of clover was once used to
measure code coverage. It is my intention to compare both coverage and
execution time of the tests with the initial test coverage figures to
prevent a drop of test coverage - how about switching to JaCoCo
(http://www.eclemma.org/jacoco/)? The alternative could be to request
an open source license for clover from Atlassian, but I'd prefer the
former solution.

Regards,
Olaf

-----Original Message-----
From: gemini-dev-bounces@xxxxxxxxxxx
[mailto:gemini-dev-bounces@xxxxxxxxxxx]
On Behalf Of gemini-dev-request@xxxxxxxxxxx
Sent: Dienstag, 7. Mai 2013 18:00
To: gemini-dev@xxxxxxxxxxx
Subject: gemini-dev Digest, Vol 39, Issue 1

Send gemini-dev mailing list submissions to
gemini-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/gemini-dev
or, via email, send a message with subject or body 'help' to
gemini-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
gemini-dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific
than
"Re: Contents of gemini-dev digest..."


Today's Topics:

 1. Re: Gemini Blueprint 2.0.0 schedule (Glyn Normington)


----------------------------------------------------------------------

Message: 1
Date: Tue, 7 May 2013 10:18:16 +0100
From: Glyn Normington <gnormington@xxxxxxxxxxxxx>
To: Gemini and sub-projects developer discussions
<gemini-dev@xxxxxxxxxxx>
Subject: Re: [gemini-dev] Gemini Blueprint 2.0.0 schedule
Message-ID: <4B7F11F3-5F4A-442E-979B-1A69BB96F2C1@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi Olaf

Any progress on this? The end of May isn't as far off as it was...

Regards,
Glyn


On 4 Apr 2013, at 21:41, Olaf Otto <olaf@xxxxxxx> wrote:

Hi all,

First of all, I'd like to say I'm happy to be on board soon. The
gemini-blueprint project is one of the most valuable open source
additions to the projects I'm involved with and I am looking forward
to (hopefully) help advancing it.

Regarding the test improvements: End of May 2013 seems feasible.
Adding
new dependencies for testing is likely to be the first thing I'll do,
thus getting the CQs done timely should not be an issue. Presumably,
those dependencies are exclusively required for testing (i.e. "works-with"
[1]).

I will soon proceed by posting an example of the test conventions and
code
style I'd like to use to see if everyone agrees.

Regards,
Olaf

[1]
http://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Depen
d
encies

On 04/04/2013 06:00 PM, gemini-dev-request@xxxxxxxxxxx wrote:
Date: Thu, 4 Apr 2013 13:34:10 +0100
From: Glyn Normington <gnormington@xxxxxxxxxx>
To: "gemini-dev@xxxxxxxxxxx developer discussions"
<gemini-dev@xxxxxxxxxxx>
Subject: [gemini-dev] Gemini Blueprint 2.0.0 schedule
Message-ID: <DB79ABD8-8DCD-4866-B193-E392A404109F@xxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

I'm currently aiming for the end of June for Gemini Blueprint 2.0.0
([1])
so that it is available to replace 2.0.0.M01 in the Virgo 3.7.0 line
which is also currently planned to ship in June.

Olaf Otto, who should become a GB committer within about a week, is
proposing some improvements to testing which may involve additional
dependencies and therefore CQs. I'd like to understand whether the
improvements can be made by, say, the end of May 2013 so that I can
include them in the 2.0 release. If not, I may go ahead and prepare
the 2.0.0 docuware now and we can add the new test stuff in 2.1.0.

Olaf: would you care to comment please?

Regards,
Glyn
[1] http://projects.eclipse.org/projects/rt.gemini.blueprint

-------------- next part -------------- An HTML attachment was
scrubbed...
URL:
<https://dev.eclipse.org/mailman/private/gemini-dev/attachments/2013
0
404/02306ba1/attachment.html>

------------------------------

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

-------------- next part -------------- An HTML attachment was
scrubbed...
URL:
<https://dev.eclipse.org/mailman/private/gemini-dev/attachments/201305
07/60b
4c4a1/attachment.html>

------------------------------

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev


End of gemini-dev Digest, Vol 39, Issue 1
*****************************************

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130509/d4b
2ba80/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pivotal-logo-email-signature.png
Type: image/png
Size: 7498 bytes
Desc: not available
URL:
<https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130509/d4b
2ba80/attachment.png>

------------------------------

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev


End of gemini-dev Digest, Vol 39, Issue 2
*****************************************

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

PNG image

]]> Thu, 09 May 2013 13:36:31 GMT http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00910.html gnormington@xxxxxxx (Glyn Normington) [gemini-dev] Clover / JaCoCo http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00909.html former solution. [1]). -------------- next part -------------- An HTML attachment was scrubbed... URL: &lt;https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130509/d4b 2ba80/attachment.html&gt; -------------- next part -------------- A non-text a... Hi Glyn The main reason I'd prefer JaCoCo is that it is completely open source, hosted on github and published under EPL 1.0 (https://github.com/jacoco/jacoco/blob/master/LICENSE.md), thus I believe it is a better fit for this project. Regards, Olaf -----Original Message----- From: gemini-dev-bounces@xxxxxxxxxxx [mailto:gemini-dev-bounces@xxxxxxxxxxx] On Behalf Of gemini-dev-request@xxxxxxxxxxx Sent: Donnerstag, 9. Mai 2013 14:27 To: gemini-dev@xxxxxxxxxxx Subject: gemini-dev Digest, Vol 39, Issue 2 Send gemini-dev mailing list submissions to gemini-dev@xxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://dev.eclipse.org/mailman/listinfo/gemini-dev or, via email, send a message with subject or body 'help' to gemini-dev-request@xxxxxxxxxxx You can reach the person managing the list at gemini-dev-owner@xxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of gemini-dev digest..." Today's Topics: 1. Gemini Naming 1.0.2.RELEASE is now available (Violeta Georgieva) 2. Re: gemini-dev Digest, Vol 39, Issue 1 (Olaf Otto) 3. Re: gemini-dev Digest, Vol 39, Issue 1 (Glyn Normington) ---------------------------------------------------------------------- Message: 1 Date: Thu, 9 May 2013 09:31:10 +0300 From: Violeta Georgieva <milesg78@xxxxxxxxx> To: Gemini and sub-projects developer discussions <gemini-dev@xxxxxxxxxxx> Subject: [gemini-dev] Gemini Naming 1.0.2.RELEASE is now available Message-ID: <CAFmzfTUkjTynoHcGS3-F5cGPmBmesJ6GqyCLEfXfT48hLdXGPg@xxxxxxxxxxxxxx> Content-Type: text/plain; charset="iso-8859-1" Hi, Gemini Naming has shipped its 1.0.2.RELEASE. The artifacts are available for download [1]. This release contains fix for BZ407399 [2]. The official documentation can be found here [3]. Regards Violeta [1] http://eclipse.org/gemini/naming/download.php [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=407399 [3] http://eclipse.org/gemini/naming/documentation.php -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130509/61f d27d1/attachment.html> ------------------------------ Message: 2 Date: Thu, 9 May 2013 13:57:38 +0200 From: "Olaf Otto" <olaf@xxxxxxx> To: <gemini-dev@xxxxxxxxxxx> Subject: Re: [gemini-dev] gemini-dev Digest, Vol 39, Issue 1 Message-ID: <000901ce4cac$6762fef0$3628fcd0$@x100.de> Content-Type: text/plain; charset="us-ascii" Hi Glyn I am about half way through all the testcases of the gemini core. I will make the first commit once I am through with all of them to avoid inhomogeneous testing state in a branch actively under development. However, I just committed the POM with the new dependencies - I am quite sure these shall suffice for the refactorings. Regarding test coverage: I found that an old version of clover was once used to measure code coverage. It is my intention to compare both coverage and execution time of the tests with the initial test coverage figures to prevent a drop of test coverage - how about switching to JaCoCo (http://www.eclemma.org/jacoco/)? The alternative could be to request an open source license for clover from Atlassian, but I'd prefer the former solution. Regards, Olaf -----Original Message----- From: gemini-dev-bounces@xxxxxxxxxxx [mailto:gemini-dev-bounces@xxxxxxxxxxx] On Behalf Of gemini-dev-request@xxxxxxxxxxx Sent: Dienstag, 7. Mai 2013 18:00 To: gemini-dev@xxxxxxxxxxx Subject: gemini-dev Digest, Vol 39, Issue 1 Send gemini-dev mailing list submissions to gemini-dev@xxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://dev.eclipse.org/mailman/listinfo/gemini-dev or, via email, send a message with subject or body 'help' to gemini-dev-request@xxxxxxxxxxx You can reach the person managing the list at gemini-dev-owner@xxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of gemini-dev digest..." Today's Topics: 1. Re: Gemini Blueprint 2.0.0 schedule (Glyn Normington) ---------------------------------------------------------------------- Message: 1 Date: Tue, 7 May 2013 10:18:16 +0100 From: Glyn Normington <gnormington@xxxxxxxxxxxxx> To: Gemini and sub-projects developer discussions <gemini-dev@xxxxxxxxxxx> Subject: Re: [gemini-dev] Gemini Blueprint 2.0.0 schedule Message-ID: <4B7F11F3-5F4A-442E-979B-1A69BB96F2C1@xxxxxxxxxxxxx> Content-Type: text/plain; charset="iso-8859-1" Hi Olaf Any progress on this? The end of May isn't as far off as it was... Regards, Glyn On 4 Apr 2013, at 21:41, Olaf Otto <olaf@xxxxxxx> wrote: > Hi all, > > First of all, I'd like to say I'm happy to be on board soon. The gemini-blueprint project is one of the most valuable open source additions to the projects I'm involved with and I am looking forward to (hopefully) help advancing it. > > Regarding the test improvements: End of May 2013 seems feasible. > Adding new dependencies for testing is likely to be the first thing I'll do, thus getting the CQs done timely should not be an issue. Presumably, those dependencies are exclusively required for testing (i.e. "works-with" [1]). > > I will soon proceed by posting an example of the test conventions and > code style I'd like to use to see if everyone agrees. > > Regards, > Olaf > > [1] > http://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Depend > encies > > On 04/04/2013 06:00 PM, gemini-dev-request@xxxxxxxxxxx wrote: >> Date: Thu, 4 Apr 2013 13:34:10 +0100 >> From: Glyn Normington <gnormington@xxxxxxxxxx> >> To: "gemini-dev@xxxxxxxxxxx developer discussions" >> <gemini-dev@xxxxxxxxxxx> >> Subject: [gemini-dev] Gemini Blueprint 2.0.0 schedule >> Message-ID: <DB79ABD8-8DCD-4866-B193-E392A404109F@xxxxxxxxxx> >> Content-Type: text/plain; charset="us-ascii" >> >> I'm currently aiming for the end of June for Gemini Blueprint 2.0.0 >> ([1]) so that it is available to replace 2.0.0.M01 in the Virgo 3.7.0 line which is also currently planned to ship in June. >> >> Olaf Otto, who should become a GB committer within about a week, is proposing some improvements to testing which may involve additional dependencies and therefore CQs. I'd like to understand whether the improvements can be made by, say, the end of May 2013 so that I can include them in the 2.0 release. If not, I may go ahead and prepare the 2.0.0 docuware now and we can add the new test stuff in 2.1.0. >> >> Olaf: would you care to comment please? >> >> Regards, >> Glyn >> [1] http://projects.eclipse.org/projects/rt.gemini.blueprint >> >> -------------- next part -------------- An HTML attachment was >> scrubbed... >> URL: >> <https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130 >> 404/02306ba1/attachment.html> >> >> ------------------------------ >> >> _______________________________________________ >> gemini-dev mailing list >> gemini-dev@xxxxxxxxxxx >> https://dev.eclipse.org/mailman/listinfo/gemini-dev > > _______________________________________________ > gemini-dev mailing list > gemini-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/gemini-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130507/60b 4c4a1/attachment.html> ------------------------------ _______________________________________________ gemini-dev mailing list gemini-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/gemini-dev End of gemini-dev Digest, Vol 39, Issue 1 ***************************************** ------------------------------ Message: 3 Date: Thu, 9 May 2013 13:25:52 +0100 From: Glyn Normington <gnormington@xxxxxxxxxxxxx> To: Gemini and sub-projects developer discussions <gemini-dev@xxxxxxxxxxx> Subject: Re: [gemini-dev] gemini-dev Digest, Vol 39, Issue 1 Message-ID: <69D33051-B0DF-4ED5-8FE8-8B3EDD74AACF@xxxxxxxxxxxxx> Content-Type: text/plain; charset="us-ascii" Thanks Olaf. Why do you prefer JaCoCo? I'm not averse to using it, but I'd like to understand. Some background about how Clover could be used on Hudson: https://bugs.eclipse.org/bugs/show_bug.cgi?id=331221 Regards, Glyn On 9 May 2013, at 12:57, Olaf Otto <olaf@xxxxxxx> wrote: > Hi Glyn > > I am about half way through all the testcases of the gemini core. I > will make the first commit once I am through with all of them to avoid > inhomogeneous testing state in a branch actively under development. > However, I just committed the POM with the new dependencies - I am > quite sure these shall suffice for the refactorings. Regarding test > coverage: I found that an old version of clover was once used to > measure code coverage. It is my intention to compare both coverage and > execution time of the tests with the initial test coverage figures to > prevent a drop of test coverage - how about switching to JaCoCo > (http://www.eclemma.org/jacoco/)? The alternative could be to request > an open source license for clover from Atlassian, but I'd prefer the former solution. > > Regards, > Olaf > > -----Original Message----- > From: gemini-dev-bounces@xxxxxxxxxxx > [mailto:gemini-dev-bounces@xxxxxxxxxxx] > On Behalf Of gemini-dev-request@xxxxxxxxxxx > Sent: Dienstag, 7. Mai 2013 18:00 > To: gemini-dev@xxxxxxxxxxx > Subject: gemini-dev Digest, Vol 39, Issue 1 > > Send gemini-dev mailing list submissions to > gemini-dev@xxxxxxxxxxx > > To subscribe or unsubscribe via the World Wide Web, visit > https://dev.eclipse.org/mailman/listinfo/gemini-dev > or, via email, send a message with subject or body 'help' to > gemini-dev-request@xxxxxxxxxxx > > You can reach the person managing the list at > gemini-dev-owner@xxxxxxxxxxx > > When replying, please edit your Subject line so it is more specific > than > "Re: Contents of gemini-dev digest..." > > > Today's Topics: > > 1. Re: Gemini Blueprint 2.0.0 schedule (Glyn Normington) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 7 May 2013 10:18:16 +0100 > From: Glyn Normington <gnormington@xxxxxxxxxxxxx> > To: Gemini and sub-projects developer discussions > <gemini-dev@xxxxxxxxxxx> > Subject: Re: [gemini-dev] Gemini Blueprint 2.0.0 schedule > Message-ID: <4B7F11F3-5F4A-442E-979B-1A69BB96F2C1@xxxxxxxxxxxxx> > Content-Type: text/plain; charset="iso-8859-1" > > Hi Olaf > > Any progress on this? The end of May isn't as far off as it was... > > Regards, > Glyn > > > On 4 Apr 2013, at 21:41, Olaf Otto <olaf@xxxxxxx> wrote: > >> Hi all, >> >> First of all, I'd like to say I'm happy to be on board soon. The > gemini-blueprint project is one of the most valuable open source > additions to the projects I'm involved with and I am looking forward > to (hopefully) help advancing it. >> >> Regarding the test improvements: End of May 2013 seems feasible. >> Adding > new dependencies for testing is likely to be the first thing I'll do, > thus getting the CQs done timely should not be an issue. Presumably, > those dependencies are exclusively required for testing (i.e. "works-with" [1]). >> >> I will soon proceed by posting an example of the test conventions and >> code > style I'd like to use to see if everyone agrees. >> >> Regards, >> Olaf >> >> [1] >> http://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Depen >> d >> encies >> >> On 04/04/2013 06:00 PM, gemini-dev-request@xxxxxxxxxxx wrote: >>> Date: Thu, 4 Apr 2013 13:34:10 +0100 >>> From: Glyn Normington <gnormington@xxxxxxxxxx> >>> To: "gemini-dev@xxxxxxxxxxx developer discussions" >>> <gemini-dev@xxxxxxxxxxx> >>> Subject: [gemini-dev] Gemini Blueprint 2.0.0 schedule >>> Message-ID: <DB79ABD8-8DCD-4866-B193-E392A404109F@xxxxxxxxxx> >>> Content-Type: text/plain; charset="us-ascii" >>> >>> I'm currently aiming for the end of June for Gemini Blueprint 2.0.0 >>> ([1]) > so that it is available to replace 2.0.0.M01 in the Virgo 3.7.0 line > which is also currently planned to ship in June. >>> >>> Olaf Otto, who should become a GB committer within about a week, is > proposing some improvements to testing which may involve additional > dependencies and therefore CQs. I'd like to understand whether the > improvements can be made by, say, the end of May 2013 so that I can > include them in the 2.0 release. If not, I may go ahead and prepare > the 2.0.0 docuware now and we can add the new test stuff in 2.1.0. >>> >>> Olaf: would you care to comment please? >>> >>> Regards, >>> Glyn >>> [1] http://projects.eclipse.org/projects/rt.gemini.blueprint >>> >>> -------------- next part -------------- An HTML attachment was >>> scrubbed... >>> URL: >>> <https://dev.eclipse.org/mailman/private/gemini-dev/attachments/2013 >>> 0 >>> 404/02306ba1/attachment.html> >>> >>> ------------------------------ >>> >>> _______________________________________________ >>> gemini-dev mailing list >>> gemini-dev@xxxxxxxxxxx >>> https://dev.eclipse.org/mailman/listinfo/gemini-dev >> >> _______________________________________________ >> gemini-dev mailing list >> gemini-dev@xxxxxxxxxxx >> https://dev.eclipse.org/mailman/listinfo/gemini-dev > > -------------- next part -------------- An HTML attachment was > scrubbed... > URL: > <https://dev.eclipse.org/mailman/private/gemini-dev/attachments/201305 > 07/60b > 4c4a1/attachment.html> > > ------------------------------ > > _______________________________________________ > gemini-dev mailing list > gemini-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/gemini-dev > > > End of gemini-dev Digest, Vol 39, Issue 1 > ***************************************** > > _______________________________________________ > gemini-dev mailing list > gemini-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/gemini-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130509/d4b 2ba80/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: pivotal-logo-email-signature.png Type: image/png Size: 7498 bytes Desc: not available URL: <https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130509/d4b 2ba80/attachment.png> ------------------------------ _______________________________________________ gemini-dev mailing list gemini-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/gemini-dev End of gemini-dev Digest, Vol 39, Issue 2 ***************************************** ]]> Thu, 09 May 2013 12:52:05 GMT http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00909.html olaf@xxxxxxx (Olaf Otto) Re: [gemini-dev] gemini-dev Digest, Vol 39, Issue 1 http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00908.html Thanks Olaf.Why do you prefer JaCoCo? I'm not averse to using it, but I'd like to understand.Some background about how Clover could be used on Hudson: https://bugs.eclipse.org/bugs/show_bug.cgi?id=331221 Regards,Glyn On 9 May 2013, at 12:57, Olaf Otto &lt;ola... Thanks Olaf.

Why do you prefer JaCoCo? I'm not averse to using it, but I'd like to understand.

Some background about how Clover could be used on Hudson: https://bugs.eclipse.org/bugs/show_bug.cgi?id=331221

Regards,
Glyn



On 9 May 2013, at 12:57, Olaf Otto <olaf@xxxxxxx> wrote:

Hi Glyn

I am about half way through all the testcases of the gemini core. I will
make the first commit once I am through with all of them to avoid
inhomogeneous testing state in a branch actively under development. However,
I just committed the POM with the new dependencies - I am quite sure these
shall suffice for the refactorings. Regarding test coverage: I found that an
old version of clover was once used to measure code coverage. It is my
intention to compare both coverage and execution time of the tests with the
initial test coverage figures to prevent a drop of test coverage - how about
switching to JaCoCo (http://www.eclemma.org/jacoco/)? The alternative could
be to request an open source license for clover from Atlassian, but I'd
prefer the former solution.

Regards,
Olaf

-----Original Message-----
From: gemini-dev-bounces@xxxxxxxxxxx [mailto:gemini-dev-bounces@xxxxxxxxxxx]
On Behalf Of gemini-dev-request@xxxxxxxxxxx
Sent: Dienstag, 7. Mai 2013 18:00
To: gemini-dev@xxxxxxxxxxx
Subject: gemini-dev Digest, Vol 39, Issue 1

Send gemini-dev mailing list submissions to
gemini-dev@xxxxxxxxxxx

To subscribe or unsubscribe via the World Wide Web, visit
https://dev.eclipse.org/mailman/listinfo/gemini-dev
or, via email, send a message with subject or body 'help' to
gemini-dev-request@xxxxxxxxxxx

You can reach the person managing the list at
gemini-dev-owner@xxxxxxxxxxx

When replying, please edit your Subject line so it is more specific than
"Re: Contents of gemini-dev digest..."


Today's Topics:

  1. Re: Gemini Blueprint 2.0.0 schedule (Glyn Normington)


----------------------------------------------------------------------

Message: 1
Date: Tue, 7 May 2013 10:18:16 +0100
From: Glyn Normington <gnormington@xxxxxxxxxxxxx>
To: Gemini and sub-projects developer discussions
<gemini-dev@xxxxxxxxxxx>
Subject: Re: [gemini-dev] Gemini Blueprint 2.0.0 schedule
Message-ID: <4B7F11F3-5F4A-442E-979B-1A69BB96F2C1@xxxxxxxxxxxxx>
Content-Type: text/plain; charset="iso-8859-1"

Hi Olaf

Any progress on this? The end of May isn't as far off as it was...

Regards,
Glyn


On 4 Apr 2013, at 21:41, Olaf Otto <olaf@xxxxxxx> wrote:

Hi all,

First of all, I'd like to say I'm happy to be on board soon. The
gemini-blueprint project is one of the most valuable open source additions
to the projects I'm involved with and I am looking forward to (hopefully)
help advancing it.

Regarding the test improvements: End of May 2013 seems feasible. Adding
new dependencies for testing is likely to be the first thing I'll do, thus
getting the CQs done timely should not be an issue. Presumably, those
dependencies are exclusively required for testing (i.e. "works-with" [1]).

I will soon proceed by posting an example of the test conventions and code
style I'd like to use to see if everyone agrees.

Regards,
Olaf

[1]
http://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Depend
encies

On 04/04/2013 06:00 PM, gemini-dev-request@xxxxxxxxxxx wrote:
Date: Thu, 4 Apr 2013 13:34:10 +0100
From: Glyn Normington <gnormington@xxxxxxxxxx>
To: "gemini-dev@xxxxxxxxxxx developer discussions"
<gemini-dev@xxxxxxxxxxx>
Subject: [gemini-dev] Gemini Blueprint 2.0.0 schedule
Message-ID: <DB79ABD8-8DCD-4866-B193-E392A404109F@xxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

I'm currently aiming for the end of June for Gemini Blueprint 2.0.0 ([1])
so that it is available to replace 2.0.0.M01 in the Virgo 3.7.0 line which
is also currently planned to ship in June.

Olaf Otto, who should become a GB committer within about a week, is
proposing some improvements to testing which may involve additional
dependencies and therefore CQs. I'd like to understand whether the
improvements can be made by, say, the end of May 2013 so that I can include
them in the 2.0 release. If not, I may go ahead and prepare the 2.0.0
docuware now and we can add the new test stuff in 2.1.0.

Olaf: would you care to comment please?

Regards,
Glyn
[1] http://projects.eclipse.org/projects/rt.gemini.blueprint

-------------- next part -------------- An HTML attachment was
scrubbed...
URL:
<https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130
404/02306ba1/attachment.html>

------------------------------

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130507/60b
4c4a1/attachment.html>

------------------------------

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev


End of gemini-dev Digest, Vol 39, Issue 1
*****************************************

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

PNG image

]]> Thu, 09 May 2013 12:25:55 GMT http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00908.html gnormington@xxxxxxx (Glyn Normington) Re: [gemini-dev] gemini-dev Digest, Vol 39, Issue 1 http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00907.html gemini-blueprint project is one of the most valuable open source additions to the projects I'm involved with and I am looking forward to (hopefully) help advancing it. new dependencies for testing is likely to be the first thing I'll do, thus getting the ... Hi Glyn I am about half way through all the testcases of the gemini core. I will make the first commit once I am through with all of them to avoid inhomogeneous testing state in a branch actively under development. However, I just committed the POM with the new dependencies - I am quite sure these shall suffice for the refactorings. Regarding test coverage: I found that an old version of clover was once used to measure code coverage. It is my intention to compare both coverage and execution time of the tests with the initial test coverage figures to prevent a drop of test coverage - how about switching to JaCoCo (http://www.eclemma.org/jacoco/)? The alternative could be to request an open source license for clover from Atlassian, but I'd prefer the former solution. Regards, Olaf -----Original Message----- From: gemini-dev-bounces@xxxxxxxxxxx [mailto:gemini-dev-bounces@xxxxxxxxxxx] On Behalf Of gemini-dev-request@xxxxxxxxxxx Sent: Dienstag, 7. Mai 2013 18:00 To: gemini-dev@xxxxxxxxxxx Subject: gemini-dev Digest, Vol 39, Issue 1 Send gemini-dev mailing list submissions to gemini-dev@xxxxxxxxxxx To subscribe or unsubscribe via the World Wide Web, visit https://dev.eclipse.org/mailman/listinfo/gemini-dev or, via email, send a message with subject or body 'help' to gemini-dev-request@xxxxxxxxxxx You can reach the person managing the list at gemini-dev-owner@xxxxxxxxxxx When replying, please edit your Subject line so it is more specific than "Re: Contents of gemini-dev digest..." Today's Topics: 1. Re: Gemini Blueprint 2.0.0 schedule (Glyn Normington) ---------------------------------------------------------------------- Message: 1 Date: Tue, 7 May 2013 10:18:16 +0100 From: Glyn Normington <gnormington@xxxxxxxxxxxxx> To: Gemini and sub-projects developer discussions <gemini-dev@xxxxxxxxxxx> Subject: Re: [gemini-dev] Gemini Blueprint 2.0.0 schedule Message-ID: <4B7F11F3-5F4A-442E-979B-1A69BB96F2C1@xxxxxxxxxxxxx> Content-Type: text/plain; charset="iso-8859-1" Hi Olaf Any progress on this? The end of May isn't as far off as it was... Regards, Glyn On 4 Apr 2013, at 21:41, Olaf Otto <olaf@xxxxxxx> wrote: > Hi all, > > First of all, I'd like to say I'm happy to be on board soon. The gemini-blueprint project is one of the most valuable open source additions to the projects I'm involved with and I am looking forward to (hopefully) help advancing it. > > Regarding the test improvements: End of May 2013 seems feasible. Adding new dependencies for testing is likely to be the first thing I'll do, thus getting the CQs done timely should not be an issue. Presumably, those dependencies are exclusively required for testing (i.e. "works-with" [1]). > > I will soon proceed by posting an example of the test conventions and code style I'd like to use to see if everyone agrees. > > Regards, > Olaf > > [1] > http://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Depend > encies > > On 04/04/2013 06:00 PM, gemini-dev-request@xxxxxxxxxxx wrote: >> Date: Thu, 4 Apr 2013 13:34:10 +0100 >> From: Glyn Normington <gnormington@xxxxxxxxxx> >> To: "gemini-dev@xxxxxxxxxxx developer discussions" >> <gemini-dev@xxxxxxxxxxx> >> Subject: [gemini-dev] Gemini Blueprint 2.0.0 schedule >> Message-ID: <DB79ABD8-8DCD-4866-B193-E392A404109F@xxxxxxxxxx> >> Content-Type: text/plain; charset="us-ascii" >> >> I'm currently aiming for the end of June for Gemini Blueprint 2.0.0 ([1]) so that it is available to replace 2.0.0.M01 in the Virgo 3.7.0 line which is also currently planned to ship in June. >> >> Olaf Otto, who should become a GB committer within about a week, is proposing some improvements to testing which may involve additional dependencies and therefore CQs. I'd like to understand whether the improvements can be made by, say, the end of May 2013 so that I can include them in the 2.0 release. If not, I may go ahead and prepare the 2.0.0 docuware now and we can add the new test stuff in 2.1.0. >> >> Olaf: would you care to comment please? >> >> Regards, >> Glyn >> [1] http://projects.eclipse.org/projects/rt.gemini.blueprint >> >> -------------- next part -------------- An HTML attachment was >> scrubbed... >> URL: >> <https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130 >> 404/02306ba1/attachment.html> >> >> ------------------------------ >> >> _______________________________________________ >> gemini-dev mailing list >> gemini-dev@xxxxxxxxxxx >> https://dev.eclipse.org/mailman/listinfo/gemini-dev > > _______________________________________________ > gemini-dev mailing list > gemini-dev@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/gemini-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130507/60b 4c4a1/attachment.html> ------------------------------ _______________________________________________ gemini-dev mailing list gemini-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/gemini-dev End of gemini-dev Digest, Vol 39, Issue 1 ***************************************** ]]> Thu, 09 May 2013 11:57:40 GMT http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00907.html olaf@xxxxxxx (Olaf Otto) [gemini-dev] Gemini Naming 1.0.2.RELEASE is now available http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00906.html Hi,Gemini Naming has shipped its 1.0.2.RELEASE. The artifacts are available for download [1]. This release contains fix for BZ407399 [2].The official documentation can be found here [3]. RegardsVioleta&#xA0;[1] http://eclipse.org/gemini/naming/download.php[2] h...
Hi,

Gemini Naming has shipped its 1.0.2.RELEASE. The artifacts are available for download [1]. This release contains fix for BZ407399 [2].

The official documentation can be found here [3].

Regards
Violeta
 
[1] http://eclipse.org/gemini/naming/download.php
[2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=407399
[3] http://eclipse.org/gemini/naming/documentation.php
]]> Thu, 09 May 2013 06:31:09 GMT http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00906.html milesg78@xxxxxxx (Violeta Georgieva) Re: [gemini-dev] Gemini Blueprint 2.0.0 schedule http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00905.html _______________________________________________gemini-dev mailing listgemini-dev@xxxxxxxxxxxhttps://dev.eclipse.org/mailman/listinfo/gemini-dev Hi Olaf

Any progress on this? The end of May isn't as far off as it was...

Regards,
Glyn


On 4 Apr 2013, at 21:41, Olaf Otto <olaf@xxxxxxx> wrote:

Hi all,

First of all, I'd like to say I'm happy to be on board soon. The gemini-blueprint project is one of the most valuable open source additions to the projects I'm involved with and I am looking forward to (hopefully) help advancing it.

Regarding the test improvements: End of May 2013 seems feasible. Adding new dependencies for testing is likely to be the first thing I'll do, thus getting the CQs done timely should not be an issue. Presumably, those dependencies are exclusively required for testing (i.e. "works-with" [1]).

I will soon proceed by posting an example of the test conventions and code style I'd like to use to see if everyone agrees.

Regards,
Olaf

[1] http://wiki.eclipse.org/Development_Resources/IP/Test_and_Build_Dependencies

On 04/04/2013 06:00 PM, gemini-dev-request@xxxxxxxxxxx wrote:
Date: Thu, 4 Apr 2013 13:34:10 +0100
From: Glyn Normington <gnormington@xxxxxxxxxx>
To: "gemini-dev@xxxxxxxxxxx developer discussions"
	<gemini-dev@xxxxxxxxxxx>
Subject: [gemini-dev] Gemini Blueprint 2.0.0 schedule
Message-ID: <DB79ABD8-8DCD-4866-B193-E392A404109F@xxxxxxxxxx>
Content-Type: text/plain; charset="us-ascii"

I'm currently aiming for the end of June for Gemini Blueprint 2.0.0 ([1]) so that it is available to replace 2.0.0.M01 in the Virgo 3.7.0 line which is also currently planned to ship in June.

Olaf Otto, who should become a GB committer within about a week, is proposing some improvements to testing which may involve additional dependencies and therefore CQs. I'd like to understand whether the improvements can be made by, say, the end of May 2013 so that I can include them in the 2.0 release. If not, I may go ahead and prepare the 2.0.0 docuware now and we can add the new test stuff in 2.1.0.

Olaf: would you care to comment please?

Regards,
Glyn
[1] http://projects.eclipse.org/projects/rt.gemini.blueprint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://dev.eclipse.org/mailman/private/gemini-dev/attachments/20130404/02306ba1/attachment.html>

------------------------------

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev

]]> Tue, 07 May 2013 09:18:19 GMT http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00905.html gnormington@xxxxxxx (Glyn Normington) [gemini-dev] Gemini Web 2.2.2 RELEASE is now available http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00904.html Hi,Gemini Web has shipped 2.2.2 RELEASE. The artifacts are available for download [1] and the release notes are available here [2].RegardsVioleta[1]&#xA0;http://www.eclipse.org/gemini/web/download/ [2]&#xA0;http://www.eclipse.org/gemini/web/download/release-notes/2.... Hi,

Gemini Web has shipped 2.2.2 RELEASE. The artifacts are available for download [1] and the release notes are available here [2].

Regards

Violeta

[1] http://www.eclipse.org/gemini/web/download/
[2] http://www.eclipse.org/gemini/web/download/release-notes/2.2.2.RELEASE.php
]]> Fri, 26 Apr 2013 07:36:29 GMT http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00904.html milesg78@xxxxxxx (Violeta Georgieva) Re: [gemini-dev] Apologies for today's call http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00903.html That's okay. There were only three of us so it was pretty short.
Note that our next call will be May 21.

-Mike

On 23/04/2013 10:15 AM, Kissner, Juergen wrote: 
Please accept my apologies for having missed the Gemini phone call!

Best Regards,
   Jürgen
_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gemini-dev


]]> Tue, 23 Apr 2013 14:39:26 GMT http://dev.eclipse.org/mhonarc/lists/gemini-dev/msg00903.html michael.keith@xxxxxxx (michael keith)