You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In a research project, we analyzed the build file of repositories looking for comments with ready-to-be-addressed SATDs (self-admitted technical debt) that could be addressed. If the underlying issue is already resolved, the related code or comment can be removed or fixed. As we found an instance of this kind of asynchrony in esb/esb-assembly/jboss-fuse-karaf/pom.xml, we decided to report the issue to contribute community.
A comment in esb/esb-assembly/jboss-fuse-karaf/pom.xml file claims that it is workaround for https://issues.apache.org/jira/browse/CXF-5972, and this issue has been closed long ago.
In a research project, we analyzed the build file of repositories looking for comments with ready-to-be-addressed SATDs (self-admitted technical debt) that could be addressed. If the underlying issue is already resolved, the related code or comment can be removed or fixed. As we found an instance of this kind of asynchrony in esb/esb-assembly/jboss-fuse-karaf/pom.xml, we decided to report the issue to contribute community.
A comment in esb/esb-assembly/jboss-fuse-karaf/pom.xml file claims that it is workaround for https://issues.apache.org/jira/browse/CXF-5972, and this issue has been closed long ago.
Comment location:
fuse/esb/esb-assembly/jboss-fuse-karaf/pom.xml
Line 317 in e09e0d3
The text was updated successfully, but these errors were encountered: