[ https://issues.apache.org/jira/browse/MEAR-248?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143119#comment-16143119 ]
Hudson commented on MEAR-248: ----------------------------- SUCCESS: Integrated in Jenkins build maven-plugins #9079 (See [https://builds.apache.org/job/maven-plugins/9079/]) [MEAR-248] Support lookup-name in env-entry section o Added lookup-name in env-entry section. (khmarbaise: [http://svn.apache.org/viewvc/?view=rev&rev=1806368]) * (edit) maven-ear-plugin/src/main/java/org/apache/maven/plugins/ear/EnvEntry.java * (edit) maven-ear-plugin/src/main/java/org/apache/maven/plugins/ear/GenerateApplicationXmlMojo.java * (edit) maven-ear-plugin/src/site/apt/examples/specifying-env-entries-for-the-generated-application-xml.apt.vm * (edit) maven-ear-plugin/src/test/java/org/apache/maven/plugins/ear/EnvEntryTest.java > Support lookup-name in env-entry section > ---------------------------------------- > > Key: MEAR-248 > URL: https://issues.apache.org/jira/browse/MEAR-248 > Project: Maven Ear Plugin > Issue Type: New Feature > Affects Versions: 2.10.1 > Reporter: Thomas Seidel > Assignee: Karl Heinz Marbaise > Fix For: 3.0.0 > > > Add support for lookup-name tag in env-entry section to support JNDI lookup. > Currently, this tag is ignored in generated application.xml. > Example: > The pom.xml snippet > {code:xml} > <configuration> > <env-entries> > <env-entry-name>ExampleString</env-entry-name> > <env-entry-type>java.lang.String</env-entry-type> > <lookup-name>java:global/Example</lookup-name> > </env-entries> > </configuration> > {code} > should generate application.xml with > {code:xml} > <env-entry-name>ExampleString</env-entry-name> > <env-entry-type>java.lang.String</env-entry-type> > <lookup-name>java:global/Example</lookup-name> > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)