You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by Paul McMahan <pa...@gmail.com> on 2006/07/21 00:34:32 UTC
Re: Liferay Plugin for G
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?
The Derby RAR contains the usual connector deployment artifacts
(tranql and geronimo-ra.xml) and a prepopulated database that gets
copied into var/derby when the RAR is deployed (thanks BTW Matt for
the excellent tip on how to make this work!) This plugin will be
automatically installed by the plugin's dependency system when you
install the Liferay plugin if there's not already a datasource named
"liferay-datasource" deployed in Geronimo. This allows Geronimo users
to install a fully functional portal server running on Derby all in
one shot, or to manually prepare an enterprise database before
installing the Liferay plugin if they prefer.
Brian, thanks for all your support in this effort so far! With your
permission I would like to make the plugin available from a Geronimo
plugin repository (perhaps geronimoplugins.com) so the Geronimo
community can start taking a look at it.
thanks,
Paul
On 6/22/06, Brian Chan <bc...@liferay.com> wrote:
> Hi everyone,
>
> It's great to see the traction going on in the Geronimo world. Just signed up for the dev list so I'm happy to participate.
>
> In our next release of Liferay 4.1.0, we'll:
>
> 1.) Upgrade to the latest Geronimo 1.1 (even if it's just a pre zip until 1.1 gets voted final).
>
> 2.) Use Derby instead of HSQL. (Thanks to Paul!)
>
> Liferay, by default (because our users are now used to it), deploys itself to /
>
> That isn't mandatory though. So for our plugin, we just have to make it map to something like /portal or /liferay instead. It requires one xml change and one property change.
>
> I'm also working with Jeff Genender to also get the EJB version out soon too.
>
> Thanks all.
>
> --
> Brian Chan
> Chief Executive Officer
> Liferay, LLC
> Enterprise. Open Source. For Life.
>
Re: Liferay Plugin for G
Posted by Paul McMahan <pa...@gmail.com>.
On 7/20/06, Jeff Genender <jg...@apache.org> wrote:
>
>
> Paul McMahan wrote:
>
> > Brian, thanks for all your support in this effort so far! With your
> > permission I would like to make the plugin available from a Geronimo
> > plugin repository (perhaps geronimoplugins.com) so the Geronimo
> > community can start taking a look at it.
>
> Paul, what about allowing Liferay to host it themselves since they have
> their own distribution location? Would this not ultimately be the goal,
> where it acts like eclipse-plugins and one can paste in the URL to the host?
>
Yeah I agree that Liferay hosting the plugin themselves could be
preferable since it would allow them to ultimately have control over
the distribution of their IP. My only hesitation with suggesting that
approach was that IIUC in order for a plugin to show up in the admin
console's list of available plugins it needs to be in a properly
arranged repository with the appropriate directory structure and
metadata files surrounding it. I created an experimental plugin
repository for testing the Liferay plugin and it is straightforward
but not exactly trivial to setup and maintain. Another reason I
suggested a centralized location like geronimoplugins.com is because
you currently cannot paste a URL to the host where plugins are offered
into the admin console -- you need to edit config.xml and then
Geronimo to add the host, or have it added to the master list of
repositories maintained at people.apache.org. GERONIMO-2076 will
address that but not until version 1.1.2 at the earliest.
Paul
> >
> > thanks,
> > Paul
> >
> > On 6/22/06, Brian Chan <bc...@liferay.com> wrote:
> >> Hi everyone,
> >>
> >> It's great to see the traction going on in the Geronimo world. Just
> >> signed up for the dev list so I'm happy to participate.
> >>
> >> In our next release of Liferay 4.1.0, we'll:
> >>
> >> 1.) Upgrade to the latest Geronimo 1.1 (even if it's just a pre zip
> >> until 1.1 gets voted final).
> >>
> >> 2.) Use Derby instead of HSQL. (Thanks to Paul!)
> >>
> >> Liferay, by default (because our users are now used to it), deploys
> >> itself to /
> >>
> >> That isn't mandatory though. So for our plugin, we just have to make
> >> it map to something like /portal or /liferay instead. It requires one
> >> xml change and one property change.
> >>
> >> I'm also working with Jeff Genender to also get the EJB version out
> >> soon too.
> >>
> >> Thanks all.
> >>
> >> --
> >> Brian Chan
> >> Chief Executive Officer
> >> Liferay, LLC
> >> Enterprise. Open Source. For Life.
> >>
>
Re: Liferay Plugin for G
Posted by Jeff Genender <jg...@apache.org>.
Paul McMahan wrote:
> Brian, thanks for all your support in this effort so far! With your
> permission I would like to make the plugin available from a Geronimo
> plugin repository (perhaps geronimoplugins.com) so the Geronimo
> community can start taking a look at it.
Paul, what about allowing Liferay to host it themselves since they have
their own distribution location? Would this not ultimately be the goal,
where it acts like eclipse-plugins and one can paste in the URL to the host?
>
> thanks,
> Paul
>
> On 6/22/06, Brian Chan <bc...@liferay.com> wrote:
>> Hi everyone,
>>
>> It's great to see the traction going on in the Geronimo world. Just
>> signed up for the dev list so I'm happy to participate.
>>
>> In our next release of Liferay 4.1.0, we'll:
>>
>> 1.) Upgrade to the latest Geronimo 1.1 (even if it's just a pre zip
>> until 1.1 gets voted final).
>>
>> 2.) Use Derby instead of HSQL. (Thanks to Paul!)
>>
>> Liferay, by default (because our users are now used to it), deploys
>> itself to /
>>
>> That isn't mandatory though. So for our plugin, we just have to make
>> it map to something like /portal or /liferay instead. It requires one
>> xml change and one property change.
>>
>> I'm also working with Jeff Genender to also get the EJB version out
>> soon too.
>>
>> Thanks all.
>>
>> --
>> Brian Chan
>> Chief Executive Officer
>> Liferay, LLC
>> Enterprise. Open Source. For Life.
>>
Re: Liferay Plugin for G
Posted by Jason Dillon <ja...@planet57.com>.
This is awesome!
--jason
On Jul 20, 2006, at 3:34 PM, 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?
>
> The Derby RAR contains the usual connector deployment artifacts
> (tranql and geronimo-ra.xml) and a prepopulated database that gets
> copied into var/derby when the RAR is deployed (thanks BTW Matt for
> the excellent tip on how to make this work!) This plugin will be
> automatically installed by the plugin's dependency system when you
> install the Liferay plugin if there's not already a datasource named
> "liferay-datasource" deployed in Geronimo. This allows Geronimo users
> to install a fully functional portal server running on Derby all in
> one shot, or to manually prepare an enterprise database before
> installing the Liferay plugin if they prefer.
>
> Brian, thanks for all your support in this effort so far! With your
> permission I would like to make the plugin available from a Geronimo
> plugin repository (perhaps geronimoplugins.com) so the Geronimo
> community can start taking a look at it.
>
> thanks,
> Paul
>
> On 6/22/06, Brian Chan <bc...@liferay.com> wrote:
>> Hi everyone,
>>
>> It's great to see the traction going on in the Geronimo world.
>> Just signed up for the dev list so I'm happy to participate.
>>
>> In our next release of Liferay 4.1.0, we'll:
>>
>> 1.) Upgrade to the latest Geronimo 1.1 (even if it's just a pre
>> zip until 1.1 gets voted final).
>>
>> 2.) Use Derby instead of HSQL. (Thanks to Paul!)
>>
>> Liferay, by default (because our users are now used to it),
>> deploys itself to /
>>
>> That isn't mandatory though. So for our plugin, we just have to
>> make it map to something like /portal or /liferay instead. It
>> requires one xml change and one property change.
>>
>> I'm also working with Jeff Genender to also get the EJB version
>> out soon too.
>>
>> Thanks all.
>>
>> --
>> Brian Chan
>> Chief Executive Officer
>> Liferay, LLC
>> Enterprise. Open Source. For Life.
>>
Re: Liferay Plugin for G
Posted by Paul McMahan <pa...@gmail.com>.
On 7/20/06, Jeff Genender <jg...@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
Re: Re: Liferay Plugin for G
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Actually, also, your repository isn't quite right. The
geronimo-plugins.xml should go in the root of the repository (which in
this case is http://mcmahanfamily.org/repository/ not
http://mcmahanfamily.org/repository/geronimo-1.1/). So either you
should move all the files to repository/geronimo-1.1/ or you should
move the geronimo-plugins.xml to repository/ and give out the URL
without the geronimo-1.1 on the end.
Thanks,
Aaron
On 7/25/06, Paul McMahan <pa...@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 <bc...@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 <pa...@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 <jg...@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
> >
> >
> >
> >
>
Re: Re: Liferay Plugin for G
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Yeah, I'll be happy to put the plugin up. Should I just get the one
at http://mcmahanfamily.org/repository/geronimo-1.1/ to put up there?
Thanks,
Aaron
On 7/25/06, Paul McMahan <pa...@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 <bc...@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 <pa...@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 <jg...@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
> >
> >
> >
> >
>
Re: Liferay Plugin for G
Posted by Jeff Genender <jg...@apache.org>.
Nice work Paul!
Paul McMahan 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 <bc...@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 <pa...@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 <jg...@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
>>
>>
>>
>>
Re: Re: Liferay Plugin for G
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
Cool! I'll post it to the main plugin site tonight.
Thanks,
Aaron
On 7/31/06, Paul McMahan <pa...@gmail.com> wrote:
> I updated the liferay plugins as Aaron suggested, adding "tomcat" to
> the module name, providing better metadata for the plugin site, etc.
> My dev/test plugin repository is currently available at
> http://mcmahanfamily.org/repository/geronimo-1.1/ if you would like to
> follow the instructions provided earlier in this thread (quoted below)
> to add the repository to your admin console. Feedback is most
> welcome!!
>
> A few points:
>
> - you probably want to start your JVM with "-Xmx1024m" to make more
> memory available to the portal application
>
> - Jeff is helping with a new version of Liferay that can be deployed
> into Geronimo as an EAR file and can reuse some jars in Geronimo's
> repository. My understanding is that those changes will be rolled
> into the next version of Liferay (4.1.0?). I'm also going to see if
> the changes I made for Derby can make that release as well and then
> roll up a new version of the plugins.
>
> - If you notice some glitches with the UI while downloading the
> plugin then you probably need to pick up the changes made in
> GERONIMO-1959 which were committed last week (thanks Sachin).
>
> - I am offering to provide my assistance to Liferay so they can set
> up a repository and host the plugin at their site.
>
>
> thanks,
> Paul
>
>
> On 7/29/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
> > 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 <pa...@gmail.com> wrote:
> > > On 7/27/06, Aaron Mulder <am...@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 <pa...@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 <bc...@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 <pa...@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 <jg...@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
> > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
Re: Liferay Plugin for G
Posted by Jeff Genender <jg...@apache.org>.
Paul McMahan wrote:
> - Jeff is helping with a new version of Liferay that can be deployed
> into Geronimo as an EAR file and can reuse some jars in Geronimo's
> repository. My understanding is that those changes will be rolled
> into the next version of Liferay (4.1.0?). I'm also going to see if
> the changes I made for Derby can make that release as well and then
> roll up a new version of the plugins.
I got it working, but it has found some nasties with Geronimo. First,
the EAR deployment seems to want 1.5G in the JAVA_OPTS for memory to run
on Linux and MacOSX machines. It seems to run fine there with those
memory settings. But Windows can't seem to allocate more than 1.498G to
the Java heap, so it doesn't work on that platform.
The issue is, it runs fine in 1G on all other appservers, except for G.
This likely is a problem in OpenEJB and I will have to profile why the
need for so much memory. :(
Jeff
Re: Re: Liferay Plugin for G
Posted by Paul McMahan <pa...@gmail.com>.
I updated the liferay plugins as Aaron suggested, adding "tomcat" to
the module name, providing better metadata for the plugin site, etc.
My dev/test plugin repository is currently available at
http://mcmahanfamily.org/repository/geronimo-1.1/ if you would like to
follow the instructions provided earlier in this thread (quoted below)
to add the repository to your admin console. Feedback is most
welcome!!
A few points:
- you probably want to start your JVM with "-Xmx1024m" to make more
memory available to the portal application
- Jeff is helping with a new version of Liferay that can be deployed
into Geronimo as an EAR file and can reuse some jars in Geronimo's
repository. My understanding is that those changes will be rolled
into the next version of Liferay (4.1.0?). I'm also going to see if
the changes I made for Derby can make that release as well and then
roll up a new version of the plugins.
- If you notice some glitches with the UI while downloading the
plugin then you probably need to pick up the changes made in
GERONIMO-1959 which were committed last week (thanks Sachin).
- I am offering to provide my assistance to Liferay so they can set
up a repository and host the plugin at their site.
thanks,
Paul
On 7/29/06, Aaron Mulder <am...@alumni.princeton.edu> wrote:
> 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 <pa...@gmail.com> wrote:
> > On 7/27/06, Aaron Mulder <am...@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 <pa...@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 <bc...@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 <pa...@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 <jg...@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
> > > > >
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
Re: Re: Liferay Plugin for G
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
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 <pa...@gmail.com> wrote:
> On 7/27/06, Aaron Mulder <am...@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 <pa...@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 <bc...@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 <pa...@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 <jg...@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
> > > >
> > > >
> > > >
> > > >
> > >
> >
>
Re: Re: Liferay Plugin for G
Posted by Paul McMahan <pa...@gmail.com>.
On 7/27/06, Aaron Mulder <am...@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 <pa...@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 <bc...@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 <pa...@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 <jg...@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
> > >
> > >
> > >
> > >
> >
>
Re: Re: Liferay Plugin for G
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
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.
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?).
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.
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.
In the repository list, you should use
http://www.geronimoplugins.com/repository/geronimo-1.1/ instead of
http://geronimoplugins.com/repository/
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.
Thanks,
Aaron
On 7/25/06, Paul McMahan <pa...@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 <bc...@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 <pa...@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 <jg...@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
> >
> >
> >
> >
>
Re: Re: Re: Liferay Plugin for G
Posted by Aaron Mulder <am...@alumni.princeton.edu>.
On 7/27/06, Brian Chan <bc...@liferay.com> wrote:
> Hey Aaron,
>
> We've only tested in Tomcat so far. Our next step is to get a bundle out for jetty as well.
OK. If you're planning to release a Jetty bundle, that suggests that
we should name the current plugin liferay-portal-tomcat so it'll
"leave a place" for a future Jetty plugin.
Thanks,
Aaron
> From: Aaron Mulder <am...@alumni.princeton.edu>
> To: dev@geronimo.apache.org
> Subject: Re: Re: Liferay Plugin for G
> Date: Thu Jul 27 16:35:08 GMT 2006
>
> 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.
>
> 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?).
>
> 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.
>
> 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.
>
> In the repository list, you should use
> http://www.geronimoplugins.com/repository/geronimo-1.1/ instead of
> http://geronimoplugins.com/repository/
>
> 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.
>
> Thanks,
> Aaron
>
> On 7/25/06, Paul McMahan <pa...@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 <bc...@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 <pa...@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 <jg...@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
> > >
> > >
> > >
> > >
> >
>
>
>
>
Re: Re: Liferay Plugin for G
Posted by Paul McMahan <pa...@gmail.com>.
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 <bc...@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 <pa...@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 <jg...@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
>
>
>
>
Re: Liferay Plugin for G
Posted by Jeff Genender <jg...@apache.org>.
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.
>
> The Derby RAR contains the usual connector deployment artifacts
> (tranql and geronimo-ra.xml) and a prepopulated database that gets
> copied into var/derby when the RAR is deployed (thanks BTW Matt for
> the excellent tip on how to make this work!) This plugin will be
> automatically installed by the plugin's dependency system when you
> install the Liferay plugin if there's not already a datasource named
> "liferay-datasource" deployed in Geronimo. This allows Geronimo users
> to install a fully functional portal server running on Derby all in
> one shot, or to manually prepare an enterprise database before
> installing the Liferay plugin if they prefer.
>
> Brian, thanks for all your support in this effort so far! With your
> permission I would like to make the plugin available from a Geronimo
> plugin repository (perhaps geronimoplugins.com) so the Geronimo
> community can start taking a look at it.
>
> thanks,
> Paul
>
> On 6/22/06, Brian Chan <bc...@liferay.com> wrote:
>> Hi everyone,
>>
>> It's great to see the traction going on in the Geronimo world. Just
>> signed up for the dev list so I'm happy to participate.
>>
>> In our next release of Liferay 4.1.0, we'll:
>>
>> 1.) Upgrade to the latest Geronimo 1.1 (even if it's just a pre zip
>> until 1.1 gets voted final).
>>
>> 2.) Use Derby instead of HSQL. (Thanks to Paul!)
>>
>> Liferay, by default (because our users are now used to it), deploys
>> itself to /
>>
>> That isn't mandatory though. So for our plugin, we just have to make
>> it map to something like /portal or /liferay instead. It requires one
>> xml change and one property change.
>>
>> I'm also working with Jeff Genender to also get the EJB version out
>> soon too.
>>
>> Thanks all.
>>
>> --
>> Brian Chan
>> Chief Executive Officer
>> Liferay, LLC
>> Enterprise. Open Source. For Life.
>>