Hi Bob,

On Mon, Mar 8, 2010 at 8:09 AM, Bob Aiello <[email protected]> wrote:
>
> I just wrote an article on tactics for refactoring the Maven build and I
> would love to get your input.
> http://www.cmcrossroads.com/cm-basics/13317-refactoring-the-maven-build
>
> Feel free to post comments or send them to me privately.
>
> Bob Aiello
> Editor in Chief
> CM Crossroads
> http://www.linkedin.com/in/BobAiello
> raiello [at] acm.org
>

Well, you seem to be a manager and not a technical developer, so I'll
go easy on you. Your article is definitely filled with the right buzz
words, they just don't seem to be used appropriately. The title,
Refactoring the Maven Build, suggests that there will be some sort of
detail provided on how to refactor the Maven pom.xml, but there aren't
any details on this at all.

Tip # 1 - Using help:effective-pom to diagnose problems is good
Tip # 2 - Understanding what is going on in the build is generically useful
Tip # 3 - Adding tracing to Maven itself isn't going to be useful to
any reader unless you provide your changes, please do not
Tip # 4 - Declaring dependencies in a clear and consistent way? What
does this even mean? Being a correct, well-formed XML document will
see to that..
Tip # 5 - There's so much wrong in this one I don't know where to
start ... please just delete it
Tip # 6 - This is the likely result of your misunderstanding Maven,
and switching the packaging type from jar to war without ever cleaning
out the .m2/repo and/or without changing the artifact's version -
tsk-tsk on you!
Tip # 7 - Anyone that has written a plugin for Maven, even a
HelloWorldMojo, is going to be of a higher caliber Maven user than
you.. telling them to 'optimize' their plugins isn't at all valuable
or useful
Tip # 8 - Here, you seem to have digressed from the original thesis;
are you speaking about a Maven Repository Manager? It's unclear, and
worse still, you provide no details about what you're trying to fix,
or how you recommend fixing it
Tip # 9 - This is a non-issue if you are using well defined best
practices for software development - by this I mean using actual
versions and tagging your source code version control system
appropriately during a release; any deployed artifact should be
recreatable
Tip # 10 - This seems like more buzz word jumbo, I'm not sure I see
any tip here at all

I'm sorry if I'm being harsh, but this really isn't going to be a
valuable contribution. You don't even link to where you can get more
information about Maven, or where much better resources may be found
(e.g. http://www.sonatype.com/products/maven/documentation/book-defguide
)

-Jesse

-- 
There are 10 types of people in this world, those
that can read binary and those that can not.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to