Re: splitting apart a web app
Rusty Wright-2 wrote: I looked at that but they're not splitting it down to the level that I'm trying. snip / I was thinking of splitting my web app so that I have a cars-war project where in the scm it contains only things like the jsps, no java code. In its pom it will specify a dependency on cars-web which will be a jar file which contains the spring mvc controllers and such. And cars-web will depend on a jar which contains the business logic. In the end the war file will only contain jars, no class files (not that that's important). I'm thinking that this may make it easier when working with our html editor person. We do this currently - for exactly the reasons that you describe - and it works fine. -- View this message in context: http://www.nabble.com/splitting-apart-a-web-app-tp20861834p20891747.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: splitting apart a web app
Andy Law wrote: We do this currently - for exactly the reasons that you describe - and it works fine. Although picking up properties files etc. in DreamWeaver doesn't work. sigh / Later, Andy -- View this message in context: http://www.nabble.com/splitting-apart-a-web-app-tp20861834p20894413.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: splitting apart a web app
The defintive guide has a good example of a multi-module web app which may point you in the right direction. http://books.sonatype.com/maven-book/reference/multimodule.html --- Todd Thiessen -Original Message- From: Rusty Wright [mailto:[EMAIL PROTECTED] Sent: Friday, December 05, 2008 3:22 PM To: Maven Users List Subject: splitting apart a web app I haven't seen this in the examples in the 2 maven books and I was wondering if it's perhaps not a good idea. I was thinking of splitting my web app so that I have a cars-war project where in the scm it contains only things like the jsps, no java code. In its pom it will specify a dependency on cars-web which will be a jar file which contains the spring mvc controllers and such. And cars-web will depend on a jar which contains the business logic. In the end the war file will only contain jars, no class files (not that that's important). I'm thinking that this may make it easier when working with our html editor person. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: splitting apart a web app
I looked at that but they're not splitting it down to the level that I'm trying. Todd Thiessen wrote: The defintive guide has a good example of a multi-module web app which may point you in the right direction. http://books.sonatype.com/maven-book/reference/multimodule.html --- Todd Thiessen -Original Message- From: Rusty Wright [mailto:[EMAIL PROTECTED] Sent: Friday, December 05, 2008 3:22 PM To: Maven Users List Subject: splitting apart a web app I haven't seen this in the examples in the 2 maven books and I was wondering if it's perhaps not a good idea. I was thinking of splitting my web app so that I have a cars-war project where in the scm it contains only things like the jsps, no java code. In its pom it will specify a dependency on cars-web which will be a jar file which contains the spring mvc controllers and such. And cars-web will depend on a jar which contains the business logic. In the end the war file will only contain jars, no class files (not that that's important). I'm thinking that this may make it easier when working with our html editor person. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
