Issue 95477 - NetBeans Plug-in 2.0.3 : "Create OXT" deletes custom uno-manifest entries
Summary: NetBeans Plug-in 2.0.3 : "Create OXT" deletes custom uno-manifest entries
Status: ACCEPTED
Alias: None
Product: App Dev
Classification: Unclassified
Component: sdk (show other issues)
Version: 3.3.0 or older (OOo)
Hardware: All All
: P3 Trivial
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact: b.osi.ooo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-27 04:43 UTC by Ariel Constenla-Haile
Modified: 2013-02-24 20:55 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
the uno-manifest BEFORE "Create OXT" (780 bytes, text/xml)
2008-10-27 04:52 UTC, Ariel Constenla-Haile 		no flags Details
the uno-manifest AFTER "Create OXT" (633 bytes, text/xml)
2008-10-27 04:53 UTC, Ariel Constenla-Haile 		no flags Details
sample extension to reproduce (67.81 KB, application/x-compressed)
2008-10-27 04:54 UTC, Ariel Constenla-Haile 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description Ariel Constenla-Haile 2008-10-27 04:43:55 UTC 
with the new 2.0.0 version of the NB plug-in, if I have a uno-manifest like this:



<?xml version="1.0" encoding="UTF-8"?>
<manifest:manifest xmlns:manifest="http://openoffice.org/2001/manifest">
  <manifest:file-entry
manifest:media-type="application/vnd.sun.star.uno-typelibrary;type=RDB"
                       manifest:full-path="DialogComponent.uno.rdb"/>
  <manifest:file-entry
manifest:media-type="application/vnd.sun.star.uno-component;type=Java"
                       manifest:full-path="DialogComponent.uno.jar"/>
  <manifest:file-entry
manifest:media-type="application/vnd.sun.star.uno-typelibrary;type=Java"
                       manifest:full-path="DialogComponent_IDL_types.jar"/>
  <manifest:file-entry
manifest:media-type="application/vnd.sun.star.basic-library"
                       manifest:full-path="DialogComponent/"/>


</manifest:manifest>



choosing "Create OXT" will "reset" the uno-manifest, erasing the entry
for the basic library.
Comment 1 Ariel Constenla-Haile 2008-10-27 04:52:28 UTC 
Created attachment 57476 [details]
the uno-manifest BEFORE "Create OXT"
Comment 2 Ariel Constenla-Haile 2008-10-27 04:53:23 UTC 
Created attachment 57477 [details]
the uno-manifest AFTER "Create OXT"
Comment 3 Ariel Constenla-Haile 2008-10-27 04:54:54 UTC 
Created attachment 57478 [details]
sample extension to reproduce
Comment 4 steffen.grund 2008-10-27 11:23:54 UTC 
Accepted.
As a workaround: the plugin does not delete the entry, if there is a folder
named DialogComponent in your project root.
I guess that your basic library is in a different folder or sub-folder in your
project, am I right? Then the plugin assumes that the entry is invalid and
removes it. But that is a bug: Somehow the distinction between user entries and
entries made by the plugin does not work correctly here, user entries should
never be touched by the plugin.
Comment 5 Ariel Constenla-Haile 2009-01-28 14:12:38 UTC 
changed plug-in version in the summary, as this still happens in 2.0.3

arielch->sg: sorry I missed to answer you.
But no, I don't do anything special, and the basic library is inside the root
project folder, in a a folder named DialogComponent; so the workaround does not
work.
Comment 6 Ariel Constenla-Haile 2009-01-28 14:15:24 UTC 
> But no, I don't do anything special [...]

ups, I forgot I attached the project here. You can test it yourself, just unzip
DialogComponent.zip
Comment 7 steffen.grund 2010-02-12 16:05:35 UTC 
set target.