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 Fri, 11 Aug 2006 19:32:37 GMT
Great proposal, I like this.  Comment below...

On Aug 11, 2006, at 12:15 PM, Jason Dillon wrote:
[...]
>
> So, here is what I propose:
>
>     specs/trunk/pom.xml
>     specs/trunk/<artifactId>
>     specs/tags/<artifactId>/<version>

Have you thought about using specs/tags/<artifactId>-<version> for  
the tag names?  That's what maven does, so I'm guessing you noticed  
and didn't like it for some reason.

-David

> This is a single trunk so to build all specs:
>
>     svn co https://svn.apache.org/repos/asf/geronimo/specs/trunk/  
> specs
>     cd specs
>     mvn install
>
> To release an individual spec, say geronimo-spec-jms:
>
>     cd specs/geronimo-spec-jms
>     mvn release
>
> The m2 release plugin can be configured with a _tag base_, which we  
> can set to:
>
>     https://svn.apache.org/repos/asf/geronimo/specs/tags/$ 
> {pom.artifactId}
>
> When released, the plugin will svn cp just the module's directory  
> into a directory under tags, so it will be easy to see what the  
> released versions of a specific spec are.
>
>  * * *
>
> I really do not see the need for each spec to have its own trunk,  
> and really I think that if we did then it would just make it more  
> difficult for cases when we really want all specs.
>
> I do not see any downside to the approach above.
>
> I recommend that we implement this.  The only major change, which  
> isn't that major, is that the properties which live in the root pom  
> that control the versions need to be removed... or rather moved  
> back to the <version> element of the respective pom.
>
> Comments?
>
> --jason
>


Mime
View raw message