james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernd Waibel <BWai...@intarsys.de>
Subject [PTACH] AW: [jira] [Commented] (JAMES-1563) Switch to Maven3 [unsigned]
Date Fri, 31 Oct 2014 09:40:26 GMT
Hello committers,

patch has been provided. Could someone consider this and apply the patch?
Thanks.

Bernd

-----Urspr√ľngliche Nachricht-----
Von: Bernd Waibel (JIRA) [mailto:server-dev@james.apache.org] 
Gesendet: Freitag, 31. Oktober 2014 10:35
An: server-dev@james.apache.org
Betreff: [jira] [Commented] (JAMES-1563) Switch to Maven3


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

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

Patch provided.
When patching, consider first zu patch JAMES-1560 and JAMES-1559. Also JAMES-1562 for war
deployment.
They solve other maven problems, but these are independent of Maven3.

> 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
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

Mime
View raw message