[GitHub] karaf pull request #61: Add support for filtered resources to karaf-maven-pl...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/karaf/pull/61


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] karaf pull request #57: KARAF-3596: Added xerces.stax packages to org.osgi.f...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/karaf/pull/57


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] karaf pull request #58: KARAF-3596: Added xerces.stax packages to org.osgi.f...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/karaf/pull/58


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] karaf pull request #55: Cloudyle 3.0.x

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/karaf/pull/55


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] karaf pull request #51: [KARAF-3344] Fix karaf-maven-plugin non-standard URL...

[asfgit]

Github user asfgit closed the pull request at:

https://github.com/apache/karaf/pull/51


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] karaf pull request #270: KARAF-4853, Option to prevent execution as root

[lkiesow]

GitHub user lkiesow opened a pull request:

https://github.com/apache/karaf/pull/270

KARAF-4853, Option to prevent execution as root

Usually, it is not a good idea to run Karaf as root. In some cases, it
might even be harmful. This patch introduces the option `KARAF_NOROOT`
which, if set, will prevent Karaf from being executed as root.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lkiesow/karaf karaf-4853-noroot-option

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/karaf/pull/270.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #270


commit 905f5089d0386e1fadb36f678a58cbc9fce2ec21
Author: Lars Kiesow 
Date:   2016-11-26T00:06:39Z

KARAF-4853, Option to prevent execution as root

Usually, it is not a good idea to run Karaf as root. In some cases, it
might even be harmful. This patch introduces the option `KARAF_NOROOT`
which, if set, will prevent Karaf from being executed as root.

Signed-off-by: Lars Kiesow 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] karaf pull request #269: KARAF-4852, Minor issues with start script

[lkiesow]

GitHub user lkiesow opened a pull request:

https://github.com/apache/karaf/pull/269

KARAF-4852, Minor issues with start script

If a cd command fails in the start script the following behavior is
undefined and could potentially cause problems.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/lkiesow/karaf karaf-4852-start-script

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/karaf/pull/269.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #269


commit bcb9167a95cf843ed0077271d7633826fd02b9b1
Author: Lars Kiesow 
Date:   2016-11-25T22:01:32Z

KARAF-4852, Minor issues with start script

If a cd command fails in the start script the following behavior is
undefined and could potentially cause problems.

Signed-off-by: Lars Kiesow 




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Trim down the number of config files in etc/ in the distributions

[Milen Dyankov]

>
> I was able to modify above files, because I saw them being present.


That was exactly my point regarding documentation. I'd imagine a lot of
people would not be even aware something is configurable and can waste time
digging or what's worse, reinvent the wheel. For someone who is been
playing with Karaf (or OSGi in general) for a while - configuration is
fairly familiar and straightforward concept. But for people just starting
their journey it may be hard to figure out.

Best,
Milen

On Fri, Nov 25, 2016 at 12:50 PM, Fabian Lange 
wrote:

> Hi Guillaume,
>
> We are building a distribution, and we modify these files:
>
> -rw-r--r--   1 fabian  staff 0 Sep  6 16:13 blacklisted.properties
> -rw-r--r--   1 fabian  staff   977 Dec 11  2015 branding.properties
> -rw-r--r--   1 fabian  staff  2414 Oct 28 17:35 custom.properties
> -rw-r--r--   1 fabian  staff  2867 Nov 11 14:10
> org.apache.karaf.features.cfg
> -rw-r--r--@  1 fabian  staff  1935 Dec 21  2015 org.apache.karaf.log.cfg
> -rw-r--r--   1 fabian  staff  3317 Dec 11  2015 org.apache.karaf.shell.cfg
> -rw-r--r--   1 fabian  staff  2818 Nov 21 08:08 org.ops4j.pax.logging.cfg
> -rw-r--r--@  1 fabian  staff  3889 Oct  6 09:07 org.ops4j.pax.url.mvn.cfg
> -rw-r--r--   1 fabian  staff 0 Sep  6 16:13 overrides.properties
> -rw-r--r--@  1 fabian  staff  5430 Oct  5 10:02 system.properties
> -rw-r--r--   1 fabian  staff  1701 Apr  2  2016 users.properties
>
> the 0 byte properties are just to avoid the file not found exception
>
> And we have the following excludes
>
>   
> bin/**
> deploy/README
> system/README
> lib/**/README
> etc/org.apache.karaf.jaas.cfg
> etc/org.apache.karaf.management.cfg
> etc/org.apache.karaf.features.repos.cfg
> etc/org.apache.karaf.command.acl*
> etc/jmx.acl*
>   
>
>
> I am very much in favor of removing the files. The only issue i see is that
> I was able to modify above files, because I saw them being present.
>
> Fabian
> --
> Fabian Lange | Performance Expert
> mobil: +49 (0) 160.3673393
>
> codecentric AG | Merscheider Straße 1 | 42699 Solingen | Deutschland
>
> Sitz der Gesellschaft: Solingen | HRB 25917| Amtsgericht Wuppertal
> Vorstand: Michael Hochgürtel . Mirko Novakovic . Rainer Vehns
> Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Klaus Jäger . Jürgen Schütz
>
> On Fri, Nov 25, 2016 at 8:19 AM, Guillaume Nodet 
> wrote:
>
> > I'd like to trim down a bit the number of files in the etc/ directory.
> > The distribution contains a bunch of config files for the ACLs, but I'm
> not
> > sure people usually modify those.  I think this may be the same for
> various
> > configuration.
> > What I'm proposing is the following:
> >   * make sure all those configurations are moved into their respective
> > feature
> >   * remove them from the assemblies/base maven module which is embedded
> by
> > the framework and static kars
> >   * add a flag on the AssemblyMojo so that we can choose using glob
> > patterns which config pids should be extracted as files at build time
> >   * the other ones are extracted automatically by the FeaturesService
> > anyway during boot features installation
> >
> > The idea would be that distributions only contains configurations that
> are
> > actually used.
> >
> > Also, I'm going to removing some additional files from the static
> framework
> > (bin/contrib/, bin/instance(.sh|.bat), deploy/).
> >
> > Thoughts ?
> > Guillaume
> >
> >
> > --
> > 
> > Guillaume Nodet
> > 
> > Red Hat, Open Source Integration
> >
> > Email: gno...@redhat.com
> > Web: http://fusesource.com
> > Blog: http://gnodet.blogspot.com/
> >
>



-- 
http://about.me/milen

Re: [DISCUSS] Trim down the number of config files in etc/ in the distributions

[Fabian Lange]

Hi Guillaume,

We are building a distribution, and we modify these files:

-rw-r--r--   1 fabian  staff 0 Sep  6 16:13 blacklisted.properties
-rw-r--r--   1 fabian  staff   977 Dec 11  2015 branding.properties
-rw-r--r--   1 fabian  staff  2414 Oct 28 17:35 custom.properties
-rw-r--r--   1 fabian  staff  2867 Nov 11 14:10
org.apache.karaf.features.cfg
-rw-r--r--@  1 fabian  staff  1935 Dec 21  2015 org.apache.karaf.log.cfg
-rw-r--r--   1 fabian  staff  3317 Dec 11  2015 org.apache.karaf.shell.cfg
-rw-r--r--   1 fabian  staff  2818 Nov 21 08:08 org.ops4j.pax.logging.cfg
-rw-r--r--@  1 fabian  staff  3889 Oct  6 09:07 org.ops4j.pax.url.mvn.cfg
-rw-r--r--   1 fabian  staff 0 Sep  6 16:13 overrides.properties
-rw-r--r--@  1 fabian  staff  5430 Oct  5 10:02 system.properties
-rw-r--r--   1 fabian  staff  1701 Apr  2  2016 users.properties

the 0 byte properties are just to avoid the file not found exception

And we have the following excludes

  
bin/**
deploy/README
system/README
lib/**/README
etc/org.apache.karaf.jaas.cfg
etc/org.apache.karaf.management.cfg
etc/org.apache.karaf.features.repos.cfg
etc/org.apache.karaf.command.acl*
etc/jmx.acl*
  


I am very much in favor of removing the files. The only issue i see is that
I was able to modify above files, because I saw them being present.

Fabian
--
Fabian Lange | Performance Expert
mobil: +49 (0) 160.3673393

codecentric AG | Merscheider Straße 1 | 42699 Solingen | Deutschland

Sitz der Gesellschaft: Solingen | HRB 25917| Amtsgericht Wuppertal
Vorstand: Michael Hochgürtel . Mirko Novakovic . Rainer Vehns
Aufsichtsrat: Patric Fedlmeier (Vorsitzender) . Klaus Jäger . Jürgen Schütz

On Fri, Nov 25, 2016 at 8:19 AM, Guillaume Nodet  wrote:

> I'd like to trim down a bit the number of files in the etc/ directory.
> The distribution contains a bunch of config files for the ACLs, but I'm not
> sure people usually modify those.  I think this may be the same for various
> configuration.
> What I'm proposing is the following:
>   * make sure all those configurations are moved into their respective
> feature
>   * remove them from the assemblies/base maven module which is embedded by
> the framework and static kars
>   * add a flag on the AssemblyMojo so that we can choose using glob
> patterns which config pids should be extracted as files at build time
>   * the other ones are extracted automatically by the FeaturesService
> anyway during boot features installation
>
> The idea would be that distributions only contains configurations that are
> actually used.
>
> Also, I'm going to removing some additional files from the static framework
> (bin/contrib/, bin/instance(.sh|.bat), deploy/).
>
> Thoughts ?
> Guillaume
>
>
> --
> 
> Guillaume Nodet
> 
> Red Hat, Open Source Integration
>
> Email: gno...@redhat.com
> Web: http://fusesource.com
> Blog: http://gnodet.blogspot.com/
>

Re: [DISCUSS] Trim down the number of config files in etc/ in the distributions

[Guillaume Nodet]

I agree we should not remove any documentation on those configurations.
So the features inside the configuration will contain all the documentation
that exist currently in the config files.

When installing a feature using the feature service, the configuration are
always written to the etc/ dir, so I'm enhancing right now the features
service so that the comments stored in those inlined configurations can be
properly extracted.
See
https://github.com/apache/karaf/blob/master/assemblies/features/standard/src/main/feature/feature.xml#L96-L104
for example.

What this mean is that if I remove some configurations from the default
distribution and move them as inlined configurations, those files will be
re-created when the boot features are installed.  The assembly builder will
also automatically extract configurations from the startup phase.
As I indicated in my first email, I plan to enhance the AssemblyMojo so
that we can select configuration pids from the boot features to be
extracted at build time, so before the features are installed the first
time.

The end result, is that after the first boot, the etc folder should look
the same.  Before the first boot, we can have less files in the etc
folder.  My first idea was to make sure the jmx.acl.* and
org.apache.karaf.command.acl.* config would not be in the distribution by
default, and maybe a few others
(org.apache.karaf.features.repos.cfg, ...?).  I think the others should be
kept.


2016-11-25 10:26 GMT+01:00 Achim Nierbeck :

> +1 on slimming down the configs.
>
> regarding Milens comments.
> It's possible already and called config:edit pid.
> All those configurations are stored directly with config-admin service so
> there isn't a proprietary config in Karaf.
>
> I only have one comment about it.
> Would be great to have a little togle command to enable the write-to-file
> for a configuration via the config command.
> That would make it much easier.
>
> regards, Achim
>
>
>
> 2016-11-25 9:51 GMT+01:00 Milen Dyankov :
>
> > I like the idea of reducing the number of files in etc folder.
> > However I would vote against it until there is a good documentation of
> how
> > to configure everything that's in those removed files. That is what can
> be
> > configured, where, how it differs in clustered env, ...
> > Once that is place that is easy to find and use I'd love to get rid of
> > those.
> >
> > Side note: I don't know how configuration from features works but we need
> > to be careful with location bindings. We at Liferay used to have some
> > issues with bundles providing own default configuration which was not
> > possible to change later on because of location bindings. I'm not saying
> > this will be a problem with Karaf, but just to keep an eye on it while
> > changing things.
> >
> > Best,
> > Milen
> >
> > On Fri, Nov 25, 2016 at 8:19 AM, Guillaume Nodet 
> > wrote:
> >
> > > I'd like to trim down a bit the number of files in the etc/ directory.
> > > The distribution contains a bunch of config files for the ACLs, but I'm
> > not
> > > sure people usually modify those.  I think this may be the same for
> > various
> > > configuration.
> > > What I'm proposing is the following:
> > >   * make sure all those configurations are moved into their respective
> > > feature
> > >   * remove them from the assemblies/base maven module which is embedded
> > by
> > > the framework and static kars
> > >   * add a flag on the AssemblyMojo so that we can choose using glob
> > > patterns which config pids should be extracted as files at build time
> > >   * the other ones are extracted automatically by the FeaturesService
> > > anyway during boot features installation
> > >
> > > The idea would be that distributions only contains configurations that
> > are
> > > actually used.
> > >
> > > Also, I'm going to removing some additional files from the static
> > framework
> > > (bin/contrib/, bin/instance(.sh|.bat), deploy/).
> > >
> > > Thoughts ?
> > > Guillaume
> > >
> > >
> > > --
> > > 
> > > Guillaume Nodet
> > > 
> > > Red Hat, Open Source Integration
> > >
> > > Email: gno...@redhat.com
> > > Web: http://fusesource.com
> > > Blog: http://gnodet.blogspot.com/
> > >
> >
> >
> >
> > --
> > http://about.me/milen
> >
>
>
>
> --
>
> Apache Member
> Apache Karaf  Committer & PMC
> OPS4J Pax Web  Committer &
> Project Lead
> blog 
> Co-Author of Apache Karaf Cookbook 
>
> Software Architect / Project Manager / Scrum Master
>



-- 

Guillaume Nodet

Red Hat, Open Source Integration

Email: gno...@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

Re: [DISCUSS] Trim down the number of config files in etc/ in the distributions

[Achim Nierbeck]

yeah, metatype could really help.
All of the properties of Pax Web are already available. But do we use those
already with the config commands?
Should be easy to use?

regards, Achim


2016-11-25 11:13 GMT+01:00 Christian Schneider :

> +1
>
> It is really important that we do such house keeping in karaf as without
> that the distro tends to grow over time.
>
> The only small issue I see is that it is more difficult for people to
> understand the defaults if a config file is not present but maybe we can
> find another
> way to solve this. Maybe using meta type more often.
>
> Christian
>
> On 25.11.2016 08:19, Guillaume Nodet wrote:
>
>> I'd like to trim down a bit the number of files in the etc/ directory.
>> The distribution contains a bunch of config files for the ACLs, but I'm
>> not
>> sure people usually modify those.  I think this may be the same for
>> various
>> configuration.
>> What I'm proposing is the following:
>>* make sure all those configurations are moved into their respective
>> feature
>>* remove them from the assemblies/base maven module which is embedded
>> by
>> the framework and static kars
>>* add a flag on the AssemblyMojo so that we can choose using glob
>> patterns which config pids should be extracted as files at build time
>>* the other ones are extracted automatically by the FeaturesService
>> anyway during boot features installation
>>
>> The idea would be that distributions only contains configurations that are
>> actually used.
>>
>> Also, I'm going to removing some additional files from the static
>> framework
>> (bin/contrib/, bin/instance(.sh|.bat), deploy/).
>>
>> Thoughts ?
>> Guillaume
>>
>>
>>
>
> --
> Christian Schneider
> http://www.liquid-reality.de
>
> Open Source Architect
> http://www.talend.com
>
>


-- 

Apache Member
Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
blog 
Co-Author of Apache Karaf Cookbook 

Software Architect / Project Manager / Scrum Master

Re: [DISCUSS] Trim down the number of config files in etc/ in the distributions

[Christian Schneider]

+1

It is really important that we do such house keeping in karaf as without 
that the distro tends to grow over time.


The only small issue I see is that it is more difficult for people to 
understand the defaults if a config file is not present but maybe we can 
find another

way to solve this. Maybe using meta type more often.

Christian

On 25.11.2016 08:19, Guillaume Nodet wrote:

I'd like to trim down a bit the number of files in the etc/ directory.
The distribution contains a bunch of config files for the ACLs, but I'm not
sure people usually modify those.  I think this may be the same for various
configuration.
What I'm proposing is the following:
   * make sure all those configurations are moved into their respective
feature
   * remove them from the assemblies/base maven module which is embedded by
the framework and static kars
   * add a flag on the AssemblyMojo so that we can choose using glob
patterns which config pids should be extracted as files at build time
   * the other ones are extracted automatically by the FeaturesService
anyway during boot features installation

The idea would be that distributions only contains configurations that are
actually used.

Also, I'm going to removing some additional files from the static framework
(bin/contrib/, bin/instance(.sh|.bat), deploy/).

Thoughts ?
Guillaume





--
Christian Schneider
http://www.liquid-reality.de

Open Source Architect
http://www.talend.com

[GitHub] karaf pull request #268: [KARAF-4843] Updating factory configuration leads t...

[cfiehe]

Github user cfiehe closed the pull request at:

https://github.com/apache/karaf/pull/268


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] karaf pull request #268: [KARAF-4843] Updating factory configuration leads t...

[cfiehe]

GitHub user cfiehe reopened a pull request:

https://github.com/apache/karaf/pull/268

[KARAF-4843] Updating factory configuration leads to new configurati…

…on instance

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/cfiehe/karaf KARAF-4843

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/karaf/pull/268.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #268


commit e852225cdca1a1d831ceffc4b253ff2126652850
Author: Christoph Fiehe 
Date:   2016-11-24T08:18:08Z

[KARAF-4843] Updating factory configuration leads to new configuration 
instance




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Re: [DISCUSS] Trim down the number of config files in etc/ in the distributions

[Achim Nierbeck]

+1 on slimming down the configs.

regarding Milens comments.
It's possible already and called config:edit pid.
All those configurations are stored directly with config-admin service so
there isn't a proprietary config in Karaf.

I only have one comment about it.
Would be great to have a little togle command to enable the write-to-file
for a configuration via the config command.
That would make it much easier.

regards, Achim



2016-11-25 9:51 GMT+01:00 Milen Dyankov :

> I like the idea of reducing the number of files in etc folder.
> However I would vote against it until there is a good documentation of how
> to configure everything that's in those removed files. That is what can be
> configured, where, how it differs in clustered env, ...
> Once that is place that is easy to find and use I'd love to get rid of
> those.
>
> Side note: I don't know how configuration from features works but we need
> to be careful with location bindings. We at Liferay used to have some
> issues with bundles providing own default configuration which was not
> possible to change later on because of location bindings. I'm not saying
> this will be a problem with Karaf, but just to keep an eye on it while
> changing things.
>
> Best,
> Milen
>
> On Fri, Nov 25, 2016 at 8:19 AM, Guillaume Nodet 
> wrote:
>
> > I'd like to trim down a bit the number of files in the etc/ directory.
> > The distribution contains a bunch of config files for the ACLs, but I'm
> not
> > sure people usually modify those.  I think this may be the same for
> various
> > configuration.
> > What I'm proposing is the following:
> >   * make sure all those configurations are moved into their respective
> > feature
> >   * remove them from the assemblies/base maven module which is embedded
> by
> > the framework and static kars
> >   * add a flag on the AssemblyMojo so that we can choose using glob
> > patterns which config pids should be extracted as files at build time
> >   * the other ones are extracted automatically by the FeaturesService
> > anyway during boot features installation
> >
> > The idea would be that distributions only contains configurations that
> are
> > actually used.
> >
> > Also, I'm going to removing some additional files from the static
> framework
> > (bin/contrib/, bin/instance(.sh|.bat), deploy/).
> >
> > Thoughts ?
> > Guillaume
> >
> >
> > --
> > 
> > Guillaume Nodet
> > 
> > Red Hat, Open Source Integration
> >
> > Email: gno...@redhat.com
> > Web: http://fusesource.com
> > Blog: http://gnodet.blogspot.com/
> >
>
>
>
> --
> http://about.me/milen
>



-- 

Apache Member
Apache Karaf  Committer & PMC
OPS4J Pax Web  Committer &
Project Lead
blog 
Co-Author of Apache Karaf Cookbook 

Software Architect / Project Manager / Scrum Master

Re: [DISCUSS] Trim down the number of config files in etc/ in the distributions

[Milen Dyankov]

I like the idea of reducing the number of files in etc folder.
However I would vote against it until there is a good documentation of how
to configure everything that's in those removed files. That is what can be
configured, where, how it differs in clustered env, ...
Once that is place that is easy to find and use I'd love to get rid of
those.

Side note: I don't know how configuration from features works but we need
to be careful with location bindings. We at Liferay used to have some
issues with bundles providing own default configuration which was not
possible to change later on because of location bindings. I'm not saying
this will be a problem with Karaf, but just to keep an eye on it while
changing things.

Best,
Milen

On Fri, Nov 25, 2016 at 8:19 AM, Guillaume Nodet  wrote:

> I'd like to trim down a bit the number of files in the etc/ directory.
> The distribution contains a bunch of config files for the ACLs, but I'm not
> sure people usually modify those.  I think this may be the same for various
> configuration.
> What I'm proposing is the following:
>   * make sure all those configurations are moved into their respective
> feature
>   * remove them from the assemblies/base maven module which is embedded by
> the framework and static kars
>   * add a flag on the AssemblyMojo so that we can choose using glob
> patterns which config pids should be extracted as files at build time
>   * the other ones are extracted automatically by the FeaturesService
> anyway during boot features installation
>
> The idea would be that distributions only contains configurations that are
> actually used.
>
> Also, I'm going to removing some additional files from the static framework
> (bin/contrib/, bin/instance(.sh|.bat), deploy/).
>
> Thoughts ?
> Guillaume
>
>
> --
> 
> Guillaume Nodet
> 
> Red Hat, Open Source Integration
>
> Email: gno...@redhat.com
> Web: http://fusesource.com
> Blog: http://gnodet.blogspot.com/
>



-- 
http://about.me/milen

Re: [DISCUSS] Trim down the number of config files in etc/ in the distributions

[Grzegorz Grzybek]

The slimmer, the better, nice to have in 4.1

regards
Grzegorz

2016-11-25 8:22 GMT+01:00 Jean-Baptiste Onofré :

> +1 to do it on master.
>
> Regards
> JB⁣​
>
> On Nov 25, 2016, 08:19, at 08:19, Guillaume Nodet 
> wrote:
> >I'd like to trim down a bit the number of files in the etc/ directory.
> >The distribution contains a bunch of config files for the ACLs, but I'm
> >not
> >sure people usually modify those.  I think this may be the same for
> >various
> >configuration.
> >What I'm proposing is the following:
> >  * make sure all those configurations are moved into their respective
> >feature
> >* remove them from the assemblies/base maven module which is embedded
> >by
> >the framework and static kars
> >  * add a flag on the AssemblyMojo so that we can choose using glob
> >patterns which config pids should be extracted as files at build time
> >  * the other ones are extracted automatically by the FeaturesService
> >anyway during boot features installation
> >
> >The idea would be that distributions only contains configurations that
> >are
> >actually used.
> >
> >Also, I'm going to removing some additional files from the static
> >framework
> >(bin/contrib/, bin/instance(.sh|.bat), deploy/).
> >
> >Thoughts ?
> >Guillaume
> >
> >
> >--
> >
> >Guillaume Nodet
> >
> >Red Hat, Open Source Integration
> >
> >Email: gno...@redhat.com
> >Web: http://fusesource.com
> >Blog: http://gnodet.blogspot.com/
>

Re: [DISCUSS] Trim down the number of config files in etc/ in the distributions

[Jean-Baptiste Onofré]

+1 to do it on master.

Regards
JB⁣​

On Nov 25, 2016, 08:19, at 08:19, Guillaume Nodet  wrote:
>I'd like to trim down a bit the number of files in the etc/ directory.
>The distribution contains a bunch of config files for the ACLs, but I'm
>not
>sure people usually modify those.  I think this may be the same for
>various
>configuration.
>What I'm proposing is the following:
>  * make sure all those configurations are moved into their respective
>feature
>* remove them from the assemblies/base maven module which is embedded
>by
>the framework and static kars
>  * add a flag on the AssemblyMojo so that we can choose using glob
>patterns which config pids should be extracted as files at build time
>  * the other ones are extracted automatically by the FeaturesService
>anyway during boot features installation
>
>The idea would be that distributions only contains configurations that
>are
>actually used.
>
>Also, I'm going to removing some additional files from the static
>framework
>(bin/contrib/, bin/instance(.sh|.bat), deploy/).
>
>Thoughts ?
>Guillaume
>
>
>-- 
>
>Guillaume Nodet
>
>Red Hat, Open Source Integration
>
>Email: gno...@redhat.com
>Web: http://fusesource.com
>Blog: http://gnodet.blogspot.com/