We have somewhat of a fairly complete geronimo-plugins.xml generated now
as a result of a Geronimo build or building other plugins. It just
requires some minor edits afterward before we can publish it. The
geronimo-plugins.xml is created (or updated) as a peer to the maven
repository (under .
If that is the case, then why don't we add support to auto-generate
this for each build and stuff the required bits into the maven
repository?
--jason
On Thu, May 8, 2008 at 12:44 AM, Joe Bohn <[EMAIL PROTECTED]> wrote:
> Donald Woods wrote:
>>
>> Seems that we need a unique plugin repo for each
Donald Woods wrote:
Seems that we need a unique plugin repo for each release, given how we
now build plugins based on the content in pom.xml instead of supplying a
separate plugin file Maybe there are some additional
car-maven-plugin enhancements needed, so you can define a range or that
Seems that we need a unique plugin repo for each release, given how we
now build plugins based on the content in pom.xml instead of supplying a
separate plugin file Maybe there are some additional
car-maven-plugin enhancements needed, so you can define a range or that
any sever release is
I've got some questions (and possibly some issues) with the plugin
repository for Geronimo 2.1.1. I went out there attempting to update
the plugin catalog after the release of 2.1.1 (as I had done after 2.1
was released). However, I hit some issues and have some questions:
1) I learned too
