Preparing Karaf 4.2.1 and some ideas

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Preparing Karaf 4.2.1 and some ideas

jbonofre
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
their own Karaf distro. I will add new examples around that (there is
already one), and I think we can improve the karaf-maven-plugin to
simplify the way of creating distribution, and give the right example
(the generate MOJO is more a source of problem and we should encourage
users to write their features XML IMHO).

On the other hand, I started a branch where I refactored the README and
other documentation file to use the md format. The advantages of md
(compare to raw text or ascii doc) is that:
1. It can be rendered directly on github
2. The doxia maven plugin supports it by default (no need to use
asciidoc specific plugin)
3. It's a well known format

We are moving forward on this and other Jira (starting the triage right
now) and hopefully, Karaf 4.2.1 will be submitted to vote soon-"ish"
(middle of this week).

Regards
JB
--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Preparing Karaf 4.2.1 and some ideas

Grzegorz Grzybek
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 distributions.

best regards
Grzegorz Grzybek

2018-06-17 17:17 GMT+02:00 Jean-Baptiste Onofré <[hidden email]>:

> 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
> their own Karaf distro. I will add new examples around that (there is
> already one), and I think we can improve the karaf-maven-plugin to
> simplify the way of creating distribution, and give the right example
> (the generate MOJO is more a source of problem and we should encourage
> users to write their features XML IMHO).
>
> On the other hand, I started a branch where I refactored the README and
> other documentation file to use the md format. The advantages of md
> (compare to raw text or ascii doc) is that:
> 1. It can be rendered directly on github
> 2. The doxia maven plugin supports it by default (no need to use
> asciidoc specific plugin)
> 3. It's a well known format
>
> We are moving forward on this and other Jira (starting the triage right
> now) and hopefully, Karaf 4.2.1 will be submitted to vote soon-"ish"
> (middle of this week).
>
> Regards
> JB
> --
> Jean-Baptiste Onofré
> [hidden email]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
Reply | Threaded
Open this post in threaded view
|

Re: Preparing Karaf 4.2.1 and some ideas

jbonofre
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 promote the by-hand features
2. Improve the assembly mojo to use <configuration/>  in a easier way

I will come with a concrete proposal around that.

Regards
JB

On 17/06/2018 17:45, Grzegorz Grzybek wrote:

> 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 distributions.
>
> best regards
> Grzegorz Grzybek
>
> 2018-06-17 17:17 GMT+02:00 Jean-Baptiste Onofré <[hidden email]>:
>
>> 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
>> their own Karaf distro. I will add new examples around that (there is
>> already one), and I think we can improve the karaf-maven-plugin to
>> simplify the way of creating distribution, and give the right example
>> (the generate MOJO is more a source of problem and we should encourage
>> users to write their features XML IMHO).
>>
>> On the other hand, I started a branch where I refactored the README and
>> other documentation file to use the md format. The advantages of md
>> (compare to raw text or ascii doc) is that:
>> 1. It can be rendered directly on github
>> 2. The doxia maven plugin supports it by default (no need to use
>> asciidoc specific plugin)
>> 3. It's a well known format
>>
>> We are moving forward on this and other Jira (starting the triage right
>> now) and hopefully, Karaf 4.2.1 will be submitted to vote soon-"ish"
>> (middle of this week).
>>
>> Regards
>> JB
>> --
>> Jean-Baptiste Onofré
>> [hidden email]
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Preparing Karaf 4.2.1 and some ideas

Andrea Cosentino
In reply to this post by jbonofre
+1, great work!

--
Andrea Cosentino 
----------------------------------
Apache Camel PMC Chair
Apache Karaf Committer
Apache Servicemix PMC Member
Email: [hidden email]
Twitter: @oscerd2
Github: oscerd






On Sunday, June 17, 2018, 5:17:23 PM GMT+2, Jean-Baptiste Onofré <[hidden email]> wrote:





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
their own Karaf distro. I will add new examples around that (there is
already one), and I think we can improve the karaf-maven-plugin to
simplify the way of creating distribution, and give the right example
(the generate MOJO is more a source of problem and we should encourage
users to write their features XML IMHO).

On the other hand, I started a branch where I refactored the README and
other documentation file to use the md format. The advantages of md
(compare to raw text or ascii doc) is that:
1. It can be rendered directly on github
2. The doxia maven plugin supports it by default (no need to use
asciidoc specific plugin)
3. It's a well known format

We are moving forward on this and other Jira (starting the triage right
now) and hopefully, Karaf 4.2.1 will be submitted to vote soon-"ish"
(middle of this week).

Regards
JB
--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com
Reply | Threaded
Open this post in threaded view
|

Re: Preparing Karaf 4.2.1 and some ideas

fpapon
In reply to this post by jbonofre
+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
[hidden email]
Open3m - https://www.open3m.io

Le 17/06/2018 à 19:17, Jean-Baptiste Onofré a écrit :

> 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
> their own Karaf distro. I will add new examples around that (there is
> already one), and I think we can improve the karaf-maven-plugin to
> simplify the way of creating distribution, and give the right example
> (the generate MOJO is more a source of problem and we should encourage
> users to write their features XML IMHO).
>
> On the other hand, I started a branch where I refactored the README and
> other documentation file to use the md format. The advantages of md
> (compare to raw text or ascii doc) is that:
> 1. It can be rendered directly on github
> 2. The doxia maven plugin supports it by default (no need to use
> asciidoc specific plugin)
> 3. It's a well known format
>
> We are moving forward on this and other Jira (starting the triage right
> now) and hopefully, Karaf 4.2.1 will be submitted to vote soon-"ish"
> (middle of this week).
>
> Regards
> JB

François Papon
fpapon@apache.org
Yupiik - https://www.yupiik.com
Reply | Threaded
Open this post in threaded view
|

Re: Preparing Karaf 4.2.1 and some ideas

jbonofre
In reply to this post by jbonofre
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, Jean-Baptiste Onofré wrote:

> 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
> their own Karaf distro. I will add new examples around that (there is
> already one), and I think we can improve the karaf-maven-plugin to
> simplify the way of creating distribution, and give the right example
> (the generate MOJO is more a source of problem and we should encourage
> users to write their features XML IMHO).
>
> On the other hand, I started a branch where I refactored the README and
> other documentation file to use the md format. The advantages of md
> (compare to raw text or ascii doc) is that:
> 1. It can be rendered directly on github
> 2. The doxia maven plugin supports it by default (no need to use
> asciidoc specific plugin)
> 3. It's a well known format
>
> We are moving forward on this and other Jira (starting the triage right
> now) and hopefully, Karaf 4.2.1 will be submitted to vote soon-"ish"
> (middle of this week).
>
> Regards
> JB
>

--
Jean-Baptiste Onofré
[hidden email]
http://blog.nanthrax.net
Talend - http://www.talend.com