2010/11/26 Javier Arias <[email protected]>: > I didn't think on that option, why is it better than having nine modules? I just guessed that the j2me/j2se are very specific to the assemblies you want to create for j2me and j2se. IOW, I guessed that those modules will not be used elsewhere (am I right?). This deep-modular structure allows you to release the whole project in one go. This is correct if you *want* to manage them this way. You can still think about releasing some projects separately, it depends on your release cycle.
> on the other side, is it possible to specify that packaging for one module is > just to > compile (leave the .class files on the target) since packaging for each > platform > will be just one jar. How is it managed by maven? So, if I understood you well, you want to collect the classes in one big jar, right? You have two options: 1. using the pre-defined "jar-with-dependencies" assembly descriptor: http://maven.apache.org/plugins/maven-assembly-plugin/descriptor-refs.html#jar-with-dependencies 2. using the Maven Shade plugin to create an Uberjar: http://maven.apache.org/plugins/maven-shade-plugin/ HTH Antonio --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
