You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Mamallan Uthaman (JIRA)" <de...@myfaces.apache.org> on 2010/12/22 23:39:01 UTC
[jira] Created: (TRINIDAD-1986) Fix for TRINIDAD-1978 Has Broken
the Trinidad Build
Fix for TRINIDAD-1978 Has Broken the Trinidad Build
---------------------------------------------------
Key: TRINIDAD-1986
URL: https://issues.apache.org/jira/browse/TRINIDAD-1986
Project: MyFaces Trinidad
Issue Type: Bug
Components: Components
Affects Versions: 2.0.0.3-core
Environment: all platforms
Reporter: Mamallan Uthaman
My patch for TRINIDAD-1978 seems to have broken the Trinidad build. While I'm investigating why my patch has broken the build. I will upload a patch to revert the TRINIDAD-1978's fix. Of course, I tested TRINIDAD-1978's patch before applying it. I'm wondering if there is any inconsistency in the Trinidad build process that might have skipped some testing in some scenarios. Example, when the build failure is reported, I reverted TRINIDAD-1978's fix, and the build became successful. But when I again ran the build (mvn clean install) with TRINIDAD-1978's fix, the build succeeded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1986) Fix for TRINIDAD-1978 Has Broken
the Trinidad Build
Posted by "Mamallan Uthaman (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamallan Uthaman updated TRINIDAD-1986:
---------------------------------------
Resolution: Fixed
Fix Version/s: 2.0.0.3-core
Status: Resolved (was: Patch Available)
> Fix for TRINIDAD-1978 Has Broken the Trinidad Build
> ---------------------------------------------------
>
> Key: TRINIDAD-1986
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1986
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 2.0.0.3-core
> Environment: all platforms
> Reporter: Mamallan Uthaman
> Fix For: 2.0.0.3-core
>
> Attachments: TRINIDAD-1986.patch
>
>
> My patch for TRINIDAD-1978 seems to have broken the Trinidad build. While I'm investigating why my patch has broken the build. I will upload a patch to revert the TRINIDAD-1978's fix. Of course, I tested TRINIDAD-1978's patch before applying it. I'm wondering if there is any inconsistency in the Trinidad build process that might have skipped some testing in some scenarios. Example, when the build failure is reported, I reverted TRINIDAD-1978's fix, and the build became successful. But when I again ran the build (mvn clean install) with TRINIDAD-1978's fix, the build succeeded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (TRINIDAD-1986) Fix for TRINIDAD-1978 Has Broken
the Trinidad Build
Posted by "Mamallan Uthaman (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mamallan Uthaman updated TRINIDAD-1986:
---------------------------------------
Status: Patch Available (was: Open)
> Fix for TRINIDAD-1978 Has Broken the Trinidad Build
> ---------------------------------------------------
>
> Key: TRINIDAD-1986
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1986
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 2.0.0.3-core
> Environment: all platforms
> Reporter: Mamallan Uthaman
>
> My patch for TRINIDAD-1978 seems to have broken the Trinidad build. While I'm investigating why my patch has broken the build. I will upload a patch to revert the TRINIDAD-1978's fix. Of course, I tested TRINIDAD-1978's patch before applying it. I'm wondering if there is any inconsistency in the Trinidad build process that might have skipped some testing in some scenarios. Example, when the build failure is reported, I reverted TRINIDAD-1978's fix, and the build became successful. But when I again ran the build (mvn clean install) with TRINIDAD-1978's fix, the build succeeded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (TRINIDAD-1986) Fix for TRINIDAD-1978 Has Broken
the Trinidad Build
Posted by "Mamallan Uthaman (JIRA)" <de...@myfaces.apache.org>.
[ https://issues.apache.org/jira/browse/TRINIDAD-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974422#action_12974422 ]
Mamallan Uthaman commented on TRINIDAD-1986:
--------------------------------------------
The patch is applicable only to the trunk.
> Fix for TRINIDAD-1978 Has Broken the Trinidad Build
> ---------------------------------------------------
>
> Key: TRINIDAD-1986
> URL: https://issues.apache.org/jira/browse/TRINIDAD-1986
> Project: MyFaces Trinidad
> Issue Type: Bug
> Components: Components
> Affects Versions: 2.0.0.3-core
> Environment: all platforms
> Reporter: Mamallan Uthaman
> Attachments: TRINIDAD-1986.patch
>
>
> My patch for TRINIDAD-1978 seems to have broken the Trinidad build. While I'm investigating why my patch has broken the build. I will upload a patch to revert the TRINIDAD-1978's fix. Of course, I tested TRINIDAD-1978's patch before applying it. I'm wondering if there is any inconsistency in the Trinidad build process that might have skipped some testing in some scenarios. Example, when the build failure is reported, I reverted TRINIDAD-1978's fix, and the build became successful. But when I again ran the build (mvn clean install) with TRINIDAD-1978's fix, the build succeeded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.