Skip to content
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

Dependency Updates #1923

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Dependency Updates #1923

wants to merge 1 commit into from

Conversation

github-actions[bot]
Copy link

@github-actions github-actions bot commented Feb 6, 2025

The content of the target target-platform.target was updated

Please review the changes and merge if appropriate, or cherry pick individual updates.

The location https://download.eclipse.org/eclipse/updates/4.34/ was updated:

The location https://download.eclipse.org/tools/orbit/simrel/orbit-aggregation/2025-03/ was updated:

The location https://download.eclipse.org/egit/updates-7.1/ was updated:

The following maven artifacts have been updated:

  • ch.qos.logback:logback-classic:jar:1.5.17 has been updated to version 1.5.18
  • org.apache.maven.archetype:archetype-common:jar:3.2.1 has been updated to version 3.3.1
  • org.apache.maven.archetype:archetype-catalog:jar:3.2.1 has been updated to version 3.3.1
  • org.apache.maven.archetype:archetype-descriptor:jar:3.2.1 has been updated to version 3.3.1

@laeubi
Copy link
Member

laeubi commented Feb 6, 2025

Looks like we now need the setting in jenkins to not build PR branches twice :-\

@laeubi
Copy link
Member

laeubi commented Feb 6, 2025

Archetype update seem to require us to adjust some method calls and signatures.

@HannesWell
Copy link
Contributor

Archetype update seem to require us to adjust some method calls and signatures.

I wanted to take this new version as an opportunity to update the structure of the generated OSGi metadata and therefore would like to do this in a separate change. Who knows when the next version will be released and we have the opportunity again without the need for (manual) qualifiers.

@laeubi
Copy link
Member

laeubi commented Feb 8, 2025

I wanted to take this new version as an opportunity to update the structure of the generated OSGi metadata and therefore would like to do this in a separate change.

No problem, once the PR is there and merged it will automatically update this PR and we can see if there is more to do.

By the way whats wrong with the current metadata?

@github-actions github-actions bot force-pushed the update_target branch 3 times, most recently from c645eaa to e233c0d Compare February 10, 2025 00:08
akurtakov added a commit to akurtakov/m2e-core that referenced this pull request Feb 20, 2025
Content taken from eclipse-m2e#1923 as
all updates are not appliable without code changes.
Updated are:
* ch.qos.logback:logback-classic:jar:1.5.12 has been updated to version
1.5.16
    additionally requires java.package; java.lang.module 0.0.0 compared
to the previous version
* com.google.code.gson:gson:jar:2.11.0 has been updated to version
2.12.1
    additionally requires osgi.ee; (&(osgi.ee=JavaSE)(version=1.8))
compared to the previous version
* com.google.guava:guava:jar:33.3.1-jre has been updated to version
33.4.0-jre
* commons-codec:commons-codec:jar:1.17.1 has been updated to version
1.18.0
akurtakov added a commit that referenced this pull request Feb 20, 2025
Content taken from #1923 as
all updates are not appliable without code changes.
Updated are:
* ch.qos.logback:logback-classic:jar:1.5.12 has been updated to version
1.5.16
    additionally requires java.package; java.lang.module 0.0.0 compared
to the previous version
* com.google.code.gson:gson:jar:2.11.0 has been updated to version
2.12.1
    additionally requires osgi.ee; (&(osgi.ee=JavaSE)(version=1.8))
compared to the previous version
* com.google.guava:guava:jar:33.3.1-jre has been updated to version
33.4.0-jre
* commons-codec:commons-codec:jar:1.17.1 has been updated to version
1.18.0
@github-actions github-actions bot force-pushed the update_target branch 3 times, most recently from ef85d6f to 92e7e0e Compare February 21, 2025 00:08
@laeubi
Copy link
Member

laeubi commented Feb 21, 2025

@HannesWell do you plan to pick up the archetype and apply your wanted adjustments? It seems to be the last item on the list now.

@HannesWell
Copy link
Contributor

@HannesWell do you plan to pick up the archetype and apply your wanted adjustments? It seems to be the last item on the list now.

Yes, I'll to it at the weekend.

By the way whats wrong with the current metadata?

It's not wrong. I think it just can be done a bit better/cleaner. I'll put the details in the new PR.

@github-actions github-actions bot force-pushed the update_target branch 6 times, most recently from fd30aa2 to d65e4da Compare February 27, 2025 00:08
@github-actions github-actions bot force-pushed the update_target branch 3 times, most recently from 2192202 to b687182 Compare March 5, 2025 00:08
@github-actions github-actions bot force-pushed the update_target branch 2 times, most recently from 5fbdd52 to 2b011d9 Compare March 13, 2025 00:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants