You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mahout.apache.org by "Karl Wettin (JIRA)" <ji...@apache.org> on 2008/03/15 23:16:33 UTC
[jira] Updated: (MAHOUT-17) Maven support
[ https://issues.apache.org/jira/browse/MAHOUT-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Wettin updated MAHOUT-17:
------------------------------
Attachment: pomification_hama.diff
pomification.diff
Current trunk has been moved to the new module 'core' that contains a pom.xml pointing back at the new super project in the trunk root. There is also an intermediate contrib/pom.xml, and there is an alternative patch where Hama is a contrib module. (I don't say Hama belongs in contrib and not in core, it was just a way great way for me to extend the build files.)
http://people.apache.org/~kalle/mahout/maven2/
This is a repository to wich I have added all dependencies available in trunk/lib. All snapshots are todays revision, built on my laptop.
I have also choosen short names for modules not already available in repo1. core rather than hadoop-core, and core rather than mahout-core, but in different groups.
{noformat}
./org/apache/hadoop/core/0.17.0-SNAPSHOT
./org/apache/hadoop/hbase/0.2.0-SNAPSHOT
./commons-cli/commons-cli/2.0-SNAPSHOT
./libthrift/libthrift/r746
./org/kosmix/kosmosfs/komsosfs/0.1
./jetty/jetty/5.1.4
{noformat}
mvn idea:idea in the trunk root creates a multimodule project that I can open and pass all tests in. But it also creates modules for the intermediate projects without code...
I added all this info in the root pom, but mvn site:site does not seem to use it? I thought, maybe it would be fun to see if it looks nice. I will try some more before I remove it.
There should be some properties for versions and such. And speaking of versions, I see it is 0.1 in Jira, but my patches are 0.0.1.
How do you feel about going to Maven all the way like this? I call for a vote!
> Maven support
> -------------
>
> Key: MAHOUT-17
> URL: https://issues.apache.org/jira/browse/MAHOUT-17
> Project: Mahout
> Issue Type: Improvement
> Affects Versions: 0.1
> Reporter: Karl Wettin
> Assignee: Karl Wettin
> Priority: Minor
> Attachments: pomification.diff, pomification_hama.diff
>
>
> The trunk is a Maven module root. I think it should be refactored to a Maven project root.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
Re: [jira] Updated: (MAHOUT-17) Maven support
Posted by Grant Ingersoll <gs...@apache.org>.
On Mar 15, 2008, at 11:25 PM, Karl Wettin wrote:
> Grant Ingersoll skrev:
>> I'm -0, if there were such a thing. I guess I can live w/ Maven if
>> it makes others life easier, but in general the only things I like
>> about Maven anymore are the repository, the nice dependency
>> descriptions in the pom and the conventions for project structure.
>> In other words, the
>
> These alone are great reasons. I don't want to replace Ant, only
> enable maximum optional Maven support.
>
>> metadata is great, but the execution stuff, not so much. I don't
>> like the plugins, unless we lock in versions, and I don't like that
>> you can't tie a bunch of tasks together all that easily like you
>> can with Ant.
> >
>> As for the lib changes, etc. those look fine.
>
> It's OK to host stuff like that on people.apache.org, right?
>
As a proof of concept or as a permanent thing? I think it is fine if
you are just showing it as an example, but I don't know if it means
there are a lot of people hitting it.
Re: [jira] Updated: (MAHOUT-17) Maven support
Posted by Karl Wettin <ka...@gmail.com>.
Grant Ingersoll skrev:
> I'm -0, if there were such a thing. I guess I can live w/ Maven if it
> makes others life easier, but in general the only things I like about
> Maven anymore are the repository, the nice dependency descriptions in
> the pom and the conventions for project structure. In other words, the
These alone are great reasons. I don't want to replace Ant, only enable
maximum optional Maven support.
> metadata is great, but the execution stuff, not so much. I don't like
> the plugins, unless we lock in versions, and I don't like that you can't
> tie a bunch of tasks together all that easily like you can with Ant.
>
> As for the lib changes, etc. those look fine.
It's OK to host stuff like that on people.apache.org, right?
karl
>
> -Grant
>
> On Mar 15, 2008, at 6:16 PM, Karl Wettin (JIRA) wrote:
>
>>
>> [
>> https://issues.apache.org/jira/browse/MAHOUT-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
>>
>>
>> Karl Wettin updated MAHOUT-17:
>> ------------------------------
>>
>> Attachment: pomification_hama.diff
>> pomification.diff
>>
>> Current trunk has been moved to the new module 'core' that contains a
>> pom.xml pointing back at the new super project in the trunk root.
>> There is also an intermediate contrib/pom.xml, and there is an
>> alternative patch where Hama is a contrib module. (I don't say Hama
>> belongs in contrib and not in core, it was just a way great way for me
>> to extend the build files.)
>>
>> http://people.apache.org/~kalle/mahout/maven2/
>>
>> This is a repository to wich I have added all dependencies available
>> in trunk/lib. All snapshots are todays revision, built on my laptop.
>>
>> I have also choosen short names for modules not already available in
>> repo1. core rather than hadoop-core, and core rather than mahout-core,
>> but in different groups.
>>
>> {noformat}
>> ./org/apache/hadoop/core/0.17.0-SNAPSHOT
>> ./org/apache/hadoop/hbase/0.2.0-SNAPSHOT
>> ./commons-cli/commons-cli/2.0-SNAPSHOT
>> ./libthrift/libthrift/r746
>> ./org/kosmix/kosmosfs/komsosfs/0.1
>> ./jetty/jetty/5.1.4
>> {noformat}
>>
>> mvn idea:idea in the trunk root creates a multimodule project that I
>> can open and pass all tests in. But it also creates modules for the
>> intermediate projects without code...
>>
>> I added all this info in the root pom, but mvn site:site does not seem
>> to use it? I thought, maybe it would be fun to see if it looks nice. I
>> will try some more before I remove it.
>>
>> There should be some properties for versions and such. And speaking of
>> versions, I see it is 0.1 in Jira, but my patches are 0.0.1.
>>
>> How do you feel about going to Maven all the way like this? I call for
>> a vote!
>>
>>> Maven support
>>> -------------
>>>
>>> Key: MAHOUT-17
>>> URL: https://issues.apache.org/jira/browse/MAHOUT-17
>>> Project: Mahout
>>> Issue Type: Improvement
>>> Affects Versions: 0.1
>>> Reporter: Karl Wettin
>>> Assignee: Karl Wettin
>>> Priority: Minor
>>> Attachments: pomification.diff, pomification_hama.diff
>>>
>>>
>>> The trunk is a Maven module root. I think it should be refactored to
>>> a Maven project root.
>>
>> --
>> This message is automatically generated by JIRA.
>> -
>> You can reply to this email to add a comment to the issue online.
>>
>
> --------------------------
> Grant Ingersoll
> http://www.lucenebootcamp.com
> Next Training: April 7, 2008 at ApacheCon Europe in Amsterdam
>
> Lucene Helpful Hints:
> http://wiki.apache.org/lucene-java/BasicsOfPerformance
> http://wiki.apache.org/lucene-java/LuceneFAQ
>
>
>
>
>
Re: [jira] Updated: (MAHOUT-17) Maven support
Posted by Grant Ingersoll <gs...@apache.org>.
I'm -0, if there were such a thing. I guess I can live w/ Maven if it
makes others life easier, but in general the only things I like about
Maven anymore are the repository, the nice dependency descriptions in
the pom and the conventions for project structure. In other words,
the metadata is great, but the execution stuff, not so much. I don't
like the plugins, unless we lock in versions, and I don't like that
you can't tie a bunch of tasks together all that easily like you can
with Ant.
As for the lib changes, etc. those look fine.
-Grant
On Mar 15, 2008, at 6:16 PM, Karl Wettin (JIRA) wrote:
>
> [ https://issues.apache.org/jira/browse/MAHOUT-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
> ]
>
> Karl Wettin updated MAHOUT-17:
> ------------------------------
>
> Attachment: pomification_hama.diff
> pomification.diff
>
> Current trunk has been moved to the new module 'core' that contains
> a pom.xml pointing back at the new super project in the trunk root.
> There is also an intermediate contrib/pom.xml, and there is an
> alternative patch where Hama is a contrib module. (I don't say Hama
> belongs in contrib and not in core, it was just a way great way for
> me to extend the build files.)
>
> http://people.apache.org/~kalle/mahout/maven2/
>
> This is a repository to wich I have added all dependencies available
> in trunk/lib. All snapshots are todays revision, built on my laptop.
>
> I have also choosen short names for modules not already available in
> repo1. core rather than hadoop-core, and core rather than mahout-
> core, but in different groups.
>
> {noformat}
> ./org/apache/hadoop/core/0.17.0-SNAPSHOT
> ./org/apache/hadoop/hbase/0.2.0-SNAPSHOT
> ./commons-cli/commons-cli/2.0-SNAPSHOT
> ./libthrift/libthrift/r746
> ./org/kosmix/kosmosfs/komsosfs/0.1
> ./jetty/jetty/5.1.4
> {noformat}
>
> mvn idea:idea in the trunk root creates a multimodule project that I
> can open and pass all tests in. But it also creates modules for the
> intermediate projects without code...
>
> I added all this info in the root pom, but mvn site:site does not
> seem to use it? I thought, maybe it would be fun to see if it looks
> nice. I will try some more before I remove it.
>
> There should be some properties for versions and such. And speaking
> of versions, I see it is 0.1 in Jira, but my patches are 0.0.1.
>
> How do you feel about going to Maven all the way like this? I call
> for a vote!
>
>> Maven support
>> -------------
>>
>> Key: MAHOUT-17
>> URL: https://issues.apache.org/jira/browse/MAHOUT-17
>> Project: Mahout
>> Issue Type: Improvement
>> Affects Versions: 0.1
>> Reporter: Karl Wettin
>> Assignee: Karl Wettin
>> Priority: Minor
>> Attachments: pomification.diff, pomification_hama.diff
>>
>>
>> The trunk is a Maven module root. I think it should be refactored
>> to a Maven project root.
>
> --
> This message is automatically generated by JIRA.
> -
> You can reply to this email to add a comment to the issue online.
>
--------------------------
Grant Ingersoll
http://www.lucenebootcamp.com
Next Training: April 7, 2008 at ApacheCon Europe in Amsterdam
Lucene Helpful Hints:
http://wiki.apache.org/lucene-java/BasicsOfPerformance
http://wiki.apache.org/lucene-java/LuceneFAQ
Re: [jira] Updated: (MAHOUT-17) Maven support
Posted by Karl Wettin <ka...@gmail.com>.
Ted Dunning skrev:
> -0
>
> I see no particular benefit at this point. As long as the maven support
> does imply that I would have to use maven to check out the project an build
> it, then I don't care if somebody else uses it.
For me it's about generating the project files for the IDE, and that is
makes is easy for me to use Mahout from my other Maven driven projects.
> If it implies that I have to use maven, then I would change my vote to -1.
It does not.
But to support Maven users I think we have to refacor the trunk.
karl
Re: [jira] Updated: (MAHOUT-17) Maven support
Posted by Ted Dunning <td...@veoh.com>.
-0
I see no particular benefit at this point. As long as the maven support
does imply that I would have to use maven to check out the project an build
it, then I don't care if somebody else uses it.
If it implies that I have to use maven, then I would change my vote to -1.
On 3/15/08 3:16 PM, "Karl Wettin (JIRA)" <ji...@apache.org> wrote:
> How do you feel about going to Maven all the way like this? I call for a vote!