Thursday, September 6, 2018, 6:27:34 PM, Ben Jackson wrote:
> BTW,
>
> The naming convention for maven plugins is either 'maven-XXX-plugin' if
> supported by the maven team or 'XXX-maven-plugin' for all other plugins;
> this why Mark originally named it freemarker-maven-plugin. See
> https://maven.apache.org/guides/plugin/guide-java-plugin-development.html
>
> So someone looking for this plugin will almost certainly default to
> searching for "freemarker-maven-plugin" so it is possible that the existing
> name is the superior choice.
I think they will just search the web for `freemarker maven plugin`,
and not `freemarker-maven-plugin`. So if the thing is called, for
example, "FreeMarker Generator Maven Plugin", it will be still a top
hit (especially if someone also looks for "generating" source code
with FreeMarker). And then the directory can be
"freemarker-generator", not the overly generic "freemarker" (which can
lead to some confusion, like people put their e-mail templates there,
instead of /src/resources/freemarker/).
But it's not like I want to drag this too long. Either one is
acceptable to me. So, guys, care for a totally informal vote? (We can
do a formal one in case no consensus reached soon.)
I prefer ("Offical name" (artifact-name; src/directory-name):
A "Apache FreeMarker Maven Plugin"
(freemarker-maven-plugin; src/freemarker)
B "Apache FreeMarker Generator Maven Plugin"
(freemarker-generator-maven-plugin; src/freemarker-generator)
C "Apache FreeMarker File Generator Maven Plugin"
(freemarker-file-generator-maven-plugin; src/freemarker-file-generator)
D Something else (please provide the name)
I vote for B.
> -Ben
>
>
> On Thu, Sep 6, 2018 at 11:14 AM Ben Jackson <[email protected]> wrote:
>
>> Here is the existing codebase for this project.
>>
>> https://github.com/yahoo/freemarker-maven-plugin
>>
>> It seemed more straightforward to work through our opensource team to
>> publish the code so that it could be reviewed before continuing this
>> conversation. Please comment on any remediations you see as needed (if
>> any) before working towards gifting this code to the apache foundation as a
>> starting point for this plugin.
>>
>> Also, as mentioned in the conversation above, it would be preferable if
>> this plugin had a unique and easily searchable name. Does anyone have
>> ideas?
>> I have no good ideas; here are some uninspired options:
>>
>> FreeGenerator
>> FMGenerator
>> FMGen
>> fmg
>> fmgen
>> FMarkerGen
>> MarkerGen
>> MGen
>> MGenerator
>>
>>
>> On Mon, Aug 20, 2018 at 10:05 AM Woonsan Ko <[email protected]> wrote:
>>
>>> On Mon, Aug 20, 2018 at 10:15 AM, Daniel Dekany <[email protected]>
>>> wrote:
>>> ...snip...
>>> > Without an ASF account the contributors couldn't edit the Wiki page.
>>> > If *they* open a JIRA issue, then we all can edit it. So that's what I
>>> > recommend.
>>> Makes sense to me. We can wait for Ben/Mark to create a JIRA ticket
>>> and we can edit its description together there.
>>>
>>> ...snip...
>>> > This was my intent from the beginning. A generator file can be a
>>> > .json, or an .ftl[h|x] (or whatever we come up with later, like an xml
>>> > that's transformed by a templates/myxmltransformat.ftl). They are
>>> > totally unrelated, independent generator files. I have never assumed
>>> > that they come in pairs, hence there was never a such thing as "ftl
>>> > only generator" in my head either. All generator files are lonely.
>>> That's clear now. I think I made an unnecessary confusion by using
>>> 'ftl-only' generator when mentioning .ftl type generator.
>>> Thanks!
>>>
>>> Woonsan
>>>
>>
>>
>> --
>> Benjamin Grant Jackson
>>
>
>
--
Thanks,
Daniel Dekany
