Skip to content

Conversation

@chonton
Copy link
Member

@chonton chonton commented Mar 10, 2018

Setting installAtEnd causes no installs to occur when a multimodule project has multiple class realms

@chonton
Copy link
Member Author

chonton commented Apr 12, 2018

Unfortunately, this technique interferes with surefire/failsafe. The user properties must contain String properties. I could make the pojos into json encoding.

Or, what other places can a plugin save information across invocations? It appears that plugin context is also tied to the ClassLoader.

@elharo
Copy link
Contributor

elharo commented Apr 26, 2021

Is this still in progress? Should we close it?

@chonton
Copy link
Member Author

chonton commented May 31, 2021

Since implementation is difficult without changes to core maven, I've updated this pull request to be documentation only.

@elharo elharo changed the title MINSTALL-115: installAtEnd fails with multiple class realms [MINSTALL-115] installAtEnd fails with multiple class realms May 31, 2021
@cstamas
Copy link
Member

cstamas commented Oct 7, 2021

Check out #15

@cstamas
Copy link
Member

cstamas commented Jul 12, 2022

This PR is obsolete now, as skip/installAtEnd should be normally and "as expected" supported. No need anymore to "consistently" (I guess it was means "same"?), one can now skip some, installAtEnd some and install the rest.

@cstamas cstamas closed this Jul 12, 2022
@jira-importer
Copy link

Resolve #276

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