geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder" <ammul...@alumni.princeton.edu>
Subject Re: Re: Liferay Plugin for G
Date Sat, 29 Jul 2006 19:48:36 GMT
Paul,

If you're going to update the liferay plugin soon with more extensive
metadata and to add tomcat to the name, I'd rather wait to post it
until I get the update -- so the page about it will be more complete,
so the module ID won't be changing for the next release, and so we
don't have a dilemma caused by a second release of the "version 4.0.0"
plugin.  If that's going to be a problem, let me know and I'll post
the version I have now.

I don't remember of you've done this already, but if not, you might
also want to make sure that the plugin lists itself in the "obsoletes"
section, so it will uninstall older versions when you install a newer
version.

Thanks,
     Aaron

On 7/27/06, Paul McMahan <paulmcmahan@gmail.com> wrote:
> On 7/27/06, Aaron Mulder <ammulder@alumni.princeton.edu> wrote:
> > Paul,
> >
> > I haven't heard back about whether you want me to post the same
> > plugins that are on your site, so I'll assume yes unless I hear
> > otherwise.  I see you updated the paths on your server though, which
> > is great.
>
> Aaron, I'm at a conference this week and have limited devlist time so
> thanks for your patience.  I did update the repository paths as you
> suggested, thanks for the tip.
>
> Posting the plugin to your site sounds great. But for the longer term
> I would like to encourage Liferay to host the plugin instead.  I'll
> offer my assistance in setting up their repository and also help fix
> GERONIMO-2076 so people can copy/paste alternate repository URLs into
> the admin console.
>
> > A few more notes about the liferay plugins:
> >
> > It looks like you have a plugin for Geronimo/Tomcat only (not
> > Geronimo/Jetty).  Can you build a Jetty plugin too, or does the
> > integration only work with Tomcat?  If there are going to be versions
> > for both, it would be best to put "tomcat" or "jetty" in the module ID
> > for the portal plugin -- liferay/liferay-portal-tomcat/4.0.0/car and
> > liferay/liferay-portal-jetty/4.0.0/car instead of just using
> > liferay/liferay-portal/4.0.0/car for the Tomcat version (and then what
> > for Jetty?).
>
> Agreed.  Adding a Jetty version of the plugin is definitely near the
> top of the todo list.  It should be straightfoward since Liferay
> already provides a Jetty version.
>
> I'll rename the plugin to include the servlet engine name as you
> suggest.  Does the plugin system support either/or style dependencies
> so I could create a single plugin with a dependency against either
> tomcat or jetty?  If not then does it sound like a reasonable
> enhancement request for the 1.2 timeframe (maybe I can work on this)?
>
> > You should use a human-readable <name> for the plugin metadata, and
> > make the <description> an actual description (it will be used as text
> > on the web page that describes the plugin).  There is no real
> > description for the Liferay plugin (only for the Liferay database
> > plugin), which means the web page on the site for the plugin will be
> > pretty empty.  They both use the module ID as the name, which isn't so
> > good.  It would be great if you could update the metadata accordingly.
>
> I agree and will add some better info to the plugin's metadata in its
> next iteration.
>
> > Generally, I'm not sure it's wise to make the plugin version the same
> > as the Liferay product version.  That means you can't release
> > enhancements to the plugin separately from new versions of the
> > product.  However, if you're simply repackaging the default Liferay
> > install (so you think there's no reason to release a separate plugin
> > update), then it makes sense.
>
> Right now the procedure I use to generate the plugin is just to export
> the Liferay WAR as a CAR using the plugin UI.  I made a few changes to
> the exported artifact so it could support Derby.  Liferay has
> indicated they are willing to incorporate those changes back into
> their main release.  So I think for now it makes sense to keep the
> version numbers in synch.  I think its possible that the version
> numbers may need to diverge later, but hopefully not because IMHO it
> would cause too much confusion.
>
> > In the repository list, you should use
> > http://www.geronimoplugins.com/repository/geronimo-1.1/ instead of
> > http://geronimoplugins.com/repository/
>
> OK,  I'll fix that.   BTW, that repository is really just for dev/test
> purposes, so you may see some disorganization in there from time to
> time.
>
> > If you want a site to maintain anything in relation to these plugins
> > (e.g. the geronimo-service.xml files for the plugins), I have a
> > plugins project on sourceforge I can add you to.  That would make it
> > easier for me to help with some of the metadata maintenance if you
> > like.
>
> That sounds cool.  I don't have any peripheral stuff right now but I
> bet there may be something later.  I have also been looking into
> setting up a Geronimo plugin related site that I'd like to get
> everyone's feedback on.  I'll start a separate thread on that.
>
> thanks,
> Paul
>
> >
> > Thanks,
> >      Aaron
> >
> > On 7/25/06, Paul McMahan <paulmcmahan@gmail.com> wrote:
> > > Sorry I've left this thread sitting idle for the last few days.  I'm
> > > just now recovering from a complete system overhaul after my OS
> > > crashed *wince*.
> > >
> > > Thanks Brian for being so flexible.  In the long run I agree with Jeff
> > > that it would be ideal if the plugin was hosted at liferay.com. That
> > > way Liferay can update it when necessary, track downloads, etc. I
> > > would be happy to work with someone to set up a plugin repository at
> > > the Liferay site and then get that repository added to the master list
> > > so it will automatically appear in the admin console,  just let me
> > > know if/when the time is right.
> > >
> > > In the meantime I really hope that the Geronimo community will start
> > > trying out the Liferay plugin and provide feedback.  Aaron would you
> > > like to upload the plugin to your repository so it can automatically
> > > appear in the admin console?   I have also made the plugin available
> > > in a private repository I use for development/testing.  You can add
> > > that repository to your admin console by shutting down your server,
> > > editing config.xml,  and setting this attribute inside the
> > > DownloadedPluginRepos gbean:
> > >
> > > <attribute name="userRepositories">[http://mcmahanfamily.org/repository/geronimo-1.1/]</attribute>
> > >
> > > Then start your Geronimo server, log into the admin console, and then
> > > click the "Search for Plugins" button in the Plugin portlet.  Select
> > > the liferay/liferay-portal/4.0.0/car plugin and follow the prompts
> > > from there.  You may notice a few glitches in the progress bar UI
> > > while the plugin is uploading.  I attached a fix for that to
> > > GERONIMO-1959.
> > >
> > > If you have any questions then please don't hesitate to send me a note
> > > or catch me on irc.
> > >
> > > thanks,
> > > Paul
> > >
> > >
> > >
> > > On 7/21/06, Brian Chan <bchan@liferay.com> wrote:
> > > > Hey everyone,
> > > >
> > > > Great job! I'd rather optimize for ease of use for the end user. If geronimoplugins
is better, so be it. I'm fine either way.
> > > >
> > > > Jeff just sent use the DD for the ejb version. It's still on our todo
list and is the last thing holding us back for 4.1.0 release (this weekend/next few days).
> > > >
> > > > Thanks for the help Jeff, Paul!
> > > >
> > > > --
> > > > Brian Chan
> > > > Chief Executive Officer
> > > > Liferay, LLC
> > > > Enterprise. Open Source. For Life.
> > > >
> > > >
> > > >
> > > > From: Paul McMahan <paulmcmahan@gmail.com>
> > > > To: dev@geronimo.apache.org, jgenender@apache.org
> > > > Subject: Re: Liferay Plugin for G
> > > > Date: Fri Jul 21 03:23:22 GMT 2006
> > > >
> > > > On 7/20/06, Jeff Genender <jgenender@apache.org> wrote:
> > > > >
> > > > >
> > > > > Paul McMahan wrote:
> > > > > > Hey folks.  I have the Liferay Portal plugin ready to make available
> > > > > > so others can start looking at it and provide feedback.  It
actually
> > > > > > consists of two separate plugins --- the Liferay WAR and a Derby
RAR.
> > > > > >
> > > > > > I created the Liferay WAR by exporting it from the Geronimo
version of
> > > > > > Liferay offered at liferay.com.  Then I made some adjustments
to it so
> > > > > > it could deploy into Geronimo 1.1 and so it could work with
Derby.
> > > > > > Jeff, IIUC you're already working with the Liferay devs on an
EJB
> > > > > > version so maybe I can synch up with you instead of contributing
> > > > > > patches to Liferay separately?
> > > > >
> > > > > Absolutely...I handed off a geronimo-application.xml to them and
they
> > > > > are making some changes on their side.  I would be happy to share
the DD
> > > > > if you would like.
> > > >
> > > > Great! please send me the DD when you get a chance.  I'll compare it
> > > > with mine and combine it with the other changes I'm sending to the
> > > > Liferay folks.  Those other changes include:
> > > >
> > > > -  Changed the default context root from "/" to "/liferay" in order to
> > > > avoid collision with Geronimo's welcome app
> > > > -  Added Derby to Liferay's Hibernate dialects
> > > > -  Added support for Derby to the code that generates Liferay's schema
> > > > and database initialization SQL
> > > >
> > > >
> > > > thanks,
> > > > Paul
> > > >
> > > >
> > > >
> > > >
> > >
> >
>

Mime
View raw message