Re: [VOTE] Release geronimo-jpa_2.0_spec-1.0-PFD2 and geronimo-valdiation_1.0_spec-1.0-CR5 for OpenJPA

[Donald Woods]

My +1.  Passed rat and ianal checks.


-Donald

Donald Woods wrote:
The OpenJPA project will be releasing a 2.0.0-M3 release next week and 
needs tagged versions of the JPA2 and Bean Validation spec APIs.


This vote is for the following TWO releases, which are based on early 
drafts of the specs, which we are now allowed to release.


geronimo-jpa_2.0_spec-1.0-PFD2
source:https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-jpa_2.0_spec-1.0-PFD2 

artifacts:https://repository.apache.org/content/repositories/geronimo-staging-015/ 



geronimo-validation_1.0_spec-1.0-CR5
source:https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-validation_1.0_spec-1.0-CR5 

artifacts:https://repository.apache.org/content/repositories/geronimo-staging-015/ 



Both of the above passed rat:check and the ianal plugin.

The branches will be moved to tags and the staging artifacts promoted to 
the release repo if the vote passes.



Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1 (and reason why)


Thanks,
Donald

[BUILD] trunk: Failed for Revision: 820502

[gawor]

Geronimo Revision: 820502 built with tests included
 
See the full build-2100.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090930/build-2100.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090930/unit-test-reports
 

The system is out of resources.
Consult the following stack trace for details.
java.lang.OutOfMemoryError
at com.sun.tools.javac.zip.ZipFileIndex.readBytes(ZipFileIndex.java:569)
at com.sun.tools.javac.zip.ZipFileIndex.read(ZipFileIndex.java:523)
at 
com.sun.tools.javac.util.DefaultFileManager$ZipFileIndexFileObject.read(DefaultFileManager.java:1641)
at 
com.sun.tools.javac.util.DefaultFileManager$ZipFileIndexFileObject.openInputStream(DefaultFileManager.java:1561)
at com.sun.tools.javac.jvm.ClassReader.fillIn(ClassReader.java:1856)
at com.sun.tools.javac.jvm.ClassReader.complete(ClassReader.java:1789)
at com.sun.tools.javac.code.Symbol.complete(Symbol.java:398)
at com.sun.tools.javac.code.Symbol$ClassSymbol.complete(Symbol.java:770)
at com.sun.tools.javac.code.Symbol$ClassSymbol.flags(Symbol.java:702)
at com.sun.tools.javac.code.Types$14.visitClassType(Types.java:1305)
at com.sun.tools.javac.code.Types$14.visitClassType(Types.java:1288)
at com.sun.tools.javac.code.Type$ClassType.accept(Type.java:566)
at 
com.sun.tools.javac.code.Types$DefaultTypeVisitor.visit(Types.java:3173)
at com.sun.tools.javac.code.Types.asSuper(Types.java:1285)
at com.sun.tools.javac.code.Types$14.visitClassType(Types.java:1301)
at com.sun.tools.javac.code.Types$14.visitClassType(Types.java:1288)
at com.sun.tools.javac.code.Type$ClassType.accept(Type.java:566)
at 
com.sun.tools.javac.code.Types$DefaultTypeVisitor.visit(Types.java:3173)
at com.sun.tools.javac.code.Types.asSuper(Types.java:1285)
at com.sun.tools.javac.code.Types.unboxedType(Types.java:2713)
at com.sun.tools.javac.comp.Attr.condType1(Attr.java:968)
at com.sun.tools.javac.comp.Attr.condType(Attr.java:939)
at com.sun.tools.javac.comp.Attr.visitConditional(Attr.java:920)
at 
com.sun.tools.javac.tree.JCTree$JCConditional.accept(JCTree.java:1033)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:372)
at com.sun.tools.javac.comp.Attr.attribExpr(Attr.java:389)
at com.sun.tools.javac.comp.Attr.visitVarDef(Attr.java:695)
at 
com.sun.tools.javac.tree.JCTree$JCVariableDecl.accept(JCTree.java:703)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:372)
at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:409)
at com.sun.tools.javac.comp.Attr.attribStats(Attr.java:425)
at com.sun.tools.javac.comp.Attr.visitBlock(Attr.java:727)
at com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:751)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:372)
at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:409)
at com.sun.tools.javac.comp.Attr.visitForLoop(Attr.java:752)
at com.sun.tools.javac.tree.JCTree$JCForLoop.accept(JCTree.java:830)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:372)
at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:409)
at com.sun.tools.javac.comp.Attr.attribStats(Attr.java:425)
at com.sun.tools.javac.comp.Attr.visitBlock(Attr.java:727)
at com.sun.tools.javac.tree.JCTree$JCBlock.accept(JCTree.java:751)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:372)
at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:409)
at com.sun.tools.javac.comp.Attr.visitMethodDef(Attr.java:646)
at com.sun.tools.javac.tree.JCTree$JCMethodDecl.accept(JCTree.java:651)
at com.sun.tools.javac.comp.Attr.attribTree(Attr.java:372)
at com.sun.tools.javac.comp.Attr.attribStat(Attr.java:409)
at com.sun.tools.javac.comp.Attr.attribClassBody(Attr.java:2709)
at com.sun.tools.javac.comp.Attr.attribClass(Attr.java:2640)
at com.sun.tools.javac.comp.Attr.attribClass(Attr.java:2576)
at 
com.sun.tools.javac.main.JavaCompiler.attribute(JavaCompiler.java:1048)
at com.sun.tools.javac.main.JavaCompiler.compile2(JavaCompiler.java:777)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:742)
at com.sun.tools.javac.main.Main.compile(Main.java:365)
at com.sun.tools.javac.main.Main.compile(Main.java:291)
at com.sun.tools.javac.main.Main.compile(Main.java:282)
at com.sun.tools.javac.Main.compile(Main.java:99)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
at java.lang.reflect.Method.invoke(Method.java

[BUILD] branches/2.2: Failed for Revision: 820499

[gawor]

Geronimo Revision: 820499 built with tests included
 
See the full build-2000.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090930/build-2000.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090930/unit-test-reports
 
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar: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.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -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.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3-SNAPSHOT
3) org.apache.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar: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.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -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.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3-SNAPSHOT
3) org.apache.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar: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)
at

[DISCUSS] Release geronimo-jpa_2.0_spec-1.0-PFD2 and geronimo-valdiation_1.0_spec-1.0-CR5 for OpenJPA

[Donald Woods]

Discussion thread for the vote


-Donald

[VOTE] Release geronimo-jpa_2.0_spec-1.0-PFD2 and geronimo-valdiation_1.0_spec-1.0-CR5 for OpenJPA

[Donald Woods]

The OpenJPA project will be releasing a 2.0.0-M3 release next week and 
needs tagged versions of the JPA2 and Bean Validation spec APIs.


This vote is for the following TWO releases, which are based on early 
drafts of the specs, which we are now allowed to release.


geronimo-jpa_2.0_spec-1.0-PFD2
source:https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-jpa_2.0_spec-1.0-PFD2
artifacts:https://repository.apache.org/content/repositories/geronimo-staging-015/

geronimo-validation_1.0_spec-1.0-CR5
source:https://svn.apache.org/repos/asf/geronimo/specs/branches/geronimo-validation_1.0_spec-1.0-CR5
artifacts:https://repository.apache.org/content/repositories/geronimo-staging-015/

Both of the above passed rat:check and the ianal plugin.

The branches will be moved to tags and the staging artifacts promoted to 
the release repo if the vote passes.



Vote open for 72 hours.

[ ] +1
[ ] +0
[ ] -1 (and reason why)


Thanks,
Donald

Re: put XSD schemas on G web

[Kevan Miller]

On Sep 30, 2009, at 10:03 AM, Radim Kolar wrote:





Ellen Tang-2 wrote:


Ellen,

I can't open the URL in your email:

http://geronimo.apache.org/xsd/geonimo-module-1.2.xsd


Is there any typo in there?



There is no typo, but these XSD files are not at that URL yet. My  
message
was proposal for Geronimo web space change, because it will help  
people with
validating XML editors to write deployement plans. I dont have  
access rights

to upload XSD files at that location.


Hi Radim,
Does http://geronimo.apache.org/xml/ns/ meet your needs? For example,  
geronimo-module-1.2.xsd can be found here:


http://geronimo.apache.org/xml/ns/deployment-1.2

--kevan

[BUILD] trunk: Failed for Revision: 820389

[gawor]

Geronimo Revision: 820389 built with tests included
 
See the full build-1500.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090930/build-1500.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090930/unit-test-reports
 

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2),
  amq-protobuf-staging 
(https://repository.apache.org/content/repositories/releases/),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-030/)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.activemq:activemq-core:jar:5.3.0

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -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.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3.0

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2),
  amq-protobuf-staging 
(https://repository.apache.org/content/repositories/releases/),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-030/)


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:597)
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.activemq:activemq-core:jar:5.3.0

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -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.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3.0

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2),
  amq-protobuf-staging 
(https://repository.apache.org/content/repositories/releases/),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-030/)


at

[BUILD] branches/2.2: Failed for Revision: 820365

[gawor]

Geronimo Revision: 820365 built with tests included
 
See the full build-1400.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090930/build-1400.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090930/unit-test-reports
 
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar: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.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -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.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3-SNAPSHOT
3) org.apache.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar: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.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -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.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3-SNAPSHOT
3) org.apache.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar: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)
at

Re: OSGI progress

[David Jencks]

On Sep 30, 2009, at 10:47 AM, Rick McGuire wrote:

I've been looking into how to create an RFC 66 implementation that  
can deploy to whatever the Geronimo-hosted web container happens to  
be.  One issue that seems to keep popping up is crossing the bridge  
between GBeans and OSGi.  A lot (ok, all really) that deal with the  
server runtime and configuration are GBean instances.  Some of these  
GBeans will occasionally need a BundleContext to perform OSGi  
operations.  It would appear that we'd need to have an mechanism to  
allow a GBean to be injected with a Bundle and/or BundleContext for  
its hosting configuration.


That's implemented and appears to be working in my osgi sandbox.  One  
of the tasks I envision once the g. framework actually boots up inside  
karaf is converting all the gbeans that use the magic classloader  
attribute to use bundle context instead.


Currently I'm fighting with a classcast exception deep in plexus that  
I managed to avoid a couple weeks ago but its popped up again.  There  
are a lot of jars that need to be bundleized and a bunch of problems  
in the servicemix bundleizations I may be making some progress  
however.


thanks
david jencks


Rick

David Jencks wrote:


On Sep 22, 2009, at 10:50 PM, Ivan wrote:

After reading some code changes of the geronimo-kenel in the  
sanbox, I found that we keep the Geronimo kenel as an OSGI  
service, and each Configuration ( or a bundle) will search it and  
start the configuration as we do in the past while starting.


There's a difference in lifecycles between osgi bundles and  
geronimo configurations.


OSGI:
bundles can be installed, in which case the classes are not  
available, or started, in which case the classes are all available  
and the bundle activator has been started.  AFAICT there is no  
other built in "no-really-start-it" state beyond "started".  There  
might be more less-started states I'm not aware of.


Geronimo:
A Configuration is a gbean.  You can't get much usefaul data out of  
it until its started.  Once it is started the classes are available  
and you can find out what services (gbeans) are in the  
configuration and look at their attributes.  There's a further  
state of "all gbeans started".  The configuration manager treats  
these states as "loaded" and "started"


So far it seems to work to do something similar in the osgi  
environment but it doesn't really fit very well yet.  I'm not sure  
where we will end up with this.



I have a feeling that, if we do that, Geronimo is still a part of  
OSGI env, could we make the Geronimo is an OSGI env?


I don't understand what you are asking here.  In the sandbox,  
geronimo plugins are running in an osgi enviroment, and all the  
classes are loaded from osgi bundles.  Could you explain more what  
you are asking about?


Could we publish GBeans as OSGI service via a  
ConfigurationActivator, or though a GBean-OSGI adapter ?


I'm pretty sure we could, but I'd like to get more stuff working  
before we decide if its a good idea.  IIUC blueprint doesn't  
publish every blueprint bean as an osgi service, but only ones you  
configure to be published.  I suspect we may want to, similarly,  
only publish some gbeans as osgi services.


My current approach is to try to modify the existing geronimo  
architecture relatively little where possible to get it to run in  
osgi, respecting osgi architecture.  So, I am trying to get stuff  
working with the kernel as an osgi service, get the deployers  
working, etc etc.  I think after we have done this we will have a  
much better idea what other work we want to try.  For instance, we  
might not need a kernel at all: possibly gbeans can just be osgi  
services with  a few extra attributes.


thanks
david jencks



Thanks !

2009/9/22 Rex Wang mailto:rwo...@gmail.com>>

   Yes! hope for detail sharing :-)
   -Rex

   2009/9/22 Jack Cai mailto:greensi...@gmail.com>>

   David, that's exciting work!

   It'll be great if you can share some more details. There are
   a few puzzles that flow around my mind -
* Are we just taking OSGi framework in as another plug-in to
   let it host OSGi applications? Or, vice-versa, we are
   converting Geronimo into an OSGi application?
* If the latter case, will GBean go away?
* If yes, how much code changes are required? I'd say a  
lot ...


   -Jack


   On Tue, Sep 22, 2009 at 8:25 AM, David Jencks
   mailto:david_jen...@yahoo.com>>  
wrote:


   Over the weekend I got my sandbox osgi framework to build
   and generate all the plugins as osgi bundles.  This
   involves running some of the geronimo server on
   osgi/felix inside maven.  The dependency management
   system seems to work OK at least for starting bundles.  I
   also started doing a little bit of code cleanup.

   I think the next step will be to get the framework server
   running in

Re: OSGI progress

[Jarek Gawor]

I was just looking at David's framework code and it looks like there
is already a way to inject a bundle or bundleContext into a gbean. It
works just like injecting the kernel or classLoader attributes. I'm
just looking at the code at this point so I don't really know if it
works right or not.

Jarek

On Wed, Sep 30, 2009 at 1:47 PM, Rick McGuire  wrote:
> I've been looking into how to create an RFC 66 implementation that can
> deploy to whatever the Geronimo-hosted web container happens to be.  One
> issue that seems to keep popping up is crossing the bridge between GBeans
> and OSGi.  A lot (ok, all really) that deal with the server runtime and
> configuration are GBean instances.  Some of these GBeans will occasionally
> need a BundleContext to perform OSGi operations.  It would appear that we'd
> need to have an mechanism to allow a GBean to be injected with a Bundle
> and/or BundleContext for its hosting configuration.
> Rick
>

Re: OSGI progress

[Rick McGuire]

I've been looking into how to create an RFC 66 implementation that can 
deploy to whatever the Geronimo-hosted web container happens to be.  One 
issue that seems to keep popping up is crossing the bridge between 
GBeans and OSGi.  A lot (ok, all really) that deal with the server 
runtime and configuration are GBean instances.  Some of these GBeans 
will occasionally need a BundleContext to perform OSGi operations.  It 
would appear that we'd need to have an mechanism to allow a GBean to be 
injected with a Bundle and/or BundleContext for its hosting configuration. 


Rick

David Jencks wrote:


On Sep 22, 2009, at 10:50 PM, Ivan wrote:

After reading some code changes of the geronimo-kenel in the sanbox, 
I found that we keep the Geronimo kenel as an OSGI service, and each 
Configuration ( or a bundle) will search it and start the 
configuration as we do in the past while starting. 


There's a difference in lifecycles between osgi bundles and geronimo 
configurations.


OSGI:
bundles can be installed, in which case the classes are not available, 
or started, in which case the classes are all available and the bundle 
activator has been started.  AFAICT there is no other built in 
"no-really-start-it" state beyond "started".  There might be more 
less-started states I'm not aware of.


Geronimo:
A Configuration is a gbean.  You can't get much usefaul data out of it 
until its started.  Once it is started the classes are available and 
you can find out what services (gbeans) are in the configuration and 
look at their attributes.  There's a further state of "all gbeans 
started".  The configuration manager treats these states as "loaded" 
and "started"


So far it seems to work to do something similar in the osgi 
environment but it doesn't really fit very well yet.  I'm not sure 
where we will end up with this.



I have a feeling that, if we do that, Geronimo is still a part of 
OSGI env, could we make the Geronimo is an OSGI env?


I don't understand what you are asking here.  In the sandbox, geronimo 
plugins are running in an osgi enviroment, and all the classes are 
loaded from osgi bundles.  Could you explain more what you are asking 
about?


Could we publish GBeans as OSGI service via a ConfigurationActivator, 
or though a GBean-OSGI adapter ?


I'm pretty sure we could, but I'd like to get more stuff working 
before we decide if its a good idea.  IIUC blueprint doesn't publish 
every blueprint bean as an osgi service, but only ones you configure 
to be published.  I suspect we may want to, similarly, only publish 
some gbeans as osgi services.


My current approach is to try to modify the existing geronimo 
architecture relatively little where possible to get it to run in 
osgi, respecting osgi architecture.  So, I am trying to get stuff 
working with the kernel as an osgi service, get the deployers working, 
etc etc.  I think after we have done this we will have a much better 
idea what other work we want to try.  For instance, we might not need 
a kernel at all: possibly gbeans can just be osgi services with  a few 
extra attributes.


thanks
david jencks



Thanks !

2009/9/22 Rex Wang mailto:rwo...@gmail.com>>

Yes! hope for detail sharing :-)
-Rex

2009/9/22 Jack Cai mailto:greensi...@gmail.com>>

David, that's exciting work!

It'll be great if you can share some more details. There are
a few puzzles that flow around my mind -
 * Are we just taking OSGi framework in as another plug-in to
let it host OSGi applications? Or, vice-versa, we are
converting Geronimo into an OSGi application? 


 * If the latter case, will GBean go away?
 * If yes, how much code changes are required? I'd say a lot ...

-Jack


On Tue, Sep 22, 2009 at 8:25 AM, David Jencks
mailto:david_jen...@yahoo.com>> wrote:

Over the weekend I got my sandbox osgi framework to build
and generate all the plugins as osgi bundles.  This
involves running some of the geronimo server on
osgi/felix inside maven.  The dependency management
system seems to work OK at least for starting bundles.  I
also started doing a little bit of code cleanup.

I think the next step will be to get the framework server
running in standalone karaf or felix.  Hopefully this
will be no harder than getting it running in embedded
felix in maven.

thanks
david jencks






--
Ivan

Re: Wiki link to current version page

[Juergen Weber]

Fixing the links doesn't seem to be the general solution,
e.g. with
geronimo ra.xml and "I'm feeling lucky" you get the 1.1 docs, even if google
knows the 2.1 docs.
There should be a friendly big red box on old pages "There exists a more
recent version of this page" with a link to it.

Greetings, Juergen


Ellen Tang-2 wrote:
> 
> I've tried to find the page of the same topic (Daytrader) in documentation
> v2.1 by changing the link directly from
> http://cwiki.apache.org/GMOxDOC20/daytrader.html to
> http://cwiki.apache.org/GMOxDOC21/daytrader.html . The page does open and
> has correct contents, but when I tried to find the link of the same topic
> in
> the table of contents of v2.1 documentation (
> http://cwiki.apache.org/GMOxDOC21/documentation.html ), I couldn't find
> the
> link for the "Daytrader" page, which does exist.
> 
> I guess that this is why the google search can't find the page of
> "Daytrader" in Geronimo v2.1 documentation.
> 
> Jeff, maybe you can have a check for this to see if you get the same
> result
> as me.
> 
> Thanks!
> 
> Ellen
> 
> 2009/9/30 chi runhua 
> 
>> I think it's the problem of the template in auto-export plugin,  but only
>> confluence admin could do some configuration to update the template.
>>
>> Jeff C
>>
>> On Wed, Sep 30, 2009 at 10:12 AM, Ellen Tang
>> wrote:
>>
>>> Hi Juergen,
>>>
>>> I guess that could be a good thing to do. We'll discuss about that to
>>> see
>>> if it's possible and necessary to do that.
>>>
>>> Thank you for your idea!
>>>
>>> Best regards,
>>>
>>> Ellen
>>>
>>> 2009/9/28 Juergen Weber 
>>>
>>>
 Hi,

 googling often leads to an old version of a Geronimo wiki page.
 e.g. google daytrader apache goes to
 http://cwiki.apache.org/GMOxDOC20/daytrader.html

 Can you somehow make the wiki automatically display links to the most
 recent
 version?

 Thanks,
 Juergen
 --
 View this message in context:
 http://www.nabble.com/Wiki-link-to-current-version-page-tp25645167s134p25645167.html
 Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.


>>>
>>
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Wiki-link-to-current-version-page-tp25645167s134p25685083.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.

Re: Wiki link to current version page

[Ellen Tang]

I've tried to find the page of the same topic (Daytrader) in documentation
v2.1 by changing the link directly from
http://cwiki.apache.org/GMOxDOC20/daytrader.html to
http://cwiki.apache.org/GMOxDOC21/daytrader.html . The page does open and
has correct contents, but when I tried to find the link of the same topic in
the table of contents of v2.1 documentation (
http://cwiki.apache.org/GMOxDOC21/documentation.html ), I couldn't find the
link for the "Daytrader" page, which does exist.

I guess that this is why the google search can't find the page of
"Daytrader" in Geronimo v2.1 documentation.

Jeff, maybe you can have a check for this to see if you get the same result
as me.

Thanks!

Ellen

2009/9/30 chi runhua 

> I think it's the problem of the template in auto-export plugin,  but only
> confluence admin could do some configuration to update the template.
>
> Jeff C
>
> On Wed, Sep 30, 2009 at 10:12 AM, Ellen Tang wrote:
>
>> Hi Juergen,
>>
>> I guess that could be a good thing to do. We'll discuss about that to see
>> if it's possible and necessary to do that.
>>
>> Thank you for your idea!
>>
>> Best regards,
>>
>> Ellen
>>
>> 2009/9/28 Juergen Weber 
>>
>>
>>> Hi,
>>>
>>> googling often leads to an old version of a Geronimo wiki page.
>>> e.g. google daytrader apache goes to
>>> http://cwiki.apache.org/GMOxDOC20/daytrader.html
>>>
>>> Can you somehow make the wiki automatically display links to the most
>>> recent
>>> version?
>>>
>>> Thanks,
>>> Juergen
>>> --
>>> View this message in context:
>>> http://www.nabble.com/Wiki-link-to-current-version-page-tp25645167s134p25645167.html
>>> Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
>>>
>>>
>>
>

Re: Wiki link to current version page

[chi runhua]

I think it's the problem of the template in auto-export plugin,  but only
confluence admin could do some configuration to update the template.

Jeff C

On Wed, Sep 30, 2009 at 10:12 AM, Ellen Tang  wrote:

> Hi Juergen,
>
> I guess that could be a good thing to do. We'll discuss about that to see
> if it's possible and necessary to do that.
>
> Thank you for your idea!
>
> Best regards,
>
> Ellen
>
> 2009/9/28 Juergen Weber 
>
>
>> Hi,
>>
>> googling often leads to an old version of a Geronimo wiki page.
>> e.g. google daytrader apache goes to
>> http://cwiki.apache.org/GMOxDOC20/daytrader.html
>>
>> Can you somehow make the wiki automatically display links to the most
>> recent
>> version?
>>
>> Thanks,
>> Juergen
>> --
>> View this message in context:
>> http://www.nabble.com/Wiki-link-to-current-version-page-tp25645167s134p25645167.html
>> Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
>>
>>
>

Re: put XSD schemas on G web

[Radim Kolar]

Ellen Tang-2 wrote:
> 
> Ellen,
> 
> I can't open the URL in your email:
> 
> http://geronimo.apache.org/xsd/geonimo-module-1.2.xsd
> 
> Is there any typo in there?
> 

There is no typo, but these XSD files are not at that URL yet. My message
was proposal for Geronimo web space change, because it will help people with
validating XML editors to write deployement plans. I dont have access rights
to upload XSD files at that location.
-- 
View this message in context: 
http://www.nabble.com/There%27s-still-hope-for-2.2...-tp25395776s134p25681686.html
Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.

[BUILD] trunk: Failed for Revision: 820258

[gawor]

Geronimo Revision: 820258 built with tests included
 
See the full build-0900.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090930/build-0900.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090930/unit-test-reports
 

from the specified remote repositories:
  amq-protobuf-staging 
(https://repository.apache.org/content/repositories/releases/),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-030/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.activemq:activemq-core:jar:5.3.0

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -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.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3.0

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT

from the specified remote repositories:
  amq-protobuf-staging 
(https://repository.apache.org/content/repositories/releases/),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-030/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  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:37)
at java.lang.reflect.Method.invoke(Method.java:599)
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.activemq:activemq-core:jar:5.3.0

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -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.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3.0

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT

from the specified remote repositories:
  amq-protobuf-staging 
(https://repository.apache.org/content/repositories/releases/),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-030/),
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  ibiblio.org (http://repo.exist.com/maven2),
  apache.snapshots (http://repository.apache.org/snapshots)


at

Re: put XSD schemas on G web

[chi runhua]

Hi  Radim,

You may find XSD files under /schema directory. I didn't look
into the code to find out whether schema validation was done against local
.xsd files.

I am not sure if it's necessary to put these schema files in text/xml format
on G website if validation happens on local.

Hope someone with more experiences in G development could answer the
question.

When you are developing applications in Eclipse, I'd like to recommend GEP
cause it could help you with development of deployment plans, especially
using its Geronimo Plan Editor and wizards.

Thanks.

Jeff C



> 2009/9/25 Radim Kolar 
>
>
>> These diagrams drawn from XSD are very nice. I recommend to put plain XSD
>> files in text/xml format on G web similar how maven have it. Desired URL
>> will look like:
>>
>> http://geronimo.apache.org/xsd/geronimo-module-1.2.xsd
>>
>> we can then start using this URL in xsi:schemaLocation so XML editors can
>> check syntax during typing deployement plans and then update deployment
>> examples to let people know about it.
>> --
>> View this message in context:
>> http://www.nabble.com/There%27s-still-hope-for-2.2...-tp25395776s134p25610559.html
>> Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
>>
>>
>

Re: Upgrade to activemq-protobuf version 1.0?

[Jason Warner]

Ah, ok.  Thanks for catching that.  That'll teach me to look at things on a
wednesday morning.

~Jason Warner


On Wed, Sep 30, 2009 at 9:38 AM, Ivan  wrote:

> From the stack, it seems that activemq-core 5.3-snapshot depends on
> activemq-protobuf 1.0-snapshot, not Geronimo depends on it directly.
> One way is to wait the activemq 5.3, or use the exclude in our pom file to
> use 1.0 temporarily ?
>
> 2009/9/30 Jason Warner 
>
>> It looks like all our builds are reliant upon activemq-protobuf version
>> 1.0-Snapshot.  Activemq released version 1.0 of activemq-protobuf last
>> week.  Should we be upgrading?  That should fix the build failures we've
>> been having.
>>
>> ~Jason Warner
>>
>
>
>
> --
> Ivan
>

Re: Upgrade to activemq-protobuf version 1.0?

[Ivan]

>From the stack, it seems that activemq-core 5.3-snapshot depends on
activemq-protobuf 1.0-snapshot, not Geronimo depends on it directly.
One way is to wait the activemq 5.3, or use the exclude in our pom file to
use 1.0 temporarily ?

2009/9/30 Jason Warner 

> It looks like all our builds are reliant upon activemq-protobuf version
> 1.0-Snapshot.  Activemq released version 1.0 of activemq-protobuf last
> week.  Should we be upgrading?  That should fix the build failures we've
> been having.
>
> ~Jason Warner
>



-- 
Ivan

Upgrade to activemq-protobuf version 1.0?

[Jason Warner]

It looks like all our builds are reliant upon activemq-protobuf version
1.0-Snapshot.  Activemq released version 1.0 of activemq-protobuf last
week.  Should we be upgrading?  That should fix the build failures we've
been having.

~Jason Warner

[BUILD] branches/2.2: Failed for Revision: 820252

[gawor]

Geronimo Revision: 820252 built with tests included
 
See the full build-0800.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090930/build-0800.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/2.2/20090930/unit-test-reports
 
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar: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.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -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.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3-SNAPSHOT
3) org.apache.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar: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.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -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.activemq.protobuf 
-DartifactId=activemq-protobuf -Dversion=1.0-SNAPSHOT -Dpackaging=jar 
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3-SNAPSHOT
3) org.apache.activemq.protobuf:activemq-protobuf:jar:1.0-SNAPSHOT

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar: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)
at

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

[gawor]

Geronimo Revision: 820181 built with tests included
 
See the full build-0200.log file at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090930/build-0200.log
 
Download the binaries from 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090930
[INFO] BUILD SUCCESSFUL
[INFO] 
[INFO] Total time: 36 minutes 24 seconds
[INFO] Finished at: Wed Sep 30 02:40:21 EDT 2009
[INFO] Final Memory: 264M/913M
[INFO] 
 
TESTSUITE RESULTS (Failures only)
=
 
Assembly: tomcat
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090930/logs-0200-tomcat/
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 15, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 73.764 
sec <<< FAILURE!
 
Assembly: jetty
=
See full test results and logs at 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090930/logs-0200-jetty/
 
[INFO] Running console-testsuite.advance-test
[INFO] Tests run: 15, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 80.542 
sec <<< FAILURE!
 
Samples: branches/2.1
=
Log: 
http://people.apache.org/builds/geronimo/server/binaries/2.1/20090930/samples-0200.log
 
Build status: OK
 

[BUILD] trunk: Failed for Revision: 820189

[gawor]

Geronimo Revision: 820189 built with tests included
 
See the full build-0300.log file at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090930/build-0300.log
 
 
See the unit test reports at 
http://people.apache.org/builds/geronimo/server/binaries/trunk/20090930/unit-test-reports
 

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2),
  amq-protobuf-staging 
(https://repository.apache.org/content/repositories/releases/),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-030/)



[INFO] 
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Missing:
--
1) org.apache.activemq:activemq-core:jar:5.3.0

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -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.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3.0

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2),
  amq-protobuf-staging 
(https://repository.apache.org/content/repositories/releases/),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-030/)


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:597)
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.activemq:activemq-core:jar:5.3.0

  Try downloading the file manually from the project website.

  Then, install it using the command: 
  mvn install:install-file -DgroupId=org.apache.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -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.activemq 
-DartifactId=activemq-core -Dversion=5.3.0 -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]

  Path to dependency: 
1) org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT
2) org.apache.activemq:activemq-core:jar:5.3.0

--
1 required artifact is missing.

for artifact: 
  org.apache.geronimo.modules:geronimo-activemq:jar:3.0-SNAPSHOT

from the specified remote repositories:
  codehaus.snapshots (http://snapshots.repository.codehaus.org),
  apache.snapshots (http://repository.apache.org/snapshots),
  ibiblio.org (http://repo.exist.com/maven2),
  amq-protobuf-staging 
(https://repository.apache.org/content/repositories/releases/),
  amq-staging 
(https://repository.apache.org/content/repositories/activemq-staging-030/)


at

[jira] Resolved: (GERONIMO-4810) Predefine a "localhost" server with some predefined graphs and views

[Ivan (JIRA)]

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

Ivan resolved GERONIMO-4810.


   Resolution: Fixed
Fix Version/s: 3.0
   2.2
   2.1.5

Commit the changes to 2.1.5 At revision: 820185, 2.2-snapshot At revision: 
820189 and trunk At revision: 820191.
Thanks for the patch, Vanessa !

> Predefine a "localhost" server with some predefined graphs and views
> 
>
> Key: GERONIMO-4810
> URL: https://issues.apache.org/jira/browse/GERONIMO-4810
> Project: Geronimo
>  Issue Type: New Feature
>  Security Level: public(Regular issues) 
>Affects Versions: 2.1.5, 2.2
>Reporter: Jack Cai
>Assignee: Shawn Jiang
>Priority: Minor
> Fix For: 2.1.5, 2.2, 3.0
>
> Attachments: predefined data-2.1.5.patch, predefined data-2.2.patch
>
>
> It will be useful if we can predefine a "localhost" server. Some 
> frequent-used graphs/views can also be prodefined.

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