You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
and delete the now empty m2e-maven-runtime project.
Since o.e.m2e.maven.runtime is the only remaining module in
m2e-maven-runtime there is no need anymore to keep m2e-maven-runtime as
its parent project.
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+1-5Lines changed: 1 addition & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -57,7 +57,7 @@ Step by Step guide:
57
57
3. Click *Next* .
58
58
7. Press *Finish* on the *Confirmation* page will start the installation process.
59
59
8. The installer will download the selected Eclipse version, starts Eclipse and will perform all the additional steps (cloning the git repos, etc...). When the downloaded Eclispe started, the progress bar in the status bar shows the progress of the overall setup.
60
-
9. Once the *Executing startup task* job is finished you should have all the *m2-core*, *m2-core-tests*and *m2e-maven-runtime*projects imported into three working sets called *m2-core*, *m2-core-tests* and *m2e-maven-runtime*.
60
+
9. Once the *Executing startup task* job is finished you should have all the *m2-core* and *m2-core-tests* projects imported into three working sets called *m2-core* and *m2-core-tests*.
61
61
10. Remaining errors are resolved after a restart of Eclipse.
62
62
11. Happy coding!
63
63
@@ -70,10 +70,6 @@ Some tests are in a separate repository which is referenced as a Git submodule i
70
70
* Use latest release of the Eclipse SDK or Eclipse IDE with the Plugin Development Environment installed.
71
71
* Make sure m2e is installed in this IDE, including the "m2e PDE" feature,
72
72
*_File > Open Projects from Filesystem..._ , select the path to m2e-core Git repo and the relevant children projects you want to import; approve m2e connectors installation if prompted
73
-
* Depending on the task you're planning to work on, multiple workflows are available to configure the [target-platform](https://help.eclipse.org/2021-03/topic/org.eclipse.pde.doc.user/concepts/target.htm?cp=4_1_5)
74
-
* In many cases, this simplest workflow will be sufficient: Install latest m2e snapshot in your target-platform (can be your current IDE), or
75
-
* If you don't want to mix versions of m2e, open __target-platform/dev-worksace.target__ and _Set as Target-Platform_ from the editor, or
76
-
* In case you're working on the content of the `m2e-maven-runtime` folder, then run `mvn install -f m2e-maven-runtime/` after your changes to deploy them locally and then tweak the _target-platform/dev-worksace.target_ to reference the versions of those artifacts you build locally and reload this target platform
77
73
* Open the project modules you want to work on (right-click > Open project) and their dependencies; approve m2e connectors installation if prompted
# To force a version qualifier update add the bug here
2
2
Update build-qualifier because maven-runtime components currently use the committer's time-zone for their qualifier and don't align with the other projects that use UTC.
3
3
Update build-qualifier because maven-runtime components now use again UTC+0-based qualifiers.
0 commit comments