date:20090127


ApacheCon EU 2009 registration is now open!
23-27 March -- Mövenpick Hotel, Amsterdam, Netherlands
http://www.eu.apachecon.com/


Registration for ApacheCon Europe 2009 is now open - act before early  
bird prices expire 6 February.  Remember to book a room at the  
Mövenpick and use the Registration Code: Special package attendees for  
the conference registration, and get 150 Euros off your full  
conference registration.


Lower Costs - Thanks to new VAT tax laws, our prices this year are 19%  
lower than last year in Europe!  We've also negotiated a Mövenpick  
rate  of a maximum of 155 Euros per night for attendees in our room  
block.


Quick Links:

  http://xrl.us/aceu09sc  See the schedule
  http://xrl.us/aceu09hc  Get your hotel room
  http://xrl.us/aceu09rc  Register for the conference

Other important notes:

- Geeks for Geeks is a new mini-track where we can feature advanced  
technical content from project committers.  And our Hackathon on  
Monday and Tuesday is open to all attendees - be sure to check it off  
in your registration.


- The Call for Papers for ApacheCon US 2009, held 2-6 November
2009 in Oakland, CA, is open through 28 February, so get your  
submissions in now.  This ApacheCon will feature special events with
some of the ASF's original founders in celebration of the 10th  
anniversary of The Apache Software Foundation.


  http://www.us.apachecon.com/c/acus2009/

- Interested in sponsoring the ApacheCon conferences?  There are plenty
of sponsor packages available - please contact Delia Frees at
de...@apachecon.com for further information.

==
ApacheCon EU 2008: A week of Open Source at it's best!

Hackathon - open to all! | Geeks for Geeks | Lunchtime Sessions
In-Depth Trainings | Multi-Track Sessions | BOFs | Business Panel
Lightning Talks | Receptions | Fast Feather Track | Expo... and more!

--kevan

[jira] Assigned: (GERONIMO-4324) Upgrade to MyFaces v1.2.4


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Bohn reassigned GERONIMO-4324:
--

Assignee: Joe Bohn

> Upgrade to MyFaces v1.2.4
> -
>
> Key: GERONIMO-4324
> URL: https://issues.apache.org/jira/browse/GERONIMO-4324
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: dependencies
>Affects Versions: 2.0.3, 2.1.4, 2.2
>Reporter: Donald Woods
>Assignee: Joe Bohn
>Priority: Minor
> Fix For: Wish List
>
>
> Upgrade to MyFaces v1.2.4 released on August 30th.
> Release Notes - 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&styleName=Html&version=12313378

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Commented: (GERONIMO-4324) Upgrade to MyFaces v1.2.6


[ 
https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12667701#action_12667701
 ] 

Joe Bohn commented on GERONIMO-4324:


MyFaces 1.2.6 was released.

> Upgrade to MyFaces v1.2.6
> -
>
> Key: GERONIMO-4324
> URL: https://issues.apache.org/jira/browse/GERONIMO-4324
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: dependencies
>Affects Versions: 2.0.3, 2.1.4, 2.2
>Reporter: Donald Woods
>Assignee: Joe Bohn
>Priority: Minor
> Fix For: 2.1.4, 2.2
>
>
> Upgrade to MyFaces v1.2.4 released on August 30th.
> Release Notes - 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&styleName=Html&version=12313378

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4324) Upgrade to MyFaces v1.2.6


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Bohn updated GERONIMO-4324:
---

Fix Version/s: (was: Wish List)
   2.2
   2.1.4
  Summary: Upgrade to MyFaces v1.2.6  (was: Upgrade to MyFaces v1.2.4)

> Upgrade to MyFaces v1.2.6
> -
>
> Key: GERONIMO-4324
> URL: https://issues.apache.org/jira/browse/GERONIMO-4324
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: dependencies
>Affects Versions: 2.0.3, 2.1.4, 2.2
>Reporter: Donald Woods
>Assignee: Joe Bohn
>Priority: Minor
> Fix For: 2.1.4, 2.2
>
>
> Upgrade to MyFaces v1.2.4 released on August 30th.
> Release Notes - 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&styleName=Html&version=12313378

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4324) Upgrade to MyFaces v1.2.6


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Joe Bohn updated GERONIMO-4324:
---

Description: 
Upgrade to MyFaces v1.2.6 released on January 26, 2009



  was:
Upgrade to MyFaces v1.2.4 released on August 30th.
Release Notes - 
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10600&styleName=Html&version=12313378



> Upgrade to MyFaces v1.2.6
> -
>
> Key: GERONIMO-4324
> URL: https://issues.apache.org/jira/browse/GERONIMO-4324
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: dependencies
>Affects Versions: 2.0.3, 2.1.4, 2.2
>Reporter: Donald Woods
>Assignee: Joe Bohn
>Priority: Minor
> Fix For: 2.1.4, 2.2
>
>
> Upgrade to MyFaces v1.2.6 released on January 26, 2009

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Re: [VOTE] Release XBean 3.5 - rc2

2009-01-27 Thread Joe Bohn


my +1

Joe

Joe Bohn wrote:
I uploaded a second distribution of XBean 3.5 which should include the 
NOTICE/LICENSE files in all the appropriate places (I hope).  The same 
changes are present in this candidate that were present in the last one:

   * SocketAddress factory example for Alex [1]
   * XBEAN-111 Only register Converters with the VM when requested [2]
   * Make dependencies optional [3]
   * XBEAN-114 generify xbean-naming [4]
   * XBEAN-115 Fix rebind of entry added using deepBind [5]
   * XBEAN-115 similar fix to for WritableContext for consistency [6]
   * try to follow apache policy and not deploy timestamped snapshots [7]
   * Fix classloader name when throwing a CNFE [8]
   * Let the tests pass on non-MacOS OSes [9]
   * XBEAN-120 Search for semi-annotated classes in inheritance tree (as 
if @Inherited's applied) [10]
   * XBEAN-120 Search for semi-annotated classes in inheritance tree (as 
if @Inherited's applied) [11]

   * update copyright years to include 2009 [12]
   * add a siteId property to assist in release [13]

Please help validate this release.  I'm a little concerned about 
xbean-spring as I noticed some errors fly by during the release process 
but everything eventually passed successfully.  I'll start validating 
this in a Geronimo server image but at the moment it will only utilize 
xbean-naming 3.5.


The staging repository is available at
http://people.apache.org/~jbohn/staging-repo/xbean/
and the tag is available at
http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.5/

I've run the rat tool to validate license headers.

Please review and vote:
   [ ] +1 Release XBean 3.5
   [ ] -1 Do not, because ...

The vote will be open for 72 hours or longer as necessary to validate 
the images and get sufficient participation in the vote.


[1] http://svn.apache.org/viewvc?view=rev&revision=689356
[2] http://svn.apache.org/viewvc?view=rev&revision=703580
[3] http://svn.apache.org/viewvc?view=rev&revision=705314
[4] http://svn.apache.org/viewvc?view=rev&revision=707161
[5] http://svn.apache.org/viewvc?view=rev&revision=707227
[6] http://svn.apache.org/viewvc?view=rev&revision=707230
[7] http://svn.apache.org/viewvc?view=rev&revision=707719
[8] http://svn.apache.org/viewvc?view=rev&revision=725706
[9] http://svn.apache.org/viewvc?view=rev&revision=729545
[10] http://svn.apache.org/viewvc?view=rev&revision=729546
[11] http://svn.apache.org/viewvc?view=rev&revision=731945
[12] http://svn.apache.org/viewvc?view=rev&revision=737042
[13] http://svn.apache.org/viewvc?view=rev&revision=737184


Thanks,
Joe

Re: svn commit: r738106 - in /geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view: ca/confirmCA.jsp ca/setupCA.jsp ca/unlockCA.jsp keystore/confirmKey.jsp k

2009-01-27 Thread Joe Bohn


Heh .. you beat me to the check-in.

I have a number of additional changes from get->post (hopefully I hit 
all the remaining references).   I'm building and running tests now to 
make sure I didn't make any typos.  When that finishes I'll update to 
get your changes and merge anything necessary before I check in.


This is just a heads-up to let you know that I'm making some of the same 
changes with a check-in soon.


Joe


dwo...@apache.org wrote:

Author: dwoods
Date: Tue Jan 27 14:58:28 2009
New Revision: 738106

URL: http://svn.apache.org/viewvc?rev=738106&view=rev
Log:
part 3 of more cleanup of old forms (see Rev735746 for part 2)

Modified:

geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/confirmCA.jsp

geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/setupCA.jsp

geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/unlockCA.jsp

geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/confirmKey.jsp

geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/unlockKey.jsp

geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/unlockKeystore.jsp

Modified: 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/confirmCA.jsp
URL: 
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/confirmCA.jsp?rev=738106&r1=738105&r2=738106&view=diff
==
--- 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/confirmCA.jsp
 (original)
+++ 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/confirmCA.jsp
 Tue Jan 27 14:58:28 2009
@@ -26,7 +26,7 @@
 
 
 
-

+
 
 
 

Modified: 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/setupCA.jsp
URL: 
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/setupCA.jsp?rev=738106&r1=738105&r2=738106&view=diff
==
--- 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/setupCA.jsp
 (original)
+++ 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/setupCA.jsp
 Tue Jan 27 14:58:28 2009
@@ -44,8 +44,8 @@
 alert('validFrom date must be before validTo date');
 return false;
 }
-// Check if password and confirm password match
-if(document.forms[formName].password.value != 
document.forms[formName].confirm.value) {
+// Check if password and confirmPassword match
+if(document.forms[formName].password.value != 
document.forms[formName].confirmPassword.value) {
 alert('password and confirm password do not match.');
 document.forms[formName].password.focus();
 return false;
@@ -143,7 +143,7 @@
 
 :
 
-
+
 
 
  

Modified: 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/unlockCA.jsp
URL: 
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/unlockCA.jsp?rev=738106&r1=738105&r2=738106&view=diff
==
--- 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/unlockCA.jsp
 (original)
+++ 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/unlockCA.jsp
 Tue Jan 27 14:58:28 2009
@@ -38,7 +38,7 @@
 
 
 
-

+
 
 :
 

Modified: 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/confirmKey.jsp
URL: 
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/confirmKey.jsp?rev=738106&r1=738105&r2=738106&view=diff
==
--- 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/confirmKey.jsp
 (original)
+++ 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/confirmKey.jsp
 Tue Jan 27 14:58:28 2009
@@ -23,7 +23,7 @@
 
 
 
-

+
 
 
 

Modified: 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/

Cannot Start Geronimo server in RSA 7.5

2009-01-27 Thread Michael2


I added the Apache Geronimo server 2.1 adapter in RSA 7.5 through WTP and was
able to add the Geronimo server to the RSA server list. But I have a problem
to start it. When I click the Server Start button, the server will start in
the console, I can see the message:

.
Web Applications:
/
/CAHelper
/activemq
/console
/console-base
/debug-views
/dojo
/dojo/0.4
/juddi
/monitoring
/plan-creator
/plugin
/remote-deploy
/system-database

Geronimo Application Server started

but the server state is staying in "starting..." and after a few minutes,
the server will stop and I got a time-out message "Server Apache Geronimo
v2.1 Server at localhost was unable to start within 480 seconds. If the
server requires more time, try increasing the timeout in the server
editor.", although I have tried to increase the Start time in timeouts to
its maximum value.

I have tested with WAS CE 2.1 server and get the same thing.

If I start the Geronimo server outside the RSA, RSA will not read the server
state and still show a "Stopped" state of the server.

Does anyone knows if RSA 7.5 is working for Geronimo 2.1 and WAS CE 2.1?
Anything suggestion how to fix this problem?

Thanks in advance.

-- 
View this message in context: 
http://www.nabble.com/Cannot-Start-Geronimo-server-in-RSA-7.5-tp21688791s134p21688791.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.

Re: svn commit: r738106 - in /geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view: ca/confirmCA.jsp ca/setupCA.jsp ca/unlockCA.jsp keystore/confirmKey.jsp k

2009-01-27 Thread Donald Woods

OK, thanks.  That should be the last form updates I have, unless I find 
another instance where a password field doesn't use "password" as part 
of the value name



-Donald


Joe Bohn wrote:

Heh .. you beat me to the check-in.

I have a number of additional changes from get->post (hopefully I hit 
all the remaining references).   I'm building and running tests now to 
make sure I didn't make any typos.  When that finishes I'll update to 
get your changes and merge anything necessary before I check in.


This is just a heads-up to let you know that I'm making some of the same 
changes with a check-in soon.


Joe


dwo...@apache.org wrote:

Author: dwoods
Date: Tue Jan 27 14:58:28 2009
New Revision: 738106

URL: http://svn.apache.org/viewvc?rev=738106&view=rev
Log:
part 3 of more cleanup of old forms (see Rev735746 for part 2)

Modified:

geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/confirmCA.jsp 


geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/setupCA.jsp 


geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/unlockCA.jsp 


geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/confirmKey.jsp 


geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/unlockKey.jsp 


geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/unlockKeystore.jsp 



Modified: 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/confirmCA.jsp 

URL: 
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/confirmCA.jsp?rev=738106&r1=738105&r2=738106&view=diff 

== 

--- 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/confirmCA.jsp 
(original)
+++ 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/confirmCA.jsp 
Tue Jan 27 14:58:28 2009

@@ -26,7 +26,7 @@
 
 
 
-action="">
+action="" method="POST">

 
 
 

Modified: 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/setupCA.jsp 

URL: 
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/setupCA.jsp?rev=738106&r1=738105&r2=738106&view=diff 

== 

--- 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/setupCA.jsp 
(original)
+++ 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/setupCA.jsp 
Tue Jan 27 14:58:28 2009

@@ -44,8 +44,8 @@
 alert('validFrom date must be before validTo date');
 return false;
 }
-// Check if password and confirm password match
-if(document.forms[formName].password.value != 
document.forms[formName].confirm.value) {

+// Check if password and confirmPassword match
+if(document.forms[formName].password.value != 
document.forms[formName].confirmPassword.value) {

 alert('password and confirm password do not match.');
 document.forms[formName].password.focus();
 return false;
@@ -143,7 +143,7 @@
 
 key="consolebase.common.confirmPassword"/>:

 
-maxlength="200"/>
+size="20" maxlength="200"/>

 
 
  

Modified: 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/unlockCA.jsp 

URL: 
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/unlockCA.jsp?rev=738106&r1=738105&r2=738106&view=diff 

== 

--- 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/unlockCA.jsp 
(original)
+++ 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/ca/unlockCA.jsp 
Tue Jan 27 14:58:28 2009

@@ -38,7 +38,7 @@
 
 
 
-action="">
+action="" method="POST">

 
 :
 

Modified: 
geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/confirmKey.jsp 

URL: 
http://svn.apache.org/viewvc/geronimo/server/branches/2.1/plugins/console/console-base-portlets/src/main/webapp/WEB-INF/view/keystore/confirmKey.jsp?rev=738106&r1=738105&r2=738106&view=diff 

== 

--- 
geronimo/server/branches/2.1/plugins/co

Re: [VOTE] Release XBean 3.5 - rc2


Here's my +1.

I scanned code using RAT, reviewed artifacts, and ran a build.

--kevan

On Jan 26, 2009, at 3:18 PM, Joe Bohn wrote:

I uploaded a second distribution of XBean 3.5 which should include  
the NOTICE/LICENSE files in all the appropriate places (I hope).   
The same changes are present in this candidate that were present in  
the last one:

  * SocketAddress factory example for Alex [1]
  * XBEAN-111 Only register Converters with the VM when requested [2]
  * Make dependencies optional [3]
  * XBEAN-114 generify xbean-naming [4]
  * XBEAN-115 Fix rebind of entry added using deepBind [5]
  * XBEAN-115 similar fix to for WritableContext for consistency [6]
  * try to follow apache policy and not deploy timestamped snapshots  
[7]

  * Fix classloader name when throwing a CNFE [8]
  * Let the tests pass on non-MacOS OSes [9]
  * XBEAN-120 Search for semi-annotated classes in inheritance tree  
(as if @Inherited's applied) [10]
  * XBEAN-120 Search for semi-annotated classes in inheritance tree  
(as if @Inherited's applied) [11]

  * update copyright years to include 2009 [12]
  * add a siteId property to assist in release [13]

Please help validate this release.  I'm a little concerned about  
xbean-spring as I noticed some errors fly by during the release  
process but everything eventually passed successfully.  I'll start  
validating this in a Geronimo server image but at the moment it will  
only utilize xbean-naming 3.5.


The staging repository is available at
   http://people.apache.org/~jbohn/staging-repo/xbean/
and the tag is available at
   http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.5/

I've run the rat tool to validate license headers.

Please review and vote:
  [ ] +1 Release XBean 3.5
  [ ] -1 Do not, because ...

The vote will be open for 72 hours or longer as necessary to  
validate the images and get sufficient participation in the vote.


[1] http://svn.apache.org/viewvc?view=rev&revision=689356
[2] http://svn.apache.org/viewvc?view=rev&revision=703580
[3] http://svn.apache.org/viewvc?view=rev&revision=705314
[4] http://svn.apache.org/viewvc?view=rev&revision=707161
[5] http://svn.apache.org/viewvc?view=rev&revision=707227
[6] http://svn.apache.org/viewvc?view=rev&revision=707230
[7] http://svn.apache.org/viewvc?view=rev&revision=707719
[8] http://svn.apache.org/viewvc?view=rev&revision=725706
[9] http://svn.apache.org/viewvc?view=rev&revision=729545
[10] http://svn.apache.org/viewvc?view=rev&revision=729546
[11] http://svn.apache.org/viewvc?view=rev&revision=731945
[12] http://svn.apache.org/viewvc?view=rev&revision=737042
[13] http://svn.apache.org/viewvc?view=rev&revision=737184


Thanks,
Joe

Re: git, hg or bzr for G development?



On Dec 26, 2008, at 3:48 PM, Jacek Laskowski wrote:

On Thu, Dec 18, 2008 at 7:55 AM, Jason Dillon   
wrote:
I've been doing some experimenting using svn.eu.apache.org with  
git, so far

it has gone well.


What does git have that svn doesn't which makes you so interested in
the subject?


IIUC, the major advantages of GIT are:

* offline commits - you can commit changes, even if online.
* cheap branching - this would make it much simpler for individuals to  
create private local branches and work on implementing a particular  
feature, without interfering with other development they might be  
working on in the same code branch.
* fast merging - given the cheap branching, you need to do a lot of  
merging, which GIT is supposed to do very well


GIT would not be a replacement of SVN. The GIT repositories are  
actually mirroring svn. GIT would just be a new tool for accessing our  
code.


There are some usages of GIT that would not fit well into an Apache  
project. For instance, I would not want to see project members using  
GIT as a private means of sharing code updates. Ultimately, code needs  
to get into our svn repo -- that's where we should be sharing code.


I'm going to look for some guides on using GIT on apache projects.

Barring any objections, I'm going to request that Geronimo be added to  
the GIT mirrors later this week.


--kevan

Re: svn commit: r738120 - /geronimo/server/trunk/pom.xml

2009-01-27 Thread Donald Woods

BTW - the repo1.maven.org mirror that I'm hitting doesn't have the 1.2.6 
artifacts yet



-Donald


jb...@apache.org wrote:

Author: jbohn
Date: Tue Jan 27 16:02:25 2009
New Revision: 738120

URL: http://svn.apache.org/viewvc?rev=738120&view=rev
Log:
GERONIMO-4324 upgrade to MyFaces 1.2.6

Modified:
geronimo/server/trunk/pom.xml

Modified: geronimo/server/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=738120&r1=738119&r2=738120&view=diff
==
--- geronimo/server/trunk/pom.xml (original)
+++ geronimo/server/trunk/pom.xml Tue Jan 27 16:02:25 2009
@@ -1754,7 +1754,7 @@
 
 org.apache.myfaces.core
 myfaces-api
-1.2.3
+1.2.6
 
 
 commons-logging
@@ -1766,7 +1766,7 @@
 
 org.apache.myfaces.core
 myfaces-impl
-1.2.3
+1.2.6
 
 
 commons-logging

Re: [jira] Closed: (GERONIMO-4522) history dependencies.xml file should support property substitutions. Plan processing should use maven filtering, not velocity

2009-01-27 Thread David Jencks

Hi Trygve,

Maybe I broke stuff its a bit hard to tell from your description.
There are two things going on in your build:

1. car-maven-plugin "car" packaging which for each plugin project
builds a plugin and puts it in the local maven repo. It's plausible
that the changes here broke this step.
2. car-maven-plugin assembly packaging which assembles a server out of
the plugins from the maven repo. I don't see how this could have
broken but you never know...

To clarify the situation... IIUC (1) is actually generating artifacts
that get into the local maven repo?? Are these artifacts copied into
the geronimo server repository in (2)? If not, something else must
have changed so these plugins aren't dependencies of the server
assembly project.

back to (1)...
in each plugin project, there should be a target/fliteredplan/plan.xml
file that should be your plan with the property substitutions done
(but not the environment element inserted). Is it there and did the
property substitution work?
Furthermore, there should be target/resources/META-INF/plan.xml which
should be your completed plan file with the dependencies etc included
and target/resources/META-INF/geronimo-;plugin.xml which should have
the dependencies and the category. Finally both these files should be
in the completed car file.

I'd also like to make two suggestions about your build... is a very
bad idea to have projects reference into each others directories or
into other file system locations. I'm not sure why you have a lot of
individual db pools...
- if the db pools are all used in one application, note that you can
set up as many db pools in one plan as you need, as
connectiondefinitiony-instance elements.
- if you actually need separate plugins for each db pool so they can
be used independently, I strongly advise packing the common plan into
a jar file as a resource (in its own project) and then using the maven-
dependency-plugin to unpack it into target/rawplan or similar location.

Please let us know what is wrong.

thanks
david jencks

On Jan 27, 2009, at 6:15 AM, Trygve Hardersen wrote:

I hit a problem today with our custom Geronimo assembly that I think
is related to this:

We have many MySQL DB pools, each represented as a Geronimo plugin.
The plan.xml file for these plugins is very simmilar, so I'm sharing
a common file between the plugins:

db-plugin/pom.xml -->

org.apache.geronimo.buildsupport
car-maven-plugin
true

mysql-pool-plan.xml
${project.parent.basedir}/src/main/plansourceDir>

db-plugin/src/main/plan/mysql-pool-plan.xml -->

http://geronimo.apache.org/xml/ns/j2ee/connector-$
{geronimoSchemaVersion}">

javax.sql.DataSourceconnectionfactory-interface>

${currentDBName}
$
{currentDBHost}
$
{currentDBPort}
$
{currentDBSchema}
$
{currentDBUser}
$
{currentDBPass}

${currentDBMaxPoolSize}size>
${currentDBMinPoolSize}size>
$
{currentDBBlockTimeout}
$
{currentDBIdleTimeout}

db-plugin/db-001/pom.xml -->

db-001
db/shard-001
jdb_shard_001

...

org.apache.geronimo.buildsupport
car-maven-plugin

${connectorDeployer}deploymentConfig>

${productName}

org.tranql
tranql-connector-mysql-localartifactId>

rar

...

The build still works, but the DB plugins are not included in the
final /var/config/config.xml file, so they are not started with the
server. If I create a plan.xml file in src/main/plan for each of the
DB plugins everything works fine.

Is "my way" of doing it not supported any longer, or is this a bug
with Geronimo?

Many thanks for your help!

Trygve

On Mon, Jan 26, 2009 at 9:35 AM, David Jencks (JIRA)
wrote:

[ https://issues.apache.org/jira/browse/GERONIMO-4522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

David Jencks closed GERONIMO-4522.
--

Resolution: Fixed

Implemented rev 737650.

To build g. with ee6 bits first build the jetty7 plugins from
sandbox/djencks then do the main build with

mvn clean install -Pee6,default

> history dependencies.xml file should support property
substitutions. Plan

Re: svn commit: r738120 - /geronimo/server/trunk/pom.xml

2009-01-27 Thread Joe Bohn


Yep, I discovered that a short while ago.

I had pulled the image that was up for vote and so it was in my local 
repo - hence I didn't catch that.  The artifacts were pushed out 
yesterday so I hope they show up soon.  I will back it out if it doesn't 
show up in the mirrors soon.


Joe


Donald Woods wrote:
BTW - the repo1.maven.org mirror that I'm hitting doesn't have the 1.2.6 
artifacts yet



-Donald


jb...@apache.org wrote:

Author: jbohn
Date: Tue Jan 27 16:02:25 2009
New Revision: 738120

URL: http://svn.apache.org/viewvc?rev=738120&view=rev
Log:
GERONIMO-4324 upgrade to MyFaces 1.2.6

Modified:
geronimo/server/trunk/pom.xml

Modified: geronimo/server/trunk/pom.xml
URL: 
http://svn.apache.org/viewvc/geronimo/server/trunk/pom.xml?rev=738120&r1=738119&r2=738120&view=diff 

== 


--- geronimo/server/trunk/pom.xml (original)
+++ geronimo/server/trunk/pom.xml Tue Jan 27 16:02:25 2009
@@ -1754,7 +1754,7 @@
 
 org.apache.myfaces.core
 myfaces-api
-1.2.3
+1.2.6
 
 
 commons-logging
@@ -1766,7 +1766,7 @@
 
 org.apache.myfaces.core
 myfaces-impl
-1.2.3
+1.2.6
 
 
 commons-logging

Re: git, hg or bzr for G development?

2009-01-27 Thread Jason Dillon


On Jan 28, 2009, at 12:07 AM, Kevan Miller wrote:

What does git have that svn doesn't which makes you so interested in
the subject?


IIUC, the major advantages of GIT are:

* offline commits - you can commit changes, even if online.
* cheap branching - this would make it much simpler for individuals  
to create private local branches and work on implementing a  
particular feature, without interfering with other development they  
might be working on in the same code branch.
* fast merging - given the cheap branching, you need to do a lot of  
merging, which GIT is supposed to do very well


GIT would not be a replacement of SVN. The GIT repositories are  
actually mirroring svn. GIT would just be a new tool for accessing  
our code.


There are some usages of GIT that would not fit well into an Apache  
project. For instance, I would not want to see project members using  
GIT as a private means of sharing code updates. Ultimately, code  
needs to get into our svn repo -- that's where we should be sharing  
code.


Why do you have a problem with users sharing code via their own GIT  
repos?  I guess I can kinda see your concern, but I'd expect folks  
with significant changes to the codebase to want to share their GIT  
repos with others *before* pushing those changes back into SVN.



Barring any objections, I'm going to request that Geronimo be added  
to the GIT mirrors later this week.


No objections here, so far I really like GIT, only thing I don't like  
is the huge wait while I setup my local repo due to the crazy ASF SVN  
singleton repository.


--jason

Re: git, hg or bzr for G development?

2009-01-27 Thread Jay D. McHugh

It seems like using git could provide some really compelling advantages.

At least one of which would be to enable the security team to put
together a patch set outside of SVN.  That would make it easier for us
to compile, test, and save partial fixes to security problems without
having the subversion commit logs reveal the issues prematurely.

Jay

Kevan Miller wrote:
> 
> On Dec 26, 2008, at 3:48 PM, Jacek Laskowski wrote:
> 
>> On Thu, Dec 18, 2008 at 7:55 AM, Jason Dillon > > wrote:
>>> I've been doing some experimenting using svn.eu.apache.org with git,
>>> so far
>>> it has gone well.
>>
>> What does git have that svn doesn't which makes you so interested in
>> the subject?
> 
> IIUC, the major advantages of GIT are:
> 
> * offline commits - you can commit changes, even if online. 
> * cheap branching - this would make it much simpler for individuals to
> create private local branches and work on implementing a particular
> feature, without interfering with other development they might be
> working on in the same code branch.
> * fast merging - given the cheap branching, you need to do a lot of
> merging, which GIT is supposed to do very well
> 
> GIT would not be a replacement of SVN. The GIT repositories are actually
> mirroring svn. GIT would just be a new tool for accessing our code. 
> 
> There are some usages of GIT that would not fit well into an Apache
> project. For instance, I would not want to see project members using GIT
> as a private means of sharing code updates. Ultimately, code needs to
> get into our svn repo -- that's where we should be sharing code.
> 
> I'm going to look for some guides on using GIT on apache projects.
> 
> Barring any objections, I'm going to request that Geronimo be added to
> the GIT mirrors later this week.
> 
> --kevan

Re: git, hg or bzr for G development?



On Jan 27, 2009, at 12:47 PM, Jason Dillon wrote:


On Jan 28, 2009, at 12:07 AM, Kevan Miller wrote:

What does git have that svn doesn't which makes you so interested in
the subject?


IIUC, the major advantages of GIT are:

* offline commits - you can commit changes, even if online.
* cheap branching - this would make it much simpler for individuals  
to create private local branches and work on implementing a  
particular feature, without interfering with other development they  
might be working on in the same code branch.
* fast merging - given the cheap branching, you need to do a lot of  
merging, which GIT is supposed to do very well


GIT would not be a replacement of SVN. The GIT repositories are  
actually mirroring svn. GIT would just be a new tool for accessing  
our code.


There are some usages of GIT that would not fit well into an Apache  
project. For instance, I would not want to see project members  
using GIT as a private means of sharing code updates. Ultimately,  
code needs to get into our svn repo -- that's where we should be  
sharing code.


Why do you have a problem with users sharing code via their own GIT  
repos?  I guess I can kinda see your concern, but I'd expect folks  
with significant changes to the codebase to want to share their GIT  
repos with others *before* pushing those changes back into SVN.


Right. So, I wouldn't want a few people to decide to implement some  
new function, start sharing code (privately amongst themselves), and  
then dump it into svn. IIUC, GIT makes this pretty easy to do.  
Currently, this sort of activity would happen in an svn sandbox or via  
patches posted to a Jira. In either case the collaboration and work  
should be public. I want to make sure we maintain this.


Until *everyone* is using GIT and we have community policies governing  
its usage, svn and our mailing lists are where we need to be  
collaborating.


--kevan

Re: [VOTE] Release XBean 3.5 - rc2

2009-01-27 Thread Jay D. McHugh

+1

I added the rat plugin to my local pom and checked each module.  There
were some files that were flagged as failures - but they were reasonable
(i.e. generated files, etc).  Built fine w/ tests.

Jay

Kevan Miller wrote:
> Here's my +1.
> 
> I scanned code using RAT, reviewed artifacts, and ran a build.
> 
> --kevan
> 
> On Jan 26, 2009, at 3:18 PM, Joe Bohn wrote:
> 
>> I uploaded a second distribution of XBean 3.5 which should include the
>> NOTICE/LICENSE files in all the appropriate places (I hope).  The same
>> changes are present in this candidate that were present in the last one:
>>   * SocketAddress factory example for Alex [1]
>>   * XBEAN-111 Only register Converters with the VM when requested [2]
>>   * Make dependencies optional [3]
>>   * XBEAN-114 generify xbean-naming [4]
>>   * XBEAN-115 Fix rebind of entry added using deepBind [5]
>>   * XBEAN-115 similar fix to for WritableContext for consistency [6]
>>   * try to follow apache policy and not deploy timestamped snapshots [7]
>>   * Fix classloader name when throwing a CNFE [8]
>>   * Let the tests pass on non-MacOS OSes [9]
>>   * XBEAN-120 Search for semi-annotated classes in inheritance tree
>> (as if @Inherited's applied) [10]
>>   * XBEAN-120 Search for semi-annotated classes in inheritance tree
>> (as if @Inherited's applied) [11]
>>   * update copyright years to include 2009 [12]
>>   * add a siteId property to assist in release [13]
>>
>> Please help validate this release.  I'm a little concerned about
>> xbean-spring as I noticed some errors fly by during the release
>> process but everything eventually passed successfully.  I'll start
>> validating this in a Geronimo server image but at the moment it will
>> only utilize xbean-naming 3.5.
>>
>> The staging repository is available at
>>http://people.apache.org/~jbohn/staging-repo/xbean/
>> and the tag is available at
>>http://svn.apache.org/repos/asf/geronimo/xbean/tags/xbean-3.5/
>>
>> I've run the rat tool to validate license headers.
>>
>> Please review and vote:
>>   [ ] +1 Release XBean 3.5
>>   [ ] -1 Do not, because ...
>>
>> The vote will be open for 72 hours or longer as necessary to validate
>> the images and get sufficient participation in the vote.
>>
>> [1] http://svn.apache.org/viewvc?view=rev&revision=689356
>> [2] http://svn.apache.org/viewvc?view=rev&revision=703580
>> [3] http://svn.apache.org/viewvc?view=rev&revision=705314
>> [4] http://svn.apache.org/viewvc?view=rev&revision=707161
>> [5] http://svn.apache.org/viewvc?view=rev&revision=707227
>> [6] http://svn.apache.org/viewvc?view=rev&revision=707230
>> [7] http://svn.apache.org/viewvc?view=rev&revision=707719
>> [8] http://svn.apache.org/viewvc?view=rev&revision=725706
>> [9] http://svn.apache.org/viewvc?view=rev&revision=729545
>> [10] http://svn.apache.org/viewvc?view=rev&revision=729546
>> [11] http://svn.apache.org/viewvc?view=rev&revision=731945
>> [12] http://svn.apache.org/viewvc?view=rev&revision=737042
>> [13] http://svn.apache.org/viewvc?view=rev&revision=737184
>>
>>
>> Thanks,
>> Joe
> 
>

[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kan Ogawa updated GERONIMO-4485:


Attachment: sysdb-portlets.patch

Attached the sysdb-portlets patch.

> Port the GERONIMO-4474 patch for V2.1
> -
>
> Key: GERONIMO-4485
> URL: https://issues.apache.org/jira/browse/GERONIMO-4485
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>Reporter: Kan Ogawa
>Assignee: Kan Ogawa
>Priority: Minor
> Fix For: 2.1.4
>
> Attachments: console-base-portlets.patch, 
> console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, 
> mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, 
> plancreator-console-tomcat.patch, plancreator-portlets.patch, 
> plugin-portlets.patch, sysdb-portlets.patch
>
>
> Target release should be 2.2, if you can attach the patches by Jan. 7th.
> If you would like to see this in 2.1.4, then please attach additional patches 
> created from that branch and we'll try to get them in after we wrap up the 
> 2.2 release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[BUILD] trunk: Failed for Revision: 738327

2009-01-27 Thread gawor

Geronimo Revision: 738327 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090127/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090127/unit-test-reports
 
[INFO] 
[INFO] Building Geronimo Plugins, CXF :: CXF
[INFO]task-segment: [install]
[INFO] 
[WARNING] POM for 'xpp3:xpp3_min:pom:1.1.4c:provided' is invalid. It will be 
ignored for artifact resolution. Reason: Parse error reading POM. Reason: 
expected START_TAG or END_TAG not TEXT (position: TEXT seen ...e with exception 
of classes directly in package org.xmlpull.v1 )

[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kan Ogawa updated GERONIMO-4485:


Attachment: (was: plancreator-portlets.patch)

> Port the GERONIMO-4474 patch for V2.1
> -
>
> Key: GERONIMO-4485
> URL: https://issues.apache.org/jira/browse/GERONIMO-4485
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>Reporter: Kan Ogawa
>Assignee: Kan Ogawa
>Priority: Minor
> Fix For: 2.1.4
>
> Attachments: console-base-portlets.patch, 
> console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, 
> mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, 
> plancreator-console-tomcat.patch, plancreator-portlets.patch, 
> plugin-portlets.patch, sysdb-portlets.patch
>
>
> Target release should be 2.2, if you can attach the patches by Jan. 7th.
> If you would like to see this in 2.1.4, then please attach additional patches 
> created from that branch and we'll try to get them in after we wrap up the 
> 2.2 release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kan Ogawa updated GERONIMO-4485:


Attachment: plancreator-portlets.patch

> Port the GERONIMO-4474 patch for V2.1
> -
>
> Key: GERONIMO-4485
> URL: https://issues.apache.org/jira/browse/GERONIMO-4485
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>Reporter: Kan Ogawa
>Assignee: Kan Ogawa
>Priority: Minor
> Fix For: 2.1.4
>
> Attachments: console-base-portlets.patch, 
> console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, 
> mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, 
> plancreator-console-tomcat.patch, plancreator-portlets.patch, 
> plugin-portlets.patch, sysdb-portlets.patch
>
>
> Target release should be 2.2, if you can attach the patches by Jan. 7th.
> If you would like to see this in 2.1.4, then please attach additional patches 
> created from that branch and we'll try to get them in after we wrap up the 
> 2.2 release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kan Ogawa updated GERONIMO-4485:


Attachment: plugin-portlets.patch

> Port the GERONIMO-4474 patch for V2.1
> -
>
> Key: GERONIMO-4485
> URL: https://issues.apache.org/jira/browse/GERONIMO-4485
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>Reporter: Kan Ogawa
>Assignee: Kan Ogawa
>Priority: Minor
> Fix For: 2.1.4
>
> Attachments: console-base-portlets.patch, 
> console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, 
> mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, 
> plancreator-console-tomcat.patch, plancreator-portlets.patch, 
> plugin-portlets.patch, sysdb-portlets.patch
>
>
> Target release should be 2.2, if you can attach the patches by Jan. 7th.
> If you would like to see this in 2.1.4, then please attach additional patches 
> created from that branch and we'll try to get them in after we wrap up the 
> 2.2 release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kan Ogawa updated GERONIMO-4485:


Attachment: (was: plugin-portlets.patch)

> Port the GERONIMO-4474 patch for V2.1
> -
>
> Key: GERONIMO-4485
> URL: https://issues.apache.org/jira/browse/GERONIMO-4485
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>Reporter: Kan Ogawa
>Assignee: Kan Ogawa
>Priority: Minor
> Fix For: 2.1.4
>
> Attachments: console-base-portlets.patch, 
> console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, 
> mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, 
> plancreator-console-tomcat.patch, plancreator-portlets.patch, 
> plugin-portlets.patch, sysdb-portlets.patch
>
>
> Target release should be 2.2, if you can attach the patches by Jan. 7th.
> If you would like to see this in 2.1.4, then please attach additional patches 
> created from that branch and we'll try to get them in after we wrap up the 
> 2.2 release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kan Ogawa updated GERONIMO-4485:


Attachment: plancreator-portlets.patch

> Port the GERONIMO-4474 patch for V2.1
> -
>
> Key: GERONIMO-4485
> URL: https://issues.apache.org/jira/browse/GERONIMO-4485
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>Reporter: Kan Ogawa
>Assignee: Kan Ogawa
>Priority: Minor
> Fix For: 2.1.4
>
> Attachments: console-base-portlets.patch, 
> console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, 
> mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, 
> plancreator-console-tomcat.patch, plancreator-portlets.patch, 
> plancreator-portlets.patch, plugin-portlets.patch, sysdb-portlets.patch
>
>
> Target release should be 2.2, if you can attach the patches by Jan. 7th.
> If you would like to see this in 2.1.4, then please attach additional patches 
> created from that branch and we'll try to get them in after we wrap up the 
> 2.2 release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kan Ogawa updated GERONIMO-4485:


Attachment: (was: plancreator-portlets.patch)

> Port the GERONIMO-4474 patch for V2.1
> -
>
> Key: GERONIMO-4485
> URL: https://issues.apache.org/jira/browse/GERONIMO-4485
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>Reporter: Kan Ogawa
>Assignee: Kan Ogawa
>Priority: Minor
> Fix For: 2.1.4
>
> Attachments: console-base-portlets.patch, 
> console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, 
> mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, 
> plancreator-console-tomcat.patch, plancreator-portlets.patch, 
> plugin-portlets.patch, sysdb-portlets.patch
>
>
> Target release should be 2.2, if you can attach the patches by Jan. 7th.
> If you would like to see this in 2.1.4, then please attach additional patches 
> created from that branch and we'll try to get them in after we wrap up the 
> 2.2 release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1


 [ 
https://issues.apache.org/jira/browse/GERONIMO-4485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kan Ogawa updated GERONIMO-4485:


Attachment: plancreator-portlets.patch

> Port the GERONIMO-4474 patch for V2.1
> -
>
> Key: GERONIMO-4485
> URL: https://issues.apache.org/jira/browse/GERONIMO-4485
> Project: Geronimo
>  Issue Type: Improvement
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.2
>Reporter: Kan Ogawa
>Assignee: Kan Ogawa
>Priority: Minor
> Fix For: 2.1.4
>
> Attachments: console-base-portlets.patch, 
> console-portal-driver.patch, debugviews-portlets.patch, mconsole-jetty.patch, 
> mconsole-tomcat.patch, mconsole-war.patch, plancreator-console-jetty.patch, 
> plancreator-console-tomcat.patch, plancreator-portlets.patch, 
> plancreator-portlets.patch, plugin-portlets.patch, sysdb-portlets.patch
>
>
> Target release should be 2.2, if you can attach the patches by Jan. 7th.
> If you would like to see this in 2.1.4, then please attach additional patches 
> created from that branch and we'll try to get them in after we wrap up the 
> 2.2 release.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

[jira] Updated: (GERONIMO-4485) Port the GERONIMO-4474 patch for V2.1