Mailing-List: contact user-help@struts.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Struts Users Mailing List" <user@struts.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
From: "Marcus Bond" <marcus@marcusbond.me.uk>
To: "Struts Users Mailing List" <user@struts.apache.org>
Subject: Modularisation of project web artifacts
Date: Tue, 6 Sep 2011 20:00:08 +0100
Message-ID: <001201cc6cc7$32ea9d70$98bfd850$@marcusbond.me.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0013_01CC6CCF.94B06500"
Thread-Index: AcxsxH1ZG2BrtJGSQ8SESOggD8LAlw==
Content-Language: en-gb

------=_NextPart_000_0013_01CC6CCF.94B06500
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Has anyone here much experience of separating out actions and associated
jsp's into their own projects (cvs , git whatever) and incorporating these
as artifacts into a larger project (aka the app)?

 
I want to be able to separate out my JSPs into a number of projects which
could be packaged into jars as maven artifacts (un-compiled is fine) and
then using a project maven build file draw these jsp out of their respective
jar files and add to the WEB-INF/whateverpath/ directory of the web-app
build. It looks at first glance like Overlays in Maven could do the trick
but does this approach work in Eclipse when developing too?

 
Anyone have any food for thought on this? Are there any other alternatives
such as deploying jsp in jar files (pre-compilation and corresponding
web.xml path mapping is a non starter)?

 
Cheers,

Marcus 


------=_NextPart_000_0013_01CC6CCF.94B06500--