As far as I know, the settings file is the correct place to store the
information. Brett Porter has done a couple of informal code reviews on the
patch and seems to be in agreement. A temp file would definitely be an
option though, especially if all we want is a temporary solution internal to
Tapestry.
On 12/13/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Ah .
I wonder if it really needs to store the values in the users
settings.xml file at all? The System.getProperty("java.io.tmpdir")
property should at a minimum be globally friendly as a place to write
things.
It looks like the "Preferences" API is even available in jre 1.4
versions, that would probably be the "optimal" place to store such
data.
http://java.sun.com/j2se/1.4.2/docs/api/java/util/prefs/Preferences.html
I'll try and keep track of things, thanks for the update.
On 12/13/06, D&J Gredler <[EMAIL PROTECTED]> wrote:
> The work I've done has been patching the official
maven-artifact-manager,
> maven-artifact and maven-settings modules. The patch, comments and
answers
> are all here:
>
> http://jira.codehaus.org/browse/MNG-671
>
> The holdup currently is that I don't know what the standard way of
accessing
> and modifying the user's settings is (nor do any of the maven devs!).
I've
> asked multiple times on the maven dev mailing list and in the JIRA issue
> itself, but no answer. Based on a thread in the dev list
> (http://www.nabble.com/how-to-get-current-settings-object-tf2180267.html
)
> it looks like Jason van Zyl may be the one who holds the key.
>
> It might be possible to produce custom snapshots of these three modules
for
> internal use, but without the settings info it would prompt the user
about
> unknown licenses each and every time, instead of saving the response. If
> anyone knows Jason, maybe they can give him a friendly nudge?
>
>
> On 12/13/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
> > I have been using Tapernate more and more lately, and would really
> > ~love~ to get my hands on some of the source code in such a way that
> > it is more conveniently available / documented for all.
> >
> > Is there any hope of getting even a snapshot version of some sort of
> > "licensing click through" plugin for maven? Is it a modification of an
> > existing plugin or just a brand new thing? If it's new I think we can
> > host it in the tapestry snapshot repos ...Otherwise maybe I can help
> > try and move things along in maven land if it's getting held up there.
> >
> > I think it would make sense to have it live as a bonafied sub-project
> > of tapestry.apache.org, but maybe others think it should live
> > elsewhere? (perhaps as a sub-project of hivemind.apache.org
> > originally, with tapestry specific stuff existing under
> > tapestry.apache.org ? I think that might get confusing but who
knows..)
> >
> > --
> > Jesse Kuhnert
> > Tapestry/Dojo team member/developer
> >
> > Open source based consulting work centered around
> > dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
> >
>
>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
