[M2] multiple-artifacts

[Ca...@usitc.gov]

I am very new to maven and trying to wrap my head around how best to
port an existing ant based project to maven.

The project is a webservice layer for application.  The ant build
currently generates two artifacts:

- my-ws-client.jar.  Consists of WS interfaces, a few concrete classes
used only by the client and a client spring config file.
- my-ws.war.  Consists of WS interfaces, WS impls, server spring config
file and other config resources (e.g. web.xml etc)

Although maven strongly encourages a single primary artifact per
project, there is support for attached artifacts.  I normally see this
in reference to the ejb plugin.  However, there are archived emails that
mention registering the build-helper-maven-plugin and using it to
generate other associated artifacts.

Should I use these plugins to generate the client jar?  What is the best
way of doing that?

Or should I break this project into separate modules?

If I break them into separate modules I suspect that I will need three
modules:

1 - my-ws-client: classes and config files used by client only.
2 - my-ws: classes and config files used by the server only.
3 - my-ws-common: common classes, almost all interfaces, that the two
previous modules depend on.

Any help or reference to online docs/mail thread I have missed would be
appreciated.

Carlos.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [M2] multiple-artifacts

[Wayne Fay <wa...@gmail.com>]

Easiest is always to break into multiple modules as you've already outlined.

Wayne

On 5/23/06, Carlos.Fernandez@usitc.gov <Ca...@usitc.gov> wrote:
> I am very new to maven and trying to wrap my head around how best to
> port an existing ant based project to maven.
>
> The project is a webservice layer for application.  The ant build
> currently generates two artifacts:
>
> - my-ws-client.jar.  Consists of WS interfaces, a few concrete classes
> used only by the client and a client spring config file.
> - my-ws.war.  Consists of WS interfaces, WS impls, server spring config
> file and other config resources (e.g. web.xml etc)
>
> Although maven strongly encourages a single primary artifact per
> project, there is support for attached artifacts.  I normally see this
> in reference to the ejb plugin.  However, there are archived emails that
> mention registering the build-helper-maven-plugin and using it to
> generate other associated artifacts.
>
> Should I use these plugins to generate the client jar?  What is the best
> way of doing that?
>
> Or should I break this project into separate modules?
>
> If I break them into separate modules I suspect that I will need three
> modules:
>
> 1 - my-ws-client: classes and config files used by client only.
> 2 - my-ws: classes and config files used by the server only.
> 3 - my-ws-common: common classes, almost all interfaces, that the two
> previous modules depend on.
>
> Any help or reference to online docs/mail thread I have missed would be
> appreciated.
>
> Carlos.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org