On Wed, Sep 22, 2010 at 6:45 PM, Raymond Feng <enjoyj...@gmail.com> wrote: > It's good to not respond right the way :-). > You can find more options at the fields with @parameter: > https://svn.apache.org/repos/asf/tuscany/maven-plugins/trunk/maven-bundle-plugin/src/main/java/org/apache/tuscany/maven/bundle/plugin/ModuleBundlesBuildMojo.java > For the feature poms, we only look at the names starts with > tuscany-feature-. We can enhance it to accept a list of pom projects to > produce feature-specific distributions. > Thanks, > Raymond
Yep Raymond, I found it straight after I posted. Doh;-) Yes, that's what I'd like to have as an option so that we can have a list of features to produce the features subdirectories loaded with appropriate manifest, ant build etc. files that the plugin can already produce. I'd like to get config.ini info in there also but I don't know if you can load Equinox with multiple of these files (if nothing else we can provide them as fragments and people can bolt them together manually. That's going to be better than having to create them manually). I also want to have it so we can also generate the the same info for specific extensions. I happy to conceed that this is a separate list in the first instance per the the post from yesterday [1] so that it's clear to the user when looking at the distro where they go to pick up say an extension like implementation.bpel vs some other feature collection that someone invents. Am making some changes to the plugin to see how this hangs together. Regards Simon [1] http://www.mail-archive.com/dev%40tuscany.apache.org/msg14149.html -- Apache Tuscany committer: tuscany.apache.org Co-author of a book about Tuscany and SCA: tuscanyinaction.com
