[jira] Resolved: (FELIX-1611) -resource: @path-to-jar should only resolve path-to-jar if it exists
[ https://issues.apache.org/jira/browse/FELIX-1611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Baum resolved FELIX-1611. --- Resolution: Fixed in-line jar path is now only resolved if it exists, allowing BND to search classpath for jar. -resource: @path-to-jar should only resolve path-to-jar if it exists Key: FELIX-1611 URL: https://issues.apache.org/jira/browse/FELIX-1611 Project: Felix Issue Type: Bug Components: Sigil Reporter: Derek Baum Assignee: Derek Baum Priority: Minor -resource: @path-to-jar falls through to BND with embeds the content of the jar. Sigil resolves the specified path against the location of sigil.properties, so BND can still find the jar when invoked from higher-level builds. However, this stops the BND feature of searching the classpath for a jar of the specified name. So if the resolved path that sigil creates does not exist, then the original path should be passed to BND. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1610) OBR repository update check is hard-coded at 7 days
[ https://issues.apache.org/jira/browse/FELIX-1610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Derek Baum reassigned FELIX-1610: - Assignee: (was: Derek Baum) main problem is already resolved, by previous refactoring of repo cache. this issue is now just reminder to remove hard-coded 7-day expiry. OBR repository update check is hard-coded at 7 days --- Key: FELIX-1610 URL: https://issues.apache.org/jira/browse/FELIX-1610 Project: Felix Issue Type: Bug Components: Sigil Reporter: Derek Baum Priority: Minor OBR repository provided hard codes update check as 7 days. It makes no account of file: URLs, so once it has copied a file: URL to its cache, it won't update it for 7 days. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Assigned: (FELIX-1383) sigil.properties -defaults should support variable expansion to allow it to be overriden
[
https://issues.apache.org/jira/browse/FELIX-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Derek Baum reassigned FELIX-1383:
-
Assignee: Derek Baum
sigil.properties -defaults should support variable expansion to allow it to
be overriden
Key: FELIX-1383
URL: https://issues.apache.org/jira/browse/FELIX-1383
Project: Felix
Issue Type: Improvement
Components: Sigil
Reporter: Derek Baum
Assignee: Derek Baum
Priority: Minor
sigil.properties files support a directive:
-defaults: [-]path-to-defaults
which allows for default values (such as default package import versions) to
be inherited.
If -defaults is not specified, '-../sigil-defaults.properties' is used to
implicitly use defaults from parent.
The leading - means ignore error if the file is not found.
It would be useful if the defaults value was variable expanded against System
properties and the environment:
-defaults: ${DEFAULTS_DIR:-../common}/sigil-defaults.properties
sigil already contains the necessary property variable expansion code.
however, property variable expansion is NOT globally applied to all values in
sigil.properties, as the eclipse plugin is not aware of variable expansion,
so when it updates sigil.properties all variables would have their expanded
value.
This is not a problem with -defaults, as the eclipse plugin is not aware of
this value.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1613) [sigil] reformat code using fixed eclipse template
[sigil] reformat code using fixed eclipse template -- Key: FELIX-1613 URL: https://issues.apache.org/jira/browse/FELIX-1613 Project: Felix Issue Type: Task Components: Sigil Reporter: Derek Baum Priority: Minor The felix eclipse code format template used to format sigil code was wrong (FELIX-1406). It has now been fixed, so sigil code needs to be re-formatted to comply with felix coding standards. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1614) Exclusion of the springsource AOP bundle in the pom
Exclusion of the springsource AOP bundle in the pom --- Key: FELIX-1614 URL: https://issues.apache.org/jira/browse/FELIX-1614 Project: Felix Issue Type: Bug Components: Karaf Reporter: Jean-Baptiste Onofré As we already have a bundle for the springsource AOP, I have excluded this from the spring core osgi dependency. This dependency fails the build using maven 2.0.x (either if it works using maven 2.2.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-1614) Exclusion of the springsource AOP bundle in the pom
[ https://issues.apache.org/jira/browse/FELIX-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jean-Baptiste Onofré updated FELIX-1614: Attachment: FELIX-1614.patch The patches karaf pom. Exclusion of the springsource AOP bundle in the pom --- Key: FELIX-1614 URL: https://issues.apache.org/jira/browse/FELIX-1614 Project: Felix Issue Type: Bug Components: Karaf Reporter: Jean-Baptiste Onofré Attachments: FELIX-1614.patch As we already have a bundle for the springsource AOP, I have excluded this from the spring core osgi dependency. This dependency fails the build using maven 2.0.x (either if it works using maven 2.2.1). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1615) FilterMapping/ServletMapping object to API
FilterMapping/ServletMapping object to API -- Key: FELIX-1615 URL: https://issues.apache.org/jira/browse/FELIX-1615 Project: Felix Issue Type: Improvement Components: HTTP Service Reporter: Sten Roger Sandvik Assignee: Sten Roger Sandvik Fix For: http-2.0.0 Add FilterMapping and ServletMapping to API for easily adding multiple paths for a single servlet/filter. Will also be used in whiteboard implementation. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1616) Convert to Java 1.4 compliant code
Convert to Java 1.4 compliant code -- Key: FELIX-1616 URL: https://issues.apache.org/jira/browse/FELIX-1616 Project: Felix Issue Type: Improvement Components: HTTP Service Reporter: Sten Roger Sandvik Assignee: Sten Roger Sandvik Fix For: http-2.0.0 Now all code use 1.5 java features. Convert to be compatible with 1.4. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[VOTE RESULT] Release Felix Maven SCR Plugin 1.4.0 and SCR Annotations 1.0.0
The vote passed successfully with five +1 votes from: Felix Meschberger, Carsten Ziegeler, Clement Escoffier, Richard S. Hall, and Karl Pauls. No other votes have been cast. I'll continue with uploading the artifacts now. Thanks for testing and voting! Regards Carsten -- Carsten Ziegeler cziege...@apache.org
Re: [karaf] sub-modules naming
On 9/18/09 10:21, Guillaume Nodet wrote: Currently, Karaf has maven modules, but their naming is not consistent. We have: * karaf/jaas/jaas-boot * karaf/features/core * karaf/deployer/blueprint * karaf/gshell/gshell-admin So I'd like to fix those. The question is which one we prefer ? I'm kinda leaning towards karaf/features/boot i.e not repeating the parent module in the name. +1 Also, I think we should rename gshell to shell, given we don't use gshell anymore but switched to gogo. Shell is a bit more neutral. Thoughts ? +1 - richard
[jira] Created: (FELIX-1617) Modify framework to depend on official OSGi R4.2 JAR files
Modify framework to depend on official OSGi R4.2 JAR files -- Key: FELIX-1617 URL: https://issues.apache.org/jira/browse/FELIX-1617 Project: Felix Issue Type: Task Affects Versions: felix-2.0.0 Reporter: Richard S. Hall Fix For: felix-2.2.0 The OSGi R.4.2 JAR files are now in the central maven repo, so we should be able to depend on them directly and eliminate our copies completely. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Group rights in dist directory
Hi, could you please ensure that you set the group to felix for the artifacts you upload to www.apache.org/dist/felix ? Thanks Carsten -- Carsten Ziegeler cziege...@apache.org
[jira] Created: (FELIX-1618) in spring-dm feature, optional imports in spring-context won't get resolved
in spring-dm feature, optional imports in spring-context won't get resolved --- Key: FELIX-1618 URL: https://issues.apache.org/jira/browse/FELIX-1618 Project: Felix Issue Type: Bug Affects Versions: karaf-1.0.0 Reporter: Hans Couder Fix For: karaf-1.0.0 In the spring-dm feature, the spring-context bundle precedes spring-aop. This causes optional imports in the spring-context bundle won't get resolved resulting in: Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=org.apache.camel.camel-example-osgi, config=osgibundle:/META-INF/spring/*.xml)) java.lang.NoClassDefFoundError: org/springframework/aop/support/AopUtils at org.springframework.jmx.export.assembler.MetadataMBeanInfoAssembler.checkManagedBean(MetadataMBeanInfoAssembler.java:106) at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getMBeanInfo(AbstractMBeanInfoAssembler.java:63) at org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:202) at org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:193) at org.apache.camel.management.ManagedManagementStrategy.manageNamedObject(ManagedManagementStrategy.java:68) at org.apache.camel.management.ManagedManagementStrategy.manageObject(ManagedManagementStrategy.java:61) at org.apache.camel.management.DefaultManagementLifecycleStrategy.onContextStart(DefaultManagementLifecycleStrategy.java:99) at org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:918) at org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:869) at org.apache.camel.spring.SpringCamelContext.maybeDoStart(SpringCamelContext.java:165) at org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:160) at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:52) at org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:832) at org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:99) at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:119) at org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:516) at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78) at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76) at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736) at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358) at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: *** Class 'org.springframework.aop.support.AopUtils' was not found because bundle 38 does not import 'org.springframework.aop.support' even though bundle 39 does export it. To resolve this issue, add an import for 'org.springframework.aop.support' to bundle 38. *** at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1645) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 27 more Caused by: java.lang.ClassNotFoundException: org.springframework.aop.support.AopUtils at org.apache.felix.framework.ModuleImpl.findClassOrResourceByDelegation(ModuleImpl.java:726) at org.apache.felix.framework.ModuleImpl.access$100(ModuleImpl.java:60) at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1631) ... 29 more -- This message is automatically generated by JIRA. - You can reply to this
[jira] Assigned: (FELIX-1618) in spring-dm feature, optional imports in spring-context won't get resolved
[ https://issues.apache.org/jira/browse/FELIX-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen reassigned FELIX-1618: -- Assignee: Gert Vanthienen in spring-dm feature, optional imports in spring-context won't get resolved --- Key: FELIX-1618 URL: https://issues.apache.org/jira/browse/FELIX-1618 Project: Felix Issue Type: Bug Affects Versions: karaf-1.0.0 Reporter: Hans Couder Assignee: Gert Vanthienen Fix For: karaf-1.0.0 In the spring-dm feature, the spring-context bundle precedes spring-aop. This causes optional imports in the spring-context bundle won't get resolved resulting in: Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=org.apache.camel.camel-example-osgi, config=osgibundle:/META-INF/spring/*.xml)) java.lang.NoClassDefFoundError: org/springframework/aop/support/AopUtils at org.springframework.jmx.export.assembler.MetadataMBeanInfoAssembler.checkManagedBean(MetadataMBeanInfoAssembler.java:106) at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getMBeanInfo(AbstractMBeanInfoAssembler.java:63) at org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:202) at org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:193) at org.apache.camel.management.ManagedManagementStrategy.manageNamedObject(ManagedManagementStrategy.java:68) at org.apache.camel.management.ManagedManagementStrategy.manageObject(ManagedManagementStrategy.java:61) at org.apache.camel.management.DefaultManagementLifecycleStrategy.onContextStart(DefaultManagementLifecycleStrategy.java:99) at org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:918) at org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:869) at org.apache.camel.spring.SpringCamelContext.maybeDoStart(SpringCamelContext.java:165) at org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:160) at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:52) at org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:832) at org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:99) at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:119) at org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:516) at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78) at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76) at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736) at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358) at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: *** Class 'org.springframework.aop.support.AopUtils' was not found because bundle 38 does not import 'org.springframework.aop.support' even though bundle 39 does export it. To resolve this issue, add an import for 'org.springframework.aop.support' to bundle 38. *** at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1645) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 27 more Caused by: java.lang.ClassNotFoundException: org.springframework.aop.support.AopUtils at
[jira] Resolved: (FELIX-1618) in spring-dm feature, optional imports in spring-context won't get resolved
[ https://issues.apache.org/jira/browse/FELIX-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gert Vanthienen resolved FELIX-1618. Resolution: Fixed Reordering the bundles in the features descriptor should fix this, cfr. http://svn.apache.org/viewvc?view=revrevision=816629 @Hans: Can you close this issue if this fixes your problem? in spring-dm feature, optional imports in spring-context won't get resolved --- Key: FELIX-1618 URL: https://issues.apache.org/jira/browse/FELIX-1618 Project: Felix Issue Type: Bug Affects Versions: karaf-1.0.0 Reporter: Hans Couder Assignee: Gert Vanthienen Fix For: karaf-1.0.0 In the spring-dm feature, the spring-context bundle precedes spring-aop. This causes optional imports in the spring-context bundle won't get resolved resulting in: Application context refresh failed (OsgiBundleXmlApplicationContext(bundle=org.apache.camel.camel-example-osgi, config=osgibundle:/META-INF/spring/*.xml)) java.lang.NoClassDefFoundError: org/springframework/aop/support/AopUtils at org.springframework.jmx.export.assembler.MetadataMBeanInfoAssembler.checkManagedBean(MetadataMBeanInfoAssembler.java:106) at org.springframework.jmx.export.assembler.AbstractMBeanInfoAssembler.getMBeanInfo(AbstractMBeanInfoAssembler.java:63) at org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:202) at org.apache.camel.management.DefaultManagementAgent.register(DefaultManagementAgent.java:193) at org.apache.camel.management.ManagedManagementStrategy.manageNamedObject(ManagedManagementStrategy.java:68) at org.apache.camel.management.ManagedManagementStrategy.manageObject(ManagedManagementStrategy.java:61) at org.apache.camel.management.DefaultManagementLifecycleStrategy.onContextStart(DefaultManagementLifecycleStrategy.java:99) at org.apache.camel.impl.DefaultCamelContext.doStartCamel(DefaultCamelContext.java:918) at org.apache.camel.impl.DefaultCamelContext.doStart(DefaultCamelContext.java:869) at org.apache.camel.spring.SpringCamelContext.maybeDoStart(SpringCamelContext.java:165) at org.apache.camel.spring.SpringCamelContext.doStart(SpringCamelContext.java:160) at org.apache.camel.impl.ServiceSupport.start(ServiceSupport.java:52) at org.apache.camel.impl.DefaultCamelContext.start(DefaultCamelContext.java:832) at org.apache.camel.spring.SpringCamelContext.maybeStart(SpringCamelContext.java:99) at org.apache.camel.spring.SpringCamelContext.onApplicationEvent(SpringCamelContext.java:119) at org.apache.camel.spring.CamelContextFactoryBean.onApplicationEvent(CamelContextFactoryBean.java:516) at org.springframework.context.event.SimpleApplicationEventMulticaster$1.run(SimpleApplicationEventMulticaster.java:78) at org.springframework.core.task.SyncTaskExecutor.execute(SyncTaskExecutor.java:49) at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:76) at org.springframework.context.support.AbstractApplicationContext.publishEvent(AbstractApplicationContext.java:274) at org.springframework.context.support.AbstractApplicationContext.finishRefresh(AbstractApplicationContext.java:736) at org.springframework.osgi.context.support.AbstractOsgiBundleApplicationContext.finishRefresh(AbstractOsgiBundleApplicationContext.java:235) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext$4.run(AbstractDelegatedExecutionApplicationContext.java:358) at org.springframework.osgi.util.internal.PrivilegedUtils.executeWithCustomTCCL(PrivilegedUtils.java:85) at org.springframework.osgi.context.support.AbstractDelegatedExecutionApplicationContext.completeRefresh(AbstractDelegatedExecutionApplicationContext.java:320) at org.springframework.osgi.extender.internal.dependencies.startup.DependencyWaiterApplicationContextExecutor$CompleteRefreshTask.run(DependencyWaiterApplicationContextExecutor.java:136) at java.lang.Thread.run(Thread.java:619) Caused by: java.lang.ClassNotFoundException: *** Class 'org.springframework.aop.support.AopUtils' was not found because bundle 38 does not import 'org.springframework.aop.support' even though bundle 39 does export it. To resolve this issue, add an import for 'org.springframework.aop.support' to bundle 38. *** at org.apache.felix.framework.ModuleImpl$ModuleClassLoader.loadClass(ModuleImpl.java:1645) at java.lang.ClassLoader.loadClass(ClassLoader.java:252) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:320) ... 27 more Caused
[jira] Closed: (FELIX-1547) OS shell level admin commands for Karaf
[ https://issues.apache.org/jira/browse/FELIX-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert closed FELIX-1547. --- OS shell level admin commands for Karaf --- Key: FELIX-1547 URL: https://issues.apache.org/jira/browse/FELIX-1547 Project: Felix Issue Type: New Feature Components: Karaf Reporter: David Bosschaert Assignee: Guillaume Nodet Fix For: karaf-1.0.0 Attachments: karaf-admin-8.patch Karaf has admin commands to create new instances from within its shell. Examples are admin:create admin:list admin:start etc... It would be good if (some of) these commands were available from the OS-level command line - outside of the Karaf container. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1548) admin:create
[ https://issues.apache.org/jira/browse/FELIX-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert closed FELIX-1548. --- Resolution: Fixed admin:create Key: FELIX-1548 URL: https://issues.apache.org/jira/browse/FELIX-1548 Project: Felix Issue Type: Sub-task Components: Karaf Affects Versions: karaf-1.0.0 Reporter: David Bosschaert The admin:create command -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1549) admin:list
[ https://issues.apache.org/jira/browse/FELIX-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert closed FELIX-1549. --- Resolution: Fixed admin:list -- Key: FELIX-1549 URL: https://issues.apache.org/jira/browse/FELIX-1549 Project: Felix Issue Type: Sub-task Reporter: David Bosschaert -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Closed: (FELIX-1550) admin:destroy
[ https://issues.apache.org/jira/browse/FELIX-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Bosschaert closed FELIX-1550. --- Resolution: Fixed admin:destroy - Key: FELIX-1550 URL: https://issues.apache.org/jira/browse/FELIX-1550 Project: Felix Issue Type: Sub-task Reporter: David Bosschaert -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
Re: Group rights in dist directory
I've run a chmod g+w * ; chown :felix * so those that i am the owner are now ok. On Fri, Sep 18, 2009 at 14:14, Carsten Ziegeler cziege...@apache.org wrote: Hi, could you please ensure that you set the group to felix for the artifacts you upload to www.apache.org/dist/felix ? Thanks Carsten -- Carsten Ziegeler cziege...@apache.org -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com
Re: Group rights in dist directory
On Fri, Sep 18, 2009 at 5:23 PM, Guillaume Nodet gno...@gmail.com wrote: I've run a chmod g+w * ; chown :felix * so those that i am the owner are now ok. I did the same. regards, Karl On Fri, Sep 18, 2009 at 14:14, Carsten Ziegeler cziege...@apache.org wrote: Hi, could you please ensure that you set the group to felix for the artifacts you upload to www.apache.org/dist/felix ? Thanks Carsten -- Carsten Ziegeler cziege...@apache.org -- Cheers, Guillaume Nodet Blog: http://gnodet.blogspot.com/ Open Source SOA http://fusesource.com -- Karl Pauls karlpa...@gmail.com
[jira] Closed: (FELIX-1597) Sigil features files and update site are hard coded to release 0.9.0.SNAPSHOT
[ https://issues.apache.org/jira/browse/FELIX-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] David Savage closed FELIX-1597. --- Resolution: Fixed Fix Version/s: sigil-1.0.0 sigil build patched to set versions in features.xml files via bnd preprocessing update site generated by parsing site directory via a groovy script to read bundle symbolic name and bundle version from features Sigil features files and update site are hard coded to release 0.9.0.SNAPSHOT - Key: FELIX-1597 URL: https://issues.apache.org/jira/browse/FELIX-1597 Project: Felix Issue Type: Bug Components: Sigil Reporter: David Savage Assignee: David Savage Fix For: sigil-1.0.0 Better to parametrize this in the build -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1619) Change the detaul auto-deploy actions to be install and start only
Change the detaul auto-deploy actions to be install and start only -- Key: FELIX-1619 URL: https://issues.apache.org/jira/browse/FELIX-1619 Project: Felix Issue Type: Improvement Components: Main Affects Versions: felix-2.0.0 Reporter: Richard S. Hall Priority: Minor Fix For: felix-2.2.0 After thinking about this some more, I think the default configuration for Main should set the auto-deploy actions to install, start and not include update...at the time I set it originally, I was doing some shell bundle development so it seemed handy, but I think generally it probably makes sense to not do it this way and have people add update if they are doing updates to the bundles in the auto-deploy directory. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
[jira] Commented: (FELIX-1439) maven-bundle-plugin resource filtering does not substitute project.organization.*
[
https://issues.apache.org/jira/browse/FELIX-1439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12757372#action_12757372
]
Tim Moore commented on FELIX-1439:
--
Confirmed: 2.0.1 fixes my problem. Thanks!
maven-bundle-plugin resource filtering does not substitute
project.organization.*
-
Key: FELIX-1439
URL: https://issues.apache.org/jira/browse/FELIX-1439
Project: Felix
Issue Type: Bug
Components: Maven Bundle Plugin
Affects Versions: maven-bundle-plugin-2.0.0
Reporter: Tim Moore
Assignee: Stuart McCulloch
Fix For: maven-bundle-plugin-2.0.1
Attachments: FELIX-1439.patch
We have an XML file in our project's resource directory that contains various
Maven properties that are substituted by the maven-bundle-plugin at build
time. Most of the properties work (for example, ${pom.name},
${pom.description}, ${pom.version}) but ${pom.organization.name} and
${pom.organization.url} do not. Changing them to ${project.organization.name}
and ${project.organization.url} did not help.
These properties are a little unusual in that they refer to properties of a
nested object within the project model, kind of like how project.build works,
so they probably have to be special-cased the same way.
I notice that when I run mvn with -X, I see this in the BND Instructions:
[DEBUG] pom.organization: null
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Created: (FELIX-1620) Script for running the created Karaf instances with a console
Script for running the created Karaf instances with a console - Key: FELIX-1620 URL: https://issues.apache.org/jira/browse/FELIX-1620 Project: Felix Issue Type: Bug Components: Karaf Affects Versions: karaf-1.0.0 Reporter: David Bosschaert When I create a Karaf instance using the admin commands it creates start and stop scripts to run this instance in the background. I think this is really good for certain use-cases. But for other use-cases it would be important to simply launch that karaf instance with a console. In that case its important that the lifecycle of the instance is linked to the lifecycle of the console (so if someone exits the console, the instance dies). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
