What I read from the documentation is that "bundle:deploy-file adds a
local bundle file to a remote OBR". but I need the opposite while
using a maven dependency: "bundle:install-dependencies adds maven
bundle dependencies to a local OBR".
Furthermore I would depend on a specific maven reposit
Clement,
I just determined where the problem is.
I have a @Property defined:
@Property( name = "endOfLine", value = "\r\n")
protected String endOfLine;
when I change this line to
protected String endOfLine = "\r\n";
and remove the @Property everything works just fine.
So, it seems that the
Mike-
Please keep reply on-list and without thread trimming...
I didn't actually mean to hit send because this seemed to warrant a
longer response than I was prepared to give at the time.
First off, yes, I was answering your question in the context of
maven-bundle-plugin. Wildcards are perfectly
I don't know if this is intended or not, but it isn't surprising to me.
As an aside, I would be VERY careful about the version of packages
contained in the JDK/JRE. In general, the version numbers for JRE
packages isn't defined. Check the list archives for both felix-users and
osgi-dev for past di
Thanks if I find a reference for use of Web Start you will be the first to know.
I just heard that Web Start has problems with SOCKS Proxy. Hopefully OSGi does
not have issues with that type of proxy.
Regards,
-Tony
- Original Message
From: Richard S. Hall
To: users@felix.apache.org
Don't use .*
On Sep 27, 2010, at 12:09 PM, mvangeert...@comcast.net wrote:
>
>
> All,
>
>
>
> Currently, I am having an issue where when I include 2 specific packages in
> the import directive of the maven-bundle-plugin, the plugin decides it
> doesn't need them, and leaves them out, ev
Using maven-bundle-plugin version 2.1.0, in my import package I have the
following:
javax.xml.*;version="1.6",
javax.xml.bind.*;version="2.1.0",
javax.xml.bind.annotation.*;version="2.1.0"
In the MANIFEST.MF file that is generated, I see the following:
Import-Packag
All,
Currently, I am having an issue where when I include 2 specific packages in the
import directive of the maven-bundle-plugin, the plugin decides it doesn't need
them, and leaves them out, even if I change the resolution to "mandatory".
These packages are used to set up my tibco JMS qu
On 9/27/10 11:07, Tony Anecito wrote:
First off thanks Richard for your prompt replies.
What I did using web start was have seperate bundles for each OS/arch for the
swing client so there is no duplication. I kept the java classes out of the
native lib jars for web start. So do I have to duplic
First off thanks Richard for your prompt replies.
What I did using web start was have seperate bundles for each OS/arch for the
swing client so there is no duplication. I kept the java classes out of the
native lib jars for web start. So do I have to duplicate the bundles with the
classes since
It sounds to me like you should use bundle:deploy-file. That goal allows
you to specify the URL to the deployed bundle.
On 9/25/10 1:29 AM, Enrico Schnepel wrote:
> Thanks for your answer.
>
> I am rebundling to achive a higher goal ... I want to put a maven bundle
> dependency into the obr. inst
Yes the app is the Java Swing client that I am trying to bundle.
Thanks,
-Tony
- Original Message
From: Michael Hess
To: users@felix.apache.org
Sent: Mon, September 27, 2010 1:08:07 AM
Subject: Re: OSGi and Signing...
> Seems signing is an option in OSGi. The question came up at Java
Many thanks that is the next step once I work out the native lib bundle issues.
-Tony
- Original Message
From: Charles Moulliard
To: users@felix.apache.org
Sent: Mon, September 27, 2010 12:44:57 AM
Subject: Re: 3rd party jars...
Hy Toni,
Here is the maven plugin that we use in Apach
On 9/26/10 23:52, Tony Anecito wrote:
Hi All,
If you have a 3rd party jar how does it get included? Seems like OSGi requires
the manifest to be modified which might be an issue. When "bundled" is there
another manifest created for OSGi?
You can wrap a JAR file in a bundle JAR file by embeddin
On 9/27/10 1:52, Marcel Offermans wrote:
On 27 Sep 2010, at 5:09 , Richard S. Hall wrote:
On 9/26/10 22:22, Tony Anecito wrote:
I have my native libs for each OS in separate jars and in some cases I have
quite a few jars. I have some simple questions
1. Can I keep my native jars as separate b
On 9/26/10 23:41, Tony Anecito wrote:
Okay the reason I asked about the *.dll because I have over 200 dlls. I can
write a program that reads the libs and creates the names with the ; for the
manifest file I guess.
Yeah, I'd recommend that.
When I said separate bundles I meant one for native
On 9/26/10 23:58, Tony Anecito wrote:
Hi All,
Does Felix support pack200 compression?
No, but it should be fairly easy to create a bundle that supports it.
-> richard
Thanks,
-Tony
-
To unsubscribe, e-mail: users-unsub
Hi,
On 25.09.2010, at 10:05, Clement Escoffier wrote:
>
> On 24.09.2010, at 18:02, Joel Schuster wrote:
>
>> Made the same changes, upgraded to 384 of bnd task and removed Service
>> interface extension.
>>
>> You are running on Windows 7? Everything works fine for me on XP, but not
>> Win7.
> If you have a 3rd party jar how does it get included? Seems like OSGi
requires
> the manifest to be modified which might be an issue. When "bundled" is
there
> another manifest created for OSGi?
There is no definite answer to this, as you first need to state what you
are planning
to do with
> Seems signing is an option in OSGi. The question came up at JavaOne if
signing
> was needed. If not signed and the app is installed using OSGi will there
be
> issues?
>
> This would be a plus for Felix/OSGi if the java app ran without needing
> certificates.
I am not really sure which app
20 matches
Mail list logo
