On 01/02/2008, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>
> On Feb 1, 2008 1:19 PM, Oberhuber, Martin
> <[EMAIL PROTECTED]> wrote:
> > Hello Niall / Stuart,
> >
> > thanks for your answers. It looks like the usage patterns
> > of OSGi in the Apache and Eclipse communities are just
> > a bit diffe
On Feb 1, 2008 4:07 PM, Stuart McCulloch <[EMAIL PROTECTED]> wrote:
> On 01/02/2008, Niall Pemberton <[EMAIL PROTECTED]> wrote:
> >
> > Would it be possible to add bnd 0.0.236 to the maven repo so I can try
> > out these new features with Felix's bundle plugin?
> >
> > http://repo1.maven.org/maven2
o-generated.
> > But, as with any tool, you should verify it yourself and add
> > any customized
> > attributes and minor
> > adjustments.
> >
> > Otherwise you'll have to manually keep the manifest in step
> > with your code,
> > and it's amazingly
> &g
But for me, it also shows that in the current stage
> > it looks like the OSGi manifest still needs to be
> > written by hand and not auto-generated.
> >
> > Anyways, if there is a plan to make a downloadable
> > release of any commons packages with OSGi info
> >
ECTED] On Behalf
> Of Stuart McCulloch
> Sent: Donnerstag, 31. Jänner 2008 16:53
> To: [EMAIL PROTECTED]
> Cc: Jakarta Commons Developers List; Orbit Developer discussion
> Subject: Re: Support for OSGi
>
> On 31/01/2008, Oberhuber, Martin
> <[EMAIL PROTECTED]> wrote
On 31/01/2008, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>
> These isn't much OSGi knowledge here in commons - we're doing this at
> the request of the Apache Felix project so that they don't have to
> re-package our artifacts for OSGi. So I'm hoping that someone from
> Felix will pick up your sec
well enough to craft an OSGi manifest yourself)
Anyways, if there is a plan to make a downloadable
> release of any commons packages with OSGi info
> added, I'd like to know.
>
> Thanks,
> --
> Martin Oberhuber, Senior Member of Technical Staff, Wind River
> Target Management
SGi info
added, I'd like to know.
Thanks,
--
Martin Oberhuber, Senior Member of Technical Staff, Wind River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
-Original Message-
From: Niall Pemberton [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 29, 200
pache.org/commons/CommonsOsgi
Thanks for the feedback, much appreciated.
Niall
> Thanks,
> --
> Martin Oberhuber, Senior Member of Technical Staff, Wind River
> Target Management Project Lead, DSDP PMC Member
> http://www.eclipse.org/dsdp/tm
>
>
>
>
> > -Original Me
d River
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
> -Original Message-
> From: Niall Pemberton [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 29, 2008 11:30 PM
> To: Commons Developers List
> Cc: [EMAIL PROTECTED]
> Subject:
I have created a JIRA ticket for the changes to the commons-parent pom
to add the bundle plugin:
https://issues.apache.org/jira/browse/COMMONSSITE-23
I have also tested out the plugin by generating the jars/manifest for
all but three components:
http://people.apache.org/~niallp/commons-osgi/
sebb <[EMAIL PROTECTED]> schrieb:
> On 22/01/2008, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> > Mark Proctor wrote:
> > > Torsten Curdt wrote:
> > >>
> > >> On 21.01.2008, at 10:08, Tom Schindl wrote:
> > >>
> > >>> Hi Torsten,
> > >>>
> > >>> I understand this but we are seeing many J2EE-Serv
On 22/01/2008, Jörg Schaible <[EMAIL PROTECTED]> wrote:
> Mark Proctor wrote:
> > Torsten Curdt wrote:
> >>
> >> On 21.01.2008, at 10:08, Tom Schindl wrote:
> >>
> >>> Hi Torsten,
> >>>
> >>> I understand this but we are seeing many J2EE-Servers adopting OSGi
> >>> and many applications (I admit mo
Mark Proctor wrote:
> Torsten Curdt wrote:
>>
>> On 21.01.2008, at 10:08, Tom Schindl wrote:
>>
>>> Hi Torsten,
>>>
>>> I understand this but we are seeing many J2EE-Servers adopting OSGi
>>> and many applications (I admit most of them in Eclipse-world) also.
>>> It seems strange to me in those
Torsten Curdt wrote:
On 21.01.2008, at 10:08, Tom Schindl wrote:
Hi Torsten,
I understand this but we are seeing many J2EE-Servers adopting OSGi
and many applications
(I admit most of them in Eclipse-world) also. It seems strange to me
in those envs to use this "artificial"
package to overc
Tom Schindl wrote:
> Hi,
>
> Couldn't this OSGi-adoption made by some commons packages make the
> package shift for java5 unneeded?
> With OSGi one can run different versions in the same JVM so its not
> needed any more.
Well, there's a world outside of OSGi ...
- Jörg
Torsten Curdt <[EMAIL PROTECTED]> schrieb:
>
> On 21.01.2008, at 10:08, Tom Schindl wrote:
>
> > Hi Torsten,
> >
> > I understand this but we are seeing many J2EE-Servers adopting OSGi
> > and many applications
> > (I admit most of them in Eclipse-world) also. It seems strange to
> > me
On 21.01.2008, at 10:08, Tom Schindl wrote:
Hi Torsten,
I understand this but we are seeing many J2EE-Servers adopting OSGi
and many applications
(I admit most of them in Eclipse-world) also. It seems strange to
me in those envs to use this "artificial"
package to overcome jar-hell (which
Hi Torsten,
I understand this but we are seeing many J2EE-Servers adopting OSGi and
many applications
(I admit most of them in Eclipse-world) also. It seems strange to me in
those envs to use this "artificial"
package to overcome jar-hell (which is the only reason for the
java5-package right?)
Not everyone is using OSGi ...so I doubt this is really an option to
prevent a package shift.
My 2 cents
--
Torsten
On 21.01.2008, at 09:13, Tom Schindl wrote:
Hi,
Couldn't this OSGi-adoption made by some commons packages make the
package shift for java5 unneeded?
With OSGi one can run di
Hi,
Couldn't this OSGi-adoption made by some commons packages make the
package shift for java5 unneeded?
With OSGi one can run different versions in the same JVM so its not
needed any more.
Tom
Niall Pemberton schrieb:
On Dec 28, 2007 2:39 PM, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
T
On Dec 28, 2007 2:39 PM, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> Two things:
>
> - if the bundle plugin could be released, it'd be great, if not
> projects won't be able to make a release
>
> - my approach to add an osgified manifest to the current project is
> different in order not to change
Forwarding to the Felix list.
Carsten
--
Carsten Ziegeler
[EMAIL PROTECTED]
--- Begin Message ---
On Dec 28, 2007 12:35 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Hi,
>
> in the meantime Stuart fixed the problem with the maven bundleplugin, so
> I think we can give it a test drive :)
>
> A
On Dec 28, 2007 12:35 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Hi,
>
> in the meantime Stuart fixed the problem with the maven bundleplugin, so
> I think we can give it a test drive :)
>
> Attached is a patch for the parent pom of commons and one to demonstrate
> how to add support for OSG
On Dec 30, 2007, at 10:10 PM, Niclas Hedhman wrote:
On Thursday 20 December 2007 03:28, simon wrote:
If you provide patches, I'm happy to apply them for commons-logging
and
commons-digester.
Please do not do this for commons-logging. Pax Logging provides the
commons-logging API, and hooks
Niall Pemberton wrote:
> On Dec 28, 2007 12:35 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> in the meantime Stuart fixed the problem with the maven bundleplugin, so
>> I think we can give it a test drive :)
>>
>> Attached is a patch for the parent pom of commons and one to demonstra
On Dec 28, 2007 12:35 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Hi,
>
> in the meantime Stuart fixed the problem with the maven bundleplugin, so
> I think we can give it a test drive :)
>
> Attached is a patch for the parent pom of commons and one to demonstrate
> how to add support for OSG
Henri Yandell wrote:
>
> Guess that means Lang should start using m2 and not m1 for the release :)
:)
It's also possible to add the meta information to the jar "by hand". So
you could look at the result of the m2 build and then add the manifest
entries by hand using the m1 build - it's not that f
On Dec 28, 2007 4:35 AM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Hi,
>
> in the meantime Stuart fixed the problem with the maven bundleplugin, so
> I think we can give it a test drive :)
>
> Attached is a patch for the parent pom of commons and one to demonstrate
> how to add support for OSGi
On Monday 31 December 2007 14:57, Alan D. Cabrera wrote:
> I'm sorry but I'm not completely following. What problems does this
> create? How is it counter-productive.
Commons-logging is not designed for
a) OSGi environment with classes loaded and unloaded in runtime.
b) Unifying Commons-logg
On Thursday 20 December 2007 03:28, simon wrote:
> If you provide patches, I'm happy to apply them for commons-logging and
> commons-digester.
Please do not do this for commons-logging. Pax Logging provides the
commons-logging API, and hooks into a unified logging framework specifically
designed
Two things:
- if the bundle plugin could be released, it'd be great, if not
projects won't be able to make a release
- my approach to add an osgified manifest to the current project is
different in order not to change the packaging to bundle. bundle
packaging only needs to be used to osgify 3rd p
Hi,
in the meantime Stuart fixed the problem with the maven bundleplugin, so
I think we can give it a test drive :)
Attached is a patch for the parent pom of commons and one to demonstrate
how to add support for OSGi to commons-lang.
The changes to the parent pom are minimal: it just adds the ma
nicolas de loof schrieb:
> I also got some troubles when (quick) testing the felix bundle-plugin :
> I have configured the maven-jar-plugin to set some custom MANIFEST entries
> (in my case, the SVN revision number as Build-Revision). When using the
> felix plugin, my MANIFEST is replaced by OSGi o
I also got some troubles when (quick) testing the felix bundle-plugin :
I have configured the maven-jar-plugin to set some custom MANIFEST entries
(in my case, the SVN revision number as Build-Revision). When using the
felix plugin, my MANIFEST is replaced by OSGi one, not merged.
But maybe I miss
Thanks for the very positive response so far! Great!
I'll come up with some patches for some of the commons projects; there
is a minor problem as the current commons parent pom defines the
manifest entries, but I think that we can come up with a solution for this.
Carsten
--
Carsten Ziegeler
[E
On 20/12/2007, Niall Pemberton <[EMAIL PROTECTED]> wrote:
>
> We have a mixed bag of build systems here at commons. Until recently
> we were pretty much maven1, with the odd ant/maven1 mixture. A few
> components have m2 builds that have been used in anger and recently we
> added m2 builds for all
Carsten Ziegeler wrote:
Now, it would be great, if the projects here at Apache Commons would
already provide artifacs that can be directly used in an OSGi environment.
I think that this is a really good idea, benefitting both us and OSGi.
If maven 2 can generate all this for us, then it might
In general I think it's a good idea. Happy to help and apply patches.
cheers
--
Torsten
It would be great if some of the projects here could add these
meta data
as part of their next release. This will make the life of all
projects
using OSGi much much easier.
So if you're interested in he
On Dec 19, 2007 2:38 PM, Carsten Ziegeler <[EMAIL PROTECTED]> wrote:
> Hi,
>
> the products of commons are highly used throughout many projects.
>
> It would be great, if the projects here at Apche Commons could help
> those projects that are using OSGi.
>
> OSGi is based around the concept of a bu
On Wed, 2007-12-19 at 15:38 +0100, Carsten Ziegeler wrote:
> Hi,
>
> the products of commons are highly used throughout many projects.
>
> It would be great, if the projects here at Apche Commons could help
> those projects that are using OSGi.
If you provide patches, I'm happy to apply them fo
nicolas de loof wrote:
> Could such support be added using maven-osgi ?
> (https://svn.apache.org/repos/asf/maven/shared/trunk/maven-osgi/)
This artifact contains some utility code - in fact it is used by the
Felix bundleplugin
http://svn.apache.org/repos/asf/felix/trunk/bundleplugin
So, you need t
Could such support be added using maven-osgi ?
(https://svn.apache.org/repos/asf/maven/shared/trunk/maven-osgi/)
I've never used it myself, but from what I've read on osgi, the bundle
meta-datas could be created based on the POM (for modules depdendencies,
version, etc..) Just the public API needs
What a great idea this would be nice for me as RCP developer because
currently I have to create my
own bundles from the commons-packages.
Tom
Carsten Ziegeler schrieb:
Hi,
the products of commons are highly used throughout many projects.
It would be great, if the projects here at Apche Commo
44 matches
Mail list logo
