james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bernd Waibel (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-1563) Switch to Maven3
Date Fri, 31 Oct 2014 09:32:34 GMT

    [ https://issues.apache.org/jira/browse/JAMES-1563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14191634#comment-14191634

Bernd Waibel commented on JAMES-1563:

Switching from Maven2 to Maven3 has a effekt on the maven-site-plugin.
Because the project "org.sonatype.aether" has been moved from one project to another, there
are incompatibilities.
If of interest, details here: https://cwiki.apache.org/confluence/display/MAVEN/AetherClassNotFound.
It is easy to fix this issues, just use v3.4 of the maven-site-plugin.

It is possible to configure this as a maven profile, so you can build both with Maven2 and
So the patch will provide a profile for maven3, which (automatically) only will be used if
maven3 has been called for building.
Also to do a succesful build you need the maven-project-info-reports-plugin, which is also
mentioned in the profile.

This pom.xml builds completely inside eclipse with Maven3.2.1, for the site command it builds
with Maven 3.2.3.

> Switch to Maven3
> ----------------
>                 Key: JAMES-1563
>                 URL: https://issues.apache.org/jira/browse/JAMES-1563
>             Project: James Server
>          Issue Type: Improvement
>          Components: Build System
>    Affects Versions: Trunk, 3.0.0-beta5
>         Environment: Eclipse LUNA with integrated Mave 3.2.1 (m2eclipse)
> Together with Maven 3.2.3 
>            Reporter: Bernd Waibel
>            Priority: Minor
>             Fix For: 3.0.0-beta5
>         Attachments: maven3.patch
>   Original Estimate: 1h
>  Remaining Estimate: 1h
> Building with old maven in actual eclipse is some kind outdated.
> It is easy possible to switch to maven 3, with the following changes:
> 1. Eclipse Luna with Maven 3.2.1 is ok for: mvn install, package, clean. Not for mvn
> 2. Maven 3.2.3 is ok for mvn install, package, clean, site.
> The Maven 3.2.1 could not build the site, because the structure on "http://repo.maven.apache.org/maven2/"
is wrong. The structure is from 2012 and for Maven2, so maybe the structure need to get updated.
Nothing I can do.
> For switching to Maven3, which I did, you need to change the pom.xml. Details and patch
will follow.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message