Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Language IDEs » ServerTools (WTP) » Dynamic Deployment Assemblies
icon5.gif  Dynamic Deployment Assemblies [message #723445] Thu, 08 September 2011 15:10 Go to next message
Blank Reg is currently offline Blank RegFriend
Messages: 4
Registered: September 2011
Junior Member
I have a dynamic web page project that builds with maven and runs on Tomcat.
I am using a Server project to test the web application.
I am now adding a new customer who has different files, e.g. classes, configuration files, images, etc.
I can easily configure a different build in maven using a customer property but this obviously has no effect on the publishing of the server using the Server project.

What is the best way to handle the different configurations so they work in both maven and the Servers project?

I can hack Maven to copy stuff in and out of different places during the compile instead of the deployment, but I wonder if there is a less hacky solution?

Re: Dynamic Deployment Assemblies [message #723808 is a reply to message #723445] Fri, 09 September 2011 14:21 Go to previous message
Larry Isaacs is currently offline Larry IsaacsFriend
Messages: 1354
Registered: July 2009
Senior Member
On 9/8/2011 11:10 AM, Blank Reg wrote:
> I have a dynamic web page project that builds with maven and runs on
> Tomcat.
> I am using a Server project to test the web application.
> I am now adding a new customer who has different files, e.g. classes,
> configuration files, images, etc.
> I can easily configure a different build in maven using a customer
> property but this obviously has no effect on the publishing of the
> server using the Server project.
>
> What is the best way to handle the different configurations so they work
> in both maven and the Servers project?
>
> I can hack Maven to copy stuff in and out of different places during the
> compile instead of the deployment, but I wonder if there is a less hacky
> solution?
>
>

Maybe what you had in mind, but I think your best bet is to limit what
WTP thinks your webapp is to just some "webcontent" folder. You
wouldn't want any Java source folders publishing to "WEB-INF/classes".
It would be up to the maven build to populate that folder with just what
belongs for that configuration, including coping classes to the folder's
"WEB-INF/classes". Publishing will sync the server with what is in that
"webcontent" folder, removing any files that don't still exist there.

Cheers,
Larry
Previous Topic:Problem with republish not getting triggered
Next Topic:Node "Faces Configuration" shown many times in Project Explorer
Goto Forum:
  


Current Time: Thu Apr 25 11:37:54 GMT 2024

Powered by FUDForum. Page generated in 0.02682 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top