Thank you, Rene. Is that a hard requirement? If so, then I will have to wait until we update to Java 11 (which is not scheduled at this time), so I’ll likely have to abandon for now.
Shouldn’t it be possible to compile in Java 8, though? This page states that JRE8 is the requirement: —> https://james.apache.org/server/quick-start.html Cheers, =David On Apr 27, 2020 13:44 +0900, Rene Cordier <rcord...@apache.org>, wrote: > Hi David, > > I think you are trying to compile the latest code from master branch > right? A move has been made lately towards java 11 on it if I'm correct. > Try to compile and run with Java11 instead? > > Regards, > Rene. > > On 27/04/2020 06:06, David Leangen (Apache) wrote: > > Hi! > > > > This is the first error: > > > > [INFO] Apache James :: Server :: Common Utilities ......... FAILURE [ > > 0.659 s] > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile > > (default-compile) on project james-server-util: Fatal error compiling: > > invalid flag: --release -> [Help 1] > > > > Googling tells me to comment out the “release” flag in > > maven-compiler-plugin, so I try that (though I don’t understand why) and > > get a different error: > > > > [INFO] Apache James :: Server :: Common Utilities ......... FAILURE [ > > 0.551 s] > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile > > (default-compile) on project james-server-util: Fatal error compiling: > > invalid target release: 11 -> [Help 1] > > > > Yeah, that makes sense. I am still on Java 8. So I modify the target.jdk > > version to 8 and make a bit of progress: > > > > [INFO] Apache James :: Core Domain Objects ................ FAILURE [ > > 0.597 s] > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile > > (default-compile) on project james-core: Compilation failure: Compilation > > failure: > > [ERROR] > > /Users/dleangen/libs/james-project/core/src/main/java/org/apache/james/core/builder/MimeMessageBuilder.java:[400,46] > > no suitable method found for toArray(InternetAd[...]::new) > > > > Hmmmm. This is in the code. I just want to compile, not debug at this > > point. This makes me think that the project is currently being neglected. > > :-( > > > > Ok, let me try to omit the core project (though that does not sound like a > > promising approach). > > > > [INFO] Apache James Cassandra backend ..................... FAILURE [ > > 18.471 s] > > > > [ERROR] Failed to execute goal on project apache-james-backends-cassandra: > > Could not resolve dependencies for project > > org.apache.james:apache-james-backends-cassandra:jar:3.6.0-SNAPSHOT: Could > > not find artifact org.apache.james:james-core:jar:3.6.0-SNAPSHOT in > > apache.snapshots (https://repository.apache.org/snapshots) -> [Help 1] > > > > Yeah, like I expected. > > > > Ok, so try mvn eclipse:eclipse without building the project, then? I only > > get this far: > > > > [INFO] Apache James :: Test helpers for Mailet ............ FAILURE [ > > 1.859 s] > > > > [ERROR] Failed to execute goal > > org.apache.maven.plugins:maven-remote-resources-plugin:1.6.0:process > > (process-resource-bundles) on project apache-mailet-test: Execution > > process-resource-bundles of goal > > org.apache.maven.plugins:maven-remote-resources-plugin:1.6.0:process > > failed: Failed to resolve dependencies for one or more projects in the > > reactor. Reason: Missing: > > [ERROR] 1) org.apache.james:james-core:jar:3.6.0-SNAPSHOT > > [ERROR] 2) org.apache.james:apache-james-mailbox-api:jar:3.6.0-SNAPSHOT > > > > Perhaps only a simple fix is required to get everything compiling, but > > since I have never yet looked at any of the code base, I don’t know. I > > can’t even set it up in my Eclipse yet because I cannot run mvn > > eclipse:eclipse until I can get the projects to compile. > > > > I’m sure someone with enough motivation could figure out a way around these > > issues, but I thought that the golden rule was that the project should > > compile out of the box. That’s why I asked my original question. > > > > Cheers, > > =David > > > > On Apr 27, 2020 02:39 +0900, Jerry Malcolm <techst...@malcolms.com>, wrote: > > > Sadly I realized a while back that it does not build out of the box. > > > Through much trial and error, I finally got the build to complete. > > > However, even with that, for some reason I still get several errors. > > > Apparently they aren't fatal errors. I have learned that if there is > > > really something wrong, the build won't complete. However, if the maven > > > build gets to the end, even if there were errors reported, the build > > > works. I would really like to understand this better. If the 'errors' > > > I get aren't really critical, seems they should be warnings. I build > > > and use James. But it doesn't give me a whole load of confidence that > > > there were errors in the build, even though the build doesn't abort on > > > them. > > > > > > What kind of errors are you getting? Does the build stop on those errors? > > > > > > Jerry > > > > > > On 4/26/2020 5:58 AM, David Leangen wrote: > > > > Hi! > > > > > > > > I am trying to build JAMES from HEAD using mvn install. It is my > > > > expectation (from working with other projects) that I should just be > > > > able to build “out of the box”. > > > > > > > > My first question: is my expectation correct? Am I supposed to be able > > > > to build JAMES without any compilation errors? > > > > > > > > > > > > If so, is anybody willing to help me understand the problems so I can > > > > make PRs to fix the build issues? > > > > > > > > If not: what is the expected path to be able to use the source code. It > > > > is not clear to me from the documentation (which only seems to discuss > > > > building the websites). > > > > > > > > > > > > Thanks! > > > > =David > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > > > > For additional commands, e-mail: server-user-h...@james.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > > > For additional commands, e-mail: server-user-h...@james.apache.org > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org >
