Back to bug 790873

Who When What Removed Added
Karel Piwko 2012-02-29 12:00:56 UTC CC kpiwko
Assignee myarboro rnewton
Rebecca Newton 2012-03-08 00:57:38 UTC Flags needinfo?(okiss)
Karel Piwko 2012-03-12 22:39:48 UTC Priority unspecified medium
Flags needinfo?(okiss)
Severity unspecified medium
Karel Piwko 2012-06-01 12:50:34 UTC Status NEW VERIFIED
Target Release --- 2.0.0.GA
Karel Piwko 2012-06-22 07:40:03 UTC Status VERIFIED ASSIGNED
Target Release 2.0.0.GA 2.1.0.GA
Assignee rnewton kpiwko
QA Contact kpiwko
Karel Piwko 2012-06-22 07:47:56 UTC Version unspecified 2.0.0.GA
mark yarborough 2012-11-05 15:23:40 UTC Target Release 2.1.0 2.2.0
CC myarboro
Tomas Repel 2012-11-27 15:12:22 UTC CC trepel
mark yarborough 2013-02-28 12:57:50 UTC Target Release 2.2.0 2.3.0
Karel Piwko 2013-04-19 10:06:42 UTC Type --- Bug
Petr Penicka 2013-04-19 12:14:50 UTC CC ppenicka
Doc Text OSGi is not enabled in JBoss Enterprise Application Server 6. Artifacts produced by Grails miss a Package-Import of javax.naming in the bundle. The workaround for this issue is to disable OSGi while packaging your Grails application. You can do this by setting the following property in the BuildConfig.groovy configuration file:

grails.project.war.osgi.headers = false
OSGi is not enabled in JBoss Enterprise Application Platform 6. Artifacts produced by Grails miss a Package-Import of javax.naming in the bundle. The workaround for this issue is to disable OSGi while packaging your Grails applications. You can do this using the following configuration in the BuildConfig.groovy configuration file:

grails.project.war.osgi.headers = false
mark yarborough 2013-06-04 00:43:40 UTC Target Release 2.3.0 2.4.0
Marek Schmidt 2013-07-08 15:46:22 UTC CC maschmid
QA Contact kpiwko maschmid
Marek Schmidt 2013-07-08 15:51:07 UTC Doc Text OSGi is not enabled in JBoss Enterprise Application Platform 6. Artifacts produced by Grails miss a Package-Import of javax.naming in the bundle. The workaround for this issue is to disable OSGi while packaging your Grails applications. You can do this using the following configuration in the BuildConfig.groovy configuration file:

grails.project.war.osgi.headers = false
OSGi is not enabled in JBoss Enterprise Application Platform 6. Artifacts produced by Grails miss a Package-Import of javax.naming in the bundle. The workaround for this issue is to disable OSGi while packaging your Grails applications. You can do this using the following configuration in the BuildConfig.groovy configuration file:

grails.project.war.osgi.headers = false
Doc Type Bug Fix Known Issue
Red Hat Bugzilla 2013-07-08 15:51:07 UTC Doc Type Known Issue Bug Fix
Marek Schmidt 2013-07-08 15:55:51 UTC Assignee kpiwko maschmid
Doc Type Bug Fix Known Issue
Red Hat Bugzilla 2013-07-08 15:55:51 UTC Doc Type Known Issue Bug Fix
Marek Schmidt 2013-07-08 15:56:26 UTC Doc Text OSGi is not enabled in JBoss Enterprise Application Platform 6. Artifacts produced by Grails miss a Package-Import of javax.naming in the bundle. The workaround for this issue is to disable OSGi while packaging your Grails applications. You can do this using the following configuration in the BuildConfig.groovy configuration file:

grails.project.war.osgi.headers = false
OSGi is not enabled in JBoss Enterprise Application Platform 6. Artifacts produced by Grails miss a Package-Import of javax.naming in the bundle. To workaround this issue, disable OSGi while packaging your Grails applications. You can do this using the following configuration in the BuildConfig.groovy configuration file:

grails.project.war.osgi.headers = false
Doc Type Bug Fix Known Issue
Petr Penicka 2013-07-08 16:36:00 UTC Doc Text OSGi is not enabled in JBoss Enterprise Application Platform 6. Artifacts produced by Grails miss a Package-Import of javax.naming in the bundle. To workaround this issue, disable OSGi while packaging your Grails applications. You can do this using the following configuration in the BuildConfig.groovy configuration file:

grails.project.war.osgi.headers = false
OSGi is not enabled in JBoss Enterprise Application Platform 6, and artifacts produced by Grails miss a Package-Import of javax.naming in the bundle. To workaround this issue, disable adding of OSGi headers while packaging your Grails applications by adding the following configuration into the BuildConfig.groovy configuration file:

grails.project.war.osgi.headers = false
Marek Schmidt 2013-07-18 14:56:28 UTC Status ASSIGNED CLOSED
Resolution --- INSUFFICIENT_DATA
Link ID JBoss Issue Tracker WFK2-63
Last Closed 2013-07-18 10:56:28 UTC
Marek Schmidt 2013-07-18 14:57:31 UTC Link ID JBoss Issue Tracker WFK2-63 JBoss Issue Tracker WFK2-65
John Skeoch 2015-08-02 23:42:44 UTC CC oskutka

Back to bug 790873