Re: Maven plug-in for building extension description.xml files

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Re: Maven plug-in for building extension description.xml files

Rob Weir
On Wed, Nov 21, 2012 at 5:31 PM, Robert Barbey
<[hidden email]> wrote:
> Rob,
>
> thanks for the quick answer. Unfortunately, I wasn't talking about the Writer extension but about the Maven plug-in. It hasn't been decided yet whether the extension will be publicly available.
>
> Sorry for the confusion!
>

(cc'ing the API list, since they may be interested in this as well.)

Hi Robert,

OK. I get it now. So the audience for this would be OpenOffice
extension authors who use Maven.  But it is independent of Acrolinx.
It could be included our SDK, for example.

In that case, the requirements for source file headers are here:
http://www.apache.org/legal/src-headers.html

Package names would ideally be: org.apache.openoffice

-Rob

> Robert
>
>
> On Nov 21, 2012, at 10:37 PM, Rob Weir <[hidden email]> wrote:
>
>> On Wed, Nov 21, 2012 at 4:23 PM, Robert Barbey
>> <[hidden email]> wrote:
>>> Hi everyone,
>>>
>>> as I mentioned earlier on this list, I'm working on a Writer extension in Java. We're using Maven as a build tool and I wanted to let Maven generate description.xml and update.xml files based on the information in the POM. That's why I started writing a Maven plug-in that can do that.
>>>
>>> I convinced my CTO that it would be a good idea to donate this plug-in's sources once it's completed. I'd like to know what's necessary in terms of licensing. Is it sufficient to prepend a licensing statement to each source file or is more involved? Are they any formatting conventions I should know about? And what about package names?
>>>
>>
>> So two options:
>>
>> 1) Make your extension be open source at Apache, for distribution
>> within an OpenOffice release
>>
>> 2) Make it open source elsewhere, like on SourceForge, and distribute
>> it on our extensions website:  http://extensions.openoffice.org/
>>
>> Key insight is that for #2 you can have any license you want.  Of
>> course, we think the Apache License is a fine license.
>>
>> For #1 we'd want to first have a discussion on the list on what your
>> extension does and whether it makes sense to be part of the project.
>>
>> Regards
>>
>> -Rob
>>
>>
>>
>>> Thanks for your help!
>>>
>>> Best,
>>> Robert
>>>
>