DependencyManager ConfigurationDependency update isn't propagated to super
classes
--
Key: FELIX-2987
URL: https://issues.apache.org/jira/browse/FELIX-2987
Project: Felix
[
https://issues.apache.org/jira/browse/FELIX-2961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13046319#comment-13046319
]
Andrei Pozolotin commented on FELIX-2961:
-
re: "new feature of the @Component anno
On 6/8/11 11:16, Peter Kriens wrote:
Obviously everybody needs all these goodies you mention. However the choice is to do this
in iPOJO with a new "language" and new semantics
Actually, there is no new "language"...the annotations are basically the
same as the ones you like for DS...but, yes,
Obviously everybody needs all these goodies you mention. However the choice is
to do this in iPOJO with a new "language" and new semantics attached to it or
do it in Java. I am very familiar with the semantics of Java and the pain of
the redundancy in Java over iPOJO in this area has not been hi
[
https://issues.apache.org/jira/browse/FELIX-2963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045988#comment-13045988
]
Andrei Pozolotin commented on FELIX-2963:
-
still does not work for me; probably I
[
https://issues.apache.org/jira/browse/FELIX-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13045978#comment-13045978
]
Andrei Pozolotin commented on FELIX-2980:
-
now I am getting NPE again :-)
it seem
On 6/8/11 9:13, Peter Kriens wrote:
The summary for me is that DS is limited to simplifying being a service and
depending on other services while iPOJO and Blueprint add a programming
language (XML/Annotations) that support services among many, many other
features.
In my experience DS is the
The summary for me is that DS is limited to simplifying being a service and
depending on other services while iPOJO and Blueprint add a programming
language (XML/Annotations) that support services among many, many other
features.
In my experience DS is the simplest and least intrusive, especial
I think the primary focus is grouping packages with the following rules:
1) Group packages that are strongly connected
2) Start with the largest group and try to merge groups into it that do
not cause additional dependencies
3) repeat for all groups
I think you need a cos
Hi Peter,
I am working about source code dependencies analyse algorithm design
and implement job, i will finish the whole analyse algorithm in the
coming month. This algorithm include two sections: package and class.
1. Package section
a. It can analyse package cycles in project source code
b. A
10 matches
Mail list logo
