On Tue, Apr 5, 2011 at 8:10 AM, Ioan Eugen Stan <stan.ieu...@gmail.com> wrote:
>>> welcome :) You need to install maven3 to build james. Just download the
>>> tar.gz, unpack it and use it. You can find it here:
>>> http://maven.apache.org/
>
> it built fain. I was a little mislead about the info on
> http://james.apache.org/mailbox/source-code.html
> It does not specify the switch to maven 3 or the fact that you do not
> need to replace mailbox with imap when getting the sources.

submit a patch ;-)

(at Apache, karma is earned by contribution)

edit the source [1]
rebuild locally ('mvn site')
check the results by browsing mailbox/target/site/source-code.html
sign up to JIRA [2]
create an issue
attach a diff

We can then apply the diff and commit the change, crediting the
contributor (you) and noting the JIRA in the commit message. This
process establishes a chain of provenance for the source.

[1] 
http://svn.apache.org/repos/asf/james/mailbox/trunk/src/site/xdoc/source-code.xml
[2] https://issues.apache.org/jira/

>> (Gentoo is also still on Maven 2, so I've installed Maven 3 into
>> /usr/local/ and use a script to switch my environment when building
>> James)
>
> I wonder why isn't there maven 3 in Debian or other big distros.

AIUI Java is problematic for many distros. Java applications typically
compose a large number of finely grained components. Maven (and other
applications like Eclipse) use provisioning and repository standards
independent of the library systems employed by distribution packagers.
>From an upstream perspective, it would be preferable for downstream
distributions to accept that byte code languages need different
packaging rules...

Robert

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

Reply via email to