Hi David,
On Thu, May 3, 2018 at 10:11 AM, David Bosschaert
wrote:
> ...I'm not sure I like the idea of renaming sling-org-apache-sling-feature to
> sling-org-apache-sling-feature-docs as that repository also contains the
> API classes, so it's not just a docs
Hi David,
This [1] is the script that generates the Sling modules’ grouping. Robert and
Bertrand might be able to help if you don’t want to update the script yourself.
Cheers,
Radu
[1] -
https://github.com/apache/sling-aggregator/blob/master/collect-sling-repos.groovy
On 3 May 2018 at 09:11, David Bosschaert wrote:
> Hi Bertrand,
>
> I'm not sure I like the idea of renaming sling-org-apache-sling-feature to
> sling-org-apache-sling-feature-docs as that repository also contains the
> API classes, so it's not just a docs repo.
>
> I
Hi Bertrand,
I'm not sure I like the idea of renaming sling-org-apache-sling-feature to
sling-org-apache-sling-feature-docs as that repository also contains the
API classes, so it's not just a docs repo.
I wasn't aware of the http://sling.apache.org/repolist.html page, but it
seems that the
On Wed, May 2, 2018 at 3:30 PM, Bertrand Delacretaz
wrote:
> ...Should those README point to
> https://github.com/apache/sling-org-apache-sling-feature as the source
> of documentation?...
...and, thinking about it, if that's the case it would be good to
rename that
On Wed, May 2, 2018 at 3:13 PM, David Bosschaert
wrote:
> ...I have now added readme.md files to all feature model related repos. They
> are short and should definitely be expanded, but they might do for the
> 0.1.0 release...
Cool, thanks!
Should those README point
I have now added readme.md files to all feature model related repos. They
are short and should definitely be expanded, but they might do for the
0.1.0 release.
Best regards,
David
On 2 May 2018 at 11:40, David Bosschaert wrote:
> Hi Bertrand,
>
> Good point. The
Hi Bertrand,
Good point. The original featuremodel component in the sling whiteboard had
a readme which went to sling-org-apache-sling-feature.
However the other repos don't have a readme yet.
Best regards,
David
On 2 May 2018 at 10:49, Bertrand Delacretaz wrote:
>
Hi,
On Mon, Apr 30, 2018 at 12:32 PM, David Bosschaert
wrote:
> With the Sling Feature Model now being outside of the Sling Whiteboard in
> proper Git repositories, I'd like to do a an initial release of the
> following components some time soon...
Do we have any
0.1.0 works for me too.
I'll work on preparing the repos with this.
Best regards,
David
On 1 May 2018 at 07:55, Carsten Ziegeler wrote:
> Good idea, we usually start with 0.1.0 for such releases. I think to
> clearly mark these as pre-versions, the package exports
Good idea, we usually start with 0.1.0 for such releases. I think to
clearly mark these as pre-versions, the package exports should be
changed from 1.0.0 to 0.1.0. Versions below 1.0 mark them as potentially
unstable.
Once we are happy with these modules and we release a 1.0.0, the package
Note that the Felix Utils Component will need to be released before we can
release these. I'm planning on starting the release of that component over
the coming few days.
Best regards,
David
On 30 April 2018 at 11:32, David Bosschaert
wrote:
> Hi all,
>
> With the
Hi all,
With the Sling Feature Model now being outside of the Sling Whiteboard in
proper Git repositories, I'd like to do a an initial release of the
following components some time soon:
sling-org-apache-sling-feature
sling-org-apache-sling-feature-analyser
Thanks Robert, I moved them there.
Best regards,
David
On 27 April 2018 at 12:23, Robert Munteanu wrote:
> Hi David,
>
> On Fri, 2018-04-27 at 12:17 +0100, David Bosschaert wrote:
> > Thanks Karl!
> >
> > I have now moved the content to the new git repositories.
> >
> >
Hi David,
On Fri, 2018-04-27 at 12:17 +0100, David Bosschaert wrote:
> Thanks Karl!
>
> I have now moved the content to the new git repositories.
>
> There is one directory left in sling-whiteboard/featuremodel and
> that's the
> example directory. This would be a nice starting point for user
>
Thanks Karl!
I have now moved the content to the new git repositories.
There is one directory left in sling-whiteboard/featuremodel and that's the
example directory. This would be a nice starting point for user
documentation etc. Maybe we should create a separate repository for this?
I create the repositories (including the slingfeature-maven-plugin).
regards,
Karl
On Thu, Apr 26, 2018 at 8:34 PM, Carsten Ziegeler wrote:
> Sounds good to me, sling-slingfeature-maven-plugin sounds like a good
> name as well. As we'll need a plugin at some point, I
Sounds good to me, sling-slingfeature-maven-plugin sounds like a good
name as well. As we'll need a plugin at some point, I think it makes
sense to create it now already
Regards
Carsten
David Bosschaert wrote
> Hi all,
>
> Thanks all for supporting the idea!
>
> I would propose the following
Hi all,
Thanks all for supporting the idea!
I would propose the following Git repository names:
> * feature - The Feature Model API
sling-org-apache-sling-feature
> * feature-analyser - Analyser Module for Features
sling-org-apache-sling-feature-analyser
> * feature-applicationbuilder -
On Thu, Apr 26, 2018 at 12:54 PM, David Bosschaert
wrote:
> ...With the current state I would propose that we start looking at moving the
> Feature Model into mainstream Sling. Would everyone be ok with this?...
Sure!
-Bertrand
HI David,
On Thu, 2018-04-26 at 11:54 +0100, David Bosschaert wrote:
> Hi all,
>
>
> Over the past weeks a lot of work went into improving the Feature
> Model in
> the Sling Whiteboard codebase and trying to find the module structure
> for
> that would hopefully be stable going forward.
>
>
>
Hi all,
Over the past weeks a lot of work went into improving the Feature Model in
the Sling Whiteboard codebase and trying to find the module structure for
that would hopefully be stable going forward.
Right now the following modules are part of the Feature Model:
* feature - The Feature
22 matches
Mail list logo