MAVEN - Revision history

James: Maven build retired in favor of gradle.

2014-07-05T06:14:04Z

Maven build retired in favor of gradle.

Karianna: /* Maven For Autobuilds */

2008-09-02T12:54:04Z

‎Maven For Autobuilds

Karianna: /* Introduction */

2008-09-02T12:53:45Z

‎Introduction

Karianna: New page: {| align="right" | TOC |} =Introduction= '''NB''' Maven is not yet ready for building a finished installation. Use ant for that until the maven build fully catches up. Maven is c...

2008-09-02T12:53:16Z

New page: {| align="right" | __TOC__ |} =Introduction= '''NB''' Maven is not yet ready for building a finished installation. Use ant for that until the maven build fully catches up. Maven is c...

New page

{| align="right"
| __TOC__
|}

=Introduction=

'''NB''' Maven is not yet ready for building a finished installation. Use ant for that until the maven build fully catches up. Maven is currently used to generate a site full of extremely useful reports about the code quality of PCGen. See [[Maven Release Process]] for what is planned for the release process.

The new monkey on the tree is Maven. It builds on ant and simplifies the build script maintenance considerably. Here is how you can run maven:

# Get maven from the Apache Maven site. Get Maven 1.1. Maven 2.0.9 works with PCGen, but we need to put some work into the conversion.
# Unpack it wherever you will. Add these two environment variables for yourself (the example is for Windows, adjust accordingly for other platforms):

{{MAVEN_HOME=wherever you unpacked maven}}, e.g., {{C:\maven-1.1}}
{{PATH=%MAVEN_HOME%\bin;%PATH%}}

# Open a command line, change to where you fetched PCGen from SVN, and test maven: ''maven -q'', you should get no output if successful; (without -q, huge banner will appear). If all is not well, please refer to the Maven 1 documentation or drop one of the lists a line with your situation.
# Build pcgen and run the tests: ''maven test'', you should see lots of output, hopefully a tests successful at the end
# Build the site documentation and code metrics: ''maven site'', this will take some time to complete and you should see lots of output, hopefully a finished site at the end! If ''maven site'' works for you, point a browser at ''target/docs/index.html'' and see the result.

You are now ready to use Maven for command line builds.

'''NB''' You can also use maven integration with your IDE (Eclipse and IDEA both support ant with extensions, plugins or tools).

=Maven For Autobuilds=

Do not use this yet, this is WIP

* maven -DentityExpansionLimit=100000 scm:bootstrap
* you need a build.properties that has:

maven.scm.url=scm:svn:https://svn.sourceforge.net/svnroot/pcgen/Trunk
maven.scm.bootstrap.goals=site
maven.scm.bootstrap.pom.dir=pcgen
maven.scm.checkout.dir=pcgen_Trunk
maven.scm.username=pcgen_autobuild
maven.scm.password=password123456

← Older revision		Revision as of 06:14, 5 July 2014
Line 5:		Line 5:
	=Introduction=		=Introduction=

−	'''NB''' Maven is not yet ready for building a finished installation. Use ant for that until the maven build fully catches up. Maven is currently used to generate a site full of extremely useful reports about the code quality of PCGen. See [[Maven Release Process]] for what is planned for the release process.	+	The maven build has now been replaced by Gradle.
−
−	The ~~new monkey on the tree is Maven. It builds on ant and simplifies the build script maintenance considerably. Here is how you can run maven:~~
−
−	~~# Get~~ maven ~~from the Apache Maven site. Get Maven 1.1. Maven 2.0.9 works with PCGen, but we need to put some work into the conversion.~~
−	~~# Unpack it wherever you will. Add these two environment variables for yourself (the example is for Windows, adjust accordingly for other platforms):~~
−
−	~~''MAVEN_HOME=wherever you unpacked maven'', e.g., ''C:\maven-1.1''<br>~~
−	~~''PATH=%MAVEN_HOME%\bin;%PATH%''~~
−
−	# Open a command line, change to where you fetched PCGen from SVN, and test maven: ''maven -q'', you should get no output if successful; (without -q, huge banner will appear). If all is not well, please refer to the Maven 1 documentation or drop one of the lists a line with your situation.
−	~~# Build pcgen and run the tests: ''maven test'', you should see lots of output, hopefully a tests successful at the end~~
−	# Build the site documentation and code metrics: ''maven site'', this will take some time to complete and you should see lots of output, hopefully a finished site at the end! If ''maven site'' works for you, point a browser at ''target/docs/index.html'' and see the result.
−
−	~~You are now ready to use Maven for command line builds.~~
−
−	~~'''NB''' You can also use maven integration with your IDE (Eclipse and IDEA both support ant with extensions, plugins or tools).~~
−
−	~~=Maven For Autobuilds=~~
−
−	~~Do not use this yet, this is WIP~~
−
−	* maven -DentityExpansionLimit=100000 scm:bootstrap
−	* you need a build~~.properties that~~ has:
−
−	~~maven.scm.url=scm:svn:https://svn.sourceforge.net/svnroot/pcgen/Trunk<br>~~
−	~~maven.scm.bootstrap.goals=site<br>~~
−	~~maven.scm.bootstrap.pom.dir=pcgen<br>~~
−	~~maven.scm.checkout.dir=pcgen_Trunk<br>~~
−	~~maven.scm.username=pcgen_autobuild<br>~~
−	~~maven.scm~~.~~password=password123456~~

@@ Line 30: / Line 30: @@
 * you need a build.properties that has:
-maven.scm.url=scm:svn:https://svn.sourceforge.net/svnroot/pcgen/Trunk
+maven.scm.url=scm:svn:https://svn.sourceforge.net/svnroot/pcgen/Trunk<br>
-maven.scm.bootstrap.goals=site
+maven.scm.bootstrap.goals=site<br>
-maven.scm.bootstrap.pom.dir=pcgen
+maven.scm.bootstrap.pom.dir=pcgen<br>
-maven.scm.checkout.dir=pcgen_Trunk
+maven.scm.checkout.dir=pcgen_Trunk<br>
-maven.scm.username=pcgen_autobuild
+maven.scm.username=pcgen_autobuild<br>
 maven.scm.password=password123456

@@ Line 12: / Line 12: @@
 # Unpack it wherever you will. Add these two environment variables for yourself (the example is for Windows, adjust accordingly for other platforms):
-{{MAVEN_HOME=wherever you unpacked maven}}, e.g., {{C:\maven-1.1}}
+''MAVEN_HOME=wherever you unpacked maven'', e.g., ''C:\maven-1.1''<br>
-{{PATH=%MAVEN_HOME%\bin;%PATH%}}
+''PATH=%MAVEN_HOME%\bin;%PATH%''
 # Open a command line, change to where you fetched PCGen from SVN, and test maven: ''maven -q'', you should get no output if successful; (without -q, huge banner will appear). If all is not well, please refer to the Maven 1 documentation or drop one of the lists a line with your situation.

MAVEN - Revision history

James: Maven build retired in favor of gradle.

Karianna: /* Maven For Autobuilds */

Karianna: /* Introduction */

Karianna: New page: {| align="right" | __TOC__ |} =Introduction= '''NB''' Maven is not yet ready for building a finished installation. Use ant for that until the maven build fully catches up. Maven is c...

Karianna: New page: {| align="right" | TOC |} =Introduction= '''NB''' Maven is not yet ready for building a finished installation. Use ant for that until the maven build fully catches up. Maven is c...