Hi, The tuscany-bundle-plugin/target/classes/META-INF/maven/plugin.xml usually gives you the list of build goals and parameters. We could add a bit more documents to describe what each goal does.
Ant, I don't think it's a good idea to switch back a binary distribution without OSGi support. If so, do we discard the OSGi enablement for Tuscany? We spent a lot of efforts to make it happen and I think the OASIS compliance tests run with the OSGi mode. Thanks, Raymond ________________________________________________________________ Raymond Feng rf...@apache.org Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com ________________________________________________________________ On Jun 27, 2011, at 4:57 AM, ant elder wrote: > That seems an odd position to me Mike given that we know Tuscany will > become unbuildable unless we do this release. The source code is there > in SVN if you really want to see what it does and write doc from that. > > I've never been that fond of the bundle plugin approach so instead of > spending more time on it I'm going to go look at creating a new > Tuscany binary distribution which doesn't use the bundle plugin so > that if we haven't got this plugin release out by the time the build > breaks we can switch to having the new distribution be the default. > > ...ant > > On Mon, Jun 27, 2011 at 11:14 AM, Mike Edwards > <mike.edwards.inglen...@gmail.com> wrote: >> Ant, >> >> The lack of documentation is the reason I will not vote in favour of this. >> >> Having done releases without documentation before is no justification in my >> opinion. How is anyone supposed to learn how to use something if there is no >> documentation? >> >> I'll be happy to help create documentation, but since I am not an expert in >> this plugin, I don't know what to write. >> >> >> Yours, Mike. >> >> >> On 27/06/2011 10:58, ant elder wrote: >>> >>> No i couldn't because i don't think there is any, and i don't >>> particularly want to have to go write any, does anyone else want to >>> volunteer? We've done half a dozen releases of the plugin before and >>> haven't had to have doc so why should that block this release now >>> especially when we know if we don't do this release its going to end >>> up breaking the Tuscany build. >>> >>> ...ant >>> >>> On Mon, Jun 27, 2011 at 10:44 AM, Florian Moga<moga....@gmail.com> wrote: >>>> >>>> Some documentation would definitely help me. Could you point me some >>>> resources? Thanks. >>>> >>>> On Mon, Jun 27, 2011 at 12:31 PM, ant elder<ant.el...@gmail.com> wrote: >>>>> >>>>> Any votes? Tuscany will become unbuildable if we don't release this to >>>>> fix the naming issue in TUSCANY-3861. Is there anything we can do to >>>>> help get votes for releasing this? >>>>> >>>>> ...ant >>>>> >>>>> On Tue, Jun 21, 2011 at 7:47 AM, ant elder<ant.el...@gmail.com> wrote: >>>>>> >>>>>> Please vote on releasing the Tuscany Bundle Plugin module 1.0.8 (RC1). >>>>>> >>>>>> The change over the 1.0.7 release is to rename the module from >>>>>> maven-bundle-plugin to tuscany-bundle-plugin, see TUSCANY-3861. >>>>>> >>>>>> The tag for the release is: >>>>>> >>>>>> >>>>>> https://svn.apache.org/repos/asf/tuscany/maven-plugins/tags/tuscany-bundle-plugin-1.0.8 >>>>>> >>>>>> The Maven staging repository is: >>>>>> >>>>>> >>>>>> http://people.apache.org/~antelder/tuscany/tuscany-bundle-plugin-1.0.8-RC1 >>>>>> >>>>>> +1 from me. >>>>>> >>>>>> ...ant >>>>>> >>>> >>>> >>> >> >>
