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

Bump emf version to match the content of 2024.3 #3293

Merged
merged 11 commits into from
Dec 17, 2024
Merged

Bump emf version to match the content of 2024.3 #3293

merged 11 commits into from
Dec 17, 2024

Conversation

szarnekow
Copy link
Contributor

No description provided.

@cdietrich
Copy link
Contributor

nice, can you please check

  • SimpleTestLanguageFragments.mwe2
  • we still have complianceLevel 11 a lot

@cdietrich
Copy link
Contributor

the swt bot change does not work for me. the versions oomph pulls for me is 4.0.0

@cdietrich
Copy link
Contributor

it also looks like a transitive reexport of guice got lost somewhere. see failed build

@szarnekow
Copy link
Contributor Author

it also looks like a transitive reexport of guice got lost somewhere. see failed build

$git diff origin/main | grep google
+import com.google.common.collect.ForwardingMap;

hmm

@szarnekow
Copy link
Contributor Author

But javax.inject doesn't seem to be there anymore

Error:  Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.11.0:compile (default-compile) on project org.eclipse.xtext.web.example.statemachine: Compilation failure
Error:  /home/runner/work/xtext/xtext/org.eclipse.xtext.web.example.statemachine/src-gen/org/eclipse/xtext/web/example/statemachine/AbstractStatemachineRuntimeModule.java:[131,37] cannot access javax.inject.Provider
Error:    class file for javax.inject.Provider not found
Error:  -> [Help 1]

Copy link

github-actions bot commented Dec 15, 2024

Test Results

  6 461 files  +  6 461    6 461 suites  +6 461   3h 25m 25s ⏱️ + 3h 25m 25s
 43 239 tests + 43 239   42 655 ✅ + 42 655    584 💤 +  584  0 ❌ ±0 
170 246 runs  +170 246  167 904 ✅ +167 904  2 337 💤 +2 337  5 ❌ +5 

Results for commit 881c922. ± Comparison against base commit 4fb59cc.

♻️ This comment has been updated with latest results.

@cdietrich
Copy link
Contributor

werent we using com.google.inject.Provider everywhere to circumvent the jaxax jakartax problem?

@cdietrich
Copy link
Contributor

cdietrich commented Dec 15, 2024

regenerating langs fails for me everywhere witjh
Caused by: java.lang.ClassNotFoundException: org.slf4j.LoggerFactory
at java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:641)
at java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:188)
at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:526)
... 35 more

likely due to our wild mix of p2 and maven

@cdietrich
Copy link
Contributor

can reproduce the compile error but still have no clue what causes it

apache-maven-3.9.9/bin/mvn clean verify -f org.eclipse.xtext.maven.releng -B  -PuseJenkinsSnapshots -Pstrict-jdk-21

@cdietrich
Copy link
Contributor

one suspicious diff in classpath is

/Users/dietrich/.m2/repository/.cache/tycho/org.eclipse.m2e.maven.runtime-3.9.900.20240824-1409.jar/jars/org.eclipse.sisu.inject-0.9.0.M3.jar:

i dont see that one on main

maybe something with the m2e changes?

@cdietrich
Copy link
Contributor

but i have no idea why this is there at all

@HannesWell do you have an idea?

@cdietrich
Copy link
Contributor

wait. why do have have

org.eclipse.xtext.util/build.properties:additional.bundles = org.eclipse.m2e.maven.runtime

@LorenzoBettini
Copy link
Contributor

one suspicious diff in classpath is

/Users/dietrich/.m2/repository/.cache/tycho/org.eclipse.m2e.maven.runtime-3.9.900.20240824-1409.jar/jars/org.eclipse.sisu.inject-0.9.0.M3.jar:

i dont see that one on main

maybe something with the m2e changes?

I seem to understand that's the new additional bundle, maybe due to the change in bump versions that reads the dev bom?

@cdietrich
Copy link
Contributor

Maybe tycho sips add. Bundles into downstream classpathes too

@cdietrich
Copy link
Contributor

Removing the additional helped locally. Reverting the manifest changes not

@LorenzoBettini
Copy link
Contributor

Removing the additional helped locally. Reverting the manifest changes not

I don't understand: what's solved and what's not?

@cdietrich
Copy link
Contributor

Reverting the two manifest changes regarding M2e still compile error
Reverting the add bundle this compile errors gone.

@szarnekow
Copy link
Contributor Author

I’ll move BumpVersions to its own bundle

@HannesWell
Copy link
Contributor

/Users/dietrich/.m2/repository/.cache/tycho/org.eclipse.m2e.maven.runtime-3.9.900.20240824-1409.jar/jars/org.eclipse.sisu.inject-0.9.0.M3.jar:

maybe something with the m2e changes?

Recently there haven't been any change in the embedded Maven-runtime in m2e:
https://github.com/eclipse-m2e/m2e-core/commits/master/org.eclipse.m2e.maven.runtime

Or do you mean why Sisu is included in the runtime? Sorry if I don't get the question right.

@cdietrich
Copy link
Contributor

cdietrich commented Dec 16, 2024

yes was wondering about sisu
and why tycho puts add. bundles to transitive classpaths

Signed-off-by: Sebastian Zarnekow <[email protected]>
@szarnekow
Copy link
Contributor Author

I’ll move BumpVersions to its own bundle

Done.

Build is certainly making more progress now.

I had to bump log4j to 1.2.26 because 1.2.25 disappeared

@szarnekow
Copy link
Contributor Author

regenerating langs fails for me everywhere witjh

How do you regenerate them?

@cdietrich
Copy link
Contributor

cdietrich commented Dec 16, 2024

regenerating langs fails for me everywhere witjh

How do you regenerate them?

go through the list and calling the workflows from eclipse.
am not sure if it is related to me having mwe imported in workspace

https://github.com/eclipse-xtext/xtext/blob/main/dev-doc/RegenerateLanguages.md

Signed-off-by: Sebastian Zarnekow <[email protected]>
@cdietrich
Copy link
Contributor

hi, what is the status on the open points?
or should we cherry pick the log4j changes to unblock main

@szarnekow
Copy link
Contributor Author

On this branch, I can regenerate languages.
I'm working on a workflow that builds them all from xtext.relengutils

Of course I've plenty changes since almost all files get a new copyright header

@cdietrich
Copy link
Contributor

Of course I've plenty changes since almost all files get a new copyright header

  • which emf/tp version do you use to regen?
  • isnt the header configured in the genmodels?

@szarnekow
Copy link
Contributor Author

Ok, a single script doesn't work because the workflows are sensitive to global registry content.

@cdietrich
Copy link
Contributor

so maybe a launch group similar to the one in ref projects.maybe with wait on each

@szarnekow
Copy link
Contributor Author

Yes, I'm looking into that.

which tp

2024-03

@szarnekow
Copy link
Contributor Author

isnt the header configured in the genmodels?

Yes, it is. Some files have not been regenerated yet in 2024

@cdietrich
Copy link
Contributor

maybe we can do it in a follow up then if there is no significant other change

@szarnekow
Copy link
Contributor Author

maybe we can do it in a follow up then if there is no significant other change

Yes, we surely can do that

@cdietrich
Copy link
Contributor

otherwise what is open besides
lorenzos comments
e.g. on org.eclipse.xtext.relengutil/.classpath

Signed-off-by: Sebastian Zarnekow <[email protected]>
@szarnekow
Copy link
Contributor Author

otherwise what is open besides lorenzos comments

Made adjustments accordingly and I think we are good to go now.

Copy link
Contributor

@LorenzoBettini LorenzoBettini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

@cdietrich cdietrich merged commit a68a47b into main Dec 17, 2024
17 checks passed
@cdietrich
Copy link
Contributor

thx @szarnekow

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.

4 participants