[
https://issues.apache.org/jira/browse/JAMES-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara reassigned JAMES-840:
-------------------------------------
Assignee: Stefano Bagnara
> 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
> Assignee: Stefano Bagnara
> 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]
