[jira] [Resolved] (GERONIMO-6443) Bundles resolve even though package uses conflict error is reported during EBA deployment
[ https://issues.apache.org/jira/browse/GERONIMO-6443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6443. --- Resolution: Fixed Resolving as the work-around seems to be working ok. Bundles resolve even though package uses conflict error is reported during EBA deployment Key: GERONIMO-6443 URL: https://issues.apache.org/jira/browse/GERONIMO-6443 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor During EBA deployment uses directive conflict errors are reported and the given bundles are left in Installed state. However, starting or resolving the bundles again is successful (and the bundles move to Active or Resolved state). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-809) In-use port detection does not work sometimes
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-809. -- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as the new port checking seems to be working as expected. In-use port detection does not work sometimes - Key: GERONIMODEVTOOLS-809 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-809 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 3.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Before starting a server, GEP checks if the http and naming ports are free. This check does not work sometimes on some platforms (e.g. Windows). That's because on Windows it is possible to bind to 0.0.0.0 (any/all network interfaces) and 127.0.0.1 with the same port at the same time. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (XBEAN-242) Potential file descriptor leak in BundleResourceFinder
[ https://issues.apache.org/jira/browse/XBEAN-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor closed XBEAN-242. - Resolution: Fixed Fix Version/s: 3.13 Fixed. Potential file descriptor leak in BundleResourceFinder -- Key: XBEAN-242 URL: https://issues.apache.org/jira/browse/XBEAN-242 Project: XBean Issue Type: Bug Components: bundleutils Affects Versions: 3.12 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.13 BundleResourceFinder opens ZipInputStream but never explicitly closes it. That can potentially lead to file descriptor leaks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-795) Synchronizing port configuration
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-795. -- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as it works as expected. Synchronizing port configuration Key: GERONIMODEVTOOLS-795 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-795 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Currently, GEP keep its own port configuration, separate from the server's configuration. The port information between GEP server is not synchronized in any way. And sometimes as the port information between the server GEP becomes out of synch, it creates problems for users when starting or deploying modules to the server from GEP. It would be nice to update the GEP to keep the port information in synch with the server. That is, if the server configuration is changed, that change is reflected in GEP. And if the change in made in GEP, the server configuration is updated as well. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6417) Launch listener
[ https://issues.apache.org/jira/browse/GERONIMO-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6417. --- Resolution: Fixed Fix Version/s: 3.0.1 Launch listener --- Key: GERONIMO-6417 URL: https://issues.apache.org/jira/browse/GERONIMO-6417 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: startup/shutdown Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Add support for launch listeners. This is so that one can register a listener to receive events about launcher starting and stopping the runtime in order to perform custom action based on those events. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6445) Support configuration imports
[ https://issues.apache.org/jira/browse/GERONIMO-6445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6445. --- Resolution: Fixed Fix Version/s: 3.0.1 Support configuration imports -- Key: GERONIMO-6445 URL: https://issues.apache.org/jira/browse/GERONIMO-6445 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: kernel Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Add support for configuration imports for config.properties and system.properties files. That will make it simpler to have separate configuration files for command line tools and server without duplicating the configuration information. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5166) Enable car-maven-plugin to use Equinox
[ https://issues.apache.org/jira/browse/GERONIMO-5166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5166. --- Resolution: Fixed Fix Version/s: 3.0.0 Resolving as this is done and we are / were building with Equinox for a while. Enable car-maven-plugin to use Equinox -- Key: GERONIMO-5166 URL: https://issues.apache.org/jira/browse/GERONIMO-5166 Project: Geronimo Issue Type: Sub-task Security Level: public(Regular issues) Components: car-maven-plugin Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1, 3.0.0 Ability for car-maven-plugin to switch between Felix or Equinox as the OSGi framework. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-5231) Override JVM libraries with newer versions
[ https://issues.apache.org/jira/browse/GERONIMO-5231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-5231. --- Resolution: Fixed Fix Version/s: (was: 3.0.1) 3.0.0 This was done/enabled a while ago. Forgot to close it. Override JVM libraries with newer versions -- Key: GERONIMO-5231 URL: https://issues.apache.org/jira/browse/GERONIMO-5231 Project: Geronimo Issue Type: Bug Security Level: public(Regular issues) Components: buildsystem Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.0 In some cases, Java EE 6 requires newer library versions then what is provided by Java SE 6. For example, EE 6 requires annotations 1.1 api but SE 6 provides annotation 1.0 api. So it is necessary that during a build we override the JVM provided libraries with newer versions. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6434) in-place deployment for OSGi applications
[ https://issues.apache.org/jira/browse/GERONIMO-6434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6434. --- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as in-place deployment of OSGi applications seems to be working now. in-place deployment for OSGi applications - Key: GERONIMO-6434 URL: https://issues.apache.org/jira/browse/GERONIMO-6434 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Add support for in-place deployment of OSGi applications. That is, the contents of the .eba archive and its bundles are expanded on disk. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6397) Improve resolver-based error messages for OSGi application
[ https://issues.apache.org/jira/browse/GERONIMO-6397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6397. --- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as this work is done. Improve resolver-based error messages for OSGi application -- Key: GERONIMO-6397 URL: https://issues.apache.org/jira/browse/GERONIMO-6397 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Improve ResolverErrorAnalyzer for OSGi applications. Specifically in cases where a import package cannot be satisfied provide details if the given package is exported by any bundles or if there are bundles that export that package with different version, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMO-6319) Discover and provision fragment bundles during OSGi application resolution
[ https://issues.apache.org/jira/browse/GERONIMO-6319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMO-6319. --- Resolution: Fixed Fix Version/s: 3.0.1 Resolving as this work is done. Discover and provision fragment bundles during OSGi application resolution -- Key: GERONIMO-6319 URL: https://issues.apache.org/jira/browse/GERONIMO-6319 Project: Geronimo Issue Type: New Feature Security Level: public(Regular issues) Components: Aries Affects Versions: 3.0-beta-1 Reporter: Jarek Gawor Assignee: Jarek Gawor Fix For: 3.0.1 Add support for discovering and provisioning fragment bundles during OSGi application resolution. The application resolver will look for one fragment per application bundle. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-235) Plugin cannot synchronize with the server when non-zero portOffset value in the config-substitutions.properties file
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-235. -- Resolution: Fixed Fix Version/s: (was: 2.2.2) 3.0.1 WIth GERONIMODEVTOOLS-795 GEP will tell the server what ports to use. Plugin cannot synchronize with the server when non-zero portOffset value in the config-substitutions.properties file Key: GERONIMODEVTOOLS-235 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-235 Project: Geronimo-Devtools Issue Type: Bug Components: eclipse-plugin Affects Versions: 2.0.0 Reporter: Tim McConnell Fix For: 3.0.1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-695) Synchronize dependency version with Geronimo 3.0 M2
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-695. -- Resolution: Fixed This is/was already done. Synchronize dependency version with Geronimo 3.0 M2 --- Key: GERONIMODEVTOOLS-695 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-695 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Han Hong Fang Assignee: Han Hong Fang Fix For: 3.0-M2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-714) Synchronize the server configuration between GEP and server
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-714?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-714. -- Resolution: Duplicate This is duplicate of GERONIMODEVTOOLS-795. Synchronize the server configuration between GEP and server --- Key: GERONIMODEVTOOLS-714 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-714 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 2.2.1, 2.1.7, 3.0 Reporter: Han Hong Fang Currently GEP has server configuration such as administrator id, administrator password, HTTP port value and RMI Naming port value. These are set with default values when server is created. Although the values can be modified during server creation or after server creation, this can be improved by reading such values from server configuration files when runtime is located on local machine. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-762) GEP needs a nightly builds repositary
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-762. -- Resolution: Fixed Resolving as the latest deployable and p2 zip are now automatically published after each change at https://repository.apache.org/content/groups/snapshots/org/apache/geronimo/devtools/assembly/ GEP needs a nightly builds repositary - Key: GERONIMODEVTOOLS-762 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-762 Project: Geronimo-Devtools Issue Type: Wish Components: eclipse-plugin Affects Versions: 3.0 Reporter: Yi Xiao Assignee: Yi Xiao Labels: build, gep,, nightly Attachments: gep_nightly_build_new.patch The GEP had a nightly build repo before(refer to: http://geronimo.apache.org/development-tools.html#DevelopmentTools-NightlyBuilds), but it does not work now. So, I thought we should set up a environment to redo it. I've attached a patch to resolve the issue temporally. If you want to test it in your local environment, should add below content to your maven's settings.xml file: server idgeronimo-devtools-nightly-repo/id usernamepeople.apache.org.username/username passwordpeople.apache.org.password/password /server Thank Janet for helping me test to upload the devtools onto the apache site. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (GERONIMODEVTOOLS-706) Consider enabling Karaf shell in Eclipse console
[ https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jarek Gawor resolved GERONIMODEVTOOLS-706. -- Resolution: Fixed Fix Version/s: 3.0.1 This feature is implemented now. Consider enabling Karaf shell in Eclipse console Key: GERONIMODEVTOOLS-706 URL: https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-706 Project: Geronimo-Devtools Issue Type: Improvement Components: eclipse-plugin Affects Versions: 3.0-M2 Reporter: Jarek Gawor Assignee: Ted Kirby Fix For: 3.0.1 Attachments: enableKarafShell_706_m0.patch, enableKarafShell_706_m1.patch, enableKarafShell_706.patch, karafSSHTerminal_improvement.jpg, karafSSHTerminal.jpg (If possible) I think it would be pretty nice to have an option to enable and access Karaf shell directly in Eclipse console window. If that can be done make sure to start Geronimo server with -Djline.terminal=jline.UnsupportedTerminal option. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6446) Build with Java 7
[
https://issues.apache.org/jira/browse/GERONIMO-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13630284#comment-13630284
]
Kevan Miller commented on GERONIMO-6446:
FYI, I'm seeing the following:
{code}
Exception in thread main java.lang.AssertionError: Missing tools.jar at:
/Library/Java/JavaVirtualMachines/jdk1.7.0_17.jdk/Contents/Home/Classes/classes.jar.
Expression: file.exists()
at
org.codehaus.groovy.runtime.InvokerHelper.assertFailed(InvokerHelper.java:395)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.assertFailed(ScriptBytecodeAdapter.java:683)
at
org.codehaus.mojo.jspc.CompilationMojoSupport.findToolsJar(CompilationMojoSupport.groovy:371)
at
org.codehaus.mojo.jspc.CompilationMojoSupport.this$4$findToolsJar(CompilationMojoSupport.groovy)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.groovy.reflection.CachedMethod.invoke(CachedMethod.java:86)
at groovy.lang.MetaMethod.doMethodInvoke(MetaMethod.java:230)
at groovy.lang.MetaClassImpl.invokeMethod(MetaClassImpl.java:912)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodOnCurrentN(ScriptBytecodeAdapter.java:78)
at
org.codehaus.groovy.runtime.ScriptBytecodeAdapter.invokeMethodOnCurrent0(ScriptBytecodeAdapter.java:112)
at
org.codehaus.mojo.jspc.CompilationMojoSupport.execute(CompilationMojoSupport.groovy:318)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:319)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
{code}
in
{code}
[INFO]
[INFO] Building Geronimo Plugins, System Database :: Portlets 3.0.1-SNAPSHOT
[INFO]
{code}
This must be a known/resolved problem... My first google search didn't turn up
anything...
Build with Java 7
-
Key: GERONIMO-6446
URL: https://issues.apache.org/jira/browse/GERONIMO-6446
Project: Geronimo
Issue Type: Improvement
Security Level: public(Regular issues)
Components: buildsystem
Affects Versions: 3.0.0
Reporter: Jarek Gawor
Assignee: Jarek Gawor
Ensure that 3.0 branch builds with Java 7.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (GERONIMO-6446) Build with Java 7
[ https://issues.apache.org/jira/browse/GERONIMO-6446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13630901#comment-13630901 ] Jarek Gawor commented on GERONIMO-6446: --- Looks like this is a known issue in the jspc plugin - see https://jira.codehaus.org/browse/MJSPC-53. There is a work-around but there is no fixed version of the plugin. Build with Java 7 - Key: GERONIMO-6446 URL: https://issues.apache.org/jira/browse/GERONIMO-6446 Project: Geronimo Issue Type: Improvement Security Level: public(Regular issues) Components: buildsystem Affects Versions: 3.0.0 Reporter: Jarek Gawor Assignee: Jarek Gawor Ensure that 3.0 branch builds with Java 7. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
