Hi guys,
just to let you know that 4.2.1 preparation is on the way (SNAPSHOT
dependencies have been resolved, example and docker feature/image will
be in PR soon).
I plan to submit the release to vote soon (probably during the weekend
or beginning of next week).
Regards
JB
On 17/06/2018 17:17,
+1 for all !
We have to simplify and document the way to make custom distribution for
end user ;)
I also note many questions about JPA on the mailing list and we will add
other examples by provider (Apache OpenJPA, EclipseLink, Hibernate, ...)
regards,
François Papon
fpa...@apache.org
Open3m -
+1, great work!
--
Andrea Cosentino
--
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: ancosen1...@yahoo.com
Twitter: @oscerd2
Github: oscerd
On Sunday, June 17, 2018, 5:17:23 PM GMT+2, Jean-Baptiste Onofré
wrote:
Hi
I think that's fair for some use cases, but generally speaking, we
should improve the global usage.
scope (compile, runtime, provided) is not well used, kar requirement is
overhead, the generate mojo is not accurate, etc.
I would propose the following:
1. Deprecate the generate features mojo to p
Hello
At some point I'm going to "fix"
https://issues.apache.org/jira/browse/KARAF-5540 which is a documentation
issue of new "overrides and blacklisting" mechanism.
In fact this mechanism was created from "custom distro" point of view and
some fixes/changes make things easier with custom distrib
Hi guys,
As I started to prepare Karaf 4.2.1, I rebased and cleaned up the
examples. The corresponding PR is there:
https://github.com/apache/karaf/pull/484
As already mention on the mailing list, I gonna add new examples asked
by users. It seems also that lot of users has difficulties to create