You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mahout.apache.org by Ted Yu <yu...@gmail.com> on 2011/03/10 20:22:26 UTC
generating Eclipse project
Hi,
I typed the following command under mahout root dir:
mvn eclipse:eclipse
But I don't see any .classpath generated.
Please comment.
Re: generating Eclipse project
Posted by Dmitriy Lyubimov <dl...@gmail.com>.
actually Mahout-math module would not compile in eclipse because maven
specifies code style 1.5 for that module whereas it is actually 1.6
style. There was a recent bug filed for that. To overcome, go to java
compiler settings for mahout-math module and manually set them to 1.6.
All be fine then.
-D
On Thu, Mar 10, 2011 at 12:13 PM, Dmitriy Lyubimov <dl...@gmail.com> wrote:
> Yes eclipse comes up with some errors in some projects -- normally it
> doesn't happen unless there's a lot of <exclude> dependency tags --
> but not in core or math (which is all i care for now). I did not look
> in compilation errors in other modules.
>
> But at least it creates the project structure. just do "import
> existing projects" -> select top level dir --> select all projects
> found -- enter. should end up with 4 or 5 projects on top level.
>
> -d
>
> On Thu, Mar 10, 2011 at 12:05 PM, Chris Schilling <ch...@cellixis.com> wrote:
>> In eclipse you can import the top level pom file. As Dmitriy stated, it does break the project down into several sub-modules.
>>
>> I generally compile using maven at command line then import the pom.xml. I have not had much success trying to compile mahout inside of eclipse.
>>
>>
>> On Mar 10, 2011, at 11:56 AM, Dmitriy Lyubimov wrote:
>>
>>> .projects and .classpaths are generated in submodules. Each maven
>>> module results in a standalone project in eclipse. You won't see any
>>> on the top level. It works and that's how i use it.
>>>
>>> On Thu, Mar 10, 2011 at 11:51 AM, Ted Dunning <te...@gmail.com> wrote:
>>>> Can't help you directly. IntelliJ imports the pom directly. I had thought
>>>> that eclipse would do the same.
>>>>
>>>> Otherwise, perhaps an eclipse master can help?
>>>>
>>>> On Thu, Mar 10, 2011 at 11:22 AM, Ted Yu <yu...@gmail.com> wrote:
>>>>
>>>>> Hi,
>>>>> I typed the following command under mahout root dir:
>>>>> mvn eclipse:eclipse
>>>>>
>>>>> But I don't see any .classpath generated.
>>>>>
>>>>> Please comment.
>>>>>
>>>>
>>
>>
>
Re: generating Eclipse project
Posted by Dmitriy Lyubimov <dl...@gmail.com>.
Yes eclipse comes up with some errors in some projects -- normally it
doesn't happen unless there's a lot of <exclude> dependency tags --
but not in core or math (which is all i care for now). I did not look
in compilation errors in other modules.
But at least it creates the project structure. just do "import
existing projects" -> select top level dir --> select all projects
found -- enter. should end up with 4 or 5 projects on top level.
-d
On Thu, Mar 10, 2011 at 12:05 PM, Chris Schilling <ch...@cellixis.com> wrote:
> In eclipse you can import the top level pom file. As Dmitriy stated, it does break the project down into several sub-modules.
>
> I generally compile using maven at command line then import the pom.xml. I have not had much success trying to compile mahout inside of eclipse.
>
>
> On Mar 10, 2011, at 11:56 AM, Dmitriy Lyubimov wrote:
>
>> .projects and .classpaths are generated in submodules. Each maven
>> module results in a standalone project in eclipse. You won't see any
>> on the top level. It works and that's how i use it.
>>
>> On Thu, Mar 10, 2011 at 11:51 AM, Ted Dunning <te...@gmail.com> wrote:
>>> Can't help you directly. IntelliJ imports the pom directly. I had thought
>>> that eclipse would do the same.
>>>
>>> Otherwise, perhaps an eclipse master can help?
>>>
>>> On Thu, Mar 10, 2011 at 11:22 AM, Ted Yu <yu...@gmail.com> wrote:
>>>
>>>> Hi,
>>>> I typed the following command under mahout root dir:
>>>> mvn eclipse:eclipse
>>>>
>>>> But I don't see any .classpath generated.
>>>>
>>>> Please comment.
>>>>
>>>
>
>
Re: generating Eclipse project
Posted by Chris Schilling <ch...@cellixis.com>.
In eclipse you can import the top level pom file. As Dmitriy stated, it does break the project down into several sub-modules.
I generally compile using maven at command line then import the pom.xml. I have not had much success trying to compile mahout inside of eclipse.
On Mar 10, 2011, at 11:56 AM, Dmitriy Lyubimov wrote:
> .projects and .classpaths are generated in submodules. Each maven
> module results in a standalone project in eclipse. You won't see any
> on the top level. It works and that's how i use it.
>
> On Thu, Mar 10, 2011 at 11:51 AM, Ted Dunning <te...@gmail.com> wrote:
>> Can't help you directly. IntelliJ imports the pom directly. I had thought
>> that eclipse would do the same.
>>
>> Otherwise, perhaps an eclipse master can help?
>>
>> On Thu, Mar 10, 2011 at 11:22 AM, Ted Yu <yu...@gmail.com> wrote:
>>
>>> Hi,
>>> I typed the following command under mahout root dir:
>>> mvn eclipse:eclipse
>>>
>>> But I don't see any .classpath generated.
>>>
>>> Please comment.
>>>
>>
Re: generating Eclipse project
Posted by Ted Yu <yu...@gmail.com>.
Thanks Dmitriy.
On Thu, Mar 10, 2011 at 11:56 AM, Dmitriy Lyubimov <dl...@gmail.com>wrote:
> .projects and .classpaths are generated in submodules. Each maven
> module results in a standalone project in eclipse. You won't see any
> on the top level. It works and that's how i use it.
>
> On Thu, Mar 10, 2011 at 11:51 AM, Ted Dunning <te...@gmail.com>
> wrote:
> > Can't help you directly. IntelliJ imports the pom directly. I had
> thought
> > that eclipse would do the same.
> >
> > Otherwise, perhaps an eclipse master can help?
> >
> > On Thu, Mar 10, 2011 at 11:22 AM, Ted Yu <yu...@gmail.com> wrote:
> >
> >> Hi,
> >> I typed the following command under mahout root dir:
> >> mvn eclipse:eclipse
> >>
> >> But I don't see any .classpath generated.
> >>
> >> Please comment.
> >>
> >
>
Re: generating Eclipse project
Posted by Dmitriy Lyubimov <dl...@gmail.com>.
.projects and .classpaths are generated in submodules. Each maven
module results in a standalone project in eclipse. You won't see any
on the top level. It works and that's how i use it.
On Thu, Mar 10, 2011 at 11:51 AM, Ted Dunning <te...@gmail.com> wrote:
> Can't help you directly. IntelliJ imports the pom directly. I had thought
> that eclipse would do the same.
>
> Otherwise, perhaps an eclipse master can help?
>
> On Thu, Mar 10, 2011 at 11:22 AM, Ted Yu <yu...@gmail.com> wrote:
>
>> Hi,
>> I typed the following command under mahout root dir:
>> mvn eclipse:eclipse
>>
>> But I don't see any .classpath generated.
>>
>> Please comment.
>>
>
Re: generating Eclipse project
Posted by Ted Dunning <te...@gmail.com>.
Can't help you directly. IntelliJ imports the pom directly. I had thought
that eclipse would do the same.
Otherwise, perhaps an eclipse master can help?
On Thu, Mar 10, 2011 at 11:22 AM, Ted Yu <yu...@gmail.com> wrote:
> Hi,
> I typed the following command under mahout root dir:
> mvn eclipse:eclipse
>
> But I don't see any .classpath generated.
>
> Please comment.
>