Re: [BUILD] trunk: Failed for Revision: 785862
While building 2.2, some jetty7 classes can not compiled, seems that some Jetty7 API is changed in the new snapshot. 2009/6/18 Ivan > > > 2009/6/18 David Jencks > >> This might be reason for genesis 2.0.1. I imagine that pointing to the >> new repo would work better >> Ivan: >> >So, do we have any plan for genesis 2.0.1 ? I suggest to add the repo > temporary before the new version is released. > >> >> On the other hand we shouldn't be using many snapshot plugins that we >> aren't building... >> >> This particular problem might require some kind of bootstrap to build the >> car-maven-plugin before trying to use it? Or just trying to build twice? >> Ivan : >> > I will try it. > > >> >> thanks >> david jencks >> >> >> On Jun 17, 2009, at 8:10 PM, Ivan wrote: >> >> I mean the pluginRepositories definition, not pluginManager :-) >> >> 2009/6/18 Ivan >> >>> I found that the pluginManager definition in the genesis 2.0 is >>> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository). >>> But those 2.2 artifacts are in the new nexus site. >>> So I wonder that in the future, we will publish both geromimo mudules and >>> maven plugins snapshot to the new nexus site, right ? >>> And if does, shall we need to add a pluginManager definition in the >>> geronimo pom file ? >>> Thanks ! >>> >>> >>> 2009/6/18 Ivan >>> >>> Why is "apache.snapshots ( >>>> http://people.apache.org/repo/m2-snapshot-repository)" in the log ? >>>> Ivan >>>> >>>> 2009/6/18 >>>> >>>> > >>>> > Geronimo Revision: 785862 built with tests included >>>> > >>>> > See the full build-2100.log file at >>>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/build-2100.log >>>> > >>>> > >>>> > See the unit test reports at >>>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/unit-test-reports >>>> > >>>> > from the specified remote repositories: >>>> > codehaus.snapshots (http://snapshots.repository.codehaus.org), >>>> > apache.snapshots ( >>>> http://people.apache.org/repo/m2-snapshot-repository), >>>> > ibiblio.org (http://repo.exist.com/maven2) >>>> > >>>> > >>>> > >>>> >>>> org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT >>>> > >>>> > from the specified remote repositories: >>>> > codehaus.snapshots (http://snapshots.repository.codehaus.org), >>>> > apache.snapshots ( >>>> http://people.apache.org/repo/m2-snapshot-repository), >>>> > ibiblio.org (http://repo.exist.com/maven2) >>>> > >>>> > >>>> > [INFO] >>>> >>>> > [INFO] Trace >>>> > org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could >>>> not be found - check that the goal name is correct: Unable to download the >>>> artifact from any repository >>>> > >>>> > Try downloading the file manually from the project website. >>>> > >>>> > Then, install it using the command: >>>> >mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport >>>> -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT >>>> -Dpackaging=maven-plugin -Dfile=/path/to/file >>>> > >>>> > Alternatively, if you host your own repository you can deploy the file >>>> there: >>>> >mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport >>>> -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT >>>> -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] >>>> -DrepositoryId=[id] >>>> > >>>> > >>>> > >>>> >>>> org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT >>>> > >>>> > from the specified remote repositories: >>>> > codehaus.snapshots (http://snapshots.repository.codehaus.org), >>>> > apache.snapshots ( >>>> http://people.apache.org/repo/m2-snapshot-repository), >>>> > ibiblio.org (http://repo.exist.com/maven2
[BUILD] trunk: Failed for Revision: 785918
Geronimo Revision: 785918 built with tests included See the full build-0300.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090618/build-0300.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090618/unit-test-reports from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus.snapshots (http://snapshots.repository.codehaus.org) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus.snapshots (http://snapshots.repository.codehaus.org) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus.snapshots (http://snapshots.repository.codehaus.org) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus.snapshots (http://snapshots.repository.codehaus.org) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:184) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) 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.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus.snapshots (http://snapshots.repository.codehaus.org) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), codehaus.snapshots (http://snapshots.repository.codehaus.org) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:241) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1275)
Re: Assemblies in the repo and their dependencies
Okay, I will give it a shot on trunk first, if that works I will try on branches/2.1. --jason On Jun 18, 2009, at 4:31 AM, David Jencks wrote: On Jun 17, 2009, at 1:36 AM, Jason Dillon wrote: Why do the assemblies in the repository have dependencies? I realize that they are probably there to facilitate the build, but shouldn't they all be marked as provided? The reason I think they should be, is that when a user wants to use the geronimo-maven-plugin with the assembly -bin in the repository, before they can even download the assembly -bin, first mvn has to go resolve every single dependency which is used to build that assembly -bin. I think this is broken, while I can resolve by adding a tone of excludes, I think that this problem should be solved so that users can more easily consume the assembly artifacts we publish to the repository. Any one know how easy/feasible with the current stuff (trunk and 2.1.x) it would be to mark all dependencies as provided? Just thinking about it I don't see why it would cause problems. Would you like to try it and see if the server at least builds? If there are no obvious problems I'd be fine with this change. thanks david jencks --jason
Re: [BUILD] trunk: Failed for Revision: 785862
2009/6/18 David Jencks > This might be reason for genesis 2.0.1. I imagine that pointing to the > new repo would work betterIvan: > So, do we have any plan for genesis 2.0.1 ? I suggest to add the repo temporary before the new version is released. > > On the other hand we shouldn't be using many snapshot plugins that we > aren't building... > > This particular problem might require some kind of bootstrap to build the > car-maven-plugin before trying to use it? Or just trying to build twice? > Ivan : > I will try it. > > thanks > david jencks > > > On Jun 17, 2009, at 8:10 PM, Ivan wrote: > > I mean the pluginRepositories definition, not pluginManager :-) > > 2009/6/18 Ivan > >> I found that the pluginManager definition in the genesis 2.0 is >> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository). >> But those 2.2 artifacts are in the new nexus site. >> So I wonder that in the future, we will publish both geromimo mudules and >> maven plugins snapshot to the new nexus site, right ? >> And if does, shall we need to add a pluginManager definition in the >> geronimo pom file ? >> Thanks ! >> >> >> 2009/6/18 Ivan >> >> Why is "apache.snapshots ( >>> http://people.apache.org/repo/m2-snapshot-repository)" in the log ? >>> Ivan >>> >>> 2009/6/18 >>> >>> > >>> > Geronimo Revision: 785862 built with tests included >>> > >>> > See the full build-2100.log file at >>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/build-2100.log >>> > >>> > >>> > See the unit test reports at >>> http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/unit-test-reports >>> > >>> > from the specified remote repositories: >>> > codehaus.snapshots (http://snapshots.repository.codehaus.org), >>> > apache.snapshots ( >>> http://people.apache.org/repo/m2-snapshot-repository), >>> > ibiblio.org (http://repo.exist.com/maven2) >>> > >>> > >>> > >>> org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT >>> > >>> > from the specified remote repositories: >>> > codehaus.snapshots (http://snapshots.repository.codehaus.org), >>> > apache.snapshots ( >>> http://people.apache.org/repo/m2-snapshot-repository), >>> > ibiblio.org (http://repo.exist.com/maven2) >>> > >>> > >>> > [INFO] >>> >>> > [INFO] Trace >>> > org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could >>> not be found - check that the goal name is correct: Unable to download the >>> artifact from any repository >>> > >>> > Try downloading the file manually from the project website. >>> > >>> > Then, install it using the command: >>> >mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport >>> -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT >>> -Dpackaging=maven-plugin -Dfile=/path/to/file >>> > >>> > Alternatively, if you host your own repository you can deploy the file >>> there: >>> >mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport >>> -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT >>> -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] >>> -DrepositoryId=[id] >>> > >>> > >>> > >>> org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT >>> > >>> > from the specified remote repositories: >>> > codehaus.snapshots (http://snapshots.repository.codehaus.org), >>> > apache.snapshots ( >>> http://people.apache.org/repo/m2-snapshot-repository), >>> > ibiblio.org (http://repo.exist.com/maven2) >>> > >>> > >>> > >>> org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT >>> > >>> > from the specified remote repositories: >>> > codehaus.snapshots (http://snapshots.repository.codehaus.org), >>> > apache.snapshots ( >>> http://people.apache.org/repo/m2-snapshot-repository), >>> > ibiblio.org (http://repo.exist.com/maven2) >>> > >>> > >>> >at >>> org.apache.maven.lifecycle.DefaultLifecycleExecutor.findE
Re: [BUILD] trunk: Failed for Revision: 785862
This might be reason for genesis 2.0.1. I imagine that pointing to the new repo would work better On the other hand we shouldn't be using many snapshot plugins that we aren't building... This particular problem might require some kind of bootstrap to build the car-maven-plugin before trying to use it? Or just trying to build twice? thanks david jencks On Jun 17, 2009, at 8:10 PM, Ivan wrote: I mean the pluginRepositories definition, not pluginManager :-) 2009/6/18 Ivan I found that the pluginManager definition in the genesis 2.0 is apache.snapshots (http://people.apache.org/repo/m2-snapshot- repository). But those 2.2 artifacts are in the new nexus site. So I wonder that in the future, we will publish both geromimo mudules and maven plugins snapshot to the new nexus site, right ? And if does, shall we need to add a pluginManager definition in the geronimo pom file ? Thanks ! 2009/6/18 Ivan Why is "apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository )" in the log ? Ivan 2009/6/18 > > Geronimo Revision: 785862 built with tests included > > See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/build-2100.log > > > See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/unit-test-reports > > from the specified remote repositories: > codehaus.snapshots (http://snapshots.repository.codehaus.org), > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ), > ibiblio.org (http://repo.exist.com/maven2) > > > org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin: 2.2-SNAPSHOT > > from the specified remote repositories: > codehaus.snapshots (http://snapshots.repository.codehaus.org), > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ), > ibiblio.org (http://repo.exist.com/maven2) > > > [INFO] > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository > > Try downloading the file manually from the project website. > > Then, install it using the command: >mvn install:install-file - DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven- plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/ to/file > > Alternatively, if you host your own repository you can deploy the file there: >mvn deploy:deploy-file - DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven- plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/ to/file -Durl=[url] -DrepositoryId=[id] > > > org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin: 2.2-SNAPSHOT > > from the specified remote repositories: > codehaus.snapshots (http://snapshots.repository.codehaus.org), > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ), > ibiblio.org (http://repo.exist.com/maven2) > > > org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin: 2.2-SNAPSHOT > > from the specified remote repositories: > codehaus.snapshots (http://snapshots.repository.codehaus.org), > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository ), > ibiblio.org (http://repo.exist.com/maven2) > > >at org .apache .maven .lifecycle .DefaultLifecycleExecutor .findExtensions(DefaultLifecycleExecutor.java:184) >at org .apache .maven .lifecycle .DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) >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.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository > > Try downloading the file manually from the project
Re: [BUILD] trunk: Failed for Revision: 785862
I mean the pluginRepositories definition, not pluginManager :-) 2009/6/18 Ivan > I found that the pluginManager definition in the genesis 2.0 is > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository). > But those 2.2 artifacts are in the new nexus site. > So I wonder that in the future, we will publish both geromimo mudules and > maven plugins snapshot to the new nexus site, right ? > And if does, shall we need to add a pluginManager definition in the > geronimo pom file ? > Thanks ! > > > 2009/6/18 Ivan > > Why is "apache.snapshots ( >> http://people.apache.org/repo/m2-snapshot-repository)" in the log ? >> Ivan >> >> 2009/6/18 >> >> > >> > Geronimo Revision: 785862 built with tests included >> > >> > See the full build-2100.log file at >> http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/build-2100.log >> > >> > >> > See the unit test reports at >> http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/unit-test-reports >> > >> > from the specified remote repositories: >> > codehaus.snapshots (http://snapshots.repository.codehaus.org), >> > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository >> ), >> > ibiblio.org (http://repo.exist.com/maven2) >> > >> > >> > >> org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT >> > >> > from the specified remote repositories: >> > codehaus.snapshots (http://snapshots.repository.codehaus.org), >> > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository >> ), >> > ibiblio.org (http://repo.exist.com/maven2) >> > >> > >> > [INFO] >> >> > [INFO] Trace >> > org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not >> be found - check that the goal name is correct: Unable to download the >> artifact from any repository >> > >> > Try downloading the file manually from the project website. >> > >> > Then, install it using the command: >> >mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport >> -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT >> -Dpackaging=maven-plugin -Dfile=/path/to/file >> > >> > Alternatively, if you host your own repository you can deploy the file >> there: >> >mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport >> -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT >> -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] >> -DrepositoryId=[id] >> > >> > >> > >> org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT >> > >> > from the specified remote repositories: >> > codehaus.snapshots (http://snapshots.repository.codehaus.org), >> > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository >> ), >> > ibiblio.org (http://repo.exist.com/maven2) >> > >> > >> > >> org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT >> > >> > from the specified remote repositories: >> > codehaus.snapshots (http://snapshots.repository.codehaus.org), >> > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository >> ), >> > ibiblio.org (http://repo.exist.com/maven2) >> > >> > >> >at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:184) >> >at >> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) >> >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.m
Re: [BUILD] trunk: Failed for Revision: 785862
I found that the pluginManager definition in the genesis 2.0 is apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository). But those 2.2 artifacts are in the new nexus site. So I wonder that in the future, we will publish both geromimo mudules and maven plugins snapshot to the new nexus site, right ? And if does, shall we need to add a pluginManager definition in the geronimo pom file ? Thanks ! 2009/6/18 Ivan > Why is "apache.snapshots ( > http://people.apache.org/repo/m2-snapshot-repository)" in the log ? > Ivan > > 2009/6/18 > > > > > Geronimo Revision: 785862 built with tests included > > > > See the full build-2100.log file at > http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/build-2100.log > > > > > > See the unit test reports at > http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/unit-test-reports > > > > from the specified remote repositories: > > codehaus.snapshots (http://snapshots.repository.codehaus.org), > > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository > ), > > ibiblio.org (http://repo.exist.com/maven2) > > > > > > > org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT > > > > from the specified remote repositories: > > codehaus.snapshots (http://snapshots.repository.codehaus.org), > > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository > ), > > ibiblio.org (http://repo.exist.com/maven2) > > > > > > [INFO] > > > [INFO] Trace > > org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not > be found - check that the goal name is correct: Unable to download the > artifact from any repository > > > > Try downloading the file manually from the project website. > > > > Then, install it using the command: > >mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport > -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT > -Dpackaging=maven-plugin -Dfile=/path/to/file > > > > Alternatively, if you host your own repository you can deploy the file > there: > >mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport > -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT > -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] > -DrepositoryId=[id] > > > > > > > org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT > > > > from the specified remote repositories: > > codehaus.snapshots (http://snapshots.repository.codehaus.org), > > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository > ), > > ibiblio.org (http://repo.exist.com/maven2) > > > > > > > org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT > > > > from the specified remote repositories: > > codehaus.snapshots (http://snapshots.repository.codehaus.org), > > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository > ), > > ibiblio.org (http://repo.exist.com/maven2) > > > > > >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:184) > >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) > >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.plugin.PluginNotFoundException: Plugin could > not be found - check that the goal name is correct: Unable to download the > artifact from any repository > > > > Try downloading the file manually from the project website. > > > > Then, install it using the command: > >mvn install:install-file -DgroupId=org.apache.
Re: [BUILD] trunk: Failed for Revision: 785862
Why is "apache.snapshots ( http://people.apache.org/repo/m2-snapshot-repository)" in the log ? Ivan 2009/6/18 > > Geronimo Revision: 785862 built with tests included > > See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/build-2100.log > > > See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/unit-test-reports > > from the specified remote repositories: > codehaus.snapshots (http://snapshots.repository.codehaus.org), > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), > ibiblio.org (http://repo.exist.com/maven2) > > > org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT > > from the specified remote repositories: > codehaus.snapshots (http://snapshots.repository.codehaus.org), > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), > ibiblio.org (http://repo.exist.com/maven2) > > > [INFO] > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository > > Try downloading the file manually from the project website. > > Then, install it using the command: >mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file there: >mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > > org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT > > from the specified remote repositories: > codehaus.snapshots (http://snapshots.repository.codehaus.org), > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), > ibiblio.org (http://repo.exist.com/maven2) > > > org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT > > from the specified remote repositories: > codehaus.snapshots (http://snapshots.repository.codehaus.org), > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), > ibiblio.org (http://repo.exist.com/maven2) > > >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:184) >at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) >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.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository > > Try downloading the file manually from the project website. > > Then, install it using the command: >mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file there: >mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] > > > org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT > > from the specified remote repositories: > codehaus.snapshots (http://snapshots.repository.codehaus.org), > apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), > ibiblio.org (http://repo.exist.com/maven2) > > > org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT > > from the specified remote repositories: > codehaus.snapshots (http://snapshots.re
Re: Update OpenEJB version number 3.1.1 to 3.1.2-SNAPSHOT for Geronimo 2.2 SNAPSHOT
Yes, I think we need. For some EJB cases failed, and it may be related to the OpenEJB. 2009/6/18 Joe Bohn > Ivan wrote: > >> Hi, >> I got the news from OpenEJB maillist, that the version number in the >> trunk is updated to 3.1.2-SNAPSHOT, so I wish that in Geronimo 2.2-SNAPSHOT, >> we could use 3.1.2. >> Any comment ? If no objection, I will update it. >> Thanks ! >> >> -- >> Ivan >> > > So does this mean that we need another OpenEJB release (3.1.2) before we > can release Geronimo 2.2? I thought we were hoping to release G 2.2 with > the recently released OpenEJB 3.1.1. > > Joe > > -- Ivan
[jira] Resolved: (GERONIMO-4650) changes not persisted to security realms
[ https://issues.apache.org/jira/browse/GERONIMO-4650?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jack Cai resolved GERONIMO-4650. Resolution: Duplicate As Viola pointed out, it's a duplicate of https://issues.apache.org/jira/browse/GERONIMO-4635. So closing it. > changes not persisted to security realms > > > Key: GERONIMO-4650 > URL: https://issues.apache.org/jira/browse/GERONIMO-4650 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: security >Affects Versions: 2.1.4 > Environment: Windows XP, JRE 1.5.0_06 >Reporter: Bobby Lawrence > > After creating an LDAP security realm and editing the options and/or login > module class name, a subsequent restart of the server loses all changes made. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (GERONIMO-4694) Upgrade to Derby 10.5.1.1
Upgrade to Derby 10.5.1.1 - Key: GERONIMO-4694 URL: https://issues.apache.org/jira/browse/GERONIMO-4694 Project: Geronimo Issue Type: Improvement Security Level: public (Regular issues) Components: databases Affects Versions: 2.2 Reporter: Jack Cai Fix For: 2.2 Derby has released a new version 10.5.1.1 last month. Let's upgrade to this version for 2.2. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 785862
Geronimo Revision: 785862 built with tests included See the full build-2100.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/build-2100.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/unit-test-reports from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), ibiblio.org (http://repo.exist.com/maven2) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), ibiblio.org (http://repo.exist.com/maven2) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), ibiblio.org (http://repo.exist.com/maven2) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), ibiblio.org (http://repo.exist.com/maven2) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:184) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) 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.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), ibiblio.org (http://repo.exist.com/maven2) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin:2.2-SNAPSHOT from the specified remote repositories: codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository), ibiblio.org (http://repo.exist.com/maven2) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:241) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1275
Re: Assemblies in the repo and their dependencies
On Jun 17, 2009, at 1:36 AM, Jason Dillon wrote: Why do the assemblies in the repository have dependencies? I realize that they are probably there to facilitate the build, but shouldn't they all be marked as provided? The reason I think they should be, is that when a user wants to use the geronimo-maven-plugin with the assembly -bin in the repository, before they can even download the assembly -bin, first mvn has to go resolve every single dependency which is used to build that assembly -bin. I think this is broken, while I can resolve by adding a tone of excludes, I think that this problem should be solved so that users can more easily consume the assembly artifacts we publish to the repository. Any one know how easy/feasible with the current stuff (trunk and 2.1.x) it would be to mark all dependencies as provided? Just thinking about it I don't see why it would cause problems. Would you like to try it and see if the server at least builds? If there are no obvious problems I'd be fine with this change. thanks david jencks --jason
Re: Update OpenEJB version number 3.1.1 to 3.1.2-SNAPSHOT for Geronimo 2.2 SNAPSHOT
Ivan wrote: Hi, I got the news from OpenEJB maillist, that the version number in the trunk is updated to 3.1.2-SNAPSHOT, so I wish that in Geronimo 2.2-SNAPSHOT, we could use 3.1.2. Any comment ? If no objection, I will update it. Thanks ! -- Ivan So does this mean that we need another OpenEJB release (3.1.2) before we can release Geronimo 2.2? I thought we were hoping to release G 2.2 with the recently released OpenEJB 3.1.1. Joe
Re: Update OpenEJB version number 3.1.1 to 3.1.2-SNAPSHOT for Geronimo 2.2 SNAPSHOT
Go for it! -David On Jun 16, 2009, at 7:17 PM, Ivan wrote: Hi, I got the news from OpenEJB maillist, that the version number in the trunk is updated to 3.1.2-SNAPSHOT, so I wish that in Geronimo 2.2-SNAPSHOT, we could use 3.1.2. Any comment ? If no objection, I will update it. Thanks ! -- Ivan
Question about legacy snapshots and nexus
I've been trying to cleanup some of our snapshot artifacts from the legacy repo once we have new ones deployed to the nexus snapshots repo, but after artifacts are removed from the legacy repo, they are still showing up in the aggregated snapshots view in nexus [1] - [1] http://repository.apache.org/snapshots/org/apache/geronimo/buildsupport/car-maven-plugin/2.2-SNAPSHOT/ In the above example, the old Dec 2008 artifacts were from the old legacy repo, but were removed earlier today, so why are they still showing up in the list and how do we correct this? -Donald
[jira] Closed: (GERONIMO-4692) Sort dependencies.xml history so you can tell what changed.
[ https://issues.apache.org/jira/browse/GERONIMO-4692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Jencks closed GERONIMO-4692. -- Resolution: Fixed Finished after a few commits ending with rev 785761 > Sort dependencies.xml history so you can tell what changed. > --- > > Key: GERONIMO-4692 > URL: https://issues.apache.org/jira/browse/GERONIMO-4692 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: buildsystem >Affects Versions: 2.2 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 2.2 > > > If you get fed up with the dependency change monitor and delete the > src/main/history/dependencies.xml the new file is in a random order compared > to the one in svn. If we sort them then it will be easier to tell from svn > logs what changed. > step 1: commit change in car-maven-plugin. > step 2; delete all the dependencies.xml and rebuild, commit changes. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[BUILD] trunk: Failed for Revision: 785745
Geronimo Revision: 785745 built with tests included See the full build-1500.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/build-1500.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/unit-test-reports from the specified remote repositories: ibiblio.org (http://repo.exist.com/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin: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://people.apache.org/repo/m2-snapshot-repository) [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin: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://people.apache.org/repo/m2-snapshot-repository) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin: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://people.apache.org/repo/m2-snapshot-repository) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.findExtensions(DefaultLifecycleExecutor.java:184) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140) 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.plugin.PluginNotFoundException: Plugin could not be found - check that the goal name is correct: Unable to download the artifact from any repository Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.geronimo.buildsupport -DartifactId=car-maven-plugin -Dversion=2.2-SNAPSHOT -Dpackaging=maven-plugin -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin: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://people.apache.org/repo/m2-snapshot-repository) org.apache.geronimo.buildsupport:car-maven-plugin:maven-plugin: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://people.apache.org/repo/m2-snapshot-repository) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:241) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1275
Re: Stuff I really want in 2.2
We also need to upgrade to Tomcat 6.0.20, which has 5 new security fixes (2 deemed Important) and was released on May 29th - http://tomcat.apache.org/security-6.html -Donald David Jencks wrote: Here are some things I really really want in 2.2. Since my main focus at the moment is getting the incipient 3.0 more osgi-ready if I have to do all of them 2.2 will be a long time coming... so hopefully others will become inspired and want to help :-) - in no particular order - 1. upgrade to maven 2.1 2. upgrade to latest apache pom (6?) 3. upgrade to latest assembly plugin to help with source distros (I don't think it's released yet) 4. reexamine genesis and trim it (probably means genesis 2) 5. use the release plugin 6. get all our private dependencies into maven central. This probably means releasing with our groupId unless we can get the projects to do a release 7. When we deploy, write the plan into the plugin something like the car-maven-plugin does. Same with the default geronimo-plugin.xml (GERONIMO-4628) 8. We need some way to override/configure/set javaee env-entry values from something other than the original spec dd or annotation (GERONIMO-4630) 9. In the console, provide a uniform way to completely specify the artfiact ID for a plan being created. Save the groupId and version as config-substitutions or something persistent. 10. Provide a way to edit artifact-aliases in the console. Include a way to specify artifact-alias when installing a jar. thanks david jencks
Re: Problems merging file based and nexus hosted metadata?
Looks like the activemq trunk is not really setup to deploy to Nexus
yet, as they are still using the old apache-4.pom
Here is a quick diff that will allow deploying to nexus, but it requires
someone with activemq committer rights :-)
Index: pom.xml
===
--- pom.xml (revision 785685)
+++ pom.xml (working copy)
@@ -19,7 +19,7 @@
org.apache
apache
-4
+6
4.0.0
@@ -114,6 +114,16 @@
${staging.siteURL}/${siteId}/maven/${activemq-version}
+
+ apache.releases.https
+ Apache Release Distribution Repository
+
https://repository.apache.org/service/local/staging/deploy/maven2
+
+
+ apache.snapshots.https
+ ${distMgmtSnapshotsName}
+ ${distMgmtSnapshotsUrl}
+
@@ -967,10 +977,15 @@
org.apache.maven.plugins
maven-release-plugin
- 2.0-beta-7
+ 2.0-beta-9
org.apache.maven.plugins
+ maven-deploy-plugin
+ 2.4
+
+
+ org.apache.maven.plugins
maven-remote-resources-plugin
1.0
@@ -1266,9 +1281,9 @@
org.apache.maven.plugins
maven-deploy-plugin
+2.4
true
-
${staging.altRepository}/${siteId}
true
David Jencks wrote:
Geroniomo is having problems getting up to date activemq snapshots from
the repo. I think the problem might be that the metadata from the
people.apache.org files based repo and the metadata from the nexus based
repo aren't getting merged properly:
nexus hosted repo:
https://repository.apache.org/content/repositories/snapshots/org/apache/activemq/activemq-camel/5.3-SNAPSHOT/maven-metadata.xml
has
org.apache.activemq
activemq-camel
5.3-SNAPSHOT
1
20090615193531
antique file based repo:
https://repository.apache.org/content/repositories/apache-legacy-snapshots/org/apache/activemq/activemq-core/5.3-SNAPSHOT/maven-metadata.xml
has
org.apache.activemq
activemq-core
5.3-SNAPSHOT
20090417.072917
167
20090417073310
merged repo
https://repository.apache.org/content/groups/snapshots-group/org/apache/activemq/activemq-core/5.3-SNAPSHOT/maven-metadata.xml
has
http://maven.apache.org/METADATA/1.0.0
http://maven.apache.org/xsd/metadata-1.0.0.xsd";
xmlns="http://maven.apache.org/METADATA/1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
org.apache.activemq
activemq-core
5.3-SNAPSHOT
20090417.072917
167
20090417073310
which matches the older version better.
Note that activemq is using non-unique snapshots.
What is the best way to fix this?
- remove obsolete snapshots from peopel.apache.org repo?
- use unique (timestamped) snapshots ?
- both ?
- something else ???
thanks
david jencks
Index: pom.xml
===
--- pom.xml (revision 785685)
+++ pom.xml (working copy)
@@ -19,7 +19,7 @@
org.apache
apache
-4
+6
4.0.0
@@ -114,6 +114,16 @@
${staging.siteURL}/${siteId}/maven/${activemq-version}
+
+ apache.releases.https
+ Apache Release Distribution Repository
+
https://repository.apache.org/service/local/staging/deploy/maven2
+
+
+ apache.snapshots.https
+ ${distMgmtSnapshotsName}
+ ${distMgmtSnapshotsUrl}
+
@@ -967,10 +977,15 @@
org.apache.maven.plugins
maven-release-plugin
- 2.0-beta-7
+ 2.0-beta-9
org.apache.maven.plugins
+ maven-deploy-plugin
+ 2.4
+
+
+ org.apache.maven.plugins
maven-remote-resources-plugin
1.0
@@ -1266,9 +1281,9 @@
org.apache.maven.plugins
maven-deploy-plugin
+2.4
true
-
${staging.altRepository}/${siteId}
true
Re: Update the 2.2 release status page?
Rex Wang wrote: > How frequent do you think is the most appropriate for Geronimo? Frequent releases is in a sign of a healthy and active project and nothing else. I understand that a Geronimo release is a massive undertaking with the TCK and a wide range of domain specific issues that are hard to know much about as a open source developer. Regardless, if I was allowed to dream, I'd like to see stable updates (x.y.z) at least once every second month and a new major feature release (x or x.y) once every six month. > IMHO, too more releases in a year might give users the impression that > the production is very young and not stable. Nope, not at all. At least I do not see Geronimo being anywhere close to that limit yet. No need to worry until you see "brown paper bag" releases once every week or so. ;) BTW, I'm very exited about the up coming 2.2 release! Thanks for listening to a mere user. -- Fredrik Jonson
[BUILD] branches/2.1: Failed for Revision: 785550
Geronimo Revision: 785550 built with tests included See the full build-0800.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20090617/build-0800.log Download the binaries from http://people.apache.org/builds/geronimo/server/binaries/2.1/20090617 [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 33 minutes 6 seconds [INFO] Finished at: Wed Jun 17 08:39:18 EDT 2009 [INFO] Final Memory: 320M/939M [INFO] TESTSUITE RESULTS (Failures only) = See detailed results at http://people.apache.org/builds/geronimo/server/testsuite/ResultsSummary.html Assembly: tomcat = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20090617/logs-0800-tomcat/test.log [INFO] Running console-testsuite.basic-console [INFO] Tests run: 49, Failures: 5, Errors: 0, Skipped: 15, Time elapsed: 72.135 sec <<< FAILURE! Assembly: jetty = See the full test.log file at http://people.apache.org/builds/geronimo/server/binaries/2.1/20090617/logs-0800-jetty/test.log Samples: branches/2.1 = Log: http://people.apache.org/builds/geronimo/server/binaries/2.1/20090617/samples-0800.log Build status: OK
[jira] Commented: (GERONIMO-4685) Build our own tomcat.
[ https://issues.apache.org/jira/browse/GERONIMO-4685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720665#action_12720665 ] Donald Woods commented on GERONIMO-4685: We also need to upgrade to Tomcat 6.0.20, which includes 5 new security fixes. > Build our own tomcat. > - > > Key: GERONIMO-4685 > URL: https://issues.apache.org/jira/browse/GERONIMO-4685 > Project: Geronimo > Issue Type: Bug > Security Level: public(Regular issues) > Components: buildsystem, Tomcat >Affects Versions: 2.2 >Reporter: David Jencks >Assignee: David Jencks > Fix For: 2.2 > > > We don't have the patches used to build the tomcat version we distribute, at > least I can't interpret diffs of diffs. > Build an archetype that sets up a maven multimodule project to build tomcat. > Use a bash script to svn copy tomcat source into this structure > commit > apply patches > commit > build under our own groupId. > Work started in sandbox djencks/tomcat-archetype. > Note that tomcat jars distributed by tomcat have circular dependencies. So, > combine catalina and coyote jars. Split out util for now. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: [BUILD] trunk: Failed for Revision: 785566
There were some old activemq 5.3-SNAPSHOT unique snapshot versions (5.3-20090417.072917-276) left behind on the old snapshot repo, which have now been removed. Hopefully, that will solve our build issues, as the new artifacts on the Nexus repo do not use unique timestamps -Donald ga...@apache.org wrote: Geronimo Revision: 785566 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/unit-test-reports from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) Path to dependency: 1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT 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.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.activemq:activemq-core:jar': Cannot find parent: org.apache.activemq:activemq-parent for project: null:activemq-core:bundle:null for project null:activemq-core:bundle:null org.apache.activemq:activemq-core:jar:5.3-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) Path to dependency: 1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:432) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1417) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:407) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) ... 16 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'org.apache.activemq:activemq-core:jar': Cannot find parent: org.apache.activemq:activemq-parent for project: null:activemq-core:bundle:null for project null:activemq-core:bundle:null at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:183) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedArtifact(MavenMetadataSource.java:91) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:388) ... 22 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.apache.activemq:activemq-parent for project: null:activemq-core:bundle:null for project null:activemq-core:bundle:null at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMave
[BUILD] trunk: Failed for Revision: 785566
Geronimo Revision: 785566 built with tests included See the full build-0900.log file at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/build-0900.log See the unit test reports at http://people.apache.org/builds/geronimo/server/binaries/trunk/20090617/unit-test-reports from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) Path to dependency: 1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT 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.ArtifactResolutionException: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.activemq:activemq-core:jar': Cannot find parent: org.apache.activemq:activemq-parent for project: null:activemq-core:bundle:null for project null:activemq-core:bundle:null org.apache.activemq:activemq-core:jar:5.3-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), codehaus.snapshots (http://snapshots.repository.codehaus.org), apache.snapshots (http://repository.apache.org/snapshots) Path to dependency: 1) org.apache.geronimo.modules:geronimo-activemq:jar:2.2-SNAPSHOT at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:432) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(DefaultArtifactCollector.java:74) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:300) at org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:288) at org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1417) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:407) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559) ... 16 more Caused by: org.apache.maven.artifact.metadata.ArtifactMetadataRetrievalException: Unable to read the metadata file for artifact 'org.apache.activemq:activemq-core:jar': Cannot find parent: org.apache.activemq:activemq-parent for project: null:activemq-core:bundle:null for project null:activemq-core:bundle:null at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedProject(MavenMetadataSource.java:183) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocatedArtifact(MavenMetadataSource.java:91) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(DefaultArtifactCollector.java:388) ... 22 more Caused by: org.apache.maven.project.ProjectBuildingException: Cannot find parent: org.apache.activemq:activemq-parent for project: null:activemq-core:bundle:null for project null:activemq-core:bundle:null at org.apache.maven.project.DefaultMavenProjectBuilder.assembleLineage(DefaultMavenProjectBuilder.java:1369) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:820) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromRepository(DefaultMavenProjectBuilder.
Re: Update the 2.2 release status page?
Personally, I'd like a bugfix release each month or so. I like frequent releases. Firefox 3 is at 3.0.11 now, albeit mostly with security fixes. But I also understand the points you made. On the other hand people trust more a x.1 version than an x.0 version, so a Geronimo 2.1.20 would give the impression of a very stable version with many bugs fixed (as does Tomcat 6.0.20). The rare updates of Geronimo with rare news make the website a bit un-active, it looks like there is not a lot happening with the project. http://directory.apache.org/ -> news looks much more active with their mix of new features and honorable mentions. Thanks, Juergen Rex Wang-2 wrote: > > How frequent do you think is the most appropriate for Geronimo? > IMHO, too more releases in a year might give users the impression that the > production is very young and not stable. > > > Thank you > -Rex > -- View this message in context: http://www.nabble.com/Update-the-2.2-release-status-page--tp24030920s134p24071422.html Sent from the Apache Geronimo - Dev mailing list archive at Nabble.com.
[jira] Created: (GERONIMO-4693) Update OpenEJB version from 3.1.1 to 3.1.2
Update OpenEJB version from 3.1.1 to 3.1.2 -- Key: GERONIMO-4693 URL: https://issues.apache.org/jira/browse/GERONIMO-4693 Project: Geronimo Issue Type: New Feature Security Level: public (Regular issues) Components: OpenEJB Affects Versions: 2.2 Reporter: Ivan Assignee: Ivan Fix For: 2.2 The version of OpenEJB trunk is 3.1.2-SNAPSHOT now, we need to update the OpenEJB version in Geronimo 2.2 to 3.1.2-SNAPSHOT. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-3389) console: java.lang.UnsatisfiedLinkError is thrown when create a Tomcat APR HTTP Connector
[ https://issues.apache.org/jira/browse/GERONIMO-3389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720579#action_12720579 ] Shawn Jiang commented on GERONIMO-3389: --- Documents updated for this JIRA. http://cwiki.apache.org/confluence/display/GMOxDOC21/Adding+new+listeners+for+the+Web+containers http://cwiki.apache.org/confluence/display/GMOxDOC22/Adding+new+listeners I found the message "you must install apr local lib before adding new apr connctor" message is also shown in jetty release. It should be removed from jetty release because jetty does not support apr connector. I'll upload a patch later. > console: java.lang.UnsatisfiedLinkError is thrown when create a Tomcat APR > HTTP Connector > - > > Key: GERONIMO-3389 > URL: https://issues.apache.org/jira/browse/GERONIMO-3389 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: documentation, Tomcat >Affects Versions: 2.0, 2.0.1, 2.0.2, 2.0.x, 2.1, 2.1.1, 2.1.x, 2.2 > Environment: Windows xp sp2, IE, Firefox >Reporter: Song >Assignee: Shawn Jiang > Fix For: 2.1.5, 2.2 > > Attachments: G3389_g21.patch, G3389_trunk.patch > > > Click on "Save" button after entering all necessary parameters for creating > a new Tomcat APR HTTP Connector "test_APR_HTTP", it returned to the Network > Listeners list page. However,the Protocol for test_APR_HTTP is empty, State > is failed. And java.lang.UnsatisfiedLinkError is thrown from the server > started console and server.log. > Same error to creating Tomcat APR HTTPS Connetor. > > Detailed error as below: > -- > 13:33:46,515 WARN [ConnectorGBean] test_APR_HTTP connector failed > 13:33:46,515 ERROR [Connector] Coyote connector has not been started > 13:33:46,515 ERROR [GBeanInstanceState] Error while starting; GBean is now in > the FAILED state: > abstractName="org.apache.geronimo.configs/tomcat6/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/tomcat6/2.0-SNAPSHOT/car,j2eeType=GBean,name=test_APR_HTTP" > java.lang.UnsatisfiedLinkError: org/apache/tomcat/jni/Pool.create(J)J > at org.apache.tomcat.util.net.AprEndpoint.init(AprEndpoint.java:579) > at > org.apache.coyote.http11.Http11AprProtocol.init(Http11AprProtocol.java:121) > at > org.apache.catalina.connector.Connector.initialize(Connector.java:1059) > at > org.apache.catalina.core.StandardService.addConnector(StandardService.java:267) > at org.apache.catalina.startup.Embedded.addConnector(Embedded.java:327) > at > org.apache.geronimo.tomcat.TomcatContainer.addConnector(TomcatContainer.java:383) > at > org.apache.geronimo.tomcat.TomcatContainer$$FastClassByCGLIB$$9370b073.invoke() > at net.sf.cglib.reflect.FastMethod.invoke(FastMethod.java:53) > at > org.apache.geronimo.gbean.runtime.FastMethodInvoker.invoke(FastMethodInvoker.java:38) > at > org.apache.geronimo.gbean.runtime.GBeanOperation.invoke(GBeanOperation.java:124) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.invoke(GBeanInstance.java:830) > at > org.apache.geronimo.gbean.runtime.RawInvoker.invoke(RawInvoker.java:57) > at > org.apache.geronimo.kernel.basic.RawOperationInvoker.invoke(RawOperationInvoker.java:35) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > at > org.apache.geronimo.tomcat.TomcatContainer$$EnhancerByCGLIB$$fa3733e1.addConnector() > at > org.apache.geronimo.tomcat.connector.ConnectorGBean.doStart(ConnectorGBean.java:95) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.createInstance(GBeanInstance.java:996) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.attemptFullStart(GBeanInstanceState.java:268) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.start(GBeanInstanceState.java:102) > at > org.apache.geronimo.gbean.runtime.GBeanInstanceState.startRecursive(GBeanInstanceState.java:124) > at > org.apache.geronimo.gbean.runtime.GBeanInstance.startRecursive(GBeanInstance.java:553) > at > org.apache.geronimo.kernel.basic.BasicKernel.startRecursiveGBean(BasicKernel.java:379) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor$StartRecursiveInvoke.invoke(ProxyMethodInterceptor.java:365) > at > org.apache.geronimo.kernel.basic.ProxyMethodInterceptor.intercept(ProxyMethodInterceptor.java:96) > at > org.apache.geronimo.tomcat.connector.Http11APRProtocol$$EnhancerByCGLIB$$abc46ac2.startRecursive() > at > org.apache.geronimo.console.webmanager.ConnectorPortlet.processAction(ConnectorP
[jira] Issue Comment Edited: (GERONIMO-4587) Array security issue
[
https://issues.apache.org/jira/browse/GERONIMO-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720576#action_12720576
]
Shawn Jiang edited comment on GERONIMO-4587 at 6/17/09 2:11 AM:
It turned out to be a jacc spec defect. There are two constructor used to
construct the MethodSpec of a EJB method.
1, MethodSpec(String mthdInterface, Method method)
2, MethodSpec(String mthdName, String mthdInterface, String[] methodParamsArray)
When a EJB method is like get(int[] a).
#1 will return a methodParams as *[I* while #2 always get *int[]* passed
in. So that #1.methodParams will always not equal to #2 in this case.
was (Author: genspring):
It turned out to be a jacc spec defect. There are two constructor used to
construct the MethodSpec of a EJB method.
1, MethodSpec(String mthdInterface, Method method)
2, MethodSpec(String mthdName, String mthdInterface, String[] methodParamsArray)
When a EJB method is like get(int[] a).
#1 will return a methodParams as *[I* while #2 always get *int[]" passed
in. So that #1.methodParams will always not equal to #2 in this case.
> Array security issue
>
>
> Key: GERONIMO-4587
> URL: https://issues.apache.org/jira/browse/GERONIMO-4587
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security
>Affects Versions: 2.2
> Environment: Java 6 on OS X 10.5.
>Reporter: Trygve Hardersen
>Assignee: Shawn Jiang
> Attachments: G4587.patch
>
>
> We have a stateless session bean called SSB, with a method called getX:
> SSB#getX(java.lang.String)
> Our security model has 5 roles; admin, anonymous, customer, partner and
> system. Users can only be in one role. SSB is accessible for all roles, but
> the getX method does not allow anonymous access. So we have these annotations:
> @DeclareRoles({
> Constants.ROLE_ADMIN,
> Constants.ROLE_ANONYMOUS,
> Constants.ROLE_CUSTOMER,
> Constants.ROLE_PARTNER,
> Constants.ROLE_SYSTEM})
> public class SSB
> @RolesAllowed({
> Constants.ROLE_ADMIN,
> Constants.ROLE_CUSTOMER,
> Constants.ROLE_PARTNER,
> Constants.ROLE_SYSTEM})
> public X getX(String y)
> In out test suite I have a simple test case to verify that access by users in
> the anonymous role (unauthenticated web users) is not permitted for the getX
> method:
> SSB anonymous_service = LOG_IN_AS_ANONYMOUS_USER
> X obj = null;
> EJBAccessException eae = null;
> try{
> obj = anonymous_service.getX("test")
> ;
> }catch (EJBAccessException e) {
> eae = e;
> }
> Assert.assertNull(obj);
> Assert.assertNotNull(eae);
> Assert.assertEquals(eae.getMessage(), "Unauthorized Access by Principal
> Denied");
> We've not had issues with this test case for months. However yesterday we
> decided to change the method signature of getX to support an optional list of
> int flags than control the object initialization (which related records to
> get from the DB):
> public X getX(String y, int... flags)
> After this the test shown above fails. An object is returned back and no
> exception is raised. The security system still works; we can check the user
> manually using the SessionContext resource. But the container authorization
> does not trigger.
> We have also confirmed that the security system fails if a "proper array" is
> used instead of the "vararg array". We have not had a chance to test whether
> using a XML-based configuration solves the issue.
> Since the security system is accessible through the SessionContext we work
> around this issue by manually checking the user role from our code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4587) Array security issue
[
https://issues.apache.org/jira/browse/GERONIMO-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated GERONIMO-4587:
--
Patch Info: [Patch Available]
This defect can be found in geronimo-jacc_1.1_spec 1.0.1 release and 1.0.2
snapshot.
The patch is for 1.0.2 snapshot. Thanks.
> Array security issue
>
>
> Key: GERONIMO-4587
> URL: https://issues.apache.org/jira/browse/GERONIMO-4587
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security
>Affects Versions: 2.2
> Environment: Java 6 on OS X 10.5.
>Reporter: Trygve Hardersen
>Assignee: Shawn Jiang
> Attachments: G4587.patch
>
>
> We have a stateless session bean called SSB, with a method called getX:
> SSB#getX(java.lang.String)
> Our security model has 5 roles; admin, anonymous, customer, partner and
> system. Users can only be in one role. SSB is accessible for all roles, but
> the getX method does not allow anonymous access. So we have these annotations:
> @DeclareRoles({
> Constants.ROLE_ADMIN,
> Constants.ROLE_ANONYMOUS,
> Constants.ROLE_CUSTOMER,
> Constants.ROLE_PARTNER,
> Constants.ROLE_SYSTEM})
> public class SSB
> @RolesAllowed({
> Constants.ROLE_ADMIN,
> Constants.ROLE_CUSTOMER,
> Constants.ROLE_PARTNER,
> Constants.ROLE_SYSTEM})
> public X getX(String y)
> In out test suite I have a simple test case to verify that access by users in
> the anonymous role (unauthenticated web users) is not permitted for the getX
> method:
> SSB anonymous_service = LOG_IN_AS_ANONYMOUS_USER
> X obj = null;
> EJBAccessException eae = null;
> try{
> obj = anonymous_service.getX("test")
> ;
> }catch (EJBAccessException e) {
> eae = e;
> }
> Assert.assertNull(obj);
> Assert.assertNotNull(eae);
> Assert.assertEquals(eae.getMessage(), "Unauthorized Access by Principal
> Denied");
> We've not had issues with this test case for months. However yesterday we
> decided to change the method signature of getX to support an optional list of
> int flags than control the object initialization (which related records to
> get from the DB):
> public X getX(String y, int... flags)
> After this the test shown above fails. An object is returned back and no
> exception is raised. The security system still works; we can check the user
> manually using the SessionContext resource. But the container authorization
> does not trigger.
> We have also confirmed that the security system fails if a "proper array" is
> used instead of the "vararg array". We have not had a chance to test whether
> using a XML-based configuration solves the issue.
> Since the security system is accessible through the SessionContext we work
> around this issue by manually checking the user role from our code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (GERONIMO-4587) Array security issue
[
https://issues.apache.org/jira/browse/GERONIMO-4587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shawn Jiang updated GERONIMO-4587:
--
Attachment: G4587.patch
It turned out to be a jacc spec defect. There are two constructor used to
construct the MethodSpec of a EJB method.
1, MethodSpec(String mthdInterface, Method method)
2, MethodSpec(String mthdName, String mthdInterface, String[] methodParamsArray)
When a EJB method is like get(int[] a).
#1 will return a methodParams as *[I* while #2 always get *int[]" passed
in. So that #1.methodParams will always not equal to #2 in this case.
> Array security issue
>
>
> Key: GERONIMO-4587
> URL: https://issues.apache.org/jira/browse/GERONIMO-4587
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: security
>Affects Versions: 2.2
> Environment: Java 6 on OS X 10.5.
>Reporter: Trygve Hardersen
>Assignee: Shawn Jiang
> Attachments: G4587.patch
>
>
> We have a stateless session bean called SSB, with a method called getX:
> SSB#getX(java.lang.String)
> Our security model has 5 roles; admin, anonymous, customer, partner and
> system. Users can only be in one role. SSB is accessible for all roles, but
> the getX method does not allow anonymous access. So we have these annotations:
> @DeclareRoles({
> Constants.ROLE_ADMIN,
> Constants.ROLE_ANONYMOUS,
> Constants.ROLE_CUSTOMER,
> Constants.ROLE_PARTNER,
> Constants.ROLE_SYSTEM})
> public class SSB
> @RolesAllowed({
> Constants.ROLE_ADMIN,
> Constants.ROLE_CUSTOMER,
> Constants.ROLE_PARTNER,
> Constants.ROLE_SYSTEM})
> public X getX(String y)
> In out test suite I have a simple test case to verify that access by users in
> the anonymous role (unauthenticated web users) is not permitted for the getX
> method:
> SSB anonymous_service = LOG_IN_AS_ANONYMOUS_USER
> X obj = null;
> EJBAccessException eae = null;
> try{
> obj = anonymous_service.getX("test")
> ;
> }catch (EJBAccessException e) {
> eae = e;
> }
> Assert.assertNull(obj);
> Assert.assertNotNull(eae);
> Assert.assertEquals(eae.getMessage(), "Unauthorized Access by Principal
> Denied");
> We've not had issues with this test case for months. However yesterday we
> decided to change the method signature of getX to support an optional list of
> int flags than control the object initialization (which related records to
> get from the DB):
> public X getX(String y, int... flags)
> After this the test shown above fails. An object is returned back and no
> exception is raised. The security system still works; we can check the user
> manually using the SessionContext resource. But the container authorization
> does not trigger.
> We have also confirmed that the security system fails if a "proper array" is
> used instead of the "vararg array". We have not had a chance to test whether
> using a XML-based configuration solves the issue.
> Since the security system is accessible through the SessionContext we work
> around this issue by manually checking the user role from our code.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Assemblies in the repo and their dependencies
Why do the assemblies in the repository have dependencies? I realize that they are probably there to facilitate the build, but shouldn't they all be marked as provided? The reason I think they should be, is that when a user wants to use the geronimo-maven-plugin with the assembly -bin in the repository, before they can even download the assembly -bin, first mvn has to go resolve every single dependency which is used to build that assembly - bin. I think this is broken, while I can resolve by adding a tone of excludes, I think that this problem should be solved so that users can more easily consume the assembly artifacts we publish to the repository. Any one know how easy/feasible with the current stuff (trunk and 2.1.x) it would be to mark all dependencies as provided? --jason
[jira] Resolved: (GERONIMO-4663) Improvement of "New Server Instance via plugins-GERONIMO-4382"
[ https://issues.apache.org/jira/browse/GERONIMO-4663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Rodger Zhang resolved GERONIMO-4663. Resolution: Fixed Fix Version/s: 2.2 Ok, it has been fixed. > Improvement of "New Server Instance via plugins-GERONIMO-4382" > -- > > Key: GERONIMO-4663 > URL: https://issues.apache.org/jira/browse/GERONIMO-4663 > Project: Geronimo > Issue Type: Improvement > Security Level: public(Regular issues) > Components: commands, Plugins >Affects Versions: 2.2 >Reporter: Rodger Zhang > Fix For: 2.2 > > > When using gshell command deploy/new-instance to new a instance of the server, > an error happens in start-server window: > ERROR [PluginInstallerGBean] Unable to install plugin > java.lang.IllegalArgumentException: Could not find > org.apache.geronimo.plugingro > ups/framework/2.2-SNAPSHOT/car in any repo: > [org.apache.geronimo.system.plugin.GeronimoSourceRepository]. > Because in directory > /repository/org/apache/geronimo/plugingroups, no directory > /framework (a plugin) exists, we must copy /framework from > /repository/org/apache/geronimo/framework/plugingroups (It is > a plugin "framework-2.2-SNAPSHOT.car") firstly. > I think it is inconvenient for users,so why not put the plugin in the right > position? > Or maybe it is a bug that in the code there is a path must point to the > second directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
