Details
-
Type:
New Feature
-
Status: Closed
-
Priority:
Major
-
Resolution: Invalid
-
Affects Version/s: 2.0-Beta2
-
Fix Version/s: None
-
Component/s: Sample Apps
-
Labels:None
-
Environment:sparkle
Description
When using the ICEfaces 2 Component Platform, developers should have access to a mechanism for setting up all the necessary files for creating a sample application, for running their new component, they've already created, or are in the process of creating. A likely way to implement this would be via Maven 2 archetype.
Another use case for this functionality is for IDE integration with IDEs that we don't specifically support, but which do support Maven. In that scenario, we should probably create an ICEfaces 2 compat + sparkle application project.
Another use case for this functionality is for IDE integration with IDEs that we don't specifically support, but which do support Maven. In that scenario, we should probably create an ICEfaces 2 compat + sparkle application project.
Issue Links
- depends on
-
ICE-5324 Develop a Maven 2 archetype for creating ICEfaces 2 projects
-
- Closed
-
Activity
Salesforce Case | [] | |
Fix Version/s | 2.0-Beta2 [ 10242 ] | |
Affects Version/s | 2.0-Beta1 [ 10231 ] | |
Affects Version/s | 2.0-Alpha3 [ 10032 ] | |
Assignee | Judy Guglielmin [ judy.guglielmin ] |
Salesforce Case | [] | |
Affects Version/s | 2.0-Beta2 [ 10242 ] | |
Affects Version/s | 2.0-Beta1 [ 10231 ] |
Link | This issue blocks ICE-5930 [ ICE-5930 ] |
Salesforce Case | [] | |
Description |
When using the ICEfaces 2 Component Platform, developers should have access to a mechanism for setting up all the necessary files for creating a sample application, or test application, for running their new component, they've already created, or are in the process of creating. A likely way to implement this would be via Maven 2 archetype. |
When using the ICEfaces 2 Component Platform, developers should have access to a mechanism for setting up all the necessary files for creating a sample application, for running their new component, they've already created, or are in the process of creating. A likely way to implement this would be via Maven 2 archetype. Another use case for this functionality is for IDE integration with IDEs that we don't specifically support, but which do support Maven. In that scenario, we should probably create an ICEfaces 2 compat + sparkle application project. |
Security | Private [ 10001 ] |
Salesforce Case | [] | |
Fix Version/s | 2.0.0 [ 10230 ] | |
Fix Version/s | 2.0-Beta2 [ 10242 ] |
Salesforce Case | [] | |
Fix Version/s | 2.1 [ 10241 ] | |
Fix Version/s | 2.0.0 [ 10230 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #23762 | Mon Jan 10 13:46:28 MST 2011 | judy.guglielmin | |
Files Changed | ||||
![]() ![]() ![]() |
Fix Version/s | 3.1 [ 10312 ] | |
Fix Version/s | 3.0 [ 10241 ] |
Fix Version/s | 3.1 [ 10312 ] | |
Assignee | Judy Guglielmin [ judy.guglielmin ] |
Status | Open [ 1 ] | Closed [ 6 ] |
Resolution | Invalid [ 6 ] |
Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup.
Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf
If the issue persists with the current ICEfaces release, please create a new JIRA for it.