I don't recall any issues with Seam 2.1.RC1 that should cause for missing
manifest.mf files...weird.
Thanks for letting us know it does not happen for you except for 2.1.RC1.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4199005#4199005
Reply to the post :
Max,
It makes a BIG difference when you say that you can't reproduce what i've
described while using seam 2.0
In fact we were not completely synchronized (please be patient i'll explain
all).
I've been searching and deeply testing these last three days and I'm happy
because all my troubles are
Max,
I've updated my WTP from 3.0 to 3.0.3 from the update site.
But I'm still facing with these same behaviours:
1)The generated ear has no META-INF folder
2)The librairies are not copies on top of the ear.
It seems like that the EarContent of the created ear project is completed
ignored by
Max,
I would like to add a precision. The META-INF folder is created, but it is
empty (no application.xml and jboss-app.xml files)
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4198153#4198153
Reply to the post :
Please report in jira with *exact* steps on how you created and deployed it - I
cannot reproduce this when I run Seam WTP wizard, using Seam 2.0. Both WAR and
EAR is deployed fully.
Also try and do a full rebuild of your project, to see if it is some issue with
the files not being ready before
which version of Ganymede are you using ?
We recommend to use at least WTP 3.0.3.
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=4197920#4197920
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=4197920
max.ander...@jboss.com wrote : which version of Ganymede are you using ?
|
| We recommend to use at least WTP 3.0.3.
I'm using ganymede 3.4.1 version.
It's stable and we're using it for all our projects.
Meissa
View the original post :
meissa, 3.4.1 is about the main eclipse version.
I'm talking about WTP.
And if it is stable and working for you then great, but the error you are
describing is most likely caused by a bug in WTP 3.0.1 and 3.0.2 which recently
got fixed.
If the problem persists after you upgraded to 3.0.3 then
