[
https://issues.apache.org/jira/browse/DERBY-1671?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12462424
]
Andrew McIntyre commented on DERBY-1671:
----------------------------------------
> Is subversion going to care that a bunch of existing developers already have
> some other copy of junit.jar (different version, maybe?) in their tools/java?
I'm not entirely sure. If it were text, I know Subversion would 'merge' a new
file into your checkout if an identical file already existed in your checkout.
I don't know if the behavior is the same for binary files though. If you have
JUnit 3.8.1 in tools/java/junit.jar, then you will need to remove the old
junit.jar manually, since I'm planning on checking in JUnit 3.8.2.
At worst, you just need to remove the old junit.jar so that Subversion can copy
the new one into checkout. A minor inconvenience, I think, and future upgrades
to junit.jar could then be handled through svn.
At this point, I'm planning on making an announcement to the list on Monday,
and if nobody complains, checking it in first thing Tuesday. That should give
people running automated nightly builds plenty of time to make sure that their
builds are covered.
> Include junit.jar in Derby's svn to ease getting started for developers once
> ASF third-party licencing policy has been approved.
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-1671
> URL: https://issues.apache.org/jira/browse/DERBY-1671
> Project: Derby
> Issue Type: Task
> Components: Build tools
> Reporter: Daniel John Debrunner
> Assigned To: Andrew McIntyre
> Attachments: derby-1671-v1.diff
>
>
> *Draft* policy here indicates that CPL binaries can be added to Apache's SVN.
> http://people.apache.org/~cliffs/3party.html
> This is linked (redirected from)
> http://www.apache.org/legal/3party.html
> Need to check JUNit 3.8 is CPL.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
