RE : Hot deployment in IBM RAD 7.0 (Eclipse 3.2)

[Elid OR <or...@fimasys.fr>]

You are talking about a maven plugin for IBM RAD 7. I don't think such a plugin exist perhaps IBM RAD 7 is based on a version of eclipse WTP and you can use the corresponding.
There is a maven plugin for eclipse/wtp that allow to add wtp capabilities to your maven project (i.e generate eclipse/wtp files that allow eclipse to handle your project as a wtp one). This allow to use WTP deployment and hot deployment features.

http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html

-------- Message d'origine--------
De:	Gonzalo Vásquez Sáez [mailto:gonzalo.vasquez.saez@gmail.com]
Date:	mar. 24/04/2007 17:26
À:	Maven Users List
Cc:	
Objet:	Hot deployment in IBM RAD 7.0 (Eclipse 3.2)

I hope that I can make myself clear with my problem, as it a bit complicated
to explain:

I'm using IBM RAD 7.0 (just moved a few weeks ago from RAD 6.0) with several
Java (JAR), Web Module (WAR) and Enterprise Application (EAR) projects,
which in turn we are converting them to Maven enabled projects, through the
use of the Eclipse plugin for Maven.

The whole pom.xml creation process already has been done, all projects
compile as they should, and are finally grouped into a single EAR file which
actually works fine if it gets installed as a regular application on the
application server (IBM WAS 6.0).

The problem appears when I try to deploy directly from my workspace, not
from a pre-made EAR file, as this is over 90% use case, as we are actual
team of developers, not just mere installers.

Projects do compile and build according to pom.xml specification, including
all necessary dependencies into the packaged output; but I don't have those
dependencies available at runtime, as they are only referenced at compile
time through the use of an ENVIRONMENT variable introduced by the Eclipse
Maven plugin. So all dependencies get unresolved at runtime, this is the
real issue I'm facing.

I think what I need is a plugin to deploy my workspace to WAS as RAD does
per-se, but considering Maven specified dependencies.

Can anyone provide me with a solution to this missing dependencies issue?

Regards,

Gonzalo Vasquez

Re: RE : Hot deployment in IBM RAD 7.0 (Eclipse 3.2)

[Gonzalo Vásquez Sáez <go...@gmail.com>]

It helps, but just does the same (or very similar) than the eclipse Maven
Plugin, so I doesn't solve my problem. Now I'm trying a different aproach by
just make a plain EAR project with no Maven support :(, at least that works
;)

Still any help on the problem would be appreciated.

On 24/04/07, Elid OR <or...@fimasys.fr> wrote:
>
>
> You are talking about a maven plugin for IBM RAD 7. I don't think such a
> plugin exist perhaps IBM RAD 7 is based on a version of eclipse WTP and you
> can use the corresponding.
> There is a maven plugin for eclipse/wtp that allow to add wtp capabilities
> to your maven project (i.e generate eclipse/wtp files that allow eclipse
> to handle your project as a wtp one). This allow to use WTP deployment and
> hot deployment features.
>
> http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html
>
> -------- Message d'origine--------
> De:     Gonzalo Vásquez Sáez [mailto:gonzalo.vasquez.saez@gmail.com]
> Date:   mar. 24/04/2007 17:26
> À:      Maven Users List
> Cc:
> Objet:  Hot deployment in IBM RAD 7.0 (Eclipse 3.2)
>
> I hope that I can make myself clear with my problem, as it a bit
> complicated
> to explain:
>
> I'm using IBM RAD 7.0 (just moved a few weeks ago from RAD 6.0) with
> several
> Java (JAR), Web Module (WAR) and Enterprise Application (EAR) projects,
> which in turn we are converting them to Maven enabled projects, through
> the
> use of the Eclipse plugin for Maven.
>
> The whole pom.xml creation process already has been done, all projects
> compile as they should, and are finally grouped into a single EAR file
> which
> actually works fine if it gets installed as a regular application on the
> application server (IBM WAS 6.0).
>
> The problem appears when I try to deploy directly from my workspace, not
> from a pre-made EAR file, as this is over 90% use case, as we are actual
> team of developers, not just mere installers.
>
> Projects do compile and build according to pom.xml specification,
> including
> all necessary dependencies into the packaged output; but I don't have
> those
> dependencies available at runtime, as they are only referenced at compile
> time through the use of an ENVIRONMENT variable introduced by the Eclipse
> Maven plugin. So all dependencies get unresolved at runtime, this is the
> real issue I'm facing.
>
> I think what I need is a plugin to deploy my workspace to WAS as RAD does
> per-se, but considering Maven specified dependencies.
>
> Can anyone provide me with a solution to this missing dependencies issue?
>
> Regards,
>
> Gonzalo Vasquez
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>