That's interesting, and makes me want to vote for dashes going forward.
(I'll admit that I was thinking of testCompile when I wrote my plugin, to
the extent that I was thinking of anything at all.)
For the record, the offending camelCase goals are:
compiler:testCompile
resources:testResources
plugin:updateRegistry
plugin:addPluginArtifactMetadata
Is it possible to create an alias for a goal name (without making a
nearly-empty subclass, getting documented twice, etc.)? It'd be cool to
make "test-compile" be an alias for "testCompile".
-Dan
Benjamin Bentmann wrote:
Brett Porter wrote:
I would say the first one. The first goal I could think of to have this was
testCompile, so it probably set the precedent.
While it might have been the first goal, it's apparently not today's common
case. Browsing through the Apache plugins, I found only
- maven-compiler-plugin
- maven-resources-plugin and
- maven-plugin-plugin
to use camel case for goal names. The majority of existing goals from other
plugins use lower case with hyphens, so this seems like a de-facto standard.
Is it wise to break with that?
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
