ResourceServlet.java._setHeaders() can call response.setContentType() with a
null contentType resulting in an NPE on Websphere.
---
Key: TRINIDAD-1710
[
https://issues.apache.org/jira/browse/TRINIDAD-1710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Kind updated TRINIDAD-1710:
Status: Patch Available (was: Open)
ResourceServlet.java._setHeaders() can call
ResourceServlet.java._setHeaders() can call response.setContentType() with a
null contentType resulting in an NPE on Websphere.
---
Key: TRINIDAD-1629
maven-jdev-plugin: added ability to set JVM Java Options. Default is -ea to
enable assertions
---
Key: TRINIDAD-1590
URL:
[
https://issues.apache.org/jira/browse/TRINIDAD-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Kind updated TRINIDAD-1590:
Status: Patch Available (was: Open)
maven-jdev-plugin: added ability to set JVM Java Options.
[
https://issues.apache.org/jira/browse/TRINIDAD-1477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Kind updated TRINIDAD-1477:
Status: Patch Available (was: Open)
XMLMenuModel GroupNode Functionality Broken
XMLMenuModel GroupNode Functionality Broken
---
Key: TRINIDAD-1477
URL: https://issues.apache.org/jira/browse/TRINIDAD-1477
Project: MyFaces Trinidad
Issue Type: Bug
Affects Versions: 1.2.11-core
[
https://issues.apache.org/jira/browse/TRINIDAD-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Kind updated TRINIDAD-1411:
Status: Patch Available (was: Open)
maven-jdev-plugin has been updated for JDeveloper
maven-jdev-plugin has been updated for JDeveloper 11.1.1.1.0
Key: TRINIDAD-1411
URL: https://issues.apache.org/jira/browse/TRINIDAD-1411
Project: MyFaces Trinidad
Issue Type:
xml schema files (xsd) are added for the XMLMenuModel
-
Key: TRINIDAD-1186
URL: https://issues.apache.org/jira/browse/TRINIDAD-1186
Project: MyFaces Trinidad
Issue Type: Improvement
Allows any node in the whole menu tree to be obtained through its id, unique
or not.
--
Key: TRINIDAD-1183
URL: https://issues.apache.org/jira/browse/TRINIDAD-1183
[
https://issues.apache.org/jira/browse/TRINIDAD-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12607730#action_12607730
]
Gary Kind commented on TRINIDAD-1134:
-
The action attribute, as per the spec, is
[
https://issues.apache.org/jira/browse/TRINIDAD-1127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12606090#action_12606090
]
Gary Kind commented on TRINIDAD-1127:
-
Jim, the destination is to be used to
In order to be extended correctly XMLMenuModel needs to provide API to its
viewIdFocusPathMap.
--
Key: TRINIDAD-956
URL:
[
https://issues.apache.org/jira/browse/TRINIDAD-954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12569370#action_12569370
]
Gary Kind commented on TRINIDAD-954:
Yes that is fine. FYI, the changes to the .xml
Added changes to all the Trinidad components, converters, and validators to
take advantage of the abiltity to put code usage examples in the tagdocs
Support for Code Examples in Trinidad Components, Validators, and Converters
tagdocs
Key: TRINIDAD-953
URL: https://issues.apache.org/jira/browse/TRINIDAD-953
maven-jdev-plugin does not evaluate !DOCTYPE tag correctly for taglib (.tld)
files
Key: TRINIDAD-919
URL: https://issues.apache.org/jira/browse/TRINIDAD-919
Current maven-jdev-plugin does not handle nested maven projects whose packaging
is pom
Key: TRINIDAD-907
URL: https://issues.apache.org/jira/browse/TRINIDAD-907
Added 3 new parameters to the maven-jdev-plugin.
Key: TRINIDAD-893
URL: https://issues.apache.org/jira/browse/TRINIDAD-893
Project: MyFaces Trinidad
Issue Type: Improvement
Without this new project.xml, the maven-jdev-plugin requires project migration
on each usage.
-
Key: TRINIDAD-871
URL: https://issues.apache.org/jira/browse/TRINIDAD-871
[
https://issues.apache.org/jira/browse/TRINIDAD-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549460
]
Gary Kind commented on TRINIDAD-851:
Actually Aino, you must using and looking at the old version of
[
https://issues.apache.org/jira/browse/TRINIDAD-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549488
]
Gary Kind commented on TRINIDAD-177:
I strongly disagree with this. You are breaking desired behavior in the
[
https://issues.apache.org/jira/browse/TRINIDAD-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549484
]
Gary Kind commented on TRINIDAD-846:
I strongly disagree with this. First off, I am looking at the 10.1.3.0.4
[
https://issues.apache.org/jira/browse/TRINIDAD-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12549543
]
Gary Kind commented on TRINIDAD-846:
Another question. the JDev Plugin is only intended to be used for maven
ClassLoaderResourceLoader.findResource can create a path with double forward
slash //
---
Key: TRINIDAD-855
URL: https://issues.apache.org/jira/browse/TRINIDAD-855
[
https://issues.apache.org/jira/browse/TRINIDAD-851?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548825
]
Gary Kind commented on TRINIDAD-851:
The plugin's release can already be set by using the jdev.release
[
https://issues.apache.org/jira/browse/TRINIDAD-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12548818
]
Gary Kind commented on TRINIDAD-846:
When you create a .jpr file, can it be loaded into JDev without
[
https://issues.apache.org/jira/browse/TRINIDAD-843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12546481
]
Gary Kind commented on TRINIDAD-843:
The local tag libraries, if any should be located in your maven project's
After loading a JDeveloper workspace/project created by maven-jdev-plugin,
manual steps are no longer required.
---
Key: TRINIDAD-808
URL:
[
https://issues.apache.org/jira/browse/TRINIDAD-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533196
]
Gary Kind commented on TRINIDAD-758:
After code review by Jeanne Waldman, I have attached 2 new patch files
[
https://issues.apache.org/jira/browse/TRINIDAD-758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12533221
]
Gary Kind commented on TRINIDAD-758:
Fixed one, minor compile issue. Attached 2 new patch files.
failure in
failure in parsing of sub menu models (sharedNodes) results in root menu tree
not being created. Bad sub menu models should just be skipped.
-
EL expression used for node labels gets evaluated only once
---
Key: TRINIDAD-734
URL: https://issues.apache.org/jira/browse/TRINIDAD-734
Project: MyFaces Trinidad
Issue Type: Bug
MenuNode.getLabel() does not handle complex EL expressions correctly
Key: TRINIDAD-718
URL: https://issues.apache.org/jira/browse/TRINIDAD-718
Project: MyFaces Trinidad
[
https://issues.apache.org/jira/browse/TRINIDAD-718?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Kind updated TRINIDAD-718:
---
Status: Patch Available (was: Open)
MenuNode.getLabel() does not handle complex EL expressions
Menu Model is not created if its tree is empty
--
Key: TRINIDAD-101
URL: https://issues.apache.org/jira/browse/TRINIDAD-101
Project: MyFaces Trinidad
Issue Type: Bug
Reporter: Gary
[
https://issues.apache.org/jira/browse/TRINIDAD-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Kind updated TRINIDAD-101:
---
Status: Patch Available (was: Open)
Menu Model is not created if its tree is empty
Attempt to get the value of a custom property from a node that has no custom
properties causes NPE
--
Key: TRINIDAD-102
URL:
[
https://issues.apache.org/jira/browse/TRINIDAD-102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Kind updated TRINIDAD-102:
---
Status: Patch Available (was: Open)
Attempt to get the value of a custom property from a node
Created property that allows RenderKitTestCase to return a testCaseCount that
only includes the actual test cases.
--
Key: TRINIDAD-48
URL:
41 matches
Mail list logo