On Aug 16, 2006, at 4:38 PM, David Blevins wrote:
On Aug 16, 2006, at 3:28 PM, Jason Dillon wrote:

On Aug 16, 2006, at 3:21 PM, David Blevins wrote:
I guess I'd still prefer we do <artifactId>-<version> for the tag names as maven does.

I'm planning on putting <artifactId>-<version> under <artifactId>/ but m2 handles this, all it needs it the root to exist.

I see. When I suggested "specs/tags/<artifactId>-<version>" I hadn't noticed you expand that to "specs/tags/<artifactId>/ <artifactId>-<version>"

Seems like over-organizing as 70% of those directories will have only 1 file in them ever. The ones that do change, change only once or twice a year [1].

Maybe... I don't care either way.


Here's what I mean:

$ grep -A 3 modelVersion */pom.xml | grep artifactId
geronimo-spec-activation/pom.xml- <artifactId>geronimo- activation_1.0.2_spec</artifactId> geronimo-spec-commonj/pom.xml- <artifactId>geronimo- commonj_1.1_spec</artifactId> geronimo-spec-corba-2.3/pom.xml- <artifactId>geronimo- corba_2.3_spec</artifactId> geronimo-spec-corba-3.0/pom.xml- <artifactId>geronimo- corba_3.0_spec</artifactId> geronimo-spec-corba/pom.xml- <artifactId>geronimo-spec-corba</ artifactId> geronimo-spec-ejb/pom.xml- <artifactId>geronimo-ejb_2.1_spec</ artifactId> geronimo-spec-j2ee-connector/pom.xml- <artifactId>geronimo-j2ee- connector_1.5_spec</artifactId> geronimo-spec-j2ee-deployment/pom.xml- <artifactId>geronimo-j2ee- deployment_1.1_spec</artifactId> geronimo-spec-j2ee-jacc/pom.xml- <artifactId>geronimo-j2ee- jacc_1.0_spec</artifactId> geronimo-spec-j2ee-management/pom.xml- <artifactId>geronimo-j2ee- management_1.0_spec</artifactId> geronimo-spec-j2ee/pom.xml- <artifactId>geronimo-j2ee_1.4_spec</ artifactId> geronimo-spec-javamail-1.3.1/pom.xml- <artifactId>geronimo- javamail_1.3.1_spec</artifactId> geronimo-spec-javamail-1.4/pom.xml- <artifactId>geronimo- javamail_1.4_spec</artifactId> geronimo-spec-jaxr/pom.xml- <artifactId>geronimo-jaxr_1.0_spec</ artifactId> geronimo-spec-jaxrpc/pom.xml- <artifactId>geronimo- jaxrpc_1.1_spec</artifactId> geronimo-spec-jms/pom.xml- <artifactId>geronimo-jms_1.1_spec</ artifactId> geronimo-spec-jsp/pom.xml- <artifactId>geronimo-jsp_2.0_spec</ artifactId> geronimo-spec-jta/pom.xml- <artifactId>geronimo-jta_1.0.1B_spec</ artifactId> geronimo-spec-qname/pom.xml- <artifactId>geronimo-qname_1.1_spec</ artifactId> geronimo-spec-saaj/pom.xml- <artifactId>geronimo-saaj_1.1_spec</ artifactId> geronimo-spec-servlet-2.4/pom.xml- <artifactId>geronimo- servlet_2.4_spec</artifactId> geronimo-spec-servlet-2.5/pom.xml- <artifactId>geronimo- servlet_2.5_spec</artifactId>

Ahh... well that will need to get fixed for sure. The artifactId needs to be the same as the directory name to take advantage of maven's ability to autoconfigure somethings. If they are not in sync, then we end up with extra config to put them in the right place... which is uneeded IMO.

--jason

Reply via email to