Given the discussions, I've moved the codebase from the whiteboard to tooling/ide. I've created a Sling job at https://builds.apache.org/view/S-Z/view/Sling/job/sling-ide-1.6/ and also applied exclusions for tooling/ide when building the sling-trunk-{1.6,1.7} jobs.
The tooling/ide reactor is not yet part of the default reactor. It's a good question whether it should be – or rather whether the whole tooling directory should be part of the default reactor. But that's another topic. For now, it builds separately and I'll follow up on different Jira issues/discussions for incremental improvements. BTW, should we have a Jira component for it or keep using 'Extensions' like we did so far? Thanks, Robert On Wed, Jul 24, 2013 at 6:49 PM, Daniel Klco <daniel.k...@gmail.com> wrote: > +1 > > > On Wed, Jul 24, 2013 at 10:42 AM, Robert Munteanu <rob...@lmn.ro> wrote: > >> On Wed, Jul 24, 2013 at 5:15 PM, Bertrand Delacretaz >> <bdelacre...@apache.org> wrote: >> > On Wed, Jul 24, 2013 at 4:02 PM, Felix Meschberger <fmesc...@adobe.com> >> wrote: >> >> ...create a top level "tooling" (or so) folder and put the "ide" and >> "maven" stuff in there ?... >> >> I've created [0] to track this move and will do that later on today - >> lots of stuff to adjust in the poms under maven. >> >> Robert >> >> [0]: https://issues.apache.org/jira/browse/SLING-2978 >> >> >> >> -- >> Sent from my (old) computer >> -- Sent from my (old) computer
