Hi all,
As adviced in the bugzilla, I'll ask the question here first before filing an issue.
I recently mirrorred some public repos and started playing with director to install some things from those mirrors and made a typo in the command.
I just noticed a (seems to me) very weird behaviour, here the typical command I was running :
eclipsec.exe -nosplash -verbose -application org.eclipse.equinox.p2.director.app.application \
-metadataRepository file:c:/doesnotexist \
-artifactRepository file:c:/neitherexist \
-installIU org.eclipse.platform.ide -destination c:/install_dest -profile PlatformSDKProfile -profileProperties org.eclipse.update.install.features=true -bundlepool c:/install_dest -roaming -vmargs -Declipse.p2.data.area=c:/install_dest/p2
As named above, if you point to this kind of directory that doesn't preexist. Director will seem to run fine and will create the directory c:/doesnotexist and also create the following content.xml inside this dir :
<?xml version='1.0' encoding='UTF-8'?>
<?metadataRepository class='org.eclipse.equinox.internal.p2.metadata.repository.LocalMetadataRepository' version='1.0.0'?>
<repository name='file:c:/doesnotexist - metadata' type='org.eclipse.equinox.internal.p2.metadata.repository.LocalMetadataRepository' version='1'>
<properties size='1'>
<property name='p2.timestamp' value='1221767914837'/>
</properties>
</repository>
IMO, it should just crash with the clearest possible message when it realizes the metadata or artifact directory/repository is absent, isn't it?
Should I file an issue about this?
Cheers.
--
Baptiste <Batmat> MATHUS -
http://batmat.netSauvez un arbre,
Mangez un castor !