maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl-Heinz Marbaise (JIRA)" <>
Subject [jira] (MEAR-188) Project property cannot be resolved inside <env-entry> element
Date Sun, 15 Jun 2014 12:13:10 GMT


Karl-Heinz Marbaise edited comment on MEAR-188 at 6/15/14 7:11 AM:

After taking a deeper look into that this a bug of the properties-maven-plugin cause if the
properties are being defined within the pom it works with no problem only if the were read
by the properties-maven-plugin it does not work. So it's not a bug for maven-ear-plugin. Create
one for [properties-maven-plugin|].

was (Author: khmarbaise):
This should be handled by maven-filtering component (shared). Currently can't find a simple
solution. Have to dive more into it.

> Project property cannot be resolved inside <env-entry> element
> --------------------------------------------------------------
>                 Key: MEAR-188
>                 URL:
>             Project: Maven Ear Plugin
>          Issue Type: Bug
>    Affects Versions: 2.9
>            Reporter: Maciej Kara?
>             Fix For: 2.10
>         Attachments:
> I have created simple ear project with filters. I want to use different settings for
each environment and those settings should be passed to generated *application.xml* file inside
the *env-entries*. The generation of ear package is done as shown below:
> {code:xml}
>             <plugin>
>                 <artifactId>maven-ear-plugin</artifactId>
>                 <version>2.9</version>
>                 <configuration>
>                     <generateApplicationXml>true</generateApplicationXml>
>                     <version>6</version>
>                     <envEntries>
>                         <env-entry>
>                             <env-entry-name>customProperty</env-entry-name>
>                             <env-entry-type>java.lang.String</env-entry-type>
>                             <env-entry-value>${}</env-entry-value>
>                         </env-entry>
>                     </envEntries>
>                     <applicationName>${}</applicationName>
>                 </configuration>
>             </plugin>
> {code}
> To read maven project properties from external properties file I had to use another plugin:
[properties-maven-plugin|]. It successfully
reads properties from file and sets them as maven project properties, so I can insert them
in pom.xml file using *${}*. It works for most of the pom.xml elements (i.e. *<applicationName>*),
unfortunately it is not successfully looked up when I place it inside *env-entry* element
where I need it. Below is generated *application.xml*.
> {code:xml}
>     <?xml version="1.0" encoding="UTF-8"?>
>     <application xmlns="" xmlns:xsi=""
>         <application-name>default property</application-name>
>         <display-name>test</display-name>
>         <env-entry>
>             <env-entry-name>customProperty</env-entry-name>
>             <env-entry-type>java.lang.String</env-entry-type>
>             <env-entry-value>${}</env-entry-value>
>         </env-entry>
>     </application>
> {code}
> If I put project properties inside the <properties></properties> block everything
works fine, but that doesn't allow me to use filters for *application.xml*.
> I'm attaching maven project with all necessary configuration. I have also submitted an
issue at [Stackoverflow|],
because I didn't have account here.

This message was sent by Atlassian JIRA

View raw message