[ http://jira.codehaus.org/browse/MNG-671?page=all ]
Daniel Gredler updated MNG-671:
-------------------------------
Attachment: maven-artifact-manager-patch.txt
maven-settings-patch.txt
Attaching patches with only a couple of issues (marked with TODO's):
1. What's the best way to access the current MavenProject and Settings
instances? I've assumed they need to be passed in to
ArtifactInstaller#install(...), but I'm not sure this is correct. If it is
correct, then the interface needs to change, as well as whoever is calling this
method.
2. What's the best way to persist Settings changes? There is some commented out
code that instantiates a SettingsXpp3Writer to do it, but I don't know how you
would figure out what file to write to.
Again, this is my first Maven foray, so my entire approach may be flawed...
Looking forward to comments!
> implement a license clickthrough
> --------------------------------
>
> Key: MNG-671
> URL: http://jira.codehaus.org/browse/MNG-671
> Project: Maven 2
> Issue Type: New Feature
> Reporter: Brett Porter
> Fix For: 2.1
>
> Attachments: maven-artifact-manager-patch.txt,
> maven-settings-patch.txt
>
>
> we need some basic license acceptance policy for downloadable artifacts. For
> now, this can just be a Y/N that is saved forever.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
