[jira] Assigned: (GERONIMO-4216) Examine setters methods in connector builder
[ https://issues.apache.org/jira/browse/GERONIMO-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rex Wang reassigned GERONIMO-4216: -- Assignee: Rex Wang Examine setters methods in connector builder Key: GERONIMO-4216 URL: https://issues.apache.org/jira/browse/GERONIMO-4216 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: connector Affects Versions: 2.2 Reporter: Jarek Gawor Assignee: Rex Wang Currently, the connector builder uses the getter methods to figure out the types for the attributes for the dynamic gbeans created for the various connector classes. The connector builder should use the setter methods instead (for example, in cases where there is a write-only property, i.e. setter method is present but getter is not). This is related to [GERONIMO-4131]. -- 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: 787559
Geronimo Revision: 787559 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090623/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090623/unit-test-reports for artifact: org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.camel:camel-jms:jar:2.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.camel -DartifactId=camel-jms -Dversion=2.0-20090611.201918-17 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.camel -DartifactId=camel-jms -Dversion=2.0-20090611.201918-17 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2-SNAPSHOT 2) org.apache.activemq:activemq-web:jar:5.3-SNAPSHOT 3) org.apache.activemq:activemq-camel:jar:5.3-SNAPSHOT 4) org.apache.camel:camel-jms:jar:2.0-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.camel:camel-jms:jar:2.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.camel -DartifactId=camel-jms -Dversion=2.0-20090611.201918-17 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.camel -DartifactId=camel-jms -Dversion=2.0-20090611.201918-17 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2-SNAPSHOT 2) org.apache.activemq:activemq-web:jar:5.3-SNAPSHOT 3) org.apache.activemq:activemq-camel:jar:5.3-SNAPSHOT 4) org.apache.camel:camel-jms:jar:2.0-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://repository.apache.org/snapshots), codehaus.snapshots (http://snapshots.repository.codehaus.org) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324
Re: genesis-flava - genesis-default-flava
I spent a lot of hours with genesis 1.x looking through all the poms for the setting that was causing behavior I was wondering about to want to eliminate every bit of unnecessary complexity I could. In the event we come up with a flava that doesn't want to inherit from default-flava we can put it as a direct child of the root genesis project. Fair enough :-) I also changed the groupId to o.a.g.genesis from o.a.g.genesis.flava. why? Fewer groupIds == simpler better IMO. I don't see what the additional groupId adds except complexity and chance for confusion. Am I missing something? Its just a tool for organizing similar modules, like packages in java. I tend to organize stuff, which is why I put all flava's into their own groupId. --jason
Suggest to turn off those debug and warning options for maven-compile-plugin
HI, No sure why we need to turn on those debug and warning options for the maven-compile-plugin, it made much outputs in the building process. And, it caused the compile failure on my workstation, maybe it is caused by my local setting. Shall we turn them off, or there are some reasons that we need to keep them ? Thanks ! -- Ivan
Re: Suggest to turn off those debug and warning options for maven-compile-plugin
Agree to turn off debug and warning options from current pom because they also caused build failure in my laptop. configuration optimizetrue/optimize debugtrue/debug showDeprecationtrue/showDeprecation showWarningstrue/showWarnings /configuration This setting is in release genesis pom: genesis\genesis-default-flava\2.0\genesis-default-flava-2.0.pom. So that we have to override them in server pom.xml. On Tue, Jun 23, 2009 at 4:40 PM, Ivan xhh...@gmail.com wrote: HI, No sure why we need to turn on those debug and warning options for the maven-compile-plugin, it made much outputs in the building process. And, it caused the compile failure on my workstation, maybe it is caused by my local setting. Shall we turn them off, or there are some reasons that we need to keep them ? Thanks ! -- Ivan -- Shawn
[jira] Commented: (GERONIMO-4628) Console plan wizards need to save plans
[ https://issues.apache.org/jira/browse/GERONIMO-4628?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723020#action_12723020 ] Rex Wang commented on GERONIMO-4628: Currently, there are only RepositoryConfigurationStore and geronimo-farm's MasterConfigurationStore, different store might have different behavior when deploy packages. I think the save plan action is better to go along with the action that intalling the config.ser. So in the Deployer, after store.install(configurationData) which will generate the config.ser, config.info, I add the store.savePlan(configurationData, planFile). -Rex Console plan wizards need to save plans --- Key: GERONIMO-4628 URL: https://issues.apache.org/jira/browse/GERONIMO-4628 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Reporter: David Jencks Assignee: Rex Wang Fix For: 2.1.5, 2.2 Attachments: GERONIMO-4628-b21.patch Currently we have a lot of console wizards that are great at creating basic plans for datasources, security realms, etc etc. However once you've deployed the plan through the wizard the plan is gone gone gone never to be seen again. The wizards need to do _something_ so the plans are saved on disk somehow. One possibliity is that deployment could always save the plan into the car file, like the car-maven-plugin does. I'm not certain but I think this would fix the admin console wizard problem as well. Also it would be very handy if the wizard inserted a comment mentioning the intended target artifact, such as which tranql adapter to use for a datasource plan. Furthermore you ought to be able to specify all components of the artifact id (groupId, etc) in all the wizards. In fact you should be able to set the default groupId for the whole admin console -- probably your company wants all the groupIds the same. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4706) DB2 XA properties show crash code in database pool porlet
DB2 XA properties show crash code in database pool porlet - Key: GERONIMO-4706 URL: https://issues.apache.org/jira/browse/GERONIMO-4706 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.2 Environment: os:win2003 Reporter: viola.lu Assignee: viola.lu Priority: Minor 1.Go to g console, click Database pools, create a db2 xa datasource, in the first page, there are two newly added properites: Downgrade Hold Cursors and ResultSet Holds, but it display crash code: question mark.Becasue their corresponding values are not included into message file: systemdatabase.properties So update it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4706) DB2 XA properties show crash code in database pool porlet
[ https://issues.apache.org/jira/browse/GERONIMO-4706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] viola.lu updated GERONIMO-4706: --- Attachment: GERONIMO-4706.patch pls check properties instructions whether correct. DB2 XA properties show crash code in database pool porlet - Key: GERONIMO-4706 URL: https://issues.apache.org/jira/browse/GERONIMO-4706 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Environment: os:win2003 Reporter: viola.lu Assignee: viola.lu Priority: Minor Attachments: GERONIMO-4706.patch 1.Go to g console, click Database pools, create a db2 xa datasource, in the first page, there are two newly added properites: Downgrade Hold Cursors and ResultSet Holds, but it display crash code: question mark.Becasue their corresponding values are not included into message file: systemdatabase.properties So update it. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-4696) Directory should be removed when a module's deployment fails.
[ https://issues.apache.org/jira/browse/GERONIMO-4696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723028#action_12723028 ] viola.lu commented on GERONIMO-4696: this problem exits after verification, i will take a look into it. Directory should be removed when a module's deployment fails. - Key: GERONIMO-4696 URL: https://issues.apache.org/jira/browse/GERONIMO-4696 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: deployment Affects Versions: 2.2 Reporter: Rodger Zhang Attachments: general_store.war, geronimo-web.xml I write a war using datasource. Deploy it with a geronimo-web.xml that does not contain the dependence on the datasource. As anticipated , it fails to be deployed. But when I deploy the war again with the right geronimo-web.xml (dependence has been added), there is an error: org.apache.geronimo.kernel.config.ConfigurationAlreadyExistsException: Configuration already exists: There is no module with the very name in config.xml , but a directory with the very name exists in geronimo_home/repository/ . If I remove the directory in repository manually, then I can depoly the war successfully. So, if a module's deployment fails, the directory created in repository should be removed automatically. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (GERONIMO-4685) Build our own tomcat.
[ https://issues.apache.org/jira/browse/GERONIMO-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kevan Miller reassigned GERONIMO-4685: -- Assignee: Kevan Miller (was: David Jencks) Build our own tomcat. - Key: GERONIMO-4685 URL: https://issues.apache.org/jira/browse/GERONIMO-4685 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: buildsystem, Tomcat Affects Versions: 2.2 Reporter: David Jencks Assignee: Kevan Miller Fix For: 2.2 We don't have the patches used to build the tomcat version we distribute, at least I can't interpret diffs of diffs. Build an archetype that sets up a maven multimodule project to build tomcat. Use a bash script to svn copy tomcat source into this structure commit apply patches commit build under our own groupId. Work started in sandbox djencks/tomcat-archetype. Note that tomcat jars distributed by tomcat have circular dependencies. So, combine catalina and coyote jars. Split out util for now. -- 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: 787654
Geronimo Revision: 787654 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090623/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090623/unit-test-reports for artifact: org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Missing: -- 1) org.apache.camel:camel-jms:jar:2.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.camel -DartifactId=camel-jms -Dversion=2.0-20090611.201918-17 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.camel -DartifactId=camel-jms -Dversion=2.0-20090611.201918-17 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2-SNAPSHOT 2) org.apache.activemq:activemq-web:jar:5.3-SNAPSHOT 3) org.apache.activemq:activemq-camel:jar:5.3-SNAPSHOT 4) org.apache.camel:camel-jms:jar:2.0-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:576) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:500) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:479) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:331) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:292) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:301) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: Missing: -- 1) org.apache.camel:camel-jms:jar:2.0-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.camel -DartifactId=camel-jms -Dversion=2.0-20090611.201918-17 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.camel -DartifactId=camel-jms -Dversion=2.0-20090611.201918-17 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2-SNAPSHOT 2) org.apache.activemq:activemq-web:jar:5.3-SNAPSHOT 3) org.apache.activemq:activemq-camel:jar:5.3-SNAPSHOT 4) org.apache.camel:camel-jms:jar:2.0-SNAPSHOT -- 1 required artifact is missing. for artifact: org.apache.geronimo.plugins:activemq-webconsole-jetty:car:2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:324
Build the GBeanInfo with the attribute name caselessly?
Build the GBeanInfo with the attribute name caselessly?
Currently, we build the GBeanInfo attribute according to the java code
convention. However, we user set the attribute throught the plan, he have to
pay attention to the case of the attribute name, such as:
gbean name=SMTPTransport
attribute name=host${SMTPHost}/attribute
attribute name=port${SMTPPort}/attribute
/gbean
and
gbean
name=org.apache.geronimo.configs/tomcat6/2.1.5-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.5-SNAPSHOT/car,j2eeType=GBean,name=uniquename2
load=false
gbeanInfo=org.apache.geronimo.tomcat.connector.Http11ConnectorGBean
attribute name=keepAliveTimeout6/attribute
attribute name=maxThreads40/attribute
attribute name=acceptCount10/attribute
attribute name=connectionTimeout6/attribute
attribute name=connectionLinger-1/attribute
attribute name=address0.0.0.0/attribute
but we it comes to the ra.xml, we always use the first upper case word to
define the properties, such as:
config-property-nameDatabaseName/config-property-name
config-property-typejava.lang.String/config-property-type
and that causes the program logic in the config module builder should deal
with that specificly...programmer might hate that..
So, if either the user or developer will get un-happyness on this
configuration, why not we build the GBeanInfo with a caseless name
indentifid GAttributeInfo?
-Rex
Jun 23
Re: Build the GBeanInfo with the attribute name caselessly?
Looks like a good idea to me.
-Jack
On Tue, Jun 23, 2009 at 9:06 PM, Rex Wang rwo...@gmail.com wrote:
Build the GBeanInfo with the attribute name caselessly?
Currently, we build the GBeanInfo attribute according to the java code
convention. However, we user set the attribute throught the plan, he have to
pay attention to the case of the attribute name, such as:
gbean name=SMTPTransport
attribute name=host${SMTPHost}/attribute
attribute name=port${SMTPPort}/attribute
/gbean
and
gbean
name=org.apache.geronimo.configs/tomcat6/2.1.5-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.5-SNAPSHOT/car,j2eeType=GBean,name=uniquename2
load=false
gbeanInfo=org.apache.geronimo.tomcat.connector.Http11ConnectorGBean
attribute name=keepAliveTimeout6/attribute
attribute name=maxThreads40/attribute
attribute name=acceptCount10/attribute
attribute name=connectionTimeout6/attribute
attribute name=connectionLinger-1/attribute
attribute name=address0.0.0.0/attribute
but we it comes to the ra.xml, we always use the first upper case word to
define the properties, such as:
config-property-nameDatabaseName/config-property-name
config-property-typejava.lang.String/config-property-type
and that causes the program logic in the config module builder should deal
with that specificly...programmer might hate that..
So, if either the user or developer will get un-happyness on this
configuration, why not we build the GBeanInfo with a caseless name
indentifid GAttributeInfo?
-Rex
Jun 23
Should we filter those unimportant log out from current server log ?
I believe there are some log that needs to be filtered out from current server log because they are not good/useful information as part of default INFO in log. All these kind of log messages could do is to bury the useful info or to mislead the new users. Some sample of them are: 2009-06-12 16:53:55,171 INFO [PortletContextManager] Registering 24 portlets for context /console-base 2009-06-12 16:53:55,203 INFO [PortletContextManager] Portlet application with application id '/console-base' already registered. 2009-06-12 16:53:55,203 INFO [PortletContextManager] Registering 24 portlets for context /console-base 2009-06-12 16:53:55,234 INFO [PortletContextManager] Portlet application with application id '/console-base' already registered. 2009-06-12 16:53:55,234 INFO [PortletContextManager] Registering 24 portlets for context /console-base 2009-06-12 16:53:55,265 INFO [PortletContextManager] Portlet application with application id '/console-base' already registered. . 2009-06-23 13:22:36,484 INFO [XSRFHandler] Created session for uid=null with sessionId=2486E123C24B5E399859E9F5BAFD95BD, uniqueId=-7432393335768912086 2009-06-23 13:22:36,546 INFO [XSRFHandler] Updated HTML content with XSRF JavaScript for requestURI=/ Maybe we could just redirect them to another log file or just change these kind of message to DEBUG from current INFO. Anyway, we must make sure the default log be *concise *and only contain important info *that users want to know*. Any comments ? -- Shawn
Re: svn commit: r787737 - /geronimo/samples/trunk/samples/app-per-port/app-per-port-war1-jetty/pom.xml
Shouldn't we include artifactAlias entries in the 2.2 server to preserve
existing application compatibility?
-Donald
ga...@apache.org wrote:
Author: gawor
Date: Tue Jun 23 15:52:26 2009
New Revision: 787737
URL: http://svn.apache.org/viewvc?rev=787737view=rev
Log:
minor fix for samples: use jetty property
Modified:
geronimo/samples/trunk/samples/app-per-port/app-per-port-war1-jetty/pom.xml
Modified:
geronimo/samples/trunk/samples/app-per-port/app-per-port-war1-jetty/pom.xml
URL:
http://svn.apache.org/viewvc/geronimo/samples/trunk/samples/app-per-port/app-per-port-war1-jetty/pom.xml?rev=787737r1=787736r2=787737view=diff
==
--- geronimo/samples/trunk/samples/app-per-port/app-per-port-war1-jetty/pom.xml
(original)
+++ geronimo/samples/trunk/samples/app-per-port/app-per-port-war1-jetty/pom.xml
Tue Jun 23 15:52:26 2009
@@ -56,7 +56,7 @@
dependency
groupIdorg.apache.geronimo.configs/groupId
-artifactIdjetty6-deployer/artifactId
+artifactId${jetty}-deployer/artifactId
version${geronimoVersion}/version
typecar/type
scopeprovided/scope
@@ -79,7 +79,7 @@
dependency
groupIdorg.apache.geronimo.configs/groupId
-artifactIdjetty6/artifactId
+artifactId${jetty}/artifactId
version${geronimoVersion}/version
typecar/type
/dependency
Re: Suggest to turn off those debug and warning options for maven-compile-plugin
After being initially surprised at the verbosity, I really like the new settings. IMO java code is pretty much unusable unless it is compiled with debug info, so I'm +1 to keeping the debug flag on. I have a hard time imagining how showing deprecations and warnings could cause a build error. Can you provide more details? thanks david jencks On Jun 23, 2009, at 2:46 AM, Shawn Jiang wrote: Agree to turn off debug and warning options from current pom because they also caused build failure in my laptop. configuration optimizetrue/optimize debugtrue/debug showDeprecationtrue/showDeprecation showWarningstrue/showWarnings /configuration This setting is in release genesis pom: genesis\genesis-default- flava\2.0\genesis-default-flava-2.0.pom. So that we have to override them in server pom.xml. On Tue, Jun 23, 2009 at 4:40 PM, Ivan xhh...@gmail.com wrote: HI, No sure why we need to turn on those debug and warning options for the maven-compile-plugin, it made much outputs in the building process. And, it caused the compile failure on my workstation, maybe it is caused by my local setting. Shall we turn them off, or there are some reasons that we need to keep them ? Thanks ! -- Ivan -- Shawn
Re: Build the GBeanInfo with the attribute name caselessly?
Perhaps I can be convinced otherwise but I think the attribute and
reference names should remain case sensitive. Are there other DI
systems that have case insensitive property names? What does
blueprint do?
I don't like case insensitive file systems either :-)
I'm not exactly sure what connector code you are thinking of, can you
point to it more specifically?
thanks
david jencks
On Jun 23, 2009, at 6:06 AM, Rex Wang wrote:
Build the GBeanInfo with the attribute name caselessly?
Currently, we build the GBeanInfo attribute according to the java
code convention. However, we user set the attribute throught the
plan, he have to pay attention to the case of the attribute name,
such as:
gbean name=SMTPTransport
attribute name=host${SMTPHost}/attribute
attribute name=port${SMTPPort}/attribute
/gbean
and
gbean name=org.apache.geronimo.configs/tomcat6/2.1.5-
SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.5-
SNAPSHOT/car,j2eeType=GBean,name=uniquename2 load=false
gbeanInfo=org.apache.geronimo.tomcat.connector.Http11ConnectorGBean
attribute name=keepAliveTimeout6/attribute
attribute name=maxThreads40/attribute
attribute name=acceptCount10/attribute
attribute name=connectionTimeout6/attribute
attribute name=connectionLinger-1/attribute
attribute name=address0.0.0.0/attribute
but we it comes to the ra.xml, we always use the first upper case
word to define the properties, such as:
config-property-nameDatabaseName/config-property-name
config-property-typejava.lang.String/config-property-type
and that causes the program logic in the config module builder
should deal with that specificly...programmer might hate that..
So, if either the user or developer will get un-happyness on this
configuration, why not we build the GBeanInfo with a caseless name
indentifid GAttributeInfo?
-Rex
Jun 23
Re: Build the GBeanInfo with the attribute name caselessly?
David Jencks wrote:
Perhaps I can be convinced otherwise but I think the attribute and
reference names should remain case sensitive. Are there other DI
systems that have case insensitive property names? What does
blueprint do?
Blueprint is case sensitive for property names, using the JavaBeans
convention. However, because of how case gets folded when looking for
the setter, thisProperty and ThisProperty would both worknot
totally casesensitive, just an artifact of the rules used for
constructing the method name.
Rick
I don't like case insensitive file systems either :-)
I'm not exactly sure what connector code you are thinking of, can you
point to it more specifically?
thanks
david jencks
On Jun 23, 2009, at 6:06 AM, Rex Wang wrote:
Build the GBeanInfo with the attribute name caselessly?
Currently, we build the GBeanInfo attribute according to the java
code convention. However, we user set the attribute throught the
plan, he have to pay attention to the case of the attribute name,
such as:
gbean name=SMTPTransport
attribute name=host${SMTPHost}/attribute
attribute name=port${SMTPPort}/attribute
/gbean
and
gbean
name=org.apache.geronimo.configs/tomcat6/2.1.5-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.1.5-SNAPSHOT/car,j2eeType=GBean,name=uniquename2
load=false
gbeanInfo=org.apache.geronimo.tomcat.connector.Http11ConnectorGBean
attribute name=keepAliveTimeout6/attribute
attribute name=maxThreads40/attribute
attribute name=acceptCount10/attribute
attribute name=connectionTimeout6/attribute
attribute name=connectionLinger-1/attribute
attribute name=address0.0.0.0/attribute
but we it comes to the ra.xml, we always use the first upper case
word to define the properties, such as:
config-property-nameDatabaseName/config-property-name
config-property-typejava.lang.String/config-property-type
and that causes the program logic in the config module builder should
deal with that specificly...programmer might hate that..
So, if either the user or developer will get un-happyness on this
configuration, why not we build the GBeanInfo with a caseless name
indentifid GAttributeInfo?
-Rex
Jun 23
snapshots for G 2.2 artifacts ?
It seems that there is not much in the way of snapshots available for Geronimo 2.2 in the repos. Was there a reason that fresh 2.2 snapshots were not published to the old apache snapshot repo prior to the conversion to nexus? Actually, it looks to me like the snapshots that were published earlier may have been removed - Is some nexus issue with having the snapshots available from the legacy apache snapshot repo? Also, are the current build issues the reason why new a complete set of snapshots have not yet been published to the nexus repo? Joe
Re: snapshots for G 2.2 artifacts ?
The old m2-snapshot repo had artifacts from last Dec. using 2.2-SNAPSHOT, whereas the builds are now creating unique timestamped artifacts for Nexus. And yes, there were problems when trying to build with a mix of unique vs. non-unique snapshot jars I started pushing some new 2.2-SNAPSHOT content out to nexus last week, but could only deploy the framework and testsupport artifacts due to build problems with ActiveMQ in the plugins and haven't had time to go back and rebuild everything again -Donald Joe Bohn wrote: It seems that there is not much in the way of snapshots available for Geronimo 2.2 in the repos. Was there a reason that fresh 2.2 snapshots were not published to the old apache snapshot repo prior to the conversion to nexus? Actually, it looks to me like the snapshots that were published earlier may have been removed - Is some nexus issue with having the snapshots available from the legacy apache snapshot repo? Also, are the current build issues the reason why new a complete set of snapshots have not yet been published to the nexus repo? Joe
[BUILD] trunk: Failed for Revision: 787772
Geronimo Revision: 787772 built with tests included
See the full build-1500.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090623/build-1500.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090623
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 41 minutes 50 seconds
[INFO] Finished at: Tue Jun 23 15:44:59 EDT 2009
[INFO] Final Memory: 407M/1002M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090623/logs-1500-tomcat/
[INFO] Using assembly artifact:
org.apache.geronimo.assemblies:geronimo-tomcat6-javaee5:zip:bin:2.2-SNAPSHOT:provided
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:45.675
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:20.237)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:37.395)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:41.582)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:22.212)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:29.449)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:01:27.134) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:02:00.714)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:52.594)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:01:12.234)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:46.136)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:34.372)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.584)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:35.742)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:08.732)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:00.009)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:53.987)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:32.348)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:54.255)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security SUCCESS (0:00:49.457)
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.106)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:31.594)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:33.229)
[INFO] web-testsuite/test-tomcat RUNNING
[INFO] web
Re: svn commit: r787829 - in /geronimo/daytrader/trunk: daytrader-webonly/pom.xml modules/dojo-ui-web/pom.xml modules/json-proxy/pom.xml modules/web/pom.xml pom.xml repository/
Shouldn't the server provide a artifactAlias for JSTL? -Donald jb...@apache.org wrote: Author: jbohn Date: Tue Jun 23 20:41:01 2009 New Revision: 787829 URL: http://svn.apache.org/viewvc?rev=787829view=rev Log: fix daytrader build to match the latest trunk changes - change in tomcat build and location of jstl Removed: geronimo/daytrader/trunk/repository/ Modified: geronimo/daytrader/trunk/daytrader-webonly/pom.xml geronimo/daytrader/trunk/modules/dojo-ui-web/pom.xml geronimo/daytrader/trunk/modules/json-proxy/pom.xml geronimo/daytrader/trunk/modules/web/pom.xml geronimo/daytrader/trunk/pom.xml Modified: geronimo/daytrader/trunk/daytrader-webonly/pom.xml URL: http://svn.apache.org/viewvc/geronimo/daytrader/trunk/daytrader-webonly/pom.xml?rev=787829r1=787828r2=787829view=diff == --- geronimo/daytrader/trunk/daytrader-webonly/pom.xml (original) +++ geronimo/daytrader/trunk/daytrader-webonly/pom.xml Tue Jun 23 20:41:01 2009 @@ -51,7 +51,7 @@ scopeprovided/scope /dependency dependency -groupIdjstl/groupId +groupIdjavax.servlet/groupId artifactIdjstl/artifactId scopeprovided/scope /dependency Modified: geronimo/daytrader/trunk/modules/dojo-ui-web/pom.xml URL: http://svn.apache.org/viewvc/geronimo/daytrader/trunk/modules/dojo-ui-web/pom.xml?rev=787829r1=787828r2=787829view=diff == --- geronimo/daytrader/trunk/modules/dojo-ui-web/pom.xml (original) +++ geronimo/daytrader/trunk/modules/dojo-ui-web/pom.xml Tue Jun 23 20:41:01 2009 @@ -47,7 +47,7 @@ scopeprovided/scope /dependency dependency -groupIdjstl/groupId +groupIdjavax.servlet/groupId artifactIdjstl/artifactId scopeprovided/scope /dependency Modified: geronimo/daytrader/trunk/modules/json-proxy/pom.xml URL: http://svn.apache.org/viewvc/geronimo/daytrader/trunk/modules/json-proxy/pom.xml?rev=787829r1=787828r2=787829view=diff == --- geronimo/daytrader/trunk/modules/json-proxy/pom.xml (original) +++ geronimo/daytrader/trunk/modules/json-proxy/pom.xml Tue Jun 23 20:41:01 2009 @@ -52,7 +52,7 @@ scopeprovided/scope /dependency dependency -groupIdjstl/groupId +groupIdjavax.servlet/groupId artifactIdjstl/artifactId scopeprovided/scope /dependency Modified: geronimo/daytrader/trunk/modules/web/pom.xml URL: http://svn.apache.org/viewvc/geronimo/daytrader/trunk/modules/web/pom.xml?rev=787829r1=787828r2=787829view=diff == --- geronimo/daytrader/trunk/modules/web/pom.xml (original) +++ geronimo/daytrader/trunk/modules/web/pom.xml Tue Jun 23 20:41:01 2009 @@ -59,7 +59,7 @@ scopeprovided/scope /dependency dependency -groupIdjstl/groupId +groupIdjavax.servlet/groupId artifactIdjstl/artifactId scopeprovided/scope /dependency Modified: geronimo/daytrader/trunk/pom.xml URL: http://svn.apache.org/viewvc/geronimo/daytrader/trunk/pom.xml?rev=787829r1=787828r2=787829view=diff == --- geronimo/daytrader/trunk/pom.xml (original) +++ geronimo/daytrader/trunk/pom.xml Tue Jun 23 20:41:01 2009 @@ -141,7 +141,6 @@ /organization modules -modulerepository/module modulemodules/ejb/module modulemodules/web/module modulemodules/streamer/module
Re: svn commit: r787829 - in /geronimo/daytrader/trunk: daytrader-webonly/pom.xml modules/dojo-ui-web/pom.xml modules/json-proxy/pom.xml modules/web/pom.xml pom.xml repository/
These dependency updates are necessary for the build to succeed so runtime aliases won't help. Joe Donald Woods wrote: Shouldn't the server provide a artifactAlias for JSTL? -Donald jb...@apache.org wrote: Author: jbohn Date: Tue Jun 23 20:41:01 2009 New Revision: 787829 URL: http://svn.apache.org/viewvc?rev=787829view=rev Log: fix daytrader build to match the latest trunk changes - change in tomcat build and location of jstl Removed: geronimo/daytrader/trunk/repository/ Modified: geronimo/daytrader/trunk/daytrader-webonly/pom.xml geronimo/daytrader/trunk/modules/dojo-ui-web/pom.xml geronimo/daytrader/trunk/modules/json-proxy/pom.xml geronimo/daytrader/trunk/modules/web/pom.xml geronimo/daytrader/trunk/pom.xml Modified: geronimo/daytrader/trunk/daytrader-webonly/pom.xml URL: http://svn.apache.org/viewvc/geronimo/daytrader/trunk/daytrader-webonly/pom.xml?rev=787829r1=787828r2=787829view=diff == --- geronimo/daytrader/trunk/daytrader-webonly/pom.xml (original) +++ geronimo/daytrader/trunk/daytrader-webonly/pom.xml Tue Jun 23 20:41:01 2009 @@ -51,7 +51,7 @@ scopeprovided/scope /dependency dependency -groupIdjstl/groupId +groupIdjavax.servlet/groupId artifactIdjstl/artifactId scopeprovided/scope /dependency Modified: geronimo/daytrader/trunk/modules/dojo-ui-web/pom.xml URL: http://svn.apache.org/viewvc/geronimo/daytrader/trunk/modules/dojo-ui-web/pom.xml?rev=787829r1=787828r2=787829view=diff == --- geronimo/daytrader/trunk/modules/dojo-ui-web/pom.xml (original) +++ geronimo/daytrader/trunk/modules/dojo-ui-web/pom.xml Tue Jun 23 20:41:01 2009 @@ -47,7 +47,7 @@ scopeprovided/scope /dependency dependency -groupIdjstl/groupId +groupIdjavax.servlet/groupId artifactIdjstl/artifactId scopeprovided/scope /dependency Modified: geronimo/daytrader/trunk/modules/json-proxy/pom.xml URL: http://svn.apache.org/viewvc/geronimo/daytrader/trunk/modules/json-proxy/pom.xml?rev=787829r1=787828r2=787829view=diff == --- geronimo/daytrader/trunk/modules/json-proxy/pom.xml (original) +++ geronimo/daytrader/trunk/modules/json-proxy/pom.xml Tue Jun 23 20:41:01 2009 @@ -52,7 +52,7 @@ scopeprovided/scope /dependency dependency -groupIdjstl/groupId +groupIdjavax.servlet/groupId artifactIdjstl/artifactId scopeprovided/scope /dependency Modified: geronimo/daytrader/trunk/modules/web/pom.xml URL: http://svn.apache.org/viewvc/geronimo/daytrader/trunk/modules/web/pom.xml?rev=787829r1=787828r2=787829view=diff == --- geronimo/daytrader/trunk/modules/web/pom.xml (original) +++ geronimo/daytrader/trunk/modules/web/pom.xml Tue Jun 23 20:41:01 2009 @@ -59,7 +59,7 @@ scopeprovided/scope /dependency dependency -groupIdjstl/groupId +groupIdjavax.servlet/groupId artifactIdjstl/artifactId scopeprovided/scope /dependency Modified: geronimo/daytrader/trunk/pom.xml URL: http://svn.apache.org/viewvc/geronimo/daytrader/trunk/pom.xml?rev=787829r1=787828r2=787829view=diff == --- geronimo/daytrader/trunk/pom.xml (original) +++ geronimo/daytrader/trunk/pom.xml Tue Jun 23 20:41:01 2009 @@ -141,7 +141,6 @@ /organization modules -modulerepository/module modulemodules/ejb/module modulemodules/web/module modulemodules/streamer/module
Help to republish Tomcat Ext modules
I applied a missed patch for EL to the Tomcat Ext modules, it is not published to Apache.snapshot. Please help to republish it, thanks ! -- Ivan
The scope and schedule for G 2.2 samples release
Hi folks, I would like to take the ownership of releasing a new G samples release for G 2.2 server. Please let me know your thoughts about it. So far, what I can think for this new samples release to do as follows: 1. Update and build the current samples trunk, and make sure those samples function well with G 2.2 server 2. Add one or two new samples to demo how to run popular frameworks app, such as Struts, Spring, on Geronimo 3. Verify and ensure G samples 2.1.2 functions well on G 2.2 server? let's determine the scope of samples release first, then to setup a schedule about it. By default, I will assume it is a separate release from G 2.2 server like G samples 2.1.2 did. Please raise your thoughts/comments to this thread, and I would like to get the scope determined before July 10. Thanks and looking forward to your response. Regards, Forrest -- View this message in context: http://www.nabble.com/The-scope-and-schedule-for-G-2.2-samples-release-tp24177645s134p24177645.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Created: (GERONIMO-4707) I18N logs could not displayed correctly on Web Access Log Viewer portlet
I18N logs could not displayed correctly on Web Access Log Viewer portlet Key: GERONIMO-4707 URL: https://issues.apache.org/jira/browse/GERONIMO-4707 Project: Geronimo Issue Type: Bug Security Level: public (Regular issues) Components: console Affects Versions: 2.2 Reporter: Ivan Priority: Minor While Geronimo is running on I18N platform, by default, like Jetty, it could output logs in I18N language. But in the web log portlets, those logs could not displayed correctly. -- 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: 787875
Geronimo Revision: 787875 built with tests included
See the full build-2100.log file at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090623/build-2100.log
Download the binaries from
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090623
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 39 minutes 8 seconds
[INFO] Finished at: Tue Jun 23 21:43:14 EDT 2009
[INFO] Final Memory: 681M/1012M
[INFO]
TESTSUITE RESULTS (Failures only)
=
Assembly: tomcat
=
See full test results and logs at
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090623/logs-2100-tomcat/
[INFO] Using geronimoHome:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-tomcat6-javaee5-2.2-SNAPSHOT
[INFO] Installing assembly...
[INFO] Expanding:
/home/geronimo/.m2/repository/org/apache/geronimo/assemblies/geronimo-tomcat6-javaee5/2.2-SNAPSHOT/geronimo-tomcat6-javaee5-2.2-SNAPSHOT-bin.zip
into /home/geronimo/geronimo/trunk/testsuite/target
[INFO] Starting Geronimo server...
[INFO] Selected option set: default
[INFO] Redirecting output to:
/home/geronimo/geronimo/trunk/testsuite/target/geronimo-logs/org.apache.geronimo.mavenplugins.geronimo.server.StartServerMojo.log
[INFO] Waiting for Geronimo server...
[INFO] Geronimo server started in 0:00:42.900
[INFO] [shitty:install {execution: default}]
[INFO] Installing /home/geronimo/geronimo/trunk/testsuite/pom.xml to
/home/geronimo/.m2/repository/org/apache/geronimo/testsuite/testsuite/testing/testsuite-testing.pom
[INFO] [shitty:test {execution: default}]
[INFO] Starting 36 test builds
[INFO]
[INFO]
---
[INFO]
[INFO] commands-testsuite/deploy RUNNING
[INFO] commands-testsuite/deploy SUCCESS (0:01:04.907)
[INFO] commands-testsuite/gshell RUNNING
[INFO] commands-testsuite/gshell SUCCESS (0:00:32.677)
[INFO] commands-testsuite/jaxws RUNNING
[INFO] commands-testsuite/jaxws SUCCESS (0:00:38.237)
[INFO] commands-testsuite/shutdownRUNNING
[INFO] commands-testsuite/shutdownSUCCESS (0:00:20.691)
[INFO] concurrent-testsuite/concurrent-basic RUNNING
[INFO] concurrent-testsuite/concurrent-basic SUCCESS (0:06:27.419)
[INFO] console-testsuite/advanced RUNNING
[INFO] console-testsuite/advanced FAILURE (0:01:20.891) Java
returned: 1
[INFO] console-testsuite/basicRUNNING
[INFO] console-testsuite/basicSUCCESS (0:01:56.642)
[INFO] corba-testsuite/corba-helloworld RUNNING
[INFO] corba-testsuite/corba-helloworld SUCCESS (0:00:54.012)
[INFO] corba-testsuite/corba-marshal RUNNING
[INFO] corba-testsuite/corba-marshal SUCCESS (0:00:49.390)
[INFO] corba-testsuite/corba-mytime RUNNING
[INFO] corba-testsuite/corba-mytime SUCCESS (0:00:47.039)
[INFO] deployment-testsuite/deployment-tests RUNNING
[INFO] deployment-testsuite/deployment-tests SUCCESS (0:00:33.464)
[INFO] deployment-testsuite/jca-cms-tests RUNNING
[INFO] deployment-testsuite/jca-cms-tests SUCCESS (0:00:34.655)
[INFO] deployment-testsuite/manifestcp-tests RUNNING
[INFO] deployment-testsuite/manifestcp-tests SUCCESS (0:00:36.731)
[INFO] enterprise-testsuite/ejb-tests RUNNING
[INFO] enterprise-testsuite/ejb-tests SUCCESS (0:01:00.705)
[INFO] enterprise-testsuite/jms-tests RUNNING
[INFO] enterprise-testsuite/jms-tests SUCCESS (0:01:01.644)
[INFO] enterprise-testsuite/jpa-tests RUNNING
[INFO] enterprise-testsuite/jpa-tests SUCCESS (0:00:50.946)
[INFO] enterprise-testsuite/sec-clientRUNNING
[INFO] enterprise-testsuite/sec-clientSUCCESS (0:00:29.433)
[INFO] enterprise-testsuite/sec-tests RUNNING
[INFO] enterprise-testsuite/sec-tests SUCCESS (0:00:53.258)
[INFO] security-testsuite/test-security RUNNING
[INFO] security-testsuite/test-security FAILURE (0:00:45.230) Java
returned: 1
[INFO] web-testsuite/test-2.1-jspsRUNNING
[INFO] web-testsuite/test-2.1-jspsSUCCESS (0:00:33.911)
[INFO] web-testsuite/test-2.5-servletsRUNNING
[INFO] web-testsuite/test-2.5-servletsSUCCESS (0:00:32.848)
[INFO] web-testsuite/test-myfaces RUNNING
[INFO] web-testsuite/test-myfaces SUCCESS (0:00:35.083)
[INFO] web-testsuite/test-tomcat RUNNING
[INFO] web-testsuite/test-tomcat FAILURE (0:00:21.290) Java
returned: 1
[INFO] web-testsuite/test-web
[jira] Updated: (GERONIMO-4707) I18N logs could not displayed correctly on Web Access Log Viewer portlet
[ https://issues.apache.org/jira/browse/GERONIMO-4707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ivan updated GERONIMO-4707: --- Attachment: screenshot-1.jpg I18N logs could not displayed correctly on Web Access Log Viewer portlet Key: GERONIMO-4707 URL: https://issues.apache.org/jira/browse/GERONIMO-4707 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: console Affects Versions: 2.2 Reporter: Ivan Priority: Minor Attachments: screenshot-1.jpg While Geronimo is running on I18N platform, by default, like Jetty, it could output logs in I18N language. But in the web log portlets, those logs could not displayed correctly. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: The scope and schedule for G 2.2 samples release
Add a sample for EJB security via geronimo descrptor or annotation? Forrest_Xia wrote: Hi folks, I would like to take the ownership of releasing a new G samples release for G 2.2 server. Please let me know your thoughts about it. So far, what I can think for this new samples release to do as follows: 1. Update and build the current samples trunk, and make sure those samples function well with G 2.2 server 2. Add one or two new samples to demo how to run popular frameworks app, such as Struts, Spring, on Geronimo 3. Verify and ensure G samples 2.1.2 functions well on G 2.2 server? let's determine the scope of samples release first, then to setup a schedule about it. By default, I will assume it is a separate release from G 2.2 server like G samples 2.1.2 did. Please raise your thoughts/comments to this thread, and I would like to get the scope determined before July 10. Thanks and looking forward to your response. Regards, Forrest -- View this message in context: http://www.nabble.com/The-scope-and-schedule-for-G-2.2-samples-release-tp24177645s134p24177765.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Commented: (GERONIMODEVTOOLS-580) Servlet/JSP update forces a complete redeploy of a WAR
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12723411#action_12723411 ] Delos Dai commented on GERONIMODEVTOOLS-580: Maybe GEP can try local jsp file hot replacement first, making use of Geronimo server development mode. Servlet/JSP update forces a complete redeploy of a WAR -- Key: GERONIMODEVTOOLS-580 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-580 Project: Geronimo-Devtools Issue Type: Improvement Affects Versions: 2.0.x, 2.2.0 Reporter: Kevan Miller Assignee: Tim McConnell Fix For: 2.2.0 I've had several users comment to me that application development with GEP is not as fast as it should be. Basic scenario is create an application, deploy, test, update, test, update, etc... IIUC, for each update, GEP is repackaging the WAR and running a redeploy. Repackaging/redeploy can take some time (for large apps 30 seconds). IIUC, we could be updating the appropriate JSP/Servlet classes directly and greatly improving this behavior. I don't know how this works, however. Anybody interested in looking at this? I'd like to see this improved in 2.2. If it's something that could be fixed in 2.1.x, that would be great. But that might depend on how extensive the changes are... -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Suggest to turn off those debug and warning options for maven-compile-plugin
This only happens to IBM JDK. \gt\framework\modules\geronimo-kernelmvn clean install -X + Error stacktraces are turned on. Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800) Java version: 1.5.0 Java home: d:\dev\JDKs\ibm_jdk5\jre Default locale: *zh_CN, platform encoding: GB18030* . E:\src\gt\framework\modules\geronimo-kernel\src\main\java\org\apache\geronimo\kernel\config\ConfigurationUtil.java:[407,39] 警告： 在 org.apache.geronimo.kernel.config.Configuration 中的 getConfigurationResolver() 已经不提倡使用 Set set = configuration.getConfigurationResolver().resolve(); E:\src\gt\framework\modules\geronimo-kernel\src\main\java\org\apache\geronimo\kernel\config\ConfigurationUtil.java:[468,42] 警告： 在 org.apache.geronimo.kernel.basic.BasicKernel 中的 getStateReason(org.apache.geronimo.gbean.AbstractName) 已经不提倡使用 stateReason = ((BasicKernel) kernel).getStateReason(gbeanName); [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:699) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) ... 16 more [INFO] [INFO] Total time: 8 seconds [INFO] Finished at: Wed Jun 24 10:54:30 CST 2009 [INFO] Final Memory: 25M/79M [INFO] - I guess something wrong when javac of IBM javac prints the debug/warning messages with GB18030 Encoding. here is what I get when using SUN JDK to bulid. There's no problem to build. --- \gt\framework\modules\geronimo-kernelmvn clean install -X + Error stacktraces are turned on. Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800) Java version: 1.5.0_15 Java home: D:\dev\JDKs\sun_jdk5\jre Default locale: en_US, platform encoding: Cp1252 On Wed, Jun 24, 2009 at 12:28 AM, David Jencks david_jen...@yahoo.comwrote: After being initially surprised at the verbosity, I really like the new settings. IMO java code is pretty much unusable unless it is compiled with debug info, so I'm +1 to keeping the debug flag on. I have a hard time imagining how showing deprecations and warnings could cause a build error. Can you provide more details? thanks david jencks On Jun 23, 2009, at 2:46 AM, Shawn Jiang wrote: Agree to turn off debug and warning options from current pom because they also caused build failure in my laptop. configuration optimizetrue/optimize debugtrue/debug showDeprecationtrue/showDeprecation showWarningstrue/showWarnings /configuration
Re: Suggest to turn off those debug and warning options for maven-compile-plugin
I have to admit that locale and character encoding issues are something I know almost nothing about. I think this is likely a bug in either maven or the IBM compiler, but I have no idea how to figure out which. Do you know why these are different with the different jdks? Default locale: zh_CN, platform encoding: GB18030 Default locale: en_US, platform encoding: Cp1252 Is there some way to make everything use utf-8? If you can figure out anything that makes it seem like this is a maven bug I hope you will file a maven jira :-) thanks david jencks On Jun 23, 2009, at 8:20 PM, Shawn Jiang wrote: This only happens to IBM JDK. \gt\framework\modules\geronimo-kernelmvn clean install -X + Error stacktraces are turned on. Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800) Java version: 1.5.0 Java home: d:\dev\JDKs\ibm_jdk5\jre Default locale: zh_CN, platform encoding: GB18030 . E:\src\gt\framework\modules\geronimo-kernel\src\main\java\org\apache \geronimo\kernel\config\ConfigurationUtil.java:[407,39] 警告： 在 org.apache.geronimo.kernel.config.Configuration 中的 getConfigurationResolver() 已经不提倡使用 Set set = configuration.getConfigurationResolver().resolve(); E:\src\gt\framework\modules\geronimo-kernel\src\main\java\org\apache \geronimo\kernel\config\ConfigurationUtil.java:[468,42] 警告： 在 org.apache.geronimo.kernel.basic.BasicKernel 中的 getStateReason(org.apache.geronimo.gbean.AbstractName) 已经不提倡使用 stateReason = ((BasicKernel) kernel).getStateReason(gbeanName); [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Compilation failure at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 699) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java: 519) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org .apache .maven .lifecycle .DefaultLifecycleExecutor .executeTaskSegments(DefaultLifecycleExecutor.java:332) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java: 356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java: 137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun .reflect .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun .reflect .DelegatingMethodAccessorImpl .invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure at org .apache .maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java: 516) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) at org .apache .maven .plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java: 483) at org .apache .maven .lifecycle .DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java: 678) ... 16 more [INFO] [INFO] Total time: 8 seconds [INFO] Finished at: Wed Jun 24 10:54:30 CST 2009 [INFO] Final Memory: 25M/79M [INFO] - I guess something wrong when javac of IBM javac prints the debug/ warning messages with GB18030 Encoding. here is what I get when using SUN JDK to bulid. There's no problem to build. --- \gt\framework\modules\geronimo-kernelmvn clean install -X + Error stacktraces are turned on. Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800) Java version: 1.5.0_15 Java home: D:\dev\JDKs\sun_jdk5\jre Default locale: en_US, platform encoding: Cp1252 On Wed, Jun 24, 2009 at
Re: Help to republish Tomcat Ext modules
I just pushed a new snapshot. Hopefully, I didn't screw up anything. Jarek On Tue, Jun 23, 2009 at 10:04 PM, Ivan xhh...@gmail.com wrote: I applied a missed patch for EL to the Tomcat Ext modules, it is not published to Apache.snapshot. Please help to republish it, thanks ! -- Ivan
Re: Help to republish Tomcat Ext modules
Thanks, Jarek ! 2009/6/24 Jarek Gawor jga...@gmail.com I just pushed a new snapshot. Hopefully, I didn't screw up anything. Jarek On Tue, Jun 23, 2009 at 10:04 PM, Ivan xhh...@gmail.com wrote: I applied a missed patch for EL to the Tomcat Ext modules, it is not published to Apache.snapshot. Please help to republish it, thanks ! -- Ivan -- Ivan
Re: Help to republish Tomcat Ext modules
I started a deploy, should be done in a couple of minutes. As a geronimo committer you should be able to deploy snapshots, is there a permission problem? mvn clean deploy -Papache-release Lets try to fix any problems before there's an emergency :-) thanks david jencks On Jun 23, 2009, at 7:04 PM, Ivan wrote: I applied a missed patch for EL to the Tomcat Ext modules, it is not published to Apache.snapshot. Please help to republish it, thanks ! -- Ivan
Two versions of Jacc Spec are included in the Geronimo 2.2 build
Hi, Recently, I found there are two Jacc spec jars are packaged in the repository folder of the binary Geronimo daily build, which are 1.0.2-20090622.083250-1 and 1.0.2-SNAPSHOT. The version of 1.0.2-20090622.083250-1 is referenced by jee-spec module, IMO, it should not be included. Also, in the recent sample build log, it shows the simliar build error, but for other modules. I checked the logs of maven and those POM files, so far, I still have no idea about it. Wish someone could give a hand, thanks ! -- Ivan
Re: Help to republish Tomcat Ext modules
Hmm, I never know I could do it :-(. I will try it next time if needed. Thanks ! Ivan 2009/6/24 David Jencks david_jen...@yahoo.com I started a deploy, should be done in a couple of minutes. As a geronimo committer you should be able to deploy snapshots, is there a permission problem? mvn clean deploy -Papache-release Lets try to fix any problems before there's an emergency :-) thanks david jencks On Jun 23, 2009, at 7:04 PM, Ivan wrote: I applied a missed patch for EL to the Tomcat Ext modules, it is not published to Apache.snapshot. Please help to republish it, thanks ! -- Ivan -- Ivan
Re: Suggest to turn off those debug and warning options for maven-compile-plugin
This is a Maven defect definitely, I'll open a JIRA to Maven. Besides, I would try to submit a problem to IBM JDK somewhere about the different behavior. 2009/6/24 David Jencks david_jen...@yahoo.com I have to admit that locale and character encoding issues are something I know almost nothing about. I think this is likely a bug in either maven or the IBM compiler, but I have no idea how to figure out which. Do you know why these are different with the different jdks? Default locale: *zh_CN, platform encoding: GB18030* Default locale: en_US, platform encoding: Cp1252 Is there some way to make everything use utf-8? If you can figure out anything that makes it seem like this is a maven bug I hope you will file a maven jira :-) thanks david jencks On Jun 23, 2009, at 8:20 PM, Shawn Jiang wrote: This only happens to IBM JDK. \gt\framework\modules\geronimo-kernelmvn clean install -X + Error stacktraces are turned on. Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800) Java version: 1.5.0 Java home: d:\dev\JDKs\ibm_jdk5\jre Default locale: *zh_CN, platform encoding: GB18030* . E:\src\gt\framework\modules\geronimo-kernel\src\main\java\org\apache\geronimo\kernel\config\ConfigurationUtil.java:[407,39] 警告： 在 org.apache.geronimo.kernel.config.Configuration 中的 getConfigurationResolver() 已经不提倡使用 Set set = configuration.getConfigurationResolver().resolve(); E:\src\gt\framework\modules\geronimo-kernel\src\main\java\org\apache\geronimo\kernel\config\ConfigurationUtil.java:[468,42] 警告： 在 org.apache.geronimo.kernel.basic.BasicKernel 中的 getStateReason(org.apache.geronimo.gbean.AbstractName) 已经不提倡使用 stateReason = ((BasicKernel) kernel).getStateReason(gbeanName); [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Compilation failure at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:699) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.CompilationFailureException: Compilation failure at org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:516) at org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:114) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) ... 16 more [INFO] [INFO] Total time: 8 seconds [INFO] Finished at: Wed Jun 24 10:54:30 CST 2009 [INFO] Final Memory: 25M/79M [INFO] - I guess something wrong when javac of IBM javac prints the debug/warning messages with GB18030 Encoding. here is what I get when using SUN JDK to bulid. There's no problem to build. --- \gt\framework\modules\geronimo-kernelmvn clean install -X + Error stacktraces are turned on. Apache Maven 2.1.0 (r755702; 2009-03-19 03:10:27+0800)
