How to ignore a Maven plugin -


we have groupid maven plugins:

com.company.maven.plugins

unfortunately, when created first plugin in groupid, used wrong naming convention.

maven-myplugin-plugin

the 1.x versions of plugin used name. when realized wrong changed name meet correct convention.

myplugin-maven-plugin

then updated version 2.x.

in local settings.xml file use plugingroups access plugins command line. particular plugin not have specified in pom file.

unfortunately, when try access plugin command line without scoping name latest version of incorrect naming convention. so, 1.x version.

can tell maven ignore maven-myplugin-plugin artifacts when accessing command line (i.e. mvn myplugin:mygoal)?

some projects still use old 1.x plugins, don't want delete them our repository. also, using @ least maven 3.0.3.

it somehow seems maven3 resolves prefixes plugins in order of

1. maven-myplugin-plugin 2. myplugin-maven-plugin 3. ... hard-wired groups ...

following official naming convention should other way round imho. nevertheless, think not have chance fixed. tried set of things, playing around goalprefix in maven-plugin-plugin config. installing new version of deprecated-named plugin goalprefix did not work. guess 1 thing defining prefix correctly-named plugin, e.g.:

<plugin>     <groupid>org.apache.maven.plugins</groupid>     <artifactid>maven-plugin-plugin</artifactid>     <version>3.2</version>     <configuration>         <skiperrornodescriptorsfound>true</skiperrornodescriptorsfound>         <goalprefix>myplugin2</goalprefix>     </configuration> </plugin>

another approach adjust old plugin's pom.xml, renaming different. imply colleagues need different execute different mvn command. or can rename current plugin - similar results.

if there better solution, interested!


Comments

Post a Comment

Popular posts from this blog

Why does Ruby on Rails generate add a blank line to the end of a file? -

running rails generate controller foo home results in: class foocontroller < application controller def home end end (there's nothing on line in actual file, blank line) is there purpose blank line? it's common use newline indicate end of line, last line. many editors (like vi, use) add in newline silently. consensus text files (especially in unix world) should end in newline, , there have been problems historically if wasn't present. why should text files end newline? the tool used count lines in file "wc" counts newlines in file, without trailing newline show 3 instead of 4. it improves readability of templates used in generator. consider: https://github.com/rails/rails/blob/master/railties/lib/rails/generators/rails/controller/templates/controller.rb to remove trailing newline, template have last line of: end<% end -%> instead of: end <% end -%> that seems less readable me. the discussion below refers
Read more

keyboard - Smiles and long press feature in Android -

i've created android keyboard. how add features inserting smilies, , using long keypresses display symbols? to create long-press behavior allows select several options pop-up menu, follow guide (specifically pop-up menu section): http://developer.android.com/guide/topics/ui/menus.html smileys (also known emoticons) combination of keys, understood programs , parsed same way. have do, when clicks smiley face on keyboard, simulate pressing of key combination matching emoticon. example, when clicks smiley, should simulate key presses ':' , ')' :). here's list of emoticons: http://en.wikipedia.org/wiki/list_of_emoticons
Read more

node.js - Bad Request - node js ajax post -

i'm using express 3.0 , node v0.11.0. have button submits form , i'm using ajax post data json object node server. client code is: $('#contact').submit(function(e) { console.log('submit called'); var formdata = json.stringify($('form').serializeobject()); console.log(formdata); $.ajax({ url: "http://localhost:3000/savedata/", type: "post", datatype: 'json', data: {objectdata: formdata}, contenttype: "application/json", complete: function() { console.log('process complete'); }, success: function(data) { console.log('process sucess'); }, error: function() { console.log('process error'); }, }); return false; }); then on server: var express = require('express'); var app = express(); app.set('views', __dirname + '/views'); app.set('view engine', 'jade'); app.use(express.bodyparser());
Read more