MetaData parsing

Details

  • Type: Wish Wish
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: None
  • Fix Version/s: 1.1-rc-3
  • Component/s: None
  • Labels:
    None

Description

We need a way to parse metadata at the class, field, property, method level. We should go for .NET / JDK 1.5 format. I'm no expert on this - I think Jon Tirsen seems to know about it. Examples include

[indentity foo, bar]

[pre results.each { i | assert i > 100 }]

So I'm assuming that the syntax is something like [nameOfAttribute ...] where ... can be any groovy expression/statement

Issue Links

duplicates

Sub-task - The sub-task of the issue GROOVY-1715 Annotation support

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.
is depended upon by

Task - A task that needs to be done. GROOVY-753 complete parser

  • Major - Major loss of function.
  • Closed - The issue is considered finished, the resolution is correct. Issues which are not closed can be reopened.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Sam Pullara added a comment -

Attributes are actually just classes with properties. Basically you should allow any class to be used as an attribute and then assign property like this:

[MyAttributeClass(property1=..., property2=...)]

and then be able to process those attributes at runtime. Possibly put in hooks for validation at compile time as well.

Show
Sam Pullara added a comment - Attributes are actually just classes with properties. Basically you should allow any class to be used as an attribute and then assign property like this: [MyAttributeClass(property1=..., property2=...)] and then be able to process those attributes at runtime. Possibly put in hooks for validation at compile time as well.
Hide
Permalink
james strachan added a comment -

We could really use some good documentation on what 1.5 metadata looks like & acts like. I'd like us to follow similar syntax where possible.

Show
james strachan added a comment - We could really use some good documentation on what 1.5 metadata looks like & acts like. I'd like us to follow similar syntax where possible.
Hide
Permalink
Alexandru Popescu added a comment -

I am wondering if annotations are not enough good for this, or would we like something else?

Show
Alexandru Popescu added a comment - I am wondering if annotations are not enough good for this, or would we like something else?
Hide
Permalink
Guillaume Laforge added a comment -

Yes, this old metadata jira issue is related to Java 1.5 metadata.

Show
Guillaume Laforge added a comment - Yes, this old metadata jira issue is related to Java 1.5 metadata.
Hide
Permalink
Guillaume Laforge added a comment -

Standard Java 5 annotations are now supported in Groovy 1.1

Show
Guillaume Laforge added a comment - Standard Java 5 annotations are now supported in Groovy 1.1

People

  • Assignee:
    Guillaume Laforge
    Reporter:
    james strachan
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: