[ http://issues.apache.org/jira/browse/XALANJ-2017?page=history ]
Brian Minchau resolved XALANJ-2017:
-----------------------------------
Resolution: Fixed
xalan.jar and xalansamples.jar were extracted from the distribution zip file
xalan-j_2_6_0-bin.zip. "-2.6.0" was added into their name, to follow the format
in the directory on minotaur, and .md5 files with a checksum were created using
the md5sum command on Linux.
This may yet be an issue but it is my ID, minchau, that owns the new files in
that directory, but most others are owned by the ID mdiggory, which is Mark R.
Diggory. So it may be that some ownership changes are needed.
> Put 2.6.0-jar in dist/java-repository/xalan/jars
> ------------------------------------------------
>
> Key: XALANJ-2017
> URL: http://issues.apache.org/jira/browse/XALANJ-2017
> Project: XalanJ2
> Type: Task
> Versions: 2.6
> Reporter: J�rgen Binningsb�
> Assignee: Brian Minchau
>
> The latest release of Xalan-J is not available in the java-repository at:
> http://www.apache.org/dist/java-repository/xalan/jars/
> and therefore it is, afaik, also not sync'ed to
> http://www.ibiblio.org/maven/xalan/jars/.
> Thus the latest release is not available to software projects built with
> Maven.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
