Artifacts are caching independently of Maven Profile
Hi,
Hoping someone can help with this. I'm on 2020.1.2 on Catalina.
Our project architecture is basically with Maven using Profiles. Each profile represents a client, and is used to build an EAR with the relevant resources. The ear is named using the profile name (e.g. abc123_PROFILENAME.ear ). The deployment is, however, set using the artifact that is more generic.
We deploy using either Glassfish or Wildfly.
In previous versions I could simply change profile and this would determine the artifact to look for. Since updating to 2020, I've found that the output layout shows the ear that doesn't have the current profile's designation on it, even though the maven build has created the ear for the current profile.
The only way I seem to be able to refresh the ear in the Artifact's Output Layout is to click 'Reload all maven projects' in the Maven tab. I'm 100% sure I didn't have to do this before, and I can't see a setting that would have affected this from otherwise happing automatically.
Can anyone shed any light on what might be causing this?
Please sign in to leave a comment.
>The only way I seem to be able to refresh the ear in the Artifact's Output Layout is to click 'Reload all maven projects' in the Maven tab. I'm 100% sure I didn't have to do this before, and I can't see a setting that would have affected this from otherwise happing automatically.
Could you please show the value of this option in Maven tool window:
Reloading Maven project after pom.xml changes must not be necessary if the Enable auto-reload after any changes is selected.
Sorry to be slow to respond on this, it is set to 'after any changes'.
It still shows the out-of-date snapshot in the artifacts screen. Quite annoying when you have to get stuff done.
It would appear to need a few attempts at manually clicking 'Auto Reload' before it actually does as much
Hello Chris,
Is it reproducible with new sample project?