On 1/5/12 6:39 PM, Leo Neumeyer wrote:
I'd rather leave "subprojects" to make it easy to understand where all
the sources are, it's a nice hierarchical structure. Subprojects
refers to Gradle subprojects. Otherwise you will have a bunch of dir
names mixed in the top level dir and dont' know what is under each.
To conserve the heirachichal structure, you could do:
subprojects/examples/{counter, twitter}
with a top level build script under examples.
what do you think?
We'd still need, so that we have a clean organization, to distinguish
between platform code, examples and test apps:
subprojects/platform/{s4-core, s4-comm, s4-base}
subprojects/test-apps/{simple-deployable-app-1, simple-deployable-app-2,
etc..}
subprojects/examples/{counter, twitter, etc..}
Do you agree?
Matthieu
On Thu, Jan 5, 2012 at 9:27 AM, Matthieu Morel<[email protected]> wrote:
Hi,
while working on S4-24, I ended up putting test apps in the "test-apps"
folder at the root of the S4 project, instead of putting everything under
"subprojects": it was clearer, and it was easier to make gradle work this
way.
I would like to go further, for the sake of clarity, and:
1. rename "subprojects" into "platform" , with s4-base, s4-core, s4-comm:
the code of the S4 runtime
2. add an "example" folder: it would contain example applications in
subfolders. Each example would have its own build.gradle script so that it
could be easily packaged.
What do you think?
Does anyone disagree or have a different suggestion?
Thanks!
Matthieu
