ICEfaces
  1. ICEfaces
  2. ICE-5924

Remove sparkle showcase dependency on icefaces1 el-api.jar

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0-Beta2
          • Fix Version/s: 2.0-Beta2, 2.0.0
          • Component/s: ICE-Components
          • Labels:
            None
          • Environment:
            sparkle

            Description

            I found that the sparkle showcase's build.xml file has a dependency on el-api.jar. Right now it's pointing to the developer's icefaces 1.8.x workplan to find the jar, and should be changed to take it from the new el-api.jar that Ted has added to icefaces2/lib.

              Activity

              Ascending order - Click to sort in descending order
              Mark Collette created issue -
              Mark Collette made changes -
              Field Original Value New Value
              Salesforce Case []
              Fix Version/s 2.0-Beta2 [ 10242 ]
              Affects Version/s 2.0-Beta2 [ 10242 ]
              Affects Version/s 2.0-Alpha3 [ 10032 ]
              Description I found that the sparkle showcase's build.xml file has a dependency on el-api.jar. Right now it's pointing to the developer's icefaces 1.8.x workplan to find the jar, and should be changed to either remove the dependency, or keep the dependency in sparkle, or take it from glimmer.
              		 I found that the sparkle showcase's build.xml file has a dependency on el-api.jar. Right now it's pointing to the developer's icefaces 1.8.x workplan to find the jar, and should be changed to take it from the new el-api.jar that Ted has added to glimmer/lib.
              Assignee Arturo Zambrano [ artzambrano ]
              Mark Collette made changes -
              Salesforce Case []
              Description I found that the sparkle showcase's build.xml file has a dependency on el-api.jar. Right now it's pointing to the developer's icefaces 1.8.x workplan to find the jar, and should be changed to take it from the new el-api.jar that Ted has added to glimmer/lib.
              		 I found that the sparkle showcase's build.xml file has a dependency on el-api.jar. Right now it's pointing to the developer's icefaces 1.8.x workplan to find the jar, and should be changed to take it from the new el-api.jar that Ted has added to icefaces2/lib.
              Ken Fyten made changes -
              Security Private [ 10001 ]
              Ken Fyten made changes -
              Assignee Priority P3
              Ken Fyten made changes -
              Salesforce Case []
              Assignee Priority P3 P2
              Assignee Arturo Zambrano [ artzambrano ] Yip Ng [ yip.ng ]
              Repository Revision Date User Message
              ICEsoft Public SVN Repository #22074 Mon Aug 02 12:45:57 MDT 2010 yip.ng ICE-5924: Remove sparkle showcase dependency on icefaces1 el-api.jar.
              Files Changed
              Commit graph MODIFY /icefaces/scratchpads/sparkle/showcase/test/build.xml
              Hide
              Permalink
              yip.ng added a comment -

              Done. References to glimmer/lib changed to icefaces2/lib as well.

              Show
              yip.ng added a comment - Done. References to glimmer/lib changed to icefaces2/lib as well.
              yip.ng made changes -
              Status Open [ 1 ] Resolved [ 5 ]
              Resolution Fixed [ 1 ]
              Ken Fyten made changes -
              Fix Version/s 2.0.0 [ 10230 ]
              Ken Fyten made changes -
              Status Resolved [ 5 ] Closed [ 6 ]
              Assignee Priority P2

                People

                • Assignee:
                  yip.ng
                  Reporter:
                  Mark Collette
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: