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

Test JPMS fails #1676

Closed
wants to merge 1 commit into from
Closed

Test JPMS fails #1676

wants to merge 1 commit into from

Conversation

laeubi
Copy link
Member

@laeubi laeubi commented Feb 14, 2024

No description provided.

Signed-off-by: Christoph Läubrich <[email protected]>
Copy link

Test Results

  214 files  ±0    214 suites  ±0   22m 50s ⏱️ + 1m 51s
  664 tests ±0    653 ✅  - 1  10 💤 ±0  1 ❌ +1 
1 328 runs  ±0  1 305 ✅  - 1  22 💤 ±0  1 ❌ +1 

For more details on these failures, see this check.

Results for commit 18c3042. ± Comparison against base commit 6880fa1.

@laeubi
Copy link
Member Author

laeubi commented Feb 14, 2024

I also checked this test in the local IDE and it works there correctly.

@treilhes
Copy link
Contributor

Hello @laeubi,

I was also looking into it to solve the failing test for my PR #1672 and i did reproduce the issue and found the following:

In JpmsConfigurationTest
When updating the pom content (line 103)

pomFileWS.setContents(new ByteArrayInputStream(argsSet1Content.getBytes()), true, false, null);

A IResourceChangeEvent is triggered but MavenUpdateConfigurationChangeListener never receive the event so the project JreContainer isn't updated when we want to get properties from jreAttributes.

Why ? Because MavenUpdateConfigurationChangeListener isn't registered as a listener into the NotificationManager

The MavenUpdateConfigurationChangeListener is supposed to be regsitered in M2EUIPluginActivator.start() but in this case the start method is never called.

I was able to solve the issue by removing some lines from org.eclipse.m2e.core.ui\META-INF\MANIFEST.MF

By removing the latest 6 lines from the manifest:

Service-Component: OSGI-INF/org.eclipse.m2e.core.ui.internal.archetype.ArchetypeGenerator.xml,
 OSGI-INF/org.eclipse.m2e.core.ui.internal.archetype.ArchetypePlugin.xml
Bundle-ActivationPolicy: lazy
Service-Component: OSGI-INF/org.eclipse.m2e.core.ui.internal.archetype.ArchetypeGenerator.xml,
 OSGI-INF/org.eclipse.m2e.core.ui.internal.archetype.ArchetypePlugin.xml
Bundle-ActivationPolicy: lazy


I don't have any knowledge about osgi but it seems those directives are duplicates but it is just a guess

@laeubi
Copy link
Member Author

laeubi commented Feb 14, 2024

@treilhes interesting observation, do you like to open a PR that removes the duplicates, this does not looks correct it seems these are cam in by c3fa2ed as an accident (maybe merge /rebase problem)

@treilhes
Copy link
Contributor

#1679 created, waiting for the build judgement

@treilhes
Copy link
Contributor

#1679 Seems good

@laeubi laeubi closed this Feb 14, 2024
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.

2 participants