2011/9/12 Joe Emenaker :
> On 9/12/2011 6:01 AM, Roger Westerlund wrote:
>> My suggestion is to use a Maven style directory structure.
>> (http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html)
>>
>> src/main/java
>> src/main/recources
>> src/test/java (we d
On 9/12/2011 6:01 AM, Roger Westerlund wrote:
> My suggestion is to use a Maven style directory structure.
> (http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html)
>
> src/main/java
> src/main/recources
> src/test/java (we do test, do we?)
> src/test/recour
2011/9/12 Frankie Fisher :
> On 12/09/2011 14:01, Roger Westerlund wrote:
>>
>> I am not sure that Maven is the way to go for JSynthLib. I have been
>> using Maven in my work for the last couple of years and I have seen
>> Maven being bent over backwards to build a system. It is not a pretty
>> sig
On 12/09/2011 14:01, Roger Westerlund wrote:
>
> I am not sure that Maven is the way to go for JSynthLib. I have been
> using Maven in my work for the last couple of years and I have seen
> Maven being bent over backwards to build a system. It is not a pretty
> sight. I think nothing beats Maven wh
My suggestion is to use a Maven style directory structure.
(http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html)
src/main/java
src/main/recources
src/test/java (we do test, do we?)
src/test/recources
and so on. That will also separate production code fro
Its funny you should say this because I was talking to my friend last
week, and he was saying that maven now is what ant was 10 years ago.
i.e. 10 years ago ant was the standard build system, but these days
maven is.
In the longer run it could be interesting to look into the benefits that
mave
I don't read all the mails, but have you think of using Maven to build
modules (libraries) instead of having one big build project ?
Maybe you could have one project for the core, one for the synthdrivers etc.
Just a suggestion as maven is used all the time in java projects. It
helps to separate
My first suggestion is to move all source code into /src. Optionally,
synthdrivers can be move to /src-synthdrivers or just /synthdrivers in
preparation for the plugin framework. Synths should be repackaged as well,
so the final directory will actually be
/synthdrivers/org/jsynthlib/synthdrivers/
Just wanted to get some opinions/preferences from the group:
1 - When I move all of the stuff from "core" into "org.jsynthlib", how
should it be organized? I'm planning all of the "*ConfigPanel" stuff
moving into org.jsynthlib.config, and probably all of "*Widget" going
into org.jsynthlib.widg
