| Plugin.xml and Manifest.mf [message #314487] |
Sat, 14 April 2007 20:06  |
Eclipse User |
|
|
|
I have made changes to the manifest.mf file, which changes the plugin.xml
but for some reason I see these as separate files in the Package Explorer.
The plugin.xml file has an older subversion version, but since I altered the
source in the manifest.mf file, it is marked as a file that has changed.
However, subversion indicates that it is locked and refuses to send the
thing up.
Can I DELETE the plugin.xml file that is shown separately from manifest.mf?
Or will this blow away the manifest?
|
|
|
|
|
| Re: Plugin.xml and Manifest.mf [message #314492 is a reply to message #314489] |
Sun, 15 April 2007 14:16  |
| Eclipse User |
|
|
|
The problem is that I have made changes, and the subversion repository
thinks plugin.xml has a lock on it. Thus, while the manifest.mf file gets
committed successfully, plugin.xml does NOT update. Primarily this is a
subversion issue but I wondered if the manifest.mf would stay intact if I
deleted plugin.xml - the answer is NO.
Thanks.
On 4/15/07 1:32 AM, in article evskdo$3mh$1@build.eclipse.org, "Walter
Harley" <wharley@bea.com> wrote:
> "J Michael Dean" <mdean77@comcast.net> wrote in message
> news:C246C8B9.1F408%mdean77@comcast.net...
>> I have made changes to the manifest.mf file, which changes the plugin.xml
>> but for some reason I see these as separate files in the Package Explorer.
>> The plugin.xml file has an older subversion version, but since I altered
>> the
>> source in the manifest.mf file, it is marked as a file that has changed.
>> However, subversion indicates that it is locked and refuses to send the
>> thing up.
>>
>> Can I DELETE the plugin.xml file that is shown separately from
>> manifest.mf?
>> Or will this blow away the manifest?
>
>
> The plugin.xml and manifest.mf files are separate, and serve separate
> purposes. They are both edited by the same editor in PDE, however. So
> depending on what you change in the manifest editor, either or both files
> may change. (Also, the build.properties and .classpath files might change.)
>
>
|
|
|
| Re: Plugin.xml and Manifest.mf [message #314493 is a reply to message #314492] |
Sun, 15 April 2007 14:59 |
| Eclipse User |
|
|
|
Problem was lock in repository and the Subclipse plugin has no way to force
an unlock, so this had to be done from command line in SVN. Sorry for the
confusion.
On 4/15/07 12:16 PM, in article C247C837.1F478%mdean77@comcast.net, "J
Michael Dean" <mdean77@comcast.net> wrote:
> The problem is that I have made changes, and the subversion repository
> thinks plugin.xml has a lock on it. Thus, while the manifest.mf file gets
> committed successfully, plugin.xml does NOT update. Primarily this is a
> subversion issue but I wondered if the manifest.mf would stay intact if I
> deleted plugin.xml - the answer is NO.
>
> Thanks.
>
>
> On 4/15/07 1:32 AM, in article evskdo$3mh$1@build.eclipse.org, "Walter
> Harley" <wharley@bea.com> wrote:
>
>> "J Michael Dean" <mdean77@comcast.net> wrote in message
>> news:C246C8B9.1F408%mdean77@comcast.net...
>>> I have made changes to the manifest.mf file, which changes the plugin.xml
>>> but for some reason I see these as separate files in the Package Explorer.
>>> The plugin.xml file has an older subversion version, but since I altered
>>> the
>>> source in the manifest.mf file, it is marked as a file that has changed.
>>> However, subversion indicates that it is locked and refuses to send the
>>> thing up.
>>>
>>> Can I DELETE the plugin.xml file that is shown separately from
>>> manifest.mf?
>>> Or will this blow away the manifest?
>>
>>
>> The plugin.xml and manifest.mf files are separate, and serve separate
>> purposes. They are both edited by the same editor in PDE, however. So
>> depending on what you change in the manifest editor, either or both files
>> may change. (Also, the build.properties and .classpath files might change.)
>>
>>
>
|
|
|
Powered by
FUDForum. Page generated in 0.03390 seconds
Home