12:32 p.m.
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
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
2:52 p.m.
New subject: [JBoss JIRA] Assigned: (GTNPORTAL-25) Hardcoded tld jar path and name
[
https://jira.jboss.org/jira/browse/GTNPORTAL-25?page=com.atlassian.jira.p...
]
Dimitri BAELI reassigned GTNPORTAL-25:
--------------------------------------
Assignee: Dimitri BAELI
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
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
4:15 p.m.
New subject: [JBoss JIRA] Updated: (GTNPORTAL-25) Hardcoded tld jar path and name
[
https://jira.jboss.org/jira/browse/GTNPORTAL-25?page=com.atlassian.jira.p...
]
Dimitri BAELI updated GTNPORTAL-25:
-----------------------------------
Attachment: GTNPORTAL-25.patch
Fix using maven resource filtering capabilities
Using non standard delimiter due to a maven issue
http://jira.codehaus.org/browse/MRESOURCES-104 (standalone @ in a file blocks the
filtering)
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.patch
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
4:48 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-25) Hardcoded tld jar path and name
[
https://jira.jboss.org/jira/browse/GTNPORTAL-25?page=com.atlassian.jira.p...
]
Matt Wringe commented on GTNPORTAL-25:
--------------------------------------
the patch wont work, the phase needs to be change to compile instead of package (since the
jar will be created during package and the files will be copied over to the target/classes
during the same phase)
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.patch
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
4:56 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-25) Hardcoded tld jar path and name
[
https://jira.jboss.org/jira/browse/GTNPORTAL-25?page=com.atlassian.jira.p...
]
Dimitri BAELI commented on GTNPORTAL-25:
----------------------------------------
You're right (it was working fine on my computer), I'll change the patch to
perform the resources copy during <phase>process-resources</phase>
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.patch
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
4:59 p.m.
New subject: [JBoss JIRA] Updated: (GTNPORTAL-25) Hardcoded tld jar path and name
[
https://jira.jboss.org/jira/browse/GTNPORTAL-25?page=com.atlassian.jira.p...
]
Dimitri BAELI updated GTNPORTAL-25:
-----------------------------------
Attachment: GTNPORTAL-25-2.patch
Patch with correct maven phase for the execution
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
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
5 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-25) Hardcoded tld jar path and name
[
https://jira.jboss.org/jira/browse/GTNPORTAL-25?page=com.atlassian.jira.p...
]
Dimitri BAELI commented on GTNPORTAL-25:
----------------------------------------
Matt you can commit it and resolve the issue if the fix is satisfaying.
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
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
5:06 p.m.
New subject: [JBoss JIRA] Commented: (GTNPORTAL-25) Hardcoded tld jar path and name
[
https://jira.jboss.org/jira/browse/GTNPORTAL-25?page=com.atlassian.jira.p...
]
Matt Wringe commented on GTNPORTAL-25:
--------------------------------------
I have committed the patch.
The patch only fixes the issue with the hardcoded portlet tld jar name. We are still
hardcoding the name of the ear.
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
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
7:04 p.m.
New subject: [JBoss JIRA] Updated: (GTNPORTAL-25) Hardcoded tld jar path and name
[
https://jira.jboss.org/jira/browse/GTNPORTAL-25?page=com.atlassian.jira.p...
]
Dimitri BAELI updated GTNPORTAL-25:
-----------------------------------
Original Estimate: 0 minutes
Remaining Estimate: 0 minutes
Jar path is a bit harder as there is a directory named "exoplatform.ear" in this
server patch (not this file).
I suggest to open:
* an other issue for having a configurable name that which will be directly related to
GTNPORTAL-23
* an other issue for finding a better solution to not have to create such a deployer with
hard-coded content (may be not targetted to GateIn 3.0)
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
11:26 p.m.
New subject: [JBoss JIRA] Updated: (GTNPORTAL-25) Hardcoded tld jar path and name
[
https://jira.jboss.org/jira/browse/GTNPORTAL-25?page=com.atlassian.jira.p...
]
Dimitri BAELI updated GTNPORTAL-25:
-----------------------------------
2.1.0-Beta01 part is generated
for the ear name, there is no variable for that now (will be studied later on)
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
11:26 p.m.
New subject: [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
5873
days inactive
5882
days old
10 comments
2 participants
participants (2)
-
Dimitri BAELI (JIRA) -
Matt Wringe (JIRA)