[jbosstools-dev] Problem with org.jboss.tools.common.model.ui plugin

[Nick Boldt]

We should strive to have all our plugins deployed as jars, not 
folders... and within those jars, *no nested jars.*

This is an easy thing to change in the containing feature's feature.xml 
(set unpacked="false"), the plugin's build.properties (replace "foo.jar" 
with "."), and its MANIFEST.MF (replace "foo.jar" with ".").

N

On 03/30/2010 12:50 PM, Denis Golovin wrote:
> There is no reason for that, it just the same as it was from the
> beginning. We have no naming conventions for case like this.
>
> -Denis
>
> On 03/28/2010 11:27 AM, Andersen Max wrote:
>> Denis, any reason why we are using different named jars for unpacked/packed jars ?
>>
>> /max
>>
>> On Mar 26, 2010, at 19:40, Denis Golovin wrote:
>>
>>
>>> On 03/18/2010 07:24 AM, Jiri Peterka wrote:
>>>
>>>> Hi guys,
>>>>
>>>> I have following problem with JBT plug-in dependencies and hope you
>>>> could help me.  Simply I can't import
>>>> org.jboss.tools.common.editors.ObjectMultiPageEditor. This specific
>>>> issues is here since one of recent JBT (3.1) version.
>>>>
>>>> There are simple steps to reproduce.
>>>> 1. Have JBDS 3.0.0 GA or JBT 3.1 installed
>>>> 2. Create plugin to test this problem
>>>> 3. Import org.jboss.common.model.ui on Dependencies tab
>>>> 4. In plug-in dependencies (Package Explorer)
>>>> org.jboss.tools.common.model.ui is missing and for example
>>>> ObjectMultiPageEditor (org.jboss.tool.common.editor) can't be imported
>>>>
>>>>
>>>>
>>> It is here but name is model_ui.jar because it is deployed as unpacked.
>>>
>>> <moz-screenshot.png>
>>>
>>> You cannot import
>>> ObjectMultiPageEditor
>>> because it requires org.eclipse.ui.ide.IGotoMarker and you have to add org.eclipse.ui.ide plug-in to your plug-in dependencies because it is not reexported in common.ui plug-in.
>>>
>>> Denis
>>>
>>>> Strange is that plugin is here and I can see this plugin in Plug-in
>>>> registry, plugin can be added as dependency and it has exported packages
>>>> I needed but it's not present in Plug-In Dependencies (Package Explorer)
>>>> and can't be imported in the source code. In some earlier JBT 3.1 this
>>>> worked.
>>>>
>>>> Any help appreciated, regards
>>>>
>>>> --
>>>> Jirka
>>>> _______________________________________________
>>>> jbosstools-dev mailing list
>>>>
>>>> jbosstools-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>>
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> jbosstools-dev mailing list
>>> jbosstools-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>>
>>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
Release Engineer :: Eclipse Modeling & Dash Athena
http://nick.divbyzero.com