> The current deployment strategy we use in plugins is deprecated, and > not supported anymore in maven1.1 (which I happen to be using ^^)
Does it works for maven-1.0.2 ? :) > I'd be in favor of changing to the following: > * in the root project.properties, have one property like: > > maven.repo.list=codehaus > > * each user must have a build.properties file in its home directory, > with details corresponding to the repository(ies) listed in > maven.repo.list, like I do : And does it support default values in project.properties ? I mean maven.repo.codehaus=http://dist.codehaus.org Any user should be able to build it without having a build.properties isn't it! Btw, regarding the properties defined in plugin-xxx/project.properties and top/project.properties, have you succeeded? > > maven.repo.codehaus=scp://beaver.codehaus.org > maven.repo.codehaus.directory=/dist/ > maven.repo.codehaus.username=gjoseph > maven.repo.codehaus.privatekey=${user.home}/.ssh/id_dsa > > This allows cleaner properties file, and user-specific config without > being annoyed with the fact that you can't commit the file to cvs. (in > my case, for instance, I need a different usename, on my homebox my > username is "greg", while it's "gjoseph" on beaver and other machines) Diogo ------------------------------------------------------- SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf _______________________________________________ xdoclet-plugins-interest mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xdoclet-plugins-interest
