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,
Eric
On 10/01/12 19:40, Jochen Gazda wrote:
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
http://maven.apache.org/xsd/settings-1.0.0.xsd";>
<localRepository>${user.home}/.m2/repository-james</localRepository>
</settings>
Is there something weird in it?
Performing mvn package does not touch the local repository, right?
Maybe that is why I get the errors. I probably must run "mvn install"
instead.
Thanks
Gazda
On Tue, Jan 10, 2012 at 7:21 PM, Eric Charles<[email protected]> 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 something weird in your maven settings.xml?
Thx,
Eric
On 10/01/12 11:04, Jochen Gazda wrote:
On Tue, Jan 10, 2012 at 10:20 AM, Ioan Eugen Stan<[email protected]>
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 compilation error in james-server-protocols-library
saying that org.apache.james.protocols.api.logger.Logger could not be
resolved. From maven's output it seemed that
protocols.version=1.6-beta3 was used instead of 1.6.0-RC2-SNAPSHOT. I
could not find any occurence of 1.6-beta3 in my workspace. I have
concluded that maven's local repository ~/.m2/repository must somehow
cause the inclusion of improper protocols.version. I have created a
dedicated settings-james.xml for james builds with a new empty local
repository:
<?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
http://maven.apache.org/xsd/settings-1.0.0.xsd";>
<localRepository>${user.home}/.m2/repository-james</localRepository>
</settings>
After having done that there came another james error:
[ERROR] The project org.apache.james:apache-james:3.0-beta4-SNAPSHOT
(/home/gazda/james/current/app/pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not find artifact
org.apache.james:james-server:pom:3.0-beta4-SNAPSHOT and
'parent.relativePath' points at no local POM @ line 26, column 13
I have changed the parent relativePath from empty to ../server/pom.xml
and voila... The build fails on postage. As I do not need postage I
have simply commented it out in current.pom.xml. After that the build
succeeds.
The question is: what kind of care does /current/app/pom.xml need?
(a) I should set the parent.relativePath somewhere in my environment or
(b) parent.relativePath should be fixed in /current/app/pom.xml
Thanks
Gazda
From what I know the code in trunk is going through some refactoring
right
now so it may not be buildable. I suggest you take a tag release instead
of
trunk.
Someone correct me if I'm wrong.
Thank for your prompt reply, Ioan.
Could please somebody utter a forecast when will the trunk be worth
building again?
Best,
Gazda
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
eric | http://about.echarles.net | @echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
eric | http://about.echarles.net | @echarles
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
