After some more digging, I notice that I can replace MavenCli with a custom implementation in <M2_HOME>/bin/m2.conf that I could use to manually create an instance of ProfileManager that does what I want. Is this the only way to accomplish what I need? I was hoping to be able to inject an instance of my implementation class. Anyone?
ertnutler wrote: > > I'm looking for a good way to surface external properties to Maven. For > the sake of brevity, these properties aren't in profiles.xml format but > are in a proprietary format. I was thinking I could create Profile > instances as I see fit and populate them such that the properties are > available at runtime. I've been poking around in the source and notice > that a natural place to do this is in a ProfileManager implementation, but > MavenCli manually creates an instance of DefaultProfileManager in its > main(String[], ClassWorld) method. > > Is there a better place or way to accomplish this type of thing? If not, > is there a way to change the implementation class of ProfileManager so I > can add some custom property gathering logic? > -- View this message in context: http://www.nabble.com/source-arbitrary-external-profile-data--tp18221089p18222959.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
