[jboss-dev-forums] [Design of JBoss Build System] - Re: JBoss Build Status Meeting Notes Feb 1, 2007
pgier
do-not-reply at jboss.com
Fri Feb 2 10:41:23 EST 2007
"pgier" wrote :
| Project artifact naming convention
| Project groupId will be "jboss" for all projects.
| artifactId will be the name of the project or subproject
|
|
We talked yesterday about using the "jboss" prefix for the project names. For example jboss/jboss-common-core vs. jboss/common-core. After thinking about it a little bit, I think that Scott is right that we really don't need the jboss prefix on the maven artifactId. Since the jars will always be downloaded into their appropriate subdirectory, there really isn't an issue of possible name conflicts with other organizations.
The jboss prefix on the artifactId seems redundant. The drawback is that there are already a lot of projects in the repository with jboss prefix in the name so it will take a little bit of work to change them.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010078#4010078
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4010078
More information about the jboss-dev-forums
mailing list