Run "mvn clean install" from the root directory of the project. I used
Maven 3.6.3 and jdk1.8.0_211. I updated the README.txt file in git, thanks
for pointing that out.

You indicated you are failing the OSGi unit test with the source of 1.7.9 -
I couldn't get that far on my system as the integration test failed before
that.

The git repo of axis2 with xalan 2.7.2 and commons-fileupload 1.4, does
pass the unit tests.

For the source distro of 1.7.9 and passing "-Dmaven.test.skip.exec" to
maven, the path of the war after the build, is:

./modules/distribution/target/axis2-1.7.9/dist/axis2.war





On Mon, Nov 23, 2020 at 11:23 PM Jipa, Alexandru-Stefan <
[email protected]> wrote:

> Hi,
>
>
>
> And after we successfully compile axis2, what do we need to do in order to
> generate axis2.war file?
>
>
>
> Thanks,
>
> Stefan Jipa
>
>
>
> *From:* robertlazarski <[email protected]>
> *Sent:* Tuesday, November 24, 2020 1:31 AM
> *To:* [email protected]
> *Subject:* [EXT] Re: Axis2 status (release)
>
>
>
> I figured out the OSGi problem, the fix below should allow you to build
> with the jar update.
>
>
>
> The goal for the next axis2 release continues to be JDK 11 compilation. We
> are looking at early next year for the next release.
>
>
>
> For now, JDK 8 is required for compilation though I have had no problems
> running my projects on JDK 11.
>
>
>
> ./modules/osgi-tests/src/test/java/OSGiTest.java
>
>
>
>                 // commons-fileupload 1.4 changed the MANIFEST.MF file
> from:
>                 // Bundle-SymbolicName: org.apache.commons.fileupload
>                 // to:
>                 // Bundle-SymbolicName:
> org.apache.commons.commons-fileupload
>
> url("link:classpath:org.apache.commons.commons-fileupload.link"),
>
>
>
>
> On Sun, Nov 22, 2020 at 10:48 PM Jipa, Alexandru-Stefan <
> [email protected]> wrote:
>
> Hi,
>
>
>
> Do you have any news for the axis2 status? Will it be a release in the
> following period? (with xalan 2.7.2 and commons fileupload 1.4)
>
> And one more think, can you tell us the required steps to generate the
> axis2.war file, like the one from
> https://axis.apache.org/axis2/java/core/download.html
> <https://eur02.safelinks.protection.outlook.com/?url=https%3A%2F%2Faxis.apache.org%2Faxis2%2Fjava%2Fcore%2Fdownload.html&data=04%7C01%7CAlexandruStefan.Jipa%40finastra.com%7Cc4becaa37848428bf69508d89007eef4%7C0b9b90da3fe1457ab340f1b67e1024fb%7C0%7C0%7C637417711045345801%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=t%2BRE5XUqNWBOGWdcXQ%2BsWl2ZiI%2BNyoNasnJoQKv94eE%3D&reserved=0>
> ?
>
>
>
> We tried to compile axis2 1.7.9 with xalan 2.7.2 and commons fileupload
> 1.4 but we get a failed test: Apache Axis2 - OSGi Tests generated
>
> by commons fileupload 1.4. We tried to upgrade commons io to 2.2, as it is
> a dependcy for fileuload 1.4, but we got the same failed test.
>
>
>
> Axis2 1.7.9 does compile successfully only with xalan 2.7.2 (with maven 3,
> not 2 as it says in readme (outdated maybe?) ), but after this
>
> what do he have to do to generate the axis2.war file?
>
>
>
> 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.
>
> "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.
>

Reply via email to