Thanks for all the hard work on this Daniel, I promise I'll add your changes lickety split once this is all squared away ;) (or possibly find some way to make this a tiny sub-project...we shall see)
On 8/28/06, gredler <[EMAIL PROTECTED]> wrote:
Hi Jason, Thanks for the response. I'm not aware of any license clickthrough libraries, so I wrote my own handler (one class) which resides in maven-artifact. I'm not sure how coupling it to maven-artifact precludes developers who are embeding maven-artifact from exploiting this capability? Or did you mean *not* want this capability? Anyways, my mention of Maven CLI and the other subprojects were just me trying to list the places I have been looking for examples of how to retrieve a reference to the current Settings instance. That's my main problem now: how do I get the Settings instance and persist a change to it. If you are able to take a couple of minutes to review the patches, please post any suggestions to the JIRA issue. This is my first Maven customizaton, so be gentle ;-) Regards, Daniel On 28 Aug 06, at 6:15 PM 28 Aug 06, gredler wrote: > > Hi, > > I'm working on the license clickthough functionality in the artifact > resolver (http://jira.codehaus.org/browse/MNG-671), and I need to > know: > > - what the best way of retrieving the current Settings object is > - what the best way of saving changes to the Settings object is > > I'm hoping that I can just add a line or two to a components.xml > file and > have Maven automagically wire the object up. > > I've been banging my head against MavenSettingsBuilder (recently > refactored), MavenTools, MavenEmbedder, etc. There has to be a > simple way to > do this behind all the abstractions! > Do you have a general click through library that you are binding in with a resolution listener or is this stuff coupled to maven-artifact? I will respond further once I look at the patches, but what you should have is a separate library bridge in with a listener and any configuration you need should be couched in terms of maven-artifact requests translated to what your library needs. Because people may simply embed maven-artifact and want this capability. Maybe you did this, but this is the only way I see this working. Shouldn't matter what the Maven CLI does. > Thanks, > > Daniel -- View this message in context: http://www.nabble.com/how-to-get-current-settings-object-tf2180267.html#a6030399 Sent from the Maven Developers forum at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
