Hi Peter,
Due to bad internet service in China, i can hardly connected to Github
web site, so i decided to host my project source code in Google Code
web site first, and finished initial source code commit job, its
address is here [1]. I do not know whether Apache can supply some SVN
workspace for
On Tue, May 3, 2011 at 6:38 PM, Richard S. Hall wrote:
> On 5/3/11 11:46, Pierre De Rop wrote:
>>
>> Hi Richard,
>>
>> - For dm.annotation, indeed, we don't embed json in the artifact, we are
>> only using it at runtime, when the maven plugin is running.
>> So you mean that we can remove LICENSE.j
On 5/3/11 11:46, Pierre De Rop wrote:
Hi Richard,
- For dm.annotation, indeed, we don't embed json in the artifact, we are
only using it at runtime, when the maven plugin is running.
So you mean that we can remove LICENSE.json ?
Yes, I thought that was the rule (i.e., only include the license
Hi Richard,
- For dm.annotation, indeed, we don't embed json in the artifact, we are
only using it at runtime, when the maven plugin is running.
So you mean that we can remove LICENSE.json ?
- For the extra root changelogs, I will remove them from dm.annotation and
dm.runtime.
thanks !
/pierre
O
+1
Does dm.annotations include JSON? It includes the JSON license, but I
thought we only did that if the artifact included the dependency, not
just used it. It also has two changelog.txt files (in root and doc/).
Runtime also has two changelog.txt files.
I also fixed some references to inclu
[
https://issues.apache.org/jira/browse/FELIX-2727?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13028153#comment-13028153
]
Konrad Windszus commented on FELIX-2727:
This issue also leads to Felix not starti
Bundles with higher start level get activated even before framework reaches
that start level
Key: FELIX-2942
URL: https://issues.apache.org/jira/browse/FELIX-2942
+1
