| Alternate way of packaging projects for deployment [message #213603] |
Sun, 11 May 2008 14:35  |
Eclipse User |
|
|
|
For Maven integration (in IAM project proposal), we've integrated maven
web projects with wtp so they can be launched on any configured server.
However, WTP is doing the packaging. We would like to let Maven do it
(or achive a jar/war file that's equivalent to what maven would have
generated). This is because in maven build resources can be modified
before packaging.
Could I get some pointers about how this can be done?
Also, if there is an overview of the deployment process available, it
would come handy :-)
Thanks!
--
Abel Muiño Vizcaino - http://ramblingabout.wordpress.com
|
|
|
|
|
|
| Re: Alternate way of packaging projects for deployment [message #214012 is a reply to message #213848] |
Mon, 19 May 2008 14:10  |
| Eclipse User |
|
|
|
Thanks Konstantin,
So the only way would be to create new server adapters which mimic
existing ones but with a "maven flavour"?
By looking at the Javadoc, it would seem that overriding
ServerBehaviourDelegate.publish() could do the trick (still, new servers
would be required).
Is there any pitfall I'm not seeing?
--
Abel Muiño Vizcaino - http://ramblingabout.wordpress.com
Konstantin Komissarchik wrote:
> Abel,
>
> In WTP, server adapters own the publishing logic (which includes
> getting the app ready for publishing). There is a publish steps
> extension point that lets you add additional logic to the publish
> operation, but there is no way to completely replace the packaging.
> That wouldn't work anyway, since different server adapters have
> different requirements for the form that the app must be in for
> publishing. Some require a WAR archive, some require an exploded WAR
> directory, and some have proprietary descriptors that tell the server
> where to find pieces of the WAR without actually physically assembling
> it.
>
> - Konstantin
|
|
|
Powered by
FUDForum. Page generated in 0.04525 seconds
Home