[
https://issues.apache.org/jira/browse/VELTOOLS-103?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980355#action_12980355
]
Christopher Schultz commented on VELTOOLS-103:
----------------------------------------------
Sure, I can make this into a patch, though it's just two entirely new files.
My library is not available through Maven, though I'd be happy to learn enough
Maven to tag it properly and shove it into a repo somewhere.
As for extras, I could certainly move the project there as well: should I
attach it to an existing project label, or create a new one? It's not exactly
tied to Velocity or Tomcat or any other existing Apache project. It's not
entirely clear how the apache-extras site is supposed to be used, and the FAQ
is a broken link :(
> ImportSupport really needs a unit test
> --------------------------------------
>
> Key: VELTOOLS-103
> URL: https://issues.apache.org/jira/browse/VELTOOLS-103
> Project: Velocity Tools
> Issue Type: Test
> Components: Test
> Affects Versions: 1.4, 2.0, 2.x
> Environment: All
> Reporter: Christopher Schultz
> Priority: Minor
> Attachments: VELTOOLS-103.zip
>
>
> ImportSupport needs a unit test.
> I wrote one a while ago, but it depends upon a (small) library that I wrote.
> I have since released that library under the Apache License V2.0 on
> SourceForge.net (http://sourceforge.net/projects/tuc). If the team is okay
> with including this library as a test-time dependency, I can submit a working
> unit test very quickly (just have to update it to 2.0-standards, if anything).
--
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]
