[DISCUSS] GEP 2.1 support for v1.1

[Tim McConnell]

Hi, The JAXB refactoring of the GEP 2.1.x code is almost complete for the 2.0.x 
and 2.1.x versions of the Geronimo servers. Most major functions are now working 
and we are much better positioned to handle future schema changes in a more 
timely manner. Traditionally, the GEP has supported 3 to 4 versions of the 
Geronimo server (primarily to provide a migration/upgrade path), and we had 
originally planned on supporting v1.1, v2.0.x, v2.1.x. However, since we are 
almost 2 months behind the release of the v2.1 Geronimo server I would like to 
discuss some possible alternatives for supporting the v1.1 Geronimo server in 
this release of the GEP:


#1. Proceed with the JAXB refactoring work for the v1.1 code (obviously the most 
expensive in terms of time and testing required)


#2. Leave the v1.1 support in the current EMF implementation (i.e., the JAXB and 
EMF implementations would co-exist)


#3. Remove support altogether for v1.1 in this release of the GEP -- support 
only the v2.0 and v2.1 Geronimo servers (the least expensive in terms of time 
and testing required)


I'm now of the opinion that we should pursue alternative #3 and remove v1.1 
support entirely. My primary rationale is that the the old 2.0 release of the 
GEP can still be used to provide v1.1 server support, and still provides a 
migration path from v1.1 to v2.0. It's true that we would lose the v1.1 to v2.1 
migration path, but this is mitigated somewhat since the support in the GEP for 
the v2.0 and v2.1 versions of the server is almost identical. Equally important 
is that we could then focus entirely on fixing the few remaining JIRAs and 
augmenting our JUnit testcases, and release the GEP 2.1 quicker (i.e., in the 
next week or 10 days). Thoughts ??


--
Thanks,
Tim McConnell

[jira] Created: (GERONIMODEVTOOLS-321) Installation/upgrade facility using obsolete artifacts

[Tim McConnell (JIRA)]

Installation/upgrade facility using obsolete artifacts
--

 Key: GERONIMODEVTOOLS-321
 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-321
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 1.2.1
Reporter: Tim McConnell
Assignee: Tim McConnell


> Since a few month we are testing the upcoming Eclipe version 3.3 with 
> the latest Version of the Geronimo Plugin. For our needs (we still 
> develop for Geronimo 1.1) it works great and without any issues. The 
> only thing is, that the Eclipse upgrade/installation functionallity is 
> broken, because of broken dependencies:
> 
> The current configuration contains errors and this operation can have 
> unpredictable results.
>  Geronimo v1.1.x Server Adapter (2.1.0) requires feature 
> "org.eclipse.jst (2.0.0)", or compatible.
>  Geronimo v2.0 Server Adapter (2.1.0) requires feature "org.eclipse.jst 
> (2.0.0)", or compatible.
>  Geronimo v2.1 Server Adapter (2.1.0) requires feature "org.eclipse.jst 
> (2.0.0)", or compatible.
>  Geronimo Core Feature (2.1.0) requires feature "org.eclipse.jst 
> (2.0.0)", or compatible.
> 
> It would be nice if this issue could be solved for the new version!
> 
> Best regards,
> Johannes Weberhofer

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

[jira] Resolved: (GERONIMODEVTOOLS-308) Plugin: org.apache.geronimo.st.v20.ui

[Tim McConnell (JIRA)]

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

Tim McConnell resolved GERONIMODEVTOOLS-308.


   Resolution: Fixed
Fix Version/s: 2.1.0
 Assignee: Tim McConnell  (was: Shiva Kumar H R)

Refactoring no longer needed for this plugin as all the source code has been 
removed. The v21 source code will be used instead (i.e., no longer any 
duplicate code between the v20 and v21 versions of this plugin). 

> Plugin: org.apache.geronimo.st.v20.ui
> -
>
> Key: GERONIMODEVTOOLS-308
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-308
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.1.0
>
>


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

(activemq) Fwd: Legal goo problems

[David Jencks]

Begin forwarded message:


From: David Jencks <[EMAIL PROTECTED]>
Date: March 28, 2008 4:04:53 PM PDT
To: [EMAIL PROTECTED]
Subject: Legal goo problems

In my hopefully finite-length effort to get a 4.1.2 release out  
I've been looking a little bit at the LICENSE and NOTICE files in  
the 4.1 branch and trunk and think many of them have big problems.


Current thinking expressed on the legal-discuss is that:

A source code unit expected to be checked out from svn needs  
LICENSE and NOTICE files in svn at the root of the checkout.  These  
files should apply exactly to the source code checked out, and not  
include any language only appropriate for dependencies that may be  
needed to build or run the software.  These are the only LICENSE  
and NOTICE files that need to be actually present in svn.


Each artifact distributed needs a LICENSE and NOTICE file.  These  
may be hardcoded in svn or generated.  These files should  
accurately describe the license(s) and required notices of what is  
actually in the distribution unit (e.g. jar, war, tar.bz2) and not  
describe anything not included that might be necessary to use the  
software.


Artifacts can also have descriptions of dependencies needed to use  
the software but these descriptions should not be in the LICENSE or  
NOTICE files.


so

Looking around there are 2 problems:
- some of the LICENSE and possibly NOTICE files look like they have  
generally large amounts of text appropriate for dependencies, not  
what they actually apply to
- some LICENSE files are decidedly incomplete.  For instance the  
activemq-web-console includes all the sun jaxb jars but no CDDL  
license.  The trunk root LICENSE.txt file doesn't include the  
licenses for the javascript in the activemq-web-console.


Possible solutions

The root LICENSE and NOTICE files have to be fixed by hand AFAIK.   
All the others can be generated using the maven-remote-resources  
plugin.  Thanks to Dan Kulp the latest apache resource bundle  
actually generates stuff compliant with the apparent policy.  What  
needs to happen is that modules that have extra LICENSE or NOTICE  
requirements need the extra stuff to be put into


src/main/appended-resources/META-INF/LICENSE and src/main/appended- 
resources/META-INF/NOTICE


I can help with setting this up but I don't know what code might  
need such extra legal goo.  If I'm going to be able to help I'd  
need accurate information on this.


There's also a geronimo maven plugin that can verify that legal  
files are present in all the artifacts you build (jar, war,  
javadoc, source, etc).  I think it's a big help in release auditing  
to include this plugin in the regular build to  catch problems early.


thanks
david jencks

[BUILD] trunk: Failed for Revision: 642337

[gawor]

Geronimo Revision: 642337 built with tests included
 
See the full build-1500.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/build-1500.log
 
Download the binaries from 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 31 minutes 33 seconds
[INFO] Finished at: Fri Mar 28 15:47:26 EDT 2008
[INFO] Final Memory: 313M/1012M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/logs-1500-tomcat/test.log
 
 
Assembly: jetty
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/logs-1500-jetty/test.log
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.755 
sec <<< FAILURE!
 
Samples: trunk
=
Log: 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/samples-1500.log
 
Build status: OK
 

[jira] Resolved: (GERONIMODEVTOOLS-317) CoreException when creating Enterprise Application Project

[Shiva Kumar H R (JIRA)]

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

Shiva Kumar H R resolved GERONIMODEVTOOLS-317.
--

   Resolution: Fixed
Fix Version/s: 2.1.0
 Assignee: Tim McConnell  (was: Shiva Kumar H R)

Completed: At revision: 642290  

> CoreException when creating Enterprise Application Project
> --
>
> Key: GERONIMODEVTOOLS-317
> URL: 
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-317
> Project: Geronimo-Devtools
>  Issue Type: Sub-task
>Reporter: Tim McConnell
>Assignee: Tim McConnell
> Fix For: 2.1.0
>
>
> When creating an Enterprise Applicaiton Project, and not setting the 
> "Generate Deployment Descriptor" checkbox, a CoreException will result. The 
> trace and exception stacktrace is as below:
> org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.55.531 ->- 
> ServerResourceChangeListener responding to resource change: 16 ->-
> org.eclipse.wst.server.core FINEST26/03/08 19:12.55.531 Loading project 
> preferences: P/test3
> org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.55.531 Not a server 
> project: test3
> org.eclipse.wst.server.core FINEST26/03/08 19:12.55.531 > 
> publishHandleProjectChange P/test3
> org.eclipse.wst.server.core FINEST26/03/08 19:12.55.531 - 
> publishHandleProjectChange
> org.eclipse.wst.server.core FINEST26/03/08 19:12.55.531 < 
> publishHandleProjectChange
> org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.55.531 -<- Done 
> ServerResourceChangeListener responding to resource change -<-
> org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.56.546 ->- 
> ServerResourceChangeListener responding to resource change: 16 ->-
> org.eclipse.wst.server.core FINEST26/03/08 19:12.56.546 Loading project 
> preferences: P/test3
> org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.56.546 Not a server 
> project: test3
> org.eclipse.wst.server.core FINEST26/03/08 19:12.56.546 > 
> publishHandleProjectChange P/test3
> org.eclipse.wst.server.core RESOURCES 26/03/08 19:12.56.546 -<- Done 
> ServerResourceChangeListener responding to resource change -<-
> org.apache.geronimo.st.ui:  ENTRY: 
> SharedDeploymentPlanEditor.loadDeploymentPlan( 
> parm1=[L/test3/EarContent/META-INF/geronimo-application.xml] )
> org.apache.geronimo.st.ui:  ENTRY: SharedDeploymentPlanEditor.getLoader()
> org.apache.geronimo.st.ui:  EXIT: SharedDeploymentPlanEditor.getLoader( 
> [EMAIL PROTECTED] )
> org.apache.geronimo.st.core:  ENTRY: GeronimoV21Utils.getDeploymentPlan( 
> parm1=[L/test3/EarContent/META-INF/geronimo-application.xml] )
> org.apache.geronimo.st.core:  ENTRY: 
> GeronimoV21Utils.getApplicationDeploymentPlan( 
> parm1=[L/test3/EarContent/META-INF/geronimo-application.xml] )
> org.apache.geronimo.st.ui:  EXIT: 
> SharedDeploymentPlanEditor.loadDeploymentPlan( [EMAIL PROTECTED] )
> org.apache.geronimo.st.ui:  ENTRY: SharedDeploymentPlanEditor.doAddPages()
> org.apache.geronimo.st.ui:  ENTRY: SharedDeploymentPlanEditor.getLoader()
> org.apache.geronimo.st.ui:  EXIT: SharedDeploymentPlanEditor.getLoader( 
> [EMAIL PROTECTED] )
> org.apache.geronimo.st.ui:  EXIT: SharedDeploymentPlanEditor.doAddPages()
> org.apache.geronimo.st.v21.core:  Entry/Exit: 
> DeploymentPlanInstallConfig.create()
> org.apache.geronimo.st.v21.core:  Entry/Exit: 
> DeploymentPlanInstallConfig.create()
> org.apache.geronimo.st.v21.ui:  Constructor Entry: FacetInstallPage()
> org.apache.geronimo.st.v21.ui:  Constructor Exit: FacetInstallPage()
> org.apache.geronimo.st.v21.ui:  Entry: FacetInstallPage.setConfig( [EMAIL 
> PROTECTED] )
> org.apache.geronimo.st.v21.ui:  Exit: FacetInstallPage.setConfig()
> org.apache.geronimo.st.v21.ui:  Entry: FacetInstallPage.createControl( 
> parm1=[Composite {}] )
> org.apache.geronimo.st.v21.ui:  Exit: FacetInstallPage.createControl()
> org.apache.geronimo.st.v21.ui:  Entry: 
> FacetInstallPage.transferStateToConfig()
> org.apache.geronimo.st.v21.ui:  Exit: FacetInstallPage.transferStateToConfig()
> org.apache.geronimo.st.v21.core:  Entry: 
> GeronimoV21FacetInstallDelegate.createDeploymentPlanCreationOp( 
> parm1=[P/test34], [EMAIL PROTECTED] )
> org.apache.geronimo.st.v21.core:  Exit : 
> GeronimoV21FacetInstallDelegate.createDeploymentPlanCreationOp()
> org.apache.geronimo.st.v21.core:  Constructor Entry/Exit: 
> V21DeploymentPlanCreationOperation( parm1=[IDataModel, [EMAIL PROTECTED], 
> [EMAIL PROTECTED] )
> org.apache.geronimo.st.v21.core:  Entry: 
> V21DeploymentPlanCreationOperation.createGeronimoApplicationDeploymentPlan( 
> parm1=[L/test34/EarContent/META-INF/geronimo-application.xml] )
> org.apache.geronimo.st.v21.core:  Entry: 
> V21DeploymentPlanCreationOperation.getConfigEnvironment()
> org.apache.geronimo.st.v21.core:  Entry: 
> V21DeploymentPlanCreationOperatio

[BUILD] trunk: Failed for Revision: 642216

[gawor]

Geronimo Revision: 642216 built with tests included
 
See the full build-0900.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/build-0900.log
 
Download the binaries from 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 32 minutes 26 seconds
[INFO] Finished at: Fri Mar 28 09:54:27 EDT 2008
[INFO] Final Memory: 314M/1012M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/logs-0900-tomcat/test.log
 
 
Assembly: jetty
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/logs-0900-jetty/test.log
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 71.139 
sec <<< FAILURE!
 
Samples: trunk
=
Log: 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/samples-0900.log
 
Build status: OK
 

[jira] Closed: (GERONIMO-3781) Plugin Installer, CRSF issue when attempting to install a new plugin

[Joseph Leong (JIRA)]

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

Joseph Leong closed GERONIMO-3781.
--

Resolution: Fixed

Original CRSF issue resolved.  The side effect spawn the warning message in 
Jetty will be fixed and updated at GERONIMO-3942 

> Plugin Installer, CRSF issue when attempting to install a new plugin
> 
>
> Key: GERONIMO-3781
> URL: https://issues.apache.org/jira/browse/GERONIMO-3781
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: console
>Affects Versions: 2.1, 2.1.1
> Environment: Ubuntu 7.10, Firefox 2.0.0.6
>Reporter: Joseph Leong
>Assignee: Joseph Leong
> Fix For: 2.1.1
>
>
> Plugin installer will not allow for you to install anymore plugins on a 
> second attempt given that it threw an exception the first time.  This is 
> attributed to the exception thrown that doesn't properly exit and close off 
> current sessions.  So in the second attempt there is a cookie/session 
> mismatch.

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

[jira] Created: (GERONIMO-3942) IllegalStateException warning message for Jetty plugin installer

[Joseph Leong (JIRA)]

IllegalStateException warning message for Jetty plugin installer


 Key: GERONIMO-3942
 URL: https://issues.apache.org/jira/browse/GERONIMO-3942
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: console
Affects Versions: 2.1, 2.1.1, 2.2
 Environment: Ubuntu 7.10, Firefox
Reporter: Joseph Leong
Assignee: Joseph Leong
Priority: Minor
 Fix For: 2.2


When installing plugins via the admin console (on Jetty) , at times an 
IllegalStateException Warning Message Occurs.  Otherwise, everything appears to 
look and work fine functionality wise.

StackTrace Example:

java.lang.IllegalStateException: Committed
at org.mortbay.jetty.Response.resetBuffer(Response.java:995)
at org.mortbay.jetty.Response.sendRedirect(Response.java:403)
at 
org.mortbay.jetty.security.FormAuthenticator.authenticate(FormAuthenticator.java:257)
at 
org.apache.geronimo.jetty6.handler.JettySecurityHandler.checkSecurityConstraints(JettySecurityHandler.java:216)
at org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:191)
at 
org.apache.geronimo.jetty6.handler.JettySecurityHandler.handle(JettySecurityHandler.java:114)
at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:726)
at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405)
at 
org.apache.geronimo.jetty6.handler.TwistyWebAppContext.access$101(TwistyWebAppContext.java:40)
at 
org.apache.geronimo.jetty6.handler.TwistyWebAppContext$TwistyHandler.handle(TwistyWebAppContext.java:65)
at 
org.apache.geronimo.jetty6.handler.ThreadClassloaderHandler.handle(ThreadClassloaderHandler.java:46)
at 
org.apache.geronimo.jetty6.handler.InstanceContextHandler.handle(InstanceContextHandler.java:58)
at 
org.apache.geronimo.jetty6.handler.UserTransactionHandler.handle(UserTransactionHandler.java:48)
at 
org.apache.geronimo.jetty6.handler.ComponentContextHandler.handle(ComponentContextHandler.java:47)
at 
org.apache.geronimo.jetty6.handler.TwistyWebAppContext.handle(TwistyWebAppContext.java:59)
at 
org.mortbay.jetty.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:206)
at 
org.mortbay.jetty.handler.HandlerCollection.handle(HandlerCollection.java:114)
at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:324)
at org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:505)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:374)

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

[jira] Commented: (GERONIMO-3819) Update JMS Resources Portlet

[Vamsavardhana Reddy (JIRA)]

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

Vamsavardhana Reddy commented on GERONIMO-3819:
---

Anish,

The patch seems to have some formatting changes (which are not relevant to the 
issue).  Can you submit another one without these formatting changes?

> Update JMS Resources Portlet
> 
>
> Key: GERONIMO-3819
> URL: https://issues.apache.org/jira/browse/GERONIMO-3819
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>  Components: console
>Reporter: Anish Pathadan
>Assignee: Anish Pathadan
> Fix For: 2.1.1, 2.2
>
> Attachments: Browse Messages.jpg, JMS Resource Portlet_Main.jpg, 
> JMSResource_portlet_1.0.patch, JMSResource_portlet_1.1.patch, Send Message.jpg
>
>
> Update the JMS Resources portlet to include the following information from 
> the JMS Provider
> 1.Count of messages send to each queue/topic ,pending messages
> 2.Option to send messages to messages to particular queues/topics
> 3.Purge messages from queues/topics
> 4.Browse and send messages to queues/topics

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

Re: [VOTE] Release javamail spec jar (1.3) + javamail provider jars (1.4)

[Donald Woods]

+1


-Donald

Joe Bohn wrote:


New releases of the javamail spec and javamail provider jars are 
necessary for a Geronimo 2.1.1 release.  We're voting on these 
collectively.


1)  Release 1.3 of the javamail 1.4 spec API.  The artifact in question 
is geronimo-javamail_1.4_spec-1.3.  This jar includes two bug fixes, 
GERONIMO-3842 and GERONIMO-3853.  The release archive is located here:


Staging repo:
http://people.apache.org/~jbohn/staging-repo/specs/

Staging site:
http://people.apache.org/~jbohn/staging-site/specs/

2)  Release 1.4 of the javamail 1.4 mail package.  This package includes 
bug fixes for, and upgrade to genesis 1.4 (for the release process). 
Changes include picking up the new javamail spec, additional changes for 
GERONIMO-3842, and updating to Genesis 1.4 to facilitate the release 
process for this and future releases.


This package has a top level pom and two child artifacts:

top level pom:   geronimo-javamail_1.4-1.4
javamail provider:   geronimo_javamail_1.4_provider-1.4.jar
javamail mail:   geronimo_javamail_1.4_mail-1.4.jar

The geronimo_javamail_1.4_mail-1.4 artifact is the uber-jar containing 
the merged spec and provider class files.


Staging repo:
http://people.apache.org/~jbohn/staging-repo/javamail/


These artifacts created using the maven-release-plugin

The tag locations are:
https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.3 

https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.4/ 



I have yet to test these changes in the Geronimo server with the tck 
tests but will do that now, concurrent to the vote.  I'll hold my vote 
until I confirm there are no tck implications.



Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1


Joe



smime.p7s
Description: S/MIME Cryptographic Signature

Re: [VOTE] Release javamail spec jar (1.3) + javamail provider jars (1.4)

[Rick McGuire]

+1

Joe Bohn wrote:


New releases of the javamail spec and javamail provider jars are 
necessary for a Geronimo 2.1.1 release.  We're voting on these 
collectively.


1)  Release 1.3 of the javamail 1.4 spec API.  The artifact in 
question is geronimo-javamail_1.4_spec-1.3.  This jar includes two bug 
fixes, GERONIMO-3842 and GERONIMO-3853.  The release archive is 
located here:


Staging repo:
http://people.apache.org/~jbohn/staging-repo/specs/

Staging site:
http://people.apache.org/~jbohn/staging-site/specs/

2)  Release 1.4 of the javamail 1.4 mail package.  This package 
includes bug fixes for, and upgrade to genesis 1.4 (for the release 
process). Changes include picking up the new javamail spec, additional 
changes for GERONIMO-3842, and updating to Genesis 1.4 to facilitate 
the release process for this and future releases.


This package has a top level pom and two child artifacts:

top level pom:   geronimo-javamail_1.4-1.4
javamail provider:   geronimo_javamail_1.4_provider-1.4.jar
javamail mail:   geronimo_javamail_1.4_mail-1.4.jar

The geronimo_javamail_1.4_mail-1.4 artifact is the uber-jar containing 
the merged spec and provider class files.


Staging repo:
http://people.apache.org/~jbohn/staging-repo/javamail/


These artifacts created using the maven-release-plugin

The tag locations are:
https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.3 

https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.4/ 



I have yet to test these changes in the Geronimo server with the tck 
tests but will do that now, concurrent to the vote.  I'll hold my vote 
until I confirm there are no tck implications.



Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1


Joe

[BUILD] trunk: Failed for Revision: 642105

[gawor]

Geronimo Revision: 642105 built with tests included
 
See the full build-0300.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/build-0300.log
 
Download the binaries from 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 36 minutes 25 seconds
[INFO] Finished at: Fri Mar 28 03:45:15 EDT 2008
[INFO] Final Memory: 315M/667M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
See detailed results at 
http://geronimo.apache.org/maven/server/testsuite/ResultsSummary.html
 
Assembly: tomcat
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/logs-0300-tomcat/test.log
 
 
Assembly: jetty
=
See the full test.log file at 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/logs-0300-jetty/test.log
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 13, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 73.19 
sec <<< FAILURE!
 
Samples: trunk
=
Log: 
http://geronimo.apache.org/maven/server/binaries/trunk/20080328/samples-0300.log
 
Build status: OK
 

Re: [VOTE] Release javamail spec jar (1.3) + javamail provider jars (1.4)

[Vamsavardhana Reddy]

+1

++Vamsi

On Thu, Mar 27, 2008 at 9:41 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:

>
> New releases of the javamail spec and javamail provider jars are
> necessary for a Geronimo 2.1.1 release.  We're voting on these
> collectively.
>
> 1)  Release 1.3 of the javamail 1.4 spec API.  The artifact in question
> is geronimo-javamail_1.4_spec-1.3.  This jar includes two bug fixes,
> GERONIMO-3842 and GERONIMO-3853.  The release archive is located here:
>
> Staging repo:
> http://people.apache.org/~jbohn/staging-repo/specs/
>
> Staging site:
> http://people.apache.org/~jbohn/staging-site/specs/
>
> 2)  Release 1.4 of the javamail 1.4 mail package.  This package includes
> bug fixes for, and upgrade to genesis 1.4 (for the release process).
> Changes include picking up the new javamail spec, additional changes for
> GERONIMO-3842, and updating to Genesis 1.4 to facilitate the release
> process for this and future releases.
>
> This package has a top level pom and two child artifacts:
>
> top level pom:   geronimo-javamail_1.4-1.4
> javamail provider:   geronimo_javamail_1.4_provider-1.4.jar
> javamail mail:   geronimo_javamail_1.4_mail-1.4.jar
>
> The geronimo_javamail_1.4_mail-1.4 artifact is the uber-jar containing
> the merged spec and provider class files.
>
> Staging repo:
> http://people.apache.org/~jbohn/staging-repo/javamail/
>
>
> These artifacts created using the maven-release-plugin
>
> The tag locations are:
>
> https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.3
>
> https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.4/
>
> I have yet to test these changes in the Geronimo server with the tck
> tests but will do that now, concurrent to the vote.  I'll hold my vote
> until I confirm there are no tck implications.
>
>
> Vote open for 72 hours.
>
> [ ] +1
> [ ] +0
> [ ] -1
>
>
> Joe
>

Re: [VOTE] Release javamail spec jar (1.3) + javamail provider jars (1.4)

[Jacek Laskowski]

+1

Jacek

On Thu, Mar 27, 2008 at 5:11 PM, Joe Bohn <[EMAIL PROTECTED]> wrote:
>
>  New releases of the javamail spec and javamail provider jars are
>  necessary for a Geronimo 2.1.1 release.  We're voting on these collectively.
>
>  1)  Release 1.3 of the javamail 1.4 spec API.  The artifact in question
>  is geronimo-javamail_1.4_spec-1.3.  This jar includes two bug fixes,
>  GERONIMO-3842 and GERONIMO-3853.  The release archive is located here:
>
>  Staging repo:
>  http://people.apache.org/~jbohn/staging-repo/specs/
>
>  Staging site:
>  http://people.apache.org/~jbohn/staging-site/specs/
>
>  2)  Release 1.4 of the javamail 1.4 mail package.  This package includes
>  bug fixes for, and upgrade to genesis 1.4 (for the release process).
>  Changes include picking up the new javamail spec, additional changes for
>  GERONIMO-3842, and updating to Genesis 1.4 to facilitate the release
>  process for this and future releases.
>
>  This package has a top level pom and two child artifacts:
>
>  top level pom:   geronimo-javamail_1.4-1.4
>  javamail provider:   geronimo_javamail_1.4_provider-1.4.jar
>  javamail mail:   geronimo_javamail_1.4_mail-1.4.jar
>
>  The geronimo_javamail_1.4_mail-1.4 artifact is the uber-jar containing
>  the merged spec and provider class files.
>
>  Staging repo:
>  http://people.apache.org/~jbohn/staging-repo/javamail/
>
>
>  These artifacts created using the maven-release-plugin
>
>  The tag locations are:
>  
> https://svn.apache.org/repos/asf/geronimo/specs/tags/geronimo-javamail_1.4_spec-1.3
>  
> https://svn.apache.org/repos/asf/geronimo/javamail/tags/geronimo-javamail_1.4-1.4/
>
>  I have yet to test these changes in the Geronimo server with the tck
>  tests but will do that now, concurrent to the vote.  I'll hold my vote
>  until I confirm there are no tck implications.
>
>
>  Vote open for 72 hours.
>
>  [ ] +1
>  [ ] +0
>  [ ] -1
>
>
>  Joe
>



-- 
Jacek Laskowski
http://www.JacekLaskowski.pl

[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references

[Erik B. Craig (JIRA)]

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

Erik B. Craig commented on GERONIMO-3910:
-

Revision 642109 - Cleaned up samples/branches/1.0/migration-webservices

> Rename classes, remove IBM references
> -
>
> Key: GERONIMO-3910
> URL: https://issues.apache.org/jira/browse/GERONIMO-3910
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: sample apps
>Affects Versions: 1.x
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Critical
>
> In the migration sample apps from the 1.0 branch, there are classes named 
> com.ibm.x.
> These need to be renamed to o.a.g

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

[jira] Commented: (GERONIMO-3910) Rename classes, remove IBM references

[Erik B. Craig (JIRA)]

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

Erik B. Craig commented on GERONIMO-3910:
-

Revision 642103 - Cleaned up samples/branches/1.0/migration-jca
Revision 642104 - Cleaned up samples/branches/1.0/migration-jdbc
Revision 642105 - Cleaned up samples/branches/1.0/migration-security

> Rename classes, remove IBM references
> -
>
> Key: GERONIMO-3910
> URL: https://issues.apache.org/jira/browse/GERONIMO-3910
> Project: Geronimo
>  Issue Type: Bug
>  Security Level: public(Regular issues) 
>  Components: sample apps
>Affects Versions: 1.x
>Reporter: Erik B. Craig
>Assignee: Erik B. Craig
>Priority: Critical
>
> In the migration sample apps from the 1.0 branch, there are classes named 
> com.ibm.x.
> These need to be renamed to o.a.g

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