Perhaps we should just concentrate the documentation in wiki.
In regards to upgrade,
I noticed that a clean up is required in service/osgi.bundle.
Export-Package: \
org.ops4j.pax.wicket.api;version="${pom.version}", \
org.ops4j.pax.wicket.util.*;version="${pom.version}", \
org.apache.wicket.*;version=1.4.10 # This should be 1.4.15
And we need to check the src/main/resources/wicket.properties
IIRC, I had to override the Initializer to combine all wicket initializer
into a single class.
Regards,
Edward Yakop
On Mon, Jan 10, 2011 at 11:21, Andreas Pieber <[email protected]> wrote:
> Hey,
>
> At the moment I'm at upgrading all versions of pax-wicket, cleaning the
> project
> up, getting all my use cases to work, integrate pax-wicket better with
> karaf and
> get the project to m2central.
>
> One question regarding to documentation: Do we really want to split the
> documentation
> over multible site goals and the wiki? IMHO we should either create a docs
> project
> containing all documentation (even in site format/docbkx) OR move all
> documentation
> to the wiki. What is the opinon of the long-time-pax-wicket-commiters to
> this point?
> Any other ideas from the community regarding this issue. That's one point I
> don't want
> to decide on my own...
>
> kind regards,
> andreas
>
>
> _______________________________________________
> general mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/general
>
>
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
