[jira] [Commented] (JAMES-1563) Switch to Maven3

["Bernd Waibel (JIRA)" <se...@james.apache.org>]

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

Bernd Waibel commented on JAMES-1563:
-------------------------------------

We switched to mv-3.3.9, works fine. I do not have any opinion about maven 2 support. Does not matter to me.

The m2e plugin in eclipse (mars) works fine, but it does have a bug: it just uses the wrong directory for "install".
So we run an external mvn command, instead the internal mvn build in eclipse. It is a bug of the eclipse-plugin, so it does not matter here.
But: the m2e plugin works fine based on the pom.xml. Does everything else, like clean, profile management, and so on.

We integrated it in jenkins, with deployment to our artifactory. There are problems with the pom, but this is based on our artifactory.
So not of interest in this ticket.

We are now running two build processes:
- local build in eclipse, with m2e maven plugin, and mvn 3.3.9.
- central build with jenkins, git, maven, and artifactory.
Works fine, all parts.

Offering a documentation about using eclipse for build would be nice, I think about making it. 
But this does not matter inside this ticket here.

So, my opinion, we could close this as "resolved", if you like.

> 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: 0001-JAMES-1563-Remove-version-from-maven-site-plugin-as-.patch, 0001-JAMES-1563-solve-javadoc-generation-on-modern-JDK.patch, 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 site.
> 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
(v6.3.4#6332)

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