[ http://issues.apache.org/jira/browse/GRFT-13?page=comments#action_57951 ] Stephane Bailliez commented on GRFT-13: ---------------------------------------
build properties are processed in the following order: ${project.home}/project.properties ${project.home}/build.properties ${user.home}/build.properties With the last definition being the winner. Therefore if a user defines a specific list of maven.repo.remote (which I had), it will obviouslly defeat the fact that your project 'absolutely' need a specific repository (which happen to not be a known mirror) to fetch the dreaded binaries. > Specify the maven repositories needed > ------------------------------------- > > Key: GRFT-13 > URL: http://issues.apache.org/jira/browse/GRFT-13 > Project: Graffito > Type: Improvement > Components: Project Build > Versions: 1.0-a1-dev > Reporter: Stephane Bailliez > Assignee: Christophe Lombart > > You would probably want to specify which repositories are needed to actually > build Graffito and fetch dependencies. It took me an incredible long time to > figure out a list of remote repositories that would work and fetch: > jetspeed-persistence-2.0-a1-dev.jar > jetspeed-api-2.0-a1-dev.jar > jetspeed-security-2.0-a1-dev.jar > jetspeed-cm-2.0-a1-dev.jar > jetspeed-rdbms-2.0-a1-dev.jar > jetspeed-commons-2.0-a1-dev.jar > jta1.0.1.jar > jdbc-se2.0.jar > maven-torque-plugin-3.2.jar > ibiblio.org for instance certainly do not have them at the time of this > writing. So a default maven configuration will certainly not work without > specifying the proper repos. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - If you want more information on JIRA, or have a bug to report see: http://www.atlassian.com/software/jira