You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Jacek Laskowski <ja...@laskowski.net.pl> on 2006/09/15 09:25:50 UTC
http://geronimo.apache.org/plugins?
Hi,
Just went through the archives and am not sure, but we ended up with
nothing as far as the official plugins repo is concerned[*]. Unless
I'm mistaken, I wonder what it takes to create
http://geronimo.apache.org/plugins as another official repo? Just like
the devtools project has its own place we could (should?) create a
separate space for plugins.
I'd like to gather as much suggestions/opinions/advices as possible
before calling a vote.
WDYT?
[*] Just as I was writing it I came across this lovely quote: "After
all is said and done, more is said than done." by Aesop. Google's
awesome with its quote service. I need to keep it in mind before
taking part in a discussion. ;-)
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
Re: http://geronimo.apache.org/plugins?
Posted by Paul McMahan <pa...@gmail.com>.
On 9/15/06, Jacek Laskowski <ja...@laskowski.net.pl> wrote:
> > geronimoplugincentral.org -- this is is a plugin user community site
> > inspired by eclipseplugincentral.com that was announced to the dev
> > list a few weeks ago. Where the thread left off was that there were
> > suggestions to host the site at http://geronimo.apache.org/plugins
> > instead of a private domain. I proposed a plan of action to make that
> > happen in the thread "plugin community site" and am ready for
> > feedback, assuming that +1's would equal support.
>
> Do we need a full-blown web site (with Joomla behind)? Wouldn't a
> maven-like structure be enough? Just to see how it goes and bring the
> jpa plugin here (where its home is ;-))
I think we are still misaligned here on the distinction between a
plugin repository and a plugin user community site. If we are talking
about a repository then you are correct that a full blown web site is
not required. A repository can be created by making the plugin files
available for download from a maven-like structure. No UI is even
necessary since the admin console already provides the necessary
screens to browse and install a repository's plugins. But if we are
talking about a user community site which provides news, reviews and
discussion forums then a content management system like Joomla is
needed. Unlike a repository, a user community site does not
(necessarily) host any plugin files nor interact with the admin
console.
If you already got this and I'm beating a dead horse then I apologize.
Also, if I should take your line of thought as a nudge towards
aligning our efforts to create another "official" plugin repository
then I can go along with that too. But after studying how the Eclipse
plugin ecosystem has taken shape I believe that a user community site
will be needed sooner or later since it provides a human interface on
top of what may eventually become a loosely federated collection of
plugin repositories, each with their own unique licensing issues,
download processes, business models, etc.
> > geronimo plugins subproject -- IIUC this proposed subproject is for
> > plugin developers and would be similar to the Geronimo plugins project
> > at sourceforge but hosted at ASF and governed by Geronimo (like
> > devtools). Several folks have volunteered to help and I would also
> > like to take this opportunity to volunteer to help. There's a thread
> > "maven repository hosting geronimo plugins" that proposes using the
> > maven repository for hosting the plugins generated by ASF instead of
> > creating a new infrastructure for hosting plugins. No feedback on that
> > idea yet.
>
> That's why I asked about it again. Everybody's busy so only the
> hottest features are able to survive, and the others need to be pushed
> a little ;-)
I agree and thanks for caring enough to push the issue. If we can
publish the ASF plugins to the maven repo and add the repository index
file then I am hopeful that would provide what's needed for an ASF
plugin repository. This seems pretty straight forward to me but I
haven't even read Maven for Dummies yet.
Best wishes,
Paul
Re: http://geronimo.apache.org/plugins?
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 9/15/06, Paul McMahan <pa...@gmail.com> wrote:
> Jacek, I see a couple of discussions going on in parallel:
Well, I should've seen them too, and I did in fact, but completely
forgot about them. Perhaps, it's time to start doing after
everything's said ;-)
> geronimoplugincentral.org -- this is is a plugin user community site
> inspired by eclipseplugincentral.com that was announced to the dev
> list a few weeks ago. Where the thread left off was that there were
> suggestions to host the site at http://geronimo.apache.org/plugins
> instead of a private domain. I proposed a plan of action to make that
> happen in the thread "plugin community site" and am ready for
> feedback, assuming that +1's would equal support.
Do we need a full-blown web site (with Joomla behind)? Wouldn't a
maven-like structure be enough? Just to see how it goes and bring the
jpa plugin here (where its home is ;-))
> geronimo plugins subproject -- IIUC this proposed subproject is for
> plugin developers and would be similar to the Geronimo plugins project
> at sourceforge but hosted at ASF and governed by Geronimo (like
> devtools). Several folks have volunteered to help and I would also
> like to take this opportunity to volunteer to help. There's a thread
> "maven repository hosting geronimo plugins" that proposes using the
> maven repository for hosting the plugins generated by ASF instead of
> creating a new infrastructure for hosting plugins. No feedback on that
> idea yet.
That's why I asked about it again. Everybody's busy so only the
hottest features are able to survive, and the others need to be pushed
a little ;-)
> I see these two discussions as separate because they address two
> different communities -- plugin users vs. plugin developers. But I
> wonder if you view them as the same since you allude to an official
> plugins subproject hosted at http://geronimo.apache.org/plugins ?
I don't know if they need to have their own repo. Just thinking out
loud and thinking we could separate them in a 'plugins' subdirectory
of the Geronimo repo pretty well, too. If they get large they could
become a subproject or a tlp project, whatever. I think we need to
make a home for them before people will scratch their heads where they
could be developed.
What I'm leaning toward is a very unideal yet working solution with
http://geronimo.apache.org/plugins and plugins subdirectory in place.
If/when we decide something better we'll change it.
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
Re: http://geronimo.apache.org/plugins?
Posted by Paul McMahan <pa...@gmail.com>.
Jacek, I see a couple of discussions going on in parallel:
geronimoplugincentral.org -- this is is a plugin user community site
inspired by eclipseplugincentral.com that was announced to the dev
list a few weeks ago. Where the thread left off was that there were
suggestions to host the site at http://geronimo.apache.org/plugins
instead of a private domain. I proposed a plan of action to make that
happen in the thread "plugin community site" and am ready for
feedback, assuming that +1's would equal support.
geronimo plugins subproject -- IIUC this proposed subproject is for
plugin developers and would be similar to the Geronimo plugins project
at sourceforge but hosted at ASF and governed by Geronimo (like
devtools). Several folks have volunteered to help and I would also
like to take this opportunity to volunteer to help. There's a thread
"maven repository hosting geronimo plugins" that proposes using the
maven repository for hosting the plugins generated by ASF instead of
creating a new infrastructure for hosting plugins. No feedback on that
idea yet.
I see these two discussions as separate because they address two
different communities -- plugin users vs. plugin developers. But I
wonder if you view them as the same since you allude to an official
plugins subproject hosted at http://geronimo.apache.org/plugins ?
Best wishes,
Paul
On 9/15/06, Jacek Laskowski <ja...@laskowski.net.pl> wrote:
> Hi,
>
> Just went through the archives and am not sure, but we ended up with
> nothing as far as the official plugins repo is concerned[*]. Unless
> I'm mistaken, I wonder what it takes to create
> http://geronimo.apache.org/plugins as another official repo? Just like
> the devtools project has its own place we could (should?) create a
> separate space for plugins.
>
> I'd like to gather as much suggestions/opinions/advices as possible
> before calling a vote.
>
> WDYT?
>
> [*] Just as I was writing it I came across this lovely quote: "After
> all is said and done, more is said than done." by Aesop. Google's
> awesome with its quote service. I need to keep it in mind before
> taking part in a discussion. ;-)
>
> Jacek
> --
> Jacek Laskowski
> http://www.laskowski.net.pl
>
Re: http://geronimo.apache.org/plugins?
Posted by Paul McMahan <pa...@gmail.com>.
The way it works right now the catalog has to be called
geronimo-plugins.xml. @see PluginInstallerGBean#listPlugins. I
believe it can be in the branch of the tree as long as it contains a
<default-repository> element pointing at the root. I haven't tried
that but expect it should work.
Paul
On 10/2/06, Jason Dillon <ja...@planet57.com> wrote:
> 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?
>
> --jason
Re: http://geronimo.apache.org/plugins?
Posted by Jason Dillon <ja...@planet57.com>.
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?
--jason
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 <da...@yahoo.com> 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 <ja...@laskowski.net.pl> 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
>> > http://geronimo.apache.org/plugins. 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
>>
>>
Re: http://geronimo.apache.org/plugins?
Posted by Jacek Laskowski <ja...@laskowski.net.pl>.
On 9/29/06, Paul McMahan <pa...@gmail.com> wrote:
> My main confusion right now is why the plugins built by geronimo
> aren't published in the snapshot repository. I expected :
> http://people.apache.org/maven-snapshot-repository/org/apache/geronimo/configs/
> to look like my local repo
> ~/.m2/repository/org/apache/geronimo/configs
> Are the snapshot artifacts published selectively?
@see pom.xml:1205
Jacek
--
Jacek Laskowski
http://www.laskowski.net.pl
Re: http://geronimo.apache.org/plugins?
Posted by Jason Dillon <ja...@planet57.com>.
On Sep 29, 2006, at 1:26 PM, Paul McMahan wrote:
> My main confusion right now is why the plugins built by geronimo
> aren't published in the snapshot repository. I expected :
> http://people.apache.org/maven-snapshot-repository/org/apache/
> geronimo/configs/
> to look like my local repo
> ~/.m2/repository/org/apache/geronimo/configs
> Are the snapshot artifacts published selectively?
configs at the moment are not published (neither are assemblies).
--jason
Re: http://geronimo.apache.org/plugins?
Posted by Jason Dillon <ja...@planet57.com>.
On Sep 29, 2006, at 1:26 PM, Paul McMahan wrote:
> http://people.apache.org/maven-snapshot-repository/org/apache/
> geronimo/configs/
This is an old URL too... unknown when it will be removed, but better
to use the new URL:
http://people.apache.org/repo/m2-snapshot-repository/org/apache/
geronimo/configs/
--jason
Re: http://geronimo.apache.org/plugins?
Posted by Paul McMahan <pa...@gmail.com>.
Good question. Actually right now there are three catalogs, one for
each of 1.1, 1.1.1, and 1.2-SNAPSHOT. When 1.2 is released I expect
that its catalog will replace the 1.2-SNAPSHOT catalog. I don't think
that maintaining multiple catalogs is ideal and we will probably want
to converge them into one if possible.
However, at this time the main reason for multiple catalogs is because
the plugins are not compatible across Geronimo releases, at least the
ones I tried. Since the supported geronimo versions is a property of
each plugin, and not the other way around, a consolidated plugin
catalog would need to contain a separate entry for each version of the
plugin. Loading this catalog into the plugin portlet produces a
confusing looking UI, where multiple entries are listed for each
plugin but some are grayed out as being unavailable with no obvious
indication as to why.
Another reason is because the plugin versions are hosted at different
repositories. We may be able to work around that by including a
<default-repository> element in the catalog for each repository, but I
haven't looked closely at how that works yet.
And finally another reason is because it seems like it will be pretty
straightforward to enhance geronimo's build process to create the
catalog for a release. I think this will basically entail
concatenating all the geronimo-plugin.xml files in the config tree
with a little additional munging. But I don't think there's a good
way to perform this *across* releases.
Not trying to overwhelm you with justifications, just want to be as
transparent as possible since I'm really thinking through this as I go
along and want to gather feedback :-) To avoid maintaining multiple
catalogs we may very well want to tackle some of these issues right
now. Jason had some excellent ideas earlier in this thread about how
to maintain the catalog(s) in maven and I definitely think that's
where we should be headed, along with some parallel enhancements to
the UI and CLI.
Best wishes,
Paul
On 10/4/06, Guillaume Nodet <gn...@gmail.com> wrote:
> Just a question. What is the need for two plugin catalogs ?
> I thought plugins could tell which geronimo version they can
> be deployed to.
Re: http://geronimo.apache.org/plugins?
Posted by Guillaume Nodet <gn...@gmail.com>.
Just a question. What is the need for two plugin catalogs ?
I thought plugins could tell which geronimo version they can
be deployed to.
On 10/3/06, Paul McMahan <pa...@gmail.com> wrote:
> I added catalogs for the 1.1 and 1.1.1 plugins at
> http://geronimo.apache.org/plugins/. They point at the plugins hosted
> at http://repo1.maven.org/maven2/.
>
> I also added a catalog for the 1.2-SNAPSHOT plugins pointing at the
> snapshot repository
> http://people.apache.org/repo/m2-snapshot-repository/
> This will start to work if/when the 1.2 snapshot configs get published.
>
> For anyone interested in the play-by-play :-) the next steps I had in mind are:
> - publish 1.2-SNAPSHOT configs so we can install plugins from geronimo's
> snapshot builds (need some guidance here on how to publish)
> - update config.xml to get the repository list from geronimo.apache.org
> as discussed in this thread:
> http://www.nabble.com/plugin-repository-list-URL-in-config.xml-tf2247272.html
> - figure out a way to generate the catalog during the build process
> - look into the idea Jason suggested for publishing the plugin
> catalogs directly
> in the repository
>
> Best wishes,
> Paul
>
--
Cheers,
Guillaume Nodet
Re: http://geronimo.apache.org/plugins?
Posted by Paul McMahan <pa...@gmail.com>.
On 10/4/06, Joe Bohn <jo...@earthlink.net> wrote:
> So needs to be done to get the cars published for 1.2-SNAPSHOT and can I
> help?
It might just involve uncommenting line 1246 of trunk/pom.xml so that
the configs module is listed in the release environment. Then I
suppose there are some manual steps to invoke mvn against that
profile. But I don't know for sure. Perhaps someone with more
knowledge about how the snapshot builds get published can advise.
Paul
Re: http://geronimo.apache.org/plugins?
Posted by Joe Bohn <jo...@earthlink.net>.
Great work Paul!
I am very interested in getting the 1.2-SNAPSHOT cars published as well
so that I can have a more standard way to deploy the tomcat, jetty,
tomcat-deployer, and jetty-deployer plugins I created for Micro-G.
So needs to be done to get the cars published for 1.2-SNAPSHOT and can I
help?
Joe
Paul McMahan wrote:
> I added catalogs for the 1.1 and 1.1.1 plugins at
> http://geronimo.apache.org/plugins/. They point at the plugins hosted
> at http://repo1.maven.org/maven2/.
>
> I also added a catalog for the 1.2-SNAPSHOT plugins pointing at the
> snapshot repository
> http://people.apache.org/repo/m2-snapshot-repository/
> This will start to work if/when the 1.2 snapshot configs get published.
>
> For anyone interested in the play-by-play :-) the next steps I had in
> mind are:
> - publish 1.2-SNAPSHOT configs so we can install plugins from geronimo's
> snapshot builds (need some guidance here on how to publish)
> - update config.xml to get the repository list from geronimo.apache.org
> as discussed in this thread:
>
> http://www.nabble.com/plugin-repository-list-URL-in-config.xml-tf2247272.html
>
> - figure out a way to generate the catalog during the build process
> - look into the idea Jason suggested for publishing the plugin
> catalogs directly
> in the repository
>
> Best wishes,
> Paul
>
>
Re: http://geronimo.apache.org/plugins?
Posted by Joe Bohn <jo...@earthlink.net>.
Please ignore the initial error ..... I forgot that I typed the wrong
URL on my first attempt and hence the error. If I knew how to make an
emoticon that was blushing I would use it now. :-/
Joe
Joe Bohn wrote:
> I attempted to use geronimo 1.1 and deploy the web console on little-G
> with this plugin repo. I hit some problems that I think are related to
> the information that is published (or not) in
> http://repo1.maven.org/maven2/
>
>
> For both jetty and tomcat I received the following error on the server:
> 11:29:09,875 ERROR [PluginInstallerGBean] Cannot find plugin index at
> site http://geronimo.apache.org/1.1/repository/geronimo-plugins.xml
> ############################################################
> # Installed configuration
> # id = geronimo/webconsole-tomcat/1.1/car
> # location =
> C:\g-images\1.1\tomcat-lg\geronimo-1.1\repository\geronimo\webconsole-tomcat\1.1\webconsole-tomcat-1.1.car
>
> ############################################################
> ############################################################
> # Installed configuration
> # id = geronimo/system-database/1.0/car
> # location =
> C:\g-images\1.1\tomcat-lg\geronimo-1.1\repository\geronimo\system-database\1.0\system-database-1.0.car
>
> ############################################################
> 11:30:24,578 WARN [ConfigurationStoreUtil] Checksum file not found:
> C:\g-images\1.1\tomcat-lg\geronimo-1.1\repository\geronimo\system-database\1.0\system-datab
>
> ase-1.0.car\META-INF\config.ser.sha1
>
> I'm not sure what the initial error is with finding the plugin index ...
> but it seems to continue and download the webconsole car in spite of it
> ... so I don't know if it's a real error or just a bogus message.
>
> After that it attempts to download the 1.0 system-database rather than
> the 1.1 version. I think this was the same problem that I originally
> had with geronimoplugins.com a while back. In that case Aaron updated
> the metadata on the geronimoplugins repo.
>
> The metadata in http://repo1.maven.org/maven2/geronimo/webconsole-jetty/
> currently only references 1.0 (which is also the only version that
> includes a pom.xml in the repo). Am I correct in thinking that we need
> to get both the metadata updated and the poms published on the repo
> before this will work?
>
> Thanks,
> Joe
>
>
> Paul McMahan wrote:
>
>> I added catalogs for the 1.1 and 1.1.1 plugins at
>> http://geronimo.apache.org/plugins/. They point at the plugins hosted
>> at http://repo1.maven.org/maven2/.
>>
>> I also added a catalog for the 1.2-SNAPSHOT plugins pointing at the
>> snapshot repository
>> http://people.apache.org/repo/m2-snapshot-repository/
>> This will start to work if/when the 1.2 snapshot configs get published.
>>
>> For anyone interested in the play-by-play :-) the next steps I had in
>> mind are:
>> - publish 1.2-SNAPSHOT configs so we can install plugins from geronimo's
>> snapshot builds (need some guidance here on how to publish)
>> - update config.xml to get the repository list from geronimo.apache.org
>> as discussed in this thread:
>>
>> http://www.nabble.com/plugin-repository-list-URL-in-config.xml-tf2247272.html
>>
>> - figure out a way to generate the catalog during the build process
>> - look into the idea Jason suggested for publishing the plugin
>> catalogs directly
>> in the repository
>>
>> Best wishes,
>> Paul
>>
>>
>
>
Re: http://geronimo.apache.org/plugins?
Posted by Joe Bohn <jo...@earthlink.net>.
I attempted to use geronimo 1.1 and deploy the web console on little-G
with this plugin repo. I hit some problems that I think are related to
the information that is published (or not) in http://repo1.maven.org/maven2/
For both jetty and tomcat I received the following error on the server:
11:29:09,875 ERROR [PluginInstallerGBean] Cannot find plugin index at
site http://geronimo.apache.org/1.1/repository/geronimo-plugins.xml
############################################################
# Installed configuration
# id = geronimo/webconsole-tomcat/1.1/car
# location =
C:\g-images\1.1\tomcat-lg\geronimo-1.1\repository\geronimo\webconsole-tomcat\1.1\webconsole-tomcat-1.1.car
############################################################
############################################################
# Installed configuration
# id = geronimo/system-database/1.0/car
# location =
C:\g-images\1.1\tomcat-lg\geronimo-1.1\repository\geronimo\system-database\1.0\system-database-1.0.car
############################################################
11:30:24,578 WARN [ConfigurationStoreUtil] Checksum file not found:
C:\g-images\1.1\tomcat-lg\geronimo-1.1\repository\geronimo\system-database\1.0\system-datab
ase-1.0.car\META-INF\config.ser.sha1
I'm not sure what the initial error is with finding the plugin index ...
but it seems to continue and download the webconsole car in spite of it
... so I don't know if it's a real error or just a bogus message.
After that it attempts to download the 1.0 system-database rather than
the 1.1 version. I think this was the same problem that I originally
had with geronimoplugins.com a while back. In that case Aaron updated
the metadata on the geronimoplugins repo.
The metadata in http://repo1.maven.org/maven2/geronimo/webconsole-jetty/
currently only references 1.0 (which is also the only version that
includes a pom.xml in the repo). Am I correct in thinking that we need
to get both the metadata updated and the poms published on the repo
before this will work?
Thanks,
Joe
Paul McMahan wrote:
> I added catalogs for the 1.1 and 1.1.1 plugins at
> http://geronimo.apache.org/plugins/. They point at the plugins hosted
> at http://repo1.maven.org/maven2/.
>
> I also added a catalog for the 1.2-SNAPSHOT plugins pointing at the
> snapshot repository
> http://people.apache.org/repo/m2-snapshot-repository/
> This will start to work if/when the 1.2 snapshot configs get published.
>
> For anyone interested in the play-by-play :-) the next steps I had in
> mind are:
> - publish 1.2-SNAPSHOT configs so we can install plugins from geronimo's
> snapshot builds (need some guidance here on how to publish)
> - update config.xml to get the repository list from geronimo.apache.org
> as discussed in this thread:
>
> http://www.nabble.com/plugin-repository-list-URL-in-config.xml-tf2247272.html
>
> - figure out a way to generate the catalog during the build process
> - look into the idea Jason suggested for publishing the plugin
> catalogs directly
> in the repository
>
> Best wishes,
> Paul
>
>
Re: http://geronimo.apache.org/plugins?
Posted by Paul McMahan <pa...@gmail.com>.
I added catalogs for the 1.1 and 1.1.1 plugins at
http://geronimo.apache.org/plugins/. They point at the plugins hosted
at http://repo1.maven.org/maven2/.
I also added a catalog for the 1.2-SNAPSHOT plugins pointing at the
snapshot repository
http://people.apache.org/repo/m2-snapshot-repository/
This will start to work if/when the 1.2 snapshot configs get published.
For anyone interested in the play-by-play :-) the next steps I had in mind are:
- publish 1.2-SNAPSHOT configs so we can install plugins from geronimo's
snapshot builds (need some guidance here on how to publish)
- update config.xml to get the repository list from geronimo.apache.org
as discussed in this thread:
http://www.nabble.com/plugin-repository-list-URL-in-config.xml-tf2247272.html
- figure out a way to generate the catalog during the build process
- look into the idea Jason suggested for publishing the plugin
catalogs directly
in the repository
Best wishes,
Paul
Re: http://geronimo.apache.org/plugins?
Posted by Paul McMahan <pa...@gmail.com>.
On 9/29/06, Jason Dillon <ja...@planet57.com> wrote:
> Its easy enough to make a new artifact, published to say org/apache/
> geronimo/plugincatalog/1.2-SNAPSHOT/geronimo-plugins-1.2-SNAPSHOT.xml
>
> 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.
OK now I'm starting to understand how this could work. But still
being a maven newbie I'm fuzzy on the details. From what I can see
this can be implemented in two stages, first create the catalogs at
geronimo.apache.org/plugins and then migrate them to the maven repo.
Or there may be compelling reasons to just create a copy of the
catalogs in teh maven repo instead, probably needs some more
thought...
Unless there's some concern I will start on the first stage right away
and create a separate JIRA for the second stage. Transitioning
between the stages should go smoothly since there's a level of
indirection for looking up the default list of repository catalogs at:
http://people.apache.org/~ammulder/plugin-repository-list-1.1.txt
thanks,
Paul
Since there's a level of indirection
Re: http://geronimo.apache.org/plugins?
Posted by Jason Dillon <ja...@planet57.com>.
Its easy enough to make a new artifact, published to say org/apache/
geronimo/plugincatalog/1.2-SNAPSHOT/geronimo-plugins-1.2-SNAPSHOT.xml
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.
--jason
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 :
> http://people.apache.org/maven-snapshot-repository/org/apache/
> 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 <ja...@planet57.com> 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
Re: http://geronimo.apache.org/plugins?
Posted by Paul McMahan <pa...@gmail.com>.
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 :
http://people.apache.org/maven-snapshot-repository/org/apache/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 <ja...@planet57.com> 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
Re: http://geronimo.apache.org/plugins?
Posted by Jason Dillon <ja...@planet57.com>.
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
On Sep 28, 2006, at 8:46 PM, Paul McMahan wrote:
> Like Aaron said, plugin repositories already use a maven repository
> layout with the exception of one file -- geronimo-plugins.xml. That
> file is basically a catalog for all the plugins hosted in a
> repository. I discovered something very interesting tonight, which
> is that the catalog does not actually have to reside in the plugin
> repository. It can be hosted anywhere as long as its
> default-repository element points at a valid repository location.
>
> To me this is great news because it means that we can host a catalog
> for ASF plugins wherever we like and use existing maven repositories
> without introducing any new files or requiring any changes to them.
> From maven's point of view, this makes installing a plugin look like
> importing a car into a geronimo assembly.
>
> I prototyped this idea by creating a plugin catalog at :
> http://geronimoplugincentral.org/repository/geronimo-1.1.1/
> geronimo-plugins.xml
> that uses the default-repository element to point at the plugins
> already published at :
> http://repo1.maven.org/maven2/
> When I loaded that catalog into the plugins portlet I was able to
> install the sample plugins just like when I use the default catalog.
> You can recreate these results by adding
> http://geronimoplugincentral.org/repository/geronimo-1.1.1/ to the
> plugin repositories in your 1.1.1 console.
>
> The net of all this is that I would like to take this idea to the next
> level by creating catalogs for the ASF plugins at the location Jacek
> has suggested :
> http://geronimo.apache.org/plugins/
> and point at the plugins already hosted in the maven repos. I don't
> foresee this requiring any changes to maven, but are there any
> concerns with this approach? Feedback and/or assistance from one of
> our maven experts would be especially helpful.
>
> Also, I would like to know if there are any plans to publish snapshot
> builds. Seems like I remember that being discussed recently. Having
> this in place alongside the idea described above would greatly
> increase our ability to develop and test ASF plugins between release
> boundaries.
>
> Best wishes,
> Paul
>
>
> On 9/22/06, Aaron Mulder <am...@alumni.princeton.edu> 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 <da...@yahoo.com> 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 <ja...@laskowski.net.pl> 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
>> > > http://geronimo.apache.org/plugins. 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
>> >
>> >
>>
Re: http://geronimo.apache.org/plugins?
Posted by Paul McMahan <pa...@gmail.com>.
Like Aaron said, plugin repositories already use a maven repository
layout with the exception of one file -- geronimo-plugins.xml. That
file is basically a catalog for all the plugins hosted in a
repository. I discovered something very interesting tonight, which
is that the catalog does not actually have to reside in the plugin
repository. It can be hosted anywhere as long as its
default-repository element points at a valid repository location.
To me this is great news because it means that we can host a catalog
for ASF plugins wherever we like and use existing maven repositories
without introducing any new files or requiring any changes to them.
>From maven's point of view, this makes installing a plugin look like
importing a car into a geronimo assembly.
I prototyped this idea by creating a plugin catalog at :
http://geronimoplugincentral.org/repository/geronimo-1.1.1/geronimo-plugins.xml
that uses the default-repository element to point at the plugins
already published at :
http://repo1.maven.org/maven2/
When I loaded that catalog into the plugins portlet I was able to
install the sample plugins just like when I use the default catalog.
You can recreate these results by adding
http://geronimoplugincentral.org/repository/geronimo-1.1.1/ to the
plugin repositories in your 1.1.1 console.
The net of all this is that I would like to take this idea to the next
level by creating catalogs for the ASF plugins at the location Jacek
has suggested :
http://geronimo.apache.org/plugins/
and point at the plugins already hosted in the maven repos. I don't
foresee this requiring any changes to maven, but are there any
concerns with this approach? Feedback and/or assistance from one of
our maven experts would be especially helpful.
Also, I would like to know if there are any plans to publish snapshot
builds. Seems like I remember that being discussed recently. Having
this in place alongside the idea described above would greatly
increase our ability to develop and test ASF plugins between release
boundaries.
Best wishes,
Paul
On 9/22/06, Aaron Mulder <am...@alumni.princeton.edu> 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 <da...@yahoo.com> 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 <ja...@laskowski.net.pl> 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
> > > http://geronimo.apache.org/plugins. 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
> >
> >
>
Re: http://geronimo.apache.org/plugins?
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
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 <da...@yahoo.com> 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 <ja...@laskowski.net.pl> 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
> > http://geronimo.apache.org/plugins. 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
>
>
Re: http://geronimo.apache.org/plugins?
Posted by David Jencks <da...@yahoo.com>.
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 <ja...@laskowski.net.pl> 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
> http://geronimo.apache.org/plugins. 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
Re: http://geronimo.apache.org/plugins?
Posted by Paul McMahan <pa...@gmail.com>.
On 9/15/06, Jacek Laskowski <ja...@laskowski.net.pl> 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
http://geronimo.apache.org/plugins. 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