james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Jencks (JIRA)" <server-...@james.apache.org>
Subject [jira] Updated: (JAMES-840) Alternate approach to local private repo for mvn build
Date Sun, 15 Jun 2008 17:49:45 GMT

     [ https://issues.apache.org/jira/browse/JAMES-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

David Jencks updated JAMES-840:

    Attachment: JAMES-840-2.patch

There are really two ideas behind this issue:

1. Move _all_ the jars needed for the build into a single stage directory/repo
2. Use a single maven project to get all these jars into the local maven repo rather than
using a special repo configuration for the entire build.

2.1. separate the jars in stage into several categories:
- available from maven central repo with appropriate signatures 
- not available from maven central or maven central does not have appropriate signatures.

I've found it extremely confusing that the jars required for building and running this project
are spread over so many locations:


The last two locations appear to have many of the same files in them.

The updated patch includes configuration for some files needed to run JAMES in geronimo from

Whether or not the idea (2) for alternate use of a private maven repo is adopted, getting
all the jars in one place without duplicates (1) would really improve the comprehensibility
of even the ant build.

> 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-2.patch, 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org

View raw message