+0.5 on maven I am a bit indifferent, but I think that a package should be version agnostic, and only be used for area of functionality. The JAR should be version specific.
Don't you think that it would be invalid to import maven1 and maven2 jars at the same time? So I would see as the package: org.apache.myfaces.buildtools.maven And the release as something like: apache-myfaces-maven1-1.x.x with dependency on maven 1 and apache-myfaces-maven2-1.x.x with dependency on maven 2 and apache-myfaces-maven3-1.x.x with dependency on maven 3. So the artifact ID would have the maven version somewhere in it. -Andrew On Dec 21, 2007 6:48 AM, Manfred Geiler <[EMAIL PROTECTED]> wrote: > maven2 is ok I think > > at least it makes sure we have a namespace for incompatible maven3 > plugins in the future... ;-) > > --Manfred > > > > On 12/21/07, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > Hi, > > > > should we always start with this package ? > > > > org.apache.myfaces.buildtools.maven2 > > > > or > > > > org.apache.myfaces.buildtools.maven > > > > than > > > > -plugin.wagon > > -plugin.jdev > > -plugin.faces > > -plugin.javascript > > > > that would be similar to the maven-plugins, provided by the maven-folks; > > > > not really sure on maven vs maven2 > > > > thx! > > Matthias > > > > -- > > Matthias Wessendorf > > > > further stuff: > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > mail: matzew-at-apache-dot-org > > > > > -- > http://www.irian.at > Your JSF powerhouse - JSF Consulting, > Development and Courses in English and > German > > Professional Support for Apache MyFaces >
