Hello,
I'd need some more clarification in case I use module structure proposed:
does it mean I'd have in server/pom.xml as well as in client/pom.xml?
<dependencies>
<dependency>
<groupId>core-api</groupId>
<artifactId>core-api</artifactId>
<version>0.0.1-SNAPSHOT</version>
</dependency>
or something similar that would match name+version of core-api
I'd like to have automatically built core-api in case I do some
updates in it and then I build server or client module using:
mvn site (but in client or server module, not in the root one)
As for example, server developer doesn't need client to be built (as
it's quite time consuming), but needs only server and core-api.
Do you have any suggestion? Did I get it correctly or am I missing
some important point?
Thanks
Peter B.
On Wed, May 5, 2010 at 12:20 PM, Peter Butkovic <[email protected]> wrote:
> Hello,
>
> thanks for fast reply! I'll follow your proposal.
>
> Peter B.
>
>
> On Wed, May 5, 2010 at 10:42 AM, Karl Heinz Marbaise <[email protected]> wrote:
>>
>> Hi,
>>
>> i would suggest to create the following structure. Mor
>>
>>
>> pom.xml (root) (modules: client, server, core-api)
>> +---- client
>> +-- pom.xml (parent: root: dependency: core-api)
>> +---- server
>> +-- pom.xml (parent: root: dependeny: core-api)
>> +---- core-api
>> +-- pom.xml (parent: root)
>>
>>
>> The question about core-api is that you don't positioned core-api under
>> client nor under server, cause it's used by both so you have to put it on
>> the same level.
>>
>> Kind regards
>> Karl Heinz Marbaise
>> --
>> View this message in context:
>> http://old.nabble.com/maven-multi-module-project-structure-tp28457606p28458206.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
