Maven Archetype

Use velocity expressions in descriptor properties

Details

  • Type: New Feature New Feature
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.1
  • Fix Version/s: 2.2
  • Component/s: Plugin
  • Labels:
    None
  • Number of attachments :
    1

Description

The descriptor can use velocity expressions for value and defaultValue, thus enabling the creation of velocity global properties for an archetype.
For example :
<requiredProperty key="className">
<defaultValue>$

{rootArtifactId.substring(0,1).toUpperCase()}

$

{rootArtifactId.substring(1)}

</defaultValue>
</requiredProperty>

Issue Links

is related to

Bug - A problem which impairs or prevents the functions of the product. ARCHETYPE-406 Support of velocity expressions for user-defined properties

  • Major - Major loss of function.
  • Open - The issue is open and ready for the assignee to start work on it.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Emmanuel Hugonnet added a comment -

Patch to evaluate properties before the generation of the project

Show
Emmanuel Hugonnet added a comment - Patch to evaluate properties before the generation of the project
Hide
Permalink
Emmanuel Hugonnet added a comment -

This fixes the feature although I don't see the rootArtifactId in the context so I had to use the following expression : $

{artifactId.substring(0,1).toUpperCase()}

$

{artifactId.substring(1)}
Show
Emmanuel Hugonnet added a comment - This fixes the feature although I don't see the rootArtifactId in the context so I had to use the following expression : $ {artifactId.substring(0,1).toUpperCase()} $ {artifactId.substring(1)}
Hide
Permalink
Olivier Lamy added a comment -

maybeVelocityExpression test only contains $, I will add contains on ${

Show
Olivier Lamy added a comment - maybeVelocityExpression test only contains $, I will add contains on ${
Hide
Permalink
Olivier Lamy added a comment -

fixed r1194889
Thanks!

Show
Olivier Lamy added a comment - fixed r1194889 Thanks!
Hide
Permalink
Bue Pierre-Christophe added a comment -

the bug fiw worked fine for standard properties (artifactId, groupId, ...), but still does not work with user defined properties. For example:

<requiredProperty key="a">
<defaultValue>$

{artifactId}

.substring(0,1).toUpperCase()</defaultValue>
</requiredProperty>

with artifactId=toto will give a=T, but

<requiredProperty key="b"/>
<requiredProperty key="a">
<defaultValue>$

{b}.substring(0,1).toUpperCase()</defaultValue>
</requiredProperty>

with b=toto will give a=${b}

.substring(0,1).toUpperCase()

Show
Bue Pierre-Christophe added a comment - the bug fiw worked fine for standard properties (artifactId, groupId, ...), but still does not work with user defined properties. For example: <requiredProperty key="a"> <defaultValue>$ {artifactId} .substring(0,1).toUpperCase()</defaultValue> </requiredProperty> with artifactId=toto will give a=T, but <requiredProperty key="b"/> <requiredProperty key="a"> <defaultValue>$ {b}.substring(0,1).toUpperCase()</defaultValue> </requiredProperty> with b=toto will give a=${b} .substring(0,1).toUpperCase()
Hide
Permalink
Björn Pollex added a comment -

This definitely deserves a reopen to make it work for user-defined properties.

Show
Björn Pollex added a comment - This definitely deserves a reopen to make it work for user-defined properties.
Hide
Permalink
Olivier Lamy added a comment -

please reopen an other issue.

Show
Olivier Lamy added a comment - please reopen an other issue.
Hide
Permalink
Bue Pierre-Christophe added a comment -

done with ARCHETYPE-406

Show
Bue Pierre-Christophe added a comment - done with ARCHETYPE-406

People

  • Assignee:
    Olivier Lamy
    Reporter:
    Emmanuel Hugonnet
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: