Thanks Norman,

the question is, which revision does compile? I tried 884854 from 27.11.2009 but the same error occured (the one in the phoenix-deployment tests). Or can I skip the test somehow?

Tim


Norman Maurer schrieb:
Hi Tim,

please use not HEAD atm. I will fix the build asap, unfortunally I'm
ill atm so it will maybe take some time :/

Bye,
Norman


2009/12/16 Tim-Christian Mundt <[email protected]>:
Hello,

I'm new to James and trying to build it (Win XP, JDK 1.6). I'm experiencing
the same problem Gump does as reported every night:

   [javac]
/srv/gump/public/workspace/james-server/management-library/src/main/java/org/apache/james/osgi/OSGISpoolManagementModule.java:48:
package org.ops4j.peaberry.util does not exist
   [javac]
bind(org.ops4j.peaberry.util.TypeLiterals.export(SpoolManagementService.class)).toProvider(
   [javac]                                         ^
   [javac]
/srv/gump/public/workspace/james-server/management-library/src/main/java/org/apache/james/osgi/OSGISpoolManagementModule.java:51:
cannot find symbol
   [javac] symbol  : variable Peaberry
   [javac] location: class org.apache.james.osgi.OSGISpoolManagementModule
   [javac]
Peaberry.service(SpoolManagementMBean.class).export());
   [javac]                             ^
   [javac]
/srv/gump/public/workspace/james-server/management-library/src/main/java/org/apache/james/osgi/OSGISpoolManagementModule.java:50:
package org.ops4j.peaberry.util does not exist
   [javac]
bind(org.ops4j.peaberry.util.TypeLiterals.export(SpoolManagementMBean.class)).toProvider(
   [javac]                                         ^
   [javac] Note: Some input files use unchecked or unsafe operations.
   [javac] Note: Recompile with -Xlint:unchecked for details.
I solved it by manually downloading peaberry and after that also osgi and
adding both to the /james/build-tools/common-build.xml. Is there a reason
this is not included in the build files and the /james/stage directory?

After that ant doesn't complain any more but fails running the
phoenix-deployment tests (MYDIR being the path to james):
compile-unit-tests:
    [echo] Compiling James Unit Test Java sources
   [mkdir] Created dir: MYDIR\james\phoenix-deployment\target\test
   [mkdir] Created dir: MYDIR\james\phoenix-deployment\target\test\classes
   [javac] Compiling 5 source files to
MYDIR\james\phoenix-deployment\target\test\classes
   [javac]
MYDIR\james\phoenix-deployment\src\test\org\apache\james\JamesTest.java:161:
warning: [deprecation] isLocalUser(java.lang.String) in
org.apache.mailet.MailetContext has been deprecated
   [javac]         return
((MailetContext)mailServerImpl).isLocalUser(username);
   [javac]                                               ^
   [javac] 1 warning
    [copy] Copying 17 files to
MYDIR\james\phoenix-deployment\target\test\classes
run-unit-tests:
    [echo] Running James Unit Tests in directory
MYDIR\james\phoenix-deployment
   [mkdir] Created dir: MYDIR\james\phoenix-deployment\target\test\reports
   [junit] Running org.apache.james.AvalonJamesTest
   [junit] Tests run: 5, Failures: 0, Errors: 5, Time elapsed: 0,219 sec

BUILD FAILED
MYDIR\james\build.xml:153: The following error occurred while executing
this line:
MYDIR\james\build.xml:96: The following error occurred while executing
this line:
MYDIR\james\build.xml:84: The following error occurred while executing
this line:
MYDIR\james\build.xml:40: The following error occurred while executing
this line:
MYDIR\james\phoenix-deployment\build.xml:896: Test
org.apache.james.AvalonJamesTest failed
Do I have to change anything locally or just don't use HEAD?

Regards
Tim

---------------------------------------------------------------------
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to