Hi Jeremy,
Thanks for pointing this out. Can you please file a JIRA issue ? I will
fix it ASAP.
In fact, the default value of the immediate attribute depends on the
presence of a element: If the element is present, the default
is "false", if the element is NOT present, the default is "true".
Cur
Stuart McCulloch skrev:
On 13/08/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
Karl Pauls wrote:
I'm not sure I really like the idea that we create all those artifacts
of other projects. I was assuming that we would only provide the
wrapper pom's as a starting point for the projects to ultima
While there is interest in getting NetBeans to run on top of OSGi, most
people lack the time it would take to get it done. I would certainly
love to see it happen and would find it interesting to work on, but I
just don't have the time to devote to it presently.
The NetBeans page you reference
Hi all,
It seems that if I don't explicitly specify 'immediate="true"' in my
component description, Felix DS assumes it to be delayed. I then get
errors which say that my component is marked delayed but provides no
services.
>From the spec, section 112.2.2:
"A component is an immediate componen
[
https://issues.apache.org/jira/browse/FELIX-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard S. Hall resolved FELIX-333.
---
Resolution: Fixed
Assignee: Richard S. Hall
I applied the patch, please close this issue
[
https://issues.apache.org/jira/browse/FELIX-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stuart McCulloch updated FELIX-333:
---
Attachment: FELIX-333_20070814.txt
Suggested patch (FELIX-333_20070814.txt) removes any new-li
[
https://issues.apache.org/jira/browse/FELIX-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519453
]
Stuart McCulloch commented on FELIX-333:
after discussions with Peter, these values can only come from the XML
On 14/08/07, Peter Kriens <[EMAIL PROTECTED]> wrote:
>
> I could filter it out but they can only come from the bundle plugin. I
> read the properties and manifest with proper readers that will not
> allow the newline, at least not accidentally. So I suggest to clean it
> up before the values are se
I could filter it out but they can only come from the bundle plugin. I
read the properties and manifest with proper readers that will not
allow the newline, at least not accidentally. So I suggest to clean it
up before the values are set?
Kind regards,
Peter Kriens
SM> Actually there
Actually there is a problem with the manifest, but it's not initially
obvious unless you open it using Linux.
Here's a similar example, note that there's a Unix newline that's not
followed by a space on the next line:
Include-Resource: foo=bar,
zzz=bar^M
Perhaps this
[
https://issues.apache.org/jira/browse/FELIX-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519449
]
Stuart McCulloch commented on FELIX-333:
Actually there is a problem with the manifest, but it's not initially
You're too good :-) The only strange thing I saw was actually the
tabs, but I can't imagine they are not allowed.
Kind regards,
Peter Kriens
SM> On 13/08/07, Peter Kriens <[EMAIL PROTECTED]> wrote: Hmm. I
SM> am generating the manifest with the java.util.jar.Manifest
SM> class. Are you
On 13/08/07, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
>
> Karl Pauls wrote:
> >
> > I'm not sure I really like the idea that we create all those artifacts
> > of other projects. I was assuming that we would only provide the
> > wrapper pom's as a starting point for the projects to ultimately mak
On 13/08/07, Peter Kriens <[EMAIL PROTECTED]> wrote:
>
> Hmm. I am generating the manifest with the java.util.jar.Manifest
> class. Are you sure this is not a parsing error in the Felix manifest?
Actually I think Tom said his target platform was Equinox, so it could
either be a parser error there
Karl Pauls wrote:
>
> I'm not sure I really like the idea that we create all those artifacts
> of other projects. I was assuming that we would only provide the
> wrapper pom's as a starting point for the projects to ultimately make
> their stuff available as bundles by themselves.
>
> It might ju
Hmm. I am generating the manifest with the java.util.jar.Manifest
class. Are you sure this is not a parsing error in the Felix manifest?
Kind regards,
Peter Kriens
SM> On 03/08/07, Dewire, Tom <[EMAIL PROTECTED]> wrote:
>> I'm using the 1.0.0 maven-bundle-plugin. It appears to be gener
> -Message d'origine-
> De : Richard S. Hall [mailto:[EMAIL PROTECTED]
> Envoyé : vendredi 10 août 2007 18:13
> À : dev@felix.apache.org
> Objet : Re: [FELIX-219] Applying the patch
>
> ...
> I think getting support in the bundle plugin for OBR is a good thing,
> but any changes to OBR an
[
https://issues.apache.org/jira/browse/FELIX-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger reassigned FELIX-335:
---
Assignee: Felix Meschberger
> Configuration Admin updates with empty properties and th
[
https://issues.apache.org/jira/browse/FELIX-333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12519384
]
Peter Kriens commented on FELIX-333:
Why is the manifest corrupted? It seems ok to me?
> can create a corrupt ma
19 matches
Mail list logo
