You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cocoon.apache.org by "Antonio Gallardo (JIRA)" <ji...@apache.org> on 2007/07/27 15:59:18 UTC
[jira] Closed: (COCOON-2097) Old excalibur-sourcereolve is still in
lib directory after r557984
[ https://issues.apache.org/jira/browse/COCOON-2097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Antonio Gallardo closed COCOON-2097.
------------------------------------
Resolution: Fixed
Assignee: Antonio Gallardo
Fixed. See: http://svn.apache.org/viewvc?view=rev&revision=560052
> Old excalibur-sourcereolve is still in lib directory after r557984
> ------------------------------------------------------------------
>
> Key: COCOON-2097
> URL: https://issues.apache.org/jira/browse/COCOON-2097
> Project: Cocoon
> Issue Type: Bug
> Components: * Cocoon Core
> Affects Versions: 2.1.11-dev (Current SVN)
> Reporter: Richard Frovarp
> Assignee: Antonio Gallardo
> Fix For: 2.1.11-dev (Current SVN)
>
>
> The old exaclibur-sourcereolve jar is still present, but no longer referenced in jars.xml. Several people using Lenya have had issues building due to this. Removing the offending jar fixes the issue. I see in r557984 the license was removed for the old version, and cocoon/branches/BRANCH_2_1_X/lib/core/excalibur-sourceresolve-2.1.jar was modified. It would appear that it should have been deleted instead.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.