[gatein-issues] [JBoss JIRA] Resolved: (GTNPORTAL-25) Hardcoded tld jar path and name
[
https://jira.jboss.org/jira/browse/GTNPORTAL-25?page=com.atlassian.jira.p...
]
Dimitri BAELI resolved GTNPORTAL-25.
------------------------------------
Resolution: Done
Hardcoded tld jar path and name
-------------------------------
Key: GTNPORTAL-25
URL: https://jira.jboss.org/jira/browse/GTNPORTAL-25
Project: GateIn Portal
Issue Type: Bug
Reporter: Matt Wringe
Assignee: Dimitri BAELI
Attachments: GTNPORTAL-25-2.patch, GTNPORTAL-25.patch
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
The patched jbossweb.deployers/web.xml file hardcodes the path to the jar containing the
portlet tlds.
(http://svn.exoplatform.org/projects/gatein/portal/trunk/server/jboss/patc...)
Its using the path "../../deploy/exoplatform.ear/pc-portlet-2.1.0-Beta01.jar"
which will fail if jar get updated, the ear changes it name, or a different path is used.
This path needs to be generated during the build instead of being hardcoded in the
source files.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira