james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Charles (JIRA)" <server-...@james.apache.org>
Subject [jira] [Commented] (JAMES-1612) dev-build documentation is not consistent wrt beta4
Date Fri, 25 Sep 2015 14:13:04 GMT

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

Eric Charles commented on JAMES-1612:
-------------------------------------

Not sure to understand, are you talking about the documentation or the way we structure svn?
Thx, Eric

> dev-build documentation is not consistent wrt beta4
> ---------------------------------------------------
>
>                 Key: JAMES-1612
>                 URL: https://issues.apache.org/jira/browse/JAMES-1612
>             Project: James Server
>          Issue Type: Bug
>          Components: Documentation
>    Affects Versions: Trunk
>            Reporter: Matthieu Baechler
>
> dev-build defines three different things for  JAMES_SRC_HOME :
> 1.  source distribution : it's an almost empty shell that just downloads everything from
maven central
> 2.  http://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta4/ checks
out the server sources
> 3. http://svn.apache.org/repos/asf/james/current checks out every james modules
> I suggest to change this to http://svn.apache.org/repos/asf/james/current content for
the 3 ways and to tag http://svn.apache.org/repos/asf/james/current on releases.



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