You are viewing a plain text version of this content. The canonical link for it is here.
Posted to pluto-dev@portals.apache.org by "Craig Doremus (JIRA)" <pl...@jakarta.apache.org> on 2005/03/24 01:11:25 UTC

[jira] Commented: (PLUTO-109) Input for RC3 - Maven does not patch automatically $CATALINA_HOME/conf/server.xml to enable Application Scoped session attributes.

     [ http://issues.apache.org/jira/browse/PLUTO-109?page=comments#action_61445 ]
     
Craig Doremus commented on PLUTO-109:
-------------------------------------

Used Ant replace task in distribute:binary goal of base maven.xml file to fix this one.

> Input for RC3 - Maven does not patch automatically $CATALINA_HOME/conf/server.xml to enable Application Scoped session attributes.
> ----------------------------------------------------------------------------------------------------------------------------------
>
>          Key: PLUTO-109
>          URL: http://issues.apache.org/jira/browse/PLUTO-109
>      Project: Pluto
>         Type: Bug
>     Versions: 1.0.1-rc3
>     Reporter: Michael Blum
>     Priority: Minor

>
> I made these comments on Pluto's developer mailing list as subject "Input for RC3". I was asked to put them into Jira too. Please take my apologies for being so late. 
> Michael
> Here are my comments from 02/04/2005 :
> In between my issues against Tomcat 5.5.4 from December have been resolved with the Tomcat release 5.5.7. This release has included fixes for the Tomcat bugs 28709 and 32832 which were related to portlet sessions of Pluto. I think Tomcat 5.5.7 is the a good release for the next binary release of Pluto.
> There is one minor obstacle left. When building Pluto and deploying it to Tomcat, maven does not patch automatically $CATALINA_HOME/conf/server.xml to enable Application Scoped session attributes. Until today I have had to manually  add to the Connector element the attribute "emptySessionPath=true".
> Here a complete example of this element for illustration purposes.
> <Connector port="8080"
>            maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
>            enableLookups="false" redirectPort="8443" acceptCount="100"
>            connectionTimeout="20000" disableUploadTimeout="true"
>            emptySessionPath="true" />
> I would really appreciate to have this added by maven, if possible. I allways forget to add it by myself.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Re: Closing Issues (was Re: [jira] Commented: (PLUTO-109) )

Posted by Carsten Ziegeler <cz...@apache.org>.
David H. DeWolf wrote:
> Great question!
> 
> I've been resolving issues and leaving them for closure by the person 
> that submitted the bug.  Unfortunately in most cases that never happens. 
>   Once in a while, I'll close an issue directly if I resolve it as 
> invalid or won't fix.
> 
> What should our approach be?
> 
I think this is the usual way: you first set the issue to fixed and ask
the reporter to cross check and then close the bug. If after a period of
time, the reporter does not respond, we can imho close the bug then. But
we should give the reporter time to test.

In the case of invalid/won't fix I agree that they can be closed very
quickly - if the reporter has a different opinion he can reopen the bug
anyway.

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

Closing Issues (was Re: [jira] Commented: (PLUTO-109) )

Posted by "David H. DeWolf" <dd...@apache.org>.
Great question!

I've been resolving issues and leaving them for closure by the person 
that submitted the bug.  Unfortunately in most cases that never happens. 
  Once in a while, I'll close an issue directly if I resolve it as 
invalid or won't fix.

What should our approach be?

David

CDoremus@hannaford.com wrote:
> 
> Thanks, Carsten. I changed PLUTO-109 to Resolved. What is the criteria 
> for moving a Jira issue to the Closed state?
> /Craig
> 
> 
> 
> *Carsten Ziegeler <cz...@apache.org>*
> 
> 03/24/2005 07:45 AM
> Please respond to
> pluto-dev@portals.apache.org
> 
> 
> 	
> To
> 	pluto-dev@portals.apache.org
> cc
> 	
> Subject
> 	Re: [jira] Commented: (PLUTO-109) Input for RC3 - Maven does not patch 
> automatically $CATALINA_HOME/conf/server.xml to enable Application 
> Scoped session attributes.
> 
> 
> 	
> 
> 
> 
> 
> 
> Craig Doremus wrote:
>  > Hi Carsten:
>  >
>  > I didn't realize I had two accounts. To get into Jira I use the user
>  > name cdoremus; my email for that account is craig@maine.com. I hope
>  > that's what you need.
>  >
> Hi Craig,
> 
> you are also registered under the user craig@maine.com (with the same
> email). I just added the user cdoremus to the Pluto project, so you
> should now be able to change issues.
> 
> Should I delete the other user (craig@maine.com)?
> 
> Carsten
> 
> -- 
> Carsten Ziegeler - Open Source Group, S&N AG
> http://www.s-und-n.de
> http://www.osoco.org/weblogs/rael/
> 

Re: [jira] Commented: (PLUTO-109) Input for RC3 - Maven does not patch automatically $CATALINA_HOME/conf/server.xml to enable Application Scoped session attributes.

Posted by CD...@hannaford.com.
Thanks, Carsten. I changed PLUTO-109 to Resolved. What is the criteria for 
moving a Jira issue to the Closed state?
/Craig




Carsten Ziegeler <cz...@apache.org> 
03/24/2005 07:45 AM
Please respond to
pluto-dev@portals.apache.org


To
pluto-dev@portals.apache.org
cc

Subject
Re: [jira] Commented: (PLUTO-109) Input for RC3 - Maven does not patch 
automatically $CATALINA_HOME/conf/server.xml to enable Application Scoped 
session attributes.






Craig Doremus wrote:
> Hi Carsten:
> 
> I didn't realize I had two accounts. To get into Jira I use the user 
> name cdoremus; my email for that account is craig@maine.com. I hope 
> that's what you need.
> 
Hi Craig,

you are also registered under the user craig@maine.com (with the same
email). I just added the user cdoremus to the Pluto project, so you
should now be able to change issues.

Should I delete the other user (craig@maine.com)?

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/


Re: [jira] Commented: (PLUTO-109) Input for RC3 - Maven does not patch automatically $CATALINA_HOME/conf/server.xml to enable Application Scoped session attributes.

Posted by Carsten Ziegeler <cz...@apache.org>.
Craig Doremus wrote:
> Hi Carsten:
> 
> I didn't realize I had two accounts. To get into Jira I use the user 
> name cdoremus; my email for that account is craig@maine.com. I hope 
> that's what you need.
> 
Hi Craig,

you are also registered under the user craig@maine.com (with the same
email). I just added the user cdoremus to the Pluto project, so you
should now be able to change issues.

Should I delete the other user (craig@maine.com)?

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

Re: [jira] Commented: (PLUTO-109) Input for RC3 - Maven does not patch automatically $CATALINA_HOME/conf/server.xml to enable Application Scoped session attributes.

Posted by Craig Doremus <cr...@maine.com>.
Hi Carsten:

I didn't realize I had two accounts. To get into Jira I use the user 
name cdoremus; my email for that account is craig@maine.com. I hope 
that's what you need.

TIA
/Craig

>David H. DeWolf wrote:
>  
>
>>Craig,
>>
>>I noticed that you commented on this bug but didn't resolve it.  It made 
>>me wonder if you've been given full Jira access yet.  I think Carsten's 
>>our JIRA admin; you probably want to ping him if not.
>>
>>David
>>
>>    
>>
>No, Craig is not in the pluto list for jira - if you want, Craig, just
>let me know which of your two accounts should be added to pluto.
>
>Carsten
>
>  
>


Re: [jira] Commented: (PLUTO-109) Input for RC3 - Maven does not patch automatically $CATALINA_HOME/conf/server.xml to enable Application Scoped session attributes.

Posted by Carsten Ziegeler <cz...@apache.org>.
David H. DeWolf wrote:
> Craig,
> 
> I noticed that you commented on this bug but didn't resolve it.  It made 
> me wonder if you've been given full Jira access yet.  I think Carsten's 
> our JIRA admin; you probably want to ping him if not.
> 
> David
> 
No, Craig is not in the pluto list for jira - if you want, Craig, just
let me know which of your two accounts should be added to pluto.

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

Re: [jira] Commented: (PLUTO-109) Input for RC3 - Maven does not patch automatically $CATALINA_HOME/conf/server.xml to enable Application Scoped session attributes.

Posted by "David H. DeWolf" <dd...@apache.org>.
Craig,

I noticed that you commented on this bug but didn't resolve it.  It made 
me wonder if you've been given full Jira access yet.  I think Carsten's 
our JIRA admin; you probably want to ping him if not.

David

Craig Doremus (JIRA) wrote:
>      [ http://issues.apache.org/jira/browse/PLUTO-109?page=comments#action_61445 ]
>      
> Craig Doremus commented on PLUTO-109:
> -------------------------------------
> 
> Used Ant replace task in distribute:binary goal of base maven.xml file to fix this one.
> 
> 
>>Input for RC3 - Maven does not patch automatically $CATALINA_HOME/conf/server.xml to enable Application Scoped session attributes.
>>----------------------------------------------------------------------------------------------------------------------------------
>>
>>         Key: PLUTO-109
>>         URL: http://issues.apache.org/jira/browse/PLUTO-109
>>     Project: Pluto
>>        Type: Bug
>>    Versions: 1.0.1-rc3
>>    Reporter: Michael Blum
>>    Priority: Minor
> 
> 
>>I made these comments on Pluto's developer mailing list as subject "Input for RC3". I was asked to put them into Jira too. Please take my apologies for being so late. 
>>Michael
>>Here are my comments from 02/04/2005 :
>>In between my issues against Tomcat 5.5.4 from December have been resolved with the Tomcat release 5.5.7. This release has included fixes for the Tomcat bugs 28709 and 32832 which were related to portlet sessions of Pluto. I think Tomcat 5.5.7 is the a good release for the next binary release of Pluto.
>>There is one minor obstacle left. When building Pluto and deploying it to Tomcat, maven does not patch automatically $CATALINA_HOME/conf/server.xml to enable Application Scoped session attributes. Until today I have had to manually  add to the Connector element the attribute "emptySessionPath=true".
>>Here a complete example of this element for illustration purposes.
>><Connector port="8080"
>>           maxThreads="150" minSpareThreads="25" maxSpareThreads="75"
>>           enableLookups="false" redirectPort="8443" acceptCount="100"
>>           connectionTimeout="20000" disableUploadTimeout="true"
>>           emptySessionPath="true" />
>>I would really appreciate to have this added by maven, if possible. I allways forget to add it by myself.
> 
>