[
https://issues.apache.org/jira/browse/FELIX-4467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Thomas Watson updated FELIX-4467:
-
Description:
My understanding is that the SCR implementation bundle uses its own bundle
context
[
https://issues.apache.org/jira/browse/FELIX-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947032#comment-13947032
]
Nicolas Roduit edited comment on FELIX-4281 at 3/25/14 7:35 PM:
Thomas Watson created FELIX-4467:
Summary: Option to use system bundle context for tracking bundles
Key: FELIX-4467
URL: https://issues.apache.org/jira/browse/FELIX-4467
Project: Felix
Issue
[
https://issues.apache.org/jira/browse/FELIX-4281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13947032#comment-13947032
]
Nicolas Roduit commented on FELIX-4281:
---
http://www.mail-archive.com/users%40felix.a
[
https://issues.apache.org/jira/browse/FELIX-4425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-4425.
Resolution: Fixed
Fix Version/s: gogo.shell-0.12.0
Assignee: Richard S. Hall
Thanks to take into account this bug
(https://issues.apache.org/jira/browse/FELIX-4425) in the next release.
A fix is proposed in JIRA.
[
https://issues.apache.org/jira/browse/FELIX-4466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
J.W. Janssen resolved FELIX-4466.
-
Resolution: Fixed
Fixed in rev #1581373.
> Deployment Admin does not always fire events
> --
>
> By the way if we talk about Felix "components" - Why there are "org.osgi.*"
>> and "javax.servlet.*" modules instead of direct dependencies on e.g.,
>> org.osgi:core:4.3.0 or javax.servlet:javax.servlet-api (which is proper
>> OSGi bundle for 3.x version and there must be somewhere proper 2.4
>
J.W. Janssen created FELIX-4466:
---
Summary: Deployment Admin does not always fire events
Key: FELIX-4466
URL: https://issues.apache.org/jira/browse/FELIX-4466
Project: Felix
Issue Type: Bug
On 3/25/14, 10:50 , Grzegorz Grzybek wrote:
And (in Git terms) decomposite the repository into separate repos (or
submodules)?
Well, in SVN terms, all Apache projects share one big tree, and you always
just checkout specific parts (submodules as you wish). Admittedly, you can
probably not yet ch
Thanks for replies!
That's what I thought - that Felix modules are more _loosely coupled_ than
[maven] modules of for example CXF or Karaf.
So maybe you get rid of this Ant build?
And (in Git terms) decomposite the repository into separate repos (or
submodules)?
regards
Grzegorz Grzybek
2014-03
>
> > And (in Git terms) decomposite the repository into separate repos (or
> > submodules)?
>
> Well, in SVN terms, all Apache projects share one big tree, and you always
> just checkout specific parts (submodules as you wish). Admittedly, you can
> probably not yet checkout a single subproject of
On 25 Mar 2014, at 15:34 , Grzegorz Grzybek wrote:
> Thanks for replies!
>
> That's what I thought - that Felix modules are more _loosely coupled_ than
> [maven] modules of for example CXF or Karaf.
> So maybe you get rid of this Ant build?
We probably should. Let’s wait and see a bit if anybod
I agree, subprojects evolve at their own rate. We could encourage everybody to
move to the latest plugin and parent though. Maybe we should remove the top
level build that tries to build all subprojects completely, and just explain to
everybody to go into the subproject of choice to build it.
G
There has never really been a reliable way to build trunk. For the most
part, we just build the subprojects of interest.
I'm not sure there is much value in a trunk build, especially if it
causes subprojects to have to evolve in lock step.
-> richard
On 3/25/14, 04:45 , Grzegorz Grzybek wrot
Clement Escoffier created FELIX-4465:
Summary: Service Controller cannot be set to true in the
constructor
Key: FELIX-4465
URL: https://issues.apache.org/jira/browse/FELIX-4465
Project: Felix
Clement Escoffier created FELIX-4464:
Summary: Wrong configuration admin package import / export clause
Key: FELIX-4464
URL: https://issues.apache.org/jira/browse/FELIX-4464
Project: Felix
[
https://issues.apache.org/jira/browse/FELIX-4463?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
J.W. Janssen resolved FELIX-4463.
-
Resolution: Fixed
Solved in rev #1581302.
> DA does not consistently handle non-unique resources
[
https://issues.apache.org/jira/browse/FELIX-1835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
J.W. Janssen resolved FELIX-1835.
-
Resolution: Cannot Reproduce
Cannot reproduce with latest code, but added an additional itest in
J.W. Janssen created FELIX-4463:
---
Summary: DA does not consistently handle non-unique resources
Key: FELIX-4463
URL: https://issues.apache.org/jira/browse/FELIX-4463
Project: Felix
Issue Type:
Hello all!
I was trying to build clean trunk of Felix. I added new *profile*consisting of
*all* modules and it was built fine without problems on JDK6 and Maven
3.0.x.
So my first question is: is the ANT buildfile still needed? The problematic
MNG-1682 issue was resolved long time ago...
But aft
Great!
I was wondering is there a page where we list 'new and noteworthy'
features of a release? https://felix.apache.org/news.html doesn't give
much detail and it would be good to record somewhere that Felix now
provides Core R5 support...
Cheers,
David
On 24 March 2014 16:28, Karl Pauls wrot
22 matches
Mail list logo