[jira] Created: (FELIX-2771) Configuration Admin does not work on Foundation 1.2 and Mika
Configuration Admin does not work on Foundation 1.2 and Mika Key: FELIX-2771 URL: https://issues.apache.org/jira/browse/FELIX-2771 Project: Felix Issue Type: Bug Components: Configuration Admin Affects Versions: configadmin-1.2.8 Reporter: Clement Escoffier Priority: Minor The configuration admin implementation uses classes and methods not available in Foundation and/or Mika. In Foundation: The method getCause() is undefined for the type PrivilegedActionException The method valueOf(String) in the type Boolean does not exist for the arguments (boolean) On Mika, the SecureRandom class is not available: couldn't find a SecureRandom at java.security.SecureRandom.(SecureRandom.java:78) at org.apache.felix.cm.impl.ConfigurationManager.createPid(ConfigurationManager.java:870) at org.apache.felix.cm.impl.ConfigurationManager.createFactoryConfiguration(ConfigurationManager.java:450) at org.apache.felix.cm.impl.ConfigurationAdminImpl.createFactoryConfiguration(ConfigurationAdminImpl.java:84) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1946) jetty http service issues 'started' message when disabled
[ https://issues.apache.org/jira/browse/FELIX-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Baum closed FELIX-1946. - > jetty http service issues 'started' message when disabled > - > > Key: FELIX-1946 > URL: https://issues.apache.org/jira/browse/FELIX-1946 > Project: Felix > Issue Type: Bug > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Derek Baum >Assignee: Felix Meschberger >Priority: Minor > Fix For: http-2.0.6 > > > I want to configure the felix jetty http service using config admin, so I set > the following properties to stop it from starting automatically: > org.osgi.service.http.port = -1 > org.apache.felix.http.enable = false > However, when the bundle is activated, it still reports that it has started: > % [INFO] Started jetty 6.1.x at port -1 > A 'Jetty HTTP Service' thread is actually started, but as http is not > enabled, no http server connector is created. > The above 'Started' message should not appear when http (and https) are > disabled, and it would be good if the 'Jetty HTTP Service' was not created > until the service is enabled using config admin, for example: > % setpid org.apache.felix.http org.osgi.service.http.port==1234 > org.apache.felix.http.enable==true > % [INFO] Started jetty 6.1.x at port 1234 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-2772) setting http.port=-1 should disable service rather than throw exception
setting http.port=-1 should disable service rather than throw exception --- Key: FELIX-2772 URL: https://issues.apache.org/jira/browse/FELIX-2772 Project: Felix Issue Type: Improvement Components: HTTP Service Reporter: Derek Baum Priority: Minor I want to stop http.jetty from starting automatically, as I want to ensure the correct port is first explicitly configured using config admin. I can currently do this by setting org.apache.felix.http.enable=false, but this then complicates starting the service, as I have to set both http.enable=true and http.port=PORT It would be useful if setting http.port=-1 effectively disabled the service, then just by using config admin to set a valid port the service would start. Currently setting http.port=-1 results in the following exception: [WARNING] failed selectchannelconnec...@0.0.0.0:-1: java.lang.IllegalArgumentException: port out of range:-1 [WARNING] failed ser...@1f195fc: java.lang.IllegalArgumentException: port out of range:-1 [ERROR] Exception while initializing Jetty. java.lang.IllegalArgumentException: port out of range:-1 at java.net.InetSocketAddress.(InetSocketAddress.java:83) The Equinox http service is disabled if http.port=-1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2770) maven-scr-plugin 1.6.0 incompatible with pom projects
[
https://issues.apache.org/jira/browse/FELIX-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979324#action_12979324
]
Ben Alex commented on FELIX-2770:
-
Yes, we are using it for inheritance. I know you can use the technique
mentioned, but the problem is we have 52 modules which would then need a
entry. It is preferable for us to use inheritance and not require the
entry duplication.
> maven-scr-plugin 1.6.0 incompatible with pom projects
>
>
> Key: FELIX-2770
> URL: https://issues.apache.org/jira/browse/FELIX-2770
> Project: Felix
> Issue Type: Bug
> Components: Maven SCR Plugin
>Affects Versions: scr-1.6.0
> Environment: Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-23-generic" arch: "i386" Family: "unix"
>Reporter: Ben Alex
>
> maven-scr-plugin 1.6.0 when defined in a pom.xml that is of type
> pom yields an exception during a Maven 2.2.1 reactor
> build:
> {code}
> java.lang.IllegalStateException: basedir
> /home/balex/projects/roo/osgi-roo-bundle/src/main/java does not exist
> at
> org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:290)
> at
> org.apache.felix.scrplugin.mojo.MavenJavaClassDescriptorManager.getSourceFiles(MavenJavaClassDescriptorManager.java:97)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getSources(JavaClassDescriptorManager.java:109)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getJavaClassesFromSources(JavaClassDescriptorManager.java:446)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getSourceDescriptions(JavaClassDescriptorManager.java:362)
> at
> org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:233)
> at
> org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:184)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at 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)
> {code}
> It is typical to use a pom in a parent module in large
> OSGi systems such as Spring Roo. Such modules don't have src/main/java
> directories as there is no Java code contained within them.
> This bug is not present when using maven-scr-plugin 1.4.4 and below.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: HTTP Service Release
+1 -> richard On 01/08/2011 11:14 PM, Felix Meschberger wrote: Hi all, I have fixed a few issues of the HTTP Service implementations (mostly Jetty support stuff) and have deployed SNAPSHOTs of all bundles. The list of fixed bug since the 2.0.4 release can be found at https://issues.apache.org/jira/browse/FELIX/fixforversion/12314431 For an upcoming 2.0.6 (or 2.1.0 instead) Release I still consider these following bugs: FELIX-2292 Upgrade to jetty 7.0 (org.eclipse.jetty 7.0.2v20100331) FELIX-1962 Add support for (select) Servlet API listeners I would like to drop the following bugs from the release plan: FELIX-2137 Make it possible to set servlet/filter name FELIX-1963 Add possibility to share ServletContext between bundles Basically, I do not have a good idea on how to do this and there is no patch currently attached to any of these bugs. WDYT ? Regards Felix
Re: Q on R4.2 Spec Compliance
On Wed, Dec 15, 2010 at 04:45, Ikuo Yamasaki wrote: > Felix, and David, > > Thank you for your reply. > I understand about the framework stuff. > > If anyone can provide information or a web page provides those info, it > would be very helpful, especially for newcomers to adopt Felix impl. > > Best regards, > > On Tue, 14 Dec 2010 14:42:23 +0100 > Felix Meschberger wrote: > > Felix> These I don't know the exact compliance state: > Felix> -- Http Service (might be reasonably complete) > Felix> -- Deployment Admin > Felix> -- Log Service > Felix> -- Event Admin (IIRC passes the CT) > Felix> -- UPNP The current OSGi UPnP Base Driver implementation covers almost all the specification but it doesn't only the following items: - support of icon file - configuration of the multicast address for discovery by means of Config Admin service > Felix> -- Command Shell > Felix> -- Wire Admin > Felix> -- Preferences Services >
[jira] Assigned: (FELIX-2770) maven-scr-plugin 1.6.0 incompatible with pom projects
[
https://issues.apache.org/jira/browse/FELIX-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler reassigned FELIX-2770:
---
Assignee: Carsten Ziegeler
> maven-scr-plugin 1.6.0 incompatible with pom projects
>
>
> Key: FELIX-2770
> URL: https://issues.apache.org/jira/browse/FELIX-2770
> Project: Felix
> Issue Type: Bug
> Components: Maven SCR Plugin
>Affects Versions: scr-1.6.0
> Environment: Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-23-generic" arch: "i386" Family: "unix"
>Reporter: Ben Alex
>Assignee: Carsten Ziegeler
>
> maven-scr-plugin 1.6.0 when defined in a pom.xml that is of type
> pom yields an exception during a Maven 2.2.1 reactor
> build:
> {code}
> java.lang.IllegalStateException: basedir
> /home/balex/projects/roo/osgi-roo-bundle/src/main/java does not exist
> at
> org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:290)
> at
> org.apache.felix.scrplugin.mojo.MavenJavaClassDescriptorManager.getSourceFiles(MavenJavaClassDescriptorManager.java:97)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getSources(JavaClassDescriptorManager.java:109)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getJavaClassesFromSources(JavaClassDescriptorManager.java:446)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getSourceDescriptions(JavaClassDescriptorManager.java:362)
> at
> org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:233)
> at
> org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:184)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at 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)
> {code}
> It is typical to use a pom in a parent module in large
> OSGi systems such as Spring Roo. Such modules don't have src/main/java
> directories as there is no Java code contained within them.
> This bug is not present when using maven-scr-plugin 1.4.4 and below.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2770) maven-scr-plugin 1.6.0 incompatible with pom projects
[
https://issues.apache.org/jira/browse/FELIX-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979381#action_12979381
]
Carsten Ziegeler commented on FELIX-2770:
-
Yes, I think we should check if the dir exists, and skip execution if not
> maven-scr-plugin 1.6.0 incompatible with pom projects
>
>
> Key: FELIX-2770
> URL: https://issues.apache.org/jira/browse/FELIX-2770
> Project: Felix
> Issue Type: Bug
> Components: Maven SCR Plugin
>Affects Versions: scr-1.6.0
> Environment: Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-23-generic" arch: "i386" Family: "unix"
>Reporter: Ben Alex
>Assignee: Carsten Ziegeler
>
> maven-scr-plugin 1.6.0 when defined in a pom.xml that is of type
> pom yields an exception during a Maven 2.2.1 reactor
> build:
> {code}
> java.lang.IllegalStateException: basedir
> /home/balex/projects/roo/osgi-roo-bundle/src/main/java does not exist
> at
> org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:290)
> at
> org.apache.felix.scrplugin.mojo.MavenJavaClassDescriptorManager.getSourceFiles(MavenJavaClassDescriptorManager.java:97)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getSources(JavaClassDescriptorManager.java:109)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getJavaClassesFromSources(JavaClassDescriptorManager.java:446)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getSourceDescriptions(JavaClassDescriptorManager.java:362)
> at
> org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:233)
> at
> org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:184)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at 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)
> {code}
> It is typical to use a pom in a parent module in large
> OSGi systems such as Spring Roo. Such modules don't have src/main/java
> directories as there is no Java code contained within them.
> This bug is not present when using maven-scr-plugin 1.4.4 and below.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-2772) setting http.port=-1 should disable service rather than throw exception
[ https://issues.apache.org/jira/browse/FELIX-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned FELIX-2772: Assignee: Felix Meschberger > setting http.port=-1 should disable service rather than throw exception > --- > > Key: FELIX-2772 > URL: https://issues.apache.org/jira/browse/FELIX-2772 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Derek Baum >Assignee: Felix Meschberger >Priority: Minor > Fix For: http-2.0.6 > > > I want to stop http.jetty from starting automatically, as I want to ensure > the correct port is first explicitly configured using config admin. > I can currently do this by setting org.apache.felix.http.enable=false, but > this then complicates starting the service, as I have to set both > http.enable=true and http.port=PORT > It would be useful if setting http.port=-1 effectively disabled the service, > then just by using config admin to set a valid port the service would start. > Currently setting http.port=-1 results in the following exception: > [WARNING] failed selectchannelconnec...@0.0.0.0:-1: > java.lang.IllegalArgumentException: port out of range:-1 > [WARNING] failed ser...@1f195fc: java.lang.IllegalArgumentException: port out > of range:-1 > [ERROR] Exception while initializing Jetty. > java.lang.IllegalArgumentException: port out of range:-1 > at java.net.InetSocketAddress.(InetSocketAddress.java:83) > The Equinox http service is disabled if http.port=-1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2772) setting http.port=-1 should disable service rather than throw exception
[ https://issues.apache.org/jira/browse/FELIX-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger updated FELIX-2772: - Affects Version/s: http-2.0.4 Fix Version/s: http-2.0.6 Sounds reasonable. Scheduling for next release > setting http.port=-1 should disable service rather than throw exception > --- > > Key: FELIX-2772 > URL: https://issues.apache.org/jira/browse/FELIX-2772 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Derek Baum >Assignee: Felix Meschberger >Priority: Minor > Fix For: http-2.0.6 > > > I want to stop http.jetty from starting automatically, as I want to ensure > the correct port is first explicitly configured using config admin. > I can currently do this by setting org.apache.felix.http.enable=false, but > this then complicates starting the service, as I have to set both > http.enable=true and http.port=PORT > It would be useful if setting http.port=-1 effectively disabled the service, > then just by using config admin to set a valid port the service would start. > Currently setting http.port=-1 results in the following exception: > [WARNING] failed selectchannelconnec...@0.0.0.0:-1: > java.lang.IllegalArgumentException: port out of range:-1 > [WARNING] failed ser...@1f195fc: java.lang.IllegalArgumentException: port out > of range:-1 > [ERROR] Exception while initializing Jetty. > java.lang.IllegalArgumentException: port out of range:-1 > at java.net.InetSocketAddress.(InetSocketAddress.java:83) > The Equinox http service is disabled if http.port=-1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2772) setting http.port=-1 should disable service rather than throw exception
[ https://issues.apache.org/jira/browse/FELIX-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-2772. -- Resolution: Fixed Implemented in Rev. 1056994: The JettyConfig.isUseHttp() and JettyConfig.isUseHttps() methods only return true if both the service is enabled (as per FELIX_HTTP[S]_ENABLE) and the configured port (as per HTTP[S]_PORT) is higher than zero. > setting http.port=-1 should disable service rather than throw exception > --- > > Key: FELIX-2772 > URL: https://issues.apache.org/jira/browse/FELIX-2772 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Derek Baum >Assignee: Felix Meschberger >Priority: Minor > Fix For: http-2.0.6 > > > I want to stop http.jetty from starting automatically, as I want to ensure > the correct port is first explicitly configured using config admin. > I can currently do this by setting org.apache.felix.http.enable=false, but > this then complicates starting the service, as I have to set both > http.enable=true and http.port=PORT > It would be useful if setting http.port=-1 effectively disabled the service, > then just by using config admin to set a valid port the service would start. > Currently setting http.port=-1 results in the following exception: > [WARNING] failed selectchannelconnec...@0.0.0.0:-1: > java.lang.IllegalArgumentException: port out of range:-1 > [WARNING] failed ser...@1f195fc: java.lang.IllegalArgumentException: port out > of range:-1 > [ERROR] Exception while initializing Jetty. > java.lang.IllegalArgumentException: port out of range:-1 > at java.net.InetSocketAddress.(InetSocketAddress.java:83) > The Equinox http service is disabled if http.port=-1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Reopened: (FELIX-1999) The classes in the http.base bundle do not properly handle ServletRequest.getPathInfo() == null
[ https://issues.apache.org/jira/browse/FELIX-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reopened FELIX-1999: -- Reopening to fix the resolution: Should be fixed instead of invalid, of course. > The classes in the http.base bundle do not properly handle > ServletRequest.getPathInfo() == null > --- > > Key: FELIX-1999 > URL: https://issues.apache.org/jira/browse/FELIX-1999 > Project: Felix > Issue Type: Bug > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: http-2.0.6 > > > ServletRequest.getPathInfo() is allowed to return null (if there is no > additional path information). > For example, IBM WebSphere returns null if the client accesses the Servlet > context without a trailing slash (Jetty in this case redirects to the context > path with a trailing slash and thus this case does not happen). > To prevent NullPointerExceptions from happening the FilterHandler.match and > ServletHandler.match methods must guard against the uri parameter being null -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1999) The classes in the http.base bundle do not properly handle ServletRequest.getPathInfo() == null
[ https://issues.apache.org/jira/browse/FELIX-1999?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-1999. -- Resolution: Fixed Resolving fixed. > The classes in the http.base bundle do not properly handle > ServletRequest.getPathInfo() == null > --- > > Key: FELIX-1999 > URL: https://issues.apache.org/jira/browse/FELIX-1999 > Project: Felix > Issue Type: Bug > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: http-2.0.6 > > > ServletRequest.getPathInfo() is allowed to return null (if there is no > additional path information). > For example, IBM WebSphere returns null if the client accesses the Servlet > context without a trailing slash (Jetty in this case redirects to the context > path with a trailing slash and thus this case does not happen). > To prevent NullPointerExceptions from happening the FilterHandler.match and > ServletHandler.match methods must guard against the uri parameter being null -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-2772) setting http.port=-1 should disable service rather than throw exception
[ https://issues.apache.org/jira/browse/FELIX-2772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Baum closed FELIX-2772. - great! thanks for resolving this so quickly. > setting http.port=-1 should disable service rather than throw exception > --- > > Key: FELIX-2772 > URL: https://issues.apache.org/jira/browse/FELIX-2772 > Project: Felix > Issue Type: Improvement > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Derek Baum >Assignee: Felix Meschberger >Priority: Minor > Fix For: http-2.0.6 > > > I want to stop http.jetty from starting automatically, as I want to ensure > the correct port is first explicitly configured using config admin. > I can currently do this by setting org.apache.felix.http.enable=false, but > this then complicates starting the service, as I have to set both > http.enable=true and http.port=PORT > It would be useful if setting http.port=-1 effectively disabled the service, > then just by using config admin to set a valid port the service would start. > Currently setting http.port=-1 results in the following exception: > [WARNING] failed selectchannelconnec...@0.0.0.0:-1: > java.lang.IllegalArgumentException: port out of range:-1 > [WARNING] failed ser...@1f195fc: java.lang.IllegalArgumentException: port out > of range:-1 > [ERROR] Exception while initializing Jetty. > java.lang.IllegalArgumentException: port out of range:-1 > at java.net.InetSocketAddress.(InetSocketAddress.java:83) > The Equinox http service is disabled if http.port=-1 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: HTTP Service Release
+1 Derek On 9 January 2011 17:04, Richard S. Hall wrote: > +1 > > -> richard > > On 01/08/2011 11:14 PM, Felix Meschberger wrote: > >> Hi all, >> >> I have fixed a few issues of the HTTP Service implementations (mostly >> Jetty support stuff) and have deployed SNAPSHOTs of all bundles. >> >> The list of fixed bug since the 2.0.4 release can be found at >> >>https://issues.apache.org/jira/browse/FELIX/fixforversion/12314431 >> >> For an upcoming 2.0.6 (or 2.1.0 instead) Release I still consider these >> following bugs: >> >>FELIX-2292 Upgrade to jetty 7.0 (org.eclipse.jetty 7.0.2v20100331) >>FELIX-1962 Add support for (select) Servlet API listeners >> >> I would like to drop the following bugs from the release plan: >> >>FELIX-2137 Make it possible to set servlet/filter name >>FELIX-1963 Add possibility to share ServletContext between bundles >> >> Basically, I do not have a good idea on how to do this and there is no >> patch currently attached to any of these bugs. >> >> WDYT ? >> >> Regards >> Felix >> >> >
[jira] Commented: (FELIX-2741) NPE in ResolverImpl.calculatePackageSpaces
[ https://issues.apache.org/jira/browse/FELIX-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979424#action_12979424 ] Ancoron Luciferis commented on FELIX-2741: -- Just got another one, maybe related to this: [#|2011-01-09T23:26:46.605+0100|INFO|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=74;_ThreadName=Thread-1;|In main loop, we have serious trouble: java.lang.NullPointerException|#] [#|2011-01-09T23:26:46.606+0100|INFO|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=74;_ThreadName=Thread-1;|java.lang.NullPointerException at org.apache.felix.framework.resolver.ResolverImpl.calculateExportedPackages(ResolverImpl.java:1196) at org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:604) at org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:611) at org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:611) at org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:90) at org.apache.felix.framework.Felix$FelixResolver.resolve(Felix.java:3996) at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3402) at org.apache.felix.framework.Felix.startBundle(Felix.java:1719) at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922) at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1136) at org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1122) at org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1115) at org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:433) at org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:241) |#] > NPE in ResolverImpl.calculatePackageSpaces > -- > > Key: FELIX-2741 > URL: https://issues.apache.org/jira/browse/FELIX-2741 > Project: Felix > Issue Type: Bug > Components: Framework >Affects Versions: framework-3.0.6 >Reporter: Sahoo > Fix For: framework-3.2.0 > > > A GlassFish user has reported a NPE while doing stress testing and the stack > is given below: > [#|2010-12-22T11:28:28.910+0100|INFO|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=18;_ThreadName=Thread-1;|java.lang.NullPointerException > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:557) > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:619) > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:619) > at > org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:94) > at > org.apache.felix.framework.Felix$FelixResolver.resolve(Felix.java:3982) > at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3397) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1714) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1136) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1122) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1115) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:433) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:241) > |#] > m_wires must be null for this NPE to be caused by the following code: > for (Wire wire : module.getWires()) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-2741) NPE in ResolverImpl.calculatePackageSpaces
[ https://issues.apache.org/jira/browse/FELIX-2741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979425#action_12979425 ] Ancoron Luciferis commented on FELIX-2741: -- Last stackatrace is from 3.0.7 > NPE in ResolverImpl.calculatePackageSpaces > -- > > Key: FELIX-2741 > URL: https://issues.apache.org/jira/browse/FELIX-2741 > Project: Felix > Issue Type: Bug > Components: Framework >Affects Versions: framework-3.0.6 >Reporter: Sahoo > Fix For: framework-3.2.0 > > > A GlassFish user has reported a NPE while doing stress testing and the stack > is given below: > [#|2010-12-22T11:28:28.910+0100|INFO|glassfish3.1|javax.enterprise.system.std.com.sun.enterprise.server.logging|_ThreadID=18;_ThreadName=Thread-1;|java.lang.NullPointerException > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:557) > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:619) > at > org.apache.felix.framework.resolver.ResolverImpl.calculatePackageSpaces(ResolverImpl.java:619) > at > org.apache.felix.framework.resolver.ResolverImpl.resolve(ResolverImpl.java:94) > at > org.apache.felix.framework.Felix$FelixResolver.resolve(Felix.java:3982) > at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3397) > at org.apache.felix.framework.Felix.startBundle(Felix.java:1714) > at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:922) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1136) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.start(DirectoryWatcher.java:1122) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.startAllBundles(DirectoryWatcher.java:1115) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.process(DirectoryWatcher.java:433) > at > org.apache.felix.fileinstall.internal.DirectoryWatcher.run(DirectoryWatcher.java:241) > |#] > m_wires must be null for this NPE to be caused by the following code: > for (Wire wire : module.getWires()) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1962) Add support for (select) Servlet API listeners
[ https://issues.apache.org/jira/browse/FELIX-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger reassigned FELIX-1962: Assignee: Felix Meschberger > Add support for (select) Servlet API listeners > -- > > Key: FELIX-1962 > URL: https://issues.apache.org/jira/browse/FELIX-1962 > Project: Felix > Issue Type: New Feature > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: http-2.0.6 > > Attachments: FELIX-1962-2.patch, FELIX-1962.patch > > > The new Http Service implementation currently does not support any Servlet > API listeners at all. Support for some listeners can easily be implemented in > a transparent way: ServletContextAttributeListener, ServletRequestListener, > ServletRequestAttributeListener. > The HttpSession listeners can probably not easily be implemented in such a > transparent way. > The ServletContextListener is probably not worth it supporting. Most (if not > all) use cases for ServletContextListeners in traditional web applications > can be solved in better ways in an OSGi framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1962) Add support for (select) Servlet API listeners
[ https://issues.apache.org/jira/browse/FELIX-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979491#action_12979491 ] Felix Meschberger commented on FELIX-1962: -- Added initial support for listeners in Rev. 1057092 for the base bundle. The following listeners are supported - ServletContextAttributeListener -- handled by the base bundle wrapping the ServletContext handed to the servlets - ServletRequestListener -- handled by the base bundle by calling the listeners before and after handling the request - ServletRequestAttributeListener -- handled by the base bundle by wrapping the request object - HttpSessionListener -- requires support from the container and thus handled via the EventDispatcher which must be attached to the servlet container in the same was as the DispatcherServlet - HttpSessionAttributeListener -- requires support from the container and thus handled via the EventDispatcher which must be attached to the servlet container in the same was as the DispatcherServlet > Add support for (select) Servlet API listeners > -- > > Key: FELIX-1962 > URL: https://issues.apache.org/jira/browse/FELIX-1962 > Project: Felix > Issue Type: New Feature > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: http-2.0.6 > > Attachments: FELIX-1962-2.patch, FELIX-1962.patch > > > The new Http Service implementation currently does not support any Servlet > API listeners at all. Support for some listeners can easily be implemented in > a transparent way: ServletContextAttributeListener, ServletRequestListener, > ServletRequestAttributeListener. > The HttpSession listeners can probably not easily be implemented in such a > transparent way. > The ServletContextListener is probably not worth it supporting. Most (if not > all) use cases for ServletContextListeners in traditional web applications > can be solved in better ways in an OSGi framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1962) Add support for (select) Servlet API listeners
[ https://issues.apache.org/jira/browse/FELIX-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12979493#action_12979493 ] Felix Meschberger commented on FELIX-1962: -- In Rev. 1057093 enhanced the HTTP Bridge to register the EventDispatcher such that the Proxy Listener of the HTTP Proxy bundle can access it to forward HttpSession events. In Rev. 1057094 added a ProxyListener to the HTTP Proxy bundle which actually receives the events from the listener registered with the servlet container forwarding them to the EventDispatcher service (if available) > Add support for (select) Servlet API listeners > -- > > Key: FELIX-1962 > URL: https://issues.apache.org/jira/browse/FELIX-1962 > Project: Felix > Issue Type: New Feature > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: http-2.0.6 > > Attachments: FELIX-1962-2.patch, FELIX-1962.patch > > > The new Http Service implementation currently does not support any Servlet > API listeners at all. Support for some listeners can easily be implemented in > a transparent way: ServletContextAttributeListener, ServletRequestListener, > ServletRequestAttributeListener. > The HttpSession listeners can probably not easily be implemented in such a > transparent way. > The ServletContextListener is probably not worth it supporting. Most (if not > all) use cases for ServletContextListeners in traditional web applications > can be solved in better ways in an OSGi framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-1962) Add support for (select) Servlet API listeners
[ https://issues.apache.org/jira/browse/FELIX-1962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Meschberger resolved FELIX-1962. -- Resolution: Fixed Last step done in Rev. 1057096: Adding the EventDispatcher as listener to the Jetty Context to allow Jetty to send the events to the EventDispatcher to forward them to the registered listener services > Add support for (select) Servlet API listeners > -- > > Key: FELIX-1962 > URL: https://issues.apache.org/jira/browse/FELIX-1962 > Project: Felix > Issue Type: New Feature > Components: HTTP Service >Affects Versions: http-2.0.4 >Reporter: Felix Meschberger >Assignee: Felix Meschberger > Fix For: http-2.0.6 > > Attachments: FELIX-1962-2.patch, FELIX-1962.patch > > > The new Http Service implementation currently does not support any Servlet > API listeners at all. Support for some listeners can easily be implemented in > a transparent way: ServletContextAttributeListener, ServletRequestListener, > ServletRequestAttributeListener. > The HttpSession listeners can probably not easily be implemented in such a > transparent way. > The ServletContextListener is probably not worth it supporting. Most (if not > all) use cases for ServletContextListeners in traditional web applications > can be solved in better ways in an OSGi framework. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-2770) maven-scr-plugin 1.6.0 incompatible with pom projects
[
https://issues.apache.org/jira/browse/FELIX-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-2770:
Affects Version/s: (was: scr-1.6.0)
maven-scr-plugin-1.6.0
> maven-scr-plugin 1.6.0 incompatible with pom projects
>
>
> Key: FELIX-2770
> URL: https://issues.apache.org/jira/browse/FELIX-2770
> Project: Felix
> Issue Type: Bug
> Components: Maven SCR Plugin
>Affects Versions: maven-scr-plugin-1.6.0
> Environment: Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-23-generic" arch: "i386" Family: "unix"
>Reporter: Ben Alex
>Assignee: Carsten Ziegeler
> Fix For: maven-scr-plugin-1.6.2
>
>
> maven-scr-plugin 1.6.0 when defined in a pom.xml that is of type
> pom yields an exception during a Maven 2.2.1 reactor
> build:
> {code}
> java.lang.IllegalStateException: basedir
> /home/balex/projects/roo/osgi-roo-bundle/src/main/java does not exist
> at
> org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:290)
> at
> org.apache.felix.scrplugin.mojo.MavenJavaClassDescriptorManager.getSourceFiles(MavenJavaClassDescriptorManager.java:97)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getSources(JavaClassDescriptorManager.java:109)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getJavaClassesFromSources(JavaClassDescriptorManager.java:446)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getSourceDescriptions(JavaClassDescriptorManager.java:362)
> at
> org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:233)
> at
> org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:184)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at 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)
> {code}
> It is typical to use a pom in a parent module in large
> OSGi systems such as Spring Roo. Such modules don't have src/main/java
> directories as there is no Java code contained within them.
> This bug is not present when using maven-scr-plugin 1.4.4 and below.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (FELIX-2770) maven-scr-plugin 1.6.0 incompatible with pom projects
[
https://issues.apache.org/jira/browse/FELIX-2770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-2770.
-
Resolution: Fixed
Fix Version/s: maven-scr-plugin-1.6.2
> maven-scr-plugin 1.6.0 incompatible with pom projects
>
>
> Key: FELIX-2770
> URL: https://issues.apache.org/jira/browse/FELIX-2770
> Project: Felix
> Issue Type: Bug
> Components: Maven SCR Plugin
>Affects Versions: scr-1.6.0
> Environment: Apache Maven 2.2.1 (rdebian-4)
> Java version: 1.6.0_22
> Java home: /usr/lib/jvm/java-6-sun-1.6.0.22/jre
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux" version: "2.6.35-23-generic" arch: "i386" Family: "unix"
>Reporter: Ben Alex
>Assignee: Carsten Ziegeler
> Fix For: maven-scr-plugin-1.6.2
>
>
> maven-scr-plugin 1.6.0 when defined in a pom.xml that is of type
> pom yields an exception during a Maven 2.2.1 reactor
> build:
> {code}
> java.lang.IllegalStateException: basedir
> /home/balex/projects/roo/osgi-roo-bundle/src/main/java does not exist
> at
> org.codehaus.plexus.util.DirectoryScanner.scan(DirectoryScanner.java:290)
> at
> org.apache.felix.scrplugin.mojo.MavenJavaClassDescriptorManager.getSourceFiles(MavenJavaClassDescriptorManager.java:97)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getSources(JavaClassDescriptorManager.java:109)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getJavaClassesFromSources(JavaClassDescriptorManager.java:446)
> at
> org.apache.felix.scrplugin.JavaClassDescriptorManager.getSourceDescriptions(JavaClassDescriptorManager.java:362)
> at
> org.apache.felix.scrplugin.SCRDescriptorGenerator.execute(SCRDescriptorGenerator.java:233)
> at
> org.apache.felix.scrplugin.mojo.SCRDescriptorMojo.execute(SCRDescriptorMojo.java:184)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at 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)
> {code}
> It is typical to use a pom in a parent module in large
> OSGi systems such as Spring Roo. Such modules don't have src/main/java
> directories as there is no Java code contained within them.
> This bug is not present when using maven-scr-plugin 1.4.4 and below.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
