[jbosstools-issues] [JBoss JIRA] (JBIDE-17582) Classes with same name screw up code coverage

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-17582?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12975935#comment-12975935 ] 

Mickael Istria commented on JBIDE-17582:
----------------------------------------

This has started to fail recently, so I guess it's caused by a change in Hibernate. Here is the commit that caused the error: https://github.com/jbosstools/jbosstools-hibernate/commit/a72ca810eb3da2851a26256d1741ed2d417cbfb6 . As you can see, it's adding a class that's already existing, Jacoco doesn't like that.
What would it cost to just change the package name? OSGi allowing multiple class with same name isn't really a reason to follow this bad practice.

> Classes with same name screw up code coverage
> ---------------------------------------------
>
>                 Key: JBIDE-17582
>                 URL: https://issues.jboss.org/browse/JBIDE-17582
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build, hibernate
>    Affects Versions: 4.2.0.Beta3
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>            Priority: Blocker
>             Fix For: 4.2.0.Beta3
>
>
> Several bundles contain class with same name:  org/jboss/tools/hibernate/proxy/ConfigurationProxy . Classes with same name are confusing, so that for example, it causes code coverage analysis to fail.
> When copying a class, it's recommended to at least change the package.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)