Gentlemen,
I still have problems to understand what is normal and what is not
normal with maven and James.
(1) From what goes on on this mailing list I have understood that
James Components live their lives quite independently from each other.
So, it is normal that in some development phases
2012/2/21 Jochen Gazda gazdahims...@gmail.com:
(1) []
But as for parent references I am asking myself what can be the reason
for distinct versions in the parent's project.version and its child's
project.parent.version? Here is an example from the current trunk:
apache-jsieve has version
Hi,
james-project:1.9-SNAPSHOT should be 1.8.1 or 1.8.2-SNAPSHOT
(1.9-SNAPSHOT are rest that need cleanup).
All James projects have their own lifecycle, but also communicate with
each other. For example, bidirectional dependencies, strategy for
assemble maven module... are something we talk
Thank your replies, Stefano and Eric.
See inline.
Best,
gazda
On Tue, Feb 21, 2012 at 3:31 PM, Stefano Bagnara apa...@bago.org wrote:
2012/2/21 Jochen Gazda gazdahims...@gmail.com:
(1) []
But as for parent references I am asking myself what can be the reason
for distinct versions in
2012/2/21 Jochen Gazda gazdahims...@gmail.com:
Why should we always try to build with the latest available released
parent? And who is we here? Did you mean (a) we = developers
building James to test our own changes or is it (b) we = developers
building a release for the public?
At the moment
Thanks for the tips, Eric and Ioan. Maven seems to work as expected now.
Gazda
On Thu, Jan 12, 2012 at 8:13 AM, Ioan Eugen Stan stan.ieu...@gmail.com wrote:
Pe 11.01.2012 21:40, Eric Charles a scris:
Hi Jochen,
Your settings.xml seems ok.
'mvn package' (or even compile) from a toplevel
Pe 11.01.2012 21:40, Eric Charles a scris:
Hi Jochen,
Your settings.xml seems ok.
'mvn package' (or even compile) from a toplevel should take the
snapshots from your sources even if not installed.
I usually invoke 'mvn clean install' in case of weird behaviour.
Can you now compile?
Thx,
Gentlemen,
I am quite new to maven, so maybe I am missing something obvious.
Issuing
cd james/current
svn update
mvn package -DskipTests -e
has brought a compilation error in james-server-protocols-library
saying that org.apache.james.protocols.api.logger.Logger could not be
resolved. From
Pe 10.01.2012 11:14, Jochen Gazda a scris:
Gentlemen,
I am quite new to maven, so maybe I am missing something obvious.
Issuing
cd james/current
svn update
mvn package -DskipTests -e
has brought a compilation error in james-server-protocols-library
saying that
On Tue, Jan 10, 2012 at 10:20 AM, Ioan Eugen Stan stan.ieu...@gmail.com wrote:
Pe 10.01.2012 11:14, Jochen Gazda a scris:
Gentlemen,
I am quite new to maven, so maybe I am missing something obvious.
Issuing
cd james/current
svn update
mvn package -DskipTests -e
has brought a
Hi there,
Trunk is buildable (at least here and on hudson
https://builds.apache.org/job/james-server-trunk/2530/).
Try to force a clean via 'mvn clean install' if it really does not work
Maybe there is something weird in your maven settings.xml?
Thx,
Eric
On 10/01/12 11:04, Jochen Gazda
Eric,
this is my ~/.m2/settings-james.xml which I always specify as mvn
command option:
?xml version=1.0 encoding=UTF-8?
settings xmlns=http://maven.apache.org/SETTINGS/1.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/SETTINGS/1.0.0
(but yes, postage fails, you have to comment it)
On 10/01/12 19:21, Eric Charles wrote:
Hi there,
Trunk is buildable (at least here and on hudson
https://builds.apache.org/job/james-server-trunk/2530/).
Try to force a clean via 'mvn clean install' if it really does not work
Maybe there is
13 matches
Mail list logo
