Hi all,
In short for james 3:
- First, it will be more easy to define your own project that contains
your mailet. You can copy the src/server/mailets pom.xml to your
src/server/mymailet directory
- If you use eclipse, you will be happy to use the m2eclipse plugin
that will take care of dependency resolution. You can add your mymailet
project as dependency of the spring-deployment project and run the Main
(with conf/ directory at right place and spring-beans.xml/log4j.xml in
your classpath) from eclipise. You will have debugging,... and all IDE
goodness.
- If you want to remain with command line, you can build the
mymailet.jar (mvn package) and copy it in a deployed james 3 in conf/lib
(extra jar come there).
I have planned to write some doc for james 3 website the coming days.
I will start with a kind-of "How to develop on James" and yes,
developing for james is really *super* fast if you've got a few tips.
In the meantime, you can try to create a new maven project for your
mailet and we will happily help you find your way while the doc is not
there.
Tks,
Eric
On 16/09/2010 11:00, Nitin Gupta wrote:
Yes, I was talking about James 2. However, IMO the approach to write&
deploy custom mailets should not have differed a lot between the two
versions. Developers of version 3 should shed more light into this.
rgds
-----Original Message-----
From: Max Levinson [mailto:[email protected]]
Sent: Thursday, September 16, 2010 1:42 AM
To: James Users List
Subject: Re: Small question about mailets development
Hi Nitin,
Thanks for a quick answer, I was talking about James version 3 from trunk,
I believe you refer to James 2.
There is just no /apps directory in James 3 from trunk.
2010/9/16 Nitin Gupta<[email protected]>
I do not need your requirement to write a custom mailet in mail james
project. What you can also do is write your custom mailet using the base
mailet api& deploy the compiled jar other dependencies in the following
directory:
<james-home>/apps/james/SAR-INF/lib directory. (you will need to create a
lib directory)
With this approach you will just be required to build your mailets jar&
not
the whole James project. I hope this helps.
Rgds
nitin
-----Original Message-----
From: Max Levinson [mailto:[email protected]]
Sent: Thursday, September 16, 2010 1:23 AM
To: James Users List
Subject: Small question about mailets development
Hi list,
I have a really small question about mailet development.
When I am adding a new mailet to james into
/mailets/src/main/java/org/apache/james/transport/malets
Should I everytime rebuild the whole james project like mvn -U clean
package
-Dmaven.test.skip.exec=true
Because this is what I do every time and it makes a process of development
and debugging quite slow.
Sorry for this silly question I am quite new to this :)
---------------------------------------------------------------------
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]
