>-----Original Message----- >From: cowwoc [mailto:cow...@bbs.darktech.org] > >Wayne Fay wrote: >> >>> What do you recommend I do to work around this problem? >> >> Don't use the ${swt.classifier} for now... >> >> You may notice it was reported 5 years ago so if you actually want it >> fixed, you'll probably need to help on MNG-1388. >> > >How do you deal with artifacts that need a different native library >depending on the build platform without the use of ${swt.classifier}?
This feels to me like the old problem that there is no distinction between the pom file used to control the build, and the pom file that describes the artifact. In a general sense, the properties that exist at the time that an artifact gets created (in this case swt.classifier, which was set by a profile) aren't remembered in the deployed artifact. The workaround I've seen suggested for this is to throw another layer of indirection in there and have a separate pom for each possible value of your variable. In your case, I think you'd split project B into a B-windows-x86/pom.xml, B-whateverelse/pom.xml, etc... modules that each refer to the swt.classifier with a fixed value. Then you'd need to set up an overall pom.xml that lists different modules based on the profile, and you'll probably want some kind of common pom that all of the sub-modules depend on to pull in all the other normal dependencies. Obviously, this doesn't work well if you have more than just one variable you're dealing with, and it seems (to me anyway) to be an unnecessary complex and confusing way to set things up, but supposedly that's the "maven way". eric --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
