it's actually Shan ;)
just to generalize (not fully sure if this applies to your scenario), if you
want a WAR project to produce a JAR locally (within the /lib dir of the
webapp), you can use
<archiveClasses>true</archiveClasses>
to have the same/similar JAR actually be available as a consumable artifact
in other projects, you specify this
<attachClasses>true</attachClasses>
which should install it into your local repository if you call "install"
when building your WAR project
now, this set of classes is available to your other projects as a
dependency, but you need to specify "classes" as the classifier
for example, within another project;
<dependency>
<groupId>com....</groupId>
<artifactId>webapps-project</artifactId>
<version>???</version>
<classifier>classes</classifier>
</dependency>
On Fri, Jun 11, 2010 at 1:45 PM, Jesse Farinacci <[email protected]> wrote:
> Hi Starrman,
>
> On Fri, Jun 11, 2010 at 1:27 PM, Starrman <[email protected]> wrote:
> >
> > I actually am using common code in both projects... This was the
> > project that I referred to as the "myOverlayWebapp.war" project... I
> > am trying to use war overlays for the common web components and the
> > common classes.
>
> I guess I really don't understand the problem at all then. Any common
> code should be in some common module that is depended upon your war
> modules.
>
> > Do you see a reason why Syed's suggestion wouldn't work?
>
> I'm not familiar with the mechanism proposed by Syed. Try it and see.
>
> -Jesse
>
> --
> There are 10 types of people in this world, those
> that can read binary and those that can not.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
