Building Nexus behind Nexus

While building Nexus I got a failure because org.sonatype.spice.inject:guice-plexus:pom:1.1.0-SNAPSHOT was missing.

Like any sane Maven user, I use a local repository manager (Nexus) and I knew I had the Sonatype Forge Repo proxied in my local Nexus install so ... strange I thought.

However searching for the artifact at http://repository.sonatype.org revealed it's direct path was under http://repository.sonatype.org/service/local/repositories/snapshots/content.

After adding a proxy to that repo, I was able to build Nexus no problem. Folks on IRC confirmed this is the way to go when building behind Nexus.

Maven: How to prevent generate-sources phase executing twice

The Problem

So, you've been using Maven to build your project. You require to generate some sources, so you've figured out how to attach a plugin goal to the generate-sources lifecycle phase. This looks like it works great for a while running mvn package ....

When you decide to finally release your project using the maven-release-plugin, you notice that your source generation plugin executes twice, slowing your build and possibly even breaking it. You are now trying to figure out why your sources are being generated twice, or more specifically why the generate-sources lifecycle phase is being executed twice.

You predictably do a google search and scan the Maven issues. You find several complaints and reports open that mention a similar problem related to the maven-sources-plugin sources:jar goal causing the generate-sources phase to execute twice. Suprisingly these issues are marked fix or mention what looks like a workaround and no matter what you do, the plugin goals you have attached to the generate-sources phase are still being executed twice.

Here I attempt to explain what is really going on and provide you a real workaround for it.

History

An old relic of the maven-release-plugin is that in Maven's Super POM there is defined a profile with id of release-profile. It can be activated by the releaseProfile property being set, in this case to true. This was/is a way for the release plugin to activate the creation of source and javadoc jars for a release by default. The profile defines a maven-source-plugin and maven-javadoc-plugin configuration that attaches the jar goals of those plugins to the package phase.

So what this means is that when using the maven-release-plugin or activating the release-profile manually by setting the releaseProfile property, source:jar goal gets called during the build, which will trigger the execution of generate-sources lifecycle phase to run, even if it already did in the same build.

Changing the Maven Super POM to instead call source:jar-no-fork would fix this issue, yet changing the Super POM is not something taken lightly, and in fact may have never been proposed for this case.

Until the problem is permanently addressed, here I outline a workaround that prevents the duplicate generate-sources phase from running.

Workaround

I've tested the following instructions with Maven 2.0.11, 2.2.1 and 3.0-beta-1. The version of maven-source-plugin used was 2.1.1.

1. First lets reproduce the problem on a sample project. Using the maven-archetype-plugin is the simplest way.
   

   mvn archetype:generate
   

2. Next since the problem is that generate-sources phase gets run twice, we need a visual cue when this occurs. A simple solution is attach a message to this phase with the maven-antrun-plugin.
   
   Add the following to your test project pom.xml:
   

   <build>
     <plugins>
       <plugin>
         <artifactId>maven-antrun-plugin</artifactId>
         <version>1.3</version>
         <executions>
           <execution>
             <id>generate-sources-flag</id>
             <phase>generate-sources</phase>
             <goals>
               <goal>run</goal>
             </goals>
             <configuration>
               <tasks>
                 <echo>GENERATE SOURCES IS EXECUTING</echo>
               </tasks>
             </configuration>
           </execution>
         </executions>
       </plugin>
     </plugins>
   </build>
   

3. Next lets verify that the generate-sources phase is getting executed twice when activating the release-profile. The release profile defined in the super pom gets activated by setting the performRelease property on the cmd line.
   
   

   $mvn clean install -DperformRelease=true
   Using Java version: 1.6
   [INFO] Scanning for projects...
   [INFO]
   [INFO] ------------------------------------------------------------------------
   [INFO] Building nofork 1.0-SNAPSHOT
   [INFO] ------------------------------------------------------------------------
   [INFO]
   [INFO] --- maven-clean-plugin:2.4:clean (default-clean) @ nofork ---
   [INFO] Deleting /Users/plynch/dev/plynch/trial/nofork/target
   [INFO]
   [INFO] --- maven-antrun-plugin:1.3:run (generate-sources-flag) @ nofork ---
   [INFO] Executing tasks
        [echo] GENERATE SOURCES IS EXECUTING
   [INFO] Executed tasks
   [INFO]
   [INFO] --- maven-resources-plugin:2.4.2:resources (default-resources) @ nofork ---
   [WARNING] Using platform encoding (MacRoman actually) to copy filtered resources, i.e. build is platform dependent!
   [INFO] skip non existing resourceDirectory /Users/plynch/dev/plynch/trial/nofork/src/main/resources
   [INFO]
   [INFO] --- maven-compiler-plugin:2.3:compile (default-compile) @ nofork ---
   [WARNING] File encoding has not been set, using platform encoding MacRoman, i.e. build is platform dependent!
   [INFO] Compiling 1 source file to /Users/plynch/dev/plynch/trial/nofork/target/classes
   [INFO]
   [INFO] --- maven-resources-plugin:2.4.2:testResources (default-testResources) @ nofork ---
   [WARNING] Using platform encoding (MacRoman actually) to copy filtered resources, i.e. build is platform dependent!
   [INFO] skip non existing resourceDirectory /Users/plynch/dev/plynch/trial/nofork/src/test/resources
   [INFO]
   [INFO] --- maven-compiler-plugin:2.3:testCompile (default-testCompile) @ nofork ---
   [WARNING] File encoding has not been set, using platform encoding MacRoman, i.e. build is platform dependent!
   [INFO] Compiling 1 source file to /Users/plynch/dev/plynch/trial/nofork/target/test-classes
   [INFO]
   [INFO] --- maven-surefire-plugin:2.5:test (default-test) @ nofork ---
   [INFO] Surefire report directory: /Users/plynch/dev/plynch/trial/nofork/target/surefire-reports
   
   -------------------------------------------------------
    T E S T S
   -------------------------------------------------------
   Running com.company.AppTest
   Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.029 sec
   
   Results :
   
   Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
   
   [INFO]
   [INFO] --- maven-jar-plugin:2.3:jar (default-jar) @ nofork ---
   [INFO] Building jar: /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT.jar
   [INFO]
   [INFO] >>> maven-source-plugin:2.1.1:jar (attach-sources) @ nofork >>>
   [INFO]
   [INFO] --- maven-antrun-plugin:1.3:run (generate-sources-flag) @ nofork ---
   [INFO] Executing tasks
        [echo] GENERATE SOURCES IS EXECUTING
   [INFO] Executed tasks
   [INFO]
   [INFO] <<< maven-source-plugin:2.1.1:jar (attach-sources) @ nofork <<<
   [INFO]
   [INFO] --- maven-source-plugin:2.1.1:jar (attach-sources) @ nofork ---
   [INFO] Building jar: /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT-sources.jar
   [INFO]
   [INFO] --- maven-javadoc-plugin:2.5:jar (attach-javadocs) @ nofork ---
   [WARNING] Source files encoding has not been set, using platform encoding MacRoman, i.e. build is platform dependent!
   Loading source files for package com.company...
   Constructing Javadoc information...
   Standard Doclet version 1.6.0_17
   Building tree for all the packages and classes...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//App.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//package-frame.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//package-summary.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//package-tree.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/constant-values.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//class-use/App.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//package-use.html...
   Building index for all the packages and classes...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/overview-tree.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/index-all.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/deprecated-list.html...
   Building index for all classes...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/allclasses-frame.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/allclasses-noframe.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/index.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/help-doc.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/stylesheet.css...
   [INFO] Building jar: /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT-javadoc.jar
   [INFO]
   [INFO] --- maven-install-plugin:2.3:install (default-install) @ nofork ---
   [INFO] Installing /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT.jar to /Volumes/D/m2r/com/company/nofork/1.0-SNAPSHOT/nofork-1.0-SNAPSHOT.jar
   [INFO] Installing /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT-sources.jar to /Volumes/D/m2r/com/company/nofork/1.0-SNAPSHOT/nofork-1.0-SNAPSHOT-sources.jar
   [INFO] Installing /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT-javadoc.jar to /Volumes/D/m2r/com/company/nofork/1.0-SNAPSHOT/nofork-1.0-SNAPSHOT-javadoc.jar
   [INFO] ------------------------------------------------------------------------
   [INFO] BUILD SUCCESS
   [INFO] ------------------------------------------------------------------------
   [INFO] Total time: 11.162s
   [INFO] Finished at: Thu May 13 10:39:58 EDT 2010
   [INFO] Final Memory: 13M/264M
   [INFO] ------------------------------------------------------------------------
   

   
   Notice our message gets printed twice, verifying the double execution. So lets proceed to fix the problem.
   
4. Make the following additions to your pom.xml.
   
   1. First we override the super-pom maven-sources-plugin execution with id of attach-sources. This excution is what calls the source:jar goal. The special trick used here binds this execution to a non-existent lifecycle phase of DISABLE_FORKED_LIFECYCLE_MSOURCES-13 - a phase which will never be reached, thus essentially disabling this execution.
      
      

      <pluginManagement>
        <plugins>
          <plugin>
            <artifactId>maven-source-plugin</artifactId>
            <version>2.1.1</version>
            <executions>
              <!-- here we override the super-pom attach-sources executionid which
              calls sources:jar goal. That goals forks the lifecycle, causing
              the generate-sources phase to be called twice for the install goal.
              This causes any other plugin bound to the generate-sources phase to
              be called twice which usually has nasty side effects, let alone
              creating duplicate processing and longer build times. -->
              <execution>
                <id>attach-sources</id>
                <phase>DISABLE_FORKED_LIFECYCLE_MSOURCES-13</phase>
              </execution>
            </executions>
          </plugin>
        </plugins>
      </pluginManagement>
      

   2. Next, since we would still like releases using the release-profile profile to include a sources jar file, we define a new profile with the same id as the one in the super POM. This time however we bind the execution to the jar-no-fork goal, which does not trigger the generate-sources phase to be called twice.
      
      

      <profiles>
        <!-- MSOURCES-13 related workaround overriding super-pom -->
        <profile>
          <id>release-profile</id>
          <activation>
            <property>
              <name>performRelease</name>
              <value>true</value>
            </property>
          </activation>
          <build>
            <plugins>
              <plugin>
                <inherited>true</inherited>
                <artifactId>maven-source-plugin</artifactId>
                <executions>
                  <execution>
                    <id>attach-sources-no-fork</id>
                    <inherited>true</inherited>
                    <goals>
                      <goal>jar-no-fork</goal>
                    </goals>
                  </execution>
                </executions>
              </plugin>
            </plugins>
          </build>
        </profile>
      </profiles>
      

5. Now we run the same command and verify that our solution worked.
   

   $mvn clean install -DperformRelease=true
   Using Java version: 1.6
   [INFO] Scanning for projects...
   [INFO]
   [INFO] ------------------------------------------------------------------------
   [INFO] Building nofork 1.0-SNAPSHOT
   [INFO] ------------------------------------------------------------------------
   [INFO]
   [INFO] --- maven-clean-plugin:2.4:clean (default-clean) @ nofork ---
   [INFO] Deleting /Users/plynch/dev/plynch/trial/nofork/target
   [INFO]
   [INFO] --- maven-antrun-plugin:1.3:run (generate-sources-flag) @ nofork ---
   [INFO] Executing tasks
        [echo] GENERATE SOURCES IS EXECUTING
   [INFO] Executed tasks
   [INFO]
   [INFO] --- maven-resources-plugin:2.4.2:resources (default-resources) @ nofork ---
   [WARNING] Using platform encoding (MacRoman actually) to copy filtered resources, i.e. build is platform dependent!
   [INFO] skip non existing resourceDirectory /Users/plynch/dev/plynch/trial/nofork/src/main/resources
   [INFO]
   [INFO] --- maven-compiler-plugin:2.3:compile (default-compile) @ nofork ---
   [WARNING] File encoding has not been set, using platform encoding MacRoman, i.e. build is platform dependent!
   [INFO] Compiling 1 source file to /Users/plynch/dev/plynch/trial/nofork/target/classes
   [INFO]
   [INFO] --- maven-resources-plugin:2.4.2:testResources (default-testResources) @ nofork ---
   [WARNING] Using platform encoding (MacRoman actually) to copy filtered resources, i.e. build is platform dependent!
   [INFO] skip non existing resourceDirectory /Users/plynch/dev/plynch/trial/nofork/src/test/resources
   [INFO]
   [INFO] --- maven-compiler-plugin:2.3:testCompile (default-testCompile) @ nofork ---
   [WARNING] File encoding has not been set, using platform encoding MacRoman, i.e. build is platform dependent!
   [INFO] Compiling 1 source file to /Users/plynch/dev/plynch/trial/nofork/target/test-classes
   [INFO]
   [INFO] --- maven-surefire-plugin:2.5:test (default-test) @ nofork ---
   [INFO] Surefire report directory: /Users/plynch/dev/plynch/trial/nofork/target/surefire-reports
   
   -------------------------------------------------------
    T E S T S
   -------------------------------------------------------
   Running com.company.AppTest
   Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.026 sec
   
   Results :
   
   Tests run: 1, Failures: 0, Errors: 0, Skipped: 0
   
   [INFO]
   [INFO] --- maven-jar-plugin:2.3:jar (default-jar) @ nofork ---
   [INFO] Building jar: /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT.jar
   [INFO]
   [INFO] --- maven-source-plugin:2.1.1:jar-no-fork (attach-sources-no-fork) @ nofork ---
   [INFO] Building jar: /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT-sources.jar
   [INFO]
   [INFO] --- maven-javadoc-plugin:2.5:jar (attach-javadocs) @ nofork ---
   [WARNING] Source files encoding has not been set, using platform encoding MacRoman, i.e. build is platform dependent!
   Loading source files for package com.company...
   Constructing Javadoc information...
   Standard Doclet version 1.6.0_17
   Building tree for all the packages and classes...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//App.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//package-frame.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//package-summary.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//package-tree.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/constant-values.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//class-use/App.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/com/company//package-use.html...
   Building index for all the packages and classes...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/overview-tree.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/index-all.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/deprecated-list.html...
   Building index for all classes...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/allclasses-frame.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/allclasses-noframe.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/index.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/help-doc.html...
   Generating /Users/plynch/dev/plynch/trial/nofork/target/apidocs/stylesheet.css...
   [INFO] Building jar: /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT-javadoc.jar
   [INFO]
   [INFO] --- maven-install-plugin:2.3:install (default-install) @ nofork ---
   [INFO] Installing /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT.jar to /Volumes/D/m2r/com/company/nofork/1.0-SNAPSHOT/nofork-1.0-SNAPSHOT.jar
   [INFO] Installing /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT-sources.jar to /Volumes/D/m2r/com/company/nofork/1.0-SNAPSHOT/nofork-1.0-SNAPSHOT-sources.jar
   [INFO] Installing /Users/plynch/dev/plynch/trial/nofork/target/nofork-1.0-SNAPSHOT-javadoc.jar to /Volumes/D/m2r/com/company/nofork/1.0-SNAPSHOT/nofork-1.0-SNAPSHOT-javadoc.jar
   [INFO] ------------------------------------------------------------------------
   [INFO] BUILD SUCCESS
   [INFO] ------------------------------------------------------------------------
   [INFO] Total time: 24.278s
   [INFO] Finished at: Fri May 14 07:56:39 EDT 2010
   [INFO] Final Memory: 13M/264M
   [INFO] ------------------------------------------------------------------------
   

   As you can see, our verification message prints only once, yet we still get the sources jar - a good thing!
   

I recommend the above config be considered for adding to your organization's root pom. I also suggest the permanent solution to this issue is changing the Maven super pom release-profile to rely on jar-no-fork instead of jar goal.

Update

I'm occasionally asked how to make sure you still get a sources jar for your SNAPSHOT artifacts. Simple!

Just add the following to your normal <build> section of your pom, in addition to all of the above instructions:

  <plugins>
    <plugin>
      <artifactId>maven-source-plugin</artifactId>
      <executions>
        <execution>
          <id>attach-sources-no-fork</id>
          <inherited>true</inherited>
          <phase>generate-sources</phase>
          <goals>
            <goal>jar-no-fork</goal>
          </goals>
        </execution>
      </executions>
    </plugin>  
  </plugins>

Maven plugin groupId org.codehaus.mojo not searched by default??

I got interested in removing all my explicit org.codehaus.mojo declarations on my plugin dependencies since now Maven supports searching that groupId for a plugin's artifactId. This feature was added a while ago I guess.

Just came across a nasty little bug in Maven 2.2.1 which has been reported since 2.0.9.

[#MNG-4001] Unable to resolve Dashboard mojo from Central - jira.codehaus.org

The summary above is very misleading. In fact I consider myself lucky to find it since it more has to do with any org.codehaus.mojo based plugin.

When I did try to remove my plugin's groupIds I got the classic "Unable to find resource 'org.apache.maven.plugins:buildnumber-maven-plugin:pom:1.0-beta-4' in repository central".

Turns out this may be related to maven metadata in my local repo and/or the remote repos being randomly deleting version info???? See the bug followups for more info.

In fact this bug is nasty because
1. there is no mention in the error that is what could be wrong.
2. Adding a pluginGroups section to your ~/.m2/settings.xml file with that group changes nothing, even in the error output. Plus using -X shows that maven does not even try to locate org.codehaus.mojo version of that plugin or any other groupId specified in your pluginGroups settings. It may have looked at the metadata, but we would never know.
3. Deleting your local maven metadata may only fix the error temporarily or not at all.
4. Try this: Define your plugin configuration in pluginManagement without the groupId. Next, define the same plugin in a profile with the groupId. Run a mvn cmd that activates the profile and you will notice that none of your plugin settings inside plguinManagement gets picked up - and of course there is no warning or messages in the debug output that complain. Add the group id to the pluginManagement section and it all of a sudden works as expected.

So the rule of thumb is leave well enough alone and always explicitly specify the groupId for all plugins except org.apache.maven.plugins groupId which still work.

buildnumber-maven-plugin helpful improvements

I've used the buildnumber-maven-plugin to include revision ids and timestamps in my builds for many years. Today I upgraded to the most recent version and that helped get rid of a few workarounds I had in place.

Using a previous version of the plugin, if there was no svn on your path, or your project was not checked in yet to subversion, the plugin failed the build due to svn checks. The workaround I had was to add it to a profile that only got executed when .svn file existed and/or the useReleaseProfile property was 'true'.

Now I am relieved to see I don't need to do that anymore.

For one, there is a 'revisionOnScmFailure' property you can set in the configuration that will be used if there is any type of scm exception - a byproduct of which disables further scm communication.

Second you can specify the plugin to use the javasvn scm provider implementation in case there is no 'svn' executable on your PATH. At first pass it might seem unlikely that when dealing with a subversion based project a developer would not have svn on the path, and that is likely true. Consider though that the svn version may be wrong (in which case svn may complain about not being new enough and fail the build) or you are building in a continuous integration env like hudson and you want reproducible use of the same svn tool. In those cases it makes good sense to configure the plugin with "javasvn". See below example:

<plugin>
  <groupid>org.codehaus.mojo</groupid>
  <artifactid>buildnumber-maven-plugin</artifactid>
  <version>1.0-beta-4</version>
  <configuration>
    <revisiononscmfailure>UNKNOWN_REVISION</revisiononscmfailure>
    <providerimplementations>
      <svn>javasvn</svn>
    </providerimplementations>
  </configuration>
  <executions>
    <execution>
      <id>buildnumber-one</id>
      <phase>validate</phase>
      <goals>
        <goal>create</goal>
      </goals>
    </execution>
    <execution>
      <id>buildnumber-two</id>
      <phase>validate</phase>
      <goals>
        <goal>create</goal>
      </goals>
      <configuration>
        <format>r${buildNumber} {0,date,yyyy-MM-dd'T'HH:mm:ss.SSSZ}</format>
        <items>
          <item>timestamp</item>
        </items> 
      </configuration>
    </execution>
  </executions>
</plugin>

The two executions is so that I can give some context to the ${buildNumber} by prefixing it with 'r' and adding a timestamp formatted along with it.

There are a bunch of other useful properties in this latest release. Thanks to open source.

Mac OS X environment variables + Netbeans + Maven

Applications that are not launched through your terminal in OS X do not read environment variables from ~/.profile, ~/.bash_profile and similar. These applications that launch directly can get their environment from each user's ~/.MacOSX/environment.plist file. ( You have to create it!)

I heard of this before, but I wanted to make note of a quick way to ease the maintaining of that file and finally had a need because of Netbeans.

1. Downloaded Brian D Foy's Perl plist lib and installed it.
2. Used a 3 line script to generate the ~/.MacOSX/environment.plist file from my terminal's ENV variable as he suggested.
3.  Log out and log in for the file to take effect.
   

Now I can be sure the PATH that Netbeans sees is the same thing that mvn and other tools are seeing when I execute them on the cmd line. Also I don't really have to worry about maintaining my env in two places as one is derived from the other.

References
Technical Q&A QA1067: Setting environment variables for user processes
Helpful Summary of other ways to set env variables in OS X
Brian D Foy's Perl plist reader lib and blog post
Netbeans documentation on working with OS X Environment variables

Update
Another method is setting environment variables inside your

/etc/launchd.conf

file as described here - there are clear benefits to this for apps launched outside your personal login.

Maven Special Character Encoding Properties for Sites and Reports

Thanks to the post on the Sonatype blog I've got two other global properties to set in my global parent pom that sets the encoding for Maven reports - most of them anyways.

Sonatype Blog: Special Character Encoding Properties

project.build.sourceEncoding
project.reporting.outputEncoding

Thanks for the summary Anders Hammar.