Eric/list - I forged ahead and decided to simply ignore all the
exceptions I saw when doing the maven build. I now have James3.0-beta1
up and running under Eclipse! (I tried to get beta3 up an running also,
but the instructions do not correlate with the file organization so I
gave up on it and went back to beta1)
Some comments for the wiki page, that I think might help those of us,
like me, who are not familiar with all the latest wiz-bang features of
Eclipse...
1. In the section from the
http://james.apache.org/server/3/dev-build.html document, on
Select Projects to Import
the example shows that a checkbox for "Add project(s) to working set"
has been checked. You might say more about what this means, does and
where to learn more. I looked around and couldn't figure out what it
does exactly, and ended up just guessing on what to do to set up a
working set, whatever that is....
2. Right below this there is the following instruction -
"You can also import other projects from imap, mailbox and protocols to
have a more complete view on the used sources code."
I am confused, and am sure others might also be.. did we not get all the
source code for the James server? If not, then providing instructions,
and/or links to places that describe how to import and connect these
projects would be useful.. (I know, probably something Eclipse users
fundamentally know, but I am use to monolithic projects and don't yet
grok how complex project environments play in Eclipse, so a link to a
tutorial would be helpful)
3. Next, there is an instruction in the section -
Enable Workspace Resolution
that says - "Check that 'Workspace resolution' is enable in m2eclipse
plugin." Uh how does one do that? I hunted around and found something
"close"??? by right clicking on each project Maven built, then selecting
the Maven item in the popup menu, there is a sub option to "Disable
Workspace Resolution" which I am guessing can be done on a per project
basis... So I am guessing that Workspace resolution was enabled by
default, but I dunno how to check it to be certain. Again Google
searches did not help me reach an understanding either...
4. In the section -
Prepare projects
I have a couple questions. I presume that if I run Eclipse/James as
root, I won't have to remap ports to values higher than 1024?
I did not grok the instruction - "For ease, you can also create 2 new
eclipse projects to edit the files and visualize the created
mails/store/...: james-server-container-spring-conf and
james-server-container-spring-var." I think this needs some
clarification and have no idea what to do...
That's it! Following these instructions is doable, IF you are prepared
to do a lot of experimenting/backtracking in order to grasp what one is
being asked to do. I wouldn't mind helping out with the documentation,
but it appears that getting James to run under Eclipse is a moving
target, and I suspect Beta3 and whatever upcoming releases there are,
will require a very different approach...
Also, my earlier question about all the exceptions I saw during the
Maven build (from a shell) remain a concern. (see previous email)
I am sure I will be back with more questions as I start to explore James
with Eclipse... Thanks Eric for getting me this far...
Marc..
On 10/28/2011 11:12 AM, Marc Chamberlin wrote:
Hi Eric - Thank you for replying! Yes, I saw the link at the top of
the wiki page that you are referring to and I was attempting to grok
both pages in order to do the build. ;-) While there is conflicting
information, I think I understand the gist of it, am and indeed
following those instructions as well...
To be sure we are on the same page, I exported the maven opts via my
.bashrc startup script, as can be seen and am using the following
command to invoke the maven build -
marc@bigbang:~/eclipse/james-workspace/james-server-3.0-beta1> echo
$MAVEN_OPTS
-Xmx1024m -XX:MaxPermSize=128m
marc@bigbang:~/eclipse/james-workspace/james-server-3.0-beta1> mvn
--log-file james.log clean package
and I capture all the output to the james.log file, so if you like I
can send that to you....
I have now attempted to build both the beta1 and beta3 versions of
James by checking them out from the following URLs -
http://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta1
http://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta3
Both builds report Success in the end, but there were quite a number
of exceptions thrown during the builds. (which I as a programmer
myself normally consider as serious problems needing to be fixed, but
I know other programmers have differing opinions on the usage of
exceptions and simply ignore them...) So I am not sure what to think
about whether the build is truly successful or not... Will await your
advise...
Question - Do I need to run the build as root? Sometimes, I know there
can be permissions issues, especially for such things as using low
numbered ports, and I dunno what these tests are doing under the
covers... (I have tried building as root, seemed not to make a
difference...)
Marc...
On 10/27/2011 11:50 PM, Eric Charles wrote:
Hi Marc,
Did you see on top of the wiki page:
To build James V3 in eclipse, read
http://james.apache.org/server/3/dev-build.html
The instructions on the web site are valid for beta1 tag.
For trunk we have now a new 'app' application, and the config files,
the main class... have moved.
Maybe start with beta1 src code to get used to james within eclipse,
we will update the documentation later on to align to trunk.
Thx,
Eric
On 28/10/11 06:59, Marc Chamberlin wrote:
Hello -
I am attempting to follow the instructions given on the James wiki at
http://wiki.apache.org/james/EclipseNotes and am having troubles
getting
it set up and running in Eclipse. I have no troubles getting the SVN
repository set up in Eclipse, and checking out the project as per
instructions. But when I try to verify the checkout things go wrong...
The instructions on the web page say this is an Ant project, but it is
actually a Maven project which I determined by reading the Build.txt
notes. (Suggest updating the wiki?) So I follow the instructions for
building James using Maven and I am getting a number of
exceptions/stack
walkbacks and in the end it reports that it failed to complete the
build... I have captured the output from the Maven build to a log file,
but don't think it would be polite to include it all in this posting...
So if some kind guru can help, and analyze the log file for me, I sure
would appreciate it! Let me know how to send the log file to you....
Marc..
P.S. The version of Maven that I am using reports -
~/eclipse/james-workspace/James> mvn -V
Apache Maven 3.0.3 (r1075438; 2011-02-28 09:31:09-0800)
Maven home: /usr/local/apache-maven/apache-maven-3.0.3
Java version: 1.6.0_26, vendor: Sun Microsystems Inc.
Java home: /usr/lib/jvm/java-1.6.0-sun-1.6.0/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "2.6.37.6-0.7-desktop", arch: "i386",
family:
"unix"
The repository URL I am getting James from is -
http://svn.apache.org/repos/asf/james
and I am doing a checkout on server/trunk
---------------------------------------------------------------------
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]
