Almost,

I've got 5 core modules.
1 war module which depends on all the cores. The src directory for the war
contains jsr 181 pojo endpoints, which all refer to core code.

I'm using wsconsume and wsprovide (Jboss tools) to generate the client code.
One of the requirements for the tool is that you give it a directory of
classes (a source dir).

So the trick if I want to separate this into two projects, I need to figure
away for both projects to have the same source dir.




On 9/6/07, Dan Tran <[EMAIL PROTECTED]> wrote:
>
> best practice is to break them up as much as you can so that you will
> have one build artifact per module.
>
> I my case which i use jaxws and here are my modules:
>
>   core
>   ws-client   depends on core
>   ws-server  depend on core
>   webapp   depend on core and ws-server
>
> note both ws-client and ws-server are generated from core classes.
>
> are your structures similar to this?
>
> -D
>
> On 9/6/07, Sebastian Johnck <[EMAIL PROTECTED]> wrote:
> > Hello,
> > I currently have a war project (containing web services) in which I'm
> > generating a client.jar, containing client code, to include in the war.
> > I'm generating client code into generated-sources folder and then using
> the
> > jar plugin to create the client.jar, and place it in the web resources
> > directory before war packaging.
> >
> > Would maven encourage that I use two projects for this type of case? How
> > would I do this if the source directories for both projects are the
> same?
> >
> > Thanks ahead of time.
> > z
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Sebastian Johnck
(415) 425 - 8361

~~~~~~~~~~~~~~~~~~~
MotionBased Technologies
180 Harbor Dr.
Sausalito, CA 94965
www.motionbased.com
Coordinates:
N    37° 51' 33"
W 122° 29' 08"
~~~~~~~~~~~~~~~~~~~

Reply via email to