Re: [wtp-dev] Publish failures in WTP integration build I200511111814

["Jim D'Anjou" <danjou@xxxxxxxxxx>]

Thanks. I figured it out by debugging the code involved. This helped me understand where you are really publishing to. From there it was pretty obvious. Some bogus dependencies creeped into a project that 0.7 tolerated.

Why does the server perform a publish when it's started even though its state is synchronized (Tomcat)?

BTW, The WAS 6.0 server adapter fails to start a WAS 6.0 server. I have not spent a lot of time on it yet but it just flat out fails (log: Server IBM WebSphere 6 failed to start. with no stack trace). Also, the Add/Remove project dialog does not filter out non-web apps. All projects appear. I will open a bug if that's a new problem.

Jim D'Anjou
Certified IT Specialist/Senior Software Engineer
Rational Developer Tooling
Silicon Valley Lab
Email: danjou@xxxxxxxxxx
Phone Tieline 543-2351 Outside 408-463-2351
FAX Tieline 543-3873 Outside 408-463-3873

The Java Developer's Guide to Eclipse, Second Edition - http://www.jdg2e.com

Timothy Deboer <deboer@xxxxxxxxxx>

Timothy Deboer <deboer@xxxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

11/16/2005 04:58 PM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	Re: [wtp-dev] Publish failures in WTP integration build I200511111814

Hi Jim, 

FWIW, the exception is a valid bug and I'll fix it for M9 (please feel free to open a bug). This failure only happens when there are 0 files in a Web or utility module, so the root cause would most likely be an invalid project or an empty source directly like Igor found. 

Thanks, 
Tim deBoer
WebSphere Tools - IBM Canada Ltd.
(905) 413-3503  (tieline 969)
deboer@xxxxxxxxxx

Igor Fedorenko <igorfie@xxxxxxxxx>
Sent by: wtp-dev-bounces@xxxxxxxxxxx

11/16/2005 08:34 AM

Please respond to
"General discussion of project-wide or architectural issues."

To	"General discussion of project-wide or architectural issues." <wtp-dev@xxxxxxxxxxx>
cc
Subject	Re: [wtp-dev] Publish failures in WTP integration build I200511111814

Check build path of dependent utility projects. I saw this exception
when one of my dependent projects did not have source directory (see
bugzilla 116489 for reasons why).

We tried 0.7 -> 1.0 M9 migration this week, too. Interestingly enough,
it almost worked for me but did not work a colleague of my. Same WTP
build, same set of projects. Very strange.

Jim D'Anjou wrote:
> Our group is heavily dependent on WTP 0.7 and I am doing a sniff test of 
> the near-M9 build to assess our ability to move to M9 or 1.0. I have an 
> inexplicable publish exception that occurs 3 times during publication 
> (to Tomcat 5.0). All 3 exceptions are identical which suggests there is 
> an empty zip file(s) somewhere. How can identify what might be the 
> source of the problem?
> 
> Let me add that the dynamic web project did NOT migrate when it was 
> imported into this WTP version from its origin as a 0.7 web project. 
> This in itself is a concern. I had to add manually add the Dynamic Web 
> Module facet as well as some other hand crafting to make this work. This 
> project has 20 utility project dependencies and there are confirmation 
> messages that all of them published successfully followed by 3 
> exceptions that are reported like this:
> 
> Error copying file to {0}: {1}
> java.util.zip.ZipException: ZIP file must have at least one entry
> at java.util.zip.ZipOutputStream.finish(ZipOutputStream.java:317)
> at java.util.zip.DeflaterOutputStream.close(DeflaterOutputStream.java:162)
> at java.util.zip.ZipOutputStream.close(ZipOutputStream.java:336)
> at 
> org.eclipse.jst.server.core.PublishUtil.createZipFile(PublishUtil.java:288)
> at 
> org.eclipse.jst.server.tomcat.core.internal.PublishOperation2.publishJar(PublishOperation2.java:90)
> at 
> org.eclipse.jst.server.tomcat.core.internal.PublishOperation2.execute(PublishOperation2.java:51)
> at 
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.performTasks(ServerBehaviourDelegate.java:744)
> at 
> org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:565)
> at org.eclipse.wst.server.core.internal.Server.doPublish(Server.java:719)
> at org.eclipse.wst.server.core.internal.Server.publish(Server.java:708)
> at 
> org.eclipse.wst.server.core.internal.PublishServerJob.run(PublishServerJob.java:145)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:76)
> 
> We have a large development team working on a very large project and 
> it's important that we can move off of 0.7 when its time to do so. There 
> is only limited time left to identify problems that you might have an 
> opportunity to fix before GA.
> 
> One additional concern. The migration from 0.7 will require our entire 
> team (in disbursed geographic locations) to move all at once. This is 
> doable but complicated and exposes the risk that we can't go back if we 
> have to....at least not easily.
> 
> Thank you.
> 
> Jim D'Anjou
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> wtp-dev mailing list
> wtp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/wtp-dev



_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev
_______________________________________________
wtp-dev mailing list
wtp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-dev