axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andreas Veithen (JIRA)" <>
Subject [jira] [Commented] (AXIS2-5413) build.xml is missing in source distribution at package root directory
Date Sun, 09 Sep 2012 17:22:08 GMT


Andreas Veithen commented on AXIS2-5413:

The current build setup solves the bootstrap problem by using versions of the AAR and MAR
plugins from a previous Axis2 release. For us that is not a problem because we don't have
the same constraints as you. I guess that you cannot use the same approach because RPMs for
previous Axis2 versions don't exist and/or you cannot use an RPM from a previous version in
the build of the current version.

Therefore you need to do two things:

1. Patch modules/parent/pom.xml to change the versions of axis2-mar-maven-plugin and axis2-aar-maven-plugin
in the pluginManagement section (to use ${project.version} instead of 1.5.2).
2. Build axis2-mar-maven-plugin and axis2-aar-maven-plugin before running mvn-rpmbuild, pretty
much as described in README.txt and implemented in build.xml. However, instead of trying to
use build.xml, I would recommend to integrate these steps into your build script.
> build.xml is missing in source distribution at package root directory
> ---------------------------------------------------------------------
>                 Key: AXIS2-5413
>                 URL:
>             Project: Axis2
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.6.1, 1.6.2
>         Environment: fedora 17
>            Reporter: Hiroaki Kawai
>            Priority: Critical
>              Labels: build
>         Attachments: axis2-trunk.patch
> In the subversion repository, build.xml exists at the package root directory. But in
source distribution, there is not. This seems causing bad results in fedora package builds
> The spec file does remove the modules that fails in building without ant. Most of the
modules (classes) are excluded from axis2 package, and this is not an unwanted package.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message