[
https://issues.apache.org/jira/browse/VELTOOLS-93?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731151#action_12731151
]
Mark Belling commented on VELTOOLS-93:
--------------------------------------
Wow, I'm stupidifounded: you've managed to write 1.5 annotations. How many
times has that bitten you in the ass? Six paragraphs on esoteric bugs you've
managed to write combined with your artificial complexity stroked through the
roof, I'm sure you're well on your way to a Java One conference touting a Java
Certification in your left hand, and your limp cock in the right. I'm not
interested in paying you to write even the simplest persistence layer, I'm
interested in you asking for help in writing something by a professional
programmer that has an interest in using the tools framework outside of
providing a file like it's 1999 or writing a clear API to provide simple
functionality in an oversaturated losing battle over sad brittle culture of big
dick mensa pride members.
> Missing infos on tools creation
> -------------------------------
>
> Key: VELTOOLS-93
> URL: https://issues.apache.org/jira/browse/VELTOOLS-93
> Project: Velocity Tools
> Issue Type: Improvement
> Components: Documentation
> Affects Versions: 2.0
> Environment: all
> Reporter: Claude Brisson
> Priority: Minor
> Fix For: 2.0
>
>
> (this is a reminder for Nathan or myself...)
> The documentation is lacking some infos on tools properties :
> 1) the "Creating Tools" page should explain the "configure"/"setXXX" mechanism
> 2) the "Web Framework Integration" (which should maybe be named "J2EE
> Integration" to avoid the ambiguous framework word) should list all standard
> properties that are set for every scope (setRequest,setVelocityContext...).
> (...and " grep TODO docs/* "...)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
