mahout-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Grant Ingersoll <gsing...@apache.org>
Subject Re: MAHOUT-104: Taste Web
Date Wed, 04 Feb 2009 15:50:56 GMT
Because it's a WAR file, which is it's own artifact, separate from the  
jars and has it's own set of dependencies that the other pieces do not  
need.  Have a look at: http://www.sonatype.com/books/maven-book/reference/multimodule.html

-Grant

On Feb 4, 2009, at 10:34 AM, Sean Owen wrote:

> OK but why does this reasoning not imply we should separate out any of
> the other components in Mahout -- why is this piece better as an
> artifact but nothing else is? I am not getting why it's special... I
> am sure I would not have a problem with it as long as I understand the
> logic and therefore feel confident we're setting this up the right
> way.
>
> On Wed, Feb 4, 2009 at 3:32 PM, Grant Ingersoll  
> <gsingers@apache.org> wrote:
>> B/c a POM describes an artifact.  Currently, we have what amounts to
>> multiple artifacts under one source tree.  By separating them out,  
>> it just
>> makes it easier to manage the artifacts.  It can be done the other  
>> way, but
>> it requires more work, whereas the separate tree way just requires  
>> some SVN
>> move commands and a little copy and paste.
>>
>> At least, that is my understanding of Maven.
>>
>> On Feb 4, 2009, at 10:22 AM, Sean Owen wrote:
>>
>>> ...and why is that?
>>>
>>> On Wed, Feb 4, 2009 at 3:16 PM, Grant Ingersoll  
>>> <gsingers@apache.org>
>>> wrote:
>>>>
>>>> B/c otherwise I need to write custom handling for Maven to  
>>>> separate them
>>>> out
>>>> from the various source trees.
>>
>>
>>


Mime
View raw message