[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [m2e-dev] Need help in opening m2e project in eclipse
|
These project files are created and maintained by Eclipse as the normal
development process, in fact they are the primary source and the pom.xml
are then hand-crafted afterwards to fit those, because of that pomless
is the way to go when developing eclipse/pde plugins and m2e is an
eclipse-plugin project.
The "simple pom.xml" simlpy adds unnecessary overhead and its hilarious
to even waste time to discuss about re-adding them because of the mood
of frustration... just MY whatever cents.
That the .project files are missing is a simple issue not discovered
before just because m2e devlopers not regulatory building up a complete
new workspace.
Anyways the .project files are also redundant in the sense of that they
do not carry information absolutely required and we are working on ways
to even get rid of those. but for the moment they are a valid choice.
If one really feels to improve something there are two top issues that
address these kind of things:
- https://github.com/eclipse-m2e/m2e-core/issues/120
- https://github.com/eclipse-m2e/m2e-core/issues/119
Am 02.04.21 um 01:57 schrieb Carsten Heyl:
I am just adding my € 0,02 without having an overview and being ignorant
of many issues.
On 01.04.21 20:35, Mickael Istria wrote:
On Thu, Apr 1, 2021 at 7:42 PM Fred Bricon <fbricon@xxxxxxxxx
<mailto:fbricon@xxxxxxxxx>> wrote:
- the pomless experiment (removing the simplest pom.xmls): makes
it impossible to import all the projects as maven projects. Plenty
projects are missing
That's indeed an issue. We'll add the .project files.
- The .project files must come from somewhere and they must be maintained.
- The simple pom.xml files before made it possible for me to load most
of the projects as maven projects before
and you didn't have to maintain .project files in addition that can
get out of date.
Maybe it was just too early for going pomless?
- Situation sounds like a classic regression to me. M2e core can't load
m2e-core project any more.
May indicate a missing test. Is there some integration test that
loads the m2e project itself?
That can provide a base line that should not be lost.
- If that baseline (integration test loading m2e project itself ) can be
advanced - perhaps
in a separate feature branch - to support pomless m2e-core: Maybe
migrate slowly, make support for that part of
the 2021-06 but switch m2e project to pomless after that.
- undocumented dependencies (PDE, Lemminx, Eclipse tests ..., )
We need a working .target file, but the m2e-maven-runtime stuff makes
it complicated to write a good portable target file that uses local
build of those bundles.
I felt the need for a working .target file myself.
(Currently erefactor uses the target platform but I was told to strip
away bundles and that would reduce the target platform as I understand it.)
Is it necessary to have a single .target that fits all?
Would it be useful to have 2-3 different ones?
One for the casual developer, that just needs a working dependency tree
for development version:
May be OK to have target file point to specific nightly/weekly/what
ever remote dev builds of the dependencies with information
how to update if the remote site is garbage collected. Replace deps
with stable ones when possible.
One for the "full stack" developer that needs HEAD versions of the
lemminx etc. deps locally.
Tell how to layout the different working copies and what to do to
make this target file happy.
Can some of that being scripted?
HTH,
Cal
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To unsubscribe from this list, visithttps://www.eclipse.org/mailman/listinfo/m2e-dev
_______________________________________________
m2e-dev mailing list
m2e-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/m2e-dev