[ 
https://issues.apache.org/jira/browse/TRAFODION-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14621808#comment-14621808
 ] 

Hans Zeller edited comment on TRAFODION-7 at 7/10/15 6:29 AM:
--------------------------------------------------------------

Our source tree has several pom.xml files and what I did in the make target was 
to generate several .project files from them, so people can import them easily. 
The Eclipse workspace I use has these Maven projects plus one C++ Makefile 
project for the C++ code in it. If all the Maven .project files are generated 
then it's not a good idea to check one global file into git, that would combine 
the disadvantages of both approaches.

Here is the makefile code:

eclipse: rest/.project sql/.project sqf/src/seatrans/hbase-trx/.project .project

rest/.project:
        cd rest && $(MAVEN) eclipse:eclipse

sql/.project:
        cd sql  && $(MAVEN) eclipse:eclipse

sqf/src/seatrans/hbase-trx/.project:
        cd sqf/src/seatrans/hbase-trx && $(MAVEN) eclipse:eclipse

.project:
        cp sqf/export/limited-support-tools/eclipse.project .project
        cp sqf/export/limited-support-tools/eclipse.cproject .cproject

I'm not an Eclipse expert and if someone with more knowledge wants to take this 
on that would be great.

About your suggestion about a pointer in the documentation: Yes, I would like 
to add that and a wiki page with instructions. I'm also working on your 
suggestion, Stack, of a blog entry how to build Trafodion with Apache objects. 
That will take a while and the Eclipse work could be part of it, making it 
easier for people to get a feel for the code.

Hans


was (Author: hzeller):
Our source tree has several pom.xml files and what I did in the make target was 
to generate several .project files from them, so people can import them easily. 
The Eclipse workspace I use has these Maven projects plus one C++ Makefile 
project for the C++ code in it. If all the Maven .project files are generated 
then it's not a good idea to check one global file into git, that would combine 
the disadvantages of both approaches.

Here is the makefile code:

eclipse: rest/.project sql/.project sqf/src/seatrans/hbase-trx/.project .project

rest/.project:
        cd rest && $(MAVEN) eclipse:eclipse

sql/.project:
        cd sql  && $(MAVEN) eclipse:eclipse

sqf/src/seatrans/hbase-trx/.project:
        cd sqf/src/seatrans/hbase-trx && $(MAVEN) eclipse:eclipse

.project:
        cp sqf/export/limited-support-tools/eclipse.project .project
        cp sqf/export/limited-support-tools/eclipse.cproject .cproject

I'm not an Eclipse expert and if someone else wants to take this on that would 
be great.

Hans

> Have a .project file to be able to import source code into Eclipse
> ------------------------------------------------------------------
>
>                 Key: TRAFODION-7
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-7
>             Project: Apache Trafodion
>          Issue Type: Improvement
>            Reporter: Pierre Smits
>         Attachments: Trafodion-7-project.diff
>
>
> Currently no .project file exists for an easy import of the source code into 
> Eclipse



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to