Serge,
Thank you for pointing this out. Can you submit a Jira issue on this
against Pluto-2.0.0? A patch file would also be very welcome.
/Craig
"Serge Huber"
+1 to promoting 2.0-spi-refactoring to trunk. Thanks for doing the merges. I'm really looking forward to getting Pluto 2.0 out the door. However, due to a death in the family, I cannot offer much help right now./Craig-Ate Douma <[EMAIL PROTECTED]> wrote: ->To: pluto-dev@portals.apache.org>F
No problem. Trust me, I've been called worst ;). But seriously, you have more than made up for mangling my name in all the fixes you made in the 2.0-refactoring to the mangled commits I've done in the past. Now, if I could just can get my father-in-law to stop calling me Greg . . . . .-Ate Dou
This seems to indicate that you will be replacing the trunk with the
2.0-refactoring branch rather than doing a merge. Is that true? If so,
there are some things that were applied to the trunk since the branch was
created that were not applied to the branch. Some of them are my fault. For
instanc
Hi, The 2.0-spi-refactoring branch cannot compile without error, which makes applying patches from the trunk a very difficult job. Please correct this when you get a chance.TIA/Craig
Sorry, but I just realized I submitted my response only to the PMC list.
/Craig
+1
Eric Dalquist
<[EMAIL PROTECTED]
Eric,
It would be great if you could do this. Directions for doing a release is
found on the Pluto wiki here:
http://wiki.apache.org/portals/Pluto/CuttingRelease
A couple of things to note:
1. Make sure you also create and publish the bundled distribution (Tomcat
with Pluto and Testsuite instal
Hi, I just figured out that there are two copies of the web site code in SVN. One is in the root src directory, the other is in the pluto-site module. Why do we have this redundancy?TIA/Craig
Hi,
Sorry, but I did not read the post carefully enough. Yes, in order for two
portlets to communicate (pass data), you need to use either public render
parameters or portlet events. The
javax.portlet.actionScopedRequestAttributes container runtime option can be
used by a single portlet to pass r
Eric, The attributes need to be set on the PortletRequest, not the PortletSession./Craig-"Eric Chow" <[EMAIL PROTECTED]> wrote: -To: pluto-dev@portals.apache.orgFrom: "Eric Chow" <[EMAIL PROTECTED]>Date: 07/04/2008 05:26AMSubject: Pluto-2.0 portletSession cannot share parameters !!!Hell
Hi Naresh,
Try setting the charset init-param for PortalDriverServlet in web.xml as
described here: https://issues.apache.org/jira/browse/PLUTO-446 .
/Craig
"Naresh Shorey"
David,
Thanks to you and Ate for taking the lead on this effort. I'm sure the
result will be a better Pluto and Jetspeed product. Unfortunately, other
commitments won't allow me to contribute a large block of time to help this
effort, but I'd like to chip in when I have the time.
In particular,
+1
Thanks for taking the lead on this release, Elliot.
/Craig
Elliot Metsger-3 wrote:
>
> The Pluto 1.1.5 test build has been cut and is available as indicated
> below. Many thanks to community for finding bugs, supplying patches,
> and implementing improvments!
>
> No determination as to
As soon as you open up a command window and issue the following two commands: svn checkout https://svn.apache.org/repos/asf/portals/pluto/trunk/ plutoant -f dist-build.xml -"Eric Chow" <[EMAIL PROTECTED]> wrote: -To: pluto-dev@portals.apache.org, [EMAIL PROTECTED]From: "Eric Chow" <[EMAIL
See below
"Eric Chow" <[EMAIL PROTECTED]> wrote on 01/29/2008 04:39:01 AM:
> Hello,
>
> As I checked the pluto-2.0 portal, it still using the
>
> "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
> "http://java.sun.com/dtd/web-app_2_3.dtd";>
>
>
> in the web.xml.
>
> Can it use
Ate Douma <[EMAIL PROTECTED]> wrote on 01/25/2008 09:35:43 AM:
> [EMAIL PROTECTED] wrote:
> >
> > +1 to svn:ignore
>
> Thanks Graig and the others for agreeing on this and I will proceed
> doing this shortly.
>
> >
> > I'd also like to see .classpath in the Pluto root and would not object
to
>
+1 to svn:ignore
I'd also like to see .classpath in the Pluto root and would not object to
analagous files for IDEA and Netbeans IDEs. I cannot get the maven 2
eclipse plugin to create a single .classpath in my Eclipse project's root
dir. I have to run 'mvn eclipse:eclipse' in the root dir, and
Torsten,
I very much appreciated the work you and your group has done to create
Pluto 2.0, but I was very disappointed in many of the commits you did
today. Rather than fixing most of the TODOs and FIXMEs, you just erased
them. Some of the TODOs and FIXMEs are inconsequential and not necessary
an
I'm finished. Everything went off without a hitch (See below). Welcome to the world of Pluto 2.0 (2.0.0-SNAPSHOT)!!/Craig[EMAIL PROTECTED] wrote: ->To: pluto-dev@portals.apache.org>From: [EMAIL PROTECTED]>Date: 01/07/2008 08:29PM>Subject: Subversion repository reorganization in progress>>>Hi al
Hi all, I'm going to start fiddling with the Pluto Subversion repository now as previously advertised, so refrain from doing any commits until you hear from me again. Thank you all for your input to my proposal. Based on your feedback, here's my final plan: 1. Copy trunk to tags directory (as plut
Hi Elliot, Don't be bashful about helping us. We appreciate it and can use all the help we can get./Craig -Elliot Metsger <[EMAIL PROTECTED]> wrote: -To: pluto-dev@portals.apache.orgFrom: Elliot Metsger <[EMAIL PROTECTED]>Date: 01/06/2008 02:27PMSubject: Re: trunk-mergeAgain sorry for the b
Hi all, It seems that everyone is OK with moving the Subversion 1.1-286-trunk-merge branch to the SVN trunk. I intend on doing that on Monday night (East Coast USA time), so please voice your comments and concerns by that time. Here's my basic plan. Since I am not an Subversion guru, please comment
Elliot, Here's a diff analysis I did with my suggestions for changes to move from trunk to pluto-1.1.x: **Diff between pluto-1.1.x and trunk as of 1/4/2008 Significant changes that should be
Hi Elliot, Torsten, please correct me if I am wrong, but I believe that in the 1.1-286-trunk-merge and 1.1-286-COMPATIBILITY branches, the descriptors for web.xml are still using Castor, while the descriptors for portlet.xml use JAXB. The JSR-286 spec requires that complex type event payloads be in
Eric, Thanks for this message and all the patches you have recently contributed to Pluto. I just did a diff between pluto-1.1.x and trunk, and I found a number of differences. Most if them were minor, but a few of them were not. So I'd rather not get rid of the current trunk code for now since I am
Ate, Thanks for your well-considered comments (see below). -Ate Douma <[EMAIL PROTECTED]> wrote: ->To: pluto-dev@portals.apache.org>From: Ate Douma <[EMAIL PROTECTED]>>Date: 12/19/2007 03:12AM>Subject: Re: [VOTE] Move 1.1-286-trunk-merge branch to trunk>>I'm +1 in general.>>But we also sho
Hi all,
The JSR-286 Expert Group's work is being completed in the next few weeks.
The JSR-286 RI work lead by Torsten Dettborn should also be finished at
that time. That work started in the 1.1-286-COMPATIBILITY branch, but it
has moved to the 1.1-286-trunk-merge branch with my help. As its name
Thank you, Torsten. Please also take a look at the patch that Christian
suggested being appied from PLUTO-444 (filters.271107.patch). There appears
to be a conflict with this patch and the PortletServlet class in the
1.1-286-trunk-merge branch. I tried to manually apply the patch, but I
think I g
I backed out the PLUTO-442 and PLUTO-444 patches locally. The Pluto portal builds OK now.[EMAIL PROTECTED] wrote: ->To: pluto-dev@portals.apache.org>From: [EMAIL PROTECTED]>Date: 12/10/2007 07:19PM>Subject: Problems with 1.1-286-trunk-merge build>>>Hi all,>>I commited a bunch of changes by Ben
Hi all,
I commited a bunch of changes by Ben that got me to rev 603094 (PLUTO-404
and 442 patches). This allowed me to a built portal with a testsuite having
all but a couple of minor version checks working (however, the 286 tests
did not seem to work). The admin portlet was erroring with some so
Ben,Does this code work in the 1.1-286-COMPATIBILITY branch? If you haven't tried it there yet, I suggest you do. That way we'll know if its a problem with your code or the Pluto trunk integration code. Thanks./Craig [EMAIL PROTECTED] wrote: -To: pluto-dev@portals.apache.orgFrom: [EMAIL PROTECT
Ben, I tried the introduction_jsp.patch out locally and got the following stack trace when I arrived on the test page:javax.portlet.PortletException: java.lang.IllegalArgumentException: A malformed URL has occured at org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.internalInclude(Portle
Torsten, Added missing ccpp.jar file to shared/lib of Tomcat and META-INF/pluto.properties in pluto-container.jar, which built and got the Pluto portal to start. Still. most of the portlets were erroring out, so there's still work to be done. The testsuite portlets don't error out, but the test lin
Hi Torsten,Thanks for your help. Please commit what you have done so far. I am out-of-town right now and will take a look at it when I get back./Craig-"Torsten Dettborn" <[EMAIL PROTECTED]> wrote: -To: From: "Torsten Dettborn" <[EMAIL PROTECTED]>Date: 12/07/2007 05:10AMSubject: trunk-mergeH
Eliiot,
Thank you for stepping in to help with the next release.
I'd like to see any new patches applied to the trunk and the 1.1-286-trunk
-merge branch. Some of these changes might need to be merged into
1.1-286-trunk-merge manually since it is a hybrid branch, but that
shouldn't be difficult
Joe, I wish that I could help you, but I appear to be the only active committer right now, and have to do this work on my own time in addition to my other 'free time' committments (such as family).Right now, my focus is getting the JSR-286 RI work merged into the trunk to move Pluto toward a 2.0 re
Noel, Please create a Jira issue and attach the patch to it. Thank you for your contribution./Craig -"Noel J. Bergman" <[EMAIL PROTECTED]> wrote: -To: From: "Noel J. Bergman" <[EMAIL PROTECTED]>Date: 11/11/2007 11:37AMSubject: RE: Working on Pluto during ApacheConPublic Render Parameters ar
Vackar, The pluto/WEB-INF/data directory held config files for Pluto 1.0.1. Pluto 1.1 uses config files in the WEB-INF directory./Craig-Vackar <[EMAIL PROTECTED]> wrote: -To: pluto-dev@portals.apache.orgFrom: Vackar <[EMAIL PROTECTED]>Date: 11/09/2007 11:37AMSubject: Where are the config fi
Hi Noel, I will be not be at ApacheCon and will be in training next week, but I still would like to be informed as to any work being done on Pluto at the conference. I am also very grateful for help from others in the Pluto community.TIA/Craig-"Noel J. Bergman" <[EMAIL PROTECTED]> wrote: -T
Noel, Thank you for your offer to help. I have made this fix in SVN rev 590627.Right now I am waiting for Torsten to commit merging the pluto-container module with the trunk source code before I can finish my work on the pluto-portal-driver and pluto-portal-driver-impl modules. In the meantime, the
Thanks, Torsten. I'm in the middle of merging the pluto-portal-driver and pluto-portal-driver-impl and need the merged pluto-container module finished before I can continue my work./Craig-"Torsten Dettborn" <[EMAIL PROTECTED]> wrote: -To: From: "Torsten Dettborn" <[EMAIL PROTECTED]>Date: 10
Hi Torsten,
Thanks for your reply. I hope you are feeling better. If you didn't know,
the pluto-portal-driver and pluto-portal-driver-impl are not yet merged in
the 1.1-286-trunk-merge branch (see Jira PLUTO-402). That is probably why
the Pluto servlet is not working at this point. You should a
Hi all, Obviously, I thought I was sending this to Torsten only, so sorry for the gory personal details. I realized that I already merged the pluto-testsuite module into the 1.1-286-trunk-merge branch, so when I got some time to work on this today, I finished merging the pluto-portal branch (see P
Hi Torsten, I just wanted to check with you on how you are doing with this work. Are you working on the pluto-container module or something else? It would be a good idea if you could commit your work on a regular basis. You code doesn't have to work to be committable. I'd like to make sure we aren'
Paul,
This has been done.
Elliot also updated the repo at
http://people.apache.org/builds/portals-pluto/m2-staging-repository
/Craig
Paul McMahan <[EMAIL PROTECTED]>
10/09/2007 02:29 PM
Please respond to
pluto-dev@portals.apache.org
To
pluto-dev@portals.apache.org
cc
Subject
please u
Thank you Torsten. I could use the help. My father was recently diagnosed with cancer, so I have been using much of my free time lately to help him. Why don't you start with the pluto-container module. I have made a start on the pluto-testsuite module locally on my machine, and I will continue with
Duh!
Sorry, I'm doing a lot of multitasking today. Thanks for taking care of
this.
/Craig
"David H. DeWolf" <[EMAIL PROTECTED]>
08/29/2007 08:57 AM
Please respond to
pluto-dev@portals.apache.org
To
pluto-dev@portals.apache.org
cc
Subject
Re: ccpp, commit mails, Internal...Request
Excuse me, David, but how do we get a copy of Torsten's commits to be sent
to the pluto-scm mail list?
TIA
/Craig
"David H. DeWolf" <[EMAIL PROTECTED]>
08/29/2007 08:36 AM
Please respond to
pluto-dev@portals.apache.org
To
pluto-dev@portals.apache.org
cc
Subject
Re: ccpp, commit mails, In
Hi David,
This was not intential, but an oversight on my part. I will fix it when I
get a chance. Thanks for pointing it out.
/Craig
"David H. DeWolf" <[EMAIL PROTECTED]>
08/06/2007 08:14 AM
Please respond to
pluto-dev@portals.apache.org
To
pluto-dev@portals.apache.org
cc
Subject
Re: New
Hi all, In order to jump start the merging of the JSR-286 Reference Implementation work at Pluto with our SVN trunk, I have created a 1.1-286-trunk-merge branch in Subversion. This branch starts with the 1.1-286-COMPATIBILITY branch (JSR-286 RI) as a base line. The SVN trunk will be gradually merge
Hi All,
FYI, if you haven't heard, the Public Review Draft of the JSR-286 (Portlet
2.0) specification is open for review until August 27. Copies of the
specification, API javadocs and source code can be found on the JSR-286
home page on the Java Community Process web site
(http://jcp.org/en/js
David originally posted a -1 vote, but backed away when he discovered that
the bug he thought was in 1.1.4 was not there.
David, have you changed your vote? If so, what is your current vote?
Is it legal withing Apache rules for someone to change their vote?
TIA
/Craig
Elliot Metsger <[EMA
Hi Benjamin, Torsten and others in the Univ of Jena group should comment on the completeness of the 286 branch. I was able to build it last night without error. I also have been able to run simple portlets demonstrate 286 eventing in the 286 branch. Stefan Hepper also did a demo with this branch a
Elliot, We need to hear from Torston, and, hopefully, Stefan on this issue. Stefan should also comment on the 286 spec's time line. I'd like to merge the 286 branch with the trunk and then move 286 into the trunk. But if the community is still hot for a 1.2 release, we should do it from the trunk,
Elliot,
I checked the test build and I think we're good to go.
+1 for relasing this as GA
Thanks for all your hard work on this release.
/Craig
-Elliot Metsger <[EMAIL PROTECTED]> wrote: -
To: pluto-dev@portals.apache.org
From: Elliot Metsger <[EMAIL PROTECTED]>
Date: 07/14/2007 04:5
David,
Thanks for reminding me about this. Yes, we can all go off in any number
of directions if we want.
I intend to start focussing my efforts on the 286-COMPATILIBITY branch.
merging the code with the current trunk and pushing out a Pluto 2.0 alpha
or beta release. I hope that others in th
Perhaps we should just add documentation about incompatibility of the
1.1.x branch starting at 1.1.3 and recut the 1.1.4 release as 1.1.5.
I am very much against moving toward a 1.2.0 release. We should not get
mired in a 1.2.x release cycle of a JSR-168 impl. We need to start moving
toward jsr
Elliot,
Here are a couple of diffs between the trunk and the pluto-1.1.x branch I
found and fixed recently :
PortalURLParserImpl and RelativePortalURLImpl in SVN rev 554210
PortletRequestImpl in SVN rev 553211
I was suprised to see them as these are key classes. I just don't want
other signifi
Marc,
I agree with Elliot that we should now use Java 5 on the trunk, but I'd
like to add that we should keep the pluto-1.1.x branch at JDK 1.4
compatibility.
What is your strategy on doing the Generics refactoring? Are you doing on
everything at once. or one or more modules at a time?
Thank
Elliot,
I also had failures on the same test: with Maven 2.0.6 and Java 1.5.0_11
on Windows XP.
/Craig
Elliot Metsger <[EMAIL PROTECTED]>
07/05/2007 11:36 AM
Please respond to
pluto-dev@portals.apache.org
To
pluto-dev@portals.apache.org
cc
Subject
Re: Trunk build failing
Daniel,
Pl
Hi Mar, Thank you for this post. Personally, I would welcome the help, but would like to know if someone else is working on a Jira issue that is assigned to me. The best way to do that is to comment to the Jira issue./Craig -"Marc Veary" <[EMAIL PROTECTED]> wrote: -To: pluto-dev From: "Mar
Marc, Can you also add a similar comment to PLUTO-333, so anyone else interested in this issue will be aware of your work? Thanks./Craig-"Marc Veary" <[EMAIL PROTECTED]> wrote: -To: pluto-dev From: "Marc Veary" <[EMAIL PROTECTED]>Date: 07/05/2007 03:43AMSubject: Generics SupportHi, I'm goin
Hi Marc, Any contribution would be greatly appreciated. Please group the patches into functional units (related to build system, deployer, descriptor, documentation, maven pluto plugin, portal driver, portlet container, portlet container taglibs, portlets-admin, portlets-testsuite), create a Jira i
Thank you, Torsten, for your reply.
Can you tell us what JSR-286 features have already been implemented and
committed to the 1.1-286-COMPATIBILITY branch and what features still need
to be implemented? This will allow us to figure out the testsuite tests
that need to be created.
/Craig
De
Thank you, Elliot, for you enthusiasm and offer to help.
I'd like to see the trunk be merged into the 286 branch. I think the
issues that Stefan reported with Preferences and PreferenceValidator would
be fixed by doing that. I also believe that there are a number of fixes
and enhancements in th
David,
Yes, the Univ of Jena group has not done a good job in communicating their
design decisions to the mailing list. But we should also admit that we
have dropped the ball in our code review and helping them do the commits.
I am particularly disappointed in the people who complained loudly a
Hi all,
As part of the development of the JSR-286 Reference Implementation, a copy
of the portlet API jar (found here:
http://ipc658.inf-swt.uni-jena.de/spec/JSR%202.0%20API/lib/) needs to be
deployed to a Maven 2 repository. I was wondering which repository should
I use for this purpose? Shou
Hi Andreas,
Yes, your Jira issue is a duplicate to PLUTO-340, which is more of an
annoyance than a show-stopping bug.
Here's what you have to do to deploy a portlet app in Pluto installed in
Tomcat (the bundled distribution):
1. Create a Tomcat context descriptor, giving it the same name as yo
Hi Elliot,
I wasn't able to reproduce this error because I did not know how the error
(PLUTO-355) was produced in the first place. I hope that Andreas will
provide more details.
However, I did notice that the stack trace was similar to the one I got in
PLUTO-340, which is caused by selecting Ap
Elliot,
I ran the bundled distribution through its paces and everything seems to
be in order. Thanks to you and David for all your hard work on this
release.
BTW, I noticed that a News item was not created for the 1.1.1 release. You
should make sure one is created for 1.1.2. IMHO, it should m
I have pretty much finished with PLUTO-335, but I noticed a few bugs with
the Page Admin Portlet:
1. It does not work in IE (I have version 6).
2. When you select the Apache Pluto Portal Driver application on the Pluto
Page Administrator portlet, you get a PlutoAdmin selection in the next
drop-d
Thank you David, for your thoughtful responses. I like the clarity of the
Struts download page and feel that something like that would be a good
addition to the Pluto web site. If there are obvious flaws with a release,
like a broken Admin Page IMHO, that should be noted prominently too.
I'm no
David,
Why did you change your mind from calling it a beta build when I first
reported the problem with the Page Admin Portlet to marking it a GA build
now? None of the code has changed?
I agree that a distribution does not have to be perfect to be released,
but I think this one has a glaring
see below
> +1 GA
>
> There are two bugs that have been identified that may cause others to
> vote differently, but I don't think they are significant enough to hold
> back this release. One existed in 1.1.0, the other was introduced new.
> 1.1.1 fixes several other issues that I feel are
All the testuite tests pass without a glitch, but the page administration
portlet throws an Exception. I am testing this on Windows 2000 with JDK
1.5.0_04.
Here is the full stack trace:
javax.portlet.PortletException
at
org.apache.pluto.internal.impl.PortletRequestDispatcherImpl.includ
Elliot/David,
Thanks for the response. The build still fails for me, but I'll try again
with a fresh checkout.
Are there any special incantations you need to put in settings.xml?
TIA
/Craig
"Elliot Metsger" <[EMAIL PROTECTED]>
03/02/2007 10:04 AM
Please respond to
pluto-dev@portals.apache.
David/Elliiot,
Maybe I had a pre-release version of 1.1.0 install on my machine. But I
just downloaded the bundled version of Pluto 1.1.0
(pluto-current-bundle.zip) using the link on the Pluto home page and
installed it. Going to the Misc Test page in either Testsuite portlet
produces the same
Hi Elliot,
I got this failure from a posted 1.1.0 build.
/Craig
Elliot Metsger <[EMAIL PROTECTED]>
02/28/2007 11:12 AM
Please respond to
pluto-dev@portals.apache.org
To
pluto-dev@portals.apache.org
cc
Subject
Re: [jira] Commented: (PLUTO-319) checkContextServerInfo test on Misc Test
page
David,
I'm fine with any new versioning scheme, just as long as it is well
defined and documented. I think we need to have at least some 'sub GA'
designation for releases to indicate quality of the build. Perhaps just
sticking with the Release Candidate designation is the best way to do
this.
Hi David,
That's fine with me. I just was going to suggest that you add the fact
that 1.0.1 has been 'archived' to the 1.1.0 release announcement, but I'm
too late with that suggestion :).
Is all the 1.1 documentation up to date including the build instructions?
I know that you have changed th
I want to add something to the the Pluto FAQ (a reference to a wiki page I created on remote debugging - see http://wiki.apache.org/portals/Pluto/RemoteDebuggingWithPluto), but the source code does not appear to be in the pluto-site module. In the Pluto 1.0.1 branch, the FAQ is within the xdocs mod
I did not notice before the 5 second wait requirement for this test. Doh!
When I did that the test did pass on Test Portlet #1.
However, the test consistently fails on Test Portlet #2 even after the 5
seconds wait. I will report that as a separate Jira issue, but I do not
think this should be a
Hi David,I checked out the Pluto Page Administrator and it works very well. I have a couple of comments:1. Since its operation is not intiutive, can you add a help mode page to this portlet explaining how to use it?2. I added an 'Upload and deploy new portlet war' link to the bottom of the Page Adm
I am still getting failure of this (testsuite test #10) on both a Pluto-1.1-beta2 and a snapshot that I built last night from the SVN trunk. Can anyone else confirm whether testsuite test #10 works (or fails)?/Craig-"David DeWolf (JIRA)" <[EMAIL PROTECTED]> wrote: -To: pluto-dev@portals.apa
David,
I agree with pretty much everything you say below. I was playing Devil's
advocate in my original comments. I didn't want us to jump the gun and was
hoping for more input from others.
Yes, we should move forward with a Pluto 1.1 release with what we have
right now although it probably w
Thank you, David, for working through all the Jira issues you have for the
past few days. It seems that Pluto 1.1 GA is in our sights.
But, from a users standpoint, I'm not sure if releasing Pluto 1.1 without
page layout or preferences persistence is such a good thing. It seems to
be a step bac
See below >To: pluto-dev@portals.apache.org, Oliver Spindler><[EMAIL PROTECTED]>>From: "David H. DeWolf" <[EMAIL PROTECTED]>>Sent by: "David H. DeWolf" <[EMAIL PROTECTED]>>Date: 12/04/2006 09:04PM>Subject: [Fwd: Admin Portlet]>>Hi Oliver,>>I'm forwarding this to the pluto-dev list. All of these di
Hi Chuck,
Thanks for chiming in. See below.
Charles Severance <[EMAIL PROTECTED]> wrote on 12/04/2006 11:59:08 AM:
>
> On Dec 4, 2006, at 11:43 AM, David H. DeWolf wrote:
>
> > [EMAIL PROTECTED] wrote:
> >> Since David has simplified the registration of portlets, that
> >> means that some of
See below:
"David H. DeWolf" <[EMAIL PROTECTED]> wrote on 12/04/2006 11:43:00 AM:
>
>
> [EMAIL PROTECTED] wrote:
> >
> > Hi all,
> >
> > Yes, both David and I are working on this too. Great minds think
alike ;).
> >
> > Anyway, I think Jira is the best way of discussing development issues
Hi all,
Yes, both David and I are working on this too. Great minds think alike
;).
Anyway, I think Jira is the best way of discussing development issues like
this as we have been doing with the JSR-286 stuff. Can we continue this
discussion under PLUTO-215 or create another issue that focuses
Stefan asked me to forward this announcement to the mail list./Craig -Forwarded by Craig Doremus/Info Tech/Corp/HBC on 12/03/2006 11:23PM -To: [EMAIL PROTECTED]From: Stefan Hepper <[EMAIL PROTECTED]>Date: 12/01/2006 11:53AMSubject: Fw: draft 9 availableCraig,after having my machine newly in
working on was to prevent
> this from being necessary. Please explain!
>
> Thanks,
>
>
> David
>
> [EMAIL PROTECTED] wrote:
>> Author: cdoremus
>> Date: Sun Dec 3 08:37:10 2006
>> New Revision: 481799
>>
>> URL: http://svn.apache.org/viewvc?vie
>>Thanks for applying all these Craig!>You're welcome, David. I will try to pitch in when I am able, but I hope that other Apache Portals committers will also help when they have the time, since there was so much interest in the 286 RI when it was proposed to be hosted by Pluto back in August. It
I've checked the latest JSR-286 API
sources into the 1.1-286-COMPATIBILITY branch in a portlet2-api directory
including a Maven 2 pom.xml file that builds the jar having 2.0-SNAPSHOT
as the version, which I thought was appropriate (unless anyone objects).
I've also done some work with other
pom f
I've been working with David to get
beta2 out there. I have everything in the dist directories now soft linked
to pluto-current* , which should take some time to propagate to all the
mirrors. At that time, the web site will be updated with beta2 as the current
Pluto-1.1.0 download. I'll probably d
+1 Thank you, David, for all your hard work on this./Craig-"David H. DeWolf" <[EMAIL PROTECTED]> wrote: -To: "David H. DeWolf" <[EMAIL PROTECTED]>From: "David H. DeWolf" <[EMAIL PROTECTED]>Sent by: "David H. DeWolf" <[EMAIL PROTECTED]>Date: 10/03/2006 07:59PMcc: pluto-dev@portals.apache.org
David,
I've updated the README file to reflect
the Pluto-1.1.0-beta2 status of Jira issues (bug fixes, etc) and checked
them into the SVN trunk and release-1.1.0-beta2 branch. I think this one
should be in the beta2 binary and source distributions we release. What
is currently in this cut is a be
David, I know that Elliot is close to a solution for PLUTO-233, which I think is the biggest outstanding Pluto 1.1 bug. It would be good to get that one bagged for beta2./Craig-"David H. DeWolf" <[EMAIL PROTECTED]> wrote: -To: pluto-dev@portals.apache.orgFrom: "David H. DeWolf" <[EMAIL PROT
Hi Elliot Sorry that my first reply was lost. See below. -Elliot Metsger <[EMAIL PROTECTED]> wrote: ->To: pluto-dev@portals.apache.org>From: Elliot Metsger <[EMAIL PROTECTED]>>Date: 09/04/2006 06:13AM>Subject: Re: Portlet modes and buttons in the 1.1 portal driver>>Hey Craig,>>Thanks for th
David, Thanks for confirming this. I guess I'll go back to the drawing board./Craig-"David H. DeWolf" <[EMAIL PROTECTED]> wrote: -To: pluto-dev@portals.apache.orgFrom: "David H. DeWolf" <[EMAIL PROTECTED]>Sent by: "David H. DeWolf" <[EMAIL PROTECTED]>Date: 09/04/2006 08:47AMSubject: Re: [ji
1 - 100 of 189 matches
Mail list logo
