date:20110601

Geronimo Revision: 1130025 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/build-0300.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/unit-test-reports
 
 T E S T S
---
There are no tests to run.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] [bundle:bundle {execution: default-bundle}]
[INFO] [geronimo-osgi:verify-manifest {execution: verify-manifest}]
[INFO] Resolving OSGi bundle: org.apache.geronimo.framework.geronimo-obr
[INFO] OSGi bundle is resolved: org.apache.geronimo.framework.geronimo-obr
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-obr-3.0-SNAPSHOT.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-obr/target/geronimo-obr-3.0-SNAPSHOT.jar
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/framework/geronimo-obr/3.0-SNAPSHOT/geronimo-obr-3.0-SNAPSHOT.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Parsing file:/home/geronimo/.m2/repository/repository.xml
[INFO] Installing 
org/apache/geronimo/framework/geronimo-obr/3.0-SNAPSHOT/geronimo-obr-3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO] 
[INFO] Building Geronimo Framework, Modules :: Deployment
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 33 source files to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/test/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 2 source files to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports

---
 T E S T S
---
Running org.apache.geronimo.deployment.SingleFileHotDeployerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.128 sec
Running org.apache.geronimo.deployment.DeploymentContextTest
Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.037 sec  
FAILURE!

Results :

Failed tests: 
  testMainfestClassPath3(org.apache.geronimo.deployment.DeploymentContextTest)

Tests run: 13, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports
 for the individual test results.
[INFO] 
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.

Please refer to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports
 for the individual test results.
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java

[jira] [Commented] (GERONIMODEVTOOLS-754) java.lang.NullPointerException: Could not publish to the server.

2011-06-01 Thread Yi Xiao (JIRA)


[ 
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13042059#comment-13042059
 ] 

Yi Xiao commented on GERONIMODEVTOOLS-754:
--

I test under the same environment, but use the latest GEP, here's no such 
error. Jacky, you could try it using latest GEP.

 java.lang.NullPointerException: Could not publish to the server.
 

 Key: GERONIMODEVTOOLS-754
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-754
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0
 Environment: Windows XP SP3 x86
 IBM jdk Java60
 Geronimo build on 20110525
 GEP Version: 3.0.0-20110328111526
Reporter: Jacky Liu
Priority: Minor
 Attachments: test-ejb.jar, test-web.war


 1. start Geronimo v3.0 through GEP
 2. import EJB JAR file
 3. import WAR file
 4. select the EJB project and make it run on server  --  ERROR OCCURS!!
 5. select the WAR project and make it run on server  --  ERROR OCCURS!!
 Could not publish to the server.
 java.lang.NullPointerException
 But EJB and WAR turned out to be started and synchronized correctly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Resolved] (GERONIMODEVTOOLS-754) java.lang.NullPointerException: Could not publish to the server.

2011-06-01 Thread Yi Xiao (JIRA)


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

Yi Xiao resolved GERONIMODEVTOOLS-754.
--

Resolution: Fixed

 java.lang.NullPointerException: Could not publish to the server.
 

 Key: GERONIMODEVTOOLS-754
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-754
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0
 Environment: Windows XP SP3 x86
 IBM jdk Java60
 Geronimo build on 20110525
 GEP Version: 3.0.0-20110328111526
Reporter: Jacky Liu
Priority: Minor
 Attachments: test-ejb.jar, test-web.war


 1. start Geronimo v3.0 through GEP
 2. import EJB JAR file
 3. import WAR file
 4. select the EJB project and make it run on server  --  ERROR OCCURS!!
 5. select the WAR project and make it run on server  --  ERROR OCCURS!!
 Could not publish to the server.
 java.lang.NullPointerException
 But EJB and WAR turned out to be started and synchronized correctly.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: class path issue

2011-06-01 Thread ranbaab

Hi Kevan,

With your suggestion to hide the castor, now it is working

dep:hidden-classes
  dep:filterorg.exolab/dep:filter
  dep:filterorg.castor/dep:filter
/dep:hidden-classes
  /dep:environment 

Instead of putting all the dependencies jar from the web-inf/lib to
repository folder of geronimo, I just moved the xerces.jar in the endorsed
folder and put the below deployment plan

?xml version=1.0 encoding=UTF-8?
web-app xmlns=http://geronimo.apache.org/xml/ns/j2ee/web-2.0.1;
 xmlns:sys=http://geronimo.apache.org/xml/ns/deployment-1.2;
sys:environment
sys:moduleId
sys:groupIdsamples/sys:groupId
sys:artifactIdbhm/sys:artifactId
sys:version5.2/sys:version
sys:typewar/sys:type
/sys:moduleId 
   sys:hidden-classes
  sys:filterorg.exolab/sys:filter
  sys:filterorg.castor/sys:filter
   /sys:hidden-classes
/sys:environment
context-root/bhm/context-root
gbean name=MyAppSystemProperties   
class=org.apache.geronimo.system.properties.SystemProperties
attribute name=systemPathProperties
 com.myApp.ConfigFile=var
/attribute
reference name=ServerInfo
nameServerInfo/name
/reference
/gbean
/web-app


So, is there any further improvement which can be done.

Thanks,
Ranjan



--
View this message in context: 
http://apache-geronimo.328035.n3.nabble.com/class-path-issue-tp3005965p3009991.html
Sent from the Development mailing list archive at Nabble.com.

[jira] [Closed] (GERONIMODEVTOOLS-755) Url not created rightly for dynamic web project and this deployed application can't be found on admin console from server view

2011-06-01 Thread Tina Li (JIRA)


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

Tina Li closed GERONIMODEVTOOLS-755.


   Resolution: Cannot Reproduce
Fix Version/s: 3.0

Use the Gep version:Build id: 20110531125652
This problem can't be reproduced.

 Url not created rightly for dynamic web project and this deployed application 
 can't be found on admin console from server view
 --

 Key: GERONIMODEVTOOLS-755
 URL: 
 https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-755
 Project: Geronimo-Devtools
  Issue Type: Bug
  Components: eclipse-plugin
Affects Versions: 3.0
 Environment: geronimo server build: 2011.05.16-06:06:48.065+0800-3.0 
 snapshot
 Gep version:20110526162103
 Eclipse:Helios Service Release 1
 JRE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260sr9-20110203_74623 (JIT 
 enabled, AOT enabled)
Reporter: Tina Li
 Fix For: 3.0


 1.Start eclipse using command: eclipse -clean  under the directory of eclipse
 2.Create a dynamic web project named testWeb
 3.Create an html file named index.html and add the text Hello！ inside the 
 body section
 4.Right-click this project and choose Run As--Run on server, create the 
 server runtime using jdk 6 and geronimo 3.0 snapshot
 5.Then from the console of eclipse: it showed the server started successfully 
 and the url created is 
 :http://localhost:8080/org.eclipse.jst.jee.server:testWeb/;
 6.Open the browser and open admin console of the server ,click Web 
 Apps(WAR) ,but can't find this application.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: Progress on osgi-friendliness


On May 31, 2011, at 1:44 AM, David Jencks wrote:

 The new aries proxy code also seems to consume significantly more permgen 
 space.  I didn't investigate in detail but a full server runs out of permgen 
 space around half way through starting with 128 MB permgen.  My server 
 started OK with 1024 MB permgen.

FYI, the server will start fine with a 256m permgen. I think you could get by 
with ~ 170m or so...

JAVA_OPTS=-Xmx256m -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError 
./geronimo run

should do it... 

--kevan

[jira] [Created] (GERONIMO-5987) The lock file in ActiveMQ is not referenced correctly

The lock file in ActiveMQ is not referenced correctly
-

 Key: GERONIMO-5987
 URL: https://issues.apache.org/jira/browse/GERONIMO-5987
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: ActiveMQ
Affects Versions: 3.0
 Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4 
(Tikanga)
Reporter: Russell E Glaue


I am testing with geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT, 
geronimo-tomcat7-javaee6-web-3.0-20110523.171218-97

ActiveMQ is configured to run as org.apache.geronimo.home.dir/var/activemq , 
and does not cooperate with multi-server configurations. This is the use of the 
org.apache.geronimo.server.name option. (see: 
https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html)

When wanting to run more than a single server instance, the ActiveMQ startup 
will block waiting for the lock file $GERONIMO_HOME/var/activemq/lock to 
become available.

Obviously this causes any server instance started after the first server 
instance is started to block during startup while waiting for the lock file to 
become available.


Steps to repeat:

1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)

2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
-- 2C-1. mkdir gserver1
-- 2C-2. cp -rp var gserver1/
-- 2C-3. cp -rp etc gserver1/
-- 2C-4. cp -rp repository gserver1/

-- (the deploy:new-server-instance only does step 1 and 2, create base
directory and var/ directory, you still have to manually copy/create etc and
repository)

3. update the PortOffset parameter in 
var/config/config-substitutions.properties in each instance

4. Start the server instances:
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=server1 bin/startup
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=server2 bin/startup

5. `tail -f server2/var/logs/geronimo.log` and you will see this as the last 
line that outputs:
2011-05-31 16:26:39,609 WARN  [AMQPersistenceAdapter] Waiting to Lock the 
Store var/activemq
The server waits here indefinitely.

6. Shutdown the server1 instance and you will see the server2 instance 
continue on in the startup procedures.

* When I first start the server1 instance, the directory 
$org.apache.geronimo.home.dir/var/activemq is created and populated. Instead 
it should be 
org.apache.geronimo.home.dir/org.apache.geronimo.server.name/var/activemq 
that is created and populated.
* Probably the patch should be to reference the ActiveMQ working directory as 
org.apache.geronimo.server.dir/var/activemq


--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-5987) The lock file in ActiveMQ is not referenced correctly

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

Russell E Glaue updated GERONIMO-5987:
--

Affects Version/s: 3.0-M2
3.0-M1

The lock file in ActiveMQ is not referenced correctly
-

Key: GERONIMO-5987
URL: https://issues.apache.org/jira/browse/GERONIMO-5987
Project: Geronimo
Issue Type: Bug
Security Level: public(Regular issues)
Components: ActiveMQ
Affects Versions: 3.0-M1, 3.0-M2, 3.0
Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4
(Tikanga)
Reporter: Russell E Glaue
Labels: geronimo

I am testing with geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT,
geronimo-tomcat7-javaee6-web-3.0-20110523.171218-97
ActiveMQ is configured to run as org.apache.geronimo.home.dir/var/activemq
, and does not cooperate with multi-server configurations. This is the use of
the org.apache.geronimo.server.name option. (see:
https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html)
When wanting to run more than a single server instance, the ActiveMQ startup
will block waiting for the lock file $GERONIMO_HOME/var/activemq/lock to
become available.
Obviously this causes any server instance started after the first server
instance is started to block during startup while waiting for the lock file
to become available.
Steps to repeat:
1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
-- 2C-1. mkdir gserver1
-- 2C-2. cp -rp var gserver1/
-- 2C-3. cp -rp etc gserver1/
-- 2C-4. cp -rp repository gserver1/
-- (the deploy:new-server-instance only does step 1 and 2, create base
directory and var/ directory, you still have to manually copy/create etc and
repository)
3. update the PortOffset parameter in
var/config/config-substitutions.properties in each instance
4. Start the server instances:
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=server1 bin/startup
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=server2 bin/startup
5. `tail -f server2/var/logs/geronimo.log` and you will see this as the last
line that outputs:
2011-05-31 16:26:39,609 WARN [AMQPersistenceAdapter] Waiting to Lock the
Store var/activemq
The server waits here indefinitely.
6. Shutdown the server1 instance and you will see the server2 instance
continue on in the startup procedures.
* When I first start the server1 instance, the directory
$org.apache.geronimo.home.dir/var/activemq is created and populated.
Instead it should be
org.apache.geronimo.home.dir/org.apache.geronimo.server.name/var/activemq
that is created and populated.
* Probably the patch should be to reference the ActiveMQ working directory as
org.apache.geronimo.server.dir/var/activemq

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[BUILD] trunk: Failed for Revision: 1130142

Geronimo Revision: 1130142 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/unit-test-reports
 
 T E S T S
---
There are no tests to run.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] [bundle:bundle {execution: default-bundle}]
[INFO] [geronimo-osgi:verify-manifest {execution: verify-manifest}]
[INFO] Resolving OSGi bundle: org.apache.geronimo.framework.geronimo-obr
[INFO] OSGi bundle is resolved: org.apache.geronimo.framework.geronimo-obr
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-obr-3.0-SNAPSHOT.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-obr/target/geronimo-obr-3.0-SNAPSHOT.jar
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/framework/geronimo-obr/3.0-SNAPSHOT/geronimo-obr-3.0-SNAPSHOT.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Parsing file:/home/geronimo/.m2/repository/repository.xml
[INFO] Installing 
org/apache/geronimo/framework/geronimo-obr/3.0-SNAPSHOT/geronimo-obr-3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO] 
[INFO] Building Geronimo Framework, Modules :: Deployment
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 33 source files to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/test/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 2 source files to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports

---
 T E S T S
---
Running org.apache.geronimo.deployment.SingleFileHotDeployerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.126 sec
Running org.apache.geronimo.deployment.DeploymentContextTest
Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.038 sec  
FAILURE!

Results :

Failed tests: 
  testMainfestClassPath3(org.apache.geronimo.deployment.DeploymentContextTest)

Tests run: 13, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports
 for the individual test results.
[INFO] 
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.

Please refer to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports
 for the individual test results.
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java

Re: Progress on osgi-friendliness

2011-06-01 Thread Forrest Xia

According to my recent experience, permsize=256m is kind of small for 3.0,
though the server could start, but it will fail during application
deployment from admin console after.

Forrest

On Wed, Jun 1, 2011 at 9:05 PM, Kevan Miller kevan.mil...@gmail.com wrote:


 On May 31, 2011, at 1:44 AM, David Jencks wrote:

  The new aries proxy code also seems to consume significantly more permgen
 space.  I didn't investigate in detail but a full server runs out of permgen
 space around half way through starting with 128 MB permgen.  My server
 started OK with 1024 MB permgen.

 FYI, the server will start fine with a 256m permgen. I think you could get
 by with ~ 170m or so...

 JAVA_OPTS=-Xmx256m -XX:MaxPermSize=256m -XX:+HeapDumpOnOutOfMemoryError
 ./geronimo run

 should do it...

 --kevan

Re: Progress on osgi-friendliness


On Jun 1, 2011, at 12:10 PM, Forrest Xia wrote:

 According to my recent experience, permsize=256m is kind of small for 3.0, 
 though the server could start, but it will fail during application deployment 
 from admin console after.

All depends on your application size, of course... I expect that we'll adjust 
our default settings as things stabilize. Hopefully we'll be taking some steps 
to reduce/minimize the server footprint, also. 

Note that deployment method (admin console, command line, hot-deploy) shouldn't 
make any difference...

--kevan

[jira] [Updated] (GERONIMO-5987) The ActiveMQ working directory is not referenced correctly

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

Russell E Glaue updated GERONIMO-5987:
--

Description:
I am testing with geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT,
geronimo-tomcat7-javaee6-web-3.0-20110523.171218-97

ActiveMQ is configured to run as org.apache.geronimo.home.dir/var/activemq ,
and does not cooperate with multi-server configurations. This is the use of the
org.apache.geronimo.server.name option. (see:
https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html)

When wanting to run more than a single server instance, the ActiveMQ startup
will block waiting for the lock file $GERONIMO_HOME/var/activemq/lock to
become available.

Obviously this causes any server instance started after the first server
instance is started to block during startup while waiting for the lock file to
become available.

Steps to repeat:

1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)

2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
-- 2C-1. mkdir gserver2
-- 2C-2. cp -rp var gserver2/
-- 2C-3. cp -rp etc gserver2/
-- 2C-4. cp -rp repository gserver2/

-- (the deploy:new-server-instance only does step 1 and 2, create base
directory and var/ directory, you still have to manually copy/create etc and
repository)

3. update the PortOffset parameter in
var/config/config-substitutions.properties in each instance

4. Start the server instances:
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=gserver1 bin/startup
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=gserver2 bin/startup

5. `tail -f gserver2/var/logs/geronimo.log` and you will see this as the last
line that outputs:
2011-05-31 16:26:39,609 WARN [AMQPersistenceAdapter] Waiting to Lock the
Store var/activemq
The server waits here indefinitely.

6. Shutdown the gserver1 instance and you will see the gserver2 instance
continue on in the startup procedures.

* When I first start the gserver1 instance, the directory
org.apache.geronimo.home.dir/var/activemq is created and populated. Instead
it should be
org.apache.geronimo.home.dir/org.apache.geronimo.server.name/var/activemq
that is created and populated.
* Probably the patch should be to reference the ActiveMQ working directory as
org.apache.geronimo.server.dir/var/activemq

was:
I am testing with geronimo-tomcat7-javaee6-web-3.0-SNAPSHOT,
geronimo-tomcat7-javaee6-web-3.0-20110523.171218-97

When wanting to run more than a single server instance, the ActiveMQ startup
will block waiting for the lock file $GERONIMO_HOME/var/activemq/lock to
become available.

Obviously this causes any server instance started after the first server
instance is started to block during startup while waiting for the lock file to
become available.

Steps to repeat:

1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)

2. Create the server instances:
-- 2A. cd ${GERONIMO_HOME}
-- 2B-1. mkdir gserver1
-- 2B-2. cp -rp var gserver1/
-- 2B-3. cp -rp etc gserver1/
-- 2B-4. cp -rp repository gserver1/
-- 2C-1. mkdir gserver1
-- 2C-2. cp -rp var gserver1/
-- 2C-3. cp -rp etc gserver1/
-- 2C-4. cp -rp repository gserver1/

-- (the deploy:new-server-instance only does step 1 and 2, create base
directory and var/ directory, you still have to manually copy/create etc and
repository)

3. update the PortOffset parameter in
var/config/config-substitutions.properties in each instance

4. Start the server instances:
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=server1 bin/startup
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=server2 bin/startup

5. `tail -f server2/var/logs/geronimo.log` and you will see this as the last
line that outputs:
2011-05-31 16:26:39,609 WARN [AMQPersistenceAdapter] Waiting to Lock the
Store var/activemq
The server waits here indefinitely.

6. Shutdown the server1 instance and you will see the server2 instance
continue on in the startup procedures.

* When I first start the server1 instance, the directory
$org.apache.geronimo.home.dir/var/activemq is created and populated. Instead
it should be
org.apache.geronimo.home.dir/org.apache.geronimo.server.name/var/activemq
that is created and populated.
* Probably the patch should be to reference the ActiveMQ working directory as
org.apache.geronimo.server.dir/var/activemq

Summary: The ActiveMQ working directory is not referenced correctly
(was: The lock file in ActiveMQ is not referenced correctly)

The ActiveMQ working directory is not

[jira] [Created] (GERONIMO-5988) deploy:new-server-instance does not deploy a full new server instance

deploy:new-server-instance does not deploy a full new server instance
-

 Key: GERONIMO-5988
 URL: https://issues.apache.org/jira/browse/GERONIMO-5988
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: commands
Affects Versions: 3.0-M1, 3.0-M2, 3.0
 Environment: Linux x86, Red Hat Enterprise Linux Server release 5.4 
(Tikanga)
Reporter: Russell E Glaue
Priority: Minor


Regarding the G3.0 Wiki documentation:
https://cwiki.apache.org/GMOxDOC30/running-multiple-geronimo-instances.html
Creating a new server instance can be completed with gogo commands as follows:
-
...
To create an instance named foo do the following. All your instance data will 
be put in geronimo_home/foo. All the directories named below are relative to 
geronimo_home.
Follow the procedures as below:

Create a directory foo under geronimo_home.
Copy var, repository and etc directories to foo.You can use the command 
deploy:new-server-instance to help you with this step.
Edit foo/var/config/config-substitutions.properties and change the portOffset.
Try using any integers such as 1, 2, 10, 20, 30.. for various instances.
-

I interpret that the deploy:new-server-instance command should do the 
following:
1. Create a directory foo under geronimo_home.
2. Copy var to foo
3. Copy repository to foo
4. Copy etc to foo

However, in G3.0-SNAPSHOT this command only does steps 1 and 2.
I have to perform steps 3 and 4 manually.
The deploy:new-server-instance should perform all 4 steps?


To repeat the failure, perform the following:
1. Download and unpack G3.0 SNAPSHOT (3.0-20110523 tested)
2. In Geronimo shell (or using the shell deploy command) execute
-- deploy:new-server-instance foo
3. Start the new server instance
-- env GERONIMO_OPTS=-Dorg.apache.geronimo.server.name=foo bin/startup
4. The foo instance fails to startup, complaining of missing etc/ and 
repository/

In G3.0, Geronimo refuses to start until the repository and etc exist in 
org.apache.geronimo.server.dir (which is $GERONIMO_HOME/foo/ in this example).

Ultimately, I feel that the deploy:new-server-instance procedure should not do 
a straight copy, as the documentation suggests, as long as the default shipped 
var/ directory is used for a run-time server instance. We don't want to copy 
specialized configuration the user makes in that default working directory.

However, to resolve this issue immediately and easily, I do feel it should do a 
straight copy. Those of us who will manage Geronimo on an Enterprise level will 
know to keep the default shipped var/ directory as a template directory, only 
utilizing instances, and this can be documented as an advanced practice.



--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: svn commit: r1129174 - in /geronimo/server/trunk: framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ plugins/client/geronimo-client-builder/src/main/java/org/apach

This commit broke the build. See 
http://ci.apache.org/builders/geronimo-server-trunk/builds/41

Can you fix the test errors?

--kevan

On May 30, 2011, at 9:50 AM, genspr...@apache.org wrote:

 Author: genspring
 Date: Mon May 30 13:50:57 2011
 New Revision: 1129174
 
 URL: http://svn.apache.org/viewvc?rev=1129174view=rev
 Log:
 EJB31 spec EE.8.2.1 :
 A JAR format file (such as a .jar file, .war file, or .rar file) may 
 reference a
 .jar file or directory by naming the referenced .jar file or directory in a
 Class-Path header in the referencing JAR file’s Manifest file
 
 Modified:

 geronimo/server/trunk/framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ClassPathUtils.java

 geronimo/server/trunk/plugins/client/geronimo-client-builder/src/main/java/org/apache/geronimo/client/builder/AppClientModuleBuilder.java

 geronimo/server/trunk/plugins/openejb/geronimo-openejb-builder/src/main/java/org/apache/geronimo/openejb/deployment/EjbModuleBuilder.java
 
 Modified: 
 geronimo/server/trunk/framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ClassPathUtils.java
 URL: 
 http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ClassPathUtils.java?rev=1129174r1=1129173r2=1129174view=diff
 ==
 --- 
 geronimo/server/trunk/framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ClassPathUtils.java
  (original)
 +++ 
 geronimo/server/trunk/framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ClassPathUtils.java
  Mon May 30 13:50:57 2011
 @@ -136,11 +136,13 @@ public class ClassPathUtils {
 if (!targetUri.getPath().endsWith(/)) {
 targetUri = URI.create(targetUri.getPath() + /);
 }
 +
 +//1, add the directory to classpath
 +classPath.add(targetUri.getPath());
 +
 +//2, add  *.jar under the directory to classpath
 for (File file : factory.listFiles(targetUri)) {
 -if (file.isDirectory()) {
 -log.debug(Sub directory [ + 
 file.getAbsolutePath() + ] in the manifest entry directory is ignored);
 -continue;
 -}
 +
 if (!file.getName().endsWith(.jar)) {
 log.debug(Only jar files are added to classpath, 
 file [ + file.getAbsolutePath() + ] is ignored);
 continue;
 @@ -149,15 +151,6 @@ public class ClassPathUtils {
 }
 } else {
 if (!pathUri.getPath().endsWith(.jar)) {
 -if (manifestClassLoaderMode == MFCP_STRICT) {
 -problems.add(new DeploymentException(
 -Manifest class path entries must end 
 with the .jar extension (J2EE 1.4 Section 8.2): path= 
 -+ path + , module=  + 
 moduleBaseUri));
 -} else {
 -log.info(The  + manifestClassLoaderMessage +  
 processing mode is in effect.\n
 -+ Therefore, a manifest classpath entry 
 which does not end with .jar, 
 -+ pathUri +  is being permitted and 
 ignored.);
 -}
 continue;
 }
 classPath.add(targetUri.getPath());
 @@ -234,6 +227,32 @@ public class ClassPathUtils {
 }
 
 URI targetUri = moduleBaseUri.resolve(pathUri);
 +
 +try {
 +if (factory.isDirectory(targetUri)) {
 +if (!targetUri.getPath().endsWith(/)) {
 +targetUri = URI.create(targetUri.getPath() + /);
 +}
 +
 +//1, add the directory to classpath
 +addToClassPath(moduleBaseUri, resolutionUri, targetUri, 
 classpath, exclusions, factory, problems);
 +
 +//2, add  *.jar under the directory to classpath
 +for (File file : factory.listFiles(targetUri)) {
 +
 +if (!file.getName().endsWith(.jar)) {
 +log.debug(Only jar files are added to 
 classpath, file [ + file.getAbsolutePath() + ] is ignored);
 +continue;
 +}
 +addToClassPath(moduleBaseUri, resolutionUri, 
 targetUri.resolve(file.getName()), classpath, exclusions, factory, problems);
 +}
 +} else {
 +if

[BUILD] trunk: Failed for Revision: 1130268

Geronimo Revision: 1130268 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/unit-test-reports
 
 T E S T S
---
There are no tests to run.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] [bundle:bundle {execution: default-bundle}]
[INFO] [geronimo-osgi:verify-manifest {execution: verify-manifest}]
[INFO] Resolving OSGi bundle: org.apache.geronimo.framework.geronimo-obr
[INFO] OSGi bundle is resolved: org.apache.geronimo.framework.geronimo-obr
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-obr-3.0-SNAPSHOT.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-obr/target/geronimo-obr-3.0-SNAPSHOT.jar
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/framework/geronimo-obr/3.0-SNAPSHOT/geronimo-obr-3.0-SNAPSHOT.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Parsing file:/home/geronimo/.m2/repository/repository.xml
[INFO] Installing 
org/apache/geronimo/framework/geronimo-obr/3.0-SNAPSHOT/geronimo-obr-3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO] 
[INFO] Building Geronimo Framework, Modules :: Deployment
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 33 source files to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/test/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 2 source files to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports

---
 T E S T S
---
Running org.apache.geronimo.deployment.SingleFileHotDeployerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.114 sec
Running org.apache.geronimo.deployment.DeploymentContextTest
Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.037 sec  
FAILURE!

Results :

Failed tests: 
  testMainfestClassPath3(org.apache.geronimo.deployment.DeploymentContextTest)

Tests run: 13, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports
 for the individual test results.
[INFO] 
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.

Please refer to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports
 for the individual test results.
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java

Re: svn commit: r1129174 - in /geronimo/server/trunk: framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ plugins/client/geronimo-client-builder/src/main/java/org/apach

2011-06-01 Thread David Jencks

But first please explain why you think this change is correct.  It looks wrong 
to me, and I think the test was correct.  Maybe i don't understand what the 
test is doing, but I don't think libfolder/ is in the manifest classpath 
being tested but it shows up in the results.  Why should it?

thanks
david jencks

On Jun 1, 2011, at 2:02 PM, Kevan Miller wrote:

 This commit broke the build. See 
 http://ci.apache.org/builders/geronimo-server-trunk/builds/41
 
 Can you fix the test errors?
 
 --kevan
 
 On May 30, 2011, at 9:50 AM, genspr...@apache.org wrote:
 
 Author: genspring
 Date: Mon May 30 13:50:57 2011
 New Revision: 1129174
 
 URL: http://svn.apache.org/viewvc?rev=1129174view=rev
 Log:
 EJB31 spec EE.8.2.1 :
 A JAR format file (such as a .jar file, .war file, or .rar file) may 
 reference a
 .jar file or directory by naming the referenced .jar file or directory in a
 Class-Path header in the referencing JAR file’s Manifest file
 
 Modified:
   
 geronimo/server/trunk/framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ClassPathUtils.java
   
 geronimo/server/trunk/plugins/client/geronimo-client-builder/src/main/java/org/apache/geronimo/client/builder/AppClientModuleBuilder.java
   
 geronimo/server/trunk/plugins/openejb/geronimo-openejb-builder/src/main/java/org/apache/geronimo/openejb/deployment/EjbModuleBuilder.java
 
 Modified: 
 geronimo/server/trunk/framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ClassPathUtils.java
 URL: 
 http://svn.apache.org/viewvc/geronimo/server/trunk/framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ClassPathUtils.java?rev=1129174r1=1129173r2=1129174view=diff
 ==
 --- 
 geronimo/server/trunk/framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ClassPathUtils.java
  (original)
 +++ 
 geronimo/server/trunk/framework/modules/geronimo-deployment/src/main/java/org/apache/geronimo/deployment/ClassPathUtils.java
  Mon May 30 13:50:57 2011
 @@ -136,11 +136,13 @@ public class ClassPathUtils {
if (!targetUri.getPath().endsWith(/)) {
targetUri = URI.create(targetUri.getPath() + /);
}
 +
 +//1, add the directory to classpath
 +classPath.add(targetUri.getPath());
 +
 +//2, add  *.jar under the directory to classpath
for (File file : factory.listFiles(targetUri)) {
 -if (file.isDirectory()) {
 -log.debug(Sub directory [ + 
 file.getAbsolutePath() + ] in the manifest entry directory is ignored);
 -continue;
 -}
 +
if (!file.getName().endsWith(.jar)) {
log.debug(Only jar files are added to classpath, 
 file [ + file.getAbsolutePath() + ] is ignored);
continue;
 @@ -149,15 +151,6 @@ public class ClassPathUtils {
}
} else {
if (!pathUri.getPath().endsWith(.jar)) {
 -if (manifestClassLoaderMode == MFCP_STRICT) {
 -problems.add(new DeploymentException(
 -Manifest class path entries must end 
 with the .jar extension (J2EE 1.4 Section 8.2): path= 
 -+ path + , module=  + 
 moduleBaseUri));
 -} else {
 -log.info(The  + manifestClassLoaderMessage + 
  processing mode is in effect.\n
 -+ Therefore, a manifest classpath 
 entry which does not end with .jar, 
 -+ pathUri +  is being permitted and 
 ignored.);
 -}
continue;
}
classPath.add(targetUri.getPath());
 @@ -234,6 +227,32 @@ public class ClassPathUtils {
}
 
URI targetUri = moduleBaseUri.resolve(pathUri);
 +
 +try {
 +if (factory.isDirectory(targetUri)) {
 +if (!targetUri.getPath().endsWith(/)) {
 +targetUri = URI.create(targetUri.getPath() + /);
 +}
 +
 +//1, add the directory to classpath
 +addToClassPath(moduleBaseUri, resolutionUri, targetUri, 
 classpath, exclusions, factory, problems);
 +
 +//2, add  *.jar under the directory to classpath
 +for (File file : factory.listFiles(targetUri)) {
 +
 +if (!file.getName().endsWith(.jar)) {
 +log.debug(Only jar files are added to 
 classpath,

[jira] [Created] (GERONIMO-5989) CDI EAR deployment issue

2011-06-01 Thread David Blevins (JIRA)

CDI EAR deployment issue


 Key: GERONIMO-5989
 URL: https://issues.apache.org/jira/browse/GERONIMO-5989
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: deployment, javaee6
Reporter: David Blevins


Attached is one of many EAR files produced by the CDI TCK that do not deploy.  
Both the EJB and WAR modules are found and created, but only the WAR starts and 
has none of the required jars in the classpath.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Updated] (GERONIMO-5989) CDI EAR deployment issue

2011-06-01 Thread David Blevins (JIRA)


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

David Blevins updated GERONIMO-5989:


Attachment: EnterpriseQualifierDefinitionTest.ear

As of OpenEJB/OpenWebBeans/XBean r1130358, this test should pass.

 CDI EAR deployment issue
 

 Key: GERONIMO-5989
 URL: https://issues.apache.org/jira/browse/GERONIMO-5989
 Project: Geronimo
  Issue Type: Bug
  Security Level: public(Regular issues) 
  Components: deployment, javaee6
Reporter: David Blevins
  Labels: cdi, deployment, ear, ejb, tck
 Attachments: EnterpriseQualifierDefinitionTest.ear


 Attached is one of many EAR files produced by the CDI TCK that do not deploy. 
  Both the EJB and WAR modules are found and created, but only the WAR starts 
 and has none of the required jars in the classpath.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue

2011-06-01 Thread David Blevins

Made great progress in CDI/EJB integration, but seems we have a general issue 
with deploying EARs the CDI TCK gives us so we aren't seeing it yet.

It looks like the deploy is successful but the EJB module doesn't start.  No 
errors in the log other than the webapp failing to start due to missing EJB jar 
classes.

If someone could take a quick look that would be wonderful.  I've attached an 
example EAR to the JIRA.


-David

On Jun 1, 2011, at 5:16 PM, David Blevins (JIRA) wrote:

 CDI EAR deployment issue
 
 
 Key: GERONIMO-5989
 URL: https://issues.apache.org/jira/browse/GERONIMO-5989
 Project: Geronimo
  Issue Type: Bug
  Security Level: public (Regular issues)
  Components: deployment, javaee6
Reporter: David Blevins
 
 
 Attached is one of many EAR files produced by the CDI TCK that do not deploy. 
  Both the EJB and WAR modules are found and created, but only the WAR starts 
 and has none of the required jars in the classpath.
 
 --
 This message is automatically generated by JIRA.
 For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Created] (GERONIMO-5990) Output a compound WSDL file for the queries from the clients

2011-06-01 Thread Ivan (JIRA)

Output a compound WSDL file for the queries from the clients


 Key: GERONIMO-5990
 URL: https://issues.apache.org/jira/browse/GERONIMO-5990
 Project: Geronimo
  Issue Type: New Feature
  Security Level: public (Regular issues)
  Components: webservices
Affects Versions: 3.0
Reporter: Ivan
Assignee: Ivan
 Fix For: 3.0


Sometimes, if multiple SEI shares the same provided WSDL file on the server 
side, it is better to show a compound WSDL file contains all the available port 
services while the client sends the ?wsdl request for one single SEI.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue

2011-06-01 Thread Shawn Jiang

I'll take a look.

On Thu, Jun 2, 2011 at 8:27 AM, David Blevins david.blev...@gmail.comwrote:

 Made great progress in CDI/EJB integration, but seems we have a general
 issue with deploying EARs the CDI TCK gives us so we aren't seeing it yet.

 It looks like the deploy is successful but the EJB module doesn't start.
  No errors in the log other than the webapp failing to start due to missing
 EJB jar classes.

 If someone could take a quick look that would be wonderful.  I've attached
 an example EAR to the JIRA.


 -David

 On Jun 1, 2011, at 5:16 PM, David Blevins (JIRA) wrote:

  CDI EAR deployment issue
  
 
  Key: GERONIMO-5989
  URL: https://issues.apache.org/jira/browse/GERONIMO-5989
  Project: Geronimo
   Issue Type: Bug
   Security Level: public (Regular issues)
   Components: deployment, javaee6
 Reporter: David Blevins
 
 
  Attached is one of many EAR files produced by the CDI TCK that do not
 deploy.  Both the EJB and WAR modules are found and created, but only the
 WAR starts and has none of the required jars in the classpath.
 
  --
  This message is automatically generated by JIRA.
  For more information on JIRA, see:
 http://www.atlassian.com/software/jira




-- 
Shawn

Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue

2011-06-01 Thread David Blevins

Thanks, Shawn!

On Jun 1, 2011, at 7:02 PM, Shawn Jiang wrote:

 I'll take a look.
 
 On Thu, Jun 2, 2011 at 8:27 AM, David Blevins david.blev...@gmail.com wrote:
 Made great progress in CDI/EJB integration, but seems we have a general issue 
 with deploying EARs the CDI TCK gives us so we aren't seeing it yet.
 
 It looks like the deploy is successful but the EJB module doesn't start.  No 
 errors in the log other than the webapp failing to start due to missing EJB 
 jar classes.
 
 If someone could take a quick look that would be wonderful.  I've attached an 
 example EAR to the JIRA.
 
 
 -David
 
 On Jun 1, 2011, at 5:16 PM, David Blevins (JIRA) wrote:
 
  CDI EAR deployment issue
  
 
  Key: GERONIMO-5989
  URL: https://issues.apache.org/jira/browse/GERONIMO-5989
  Project: Geronimo
   Issue Type: Bug
   Security Level: public (Regular issues)
   Components: deployment, javaee6
 Reporter: David Blevins
 
 
  Attached is one of many EAR files produced by the CDI TCK that do not 
  deploy.  Both the EJB and WAR modules are found and created, but only the 
  WAR starts and has none of the required jars in the classpath.
 
  --
  This message is automatically generated by JIRA.
  For more information on JIRA, see: http://www.atlassian.com/software/jira
 
 
 
 
 -- 
 Shawn

Re: Progress on osgi-friendliness

2011-06-01 Thread Forrest Xia

On Wed, Jun 1, 2011 at 12:25 PM, David Jencks david_jen...@yahoo.comwrote:


 On May 31, 2011, at 10:47 AM, Kevan Miller wrote:

 
  On May 31, 2011, at 1:44 AM, David Jencks wrote:
 
  Locally I now have a server that runs eba-with-isolation using aries
 trunk and fixes a lot of the tck problems that showed up with this version.
  However due to a problem with aries proxies changing the SerialVersionUID
 if it is not hardcoded on every serializable class I've had to add
 SerialVersionUID to a few hundred classes across several projects.  IMO most
 of these classes shouldn't have hardcoded serialVersionUIDs because they are
 not really intended for long-term compatibility and people will update the
 classes and forget to update the SerialVersionUID.
 
  The new aries proxy code also seems to consume significantly more
 permgen space.  I didn't investigate in detail but a full server runs out of
 permgen space around half way through starting with 128 MB permgen.  My
 server started OK with 1024 MB permgen.
 
  I'd be interested to see how much more memory it's using... Do you have a
 new drop of source? In what cases will Aries be building a proxy?

 I pushed a binary and source zip onto my people.apache site.  IIUC the
 weaving code modifies every class for aop and this aop-ization is also used
 for proxies.  I could easily understand wrong.

Hi David J,

I tried to build the new source, but get a compilation error like this:

 
/home/tcker/tckdata/tckbuildsrc/djg30/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/SerializedGBeanState.java:[128,44]
cannot find symbol
 symbol : class ObjectInputStreamPA
 location: class org.apache.geronimo.kernel.config.SerializedGBeanState

I would like to trigger another execution to see the results.

Thank you!

Forrest

[BUILD] trunk: Failed for Revision: 1130367

Geronimo Revision: 1130367 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20110601/unit-test-reports
 
 T E S T S
---
There are no tests to run.

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] [bundle:bundle {execution: default-bundle}]
[INFO] [geronimo-osgi:verify-manifest {execution: verify-manifest}]
[INFO] Resolving OSGi bundle: org.apache.geronimo.framework.geronimo-obr
[INFO] OSGi bundle is resolved: org.apache.geronimo.framework.geronimo-obr
[INFO] [ianal:verify-legal-files {execution: default}]
[INFO] Checking legal files in: geronimo-obr-3.0-SNAPSHOT.jar
[INFO] [install:install {execution: default-install}]
[INFO] Installing 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-obr/target/geronimo-obr-3.0-SNAPSHOT.jar
 to 
/home/geronimo/.m2/repository/org/apache/geronimo/framework/geronimo-obr/3.0-SNAPSHOT/geronimo-obr-3.0-SNAPSHOT.jar
[INFO] [bundle:install {execution: default-install}]
[INFO] Parsing file:/home/geronimo/.m2/repository/repository.xml
[INFO] Installing 
org/apache/geronimo/framework/geronimo-obr/3.0-SNAPSHOT/geronimo-obr-3.0-SNAPSHOT.jar
[INFO] Writing OBR metadata
[INFO] 
[INFO] Building Geronimo Framework, Modules :: Deployment
[INFO]task-segment: [install]
[INFO] 
[INFO] [genesis:validate-configuration {execution: default}]
[INFO] [enforcer:enforce {execution: default}]
[INFO] [remote-resources:process {execution: default}]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/main/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/main/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 33 source files to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/test/resources
[INFO] skip non existing resourceDirectory 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/src/test/filtered-resources
[INFO] Copying 3 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Compiling 2 source files to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/test-classes
[INFO] [surefire:test {execution: default-test}]
[INFO] Surefire report directory: 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports

---
 T E S T S
---
Running org.apache.geronimo.deployment.SingleFileHotDeployerTest
Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.126 sec
Running org.apache.geronimo.deployment.DeploymentContextTest
Tests run: 7, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.037 sec  
FAILURE!

Results :

Failed tests: 
  testMainfestClassPath3(org.apache.geronimo.deployment.DeploymentContextTest)

Tests run: 13, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] There are test failures.

Please refer to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports
 for the individual test results.
[INFO] 
[INFO] Trace
org.apache.maven.BuildFailureException: There are test failures.

Please refer to 
/home/geronimo/geronimo/trunk/framework/modules/geronimo-deployment/target/surefire-reports
 for the individual test results.
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:715)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java

Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue

2011-06-01 Thread Shawn Jiang

It's quite tricky because the war and ejb module have the same name,
Hence,  they have the same hashcode because we are returning
name.hashCode()  in Module.hashCode().

r1130391  Change to moduleURI.hashCode() will fix this because the URI can
identify a module.It should be fixed, I will trigger a G JCDI tck to
see.

On Thu, Jun 2, 2011 at 10:02 AM, Shawn Jiang genspr...@gmail.com wrote:

 I'll take a look.


 On Thu, Jun 2, 2011 at 8:27 AM, David Blevins david.blev...@gmail.comwrote:

 Made great progress in CDI/EJB integration, but seems we have a general
 issue with deploying EARs the CDI TCK gives us so we aren't seeing it yet.

 It looks like the deploy is successful but the EJB module doesn't start.
  No errors in the log other than the webapp failing to start due to missing
 EJB jar classes.

 If someone could take a quick look that would be wonderful.  I've attached
 an example EAR to the JIRA.


 -David

 On Jun 1, 2011, at 5:16 PM, David Blevins (JIRA) wrote:

  CDI EAR deployment issue
  
 
  Key: GERONIMO-5989
  URL:
 https://issues.apache.org/jira/browse/GERONIMO-5989
  Project: Geronimo
   Issue Type: Bug
   Security Level: public (Regular issues)
   Components: deployment, javaee6
 Reporter: David Blevins
 
 
  Attached is one of many EAR files produced by the CDI TCK that do not
 deploy.  Both the EJB and WAR modules are found and created, but only the
 WAR starts and has none of the required jars in the classpath.
 
  --
  This message is automatically generated by JIRA.
  For more information on JIRA, see:
 http://www.atlassian.com/software/jira




 --
 Shawn




-- 
Shawn

Re: Progress on osgi-friendliness

2011-06-01 Thread David Jencks

Hi Forrest,

I've pushed today's source to people.apache.org.  It compiles for me :-)  I 
just committed an update to OWB that makes it more compatible with aries 
proxying/weaving so you may want to build owb also.

I'll probably be around on and off tonight so if you run into problems soon I 
might be able to fix them tonight.

thanks!
david jencks

On Jun 1, 2011, at 7:59 PM, Forrest Xia wrote:

 
 
 On Wed, Jun 1, 2011 at 12:25 PM, David Jencks david_jen...@yahoo.com wrote:
 
 On May 31, 2011, at 10:47 AM, Kevan Miller wrote:
 
 
  On May 31, 2011, at 1:44 AM, David Jencks wrote:
 
  Locally I now have a server that runs eba-with-isolation using aries trunk 
  and fixes a lot of the tck problems that showed up with this version.  
  However due to a problem with aries proxies changing the SerialVersionUID 
  if it is not hardcoded on every serializable class I've had to add 
  SerialVersionUID to a few hundred classes across several projects.  IMO 
  most of these classes shouldn't have hardcoded serialVersionUIDs because 
  they are not really intended for long-term compatibility and people will 
  update the classes and forget to update the SerialVersionUID.
 
  The new aries proxy code also seems to consume significantly more permgen 
  space.  I didn't investigate in detail but a full server runs out of 
  permgen space around half way through starting with 128 MB permgen.  My 
  server started OK with 1024 MB permgen.
 
  I'd be interested to see how much more memory it's using... Do you have a 
  new drop of source? In what cases will Aries be building a proxy?
 
 I pushed a binary and source zip onto my people.apache site.  IIUC the 
 weaving code modifies every class for aop and this aop-ization is also used 
 for proxies.  I could easily understand wrong.
 Hi David J,
 
 I tried to build the new source, but get a compilation error like this:
 
  
 /home/tcker/tckdata/tckbuildsrc/djg30/framework/modules/geronimo-kernel/src/main/java/org/apache/geronimo/kernel/config/SerializedGBeanState.java:[128,44]
  cannot find symbol
  symbol : class ObjectInputStreamPA
  location: class org.apache.geronimo.kernel.config.SerializedGBeanState 
 
 I would like to trigger another execution to see the results. 
 
 Thank you!
 
 Forrest

Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue


On Jun 1, 2011, at 11:14 PM, Shawn Jiang wrote:

 It's quite tricky because the war and ejb module have the same name,  Hence,  
 they have the same hashcode because we are returning name.hashCode()  in 
 Module.hashCode().
 
 r1130391  Change to moduleURI.hashCode() will fix this because the URI can 
 identify a module.It should be fixed, I will trigger a G JCDI tck to see.

Interesting. So, is this the error you were getting?

org.testng.TestNGException: 
Cannot find class in classpath: 
org.jboss.jsr299.tck.tests.definition.qualifier.enterprise.EnterpriseQualifierDefinitionTest
org.testng.xml.XmlClass.getSupportClass(XmlClass.java:55)
org.testng.internal.Utils.xmlClassesToClasses(Utils.java:79)
org.testng.TestRunner.initMethods(TestRunner.java:289)
org.testng.TestRunner.init(TestRunner.java:235)
org.testng.TestRunner.init(TestRunner.java:197)
org.testng.TestRunner.init(TestRunner.java:141)

org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:488)
org.testng.SuiteRunner.privateRun(SuiteRunner.java:250)
org.testng.SuiteRunner.run(SuiteRunner.java:204)
org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:912)
org.testng.TestNG.runSuitesLocally(TestNG.java:876)
org.testng.TestNG.run(TestNG.java:784)
org.jboss.testharness.impl.runner.TestRunner.run(TestRunner.java:61)

org.jboss.testharness.impl.runner.servlet.ServletTestRunner.doGet(ServletTestRunner.java:77)
javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
javax.servlet.http.HttpServlet.service(HttpServlet.java:668)

Can someone refresh my memory as to *why* a class in 
org.jboss.jsr299.tck.tests.definition.qualifier.enterprise.EnterpriseQualifierDefinitionTest.jar
 should be visible, in this app?

--kevan

Re: [jira] [Created] (GERONIMO-5989) CDI EAR deployment issue

2011-06-01 Thread Shawn Jiang

The spec EE 8.3.1 does not specify if the classes in EJB module should be
visible for WAR.  But the spec does say app should not depend on such EJB
and WEB module classloading relationship.   I think the case is breaking the
rule.

Anyway,  in geronimo impl,  the content of ejb is visible to war so that we
are fine with the case reqirement.

On Thu, Jun 2, 2011 at 11:38 AM, Kevan Miller kevan.mil...@gmail.comwrote:


 On Jun 1, 2011, at 11:14 PM, Shawn Jiang wrote:

  It's quite tricky because the war and ejb module have the same name,
  Hence,  they have the same hashcode because we are returning
 name.hashCode()  in Module.hashCode().
 
  r1130391  Change to moduleURI.hashCode() will fix this because the URI
 can identify a module.It should be fixed, I will trigger a G JCDI tck to
 see.

 Interesting. So, is this the error you were getting?

 org.testng.TestNGException:
 Cannot find class in classpath:
 org.jboss.jsr299.tck.tests.definition.qualifier.enterprise.EnterpriseQualifierDefinitionTest
org.testng.xml.XmlClass.getSupportClass(XmlClass.java:55)
org.testng.internal.Utils.xmlClassesToClasses(Utils.java:79)
org.testng.TestRunner.initMethods(TestRunner.java:289)
org.testng.TestRunner.init(TestRunner.java:235)
org.testng.TestRunner.init(TestRunner.java:197)
org.testng.TestRunner.init(TestRunner.java:141)

  
 org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:488)
org.testng.SuiteRunner.privateRun(SuiteRunner.java:250)
org.testng.SuiteRunner.run(SuiteRunner.java:204)
org.testng.TestNG.createAndRunSuiteRunners(TestNG.java:912)
org.testng.TestNG.runSuitesLocally(TestNG.java:876)
org.testng.TestNG.run(TestNG.java:784)
org.jboss.testharness.impl.runner.TestRunner.run(TestRunner.java:61)

  
 org.jboss.testharness.impl.runner.servlet.ServletTestRunner.doGet(ServletTestRunner.java:77)
javax.servlet.http.HttpServlet.service(HttpServlet.java:575)
javax.servlet.http.HttpServlet.service(HttpServlet.java:668)

 Can someone refresh my memory as to *why* a class in
 org.jboss.jsr299.tck.tests.definition.qualifier.enterprise.EnterpriseQualifierDefinitionTest.jar
 should be visible, in this app?

 --kevan




-- 
Shawn

[BUILD] branches/2.1: Failed for Revision: 1130409

Geronimo Revision: 1130409 built with tests included
 
See the full build-0200.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20110602/build-0200.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20110602/unit-test-reports
 

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.2/maven-install-plugin-2.2.pom

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-plugins/8/maven-plugins-8.pom

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.2/maven-install-plugin-2.2.jar

Downloading: 
http://repo2.maven.org/maven2/org/apache/geronimo/genesis/genesis-maven-plugin/2.0/genesis-maven-plugin-2.0.pom

Downloading: 
http://repo2.maven.org/maven2/org/apache/geronimo/genesis/genesis-maven-plugin/2.0/genesis-maven-plugin-2.0.jar

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.0.2/maven-compiler-plugin-2.0.2.pom

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-compiler-plugin/2.0.2/maven-compiler-plugin-2.0.2.jar

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-enforcer-plugin/1.0-beta-1/maven-enforcer-plugin-1.0-beta-1.pom

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/enforcer/enforcer/1.0-beta-1/enforcer-1.0-beta-1.pom

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-enforcer-plugin/1.0-beta-1/maven-enforcer-plugin-1.0-beta-1.jar

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.0/maven-remote-resources-plugin-1.0.pom

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-plugins/10/maven-plugins-10.pom

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-remote-resources-plugin/1.0/maven-remote-resources-plugin-1.0.jar

Downloading: 
http://repo2.maven.org/maven2/org/codehaus/mojo/ianal-maven-plugin/1.0-alpha-1/ianal-maven-plugin-1.0-alpha-1.pom

Downloading: http://repo2.maven.org/maven2/org/codehaus/mojo/mojo/15/mojo-15.pom

Downloading: 
http://repo2.maven.org/maven2/org/codehaus/mojo/ianal-maven-plugin/1.0-alpha-1/ianal-maven-plugin-1.0-alpha-1.jar

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-javadoc-plugin/2.5/maven-javadoc-plugin-2.5.pom

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-plugins/11/maven-plugins-11.pom

Downloading: 
http://repo2.maven.org/maven2/org/apache/maven/plugins/maven-javadoc-plugin/2.5/maven-javadoc-plugin-2.5.jar

[INFO] 
[ERROR] BUILD ERROR
[INFO] 
[INFO] Internal error in the plugin manager getting plugin 
'org.apache.maven.plugins:maven-javadoc-plugin': Failed to create plugin 
container for plugin 'Plugin [org.apache.maven.plugins:maven-javadoc-plugin]': 
Error starting container
expected  to end empty tag not 1 (position: TEXT seen ...ionSpecifies the 
HTML character set for this document   con2se/1... @3882:86) 
[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the 
plugin manager getting plugin 'org.apache.maven.plugins:maven-javadoc-plugin': 
Failed to create plugin container for plugin 'Plugin 
[org.apache.maven.plugins:maven-javadoc-plugin]': Error starting container
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1544)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1503)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1282)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:534)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at

Re: Progress on osgi-friendliness