[GRADLE-905] OSGi plugin does not create the declarative service description if someone is using the aQute annotations Created: 12/Apr/10  Updated: 10/Feb/17  Resolved: 10/Feb/17

Status: Resolved
Project: Gradle
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Lars Heuer Assignee: Unassigned
Resolution: Won't Fix Votes: 4

Issue Links:
Related
Related to GRADLE-1107 OSGi instruction Include-Resource not... Resolved

 Description   

I have an aQute annotated class:

@Component
class TheComponent implements Foo {
}

but OSGi plugin does not create the OSGI-INF/component.xml file if someone is using:

jar {
manifest

{ instruction 'Service-Component', '*' }

}

The MANIFEST.MF contains:

Service-Component: OSGI-INF/com.example.TheComponent.xml

but neither the directory OSGI-INF not the XML file is part of the resulting jar.

 Comments   
Comment by Lars Heuer [ 12/Apr/10 ]

Using a non-annotated class together with

instruction 'Service-Component', 'aQute.tutorial.component.World;log=org.osgi.service.log.LogService'

does not help either. The result is the same.

Comment by Hans Dockter [ 17/Apr/10 ]

The osgi plugin does not address your use case currently. It does only generate the manifest. We will address this issue for 1.0. The workaround you have at the moment is to use the bnd ant task and then to merge the generated manifest and other files into the jar task.

Comment by Benjamin Muschko [ 15/Nov/16 ]

As announced on the Gradle blog we are planning to completely migrate issues from JIRA to GitHub.

We intend to prioritize issues that are actionable and impactful while working more closely with the community. Many of our JIRA issues are inactionable or irrelevant. We would like to request your help to ensure we can appropriately prioritize JIRA issues you’ve contributed to.

Please confirm that you still advocate for your JIRA issue before December 10th, 2016 by:

  • Checking that your issues contain requisite context, impact, behaviors, and examples as described in our published guidelines.
  • Leave a comment on the JIRA issue or open a new GitHub issue confirming that the above is complete.

We look forward to collaborating with you more closely on GitHub. Thank you for your contribution to Gradle!

Comment by Benjamin Muschko [ 10/Feb/17 ]

Thanks again for reporting this issue. We haven't heard back from you after our inquiry from November 15th. We are closing this issue now. Please create an issue on GitHub if you still feel passionate about getting it resolved.

Generated at Wed Jun 30 11:41:57 CDT 2021 using Jira 8.4.2#804003-sha1:d21414fc212e3af190e92c2d2ac41299b89402cf.