Community
Participate
Working Groups
Build Identifier: 20120216-1857 we have an eclipse prtoduct which has been exported/built many times successfully. However, recently, when I trigger the export product action, all I get in the target directory is the repository, and the eclipse directory with features and plugins subdirectories (with content), an artifact.xml file and a p2 subdirectory. No exectutable, no contents.jar or artifacts.jar as I expected. What I do see is a huge subdirectory tree under the .metadata\.plugins\org.eclipse.pde.core directory in my workspace. It contains hundreds of files that look like artifacts from an aborted build. I dont get any error messages or log entries. This is a major showstopper for us. This only happens when I check the "generate repository metadata" option. When I uncheck it, I get the executable as usual. Reproducible: Always
same build works on a colleagues PC. This is just c**p
ok, I have figured it out. Only took me about 7 hours: initially, all attempts to get product export running again failed. As I said, it myteriously *did* work on a colleagues PC. So I went ahead and tried out the p2 director app, in the hopes that at least it would provide me with some error messages why the stuff failed. I wrote me a script that used the repository which was generated during export, and when I invoked it, indeed got some error message "invalid certificate, install cannot be completed" (or so). That got me thinking - I had indeed replaced the cacerts file from the JDK by a custom CA file, which we need internally. Setting this back to the default cacerts file from the JDK got me going again. So, my urgent request from this is, that error reporting for PDE/P2 build be vastly improved. I still consider this a showstopper issue. I have had a few people looking over my shoulder while this was going on who went away concluding "this tool is not production-ready", and I cannot refute them
It isn't clear to me whether this is a problem with p2 reporting or that PDE Build (or UI) is swallowing the error. All three are involved (PDE UI runs the operation and sets up the build, PDE Build generates and runs the ant script, p2 is responsible for generating the repository). While PDE strives to make exporting from the UI as useful as possible, it isn't as flexible or robust as running the operations directly through PDE Build.
(In reply to comment #3) > While PDE strives to make exporting from the UI as useful as possible, it isn't > as flexible or robust as running the operations directly through PDE Build. what are you trying to say? That we shouldn't be using PDE UI, and go to the (horribly documented) P2 commandline stuff directly? then the UI should be removed, or an explicit warning added "use this if it works, if it doesn't, go to command line" P2 is reporting the error. PDE UI should pass it to the user. I dont think there can be any disagreement here.
(In reply to comment #4) > what are you trying to say? That we shouldn't be using PDE UI, and go to the > (horribly documented) P2 commandline stuff directly? then the UI should be > removed, or an explicit warning added "use this if it works, if it doesn't, go > to command line" > > P2 is reporting the error. PDE UI should pass it to the user. I dont think > there can be any disagreement here. Absolutely, the UI export should report what it can to the user. This is difficult in many cases because the operation is done inside a (PDE Build) generated ant script. Any help in this area is appreciated. Moving this to PDE UI.
(In reply to comment #5) > Absolutely, the UI export should report what it can to the user. This is > difficult in many cases because the operation is done inside a (PDE Build) > generated ant script. Any help in this area is appreciated. the least thing that can (easily) and must be done is to write a log file and put it in some place where the user can find it. I am not even sure that that would or has to be a UI issue
note that the issue of silently failing export is also referenced in Bug 309758 and in Bug 285514, which are bothe PDE Build bugs
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie.
This bug was marked as stalebug a while ago. Marking as worksforme. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard tag.
This bug has been marked as stalebug a while ago without any further interaction. If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.
