geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Dillon <>
Subject Re:
Date Fri, 29 Sep 2006 20:36:23 GMT
Its easy enough to make a new artifact, published to say org/apache/ 

But to make that work, we'd need to update the plugin code to look  
for a geronimo-plugins-${geronimo.version}.xml before it looks for a  
geronimo-plugins.xml, but that is very minor.


On Sep 29, 2006, at 1:26 PM, Paul McMahan wrote:

> I didn't realize maven had that capability, but I'm not surprised
> because it never ceases to impress me.  I'm not sure that we can take
> advantage of that capability right now though because from what I can
> tell there needs to be one plugin catalog per version of geronimo.
> Since maven pushes versioning down towards the artifact level I don't
> know where in the maven directory structure to put the catalogs.  I
> think there are advantages to hosting the catalogs in a separate
> location anyway, such as the ability to switch to an alternate repo
> if/when that need arises.
> My main confusion right now is why the plugins built by geronimo
> aren't published in the snapshot repository. I expected :
> geronimo/configs/
> to look like my local repo
> ~/.m2/repository/org/apache/geronimo/configs
> Are the snapshot artifacts published selectively?
> Paul
> On 9/28/06, Jason Dillon <> wrote:
>> We could publish the catalog to the m2 repo too, just need to had
>> some custom build fluff to attach the xml file as a build artifact.
>> --jason

View raw message