search

itm / wsn-device-utils

A set of command line utils to reprogram, reset, listen to, ... wireless sensor network devices
2 stars 5 forks source link

Project is not buildable and not compatible with m2e #26

Closed mlegenhausen closed 13 years ago

mlegenhausen commented 13 years ago

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.

danbim commented 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.

mlegenhausen commented 13 years ago

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 CliUtilsclass was in a file that was named CLIUtilswhich leads to a compile error. So maybe only revert the pom.xml changes.

danbim commented 13 years ago

Can you please do so yourself?

mlegenhausen commented 13 years ago

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.

danbim commented 13 years ago

Ugly. Use IntelliJ ;-)

mlegenhausen commented 13 years ago

I think I will give it a try again ;)