[jira] Updated: (FELIX-531) Allow the import package scope to be set for the bundleall goal in the maven-bundle-plugin
[ https://issues.apache.org/jira/browse/FELIX-531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mike Smoot updated FELIX-531: - Attachment: importResolution.patch The patch was created against revision 645664 in the bundleplugin directory. patch -p0 < importResolution.patch should do the trick. > Allow the import package scope to be set for the bundleall goal in the > maven-bundle-plugin > -- > > Key: FELIX-531 > URL: https://issues.apache.org/jira/browse/FELIX-531 > Project: Felix > Issue Type: New Feature > Components: Maven Bundle Plugin >Affects Versions: maven-bundle-plugin-1.4.1 > Environment: any >Reporter: Mike Smoot >Priority: Minor > Fix For: maven-bundle-plugin-1.4.1 > > Attachments: importResolution.patch > > Original Estimate: 2h > Remaining Estimate: 2h > > It would be nice if the wrap and bundleall goals of the maven-bundle-plugin > would allow for Import-Packages to allow for optional resolution. > As such, I've created a patch which allows this with a new configuration > parameter: importResolution. This now tells bnd to make all imports optional: > > > *;resolution:=optional > > I'll attach the patch as soon as I figure out how. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-531) Allow the import package scope to be set for the bundleall goal in the maven-bundle-plugin
Allow the import package scope to be set for the bundleall goal in the maven-bundle-plugin -- Key: FELIX-531 URL: https://issues.apache.org/jira/browse/FELIX-531 Project: Felix Issue Type: New Feature Components: Maven Bundle Plugin Affects Versions: maven-bundle-plugin-1.4.1 Environment: any Reporter: Mike Smoot Priority: Minor Fix For: maven-bundle-plugin-1.4.1 It would be nice if the wrap and bundleall goals of the maven-bundle-plugin would allow for Import-Packages to allow for optional resolution. As such, I've created a patch which allows this with a new configuration parameter: importResolution. This now tells bnd to make all imports optional: *;resolution:=optional I'll attach the patch as soon as I figure out how. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-530) Separate DirectoryWatch function from action
Separate DirectoryWatch function from action Key: FELIX-530 URL: https://issues.apache.org/jira/browse/FELIX-530 Project: Felix Issue Type: New Feature Components: File Install Reporter: Toni Menzel I would like to pull the actions out of the DirectoryWatcher class. Instead, this class just detect/tracks changes like it currently does and calls an appropriate action contributed via extender pattern. This way, other bundles can 1. contribute functionality like handling other stuff than final bundles and .cfg files. 2. replace the current behavior 3. DirectoryWatcher gets slicker / easier to maintain The current two behaviors (install/update/remove on .jar Bundles and .cfg) could be installed in the activator by default (just like felix.shell does with its commands) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Updated: (FELIX-528) Support nested folders in fileinstall
[ https://issues.apache.org/jira/browse/FELIX-528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Toni Menzel updated FELIX-528: -- Attachment: FELIX-528.patch If you like this "feature", patch is attached. Toni > Support nested folders in fileinstall > - > > Key: FELIX-528 > URL: https://issues.apache.org/jira/browse/FELIX-528 > Project: Felix > Issue Type: New Feature > Components: File Install >Reporter: Toni Menzel >Priority: Minor > Attachments: FELIX-528.patch > > > Currently FileInstall just supports "flat" jar-Files as bundles in its load > folder. > How about supporting (nested) folders? > This way, you could: > 1. just drop an arbitrary folder structure and fileinstall would install all > bundles inside. > 2. you could enable/disable entire "bundle-sets" with: > 2a. in/move it out of the folder > 2b. rename the folder with prefix that means "unrecognized folder" > Just a thought.. > Toni -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-527) Improve Error Reporting during binding
[ https://issues.apache.org/jira/browse/FELIX-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12586426#action_12586426 ] Felix Meschberger commented on FELIX-527: - Thanks Niclas. > Improve Error Reporting during binding > -- > > Key: FELIX-527 > URL: https://issues.apache.org/jira/browse/FELIX-527 > Project: Felix > Issue Type: Bug > Components: Declarative Services >Affects Versions: felix-1.0.0 > Environment: org.apache.felix.scr-0.9.0-SNAPSHOT > org.apache.felix.scr-1.0.0 > pax-logging-0.9.6 >Reporter: Patrick Forhan > > [cross-reported to pax-logging jira as > http://issues.ops4j.org/jira/browse/PAXLOGGING-25 ] > If a service throws an exception during binding, the following is the only > stack trace reported. The original context is lost: > Exception in thread "SCR Component Actor" java.lang.NullPointerException > at java.util.Hashtable.put(Unknown Source) > at > org.ops4j.pax.logging.internal.PaxLoggingServiceImpl.createEvent(PaxLoggingServiceImpl.java:175) > at > org.ops4j.pax.logging.internal.PaxLoggingServiceImpl.log(PaxLoggingServiceImpl.java:140) > at > org.ops4j.pax.logging.internal.PaxLoggingServiceImpl.log(PaxLoggingServiceImpl.java:76) > at > org.ops4j.pax.logging.internal.PaxLoggingServiceImpl.log(PaxLoggingServiceImpl.java:66) > at org.apache.felix.scr.Activator.log(Activator.java:455) > at > org.apache.felix.scr.ComponentActorThread.run(ComponentActorThread.java:89) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
