Back to bug 1007055
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Zuzana Krejčová | 2013-09-12 07:51:26 UTC | Blocks | 1006308 | |
| Pedro Zapata | 2013-09-12 08:15:20 UTC | CC | pzapataf | |
| Pedro Zapata | 2013-09-12 08:17:28 UTC | Assignee | msalatin | wmedvede |
| Edson Tirelli | 2013-09-13 15:27:58 UTC | Status | NEW | ASSIGNED |
| CC | etirelli | |||
| Assignee | wmedvede | etirelli | ||
| Anne-Louise Tangring | 2013-09-13 17:22:58 UTC | CC | atangrin | |
| Mario Fusco | 2013-09-16 15:00:57 UTC | CC | mfusco | |
| Assignee | etirelli | mfusco | ||
| Walter Medvedeo | 2013-09-16 15:42:08 UTC | CC | wmedvede | |
| Rajesh Rajasekaran | 2013-09-17 13:12:42 UTC | CC | rrajasek | |
| Target Milestone | --- | ER4 | ||
| Mario Fusco | 2013-09-17 13:26:57 UTC | Status | ASSIGNED | MODIFIED |
| John Skeoch | 2013-10-01 05:55:46 UTC | Target Release | --- | 6.0.0 |
| Walter Medvedeo | 2013-10-07 07:58:21 UTC | CC | wmedvede | |
| Walter Medvedeo | 2013-10-07 07:59:59 UTC | CC | wmedvede | |
| Ryan Zhang | 2013-10-12 09:48:58 UTC | Status | MODIFIED | ON_QA |
| Lukáš Petrovický | 2013-10-17 07:50:36 UTC | Severity | unspecified | urgent |
| Radovan Synek | 2013-10-18 08:19:58 UTC | CC | rsynek | |
| QA Contact | mbaluch | rsynek | ||
| Radovan Synek | 2013-10-18 10:41:28 UTC | Status | ON_QA | ASSIGNED |
| Edson Tirelli | 2013-10-18 13:12:54 UTC | Priority | unspecified | high |
| Prakash Aradhya | 2013-10-21 16:00:59 UTC | CC | paradhya | |
| Mario Fusco | 2013-10-22 08:55:39 UTC | Assignee | mfusco | wmedvede |
| Walter Medvedeo | 2013-10-23 14:21:28 UTC | Status | ASSIGNED | MODIFIED |
| Walter Medvedeo | 2013-10-24 10:06:23 UTC | Doc Text | Additional verification was added in order to detect mal formed .jars like the cigna.jar as earlier as possible. Typically when we manage the dependencies for a given project. When we set the dependencies for a project and save it, the project is compiled. At this moment we will try to detect also errors in the dependencies .jar files. Obviously an external .jar file can have whatever thing, and eventually can come from whatever origin. So it can always have errors that we cant detect, etc. With the verification added we can at least detect some mal formed cases like the cigna.jar and give some feedback to the user in the "Problems" widget. When the user saves the project, If we detect an error in the dependencies jars It will be informed in the "Problems" widget. In the attached screen I show the error message that the user will get when he updates de dependencies for a proyect using the cigna.jar file. (You must save the project in order to materialize the changes and do the internal verification) Responding the previous query, a "well formed .jar file" in this context is a .jar file that don't have missing clases like the cignar.jar. The cigna.jar file isn't well formed, because it have the following scenario. A class X uses a class Y, but the class Y is not in the .jar file, and that's why this cigna.jar file generates the error. |
|
| Vikram Goyal | 2013-10-26 06:07:24 UTC | CC | vigoyal | |
| Doc Text | Additional verification was added in order to detect mal formed .jars like the cigna.jar as earlier as possible. Typically when we manage the dependencies for a given project. When we set the dependencies for a project and save it, the project is compiled. At this moment we will try to detect also errors in the dependencies .jar files. Obviously an external .jar file can have whatever thing, and eventually can come from whatever origin. So it can always have errors that we cant detect, etc. With the verification added we can at least detect some mal formed cases like the cigna.jar and give some feedback to the user in the "Problems" widget. When the user saves the project, If we detect an error in the dependencies jars It will be informed in the "Problems" widget. In the attached screen I show the error message that the user will get when he updates de dependencies for a proyect using the cigna.jar file. (You must save the project in order to materialize the changes and do the internal verification) Responding the previous query, a "well formed .jar file" in this context is a .jar file that don't have missing clases like the cignar.jar. The cigna.jar file isn't well formed, because it have the following scenario. A class X uses a class Y, but the class Y is not in the .jar file, and that's why this cigna.jar file generates the error. | Summary: Instead of the system informing the user about a JAR with unsatisfied dependencies, the system allows the upload of the JAR into a project. This then causes various issues in the Data Modeler, Guided Rules Editor and the Guided Decision Table with the Project unable to be used due to the unsatisfied dependency. | ||
| John Skeoch | 2013-10-29 06:07:34 UTC | Target Milestone | ER4 | ER5 |
| Ryan Zhang | 2013-11-22 13:50:48 UTC | Status | MODIFIED | ON_QA |
| Radovan Synek | 2013-12-03 12:19:21 UTC | Status | ON_QA | VERIFIED |
| Rajesh Rajasekaran | 2014-08-06 20:09:13 UTC | See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1049674 | |
| See Also | https://bugzilla.redhat.com/show_bug.cgi?id=1063742 | |||
| Status | VERIFIED | CLOSED | ||
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-08-06 16:09:13 UTC |
Back to bug 1007055