Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 335008 - Generation and deployment of war within Eclipse
Summary: Generation and deployment of war within Eclipse
Status: RESOLVED FIXED
Alias: None
Product: Virgo
Classification: RT
Component: tooling (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Leo Dos Santos CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 368785
  Show dependency tree
 
Reported: 2011-01-21 08:06 EST by Lorie Pisicchio CLA
Modified: 2013-02-08 19:31 EST (History)
2 users (show)

See Also:

Attachments
The project that can not be deployed in Eclipse (91.49 KB, application/x-gzip)
2011-01-21 08:17 EST, Lorie Pisicchio CLA 		no flags Details
The parent pom.xml (11.04 KB, text/xml)
2011-01-21 08:18 EST, Lorie Pisicchio CLA 		no flags Details
Updated project with no Manifest generation working. (169.61 KB, application/zip)
2013-01-28 11:27 EST, Chris Frost CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lorie Pisicchio CLA 2011-01-21 08:06:43 EST 
Build Identifier: 20100917-0705

I have issues with war deployment within Eclipse, as reported in the following thread http://www.eclipse.org/forums/index.php?t=post&reply_to=649984&S=dcbba32f13a76dda785fb1cc62222f5a&SQ=7fd77697adf5ad8aa3356b4aefec1fa7&
If I build the project with Maven, and put the generated war in the pickup it deploys properly. But if I drag and drop the project on the server within Eclipse, the deployment fails. The Manifest file is not the one generated by Bundlor, and directory structure under the stage directory is not the same as the structure of the war file. 


Reproducible: Always

Steps to Reproduce:
1.Add the project in Eclipse
2.Deploy the project in a Virgo web server instance
Comment 1 Lorie Pisicchio CLA 2011-01-21 08:17:31 EST 
Created attachment 187279 [details]
The project that can not be deployed in Eclipse

The project uses a parent pom that will be provided in a further attachement.
Comment 2 Lorie Pisicchio CLA 2011-01-21 08:18:58 EST 
Created attachment 187280 [details]
The parent pom.xml
Comment 3 Miles Parker CLA 2012-01-16 19:42:41 EST 
Another case of a project deployable standalone but not from Tooling.
Comment 4 Chris Frost CLA 2013-01-28 11:26:29 EST 
I am still finding this a problem but I'm not sure how relevant it is. The project is not a war project as stated and is not using the tooling properly either. If I fix this up and remove the variables in the template file and correct the targeted runtime all the problems go away but it still won't build the manifest file from the template. I've tried toggling all the options but I can't get it going.
Comment 5 Chris Frost CLA 2013-01-28 11:27:00 EST 
Created attachment 226209 [details]
Updated project with no Manifest generation working.
Comment 6 Chris Frost CLA 2013-01-31 11:34:31 EST 
This newly raised bug may be related bug #399654
Comment 7 Leo Dos Santos CLA 2013-02-06 23:48:17 EST 
I haven't been able to get the project completely clean (mainly the com.mootwin references), so I'm not looking at this under ideal conditions, but with the "Scan output folders..." Manifest Generation option turned off, I can generate a manifest under src/main/java/META-INF/MANIFEST.MF. Deploying the bundle will stage the manifest under WEB-INF/classes/META-INF/MANIFEST.MF, which is where it's mapped to under the Deployment Assembly  properties page.
Comment 8 Leo Dos Santos CLA 2013-02-08 19:31:35 EST 
With recent fixes to the tooling this week, this seems to work for me as expected. Please reopen if I've overlooked something.