Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cosmos-dev] Request for approval for defect 205291


I would like to request that the following defect be considered for PMC approval for COSMOS 1.0 i6

205291 ClassNotFound exception in Cosmos web app user interface.  The problem is that the resource modeling jars where renamed and are not packaged in the COSMOS web app driver.  This is a build problem.

1. Explain why you believe this is a stop-ship defect. How does the defect manifest itself, and how will users of COSMOS/ consuming products be affected if the defect is not fixed?
- The COSMOS UI end to end scenario will not present any resources to the user.  

2. Is there a work-around? If so, why do you believe the work-around is insufficient?
- No.

3. Is this a regression or API breakage? Explain.
- Yes.  The resource modelling jars were repackaged and renamed.

4. Does this require new API?
- No.

5. Who performed the code review?
- N/A.  Node code was changed.

6. Is there a test case attached to the bugzilla record?
-
No.

7. What is the risk associated with this fix?
- Low.

8. Is this fix related to any standards that COSMOS adheres to? If so, who has validated that the fix continues to adhere

No.

Thanks,

Sheldon
______________________________________
Sheldon Lee-Loy
Tivoli Autonomic Computing, IBM Toronto Lab
email: sleeloy@xxxxxxxxxx
phone: 905.413.2610

Back to the top