my choice #2 - a hack. I tried addint the following in soap monitor pom.xml
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-jar-plugin</artifactId>
<executions>
<execution>
<phase>process-classes</phase>
<goals>
<goal>jar</goal>
</goals>
<configuration>
<basedir>${pom.basedir}/target/classes</basedir>
</configuration>
</execution>
</executions>
</plugin>
works great! only problem is it has all the META-INF/module.xml and
other unnecessary stuff which will caus problems. So Robert, can you
please try using a maven-ant-plugin and use the ant jar task to build
a jar with just the minimal classes needed in it? Then we'd have to
integrate it into the distrribution.
thanks,
dims
On 7/27/07, robert lazarski <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> Going through the axis2 branch testing stuff that I use and I noticed
> that when we moved to maven2, we lost axis2-soapmonitor-1.2.jar . The
> soapmonitor appears unique in axis2 in that there was both a jar
> produced and a mar. The jar contains the compiled applet classes, so
> the end user doesn't have to compile them themselves, and more
> importantly the servlet classes needed to run it.
>
> Best I can tell maven2 doesn't support 2 artifacts from one project. I
> see 2 solutions here:
>
> 1) Create a separate project for the jar.
> 2) Some type of hack.
>
> Feedback appreciated,
> Robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Davanum Srinivas :: http://davanum.wordpress.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
