Hi Guillaume,

I'm agree with you.

I think that we should provide one Karaf assembly and really think about profiles.

We have to append some content to the brainstorm wiki page.
I try to begin to document what I'm thinking about profiles.

Regards
JB

On 02/03/2011 11:45 PM, Guillaume Nodet wrote:
So where are we at with the assemblies ?
We currently have:
   trunk/assembly (the still in use assemblies)
   trunk/features/assembly/enteprise (contains a feature descriptor)
   trunk/features/assembly/standard (contains a feature descriptor)
   trunk/features/assembly/framework (supposed to be the minimal assembly?)
   trunk/assemblies/apache-karaf (supposed to be the main distribution?)

In all cases, I'm not really happy about having assemblies in
trunk/features and I'd like them moved to trunk/assemblies if
possible.
Second, this is not really usable yet, so do we plan to finish that
for 2.2 or postpone for 3.0 ?
Last, I'm still worried of having to split our release cycle in two
because of the maven plugin, so I'm not sure how we should deal with
that.

THoughts?

On Tue, Feb 1, 2011 at 10:23, Andreas Pieber<[email protected]>  wrote:
Ok, from my point of view we can move everything but the following issues

254, 338, 334 (optionally), 424 (including 401).

kind regards,
andreas

On Mon, Jan 31, 2011 at 11:47:33AM -0330, Jamie G. wrote:
Hi All,

We're rapidly approaching being able to cut a release candidate for
Apache Karaf 2.2.0. At this time I'd like to encourage everyone to
quickly review open issues in Jira for the 2.2.0 branch, and to test
their local snapshot builds and report any issues you encounter
(especially platform specific issues - i.e. IBM Java or WIndows).

Apache Karaf 2.2.0 issue tracker (see issues tab for complete list of
open 2.2.0 issues):
https://issues.apache.org/jira/browse/KARAF/fixforversion/12315328

Cheers,
Jamie




Reply via email to