Hello,
we have the following problem starting a bundle with obr:
In the bundle's manifest we have a header entry:
Bundle-RequiredExecutionEnvironment: OSGi/Minimum-1.0
bindex is generating this xml entry (within the element):
Execution Environment (|(ee=OSGi/Minimum-1.0))
When we t
bindex when using version ranges
Hi,
Hampel, Michael schrieb:
> Hello,
>
> when using version ranges like ;version="[2.4.0, 3.0.0)"
> in the Import-Package manifest header the bindex tool fails to
> generate the repository.xml file.
> A NumberFormatException is
Hello,
when using version ranges like ;version="[2.4.0, 3.0.0)"
in the Import-Package manifest header the bindex tool fails to
generate the repository.xml file.
A NumberFormatException is thrown for input string "[2".
Is this a known bug?
Thanx in advance for any help,
Michael
PROTECTED]
Gesendet: Dienstag, 02. Dezember 2008 16:16
An: users@felix.apache.org
Betreff: Re: bnd version policy for import-package
2008/12/2 Hampel, Michael <[EMAIL PROTECTED]>
> Hello,
>
> I have a question about how bnd determines the version for an
> import-package.
> (I am u
Hello,
I have a question about how bnd determines the version for an
import-package.
(I am using the maven bundle plugin version 1.4.3).
I have the following behaviour:
If I export packages with the version 1.0.25 then bnd imports these
packages with version 1.0.
(I think this is conform to the
tions
must add these operators as described in RFC 112. I am not sure what
software you are running, but the software should adapt ... The OBR
filter syntax is a superset of the OSGi filter syntax.
Kind regards,
Peter Kriens
On 30 sep 2008, at 08:03, Hampel, Michael wrote:
>
&g
gi.org/Download/File?url=/download/rfc-0112_BundleRepository.pdf
Kind regards,
Peter Kriens
On 29 sep 2008, at 13:00, Hampel, Michael wrote:
> Hello,
>
> today I ran into a problem when generating my repository.xml with
> bindex:
> Spring-core has a manifest entry:
>
Hello,
today I ran into a problem when generating my repository.xml with
bindex:
Spring-core has a manifest entry:
org.eclipse.core.runtime;resolution:=optional;common=split
Bindex will generate the following entry:
Import package org.eclipse.core.runtime
The problem is the
mandat
Hello,
With the felix maven-bundle-plugin it is possible to add a
element.
META-INF would place the generated
Manifest.MF
File in a META-INF folder at the root of your project and therefore enables
eclipse pde
To find your maven generated manifest.
HTH,
Michael
-Ursprüngliche Nachricht
Hello,
I have a question regarding the error handling in the
ResolverImpl.deploy() method.
As the method catches all Exceptions that might occur when installing or
starting a bundle and also has no
return value to check for problems, I am not able to react on failures
in my calling code.
I have a
ouldn't need to import this package unless
you actually use the type - otherwise the bytecode would
reference the containing package
do you have an example where the package is missing and
this causes an exception at runtime? (if so please open a
JIRA issue and attach the example project)
Clement
Hello,
I have a class with a method
public Collection getJobs(Object jobProcessor) {
return jobProcessor.getJobs();
}
The class imports MyType.
When I build the class with the maven-bundle-plugin the resulting
Manifest is not adding the MyTypes package
to its Import-Packages.
When
Export-Package header which one can
get from a call to getHeaders(). In case you create a bug report feel
free to post a reference here as well, then we can comment on the bug
as well :-)
regards,
Karl
On Fri, Mar 28, 2008 at 9:47 AM, Hampel, Michael
<[EMAIL PROTECTED]> wrote:
>
> Thank
Export-Package header which one can
get from a call to getHeaders(). In case you create a bug report feel
free to post a reference here as well, then we can comment on the bug
as well :-)
regards,
Karl
On Fri, Mar 28, 2008 at 9:47 AM, Hampel, Michael
<[EMAIL PROTECTED]> wrote:
>
> T
Yes, you are probably correct...at least it sounds reasonable.
>>
>> What we probably need to do is modify LocalRepositoryImpl to special
>> case the system bundle to calculate its exported packages differently...
>>
>> Please feel free to look into this issue an
changed.
Thanx in advance for any help,
Michael
-Ursprüngliche Nachricht-
Von: Hampel, Michael
Gesendet: Donnerstag, 20. März 2008 13:21
An: users@felix.apache.org
Betreff: AW: obr resolving and system packages
Hello again,
I have now listed the exported packages of my system bundle
eived this
e-mail in error, you are hereby notified that any review, copying or
distribution of it is strictly prohibited. Please inform us immediately and
destroy the original transmittal. Thank you for your cooperation.
-Ursprüngliche Nachricht-
Von: Hampel, Michael
Gesendet: Donn
an assumption?
OBR treats the locally installed bundles as a repository too. So, if
your local system bundle exports javax.swing, then it should resolve the
package correctly...at least that is how it is supposed to work.
-> richard
Hampel, Michael wrote:
> Hello,
>
> h
Hello,
how do I deal with system package dependencies like javax.swing - that
an OSGi runtime would be able to resolve from the system classpath -
in the OBR resolving process.
If a resource in my repository.xml has a require element for javax.swing
the Resolver tries to find the dependency in o
Hello Stuart,
thanx a lot for the fast help and the fix - it is working now.
Thank you again,
Michael
Hello,
I have just encountered the following behaviour when executing a maven
reactor build:
We have a parent pom where we configure the maven-bundle-plugin with the
directory for the manifest location e.g.: META-INF.
(within the pluginManagement section)
In child poms the plugin is inherited an
Hello,
somewhere you have to specify the plugin version for Maven - if you don't do it
in
A parent pom you have to put it in your project's pom file.
The advantage to specify the version in a parent pom is that you will inherit
the plugin version
in all child projects.
HTH,
Michael
-U
Hello Stuart,
I have tried it and it's working great - thank you a lot for the fast help,
Michael
-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Stuart McCulloch
Gesendet: Freitag, 21. September 2007 13:31
An: users@felix.apache.org
Betreff
: Freitag, 21. September 2007 13:30
An: users@felix.apache.org
Betreff: Re: split-package directive for maven bundle plugin
it needs to be:
-split-package:=merge-last
notice the ":=" v.s. your "=".
Does that change something?
regards,
Karl
On 9/21/07, Hampel, Michael <[
Hello,
I have a question regarding the bundleall goal of the bundle plugin.
Is it possible to instruct this goal with an inclusion/exclusion filter
based on the dependency scope (compile, runtime..) or the
optional element like it is possible with ?
Also can I configure the naming of the resulti
Hello,
thanx for your answers.
I am using hibernate and hibernate.annotations and therefore have to
osgify the jar files.
As both jars use org.hibernate as package root I have 3 packages with
the same name and therefore I am creating
one bundle from the two jars.
Karl's notation is working but th
se IDE
OSGi startup?
On 21/09/2007, Stuart McCulloch <[EMAIL PROTECTED]> wrote:
>
> Hi Michael,
>
> On 21/09/2007, Hampel, Michael <[EMAIL PROTECTED]> wrote:
> >
> > Hello,
> >
> > Regarding the answer of Stuart I have a question about the intended use
Hello,
Regarding the answer of Stuart I have a question about the intended use of the
bundleplugin
Manifest goal.
In the moment we are using the goal to generate the Manifest file to run our
bundles within
Eclipse (put the generated Manifest file where Eclipse expects it). (the
manifest goal ru
I only realized after sending this to the felix dev list that there is a
felix users list - so I post this here again - sorry
Hello,
after working a while now with the maven-bundle-plugin I would like to
share some
observations and ask questions about them.
I am using the plugin in my poms
29 matches
Mail list logo
