Thanks Brett, that sounds reasonable regarding the naming.
Thanks also for pointing me to mojo.codehaus.org, but this is an m1 plugin.
It looks like that's only for m2 plugins.
Regarding setting up the maven site docs on java.net, I noticed another
posting on this list (although related to m2) ab
net.java.project-name seems appropriate.
I am currently in discussions with some folks about creating a sync
form the java.net maven repository (though its only for m1 at this
point).
- Brett
On 1/10/06, Charles Daniels <[EMAIL PROTECTED]> wrote:
> Apache License 2.0, source will be available, d
How will the plugin be licensed? Is it intended to just be a binary
distribution or will the source be available? Where will be the
documentation be? How will people find out about it?
I think your choice is probably influenced by these questions. One
option, of course, is to propose it to mojo.co
Hi All,
I am creating a plugin that I plan to eventually make available on ibiblio.
In reading the instructions on creating an upload bundle (see
http://maven.apache.org/maven-1.x/reference/repository-upload.html), I see
that new projects must follow the package name rules and that the name must
b
