Details
-
Sub-task
-
Resolution: Done
-
Major
-
4.3.1.Final
-
None
-
None
-
MA Sprint 16, MA Sprint 17, MA Sprint 18, Sprint 19, Sprint 20, Sprint 21, Sprint 22
Description
While running Windup 4.3.1 Camel rules on CIA2 source code, I've noticed camel-direct rule clutters the migration issue list a bit.
It mentions 970 times "`camel-direct` has been moved issue" assigning it 970 story points. I see two issues with this:
1] It seems the project contains 222 pom.xml files so I think it should be at most 222 story points if each pom.xml really uses the direct component.
2] The camel-core still exists and still contains camel-direct as a transitive dependency in Camel 3.x. Therefore the code runs as is and this issue is not Mandatory strictly speaking. Would it be better to change the category? E.g "potential" or "information"?
The same applies for rules covering camel-core: camel-file (+700 story points), camel-seda, camel-timer etc...
WDYT mmelko@redhat.com ?
I've attached the report in https://issues.redhat.com/browse/WINDUPRULE-391 referenced here.
