geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Blevins <david.blev...@visi.com>
Subject Re: Organization and versioning of specs; a new proposal
Date Thu, 17 Aug 2006 02:42:06 GMT

On Aug 16, 2006, at 5:16 PM, Jason Dillon wrote:

> 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.

Ok, let's go with "specs/tags/<artifactId>-<version>"

>> 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-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.

I agree.

-David

> --jason
>


Mime
View raw message