sbteclipse does not respect dependencies order

I have started a new sbt project using Java EE 6 API with Glassfish Embedded for testing purpose.
This is represented by the following dependencies:

"org.glassfish.main.extras" % "glassfish-embedded-all" % "3.1.2.2" % "test",
"javax" % "javaee-api" % "6.0" % "provided"

The order of these dependencies is important for Eclipse since both will be referenced in Eclipse project. Indeed, using sbteclipse, javaee-api appears in first place and will then be used, leading to the error:

"java.lang.ClassFormatError: Absent Code attribute in method that is not native or abstract in class file"

This is because javaee-api only contains an API without the implementation (which is in glassfish-embedded-all).

javaee-api should therefore not be used at all for tests but it is still necessary for sbt to compile the project correctly.

I then thought that it would be great if sbteclipse could respect the dependencies order as it is the case in Maven currently.

Reproduce the issue in sbteclipse with the Java EE and GlassFish dependencies shown, then inspect the generated Eclipse project definition and dependency order. Done means the generated Eclipse configuration preserves the intended dependency order and the reported test class-loading error is avoided.