Re: Pro / Contra: Splitting The Project

2013-10-13 Thread Borut Bolčina
Hello Martin, always split your code! Of course it depends on how large the project is, but a good practice is to have separate projects for different layers. Some examples: simple scenario: myproject-web (contains the web app with majority of services and all the pages and components)

Re: Pro / Contra: Splitting The Project

2013-10-13 Thread Martin Kersten
Thanks for the replies, I currently split it in half. Since I use Hibernate/JPA I just split it in half having a business layer (including the so called persistence layer) and a web layer. Later on it will be joined by a project housing the rest API. And that is all necessary because Eclipse

Re: Pro / Contra: Splitting The Project

2013-10-13 Thread Muhammad Gelbana
What do you mean by that Eclipse is just not good in handling package trees ​ ? *-* *Muhammad Gelbana* http://www.linkedin.com/in/mgelbana On Sun, Oct 13, 2013 at 3:22 PM, Martin Kersten martin.kersten...@gmail.com wrote: Thanks for the replies, I currently split it

Re: Pro / Contra: Splitting The Project

2013-10-12 Thread Muhammad Gelbana
the system needs, these all depend on ih-api I build it all w/ a multi-project gradle build. Works very nicely. -Original Message- From: Robert Hailey [mailto:rhai...@allogy.com] Sent: Friday, October 11, 2013 4:29 PM To: Tapestry users Subject: Re: Pro / Contra: Splitting

Pro / Contra: Splitting The Project

2013-10-11 Thread Martin Kersten
Hi, I am sitting in front of 1.5 MB of sources and I think about splitting the project in half. One for the services + entities + utilities the rest for the web fun. It would also allow to test the core only with unit test and barely with integration tests. Where the web part might be all

Re: Pro / Contra: Splitting The Project

2013-10-11 Thread Jon Williams
yes i do that. pretty standard i think. Cheers Jon On Fri, Oct 11, 2013 at 1:30 PM, Martin Kersten martin.kersten...@gmail.com wrote: Hi, I am sitting in front of 1.5 MB of sources and I think about splitting the project in half. One for the services + entities + utilities the rest

Re: Pro / Contra: Splitting The Project

2013-10-11 Thread Thiago H de Paula Figueiredo
On Fri, 11 Oct 2013 16:30:04 -0300, Martin Kersten martin.kersten...@gmail.com wrote: Hi, Hi! Does anyone split projects in core vs web? Hell yeah! What is the point in doing so and why not? Very simple software development rule: when something gets big, break it in smaller

Re: Pro / Contra: Splitting The Project

2013-10-11 Thread Robert Hailey
The way it usually goes is a three-way split... A B (the logical split), and C (which A B both depend on). -- Robert Hailey On 2013/10/11 (Oct), at 2:44 PM, Jon Williams wrote: yes i do that. pretty standard i think. Cheers Jon On Fri, Oct 11, 2013 at 1:30 PM, Martin Kersten

RE: Pro / Contra: Splitting The Project

2013-10-11 Thread Tony Nelson
on ih-api I build it all w/ a multi-project gradle build. Works very nicely. -Original Message- From: Robert Hailey [mailto:rhai...@allogy.com] Sent: Friday, October 11, 2013 4:29 PM To: Tapestry users Subject: Re: Pro / Contra: Splitting The Project The way it usually goes