MAVEN_HOME_LOCAL
You are probably right about this. I remember setting it up, but not the details. I just browsed through my env vars thinking it was configured there. However, I now see that I have this file in Documents and Settings\~\.m2settings.xml ================================ <settings> <localRepository>E:\maven\repository</localRepository> </settings> ================================ A google search only turns it up significantly here: http://maven.apache.org/maven-1.x/apidocs/org/apache/maven/MavenConstants.html and here http://java2.5341.com/msg/42419.html
no revision of the trunk will give me what is in this particular branch
I'm not an expert on svn branching (or maven, or much of anything else :-) ). Are the branches only including an incomplete subset of the trunk (tomahawk or core or shared), and not the whole thing (shared+tomahawk or shared+core)? If so, it sounds to me like we need to improve our branching process. -Mike On 12/20/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote:
Mike Kienenberger wrote: > You can change where the repository is located using > > MAVEN_HOME_LOCAL=E:\maven for example. > Mike, Are you sure this is a standard feature? I don't see any mention of it searching through the maven online docs. I've tried it, but it didn't seem to have any effect. I do see that you can change it in the settings.xml file, as described here [4]. > Also, if you check out the full trunk (core, shared, tomahawk) at a > specific revision, I would think you could build everything without > having to worry about MyFaces versions and repository snapshots. > Hmm well yes building the trunk is very easy. :) But no revision of the trunk will give me what is in this particular branch, and any changes that may have been applied onto the branch itself, right? I basically want to create the same artifacts that are built for the Tomahawk 1.1.4 staging area [5]. The main difference is that I also get Sandbox this way. In any case, it works fine. I was just curious on a few points, and am now grateful for these explanations. Now I can start testing this upcoming Tomahawk release and flood JIRA with countless issues. ;) [4] http://maven.apache.org/guides/mini/guide-configuring-maven.html [5] http://people.apache.org/builds/myfaces/tomahawk-1.1.x/ Regards, Jeff Bischoff Kenneth L Kurz & Associates, Inc. Mike Kienenberger wrote: > You can change where the repository is located using > > MAVEN_HOME_LOCAL=E:\maven for example. > > Also, if you check out the full trunk (core, shared, tomahawk) at a > specific revision, I would think you could build everything without > having to worry about MyFaces versions and repository snapshots. > > On 12/20/06, Jeff Bischoff <[EMAIL PROTECTED]> wrote: >> Simon Kitching wrote: >> >> For Windows, look in c:\Documents and Settings\{your user}\.m2 >> >> Ah yes, after I got home I started to think that the document and >> settings might be the place to look - windows' lackluster equivalent of >> the user home directory. Thanks, I see it now! :) >> >> > And by the way, I assume you're building: >> > http://svn.apache.org/repos/asf/myfaces/shared/trunk/pom.xml >> >> Actually no, I'm building the Tomahawk 1.1.4 branch, from the shared [2] >> and tomahawk [3] locations defined in the status [1] document. >> >> I do see a similar dependancy on 2.0.4 in the 1.1.4 tomahawk pom though, >> so I see what you are saying. I found the 2.0.4 stuff in the .m2 >> directory, and the modified dates were all as expected from my local >> build. I also have the 2.0.5 shared folders in there, but I assume >> that's from earlier when I did build everything from the trunk. >> >> This .m2 folder is safe to delete right? Would just force me to >> redownload all dependencies again I guess. >> >> [1] http://svn.apache.org/repos/asf/myfaces/current/STATUS.txt >> [2] http://svn.apache.org/repos/asf/myfaces/shared/branches/2_0_4/ >> [3] http://svn.apache.org/repos/asf/myfaces/tomahawk/branches/1_1_4/ >> >> Regards, >> >> Jeff Bischoff >> Kenneth L Kurz & Associates, Inc. >> >> Simon Kitching wrote: >> > Simon Kitching wrote: >> >> Jeff Bischoff wrote: >> >>> Simon, >> >>> >> >>> Thanks a lot for responding. I'm still a bit confused, as I don't see >> >>> a ".m2" directory anywhere. I should mention that I am using windows >> >>> - do that change the behaviour at all? >> >> >> >> For Windows, look in c:\Documents and Settings\{your user}\.m2 >> > >> > And by the way, I assume you're building: >> > http://svn.apache.org/repos/asf/myfaces/shared/trunk/pom.xml >> > >> > You can see that it creates version 2.0.5-SNAPSHOT (and installs it >> > under that version-id in your local m2 directory): >> > <groupId>org.apache.myfaces.shared</groupId> >> > <artifactId>myfaces-shared-project</artifactId> >> > <packaging>pom</packaging> >> > <name>MyFaces Shared Project</name> >> > <version>2.0.5-SNAPSHOT</version> >> > >> > >> > Looking at >> > http://svn.apache.org/repos/asf/myfaces/tomahawk/trunk/ >> > you can see that file core/pom.xml declares a dependency on shared >> > 2.0.5-SNAPSHOT: >> > <dependency> >> > <groupId>org.apache.myfaces.shared</groupId> >> > <artifactId>myfaces-shared-tomahawk</artifactId> >> > <version>2.0.5-SNAPSHOT</version> >> > <scope>provided</scope> >> > </dependency> >> > which means that it will pick up the file from your local .m2 directory >> > that was installed by building the shared code. >> > >> > Cheers, >> > >> > Simon >> > >> > >> > >> >> >> > > >
