[ https://jira.codehaus.org/browse/MSANDBOX-51?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=275846#comment-275846 ]
Mark Struberg commented on MSANDBOX-51: --------------------------------------- I think I've touched 5 classes yet and 4 of them are clearly forked from ASF projects and still 90% of that code remaining. Check this locations for obvious hits: * http://maven.apache.org/maven-1.x/xref/org/apache/maven/util/ * http://svn.apache.org/repos/asf/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/ * http://svn.apache.org/repos/asf/ant/core/trunk/src/main/org/apache/tools/ant/taskdefs/condition/ * http://svn.apache.org/repos/asf/commons/proper/exec/trunk/src/main/java/org/apache/commons/exec/ Of coure, sometimes you also have to grab back into the CVS archive. A good indicator is the @author tag. Commons dropped that around 2004, but plexus-utils most times still have them. An example: All classes with @author Stefan Bodewig are most certainly 1:1 forks from Ant. > Rewrite Plexus Utils classes at the ASF from scratch > ---------------------------------------------------- > > Key: MSANDBOX-51 > URL: https://jira.codehaus.org/browse/MSANDBOX-51 > Project: Maven 2.x Sandbox > Issue Type: New Feature > Reporter: Mark Struberg > > plexus-utils are 85% written by ASF committers, but we still don't have a IP > cleared history. > For cleaning this up we aim to rewrite those classes from scratch in ASF > maven sandbox. > The strategy is the following: > 1. create unit tests for the existing plexus classes > 2. create a new implementation from scratch > 3. the new implementation must be a binary API compatible drop-in replacement -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira