| Why is "permissions.properties" not supported anymore in Eclipse 3.4 Ganymede? [message #25245] |
Mon, 06 October 2008 12:05  |
Eclipse User |
|
|
|
Hi all!
I am trying to deliver with my plugin some executables (in an OS dependant
plugin fragment). After plug-in installation the executables are do not
have the executable bit set, therefore one has to change them manually.
In Eclipse 3.3 we had two solutions for this:
1. Use a permission.properties in the fragment where the executables were
with the following content:
permissions.executable=<the list of executable files (only one in our
case)>
2. Provide a custom installation handler to the feature and change the
permissions of the executable in the completeConfigure() handler
Both solutions worked fine with 3.3 but in the Eclipse Ganymede (3.4)
version, none works anymore. Has anyone some more experience on this? How
can we make it run also on 3.4?
Thanks!
Gabriel
|
|
|
|
| Re: Why is "permissions.properties" not supported anymore in Eclipse 3.4 Ganymede? [message #26140 is a reply to message #25812] |
Mon, 13 October 2008 05:49  |
| Eclipse User |
|
|
|
In order for the p2.inf to work, one has to generate p2 metadata for the
update site. This will be stored (including the instructions provided in
the p2.inf file) in the content.xml file.
The example provided at does the job (You might have to work a little with
the parameter):
http://wiki.eclipse.org/Equinox_p2_Metadata_Generator
Unfortunatelly, the same example cannot be reproduced in an Ant build
script. The reason: the -site parameter is not provided by the p2.generate
ant task.
I found a workaround though (this workaround does not generate the
artifacts.xml file, that the example also generates. But for my purpose of
setting binary permissions, this works since the information will be
stored in the content.xml):
<target name="generate.metadata">
<p2.generator
append="false"
base="${basedir}"
bundles="${basedir}\plugins"
features="${basedir}\features"
metadatarepository="file:${basedir}"
metadatarepositoryname="My Repos Name"/>
</target>
If you provide also the artifacts repository you will get an error.
Regards,
Gabriel
|
|
|
| Re: Why is "permissions.properties" not supported anymore in Eclipse 3.4 Ganymede? [message #582472 is a reply to message #25245] |
Wed, 08 October 2008 10:58 |
| Eclipse User |
|
|
|
As I understand, the premissions.properties is replaces by the p2.inf file
that must be placed in the META-INF directory. As it was pointed to me,
more information about this can be found in this article:
http://wiki.eclipse.org/Equinox/p2/Engine/Touchpoint_Instruc tions
I have tried this but it still doesn't work with my Eclipse 3.4
Ganymede-SR1. In an attempt to see how the same thing is doen in the TPTP
plugins (more precise in: org.eclipse.tptp.platform.ac.linux_ia32_4.4.1) I
found no difference.
But when I installed the TPTP Platform plugin, many other plugins were
brought down and installed in my Ganymede (including some equinox
plugins). Then I tried one more time with my plugin and it worked.
Therefore, there is some dependency that is not available in the default
Ganymede distribution that enables the reading of the p2.inf file.
Does anybody know which is this dependency?
Thanks!
|
|
|
| Re: Why is "permissions.properties" not supported anymore in Eclipse 3.4 Ganymede? [message #582598 is a reply to message #25812] |
Mon, 13 October 2008 05:49 |
| Eclipse User |
|
|
|
In order for the p2.inf to work, one has to generate p2 metadata for the
update site. This will be stored (including the instructions provided in
the p2.inf file) in the content.xml file.
The example provided at does the job (You might have to work a little with
the parameter):
http://wiki.eclipse.org/Equinox_p2_Metadata_Generator
Unfortunatelly, the same example cannot be reproduced in an Ant build
script. The reason: the -site parameter is not provided by the p2.generate
ant task.
I found a workaround though (this workaround does not generate the
artifacts.xml file, that the example also generates. But for my purpose of
setting binary permissions, this works since the information will be
stored in the content.xml):
<target name="generate.metadata">
<p2.generator
append="false"
base="${basedir}"
bundles="${basedir}\plugins"
features="${basedir}\features"
metadatarepository="file:${basedir}"
metadatarepositoryname="My Repos Name"/>
</target>
If you provide also the artifacts repository you will get an error.
Regards,
Gabriel
|
|
|
Powered by
FUDForum. Page generated in 0.03172 seconds
Home