geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Donald Woods <>
Subject Re: [DISCUSS] Time to create a geronimo/repo branch in svn for private depends
Date Fri, 08 Aug 2008 00:26:39 GMT
True, but wouldn't that introduce the overhead of our release process 
and voting?

Would we create a geronimo/patches subproject arranged like our specs, 
where each artifact would be its own subdir and still check the patched 
artifacts in for the build to use and then move them to tags after they 
are released?

Would we version the artifacts based on the originating project or with 
a double version like we specs (which would be hard to follow)?


Kevan Miller wrote:
> On Aug 7, 2008, at 9:13 AM, Donald Woods wrote:
>> We have danced around the problem of not being able to build Samples, 
>> Plugins or GEP from a clean m2 repo without building the Server's 
>> repository subdir for long enough.  I believe it is time to create the 
>> following location in SVN -
>>     geronimo/repo
>> Which would hold our private patched artifacts of other projects (like 
>> Tomcat, Pluto, ...), just like the OpenEJB team has done for some of 
>> their private depends.
>> I don't see this as a major hit to the svn infrastructure, given the 
>> jars (10 for 2.2.) will only be downloaded when starting with a clean 
>> m2 repo or when we publish any updated depends.
>> Unless someone comes up with a better solution by Friday morning, I'll 
>> create the new repo branch and populate it with the latest 2.1.2 and 
>> 2.2 patched artifacts tomorrow.
> Agree that this is a problem we need to fix...
> There's another option -- actually release the repository artifacts so 
> that they'll be in normal maven repos. They could be under a geronimo 
> groupid (e.g. org/apache/geronimo/patches or some meaningful name). This 
> might be a cleaner solution...
> --kevan

View raw message