On 10/15/05, Brett Porter <[EMAIL PROTECTED]> wrote: > > On 10/16/05, Milos Kleint <[EMAIL PROTECTED]> wrote: > > hmmm.. ok i will try, that came to my mind as well, just wanted to make > it > > easier to use the plugin. any non-central repository plugin's > > usability is seriously hurt IMHO. > > Can you elaborate? Adding a new update center to netbeans is not that > big of a problem...
oh, now we probably misunderstood each other. I was talking about the m2 plugin. there seem to be multiple levels of citizenship in the m2's plugin enviroment. first clas citizens like site, eclipse or war plugins get recognized easily, so you just type m2 "site:site" and it works. with a second class citizen you need to type the groupId:artifactId:version:goal combo to make it run. I do understand the reasoning here and it makes perfect sense, but from useability point of view it's a complication. now if I don't have my plugin in the central repository I become even 3rd class citizen, because someone wanting to use the plugin needs to specify the additional repository in the pom of the project (Am I correct here?) I guess I can overcome that by creating the archetype template and make the setup work correctly. Then everything should work alost out of the box for everyone. Cheers Milos
