Import the project you want to change in your eclipse workspace.
m2eclipse will update the projects classpath so your changes will be taken into account.
Thx, Eric On 07/25/2012 02:55 PM, Merve Temizer wrote:
I could "mvn packageo" and could run the project but codes are in jars and .class format. What should i do if i want to edit the code (i think apache license allow me). 2012/7/25 Eric Charles <[email protected]>You can run from eclipse launching the main class. The conf files are now shipped in the jars. You can override the default properties by copying the *-template.conf files to *.conf and tuning them to your needs. If you want to build james, You will need to 'mvn package' the app project. Take the target/james*.tar.gz and deploy it somewhere else. Same logic for the conf files. Thx, Eric On 07/25/2012 12:55 PM, Merve Temizer wrote:/james/app/trunk/src/main/**resources contains files like usersrepository-template.conf Should i change it into usersrepository.xml or usersrepository.conf? And should i transport them to another directory for example into /james/app/trunk/src/main/**config ? Also should i hope it to work when i chek out and import http://svn.**apache.org/repos/**asf/james/**server/tags/james-** server-3.0-**<http://apache.org/repos/asf/james/**server/tags/james-server-3.0-**> beta4<http://svn.apache.org/**repos/asf/james/server/tags/** james-server-3.0-beta4<http://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta4>and check out and import https://svn.apache.org/repos/****asf/james/app/trunk/<https://svn.apache.org/repos/**asf/james/app/trunk/> <https://**svn.apache.org/repos/asf/**james/app/trunk/<https://svn.apache.org/repos/asf/james/app/trunk/>into same workspace in Eclipse? Should i do something extra to make them know each other? Thanks in advance. 2012/7/25 Eric Charles <[email protected]> Yep, this is the kind of change that occurred between beta1 and now.We now have a separated app project where you will find the config files. https://svn.apache.org/repos/****asf/james/app/trunk/<https://svn.apache.org/repos/**asf/james/app/trunk/> <https://**svn.apache.org/repos/asf/**james/app/trunk/<https://svn.apache.org/repos/asf/james/app/trunk/>Just continue to ask until your are up-and-running :) Sounds like we also need to update the tutorial documentation... Thx, Eric On 07/25/2012 11:57 AM, Merve Temizer wrote: Sorry for asking too muchbut there is no container-spring\src\main\****config\james directory when i checked out 3.0-beta4 from http://svn.apache.org/repos/******asf/james/server/tags/james-******<http://svn.apache.org/repos/****asf/james/server/tags/james-****> server-3.0-beta4<http://svn.**apache.org/repos/**asf/james/** server/tags/james-**server-3.**0-beta4<http://svn.apache.org/repos/**asf/james/server/tags/james-**server-3.0-beta4><http://svn.**apache.org/**repos/asf/james/**server/tags/** james-server-3.0-*<http://apache.org/repos/asf/james/**server/tags/james-server-3.0-*> *beta4<http://svn.apache.org/**repos/asf/james/server/tags/** james-server-3.0-beta4<http://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta4>. I used container-spring\src\main\****config\james when using beta1 because of tutorial http://james.apache.org/****server/3/dev-build.html<http://james.apache.org/**server/3/dev-build.html> <http:/**/james.apache.org/server/3/**dev-build.html<http://james.apache.org/server/3/dev-build.html>2012/7/25 Eric Charles <[email protected]> beta5 is not yet released (this is why there is no tag for it).the latest release is beta4 http://svn.apache.org/repos/******asf/james/server/tags/james-****<http://svn.apache.org/repos/****asf/james/server/tags/james-**> <http://svn.apache.org/**repos/**asf/james/server/tags/**james-**<http://svn.apache.org/repos/**asf/james/server/tags/james-**>server-3.0-beta4<http://svn.****apache.org/repos/asf/james/**<http://apache.org/repos/asf/james/**> server/tags/james-server-3.0-****beta4<http://svn.apache.org/** repos/asf/james/server/tags/**james-server-3.0-beta4<http://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta4>The current version is beta5-SNAPSHOT (SNAPSHOT means it is not a release). http://svn.apache.org/repos/******asf/james/server/trunk<http://svn.apache.org/repos/****asf/james/server/trunk> <http:**//svn.apache.org/repos/**asf/**james/server/trunk<http://svn.apache.org/repos/**asf/james/server/trunk><http://**svn.apache.org/**repos/asf/**james/server/trunk<http://svn.apache.org/repos/asf/**james/server/trunk> **<http://svn.apache.org/repos/**asf/james/server/trunk<http://svn.apache.org/repos/asf/james/server/trunk>Thx, Eric On 07/24/2012 03:24 PM, Merve Temizer wrote: Where can i find svn url of beta5?There is http://svn.apache.org/repos/******asf/james/server/tags/james-****<http://svn.apache.org/repos/****asf/james/server/tags/james-**> <http://svn.apache.org/**repos/**asf/james/server/tags/**james-**<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-****beta1/<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-beta1/>I tried http://svn.apache.org/repos/******asf/james/server/tags/james-** ** <http://svn.apache.org/repos/****asf/james/server/tags/james-**>< http://svn.apache.org/**repos/**asf/james/server/tags/**james-**<http://svn.apache.org/repos/**asf/james/server/tags/james-**>server-3.0-beta5/<http://svn.****apache.org/repos/asf/james/** server/tags/james-server-3.0-****beta5/<http://svn.apache.org/** repos/asf/james/server/tags/**james-server-3.0-beta5/<http://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta5/><http://svn.**apache.org/****repos/asf/james/**server/tags/****<http://apache.org/**repos/asf/james/**server/tags/**>james-server-3.0-*<http://**apache.org/repos/asf/james/**** server/tags/james-server-3.0-*<http://apache.org/repos/asf/james/**server/tags/james-server-3.0-*> **> *beta1/<http://svn.apache.org/****repos/asf/james/server/tags/****<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-beta1/<http://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta1/>does not exist. 2012/7/24 Eric Charles <[email protected]> Hi,Not sure on how it was behaving on beta1 (we changed the jar/mailet loading since then). I you only have your mailet as custom code, the simplest is to download a nightly snapshot and use it. https://repository.apache.org/********content/repositories/**<https://repository.apache.org/******content/repositories/**> <**https://repository.apache.org/******content/repositories/**<https://repository.apache.org/****content/repositories/**><ht**tps://repository.apache.**org/****content/repositories/****<http://repository.apache.org/****content/repositories/**> <https://repository.apache.**org/**content/repositories/**<https://repository.apache.org/**content/repositories/**>snapshots/org/apache/james/********apache-james/3.0-beta5-********SNAPSHOT/< https://repository.**apache.****org/content/**repositories/** snapshots/org/**<http://**apache.org/content/**** repositories/snapshots/org/**<http://apache.org/content/**repositories/snapshots/org/**>apache/james/apache-james/3.0-******beta5-SNAPSHOT/<https://** repository.apache.org/content/****repositories/snapshots/org/****<http://repository.apache.org/content/**repositories/snapshots/org/**> apache/james/apache-james/3.0-****beta5-SNAPSHOT/<https://** repository.apache.org/content/**repositories/snapshots/org/** apache/james/apache-james/3.0-**beta5-SNAPSHOT/<https://repository.apache.org/content/repositories/snapshots/org/apache/james/apache-james/3.0-beta5-SNAPSHOT/>If you have custom code (james internals), you'd better synchronize, but except some pain (huge code, project, configuration... changes). Thx, Eric On 07/24/2012 02:34 PM, Merve Temizer wrote: i have 3 beta 1. Should i checkout entire project and again import it?I have a lot of configurations in it, can i "synchronize with repository" and get updates? Can it be enough? Thanks in advance for fast responses. 2012/7/24 Eric Charles <[email protected]> Hi, We had a bug on jar loading and on documentation.You don't have to specify mailetpackage and you have to use the full class name. The jar in conf/lib will only work with latest snapshots. Thx, Eric On 07/24/2012 12:47 PM, Merve Temizer wrote: Lines from my mailetcontainer.xml<mailetcontainer enableJmx="true"> <mailetpackages> <mailetpackage>kobu.omikuji.****** ****Omikuji</mailetpackage> <mailetpackage>org.apache.**********james.transport.mailets</*** ***** mailetpackage> <mailetpackage>org.apache.****** ****james.transport.mailets.* *smime< ****** /mailetpackage> </mailetpackages> .... <processor state="transport" enableJmx="true"> ... <mailet match="RecipientIs=omikuji@***** *****localhost" class="kobu.omikuji.Omikuji" > <jinja>omikuji@localhost</**********jinja> </mailet> ... </processor> ... </mailetcontainer> i added Omukuji.class into a jar and import it into james/conf/lib i tried many other configuration like <mailetpackage>kobu.omikuji</**********mailetpackage> <mailet match="RecipientIs=omikuji@**********localhost" class="Omikuji" > than it says "i could not found org.apache.james.transport.** mailets.Omukuji" thanks for any suggestion -- eric | http://about.echarles.net | @echarles------------------------------**********----------------------** --** --**--** --**--------- To unsubscribe, e-mail: server-dev-unsubscribe@james.********** apache.org< server-dev-**unsubscribe@****jam**es.apache.org<http://** james.apache.org <http://james.apache.org>> <unsubscribe@**james.apache.**org <http://james.apache.org> < [email protected]>**> <server-dev-**unsubscribe@**ja**mes.apache.org<http://james.apache.org> <unsubscribe@**james.apache.org <[email protected]>> <server-dev-**unsubscribe@**james.apache.org<[email protected]> <server-dev-**[email protected]<[email protected]>For additional commands, e-mail: [email protected].***** ** ***org<server-dev-help@james.******apache**.org <http://apache.org> < [email protected].******org <[email protected].*** *org <[email protected].**org<[email protected]>--eric | http://about.echarles.net | @echarles ------------------------------********------------------------** --**--** --**--------- To unsubscribe, e-mail: server-dev-unsubscribe@james.******** apache.org< server-dev-**unsubscribe@**jam**es.apache.org<http://james.apache.org> <unsubscribe@**james.apache.org <[email protected]>> <server-dev-**unsubscribe@**james.apache.org<[email protected]> <server-dev-**[email protected]<[email protected]>For additional commands, e-mail: [email protected].*** *****org< server-dev-help@james.****apache**.org <http://apache.org> < [email protected].****org <[email protected].* *org <[email protected]>>--eric | http://about.echarles.net | @echarles ------------------------------******--------------------------**--** --**--------- To unsubscribe, e-mail: server-dev-unsubscribe@james.******apache.org< server-dev-**unsubscribe@**james.apache.org<[email protected]> <server-dev-**[email protected]<[email protected]>For additional commands, e-mail: [email protected].******org< server-dev-help@james.**apache**.org <http://apache.org> < [email protected].**org <[email protected]>-- eric | http://about.echarles.net | @echarles ------------------------------****----------------------------** --**--------- To unsubscribe, e-mail: server-dev-unsubscribe@james.****apache.org< server-dev-**[email protected]<[email protected]>For additional commands, e-mail: [email protected].****org< server-dev-help@james.**apache.org <[email protected]>>-- eric | http://about.echarles.net | @echarles ------------------------------**------------------------------**--------- To unsubscribe, e-mail: server-dev-unsubscribe@james.**apache.org<[email protected]> For additional commands, e-mail: [email protected].**org<[email protected]>
-- eric | http://about.echarles.net | @echarles --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
