Hi, Peter, > > Does this mean that Eclipse users are SOL for now?
> Not per se, > but https://bugs.eclipse.org/bugs/show_bug.cgi?id=225754 is preventing > using Eclipse for now I don't know why this is not fixed (tried latest > Nightly Build) yet since this is just not acceptable. So, for the time > being, either we align project folder names with POM project names, or > we cannot set up Eclipse properly, at least not anything later than > 3.3. It seems they are aiming to get this fixed in 3.4RC1! You can work around this bug. It's a bit tedious (took me over an hour to install my stuff), but you can do it. Just import your projects and change their names. Afterwards, delete the modified .project files and restore them with the ones you used when importing the project to begin with. If you have many projects like: my-package-api or whatever, you can only import one at a time, since they will both be named "api" due to this bug and will therefore cause a conflict. Import one, change the name, import the next, change the name, and so on. This works because (as I assume) the name generated during the import process is decoupled from the .project file, and is apparently not saved in the same place. If you quit and reopn, Eclipse will use the correct names (i.e. the ones you changed to). HTH. So, assuming that this is not the issue, then, you are saying that this stuff should work in Eclipse as well? In other words, it's not tied to the favourite development environment of our esteemed and beloved developers? Cheers, Dave _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
