Taglibs should be moved to their own maven 2 project and be deployed to the
maven 2 repository
----------------------------------------------------------------------------------------------
Key: DISPL-346
URL: http://jira.codehaus.org/browse/DISPL-346
Project: DisplayTag
Type: Improvement
Components: Tag Library
Versions: 1.1
Reporter: Cédric Vidal
That way, it will be possible to add taglibs as dependencies in a webapp
project so that the war artifact handler can detect them and put them in the
target/*/WEB-INF/tld/ directory automatically.
A possible naming scheme could be:
- displaytag-taglib-1.1.tld
- displaytag-taglib-el-1.1.tld
The would be referenced the following way:
<dependency>
<groupId>displaytag</groupId>
<artifactId>displaytag</artifactId>
<version>1.1</version>
<type>jar</type>
</dependency>
<dependency>
<groupId>displaytag</groupId>
<artifactId>displaytag-taglib</artifactId>
<version>1.1</version>
<type>tld</type>
</dependency>
<dependency>
<groupId>displaytag</groupId>
<artifactId>displaytag-taglib-el</artifactId>
<version>1.1</version>
<type>tld</type>
</dependency>
I've tried the following scheme, but the war artifact handler messed up with
the classifier:
- displaytag-1.1.tld
- displaytag-1.1-el.tld
Cheers,
Cédric
--
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
_______________________________________________
displaytag-devel mailing list
displaytag-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
