Support arbitrary resource paths in CARs

[hwellmann]

Problem

ceylon compile <module name> fails to put resources into the generated archive, unless the resource paths start with the module path prefix.

Example for module com.acme.foo:

source/com/acme/foo/Foo.ceylon
resource/com/acme/foo/Message.properties
resource/META-INF/services/com.acme.Bar

The resulting CAR contains

com/acme/foo/Foo.class
com/acme/foo/Message.properties

but the META-INF resource is missing.

For Java interoperability, some resources need to be in well-defined places like META-INF/, WEB-INF/, OSGI-INF/ and the like, so the ceylon tool should support arbitrary resource paths.

Possible solutions

When compiling a single module, any resources from the --resource directories can be included into the archive with the unmodified relative path.

This approach does not work well when compiling multiple modules simultaneously, e.g. with resources from ./resource/META-INF being copied to all module archives.

This can be avoided with some kind of relocation default, e.g.

resource/com/acme/module1/ROOT/META-INF/beans.xml
resource/com/acme/module2/ROOT/WEB-INF/web.xml

ending up in

com.acme.module1-1.0.0.car:
META-INF/beans.xml

com.acme.module2-1.0.0.car:
WEB-INF/web.xml

A new option for ceylon compile could be used to override the magic ROOT directory name if someone actually needs to have a ROOT entry in their archive.

[FroMage]

@quintesse can you take a look at this one?

[quintesse]

Done. By default uses the folder ROOT but this is overridable with the --resource-root option. (Btw, setting it to an empty string disables the feature).