geronimo-scm mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Geronimo Wiki] Update of "Building" by JacekLaskowski
Date Tue, 06 Sep 2005 10:03:11 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Geronimo Wiki" for change notification.

The following page has been changed by JacekLaskowski:
http://wiki.apache.org/geronimo/Building

The comment on the change is:
A build problem with the older xmlbeans plugin

------------------------------------------------------------------------------
  J2SE SDK 	
  	I used sun jdk 1.4.2_04
  	[http://java.sun.com/j2se/1.4.2/]
- Maven 
+ Apache Maven 
- 	Use maven-1.0.2. Previous versions have a bug that breaks the Geronimo build.  The builds
currently fails with Maven 1.1-beta-1.
+ 	maven-1.0.2. Previous versions have a bug that breaks the Geronimo build.  The builds currently
fails with Maven 1.1-beta-1.
  	[http://maven.apache.org/]
  subversion
- 	I used svn-1.2.0
- 	[http://subversion.tigris.org/]
+ 	svn-1.2.0 [http://subversion.tigris.org/]
  CVS
- 	I used wincvs120
- 	[http://www.wincvs.org/]
+ 	wincvs120 [http://www.wincvs.org/]
  
  The executables maven.exe, cvs.exe and svn.exe needs to be in the system PATH.
  
@@ -231, +229 @@

  
  = Problems? =
  
- If having problems building Geronimo, make sure it isn't simply because your Maven repository
has become 'corrupted' or out of sync:
+ If having problems building Geronimo, make sure it isn't simply because your Maven repository
has become 'corrupted' or out of sync. Delete (or temporarily rename) the .maven directory
in your home directory (~ - the tilde - on Unix and %USERPROFILE% on MS Windows) and try building
Geronimo again. Make sure that you're online because the dependencies need to be downloaded
again.
  
- Delete (or temporarily rename) the .maven directory in your home directory and try building
Geronimo again.
- 
- (Under UNIX this is typically in /home/yourusername whilst under Windows this is typically
in C:\Documents and Settings\yourusername)
- 
- Running the command `maven site` seems to take up a lot of memory.  If you get an out of
memory error, try setting MAVEN_OPTS=-Xmx512m.
+ Running the command `maven site` seems to take up a lot of memory.  If you get the `java.lang.OutOfMemoryError`,
try setting `MAVEN_OPTS=-Xmx512m` and rerun maven.
  
  One of the many reasons that tests fail is because some ports are in use by other programs
(for example another copy of Geronimo running on the same machine).  Check the log of the
test reports for the specific module that failed in the `target/test-reports` directory and
see if it does use a port that is already active.  You can use a program called TCPView (http://www.sysinternals.com/ntw2k/source/tcpview.shtml)
to determine which ports are in use by which program and if they are conflicting with ListOfPortsUsedDuringTesting.
  
@@ -263, +257 @@

  We now use a single global repository list which is way easier to  maintain. In maven 1.0
and 1.0.1 there was a bug that caused a  module to not inherit the repo list from the parent
project.
  }}}                                                                                    
  
  
-  If you still have problems, it might be due to an own definiton for "maven.repo.remote"
in your ${user.home}/build.properties file. Geronimo uses an own properties file (located
in the etc directory) setting the remote repo. If you have an own definition in your user
directory, this will override the Geronimo setting and there dependencies might not be found
anymore. You can either temporarily remove the settings from the properties file in your home
directory or add the settings from the Geronimo properties file to your own - concatenating
both information.
+  If you still have problems, it might be due to an own definiton for "maven.repo.remote"
in your ${user.home}/build.properties file. Geronimo uses its own properties file (located
in the etc directory) setting the remote repo. If you have your own definition in your user
directory, this will override Geronimo's setting and the dependencies might not be found anymore.
You can either temporarily remove the settings from the properties file in your home directory
or add the settings from the Geronimo properties file to your own - concatenating both information.
  
  == Tests fail with java.net.BindException : Address already in use: connect on Windows ==
  
@@ -414, +408 @@

  Total time: 6 seconds
  }}}
  
+ == Unable to obtain goal [default] -- <home.dir>\.maven\cache\xmlbeans-maven-plugin-2.0.0-beta1\plugin.jelly:24:23:
==
+ 
+ This is usually caused by having an old `xmlbeans-maven-plugin-2.0.0-beta1` from Geronimo
installed in your `.maven/cache` and `$MAVEN_HOME/plugins` directories.  Unfortunately, it
wasn't realized that groupId would be ignored in comparing plugin versions when the version
number for the xmlbeans version of this plugin was suggested.  It seems that deleting the
.maven/cache contents and removing the xmlbeans-maven-plugin-2.0.0-beta1.jar from $MAVEN_HOME/plugins
solves the issue - the the correct version and build of the plugin will be downloaded provided
you're '''online'''.
+ 
  = Improved Maven IDEA plugin =
  
  If you use Intellij IDEA, you might like to try this patched version of the maven-idea-plugin.
 It contains the changes from MPIDEA-13 plus a couple of enhancements from other maven idea
plugin patches.  When I get a little time I'll update the maven jira issue.

Mime
View raw message