Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[Eike Kettner]

Hi Daniele,

sorry for answering this late, anyways, inline reply.


On [Fri, 22.04.2011 16:09], Daniele Dellafiore wrote:
> Hi, sorry I read your reply only today...
> I got basically to the same results yesterday, but I've some problem which I
> summarized in the last message in this thread on felix mailing list:
> 
> http://old.nabble.com/A-better-life%3A-quick-webapp-deploy-to31334158.html
> 
> I'll go into details point by point.
> 
> On Fri, Apr 8, 2011 at 3:29 PM, Eike Kettner  wrote:
> 
> > Hi Daniele,
> >
> > I might have not understood your concern well enough... But here is what I
> > do: I deploy a really small war file (without any deps of course) into the
> > osgi container (I use felix...). There is another bundle from pax,
> > called pax-web-extender, that "listens" for war files coming into the
> > container and will then register them on the embedded jetty instance.
> >
> > I use the following pax bundles:
> > * org.ops4j.pax.web.pax-web-extender-war
> > * org.ops4j.pax.web.pax-web-jetty-bundle
> > * org.ops4j.pax.web.pax-web-jsp   (might be superfluous)
> >
> 
> yeah I've everything installed. I do not remember what osgi features
> installed this but there is:
> 
> [  54] [Active ] [] [   ] [   60] OPS4J Pax Web -
> Runtime (1.0.1)
> [  55] [Active ] [] [   ] [   60] OPS4J Pax Web - API
> (1.0.1)
> [  56] [Active ] [] [   ] [   60] OPS4J Pax Web - Jetty
> (1.0.1)
> [  57] [Active ] [] [   ] [   60] OPS4J Pax Web -
> Service SPI (1.0.1)
> [  59] [Active ] [] [   ] [   60] OPS4J Pax Web -
> Extender - Whiteboard (1.0.1)
> [  60] [Active ] [] [   ] [   60] OPS4J Pax Web -
> FileInstall Deployer (1.0.1)
> [  61] [Active ] [] [   ] [   60] OPS4J Pax Url - war:,
> war-i: (1.2.5)
> [  62] [Active ] [] [   ] [   60] OPS4J Pax Web -
> Extender - WAR (1.0.1)
> [  63] [Active ] [] [   ] [   60] OPS4J Pax Web - Jsp
> Support (1.0.1)
> 
> on Karaf 2.2.0
> 
> 
> >
> > Then I use the felix-bundle plugin to create a MANIFEST.MF for my war
> > file. It looks like that:
> >
> >
> >  
> >org.apache.felix
> >maven-bundle-plugin
> >
> >  
> >bundle-manifest
> >process-classes
> >
> >  manifest
> >
> >  
> >
> >
> >  
> >jar
> >war
> >bundle
> >  
> >  
> ><_include>-osgi.bnd
> >  
> >
> >  
> >  
> >org.apache.maven.plugins
> >maven-war-plugin
> >
> >  
> >
> >  ${project.build.outputDirectory}/META-INF/MANIFEST.MF
> >
> >  
> >
> >  
> >
> >
> >
> 
> it's almost the same as mine, also the war-plugin config is identical.
> I do not have
> 
><_include>-osgi.bnd
> 
> but I have this instructions
> 
>   <_wab>src/main/webapp
> /myApp


I didn't know about tha <_wab> configuration, This will maybe then add the
web bundle class path to the headers, so it needn't be specified
explicitely.
 
> There are some more instructions in the "osgi.bnd" file. You could have
> > written them directly in the  section of the bundle plugin:
> >
> >  Bundle-Classpath: ., WEB-INF/classes
> >  Web-ContextPath: mywebapp
> >  DynamicImport-Package: *
> >  Webapp-Context: mywebapp
> >
> 
> It seems that maven-bundle-plugin, at least 2.3.4 version, automatically
> add  Bundle-Classpath: WEB-INF/classes if the project is a WAR or have a
> Webapp-Context (that make the bundle a WAB, as for OSGI in Action), in fact
> I do not have that intructions and the war project  Bundle-Classpath:
> WEB-INF/classes in the MANIFEST (note, without the dot).
> I think also that Webapp-Context has been deprecated in favor of the new
> Web-ContextPath you also have.

ok, thanks for the info, I used both headers (web-contextpath and
webapp-context) so far without issues, so I didn't worry to modify this
so far.

> As for DynamicImport-Package: *
> what does this do?


This is a very generic import header for the bundle. It is needed, if
you plan to have other bundles contribute wicket pages/components.
Wicket uses reflection to create page instances. In this case, the
classes must be available to the class loader. If you do not know them
up front, you can use the DynamicImport-Package statement.

 
> It does not seem you do not have specific Import or Export package
> instructions, so you use the maven-bundle-plugin defaults, so every dep is
> explicitly written in the MANIFEST right?

yes, every dep especially wicket is explicitely written in the manifest.

 
> 
> >
> > This creates a MANIFEST with Import-Package statements for all your
> > dependencies - they are not included in the war file. The war file has
> > no /lib folder, just WEB-IN

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[Daniele Dellafiore]

Hi, sorry I read your reply only today...
I got basically to the same results yesterday, but I've some problem which I
summarized in the last message in this thread on felix mailing list:

http://old.nabble.com/A-better-life%3A-quick-webapp-deploy-to31334158.html

I'll go into details point by point.

On Fri, Apr 8, 2011 at 3:29 PM, Eike Kettner  wrote:

> Hi Daniele,
>
> I might have not understood your concern well enough... But here is what I
> do: I deploy a really small war file (without any deps of course) into the
> osgi container (I use felix...). There is another bundle from pax,
> called pax-web-extender, that "listens" for war files coming into the
> container and will then register them on the embedded jetty instance.
>
> I use the following pax bundles:
> * org.ops4j.pax.web.pax-web-extender-war
> * org.ops4j.pax.web.pax-web-jetty-bundle
> * org.ops4j.pax.web.pax-web-jsp   (might be superfluous)
>

yeah I've everything installed. I do not remember what osgi features
installed this but there is:

[  54] [Active ] [] [   ] [   60] OPS4J Pax Web -
Runtime (1.0.1)
[  55] [Active ] [] [   ] [   60] OPS4J Pax Web - API
(1.0.1)
[  56] [Active ] [] [   ] [   60] OPS4J Pax Web - Jetty
(1.0.1)
[  57] [Active ] [] [   ] [   60] OPS4J Pax Web -
Service SPI (1.0.1)
[  59] [Active ] [] [   ] [   60] OPS4J Pax Web -
Extender - Whiteboard (1.0.1)
[  60] [Active ] [] [   ] [   60] OPS4J Pax Web -
FileInstall Deployer (1.0.1)
[  61] [Active ] [] [   ] [   60] OPS4J Pax Url - war:,
war-i: (1.2.5)
[  62] [Active ] [] [   ] [   60] OPS4J Pax Web -
Extender - WAR (1.0.1)
[  63] [Active ] [] [   ] [   60] OPS4J Pax Web - Jsp
Support (1.0.1)

on Karaf 2.2.0


>
> Then I use the felix-bundle plugin to create a MANIFEST.MF for my war
> file. It looks like that:
>
>
>  
>org.apache.felix
>maven-bundle-plugin
>
>  
>bundle-manifest
>process-classes
>
>  manifest
>
>  
>
>
>  
>jar
>war
>bundle
>  
>  
><_include>-osgi.bnd
>  
>
>  
>  
>org.apache.maven.plugins
>maven-war-plugin
>
>  
>
>  ${project.build.outputDirectory}/META-INF/MANIFEST.MF
>
>  
>
>  
>
>
>

it's almost the same as mine, also the war-plugin config is identical.
I do not have

   <_include>-osgi.bnd

but I have this instructions

  <_wab>src/main/webapp
/myApp

There are some more instructions in the "osgi.bnd" file. You could have
> written them directly in the  section of the bundle plugin:
>
>  Bundle-Classpath: ., WEB-INF/classes
>  Web-ContextPath: mywebapp
>  DynamicImport-Package: *
>  Webapp-Context: mywebapp
>

It seems that maven-bundle-plugin, at least 2.3.4 version, automatically
add  Bundle-Classpath: WEB-INF/classes if the project is a WAR or have a
Webapp-Context (that make the bundle a WAB, as for OSGI in Action), in fact
I do not have that intructions and the war project  Bundle-Classpath:
WEB-INF/classes in the MANIFEST (note, without the dot).
I think also that Webapp-Context has been deprecated in favor of the new
Web-ContextPath you also have.

As for DynamicImport-Package: *
what does this do?

It does not seem you do not have specific Import or Export package
instructions, so you use the maven-bundle-plugin defaults, so every dep is
explicitly written in the MANIFEST right?


>
> This creates a MANIFEST with Import-Package statements for all your
> dependencies - they are not included in the war file. The war file has
> no /lib folder, just WEB-INF/classes and META-INF/ are there. The bundle
> classpath is extended to include the classes in WEB-INF/classes. I
> use the scope "provided" for all dependencies.
>

where do you specify the "provided" scope? In all the maven deps explicitly?
There is not a way to tell just maven-bundle-plugin to consider everything
as provided just when building the bundle? I think that this is the reason
why you do not have jars in the lib folder, right?


>
> When the war file is deployed to the osgi container, the pax bundles
> from above will make it available to jetty.
>

In fact, it seems that if I just manually remove the jars from the lib
folder, the pax extensions starts but fails to found the classes cause it
expect to found them in the WEB-INF/lib. So, I get a series of
ClassNotFoundException for spring and wicket classes during the startup (as
you can read in the same thread
http://old.nabble.com/A-better-life%3A-quick-webapp-deploy-to31334158.html)


>
> In my case the war file contains a simple wicket application that itself
> listens for other bundles to finally create content.

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[Eike Kettner]

Hi Daniele,

I might have not understood your concern well enough... But here is what I
do: I deploy a really small war file (without any deps of course) into the
osgi container (I use felix...). There is another bundle from pax,
called pax-web-extender, that "listens" for war files coming into the
container and will then register them on the embedded jetty instance.

I use the following pax bundles:
* org.ops4j.pax.web.pax-web-extender-war  
* org.ops4j.pax.web.pax-web-jetty-bundle
* org.ops4j.pax.web.pax-web-jsp   (might be superfluous)

Then I use the felix-bundle plugin to create a MANIFEST.MF for my war
file. It looks like that:


  
org.apache.felix
maven-bundle-plugin

  
bundle-manifest
process-classes

  manifest

  


  
jar
war
bundle
  
  
<_include>-osgi.bnd
  

  
  
org.apache.maven.plugins
maven-war-plugin

  

  ${project.build.outputDirectory}/META-INF/MANIFEST.MF

  

  

 
There are some more instructions in the "osgi.bnd" file. You could have
written them directly in the  section of the bundle plugin:

  Bundle-Classpath: ., WEB-INF/classes
  Web-ContextPath: mywebapp
  DynamicImport-Package: *
  Webapp-Context: mywebapp

This creates a MANIFEST with Import-Package statements for all your
dependencies - they are not included in the war file. The war file has
no /lib folder, just WEB-INF/classes and META-INF/ are there. The bundle
classpath is extended to include the classes in WEB-INF/classes. I
use the scope "provided" for all dependencies. 

When the war file is deployed to the osgi container, the pax bundles
from above will make it available to jetty.

In my case the war file contains a simple wicket application that itself
listens for other bundles to finally create content. So its just a few
bytes and I can reload/redeploy the "content bundles" without affecting
the whole application.

Regards
Eike

On [Wed, 06.04.2011 23:09], Daniele Dellafiore wrote:
>  yes the idea is not to have the huber jar, it's all about this, is the main
> feature :)
> some guys in the felix maling list suggested me that's actually possible and
> supported, it's called WAB, that's a war without /lib (a partially reverse
> recursive achronim for A Better War)
> 
> http://old.nabble.com/A-better-life%3A-quick-webapp-deploy-to31334158.html
> 
> I'll go for that tomorrow.
> 
> On Wed, Apr 6, 2011 at 4:27 PM, Martin Grigorov wrote:
> 
> > I'm not an OSGi user but here is what I'll do.
> >
> > 1) create a new Maven project with packaging type 'pom'
> > 2) combine all wicket jars in one (uber-jar)
> >  there are several approaches here:
> > 1) maven-shade-plugin
> > 2) the way we did it in RC1 with maven-dependency-plugin: see
> >
> > http://repo2.maven.org/maven2/org/apache/wicket/wicket/1.5-RC1/wicket-1.5-RC1.pom
> >
> > Here check that works with simple Wicket app (e.g. the quickstart).
> >
> > Creating one big jar with all dependendies is against OSGi idea. The goal
> > is
> > to be able to replace dependencies without restarting, e.g. upgrade the
> > service layer without undeploying the presentation.
> > But if you still want to do it:  start adding more dependencies to be
> > packed
> > in the uber jar (spring, hibernate)
> >
> > About WicketFilter:
> > - you can use embedded Jetty or Guice Filter
> > and org.apache.wicket.protocol.http.WicketFilter.FILTER_MAPPING_PARAM (I
> > explained this earlier today in another thread)
> > - OSGi 4.1+ has the notion of enterprise OSGi and you can use plain OSGi
> > gymnastics to do that (I have no experience at all in this)
> >
> 
> 
> 
> 
> 
> --
> > Martin Grigorov
> > jWeekend
> > Training, Consulting, Development
> > http://jWeekend.com 
> >

-- 
email: e...@eknet.org   https://www.eknet.org  pgp: 481161A0

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[Daniele Dellafiore]

 yes the idea is not to have the huber jar, it's all about this, is the main
feature :)
some guys in the felix maling list suggested me that's actually possible and
supported, it's called WAB, that's a war without /lib (a partially reverse
recursive achronim for A Better War)

http://old.nabble.com/A-better-life%3A-quick-webapp-deploy-to31334158.html

I'll go for that tomorrow.

On Wed, Apr 6, 2011 at 4:27 PM, Martin Grigorov wrote:

> I'm not an OSGi user but here is what I'll do.
>
> 1) create a new Maven project with packaging type 'pom'
> 2) combine all wicket jars in one (uber-jar)
>  there are several approaches here:
> 1) maven-shade-plugin
> 2) the way we did it in RC1 with maven-dependency-plugin: see
>
> http://repo2.maven.org/maven2/org/apache/wicket/wicket/1.5-RC1/wicket-1.5-RC1.pom
>
> Here check that works with simple Wicket app (e.g. the quickstart).
>
> Creating one big jar with all dependendies is against OSGi idea. The goal
> is
> to be able to replace dependencies without restarting, e.g. upgrade the
> service layer without undeploying the presentation.
> But if you still want to do it:  start adding more dependencies to be
> packed
> in the uber jar (spring, hibernate)
>
> About WicketFilter:
> - you can use embedded Jetty or Guice Filter
> and org.apache.wicket.protocol.http.WicketFilter.FILTER_MAPPING_PARAM (I
> explained this earlier today in another thread)
> - OSGi 4.1+ has the notion of enterprise OSGi and you can use plain OSGi
> gymnastics to do that (I have no experience at all in this)
>





--
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com 
>

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[Martin Grigorov]

I'm not an OSGi user but here is what I'll do.

1) create a new Maven project with packaging type 'pom'
2) combine all wicket jars in one (uber-jar)
 there are several approaches here:
1) maven-shade-plugin
2) the way we did it in RC1 with maven-dependency-plugin: see
http://repo2.maven.org/maven2/org/apache/wicket/wicket/1.5-RC1/wicket-1.5-RC1.pom

Here check that works with simple Wicket app (e.g. the quickstart).

Creating one big jar with all dependendies is against OSGi idea. The goal is
to be able to replace dependencies without restarting, e.g. upgrade the
service layer without undeploying the presentation.
But if you still want to do it:  start adding more dependencies to be packed
in the uber jar (spring, hibernate)

About WicketFilter:
- you can use embedded Jetty or Guice Filter
and org.apache.wicket.protocol.http.WicketFilter.FILTER_MAPPING_PARAM (I
explained this earlier today in another thread)
- OSGi 4.1+ has the notion of enterprise OSGi and you can use plain OSGi
gymnastics to do that (I have no experience at all in this)

On Wed, Apr 6, 2011 at 3:15 PM, Daniele Dellafiore
wrote:

> mmm, can't really understand.
>
> Anyway, I wanted to add that the point here is to deploy a jar on karaf,
> not
> a war.
> To be honest, the real advantage is to deploy a small jar on karaf that is
> far better than a heavy war on a jee container.
> My idea is to have karaf with all the wicket, spring and other deps, and
> that's the easy part.
>
> Then I need a way to start the WicketFilter in the Karaf context. Normally
> the JEE container
> looks for the web.xml, that in my case bring to the
> SpringWebApplicationFactory and a single spring xml file and from there all
> the rest.
>
> But what if no one looks for the web.xml? Can I say to osgi that my jar is
> a
> webapp? Or can I start it by hand in an activator or from another file
> loaded by spring?
>
> On Wed, Apr 6, 2011 at 3:57 PM, Martin Grigorov  >wrote:
>
> > See RC1 o.a.w:wicket:pom.xml
> > You'll need to create your own project that will combine the all needed
> > .jars as we did in RC1.
> >
> > On Wed, Apr 6, 2011 at 2:51 PM, Daniele Dellafiore
> > wrote:
> >
> > > I'd really like to start my wicket app in a osgi (karaf) container.
> > > My app uses also wicket-spring. What is the best way to do that now,
> with
> > > wichet 1.5 rc3?
> > >
> > > Thanls.
> > >
> > > On Wed, Mar 16, 2011 at 2:25 PM, Michael O'Cleirigh <
> > > michael.ocleir...@rivulet.ca> wrote:
> > >
> > > > Hello,
> > > >
> > > > The way releases have been working is that I take the current HEAD
> and
> > > then
> > > > change the wicket.version to the current stable and the pom version
> to
> > > the
> > > > next release.
> > > >
> > > > If you can commit your changes onto the master branch (wicket
> > > 1.5-SNAPSHOT)
> > > > then I can create a new 1.5-rc2.1 point release to get the
> wicket-osgi
> > > > module out into maven central. Just let me know when it works (i.e.
> mvn
> > > > install works without error)
> > > >
> > > > You can either fork the repository on github and then do the change
> and
> > > > file a ticket with a pull request or send a message to the dev list
> > with
> > > > your github username for push/pull access to the wicketstuff
> repository
> > > > directly.
> > > >
> > > > Look at the 'Developer Information' section on the wiki here:
> > > > https://github.com/wicketstuff/core/wiki for more details.
> > > >
> > > > Regards,
> > > >
> > > > Mike
> > > >
> > > >
> > > >  ok, I can take the pom from rc1 and adopt it for rc2 - shouldn't be
> > > >> problem since you did the work already. If it works and I find some
> > time
> > > >> I'll try with github
> > > >>
> > > >> thanks and regards,
> > > >> eike
> > > >>
> > > >> On [Tue, 15.03.2011 22:10], Martin Grigorov wrote:
> > > >>
> > > >>> Well, wicketstuff is hosted at GitHub and any user can contribute.
> > > >>> If you have some time and willing to share your work with the
> > community
> > > >>> you
> > > >>> can do it yourself.
> > > >>> Otherwise just create a ticket in wicketstuff's issue tracking
> system
> > > and
> > > >>> someone of us will do it when we have some time.
> > > >>>
> > > >>> Thanks for testing the RCs ! ;-)
> > > >>>
> > > >>> On Tue, Mar 15, 2011 at 9:21 PM, Eike Kettner
> >  wrote:
> > > >>>
> > > >>>  Hi Martin,
> > > 
> > >  thanks for your response and no need to apologize! It's good to
> have
> > > rcX
> > >  candidate releases to play with so issues can be found.
> > > 
> > >  For me a wicket-osgi dependency would be great! And I really don't
> > > care
> > >  about where to download :) I don't think that providing it from
> > >  wicketstuff
> > >  would bother users...
> > > 
> > >  If you decide to not support osgi out-of-the-box, it's still no
> > > problem
> > >  to create an aggregate jar myself. I'd think most osgi users have
> to
> > > do
> > >  this (unfortunately) quite often to add other  "no-bundle-jars".
> But
> 

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[Daniele Dellafiore]

mmm, can't really understand.

Anyway, I wanted to add that the point here is to deploy a jar on karaf, not
a war.
To be honest, the real advantage is to deploy a small jar on karaf that is
far better than a heavy war on a jee container.
My idea is to have karaf with all the wicket, spring and other deps, and
that's the easy part.

Then I need a way to start the WicketFilter in the Karaf context. Normally
the JEE container
looks for the web.xml, that in my case bring to the
SpringWebApplicationFactory and a single spring xml file and from there all
the rest.

But what if no one looks for the web.xml? Can I say to osgi that my jar is a
webapp? Or can I start it by hand in an activator or from another file
loaded by spring?

On Wed, Apr 6, 2011 at 3:57 PM, Martin Grigorov wrote:

> See RC1 o.a.w:wicket:pom.xml
> You'll need to create your own project that will combine the all needed
> .jars as we did in RC1.
>
> On Wed, Apr 6, 2011 at 2:51 PM, Daniele Dellafiore
> wrote:
>
> > I'd really like to start my wicket app in a osgi (karaf) container.
> > My app uses also wicket-spring. What is the best way to do that now, with
> > wichet 1.5 rc3?
> >
> > Thanls.
> >
> > On Wed, Mar 16, 2011 at 2:25 PM, Michael O'Cleirigh <
> > michael.ocleir...@rivulet.ca> wrote:
> >
> > > Hello,
> > >
> > > The way releases have been working is that I take the current HEAD and
> > then
> > > change the wicket.version to the current stable and the pom version to
> > the
> > > next release.
> > >
> > > If you can commit your changes onto the master branch (wicket
> > 1.5-SNAPSHOT)
> > > then I can create a new 1.5-rc2.1 point release to get the wicket-osgi
> > > module out into maven central. Just let me know when it works (i.e. mvn
> > > install works without error)
> > >
> > > You can either fork the repository on github and then do the change and
> > > file a ticket with a pull request or send a message to the dev list
> with
> > > your github username for push/pull access to the wicketstuff repository
> > > directly.
> > >
> > > Look at the 'Developer Information' section on the wiki here:
> > > https://github.com/wicketstuff/core/wiki for more details.
> > >
> > > Regards,
> > >
> > > Mike
> > >
> > >
> > >  ok, I can take the pom from rc1 and adopt it for rc2 - shouldn't be
> > >> problem since you did the work already. If it works and I find some
> time
> > >> I'll try with github
> > >>
> > >> thanks and regards,
> > >> eike
> > >>
> > >> On [Tue, 15.03.2011 22:10], Martin Grigorov wrote:
> > >>
> > >>> Well, wicketstuff is hosted at GitHub and any user can contribute.
> > >>> If you have some time and willing to share your work with the
> community
> > >>> you
> > >>> can do it yourself.
> > >>> Otherwise just create a ticket in wicketstuff's issue tracking system
> > and
> > >>> someone of us will do it when we have some time.
> > >>>
> > >>> Thanks for testing the RCs ! ;-)
> > >>>
> > >>> On Tue, Mar 15, 2011 at 9:21 PM, Eike Kettner
>  wrote:
> > >>>
> > >>>  Hi Martin,
> > 
> >  thanks for your response and no need to apologize! It's good to have
> > rcX
> >  candidate releases to play with so issues can be found.
> > 
> >  For me a wicket-osgi dependency would be great! And I really don't
> > care
> >  about where to download :) I don't think that providing it from
> >  wicketstuff
> >  would bother users...
> > 
> >  If you decide to not support osgi out-of-the-box, it's still no
> > problem
> >  to create an aggregate jar myself. I'd think most osgi users have to
> > do
> >  this (unfortunately) quite often to add other  "no-bundle-jars". But
> >  with a distributed jar, it's of course a lot easier - I would
> > appreciate
> >  it (as probably other osgi users would).
> > 
> >  regards,
> >  Eike
> > 
> >  On [Tue, 15.03.2011 20:43], Martin Grigorov wrote:
> > 
> > > Hi Eike,
> > >
> > > Sorry that we broke OSGi support again.
> > > The problem was that many users wanted -sources and -javadoc for
> the
> > > aggregate .jar and it became a bit complex and confusing.
> > >
> > > I think we can add wicket-osgi project in wicketstuff/core
> repository
> > >
> >  that
> > 
> > > will do the same we did initially in WICKET-3088 and then you will
> > use
> > > org.wicketstuff:wicket-osgi dependency instead. We release
> > wicketstuff
> > >
> >  core
> > 
> > > projects few days after Wicket releases.
> > >
> > > Other opinions/suggestions ?
> > >
> > > martin-g
> > >
> > > On Tue, Mar 15, 2011 at 3:05 PM, Eike Kettner
> >  wrote:
> > >
> > >  Hi,
> > >>
> > >> I'm using wicket 1.5-RC1 in an OSGi container. There was an issue
> > when
> > >> upgrading related to package names
> > >> (https://issues.apache.org/jira/browse/WICKET-3088)
> > >>
> > >> Now I tried upgrading to 1.5-rc2 and found that there is no
> > aggregate
> > >>>

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[Martin Grigorov]

See RC1 o.a.w:wicket:pom.xml
You'll need to create your own project that will combine the all needed
.jars as we did in RC1.

On Wed, Apr 6, 2011 at 2:51 PM, Daniele Dellafiore
wrote:

> I'd really like to start my wicket app in a osgi (karaf) container.
> My app uses also wicket-spring. What is the best way to do that now, with
> wichet 1.5 rc3?
>
> Thanls.
>
> On Wed, Mar 16, 2011 at 2:25 PM, Michael O'Cleirigh <
> michael.ocleir...@rivulet.ca> wrote:
>
> > Hello,
> >
> > The way releases have been working is that I take the current HEAD and
> then
> > change the wicket.version to the current stable and the pom version to
> the
> > next release.
> >
> > If you can commit your changes onto the master branch (wicket
> 1.5-SNAPSHOT)
> > then I can create a new 1.5-rc2.1 point release to get the wicket-osgi
> > module out into maven central. Just let me know when it works (i.e. mvn
> > install works without error)
> >
> > You can either fork the repository on github and then do the change and
> > file a ticket with a pull request or send a message to the dev list with
> > your github username for push/pull access to the wicketstuff repository
> > directly.
> >
> > Look at the 'Developer Information' section on the wiki here:
> > https://github.com/wicketstuff/core/wiki for more details.
> >
> > Regards,
> >
> > Mike
> >
> >
> >  ok, I can take the pom from rc1 and adopt it for rc2 - shouldn't be
> >> problem since you did the work already. If it works and I find some time
> >> I'll try with github
> >>
> >> thanks and regards,
> >> eike
> >>
> >> On [Tue, 15.03.2011 22:10], Martin Grigorov wrote:
> >>
> >>> Well, wicketstuff is hosted at GitHub and any user can contribute.
> >>> If you have some time and willing to share your work with the community
> >>> you
> >>> can do it yourself.
> >>> Otherwise just create a ticket in wicketstuff's issue tracking system
> and
> >>> someone of us will do it when we have some time.
> >>>
> >>> Thanks for testing the RCs ! ;-)
> >>>
> >>> On Tue, Mar 15, 2011 at 9:21 PM, Eike Kettner  wrote:
> >>>
> >>>  Hi Martin,
> 
>  thanks for your response and no need to apologize! It's good to have
> rcX
>  candidate releases to play with so issues can be found.
> 
>  For me a wicket-osgi dependency would be great! And I really don't
> care
>  about where to download :) I don't think that providing it from
>  wicketstuff
>  would bother users...
> 
>  If you decide to not support osgi out-of-the-box, it's still no
> problem
>  to create an aggregate jar myself. I'd think most osgi users have to
> do
>  this (unfortunately) quite often to add other  "no-bundle-jars". But
>  with a distributed jar, it's of course a lot easier - I would
> appreciate
>  it (as probably other osgi users would).
> 
>  regards,
>  Eike
> 
>  On [Tue, 15.03.2011 20:43], Martin Grigorov wrote:
> 
> > Hi Eike,
> >
> > Sorry that we broke OSGi support again.
> > The problem was that many users wanted -sources and -javadoc for the
> > aggregate .jar and it became a bit complex and confusing.
> >
> > I think we can add wicket-osgi project in wicketstuff/core repository
> >
>  that
> 
> > will do the same we did initially in WICKET-3088 and then you will
> use
> > org.wicketstuff:wicket-osgi dependency instead. We release
> wicketstuff
> >
>  core
> 
> > projects few days after Wicket releases.
> >
> > Other opinions/suggestions ?
> >
> > martin-g
> >
> > On Tue, Mar 15, 2011 at 3:05 PM, Eike Kettner
>  wrote:
> >
> >  Hi,
> >>
> >> I'm using wicket 1.5-RC1 in an OSGi container. There was an issue
> when
> >> upgrading related to package names
> >> (https://issues.apache.org/jira/browse/WICKET-3088)
> >>
> >> Now I tried upgrading to 1.5-rc2 and found that there is no
> aggregate
> >> jar file anymore. I then read the discussion-thread "[discuss] How
> to
> >> resolve wicket aggregate classes / sources jar issues".
> >> (nabble:
> >>
> >>
> >>
> 
> http://apache-wicket.1842946.n4.nabble.com/discuss-How-to-resolve-wicket-aggregate-classes-sources-jar-issues-td3234420.html
>  )
> 
> > As it states, the aggregate jar has been removed from the wicket
> >> distribution. Now, this introduces the very same issues described in
> >> WICKET-3088 again.
> >>
> >> While I can just repackage wicket myself and create a aggregate jar
> to
> >> feed the osgi container, it is first more inconvenient :) and
> >> secondly,
> >> there is then no real reason to have the wicket-xxx jars export
> >> packages, as they won't work in an OSGi container one by one
> anyways.
> >> I
> >> cannot add all single jars to the osgi container, because of the
> >>
> > clashes
> 
> > in export-package.
> >>
> >> so in summary, there is another use cas

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[Daniele Dellafiore]

I'd really like to start my wicket app in a osgi (karaf) container.
My app uses also wicket-spring. What is the best way to do that now, with
wichet 1.5 rc3?

Thanls.

On Wed, Mar 16, 2011 at 2:25 PM, Michael O'Cleirigh <
michael.ocleir...@rivulet.ca> wrote:

> Hello,
>
> The way releases have been working is that I take the current HEAD and then
> change the wicket.version to the current stable and the pom version to the
> next release.
>
> If you can commit your changes onto the master branch (wicket 1.5-SNAPSHOT)
> then I can create a new 1.5-rc2.1 point release to get the wicket-osgi
> module out into maven central. Just let me know when it works (i.e. mvn
> install works without error)
>
> You can either fork the repository on github and then do the change and
> file a ticket with a pull request or send a message to the dev list with
> your github username for push/pull access to the wicketstuff repository
> directly.
>
> Look at the 'Developer Information' section on the wiki here:
> https://github.com/wicketstuff/core/wiki for more details.
>
> Regards,
>
> Mike
>
>
>  ok, I can take the pom from rc1 and adopt it for rc2 - shouldn't be
>> problem since you did the work already. If it works and I find some time
>> I'll try with github
>>
>> thanks and regards,
>> eike
>>
>> On [Tue, 15.03.2011 22:10], Martin Grigorov wrote:
>>
>>> Well, wicketstuff is hosted at GitHub and any user can contribute.
>>> If you have some time and willing to share your work with the community
>>> you
>>> can do it yourself.
>>> Otherwise just create a ticket in wicketstuff's issue tracking system and
>>> someone of us will do it when we have some time.
>>>
>>> Thanks for testing the RCs ! ;-)
>>>
>>> On Tue, Mar 15, 2011 at 9:21 PM, Eike Kettner  wrote:
>>>
>>>  Hi Martin,

 thanks for your response and no need to apologize! It's good to have rcX
 candidate releases to play with so issues can be found.

 For me a wicket-osgi dependency would be great! And I really don't care
 about where to download :) I don't think that providing it from
 wicketstuff
 would bother users...

 If you decide to not support osgi out-of-the-box, it's still no problem
 to create an aggregate jar myself. I'd think most osgi users have to do
 this (unfortunately) quite often to add other  "no-bundle-jars". But
 with a distributed jar, it's of course a lot easier - I would appreciate
 it (as probably other osgi users would).

 regards,
 Eike

 On [Tue, 15.03.2011 20:43], Martin Grigorov wrote:

> Hi Eike,
>
> Sorry that we broke OSGi support again.
> The problem was that many users wanted -sources and -javadoc for the
> aggregate .jar and it became a bit complex and confusing.
>
> I think we can add wicket-osgi project in wicketstuff/core repository
>
 that

> will do the same we did initially in WICKET-3088 and then you will use
> org.wicketstuff:wicket-osgi dependency instead. We release wicketstuff
>
 core

> projects few days after Wicket releases.
>
> Other opinions/suggestions ?
>
> martin-g
>
> On Tue, Mar 15, 2011 at 3:05 PM, Eike Kettner  wrote:
>
>  Hi,
>>
>> I'm using wicket 1.5-RC1 in an OSGi container. There was an issue when
>> upgrading related to package names
>> (https://issues.apache.org/jira/browse/WICKET-3088)
>>
>> Now I tried upgrading to 1.5-rc2 and found that there is no aggregate
>> jar file anymore. I then read the discussion-thread "[discuss] How to
>> resolve wicket aggregate classes / sources jar issues".
>> (nabble:
>>
>>
>>
 http://apache-wicket.1842946.n4.nabble.com/discuss-How-to-resolve-wicket-aggregate-classes-sources-jar-issues-td3234420.html
 )

> As it states, the aggregate jar has been removed from the wicket
>> distribution. Now, this introduces the very same issues described in
>> WICKET-3088 again.
>>
>> While I can just repackage wicket myself and create a aggregate jar to
>> feed the osgi container, it is first more inconvenient :) and
>> secondly,
>> there is then no real reason to have the wicket-xxx jars export
>> packages, as they won't work in an OSGi container one by one anyways.
>> I
>> cannot add all single jars to the osgi container, because of the
>>
> clashes

> in export-package.
>>
>> so in summary, there is another use case where the aggregate jar is
>> really helpful: when using wicket with osgi. But it only is, because
>> the single wicket jars export the same packages (for example,
>> wicket-request and wicket-core both export
>> org.apache.wicket.request.handler).
>>
>> Are there any thoughts of adding this aggregate jar to the
>> distribution
>> back again?
>>
>> kind regards,
>> eike
>>
>> -

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[Michael O'Cleirigh]

Hello,

The way releases have been working is that I take the current HEAD and 
then change the wicket.version to the current stable and the pom version 
to the next release.


If you can commit your changes onto the master branch (wicket 
1.5-SNAPSHOT) then I can create a new 1.5-rc2.1 point release to get the 
wicket-osgi module out into maven central. Just let me know when it 
works (i.e. mvn install works without error)


You can either fork the repository on github and then do the change and 
file a ticket with a pull request or send a message to the dev list with 
your github username for push/pull access to the wicketstuff repository 
directly.


Look at the 'Developer Information' section on the wiki here: 
https://github.com/wicketstuff/core/wiki for more details.


Regards,

Mike


ok, I can take the pom from rc1 and adopt it for rc2 - shouldn't be
problem since you did the work already. If it works and I find some time
I'll try with github

thanks and regards,
eike

On [Tue, 15.03.2011 22:10], Martin Grigorov wrote:

Well, wicketstuff is hosted at GitHub and any user can contribute.
If you have some time and willing to share your work with the community you
can do it yourself.
Otherwise just create a ticket in wicketstuff's issue tracking system and
someone of us will do it when we have some time.

Thanks for testing the RCs ! ;-)

On Tue, Mar 15, 2011 at 9:21 PM, Eike Kettner  wrote:


Hi Martin,

thanks for your response and no need to apologize! It's good to have rcX
candidate releases to play with so issues can be found.

For me a wicket-osgi dependency would be great! And I really don't care
about where to download :) I don't think that providing it from wicketstuff
would bother users...

If you decide to not support osgi out-of-the-box, it's still no problem
to create an aggregate jar myself. I'd think most osgi users have to do
this (unfortunately) quite often to add other  "no-bundle-jars". But
with a distributed jar, it's of course a lot easier - I would appreciate
it (as probably other osgi users would).

regards,
Eike

On [Tue, 15.03.2011 20:43], Martin Grigorov wrote:

Hi Eike,

Sorry that we broke OSGi support again.
The problem was that many users wanted -sources and -javadoc for the
aggregate .jar and it became a bit complex and confusing.

I think we can add wicket-osgi project in wicketstuff/core repository

that

will do the same we did initially in WICKET-3088 and then you will use
org.wicketstuff:wicket-osgi dependency instead. We release wicketstuff

core

projects few days after Wicket releases.

Other opinions/suggestions ?

martin-g

On Tue, Mar 15, 2011 at 3:05 PM, Eike Kettner  wrote:


Hi,

I'm using wicket 1.5-RC1 in an OSGi container. There was an issue when
upgrading related to package names
(https://issues.apache.org/jira/browse/WICKET-3088)

Now I tried upgrading to 1.5-rc2 and found that there is no aggregate
jar file anymore. I then read the discussion-thread "[discuss] How to
resolve wicket aggregate classes / sources jar issues".
(nabble:



http://apache-wicket.1842946.n4.nabble.com/discuss-How-to-resolve-wicket-aggregate-classes-sources-jar-issues-td3234420.html
)

As it states, the aggregate jar has been removed from the wicket
distribution. Now, this introduces the very same issues described in
WICKET-3088 again.

While I can just repackage wicket myself and create a aggregate jar to
feed the osgi container, it is first more inconvenient :) and secondly,
there is then no real reason to have the wicket-xxx jars export
packages, as they won't work in an OSGi container one by one anyways. I
cannot add all single jars to the osgi container, because of the

clashes

in export-package.

so in summary, there is another use case where the aggregate jar is
really helpful: when using wicket with osgi. But it only is, because
the single wicket jars export the same packages (for example,
wicket-request and wicket-core both export
org.apache.wicket.request.handler).

Are there any thoughts of adding this aggregate jar to the distribution
back again?

kind regards,
eike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

--
email: e...@eknet.org   https://www.eknet.org  pgp: 481161A0

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org




--
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[news]

ok, I can take the pom from rc1 and adopt it for rc2 - shouldn't be
problem since you did the work already. If it works and I find some time
I'll try with github

thanks and regards,
eike

On [Tue, 15.03.2011 22:10], Martin Grigorov wrote:
> Well, wicketstuff is hosted at GitHub and any user can contribute.
> If you have some time and willing to share your work with the community you
> can do it yourself.
> Otherwise just create a ticket in wicketstuff's issue tracking system and
> someone of us will do it when we have some time.
> 
> Thanks for testing the RCs ! ;-)
> 
> On Tue, Mar 15, 2011 at 9:21 PM, Eike Kettner  wrote:
> 
> > Hi Martin,
> >
> > thanks for your response and no need to apologize! It's good to have rcX
> > candidate releases to play with so issues can be found.
> >
> > For me a wicket-osgi dependency would be great! And I really don't care
> > about where to download :) I don't think that providing it from wicketstuff
> > would bother users...
> >
> > If you decide to not support osgi out-of-the-box, it's still no problem
> > to create an aggregate jar myself. I'd think most osgi users have to do
> > this (unfortunately) quite often to add other  "no-bundle-jars". But
> > with a distributed jar, it's of course a lot easier - I would appreciate
> > it (as probably other osgi users would).
> >
> > regards,
> > Eike
> >
> > On [Tue, 15.03.2011 20:43], Martin Grigorov wrote:
> > > Hi Eike,
> > >
> > > Sorry that we broke OSGi support again.
> > > The problem was that many users wanted -sources and -javadoc for the
> > > aggregate .jar and it became a bit complex and confusing.
> > >
> > > I think we can add wicket-osgi project in wicketstuff/core repository
> > that
> > > will do the same we did initially in WICKET-3088 and then you will use
> > > org.wicketstuff:wicket-osgi dependency instead. We release wicketstuff
> > core
> > > projects few days after Wicket releases.
> > >
> > > Other opinions/suggestions ?
> > >
> > > martin-g
> > >
> > > On Tue, Mar 15, 2011 at 3:05 PM, Eike Kettner  wrote:
> > >
> > > > Hi,
> > > >
> > > > I'm using wicket 1.5-RC1 in an OSGi container. There was an issue when
> > > > upgrading related to package names
> > > > (https://issues.apache.org/jira/browse/WICKET-3088)
> > > >
> > > > Now I tried upgrading to 1.5-rc2 and found that there is no aggregate
> > > > jar file anymore. I then read the discussion-thread "[discuss] How to
> > > > resolve wicket aggregate classes / sources jar issues".
> > > > (nabble:
> > > >
> > > >
> > http://apache-wicket.1842946.n4.nabble.com/discuss-How-to-resolve-wicket-aggregate-classes-sources-jar-issues-td3234420.html
> > )
> > > > As it states, the aggregate jar has been removed from the wicket
> > > > distribution. Now, this introduces the very same issues described in
> > > > WICKET-3088 again.
> > > >
> > > > While I can just repackage wicket myself and create a aggregate jar to
> > > > feed the osgi container, it is first more inconvenient :) and secondly,
> > > > there is then no real reason to have the wicket-xxx jars export
> > > > packages, as they won't work in an OSGi container one by one anyways. I
> > > > cannot add all single jars to the osgi container, because of the
> > clashes
> > > > in export-package.
> > > >
> > > > so in summary, there is another use case where the aggregate jar is
> > > > really helpful: when using wicket with osgi. But it only is, because
> > > > the single wicket jars export the same packages (for example,
> > > > wicket-request and wicket-core both export
> > > > org.apache.wicket.request.handler).
> > > >
> > > > Are there any thoughts of adding this aggregate jar to the distribution
> > > > back again?
> > > >
> > > > kind regards,
> > > > eike
> > > >
> > > > -
> > > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > > > For additional commands, e-mail: users-h...@wicket.apache.org
> > > >
> > > >
> > >
> > >
> > > --
> > > Martin Grigorov
> > > jWeekend
> > > Training, Consulting, Development
> > > http://jWeekend.com 
> >
> > --
> > email: e...@eknet.org   https://www.eknet.org  pgp: 481161A0
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
> 
> 
> -- 
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com 

-- 
email: e...@eknet.org   https://www.eknet.org  pgp: 481161A0

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Fwd: wicket 1.5-rc2 and aggregate jar for osgi

[Martin Grigorov]

Well, wicketstuff is hosted at GitHub and any user can contribute.
If you have some time and willing to share your work with the community you
can do it yourself.
Otherwise just create a ticket in wicketstuff's issue tracking system and
someone of us will do it when we have some time.

Thanks for testing the RCs ! ;-)

On Tue, Mar 15, 2011 at 9:21 PM, Eike Kettner  wrote:

> Hi Martin,
>
> thanks for your response and no need to apologize! It's good to have rcX
> candidate releases to play with so issues can be found.
>
> For me a wicket-osgi dependency would be great! And I really don't care
> about where to download :) I don't think that providing it from wicketstuff
> would bother users...
>
> If you decide to not support osgi out-of-the-box, it's still no problem
> to create an aggregate jar myself. I'd think most osgi users have to do
> this (unfortunately) quite often to add other  "no-bundle-jars". But
> with a distributed jar, it's of course a lot easier - I would appreciate
> it (as probably other osgi users would).
>
> regards,
> Eike
>
> On [Tue, 15.03.2011 20:43], Martin Grigorov wrote:
> > Hi Eike,
> >
> > Sorry that we broke OSGi support again.
> > The problem was that many users wanted -sources and -javadoc for the
> > aggregate .jar and it became a bit complex and confusing.
> >
> > I think we can add wicket-osgi project in wicketstuff/core repository
> that
> > will do the same we did initially in WICKET-3088 and then you will use
> > org.wicketstuff:wicket-osgi dependency instead. We release wicketstuff
> core
> > projects few days after Wicket releases.
> >
> > Other opinions/suggestions ?
> >
> > martin-g
> >
> > On Tue, Mar 15, 2011 at 3:05 PM, Eike Kettner  wrote:
> >
> > > Hi,
> > >
> > > I'm using wicket 1.5-RC1 in an OSGi container. There was an issue when
> > > upgrading related to package names
> > > (https://issues.apache.org/jira/browse/WICKET-3088)
> > >
> > > Now I tried upgrading to 1.5-rc2 and found that there is no aggregate
> > > jar file anymore. I then read the discussion-thread "[discuss] How to
> > > resolve wicket aggregate classes / sources jar issues".
> > > (nabble:
> > >
> > >
> http://apache-wicket.1842946.n4.nabble.com/discuss-How-to-resolve-wicket-aggregate-classes-sources-jar-issues-td3234420.html
> )
> > > As it states, the aggregate jar has been removed from the wicket
> > > distribution. Now, this introduces the very same issues described in
> > > WICKET-3088 again.
> > >
> > > While I can just repackage wicket myself and create a aggregate jar to
> > > feed the osgi container, it is first more inconvenient :) and secondly,
> > > there is then no real reason to have the wicket-xxx jars export
> > > packages, as they won't work in an OSGi container one by one anyways. I
> > > cannot add all single jars to the osgi container, because of the
> clashes
> > > in export-package.
> > >
> > > so in summary, there is another use case where the aggregate jar is
> > > really helpful: when using wicket with osgi. But it only is, because
> > > the single wicket jars export the same packages (for example,
> > > wicket-request and wicket-core both export
> > > org.apache.wicket.request.handler).
> > >
> > > Are there any thoughts of adding this aggregate jar to the distribution
> > > back again?
> > >
> > > kind regards,
> > > eike
> > >
> > > -
> > > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > > For additional commands, e-mail: users-h...@wicket.apache.org
> > >
> > >
> >
> >
> > --
> > Martin Grigorov
> > jWeekend
> > Training, Consulting, Development
> > http://jWeekend.com 
>
> --
> email: e...@eknet.org   https://www.eknet.org  pgp: 481161A0
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com 

Re: wicket 1.5-rc2 and aggregate jar for osgi

[Eike Kettner]

Hi Martin,

thanks for your response and no need to apologize! It's good to have rcX
candidate releases to play with so issues can be found.

For me a wicket-osgi dependency would be great! And I really don't care
about where to download :) I don't think that providing it from wicketstuff
would bother users...

If you decide to not support osgi out-of-the-box, it's still no problem
to create an aggregate jar myself. I'd think most osgi users have to do
this (unfortunately) quite often to add other  "no-bundle-jars". But
with a distributed jar, it's of course a lot easier - I would appreciate
it (as probably other osgi users would).

regards,
Eike

On [Tue, 15.03.2011 20:43], Martin Grigorov wrote:
> Hi Eike,
> 
> Sorry that we broke OSGi support again.
> The problem was that many users wanted -sources and -javadoc for the
> aggregate .jar and it became a bit complex and confusing.
> 
> I think we can add wicket-osgi project in wicketstuff/core repository that
> will do the same we did initially in WICKET-3088 and then you will use
> org.wicketstuff:wicket-osgi dependency instead. We release wicketstuff core
> projects few days after Wicket releases.
> 
> Other opinions/suggestions ?
> 
> martin-g
> 
> On Tue, Mar 15, 2011 at 3:05 PM, Eike Kettner  wrote:
> 
> > Hi,
> >
> > I'm using wicket 1.5-RC1 in an OSGi container. There was an issue when
> > upgrading related to package names
> > (https://issues.apache.org/jira/browse/WICKET-3088)
> >
> > Now I tried upgrading to 1.5-rc2 and found that there is no aggregate
> > jar file anymore. I then read the discussion-thread "[discuss] How to
> > resolve wicket aggregate classes / sources jar issues".
> > (nabble:
> >
> > http://apache-wicket.1842946.n4.nabble.com/discuss-How-to-resolve-wicket-aggregate-classes-sources-jar-issues-td3234420.html)
> > As it states, the aggregate jar has been removed from the wicket
> > distribution. Now, this introduces the very same issues described in
> > WICKET-3088 again.
> >
> > While I can just repackage wicket myself and create a aggregate jar to
> > feed the osgi container, it is first more inconvenient :) and secondly,
> > there is then no real reason to have the wicket-xxx jars export
> > packages, as they won't work in an OSGi container one by one anyways. I
> > cannot add all single jars to the osgi container, because of the clashes
> > in export-package.
> >
> > so in summary, there is another use case where the aggregate jar is
> > really helpful: when using wicket with osgi. But it only is, because
> > the single wicket jars export the same packages (for example,
> > wicket-request and wicket-core both export
> > org.apache.wicket.request.handler).
> >
> > Are there any thoughts of adding this aggregate jar to the distribution
> > back again?
> >
> > kind regards,
> > eike
> >
> > -
> > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> > For additional commands, e-mail: users-h...@wicket.apache.org
> >
> >
> 
> 
> -- 
> Martin Grigorov
> jWeekend
> Training, Consulting, Development
> http://jWeekend.com 

-- 
email: e...@eknet.org   https://www.eknet.org  pgp: 481161A0

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org

Re: wicket 1.5-rc2 and aggregate jar for osgi

[Martin Grigorov]

Hi Eike,

Sorry that we broke OSGi support again.
The problem was that many users wanted -sources and -javadoc for the
aggregate .jar and it became a bit complex and confusing.

I think we can add wicket-osgi project in wicketstuff/core repository that
will do the same we did initially in WICKET-3088 and then you will use
org.wicketstuff:wicket-osgi dependency instead. We release wicketstuff core
projects few days after Wicket releases.

Other opinions/suggestions ?

martin-g

On Tue, Mar 15, 2011 at 3:05 PM, Eike Kettner  wrote:

> Hi,
>
> I'm using wicket 1.5-RC1 in an OSGi container. There was an issue when
> upgrading related to package names
> (https://issues.apache.org/jira/browse/WICKET-3088)
>
> Now I tried upgrading to 1.5-rc2 and found that there is no aggregate
> jar file anymore. I then read the discussion-thread "[discuss] How to
> resolve wicket aggregate classes / sources jar issues".
> (nabble:
>
> http://apache-wicket.1842946.n4.nabble.com/discuss-How-to-resolve-wicket-aggregate-classes-sources-jar-issues-td3234420.html)
> As it states, the aggregate jar has been removed from the wicket
> distribution. Now, this introduces the very same issues described in
> WICKET-3088 again.
>
> While I can just repackage wicket myself and create a aggregate jar to
> feed the osgi container, it is first more inconvenient :) and secondly,
> there is then no real reason to have the wicket-xxx jars export
> packages, as they won't work in an OSGi container one by one anyways. I
> cannot add all single jars to the osgi container, because of the clashes
> in export-package.
>
> so in summary, there is another use case where the aggregate jar is
> really helpful: when using wicket with osgi. But it only is, because
> the single wicket jars export the same packages (for example,
> wicket-request and wicket-core both export
> org.apache.wicket.request.handler).
>
> Are there any thoughts of adding this aggregate jar to the distribution
> back again?
>
> kind regards,
> eike
>
> -
> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
> For additional commands, e-mail: users-h...@wicket.apache.org
>
>


-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com 

wicket 1.5-rc2 and aggregate jar for osgi

[Eike Kettner]

Hi,

I'm using wicket 1.5-RC1 in an OSGi container. There was an issue when
upgrading related to package names
(https://issues.apache.org/jira/browse/WICKET-3088)

Now I tried upgrading to 1.5-rc2 and found that there is no aggregate
jar file anymore. I then read the discussion-thread "[discuss] How to
resolve wicket aggregate classes / sources jar issues". 
(nabble:
http://apache-wicket.1842946.n4.nabble.com/discuss-How-to-resolve-wicket-aggregate-classes-sources-jar-issues-td3234420.html
 )
As it states, the aggregate jar has been removed from the wicket
distribution. Now, this introduces the very same issues described in
WICKET-3088 again.

While I can just repackage wicket myself and create a aggregate jar to
feed the osgi container, it is first more inconvenient :) and secondly,
there is then no real reason to have the wicket-xxx jars export
packages, as they won't work in an OSGi container one by one anyways. I
cannot add all single jars to the osgi container, because of the clashes
in export-package.

so in summary, there is another use case where the aggregate jar is
really helpful: when using wicket with osgi. But it only is, because
the single wicket jars export the same packages (for example,
wicket-request and wicket-core both export
org.apache.wicket.request.handler).

Are there any thoughts of adding this aggregate jar to the distribution
back again?

kind regards,
eike

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org