You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Martijn de Bruijn (JIRA)" <ji...@codehaus.org> on 2005/11/17 10:39:06 UTC

[jira] Commented: (MPEAR-17) plugin could generate more elements in application.xml

    [ http://jira.codehaus.org/browse/MPEAR-17?page=comments#action_51204 ] 

Martijn de Bruijn commented on MPEAR-17:
----------------------------------------

Morten,
I've got the same problem with the binding between the WSAD application.xml extentions and the application.xml generated by Maven.
Could you submit your patch? Maybee I an use it to solve my problem.
I think the securoty roles should be configurable for the ear plugin. Something like:
<plugin>
	<groupId>org.apache.maven.plugins</groupId>
	<artifactId>maven-ear-plugin</artifactId>
	<configuration>
		<security>
			<security-role id="SecurityRole_1131964323008">
				<description></description>
				<role-name>manager</role-name>
			</security-role>
			<security-role id="SecurityRole_1131964323018">
				<description></description>
				<role-name>teller</role-name>
			</security-role>
		</security>	
	</configuration>
</plugin>

Thanks.

Martijn de Bruijn

> plugin could generate more elements in application.xml
> ------------------------------------------------------
>
>          Key: MPEAR-17
>          URL: http://jira.codehaus.org/browse/MPEAR-17
>      Project: maven-ear-plugin
>         Type: Improvement
>  Environment: maven-ear-plugin-1.5, maven-1.0-rc3, windows XP SP1
>     Reporter: Charles Crouch
>     Priority: Minor
>  Attachments: plugin.jelly, plugin.jelly.patch
>
>
> The EAR plugin can generate an application.xml containing display-name and module elements but it lacks several others, i.e.
> 1) application/description
> 2) application/security-role/role-name
> The changes described below are quite small and enable the creation of the above elements by specifying more properties, e.g.
> 1) maven.ear.appxml.description=Product ${pom.groupId}, version ${pom.currentVersion}
> 2) maven.ear.appxml.securityRoles=UserRole, AdminRole
> The changes to the plugin.jelly, positioned correctly, would be:
> 1)     <j:set var="applicationDescription" value="${maven.ear.appxml.description}"/>
> 	<j:if test="${!empty(applicationDescription)}">
> 	   <x:element name="description">${maven.ear.appxml.description}</x:element>
>         </j:if >
>      
> 2)       <j:set var="securityRoles" value="${maven.ear.appxml.securityRoles}"/>
> 	 <j:if test="${!empty(securityRoles)}">
> 	 	<util:tokenize var="roles" delim="," trim="true">${maven.ear.appxml.securityRoles}</util:tokenize>
> 	 	<j:forEach var="role" items="${roles}">
> 	 		<x:element name="security-role">
> 	 			<x:element name="role-name">${role.trim()}</x:element>
> 	                 </x:element>
> 	 	</j:forEach>
> 	 </j:if >

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org