Sure, The structure of the war is like this:
src -main --webapp ---admin ---css ---html ---images ---js ---WEB-INF ----conf -----axis2.xml ----modules -----addressing-1.3.mar -----rahas-1.3.mar -----rampart-1.3.mar -----soapmonitor-1.3.mar -----modules.list ----web.xml So the mar files are manually added as files under WEB-INF instead of being a Maven dependency artifact. -Dave On Sat, Jan 10, 2015 at 4:09 AM, Andreas Veithen <[email protected]> wrote: > Hi Dave, > > Can you elaborate a bit more on what you mean by "Currently the build > has the mar files as resources in WEB-INF/modules of the war's root"? > > Andreas > > On Wed, Jan 7, 2015 at 7:51 PM, David Hoffer <[email protected]> wrote: > > We have an existing Ant build (EAR build) that has 4 existing Axis2 > modules > > (in WAR), one of those is Rampart (v1.3). How are these supposed to be > > integrated in a Maven build? Currently the build has the mar files as > > resources in WEB-INF/modules of the war's root but that doesn't seem > right > > as currently the build knows nothing about the dependencies of those mar > > files. > > > > Is there a way to add the mar files as dependencies and have maven > > automatically place the mar files at WEB-INF/modules and add each mar's > > dependencies? I need all of the dependencies in the ear's APP-INF/lib > > folder as our war is a skinny war that has no jars in it's lib folder. > > > > What is the standard way of doing this for mars in Maven? > > > > -Dave > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
