About dropping in new versions of commons-fileupdate and xalan into your webapp for example ... sure, I'd expect no problems.
On Fri, Sep 11, 2020 at 5:01 AM robertlazarski <robertlazar...@gmail.com> wrote: > Go ahead and create a Jira issue for Axis2, and list the jar's you'd like > updated. > > I tried to upgrade commons-fileupload about a week ago actually. I ran > into problems with our OSGI module since it bundles some specific versions. > I'll be looking more into that soon. > > The goal for the next release is JDK 11 compilation, by the end of the > year. I'm currently trying to figure out why saaj isn't loading properly in > our adb-tests module. > > Robert > > > > > > On Fri, Sep 11, 2020 at 1:09 AM Jipa, Alexandru-Stefan < > alexandrustefan.j...@finastra.com> wrote: > >> Hi, >> >> >> >> I want to log a ticket on https://issues.apache.org/jira regarding Axis2 >> version and it`s included libs. >> >> I see that axis2-1.7.9 it is the latest version (from 2018, as well as >> other previous versions 1.7.8 and 1.7.7 I think). >> >> The current axis2 (1.7.9) includes commons-fileupload-1.3.3.jar and >> xalan-2.7.0.jar but we need to update to >> >> the latest version of these jar files: commons-fileupload-1.4.jar and >> xalan-2.7.2.jar . >> >> >> >> So should I log the Issue Type as an Improvement or bug ? Also the >> project is Axis2 ? (I see there exists a lot of apache projects, >> >> even common fileupload or xalan). >> >> >> >> If you have any information about this, how often/what triggers a new >> version of axis2? >> >> >> >> And as an alternative, in case it will take a long time before a new >> version of axis2, is it safe to update in axis2-1.7.9 >> >> the jar files for commons-fileuload and xalan to the latest version? And >> if yes, it is ok only to copy the latest jars or >> >> to the download the source code from >> http://commons.apache.org/proper/commons-fileupload/download_fileupload.cgi >> >> and compile it? >> >> >> >> Thanks, >> >> >> >> Stefan Jipa >> >> >> "FINASTRA" is the trade name of the FINASTRA group of companies. This >> email and any attachments have been scanned for known viruses using >> multiple scanners. This email message is intended for the named recipient >> only. It may be privileged and/or confidential. If you are not the named >> recipient of this email please notify us immediately and do not copy it or >> use it for any purpose, nor disclose its contents to any other person. This >> email does not constitute the commencement of legal relations between you >> and FINASTRA. Please refer to the executed contract between you and the >> relevant member of the FINASTRA group for the identity of the contracting >> party with which you are dealing. >> >
