[
https://issues.apache.org/jira/browse/XMLBEANS-544?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16936800#comment-16936800
]
Andrey ``Bass'' Shcheglov commented on XMLBEANS-544:
----------------------------------------------------
Well, in this case I would either
* drop all command line utilities and mention the fact of their removal in the
release notes (documenting the migration path for version 2.x users would also
make sense), or
* change the classpath in the corresponding scripts, especially since the fix
is trivial.
Otherwise you're releasing a piece of software which is inconsistent.
> Command-line utilities rely on nonexistent xbean.jar file
> ---------------------------------------------------------
>
> Key: XMLBEANS-544
> URL: https://issues.apache.org/jira/browse/XMLBEANS-544
> Project: XMLBeans
> Issue Type: Bug
> Components: Tools
> Affects Versions: Version 3.1.0
> Environment: Linux unit-725.msk.labs.intellij.net 4.9.0-8-amd64 #1
> SMP Debian 4.9.110-3+deb9u4 (2018-08-21) x86_64 GNU/Linux
> Reporter: Andrey ``Bass'' Shcheglov
> Priority: Major
> Labels: easyfix
>
> I've downloaded the 3.1.0 binary release, and all command-line utilities
> appear broken, as they rely on {{$XMLBEANS_LIB/xbean.jar}},
> {{$XMLBEANS_LIB/xmlbeans-qname.jar}} and {{$XMLBEANS_LIB/jsr173_1.0_api.jar}}
> files, none of which is available any more.
> The listing of my {{lib/}} directory is as follows:
> * resolver.jar
> * xmlbeans-3.1.0.jar
> * xmlbeans-3.1.0-javadoc.jar
> * xmlbeans-3.1.0-sources.jar
>
> Symlinking {{xmlbeans-3.1.0.jar}} to {{xbean.jar}} allows to work the problem
> around, but it seems impossible noone has tested any of the tools before
> making a release.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
