headers
Merlyn Albery-Speyer | 1 Dec 2009 03:34
Picon
Gravatar

Re: [groovy-dev] Automated testing of Groovy assertions in javadoc comments

True. There's no strict need for it to be part of Groovy. I could open
source it as a separate project I guess.

On Mon, Nov 30, 2009 at 10:28 AM, Hamlet D'Arcy <hamletdrc@...> wrote:
> I think this is a cool idea. PyTest is something similar from the
> Python world, right?
>
> Merlyn, could this be written as a Groovy library or does it require
> to be part of the Groovy language?
>
> --
> Hamlet D'Arcy
> hamletdrc@...
>
>
>
> On Sun, Nov 29, 2009 at 7:10 PM, Merlyn Albery-Speyer
> <curious.attempt.bunny@...> wrote:
>> Hi all,
>>
>> I've just submitted a patch for a TestSuite that can be used to
>> automate the testing of Groovy assertions in javadoc comments. It's
>> borrows conventions from the AllTestSuite and generates TestCases
>> based on code fragments nested inside a <pre class="groovyTestCase>
>> tag. I had intended to use it as a way to insure that code that I
>> added to document default Groovy methods was valid. However, it could
>> be a more general tool. What do you think? See
>> http://jira.codehaus.org/browse/GROOVY-3913
>>
>> Cheers,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Guillaume Laforge | 2 Dec 2009 12:55
Picon
Gravatar

[groovy-dev] Heads-up: Groovy 1.6.7 coming

Hi developers,

We're going to roll out a 1.6.7 version in the coming hours.
Grails had a problem related to this JIRA issue:
http://jira.codehaus.org/browse/GROOVY-3557
We needed to rollback the change on the 1.6.X branch, but it wasn't
done in 1.6.6.
So we're going to release 1.6.7 with this update, so Grails can be
released with this change.

--

-- 
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 0 comments |
headers
Guillaume Laforge | 2 Dec 2009 14:21
Picon
Gravatar

[groovy-dev] Groovy 1.6.7

Hi all,

Due to a needed fix for the next major release of Grails, we had to
make a new release of our Groovy 1.6 branch.

Groovy 1.6.7 has just been deployed and is available to download:
http://groovy.codehaus.org/Download?nc

Groovy 1.6.7 is a drop-in replacement for 1.6.6, so you can just
upgrade to 1.6.7 directly, or replace 1.6.6 with 1.6.7 in your
projects.

Thanks a lot for your attention.

--

-- 
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 2 comments |
headers
Lubomir Rintel | 3 Dec 2009 19:16
Picon
Picon
Gravatar

[groovy-dev] Groovy's License

Hi all,

During a review of Groovy package [1] into Fedora Package collection, a
reviewer complained that the distribution does not contain full text of
the license and some files do not have comments which would determine
the licensing conditions.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=534168#c8

To avoid confusion it's usually a good practice to include a file with
license text and add a header that would say where to find the license
text. I'm wondering if it would be possible for you to do that for the
next release?

Thank you in advance,
Lubo

--

-- 
Flash is the Web2.0 version of blink and animated gifs.
                                     -- Stephen Smoogen

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 2 comments |
headers
Andres Almiray | 3 Dec 2009 20:41
Picon
Favicon
Gravatar

[groovy-dev] Piggyback on an AST Transform


Hi devs, the following occurred to me after working with GfxBuilder and the
recent griffon-gorm plugin for Griffon.

GfxBuilder literally copies  <at> Bindable with  <at> GfxAttribute for two reasons:
- make the annotation visible at runtime
- add more properties

Grails has an  <at> Entity annotation that decorates a domain class with basic
info. I'm reusing it for griffon-gorm, however I would like to be able to
add more things to annotated classes. 

At this point I don't think duplicating the AST xform code (like GfxBuilder
did) is a good reason anymore. I think it would be better to have a
"secondary" set of AST xforms that can be applied after the primary one, the
only problem I see right now is how these secondary AST xforms could be
registered as primaries can be global or local.

Thoughts?

PS: these feature (if approved) should make it to 1.8 of course (and
hopefully 1.7.1, pretty please!)
--

-- 
View this message in context: http://old.nabble.com/Piggyback-on-an-AST-Transform-tp26631907p26631907.html
Sent from the groovy - dev mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
(Continue reading)

Permalink | Reply | 8 comments |
headers
Hamlet D'Arcy | 3 Dec 2009 20:53
Picon

Re: [groovy-dev] Groovy's License

I'll create a JIRA for this.

(and I like the poster's signature line :)

-- 
Hamlet D'Arcy
hamletdrc@...

On Thu, Dec 3, 2009 at 12:16 PM, Lubomir Rintel <lkundrak@...> wrote:
> Hi all,
>
> During a review of Groovy package [1] into Fedora Package collection, a
> reviewer complained that the distribution does not contain full text of
> the license and some files do not have comments which would determine
> the licensing conditions.
>
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=534168#c8
>
> To avoid confusion it's usually a good practice to include a file with
> license text and add a header that would say where to find the license
> text. I'm wondering if it would be possible for you to do that for the
> next release?
>
> Thank you in advance,
> Lubo
>
> --
> Flash is the Web2.0 version of blink and animated gifs.
>                                     -- Stephen Smoogen
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Paul King | 3 Dec 2009 21:10
Picon
Favicon
Gravatar

Re: [groovy-dev] Groovy's License


It has been my understanding that the Apache recommendations
are to point to their site for the full wording. The Apache 2
license being widely known. Have you seen recommendations
other that that?

The source files without comments obviously needs to be addressed.

Cheers, Paul.

Lubomir Rintel wrote:
> Hi all,
> 
> During a review of Groovy package [1] into Fedora Package collection, a
> reviewer complained that the distribution does not contain full text of
> the license and some files do not have comments which would determine
> the licensing conditions.
> 
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=534168#c8
> 
> To avoid confusion it's usually a good practice to include a file with
> license text and add a header that would say where to find the license
> text. I'm wondering if it would be possible for you to do that for the
> next release?
> 
> Thank you in advance,
> Lubo
> 

---------------------------------------------------------------------
(Continue reading)

Permalink | Reply | 0 comments |
headers
Guillaume Laforge | 4 Dec 2009 13:10
Picon
Gravatar

[groovy-dev] Release dates for 1.7

Hi all,

We've updated the roadmap page a bit:
http://groovy.codehaus.org/Roadmap

Especially, please note the target dates for the upcoming releases for 1.7.

We're planning to do 1.7-RC-2 on December 9th.
And if all goes well, right in time for Christmas, the final release
on December 22nd.

--

-- 
Guillaume Laforge
Groovy Project Manager
Head of Groovy Development at SpringSource
http://www.springsource.com/g2one

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 0 comments |
headers
Jason Dillon | 5 Dec 2009 13:56
Gravatar

[groovy-dev] Jansi and groovysh

Does anyone mind if I update groovysh to use Jansi ( http://jansi.fusesource.org/ ) which provides better
ANSI support under Windows?  Users actually get color if they include the JNA (
https://jna.dev.java.net/ ) jar in the classpath.  Unfortunatly its LGPL at the moment so users will have
to install it manually, but even w/o the JNA bits the shell will not spit out gunk when ANSI is enabled.

Shall we do this before 1.7 is out?

--jason
---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email
Permalink | Reply | 15 comments |
headers
Guillaume Laforge | 5 Dec 2009 14:17
Gravatar

Re: [groovy-dev] Jansi and groovysh

Hi Jason,

I've been eyeing on jansi and had heard they were supporting ANSI on
Windows, which is good.
I've not looked closely enough, it's as much featureful? Nothing we
lose by moving to jansi?

Regarding 1.7, no, it's out of question, it's really too late in the
game for including it, unfortunately.

Guillaume

On Sat, Dec 5, 2009 at 13:56, Jason Dillon <jason@...> wrote:
> Does anyone mind if I update groovysh to use Jansi ( http://jansi.fusesource.org/ ) which provides
better ANSI support under Windows?  Users actually get color if they include the JNA (
https://jna.dev.java.net/ ) jar in the classpath.  Unfortunatly its LGPL at the moment so users will
have to install it manually, but even w/o the JNA bits the shell will not spit out gunk when ANSI is enabled.
>
> Shall we do this before 1.7 is out?
>
> --jason
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>
>

--

--
(Continue reading)

Permalink | Reply | 14 comments |

Gmane