Updates: The problem is only the build-number plug-in. Currently it seems to require command-line svn to work regardless of whether m2eclipse or a command-line build is used. m2eclipse otherwise seems to integrate properly in Galileo with Subclipse (I will test with the Subversive integration later). I assume we don't need the build number for development but only for a release so using a default may do the trick.
Care needs to be taken to ensure that the local Maven repository settings are consistent. m2eclipse uses the users settings (or default users settings) and the command-line mvn uses its default settings. If the user settings in place before first creating the fedora-repository project using m2eclipse both the global dependencies are download and the installLibs.bat puts things in the users repository. However, building from the command-line creates a new repository and ignores the users settings. Simple fix is ensure both the global setting file and the users settings files exist and both point to the same local repository if you intend to build from both the command-line and using m2eclipse. If you choose not to run the tests in m2eclipse the build will fail because the tests will not be built (with the clean install goals). Daniel W. Davis Andrew Woods wrote: > The build-number plugin has a configuration element that provides a > default 'build number value' if the svn connection fails. > That is currently not set... but maybe it should be added to the root pom.xml. > > > On Tue, Jul 14, 2009 at 7:20 AM, Chris Wilper<cwil...@fedora-commons.org> > wrote: > >> Thanks for this writeup on your experiences...it would probably be >> good for the dev mailing list...I have actually only attempted >> building in maven via commandline so far. It looks like the >> buildnumber plugin depends on being able to run "svn" (and likely the >> plugin is not aware of eclipse). It'd be nice if builds could be run >> offline (provided all the dependencies are in your local repo). I'm >> not sure how we'd do that while still having build numbering enabled. >> I'm also not sure if m2eclipse is capable of installing local >> artifacts. >> >> On Mon, Jul 13, 2009 at 11:13 AM, Daniel Davis<dda...@fedora-commons.org> >> wrote: >> >>> I installed Maven on the command-line in Windows per our discussion and >>> ensured the user settings file pointed to the local repository. I ran the >>> installLibs.bat and the temporary local artifacts were created properly. >>> Eclipse (Galileo) seems very happy at this point. But I ran into a new >>> configuration issue that I wanted to discuss before putting time into it. A >>> build using the goals of "clean install" fails because the Maven build >>> process cannot find "svn" on the command-line. In theory, I would expect >>> m2eclipse to use the Eclipse svn plug-in. >>> >>> I was curious if you have succesfully built? Do you have "svn" on your >>> Windows path? >>> >>> This is a work in process but some things that I suspect: >>> >>> If using m2clipse you do not need Maven installed on the command line except >>> to run installLibs.bat (or likely .sh in Linux). You want to for supporting >>> builds outside Eclipse for other reasons. You DO need a local repository >>> and I don't know if m2eclipse has any way to install local artifacts other >>> than those actually built or downloaded in Eclipse as Maven projects. >>> >>> Like running Ant "build as" targets, some Maven tasks only know how to use >>> command-line integrations. I have no idea which ones so far. >>> >>> Notes: >>> >>> I have one Galileo with Subclipse and one with Subversive to see the >>> differences in the integrations. The Subversive integrations are new with >>> Galileo and not well documented yet. I have one installation using >>> Subclipse with Ganymede to act as a reference but it still has the problems >>> with the command-line svn. >>> >>> The "Create Project from Maven" works properly once a local repository is >>> set up. Because the local artifacts are needed for dependency checks during >>> project creation, this step needs to be done first or Eclipse goes nuts >>> trying to look for the artifacts in external repositories. When we get them >>> publicly registered this will take care of the problem but I wonder how >>> newly created projects are handled. It may simply be that Eclipse currently >>> is matching dependent projects to poms but those poms don't have local >>> dependencies yet, as Andrew described, at this point in refactoring the code >>> base. >>> >>> In "online mode": >>> >>> [INFO] Scanning for projects... >>> [INFO] Reactor build order: >>> [INFO] Fedora Repository >>> [INFO] Generate >>> [INFO] Common >>> [INFO] Server >>> [INFO] Client >>> [INFO] Integration Test >>> [INFO] Local Services >>> [INFO] Formatting Objects Processor Webapp >>> [INFO] Advanced Imaging Webapp >>> [INFO] Saxon XSLT Processor Webapp >>> [INFO] Fedora Demo Content Webapp >>> [INFO] Installer >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Building Fedora Repository >>> [INFO] >>> [INFO] Id: org.duraspace.fedora:fedora-repository:pom:1.0.0 >>> [INFO] task-segment: [clean, install] >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] [clean:clean] >>> [INFO] [buildnumber:create] >>> [INFO] Checking for local modifications: skipped. >>> [INFO] Updating project files from SCM: skipped. >>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive info" >>> [INFO] Working directory: C:\workspaces\Master\fedora-repository >>> Provider message: >>> The svn command failed. >>> Command output: >>> 'svn' is not recognized as an internal or external command, >>> operable program or batch file. >>> >>> [ERROR] >>> >>> The following mojo encountered an error while executing: >>> Group-Id: org.codehaus.mojo >>> Artifact-Id: buildnumber-maven-plugin >>> Version: 1.0-beta-3 >>> Mojo: create >>> brought in via: POM >>> >>> While building project: >>> Group-Id: org.duraspace.fedora >>> Artifact-Id: fedora-repository >>> Version: 1.0.0 >>> From file: C:\workspaces\Master\fedora-repository\pom.xml >>> Reason: Cannot get the revision information from the scm repository : >>> Error! >>> >>> >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] For more information, run with the -e flag >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] BUILD FAILED >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Total time: 4 seconds >>> [INFO] Finished at: Mon Jul 13 11:12:42 EDT 2009 >>> [INFO] Final Memory: 4M/19M >>> [INFO] >>> ------------------------------------------------------------------------ >>> >>> >>> In "offline mode": >>> >>> [INFO] You are working in offline mode. >>> [INFO] Scanning for projects... >>> [INFO] Reactor build order: >>> [INFO] Fedora Repository >>> [INFO] Generate >>> [INFO] Common >>> [INFO] Server >>> [INFO] Client >>> [INFO] Integration Test >>> [INFO] Local Services >>> [INFO] Formatting Objects Processor Webapp >>> [INFO] Advanced Imaging Webapp >>> [INFO] Saxon XSLT Processor Webapp >>> [INFO] Fedora Demo Content Webapp >>> [INFO] Installer >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Building Fedora Repository >>> [INFO] >>> [INFO] Id: org.duraspace.fedora:fedora-repository:pom:1.0.0 >>> [INFO] task-segment: [clean, install] >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] [clean:clean] >>> [INFO] [buildnumber:create] >>> [INFO] Checking for local modifications: skipped. >>> [INFO] Updating project files from SCM: skipped. >>> [INFO] Executing: cmd.exe /X /C "svn --non-interactive info" >>> [INFO] Working directory: C:\workspaces\Master\fedora-repository >>> Provider message: >>> The svn command failed. >>> Command output: >>> 'svn' is not recognized as an internal or external command, >>> operable program or batch file. >>> >>> [ERROR] >>> >>> The following mojo encountered an error while executing: >>> Group-Id: org.codehaus.mojo >>> Artifact-Id: buildnumber-maven-plugin >>> Version: 1.0-beta-3 >>> Mojo: create >>> brought in via: POM >>> >>> While building project: >>> Group-Id: org.duraspace.fedora >>> Artifact-Id: fedora-repository >>> Version: 1.0.0 >>> From file: C:\workspaces\Master\fedora-repository\pom.xml >>> Reason: Cannot get the revision information from the scm repository : >>> Error! >>> >>> >>> >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] For more information, run with the -e flag >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] BUILD FAILED >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Total time: 4 seconds >>> [INFO] Finished at: Mon Jul 13 10:38:23 EDT 2009 >>> [INFO] Final Memory: 4M/19M >>> [INFO] >>> ------------------------------------------------------------------------ >>> ------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge _______________________________________________ Fedora-commons-developers mailing list Fedora-commons-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fedora-commons-developers
