[
https://issues.apache.org/jira/browse/JAMES-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604772#action_12604772
]
David Jencks commented on JAMES-840:
------------------------------------
Bernd.... I am well aware that many james committers dislike maven almost as
much as I dislike ant, but the maven build does work. I am suggesting
something that I think is a slight simplification of it.
Stefano... I apologize for confusing the issue. After some struggles I thought
that my proxy/mirror settings were causing problems so I turned them off, but
by that time I had most of this suggestion implemented. I think but haven't
checked that the build would work fine as is if I started with my proxy/mirror
settings turned off.
I guess there are 3 parts here:
1. merging the spring-deployment stage repo into the main stage repo. I would
think you would want to do this anyway so all the dependencies are in one place.
2. turning the stage dir into a maven project whose only function is to install
the dependencies in the stage repo into the local maven repo. I think this
makes the build clearer. Another effect is that you only have to turn off your
proxy/mirror settings while building the stage module, the rest of the build
works with them on.
3. possibly separating the "available from maven central repo" dependencies
into a separate profile in the stage pom. I think this would help in tracking
which dependencies are easiliy available and which you have built yourself or
dug out of some undocumented location.
This is not a giant improvement in any sense, but to me it seems slightly
clearer what is going on with the repos and it might be slightly more
maintainable. I certainly won't mind if you keep the build the way it is now,
although I do think adding the 2 dependencies to the root dependency management
section would be a good idea. (there might be more that I didn't see).
> Alternate approach to local private repo for mvn build
> ------------------------------------------------------
>
> Key: JAMES-840
> URL: https://issues.apache.org/jira/browse/JAMES-840
> Project: James
> Issue Type: Bug
> Components: Build System
> Affects Versions: Trunk
> Reporter: David Jencks
> Attachments: JAMES-840.patch
>
>
> The mvn build did not work for me, perhaps because of some maven proxy
> settings. However I think the current use of local repositories is weird and
> suggest an alternate approach, see attachment.
> Basically the idea is to turn stage into a project that installs all required
> jars from the stage private local repo to the local maven repo.
> I would suggest having two sets of dependencies: in the regular dependencies
> include only those jars that are not available elsewhere, and in a profile
> include also those jars that are available from maven central. This will
> clarify which jars you are using from non-publically-available sources or
> builds.
> In addition, the spring integration has a separate stage. I would recommend
> moving the contents to the main stage repo with (I think)
> svn mv spring-deployment/stage/ stage
> I don't know if this would break the ant build.
> At this point the root pom is missing the javax.jcr:jcr:1.0:jar and
> avalon-phoenix:avalon-phoenix-client:4.2-SNAPSHOT:jar dependencies in the
> dependency management section
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
