geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Dillon <>
Subject Re:
Date Mon, 02 Oct 2006 06:27:36 GMT
Does it have to be called geronimo-plugins.xml? or can it be  
something like geronimo-plugins-1.1.xml?  And does it need to be in  
the root, or can it i be in a branch of the tree?


On Sep 22, 2006, at 11:42 AM, Aaron Mulder wrote:

> There's one non-standard file (geronimo-plugins.xml), but it has to go
> in the root directory of the repo and be maintained (updated every
> time a plugin in the repo is added, removed, or updated).  I have
> heard the Maven guys say they could handle that, but I'm not sure if
> they meant "someone could implement something" or "it would work right
> now" -- I kind of suspect the former.
> Thanks,
>     Aaron
> On 9/22/06, David Jencks <> wrote:
>> I don't understand the issues with using the maven repo as a plugin
>> repo.  sorry, I haven't been following the discussion that closely.
>> I was under the impression that a plugin repo had to include a bunch
>> of non-maven-recognized files in order to be useful.  If we are to do
>> this I think we need a clear and definitive opinion from the m2 folks
>> that this will not get in the way of repository maintenance.
>> My opinion at the moment, based on very little info:
>> -- if the maven guys assure us that using a maven repo as a plugin
>> repo will never cause problems, lets do that.
>> -- if there is a measurable chance it would cause problems now or in
>> the future, lets have a separate plugin repo.
>> thanks
>> david jencks
>> On Sep 22, 2006, at 11:24 AM, Paul McMahan wrote:
>> > On 9/15/06, Jacek Laskowski <> wrote:
>> >> I'd like to gather as much suggestions/opinions/advices as  
>> possible
>> >> before calling a vote.
>> >
>> > I haven't seen any feedback on this thread since last week but I  
>> think
>> > it's still an important topic.  From what I understand, Jacek has
>> > suggested that we create a plugin repository at
>> >  I proposed using the maven  
>> repo
>> > as a plugin repository instead but haven't seen any feedback on  
>> that
>> > idea so I'm doubting it has support. Other than floating that  
>> idea as
>> > an alternative (which I'm satisfied has been done) I don't  
>> really have
>> > any concerns with calling a vote at this time, if that's still the
>> > intention.  Any others out there have opinions on this matter?
>> >
>> > Best wishes,
>> > Paul

View raw message