On Mon, Feb 28, 2011 at 6:13 AM, Adelita Padilla <[email protected]> wrote: > Instead of having a profile (sounds error-prone), we could set the path as > property (we could use the 'localRepository' property) using a command line > switch (so it still match the behavior of Maven). > > So for example, user will input -DlocalRepository="D:\test\repository", > NPanday will assume that both settings.xml and npanday-settings.xml are > located in "D:\test" directory. Since npanday-settings.xml is generated, > NPanday will check on the specified directory for that file. If ever > npanday-settings.xml doesn't exist yet, NPanday will generate the file in > that specified path. > > Does it make sense?
No... a property called localRepository should be only the location of the local repository. Adding "magic" like expecting to find the settings files one level up from that will get you into trouble. What if someone puts their local repository in f:\ ? What if the user doesn't have permission to write to the parent directory? Maven uses the -s switch on the command line to point to the settings file. Is there any reason you need more than that? Before you invent a property, does Maven already have one it knows about for the regular settings.xml file? -- Wendy
