james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefano Bagnara (JIRA)" <server-...@james.apache.org>
Subject [jira] Commented: (JAMES-840) Alternate approach to local private repo for mvn build
Date Fri, 13 Jun 2008 07:50:45 GMT

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

Stefano Bagnara commented on JAMES-840:
---------------------------------------

David, thanks for the suggestion, very interesting! I'll take a better look at it to understand
pros/cons.

>From a fast overview it seems that you moved all the "local stage repository" use to the
"stage" module so other modules do not need this anymore.
I don't understand why this solution fixes your use and your maven proxy settings: do you
also add profiles to remove the stage module from your build or the simple fact that the "local
stage repository " is now only referred from a single module and there are no more "../" in
every modules fixes it?

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


Mime
View raw message