Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 331309 - Ambiguous name between a class and a project
Summary: Ambiguous name between a class and a project
Status: CLOSED FIXED
Alias: None
Product: MoDisco
Classification: Modeling
Component: Main (show other bugs)
Version: 0.9.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 0.9.0 M4   Edit
Assignee: Fabien Giquel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-29 04:32 EST by Stephane Rousseau CLA
Modified: 2011-04-27 11:23 EDT (History)
3 users (show)

See Also:
fabien.giquel: indigo+


Attachments
Patch (1.83 KB, application/octet-stream)
2010-11-29 04:32 EST, Stephane Rousseau CLA
nicolas.bros: iplog+
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephane Rousseau CLA 2010-11-29 04:32:58 EST
Created attachment 184014 [details]
Patch

Hello,

With Modisco 0.9.0 and Eclipse 3.7.0, benchmark test fails on Hudson because of the way of creating the project. In a package, we have a class named JavaDiscovererBenchmarkTest and a subpackage with the same name.

So requesting the object with the qualified name can return the class instead of the package. This makes an error.

Here is a patch to change the name of the package.
Comment 1 Stephane Rousseau CLA 2010-11-29 05:09:59 EST
Hi

(a) I, Stephane Rousseau, wrote 100% of the code I've provided.
(b) I have the right to contribute the code to Eclipse.
(c) I contribute the content under the EPL.
Comment 2 Fabien Giquel CLA 2010-11-29 09:12:38 EST
Thank you for you path.
It is less than 250 loc : no CQ required.
It has been commited into SVN on 0.9 branch (revision 3619)
Comment 3 Hugo Bruneliere CLA 2011-01-11 05:20:36 EST
Bug fixed via a patch.