Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [m2e-dev] How to properly configure m2e codebase in Eclipse?

Sure :)

2016-03-29 22:30 GMT+02:00 Anton Tanasenko <atg.sleepless@xxxxxxxxx>:
Andreas, this does actually look cool. Didn't know there was such a thing as yatta.

Just a suggestion though, as you are the publisher, can you also add m2e-core-tests git repo [1]? M2e development does require contributors to also provide regression tests.



2016-03-29 22:16 GMT+03:00 Andreas Höhmann <ahoehma@xxxxxxxxx>:
Hi folks, please have a look at ... https://marketplace.yatta.de/profiles/Es3Y

2016-03-29 18:16 GMT+02:00 David M. Karr <davidmichaelkarr@xxxxxxxxx>:
On 03/28/2016 06:35 PM, Igor Fedorenko wrote:
M2e dev env setup page [1] is reasonably up to date. Maybe you didn't let m2e install tycho project configurator?

No, it went through the connector installation.

When I first did this, I wasn't aware of these instructions you cite, so I did this again with these instructions in mind, using a fresh Eclipse Mars.2 install and a new workspace.

When I first searched for the m2e codebase, I found it on github at "https://github.com/eclipse/m2e-core".  I notice that these instructions refer to "git://git.eclipse.org/gitroot/m2e/m2e-core". I diffed these two, and I think they're identical.

Nevertheless, after cloning the two specified repos, it then says "import org.eclipse.m2e.workspace, m2e-core and m2e-core-tests as existing maven projects".  Looking at the two github repos I just cloned according to the instructions, I don't find "org.eclipse.m2e.workspace" anywhere.

Nevertheless, for whatever reason, I didn't see the same symptom here.  When it seemed to finish processing, all the Java projects were recognized as Java projects.

Note that I did see compile errors about "EasymportJob cannot be resolved to a type" in the "importer" project, but from a quick internet search, it seems like that's a recent issue, and I don't care about that at this point, so I'm fine with this for now.


[1] https://www.eclipse.org/m2e/documentation/m2e-development-environment.html
--
Regards,
Igor



On March 28, 2016 6:32:47 PM "David M. Karr" <davidmichaelkarr@xxxxxxxxx> wrote:

I'd like to get acquainted with the m2e codebase, initially for a
somewhat trivial reason, as I know it does something simple with its POM
editor view that I plan to implement in a different plugin.  At some
point in the future, however, I'd like to work on some possible
enhancements to make it a tiny bit easier for "other" kinds of
developers to create projects that are Maven projects, without having to
deal with some details.

Is there a "Developer's Guide" that describes how to properly configure
the cloned repo in Eclipse for navigating and editing? I've imported all
the Maven projects, but what I noticed is that Eclipse doesn't know they
are Java projects.  Is there something simple I have to do for that?
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev



_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev


_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev



--
Regards,
Anton.

_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/m2e-dev


Back to the top