-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
7378: Update platform to 2021-06 #301
Conversation
👋 Welcome back hirt! A progress list of the required criteria for merging this PR into |
I think it's fine. We don't support Java 1.4 anymore. :) |
@guruhb - do you happen to know if there is a way to suppress all the new Tycho warnings? |
(Maven Artifact blablabla is not a bundle and will be ignored, automatic wrapping of such artifacts can be enabled with wrapAsBundle in target platform configuration) |
This looks very interesting to solve and tycho is now capable of converting non OSGi Bundle to OSGi for maven dependency if we add but there is a catch .. If we use non OSGi dependency the "Bundle Symbolic name generated by tycho 2.x will be "groupid.artifactId" where as the p2-maven-plugin (currently used for converting non OSGi to OSGi and hosting as a local p2 server convert Bundle Symbolic name to "groupId" (Note the missing artifactId There are two solution i could think off and None of them are good at this point of time Solution 1 : Unify Core with application and remove p2-maven-plugin (+ remove releng /third-party) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
looks good to me
@thegreystone This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 2 new commits pushed to the Please see this link for an up-to-date comparison between the source branch of this pull request and the ➡️ To integrate this PR with the above commit message to the |
For me, the UI-tests will not start with this PR (on Windows). |
/integrate |
Going to push as commit d05f377.
Your commit was automatically rebased without conflicts. |
@thegreystone Pushed as commit d05f377. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
So. After not being able to figure out what is wrong, I nuked my local repo, my .m2 cache etc. And, yep, the UI tests work now. :'( |
...and removing old ones.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.java.net/jmc pull/301/head:pull/301
$ git checkout pull/301
Update a local copy of the PR:
$ git checkout pull/301
$ git pull https://git.openjdk.java.net/jmc pull/301/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 301
View PR using the GUI difftool:
$ git pr show -t 301
Using diff file
Download this PR as a diff file:
https://git.openjdk.java.net/jmc/pull/301.diff