Re: [platform-update-dev] non-plugin data - what happens to it after an

[Patrick_Mueller@xxxxxxx]

I happened to find the non-plugin jar as:

        X:\tmp\eclipse\.update\1021302748372\eclipse49770.tmp

My plugin jar was:

        X:\tmp\eclipse\.update\1021302748372\eclipse49769.tmp

And the feature jar was:

        X:\tmp\eclipse\.update\1021302748372\eclipse49768.tmp

You are obviously unpacking the feature and plugin jars correctly, so I don't care about their names; however, for the non-plugin jar, how am I ever suppsed to figure out this 'suffix', given all I got was the identifier via INonPluginEntry.getIdentifier(), which returned the identifier (file name) in the feature.xml file?  I think I either need this relatively-qualified temp name, or you will need to rename it to the identifier specifed in the feature.xml file.

        1021302748372\eclipse49770.tmp

BTW, I'm running under 

        java version "1.3.0"
        Java(TM) 2 Runtime Environment, Standard Edition (build 1.3.0)
        Classic VM (build 1.3.0, J2RE 1.3.0 IBM build cn130-20010925 (JIT enabled: jitc))

and there are all sorts of little poops left behind in my X\tmp\eclipse\.update directory.  The feature jar got left behind most often, but occasinally it was the plugin jar, or non-plugin jar, or some combination of them.

Patrick Mueller
patrick_mueller@xxxxxxx

klicnik@xxxxxxxxxx Sent by: platform-update-dev-admin@xxxxxxxxxxx 05/10/2002 03:15 PM Please respond to platform-update-dev

To:        platform-update-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [platform-update-dev] non-plugin data - what happens to it after an install

The downloads happen into a temp directory (System.getProperty("java.io.tmpdir") ... we append eclipse/.update/). The downloaded files are marked as deleteOnExit(). We verify the jars and install the features/ plugins from the jars. We do nothing with the non-plugin files .... we expect you to handle them. Whether you do, or not, when the VM terminates the files are cleaned up. 

To answer the other question .... BootLoader.getInstallURL() is the root of the install tree.

Patrick_Mueller@xxxxxxx Sent by: platform-update-dev-admin@xxxxxxxxxxx 05/10/2002 02:49 PM Please respond to platform-update-dev

To:        platform-update-dev@xxxxxxxxxxx        cc:                Subject:        [platform-update-dev] non-plugin data - what happens to it after an install

OK, so I've got a feature with a plugin and a non-plugin file.  And custom handler.  The base file name of the non-plugin file appears to be set correctly (base meaning there are no path elements to it) by the time my installComplete() (or whatever) callback is called. 

Questions: 

- the non-plugin file is not in the eclipse/install/features directory after the feature install.  My current handler does nothing but print the name of the non-plugin files.  I can't find the non-plugin file anywhere.  Did it get downloaded then erased?  Am I supposed to download it? 

- I'm going to display my incredible ineptitude with eclipse programming by asking how to get the base eclipse install directory (the directory containing the install and plugins directories).  There must be some method somewhere to get this, but I have no idea where to start looking. 

Patrick Mueller
patrick_mueller@xxxxxxx