I'm with Christoph on this one. I think people wont like us too much for changing things during minor releases. Maybe we could print a deprecation comment if the original commands are used instead of the new ones helping the users switch.
Kind regards, Andreas On Wed, Mar 5, 2014 at 12:47 AM, Christoph Gritschenberger < [email protected]> wrote: > I think it's a bad idea to _rename_ plugin-goals. That would break > compatibility with 3.0-plugin-configurations. > > Maybe the new names should be provided as aliases and the old names > removed in 4.0 > > kind regards, > christoph > > > On 04/03/14 20:27, Jean-Baptiste Onofré wrote: > >> The refactoring is on master (3.1.x), I don't change on 3.0.x as it's a >> maintenance branch now. >> >> Regards >> JB >> >> On 03/04/2014 07:48 PM, Jamie G. wrote: >> >>> 1a. Refactoring/Renaming goals - on the 3.0.x or for 3.1.x? The >>> shorter names are good, just want a clarification on target. >>> >>> 1b. New Goals - Sounds good. >>> >>> 2. New tests are always welcome :) >>> >>> On Tue, Mar 4, 2014 at 3:09 PM, Jean-Baptiste Onofré <[email protected]> >>> wrote: >>> >>>> Hi all, >>>> >>>> I would like to discuss with you about my current work on the >>>> karaf-maven-plugin: >>>> >>>> 1/ on master, I refactored the karaf-maven-plugin to use the Maven >>>> annotations. It's simpler and cleaner, and compatible with all Maven >>>> version. I also added the Maven 3.1 and 3.2 support. I also fixed the >>>> same >>>> issue as on karaf-3.0.x (see below) and cleanup the code (using global >>>> I propose the following cleanup/refactoring/renaming on the goals: >>>> - karaf:commands-generate-help renamed to karaf:commands-documentation >>>> - karaf:create-instance-archive renamed to karaf:instance-archive >>>> - karaf:features-add-to-repository renamed to karaf:populate-repository >>>> - karaf:features-create-kar renamed to karaf:create-kar >>>> - karaf:features-export-meta-data renamed to karaf:export-metadata >>>> - karaf:features-generate-descriptor renames to karaf:create-features >>>> - karaf:features-validate-descriptor renamed to karaf:validate-features >>>> Introduction of new goals: >>>> - karaf:client to interact with a running instance >>>> - karaf:instance to interact with instances (start, stop, etc) >>>> - karaf:deploy to deploy bundles or features (and eventually populate >>>> the >>>> system repository using scp) >>>> - karaf:run to bootstrap and run a Karaf container >>>> I also merged the scr-karaf-maven-plugin in karaf-maven-plugin as a >>>> dedicated goal (karaf:scr). >>>> 2/ on karaf-3.0.x branch, I introduced a set of new integration tests >>>> (using >>>> the maven-invoker-plugin). I fixed the different issues (construct >>>> global >>>> features set to resolve all features including transitive ones, >>>> support of >>>> file and http URLs, support of <configfile/> in features repository XML, >>>> etc). >>>> >>>> Thoughts ? >>>> >>>> Regards >>>> JB >>>> -- >>>> Jean-Baptiste Onofré >>>> [email protected] >>>> http://blog.nanthrax.net >>>> Talend - http://www.talend.com >>>> >>> >> > >
