search

batchu / owasp-esapi-java

Automatically exported from code.google.com/p/owasp-esapi-java
0 stars 0 forks source link

Maven build housekeeping #113

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
General tidy up of the POM whilst focusing on the following areas:

* Use Maven convention for development version number;

* Build must produce a clean artifact, such that test code and resources aren't 
included. 
However, esapi.tld must remain. There is a question over whether 
owasp-esapi-dev.jks;

* Execute the JAVADOC command to build JavaDoc for the current version;

* Execute the SITE command in a complete way for part of the deployment;

This is useful ground work towards resolving Issue #63.

Original issue reported on code.google.com by jonathan...@gmail.com on 24 Mar 2010 at 8:19

GoogleCodeExporter commented 8 years ago 
Fixed in r1237.

Relates to Issue 113. Tidied up full build process by introducing a dist 
profile for creating a distribution zip for the project (using the 
Maven Assembly plugin). The dist includes sources, libs, the site etc... To 
invoke you first need to increase the Maven heap size (if you 
haven't done so already e.g. "export MAVEN_OPTS=-Xmx512m") and then run "mvn 
clean site -Pdist". Once the build has completed you 
should find a zip file in the target named esapi-${version}-dist.zip.  

Currently JAR signing is commented out like in the original pom. The main 
change I've made to this is to move the jks file to a top level 
resources directory and externalise the storepass etc... To get this working 
you need to remove the comments from the maven-jar-plugin 
and take the dist profile from resources/settings.xml and place it in your own 
Maven settings file. I did this so we could remove any 
sensitive information relating to the signing out of the pom.

Original comment by jonathan...@gmail.com on 13 Apr 2010 at 5:51