-286-COMPATIBILITY branch into the Pluto trunk.
> Merge SVN trunk with 1.1-286-COMPATIBILITY branch using 1.1-286-trunk-merge
> branch
> ---
>
> Key: PLUTO-402
>
trunk.
> Merge pluto-descriptor-impl code from trunk to 1.1-286-trunk-merge branch
> -
>
> Key: PLUTO-413
> URL: https://issues.apache.org/jira/browse/PLUTO-413
>
trunk.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
> URL: https://issues.apache.org/jira/browse/PLUTO-404
> Project: Pluto
>
trunk.
> Merge pluto-ant-tasks code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-412
> URL: https://issues.apache.org/jira/browse/PLUTO-412
> Project: Pluto
>
trunk.
> Merge pluto-portal-driver code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-405
> URL: https://issues.apache.org/jira/browse/PLUTO-405
>
the Pluto trunk.
> Merge pluto-portal-driver-impl code from trunk to 1.1-286-trunk-merge branch
>
>
> Key: PLUTO-406
> URL: https://issues.apache.org/jira/b
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 or correct me if
:55 PM
| To: [EMAIL PROTECTED]
| Subject: svn commit: r609419 -
/portals/pluto/branches/1.1-286-trunk-merge/pluto-testsuite/pom.xml
|
| Author: cdoremus
| Date: Sun Jan 6 13:54:44 2008
| New Revision: 609419
|
| URL: http://svn.apache.org/viewvc?rev=609419&view=rev
| Log:
| Added integration
anuary 06, 2008 10:55 PM
To: [EMAIL PROTECTED]
Subject: svn commit: r609419 -
/portals/pluto/branches/1.1-286-trunk-merge/pluto-testsuite/pom.xml
Author: cdoremus
Date: Sun Jan 6 13:54:44 2008
New Revision: 609419
URL: http://svn.apache.org/viewvc?rev=609419&view=rev
Log:
Added integration
ate at night :-)>>>> Elliot>>>>>> Torsten Dettborn wrote:>>> Hi Elliot,>>>>>> I have updated my local repository and made a second run, with maven and got this error messages.>>>>>> Thanks>>>>>>
Elliot,
I have updated my local repository and made a second run, with maven and got
this error messages.
Thanks
Torsten
[INFO] [jar:jar]
[INFO] Building jar:
D:\Repositories\1.1-286-trunk-merge-060108\pluto-descriptor-impl\target\pluto-descriptor-impl-2.0.0-SNAPSHOT.jar
[INFO] [install:inst
de a second run, with maven and got
>> this error messages.
>>
>> Thanks
>>
>> Torsten
>>
>> [INFO] [jar:jar]
>> [INFO] Building jar:
>> D:\Repositories\1.1-286-trunk-merge-060108\pluto-descriptor-impl\target\pluto-descriptor-impl-2.0.0-S
ff so late at night :-)
Elliot
Torsten Dettborn wrote:
Hi Elliot,
I have updated my local repository and made a second run, with maven and got
this error messages.
Thanks
Torsten
[INFO] [jar:jar]
[INFO] Building jar:
D:\Repositories\1.1-286-trunk-merge-060108\pluto-descriptor-impl\target\
Hi Elliot,
I have updated my local repository and made a second run, with maven and got
this error messages.
Thanks
Torsten
[INFO] [jar:jar]
[INFO] Building jar:
D:\Repositories\1.1-286-trunk-merge-060108\pluto-descriptor-impl\target\pluto-descriptor-impl-2.0.0-SNAPSHOT.jar
[INFO
Ack! That's no good.
Are you using the 286 merge branch? Are you using Maven to build or are
you using Eclipse (or another IDE)?
Commit r609273 and r609358 added test dependencies on jmock-cglib
(1.2.0), spring-mock (2.0.2), and spring-core (v2.0.2). If you have
those libraries in your c
Hi Elliot,
after updating my local repository, my compiler throws a list of errors, how
long would you need to fix it?
Torsten
Elliot Metsger wrote:
Ate Douma wrote:
[EMAIL PROTECTED] wrote:
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
Ate Douma wrote:
[EMAIL PROTECTED] wrote:
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
To: pluto-dev@portals.apache.org
From: Elliot Metsger <[EMAIL PROTECTED]>
Date: 01/04/2008 03:21PM
Subject: Re: [VOTE] Move 1.1-286-trunk-merge branch to trunk
Craig,
I'll take a look at the diff this weekend. A cursory glance shows that
there are actually a
[EMAIL PROTECTED] wrote:
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 a
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, p
lliot Metsger <[EMAIL PROTECTED]> wrote: -To: pluto-dev@portals.apache.orgFrom: Elliot Metsger <[EMAIL PROTECTED]>Date: 01/04/2008 03:21PMSubject: Re: [VOTE] Move 1.1-286-trunk-merge branch to trunkCraig,I'll take a look at the diff this weekend. A cursory glance shows that there a
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 not 100% sure that all
the trunk code has been properly merged with the 1.1-286-trunk-merge branch.
Therefore, I intend to copy the current trunk to a pluto-1.2.0 branch bef
st 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 not 100% sure that all
the trunk code has been properly merged with the 1.1-286-trunk-merge branch.
Therefore, I intend to copy the current trunk to a pluto-1.2.0 branch bef
nce I am not 100% sure that all the trunk code has been properly merged with the 1.1-286-trunk-merge branch. Therefore, I intend to copy the current trunk to a pluto-1.2.0 branch before I move the 1.1-286-trunk-merge branch into the SVN trunk sometime early next week. At a later date when we have a s
r 2.0 they should be merged where
appropriate and 1.2 should be abandoned
-Eric
Elliot Metsger wrote:
Sorry I'm coming in late on this discussion.
I'm +1 for promoting the 286-trunk-merge to trunk, and +1 for bumping
all the pom revs to 2.0.0-SNAPSHOT thereafter. I haven't followe
Elliot Metsger wrote:
[EMAIL PROTECTED] wrote:
>So I think we might need to release the current trunk (as Pluto 1.1.5
>or 1.2, whatever) *before* the 1.1-JSR-286-trunk-merge branch becomes
>trunk.
A few weeks ago, Elliot volunteered to do a Pluto 1.1.5 release and
was preparin
[EMAIL PROTECTED] wrote:
>So I think we might need to release the current trunk (as Pluto 1.1.5
>or 1.2, whatever) *before* the 1.1-JSR-286-trunk-merge branch becomes
>trunk.
A few weeks ago, Elliot volunteered to do a Pluto 1.1.5 release and was
preparing that in the 1.1
Sorry I'm coming in late on this discussion.
I'm +1 for promoting the 286-trunk-merge to trunk, and +1 for bumping
all the pom revs to 2.0.0-SNAPSHOT thereafter. I haven't followed the
286 coding much at all but I fully support its promotion. Thank you to
Craig, Torsten and ot
> A few weeks ago, Elliot volunteered to do a Pluto 1.1.5 release and was
> preparing that in the 1.1.x branch, which, I believe, is a clone of the
> trunk.
Perhaps we should review the JIRA issues slated for 1.2.0, make sure that
the fixes have been applied to the 1.1.x branch where applicable,
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
active
>> Pluto versions... (comparable to for instance Tomcat 5.5.x and Tomcat
>> 6.x development).
> True.
>
>>
>> So I think we might need to release the current trunk (as Pluto 1.1.5 or
>> 1.2, whatever) *before* the 1.1-JSR-286-trunk-merge branch becomes
&
hould 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
> implies, the 1.1-286-trunk-merge branch now has fully integrated trunk code
> into the JSR-286 code.
>
> W
Tomcat 5.5.x and Tomcat
> 6.x development).
True.
>
> So I think we might need to release the current trunk (as Pluto 1.1.5 or
> 1.2, whatever) *before* the 1.1-JSR-286-trunk-merge branch becomes trunk.
> Once the trunk is released, I suggest deleting it and then simply
Hmm, I'
k we might need to release the current trunk (as Pluto 1.1.5 or 1.2,
whatever) *before* the 1.1-JSR-286-trunk-merge branch becomes trunk.
Once the trunk is released, I suggest deleting it and then simply copying the
1.1-286-trunk-merge branch to trunk.
Note: this way we might cause some annoying s
[EMAIL PROTECTED] wrote:
> 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 t
:
https://issues.apache.org/jira/browse/PLUTO-404#action_12550041). The fix for
the final broken test (MiscTest.checkContextServerInfo) was committed in SVN
rev 605359.
> Merge SVN trunk with 1.1-286-COMPATIBILITY branch using 1.1-286-trunk-merge
>
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
implies, the 1.1-286-trunk-merge branch now has fully integrated trunk code
into the JSR-286 code.
When the final RI work is done, Ate Duoma suggested that the code be tagg
+1 (even though I know, I havn't a got a vote)
After we have tested, that trunk-merge is fully backwards compatible to
jsr 168 (as it should be), it's a good point to move it to trunk I think.
[EMAIL PROTECTED] schrieb:
> Hi all,
>
> The JSR-286 Expert Group's work i
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
.
> Merge pluto-descriptor-impl code from trunk to 1.1-286-trunk-merge branch
> -
>
> Key: PLUTO-413
> URL: https://issues.apache.org/jira/browse/PLUTO-413
>
rge pluto-ant-tasks code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-412
> URL: https://issues.apache.org/jira/browse/PLUTO-412
> Project: Pluto
>
nt-tasks code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-412
> URL: https://issues.apache.org/jira/browse/PLUTO-412
> Project: Pluto
>
patch which
includes the old code. This is only the first version, so that everyone who
would like to use ant can download this patch.
> Merge pluto-ant-tasks code from trunk to 1.1-286-trunk-merge branch
> ---
>
>
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 commite
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
-impl.urlfix.patch and introduction_jsp.patch sent
by Ben Gould to pluto-dev on 12/8/2007. in SVN rev 602887. Thank you Ben.
The testsuite portlet now works in the 1.1-286-trunk-merge branch, but the
following errors occur:
Page: ExternalAppScopedAttributeTest
Test
the ExternalAppScopedAttributeTest tests do not
>use a link to confirm the tests.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
>
simply removes the import from PortalCallServiceImpl so that the
correct implementation is used.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
>
om: [EMAIL PROTECTED]Date: 12/09/2007 01:50PMSubject: Re: trunk-merge> > size=2>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
> size=2>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
>
I received the same problem last night when I was working
PROTECTED]Date: 12/08/2007 11:32AMSubject: Re: trunk-merge> there's still work to be done. The testsuite portlets don't error out, but> the test links are missing from the portlets. Ben, can you take a look at> this?> /CraigCraig,I do not really have time to test this out ri
JSR-168 spec. The portlet now renders correctly in the 1.2.0-286-SNAPSHOT
portal. A small victory!
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
>
e
JSR-168 spec. The portlet now renders correctly in the 1.2.0-286-SNAPSHOT
portal. A small victory!
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
&
> there's still work to be done. The testsuite portlets don't error out, but
> the test links are missing from the portlets. Ben, can you take a look at
> this?
> /Craig
Craig,
I do not really have time to test this out right now, but I suspect that
this patch should solve the problem. There was
t the test links are missing from the portlets. Ben, can you take a look at this?/Craig-"Torsten Dettborn" <[EMAIL PROTECTED]> wrote: -To: From: "Torsten Dettborn" <[EMAIL PROTECTED]>Date: 12/07/2007 05:10AMSubject: trunk-mergeHi, i have worked on the trun
Christian,
This is the perfect level of detail - there will be some work - and
you are going to work to make it a little easier here and there.
Now if I get some time - I can know what to scan for in the source.
I think that key thing to remember in terms of the factoring is making
sure tha
Hi Chuck,
there are a few new SPI's that you must implement:
CCPPProfileService.java
EventProvider.java
PublicRenderParameterProvider.java
FilterManager.java
ResourceURLProvider.java
Most of the functionality lies in the portal, because it is not possible
in the container (e.g. the events.) There
Torsten - I understand JSR-286 - that tells portlet writers how to
write new-style portlets.
I am curious for those of us who have portals based on Pluto 1.1.x -
we wrote a bunch of code to make Pluto 1.x handle our JSR-168 support
- things like preference store providers, user attribute pr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Chuck,
the specification proposed final version has a list of all changes of
the specification. See PLT.2.6.3 in rev. 30
http://hnsp.inf-bb.uni-jena.de/spec/JSR%202.0%20Spec/PortletSpec_20_noTrackChanges.pdf
Hope it helps you to get an overvie
Has anyone written up a basic outline/summary of the kinds of
additional SPI implementations we will need to support 286 in our
portal containers?
I am just trying to anticipate how mush work it will be to go from
Pluto 1.x to Pluto 2.x in Sakai.
Thanks in advance. No rush.
/Chuck
On D
12/07/2007 05:10AMSubject: trunk-mergeHi, i have worked on the trunk-merge branch and now it compiles without problems, but i have a problem with starting the portal, are there missing any components from the trunk? This is my error message: 07.12.2007 11:00:48 org.apache.coyote.http11.Http11BaseProtoco
Hi,
i have worked on the trunk-merge branch and now it compiles without problems,
but i have a problem with starting the portal, are there missing any components
from the trunk?
This is my error message:
07.12.2007 11:00:48 org.apache.coyote.http11.Http11BaseProtocol init
INFO: Initializing
PortletContextManager in SVN rev 593883.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
> URL: https://issues.apache.org/jira/b
in SVN
rev 593829.
Also added missing webapp/WEB-INF/fragments/admin/page/ directory and files in
SVN rev 593837.
> Merge pluto-portal code from trunk to 1.1-286-trunk-merge branch
>
>
> Ke
compile
errors -- the getAllPortlets() method needs to be modified since portlet apps
are no longer registered in the pluto-portal-driver-config.xml file.
> Merge pluto-portal-driver-impl code from trunk to 1.1-286-trunk-merge bra
ode from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-405
> URL: https://issues.apache.org/jira/browse/PLUTO-405
> Project: Pluto
>
PortletContainerImpl. Please look at this
Torsten.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
> URL: https://issues.apache.org/jira/b
errors in PortletContextManager and PortletContainerImpl. Please look at this
Torsten.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
>
updateToRev26_container_fixes102307.patch has been applied
to the 1.1-286-trunk-merge branch except for changes to PortalDriverServlet (in
pluto-portal-driver module). That class will be applied with other changes to
pluto-portal-driver when PLUTO-406 is addressed.
was (Author: cdoremus):
Applied part of
PortletURLProvider.setSecure()
calls in PortletContainerImpl and BaseURLImpl in SVN rev 590627.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
> URL: https://issues.
need the merged pluto-container module
> finished before I can continue my work.
> /Craig
>
> -"Torsten Dettborn" wrote: -
>
> To:
> From: "Torsten Dettborn"
> Date: 10/27/2007 01:51PM
> Subject: Re: [jira] Commented: (PLUTO-404) Merge pluto-containe
d before I can continue my
> work. /Craig
>
> -"Torsten Dettborn" <[EMAIL PROTECTED]> wrote: -
>
> To: From: "Torsten Dettborn"
> <[EMAIL PROTECTED]> Date: 10/27/2007 01:51PM Subject: Re:
> [jira] Commented: (PLUTO-404) Merge pluto-conta
n" <[EMAIL PROTECTED]>Date: 10/27/2007 01:51PMSubject: Re: [jira] Commented: (PLUTO-404) Merge pluto-container code from trunk to 1.1-286-trunk-merge branch-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Craig, this is only an update, in the next days i will commit some classes which
ase
> specify what classes were merged. Or is this just an update to JSR-286 Rev 26?
>
>> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
>> ---
>>
>> Key: PLUTO-4
to
actually merge the pluto-container module into the trunk? If so, please specify
what classes were merged. Or is this just an update to JSR-286 Rev 26?
> Merge pluto-container code from trunk to 1.1-286-trunk-merge bra
updateToRev26_container_fixes102307.patch in PLUTO-404 in SVN Rev 589139.
> Merge SVN trunk with 1.1-286-COMPATIBILITY branch using 1.1-286-trunk-merge
> branch
> ---
>
> Key: PLUTO-402
> URL: https:/
rom trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
> URL: https://issues.apache.org/jira/browse/PLUTO-404
> Project: Pluto
> Issue Type: Sub-task
>
unk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
> URL: https://issues.apache.org/jira/browse/PLUTO-404
> Project: Pluto
> Issue Type: Sub-task
>
updateToRev26_container_fixes102307.patch to
pluto-portal-driver-impl module in SVN Rev 589135. There may be other changes
in PortalURLParserImpl that I have added since I am in the middle of merging
pluto-portal-driver-impl with the trunk.
> Merge pluto-container code from trunk to 1.1-
[
https://issues.apache.org/jira/browse/PLUTO-405?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Doremus reassigned PLUTO-405:
---
Assignee: Craig Doremus
> Merge pluto-portal-driver code from trunk to 1.1-286-trunk-me
omponents: portal driver
> Affects Versions: 1.1-286-trunk-merge
>Reporter: Craig Doremus
>Assignee: Craig Doremus
> Fix For: 1.1-286-trunk-merge
>
>
> Merge this code with pluto-portal-driver-impl module in SVN trunk.
--
This message is automa
-driver-impl with the trunk (this issue).
> Merge pluto-portal-driver-impl code from trunk to 1.1-286-trunk-merge branch
>
>
> Key: PLUTO-406
> URL: https://issues.apache.
-driver-impl module in SVN Rev 589135. There may be other changes
in PortalURLParserImpl that I have added since I am in the middle of merging
pluto-portal-driver-impl with the trunk.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge bra
and
pluto-descriptor-api modules in SVN Rev 589129.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
> URL: https://issues.apache.org/jira/b
updateToRev26_container_fixes102307.patch to pluto-container
module in SVN Revs 589127 and 589128.
was (Author: cdoremus):
Applied part of updateToRev26_container_fixes102307.patch to
pluto-container module in SVN Rev 589127.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge bra
-container
module in SVN Rev 589127.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
> URL: https://issues.apache.org/jira/browse/PLUTO-404
>
updateToRev26_container_fixes102307.patch to portlet2-api
module in SVN Revs 589118 and 589120.
was (Author: cdoremus):
Applied part of updateToRev26_container_fixes102307.patch to portlet2-api
module in SVN Rev 589118
> Merge pluto-container code from trunk to 1.1-286-trunk-merge bra
module in SVN Rev 589118
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
> URL: https://issues.apache.org/jira/browse/PLUTO-404
>
branch so we have one
working branch with up-to-date JSR-286 changes?
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
> URL: https://issues.
pluto can be compiled. I would be happy, if
anyone can take a look on it.
> Merge pluto-container code from trunk to 1.1-286-trunk-merge branch
> ---
>
> Key: PLUTO-404
> URL: https://is
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 s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Craig,
sorry for the long time a have write nothing, but i was sick. So now
i'm back. The last thing i done, was to fix the bugs, so that the
trunk-merge can be compiled and deployed, but the servlet don't starts
with tomcat. That&
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
586829,586831,586832,586833,586836,586841,586842,586843,586844.
> Merge pluto-portal code from trunk to 1.1-286-trunk-merge branch
>
>
> Key: PLUTO-407
> URL: https://issues.apache.org/jira/browse/PLUTO-407
>
[
https://issues.apache.org/jira/browse/PLUTO-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Craig Doremus reassigned PLUTO-407:
---
Assignee: Craig Doremus
> Merge pluto-portal code from trunk to 1.1-286-trunk-merge bra
-"Torsten Dettborn" <[EMAIL PROTECTED]> wrote: -To: From: "Torsten Dettborn" <[EMAIL PROTECTED]>Date: 10/09/2007 01:55AMSubject: 286-trunk-merge* PGP Signed by an unknown keyHi Craig,I want to ask you, if i can help you with merging the last patches forthe versio
commit in SVN revision 586662.
> Merge pluto-taglib code from trunk to 1.1-286-trunk-merge branch
>
>
> Key: PLUTO-408
> URL: https://issues.apache.org/jira/browse/PLUTO-408
>
tinue with that when I get a chance. Thanks, again./Craig -"Torsten Dettborn" <[EMAIL PROTECTED]> wrote: -To: From: "Torsten Dettborn" <[EMAIL PROTECTED]>Date: 10/09/2007 01:55AMSubject: 286-trunk-merge* PGP Signed by an unknown keyHi Craig,I want to ask you, if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Craig,
I want to ask you, if i can help you with merging the last patches for
the version. I think there must be a cut, so that there is only one
version on which we are working.
Torsten
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Min
1 - 100 of 164 matches
Mail list logo
