[jboss-dev-forums] [Design of JBoss Build System] - Maven project naming conventions
pgier
do-not-reply at jboss.com
Wed Apr 18 16:46:08 EDT 2007
Looking at the snapshots repository, I can imagine the root jboss folder
http://snapshots.jboss.org/maven2/jboss getting large very quickly. Possibly to the point where it is difficult to navigate.
Would it be beneficial to change the naming conventions to group smaller projects together similar to their structure in svn?
For example, instead of the current flat structure common could be grouped like this within the jboss directory:
| /common
| /common/jboss-common-core
| /common/jboss-common-logging-jdk
| /common/jboss-common-logging-log4j
| /common/jboss-common-logging-spi
| /common/jboss-common-xb
|
This way the actual artifact names would still be unique as long as we keep the path in the artifact name.
The javaee project could have a structure like this:
| /javaee/jboss-javaee-ejb-api
| /javaee/jboss-javaee-jacc-api
| /javaee/jboss-javaee-jad-api
| etc...
|
This structure would map a little better to our svn structure, and I think it would be a little easier to navigate.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4038634#4038634
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4038634
More information about the jboss-dev-forums
mailing list