Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-users] EAR deployment problem with Eclipse Helios and m2eclipse

Thanks and sorry I didn't look well enough.

One hour ago I tested with Eclipse 3.5.2 SR2 (& JBoss Tools 3.1.1.GA). There isn't this problem with the name of the ear. I don't understand. You are talking about a new feature but with 3.5.2 SR2, the deploy-name value from the .settings/org.eclipse.wst.common.component file is used. Isn't it rather a regression in the m2e-eclipse-plugin ? Or it's the JBoss Tools 3.2.0.beta1 which overrides the behaviour of the m2e plugin ?

However I've an another problem now. The dependencies of the ejbs which are ordinary in the directory /lib at the root of the ear are in my-1.0.ear/lib/lib/. This time I found the issue : I will download the latest WTP patch at tomorrow like you said in MNGECLIPSE-2150.

To answer your question I need control deployed name of the ear to deploy 2 different versions of the same ear exactly like you thought.

I can't resist to tell you an another thing. I don't want to bother the mailing list. But I think related to the subject of the topic.

A few months ago I developed with Eclipse 3.4, Tomcat and Maven. I used m2e and sysdeo to hot-deploy my wars. I was really happy with this development environment. Today I move to ejb and Jboss. At the beginnig I tried JBossDeveloperStudio. I was forced to upgrade the RAM of my machine from 2 Go RAM to 4 Go to JBDS. It's not easy to express. I havn't had a good feeling. Build and update maven dependencies longer, freeze, crash of Eclipse, JBoss startup time ... All this tasks seems to be done slower than before with my little tomcat. I decided to restart with an eclipse and to install all plugins by my self. It's a little better but I meet some new issues as you can see.
I can believe it's the price to pay to deal with JEE and to have an app server wich provides clustering, session replication, etc. But I can too believe this is mine. I asked me lots of questions. 

On Thu, 3 Feb 2011 16:45:28 +0100, Fred Bricon <fbricon@xxxxxxxxx> wrote :

Hi Thibaut,

this is actually a JBoss Tools issue. Rob Stryker from JBoss confirmed this
feature doesn't exist.
He pointed me to which kinda
relates to this.

Out of curiosity, can I ask why you would need to strictly control the
deployed name of the ear?
It *usually* has no impact on the behavior of the deployed app(s). Except if
you need to deploy 2 versions of the same EAR on the same server at the same
time (which would lead to other issues).


Fred Bricon

On Thu, Feb 3, 2011 at 4:17 PM, Thibault Richard <thb.rchrd@xxxxxxxxx>wrote:

> Hi all,
> I'm having problems when i'm trying to deploy an ear in Eclipse Helios 3.6
> in JBoss EAP 5.1 in exploded mode.
> My problem is that i can't choose the name of the ear which is deployed in
> JBoss in exploded mode (using mode 'deploy JBoss folder').
> I tried to add ' <finalName>${project.artifactId}-${earVersion}</finalName>
> ' in  the <build> .. </build> of the pom.xml of the ear project.
> My .settings/org.eclipse.wst.common.component looks like :
> <?xml version="1.0" encoding="UTF-8"?>
> <project-modules id="moduleCoreId" project-version="1.5.0">
> <wb-module deploy-name="myproject-ear-1.4-SNAPSHOT"> // I hoped this
> deploy-name is used but it's not.
> <wb-resource deploy-path="/" source-path="/src/main/application"/>
> The only workaround i've found so far is to rename the eclipse project.
> Does it looks like I made a configuration error?
> Do you think I should file an issue on the bug tracker?
> Here's my complete 'technical stack' :
> * Eclipse Helios SR1 build id : 20100917-0705 -
> org.eclipse.rcp_3.6.1.r361_v20100827 and those plugins :
> * m2e - Maven Integration for Eclipse - org.maven.ide.eclipse
> * m2e-extras - Maven Integration for Eclipse -
> org.maven.ide.eclipse.wtp.feature_0.11.1.20101108-1810
> * WTP - Eclipse Java EE Developer Tools
> - org.eclipse.wst.common_[core|ui].feature_3.2.2.v201008091400
> * JBoss by RedHat - JBossAS Tools -
> With :
> * JBoss [EAP] 5.1.0 (build: SVNTag=JBPAPP_5_1_0 date=201009150028)
> * Apache Maven : 3.0.1 (r1038046; 2010-11-23 11:58:32+0100)
> * Java(TM) SE Runtime Environment (build 1.6.0_23-b05) - Java HotSpot(TM)
> 64-Bit Server VM (build 19.0-b09, mixed mode)
> * OS: Linux 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:32:27 UTC 2010
> x86_64 GNU/Linux
> Thanks,
> // Thibault
> _______________________________________________
> m2e-users mailing list
> m2e-users@xxxxxxxxxxx

Back to the top