Closed mlegenhausen closed 13 years ago
I guess that the root cause of that problem was old meta data of Eclipse. Is that possible? I'd rather have the module names that I chose before. netty-handlerstack for example works with the same pattern, also in Eclipse.
Yes, that was something I thought about too after the changes. Simply revert my changed, but I was also unable to build it with a mvn clean install
, cause the CliUtils
class was in a file that was named CLIUtils
which leads to a compile error. So maybe only revert the pom.xml
changes.
Can you please do so yourself?
There is no saved eclipse meta data that causes the problem. The problem is how m2e imports the project in eclipse. m2e imports the parent project by folder name which is in this case "wsn-device-utils" but imports all modules by artifactId, which leads to a conflict cause the core module has the artifactId wsn-device-utils. So a workaround is to rename the parent project to wsn-device-utils-parent and then import the core.
Ugly. Use IntelliJ ;-)
I think I will give it a try again ;)
A rename of the modules is necessary or the projekt can not be imported by eclipse. I use the same naming schema as in wsn-device-drivers.