Am Samstag, 14. Januar 2012 schrieb Andrew Rist <andrew.r...@oracle.com>:
> Sounds good - I'll wait for a day or so to see if there are any alternate
opinions, then go for it...
> A.
>
> On 1/13/2012 4:16 PM, Carl Marcum wrote:
>>
>> Hi Andrew,
>>
>> On 01/13/2012 12:08 PM, Andrew Rist wrote:
>>>
>>> Where should we check it in? If there is a consensus on the location,
>>> I'll check it in and change the headers...
>>>

after the discussion the last days I am not sure if we should put it under
trunk or better besides trunk. People who want it check the sources
necessary to build the office only would checkout trunk. If we put it also
under trunk people would check these things too and would probably never
build it.

I am fine with devtools and the plugin already have the name
ooonetbeansintegration or so. I have to check it ...

Juergen

>>> A.
>>>
>>
>> The original discussion is here [1].
>>
>> I think the proposal is to start something beside 'trunk' like
'devtools' since it won't be included with OOo source.
>>
>> I think we should put it's own directory under 'devtools' like
'netbeans' since there will probably be similar plugins in the future like
'eclipse', etc.
>>
>> [1]
http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201111.mbox/%3C4ED5FF8D.4050708%40googlemail.com%3E
>>
>> Thanks,
>> Carl
>>
>>> On 1/13/2012 12:24 AM, Jürgen Schmidt wrote:
>>>>
>>>> Hi Carl,
>>>>
>>>> thanks for the reminder, I will work with Andrew on this and we can
>>>> hopefully provide the sources asap.
>>>>
>>>> But the plugin will need some maintenance work ;-)
>>>>
>>>> Juergen
>>>>
>>>> On 1/13/12 12:54 AM, Carl Marcum wrote:
>>>>>
>>>>> Hi all,
>>>>> I've seen mentioned in another thread, the OOo NetBeans plugin was to
be
>>>>> part of the SGA, but not yet available. Does anyone know the status of
>>>>> the code, or when we should see it?
>>>>>
>>>>> Best regards,
>>>>> Carl
>>>>
>>>
>>
>
> --
>
> Andrew Rist | Interoperability Architect
> OracleCorporate Architecture Group
> Redwood Shores, CA | 650.506.9847
>
>

Reply via email to