Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
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

Back to the top