Bug 374660 - Use velocity expressions in descriptor properties
Summary: Use velocity expressions in descriptor properties
Status: RESOLVED FIXED
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: m2e (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: core
Depends on: 336461
Blocks:
  Show dependency tree
 
Reported: 2012-03-19 11:05 EDT by Alex Guerrieri CLA
Modified: 2021-04-19 13:26 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Alex Guerrieri CLA 2012-03-19 11:05:41 EDT 
Build Identifier: 20110916-0149

From maven 2.2 it is possible to use Velocity expressions like:
 
${artifactId.substring(0,1).toUpperCase()}${artifactId.substring(1)}

Maven goal "archetype:generate" creates a project where this expression is resolved from command line.

With eclipse's New Project wizard the expression remains unresolved.


Maven Bug and new Feature:
http://jira.codehaus.org/browse/ARCHETYPE-383

Reproducible: Always

Steps to Reproduce:
1. Create and install a custom archetype that uses velocity expressions in files' content and or files' name.
Comment 1 Igor Fedorenko CLA 2012-03-19 17:42:50 EDT 
This is a new feature introduced in maven archetyper 2.2, according to the JIRA issue you linked. m2e uses archetyper 2.0-alpha-4 and there are no immediate plans to update to a newer version (getting new version of anything is pretty painful @eclipse).
Comment 2 Eclipse Genie CLA 2014-05-22 16:28:57 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 3 Fred Bricon CLA 2015-03-24 14:15:28 EDT 
Fixed with along Bug #336461
Comment 4 Denis Roy CLA 2021-04-19 13:26:39 EDT 
Moved to https://github.com/eclipse-m2e/m2e-core/issues/