Within the project I am working we're using maven to handle dependencies. However we're getting issues with the apache rampart the industry security module to Axis2. We've attempted to make use of the next dependencies tags:

	<dependency>
		<groupId>org.apache.rampart</groupId>
		<artifactId>rampart</artifactId>
		<version>1.3</version>
		<type>mar</type>
	</dependency>

	<dependency>
		<groupId>org.apache.rampart</groupId>
		<artifactId>rampart</artifactId>
		<version>1.4</version>
		<type>mar</type>
	</dependency>

Ultimately that maven is not able to discover a quantity of assets which are incorporated as dependencies within the rampart pom files (observe that the rampart pom files are downloaded instantly by maven, and so i wasn't designed to edit individuals files).

When go into the URI of the rampart dependency that maven was not able to discover I recieve a 404 error. It appears like this apache rampart pom files are damaged...

Has someone effectively used rampart with maven? Could it be the apache rampart integration with maven damaged?

I simply had this issue and located a workaround. Rather than adding the rampart depedency, add all libs within the rampart standard dist, i.e:

    <dependency>
        <groupId>org.apache.rampart</groupId>
        <artifactId>rampart-core</artifactId>
        <version>1.4</version>
        <exclusions>
            <exclusion>
                <groupId>bouncycastle</groupId>
                <artifactId>bcprov-jdk15</artifactId>
            </exclusion>
            <exclusion>
                <groupId>opensaml</groupId>
                <artifactId>opensaml</artifactId>
            </exclusion>
            <exclusion>
                <groupId>org.apache.santuario</groupId>
                <artifactId>xmlsec</artifactId>
            </exclusion>
        </exclusions>
    </dependency>

    <dependency>
        <groupId>org.bouncycastle</groupId>
        <artifactId>bcprov-jdk15</artifactId>
        <version>1.44</version>
    </dependency>
    <dependency>
        <groupId>org.opensaml</groupId>
        <artifactId>opensaml</artifactId>
        <version>1.1</version>
    </dependency>
    <dependency>
        <groupId>org.apache.santuario</groupId>
        <artifactId>xmlsec</artifactId>
        <version>1.4.3</version>
    </dependency>

Note: I up-to-date a few of the version from the rampart standard dist since a number of them were not within the maven repository.

That the large problem due to .marly packaging, I truly hate this way axis2 project had decide to work, anyway you will get this working adding rampart-*.marly and all sorts of needed *.mar's to

WEB-INF/lib 

folder, you will need to create that folder whether it does not exist.

And manage other dependencies the standard way maven would do, something similar to:

org.apache.rampart rampart-core 1.4

<dependency>
    <groupId>org.apache.axis2</groupId>
    <artifactId>axis2-kernel</artifactId>
    <version>1.4.1</version>
</dependency>