Re: [VOTE] Release Apache James Server 2.3.2.1
[X] +1 Please release Am 29.08.2015 um 09:38 schrieb Eric Charles: Hi there, We have a security fix implemented in JAMES-1602 thanks to Steve Brewin. I have uploaded a signed version of the artifacts on http://people.apache.org/~eric/james-2.3.2.1/ Please review and cast your VOTE: [ ] +1 Please release [ ] +0 No time to review [ ] -1 Something is wrong Thx, Eric - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Mailbox 0.5
[X] +1 Please release Regards Felix On 03/05/2013 03:58 PM, Ioan Eugen Stan wrote: Hello, Time for a new release again. Please cast your VOTE for Apache James Mailbox 0.5 release: [ ] +1 Please release [ ] +0 No time to review [ ] -1 Something is wrong SVN tag: http://svn.apache.org/repos/asf/james/mailbox/tags/apache-james-mailbox-0.5/ Source archive: https://repository.apache.org/content/repositories/orgapachejames-331/org/apache/james/apache-james-mailbox/0.5/apache-james-mailbox-0.5-source-release.zip Staging repository with artifacts to be released: https://repository.apache.org/content/repositories/orgapachejames-331/ Before voting please take a moment to review the requirements: http://www.apache.org/dev/release.html#approving-a-release This release is minor release. Changes include: * all artifacts are OSGi bundles * each module has it's own spring context - still in works OSGi Spring DM contexts * fixes, improvements and code cleaning * dependency updates Cheers, - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Project 1.8.2
[X] +1 Please release Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache Mailet 2.5.0 and company
[X] +1 Please release Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] apache james mailet - code improvements - lazy consensus
+1 Thanks Felix On 12/02/2012 10:33 PM, Ioan Eugen Stan wrote: Hello James Devs, Please vote on the following issues. This is a lazy consensus vote starting now, ending in 72h. I propose the following new changes to James mailets: New project names: Apache James :: Mailets Parent SUCCESS [3.814s] Apache James :: Mailet API SUCCESS [0.200s] Apache James :: Basic Mailet Toolkit .. SUCCESS [0.184s] Apache James :: Mailetdocs Maven Plugin ... SUCCESS [2.274s] Apache James :: Crypto Mailets SUCCESS [0.168s] Apache James :: Standard Mailets .. SUCCESS [0.307s] Apache James :: AI Mailets SUCCESS [0.017s] Apache James :: Classic AI Mailets SUCCESS [0.189s] Apache James :: Mailets Aggregator SUCCESS [0.019s] New artifactId's and versions: ** all have groupId org.apache.james apache-james-ai-project-0.1-SNAPSHOT - apache-mailets-ai-0.0.1-SNAPSHOT apache-james-ai-classic-0.1-SNAPSHOT - apache-mailets-ai-classic-0.0.1-SNAPSHOT mailet-project-1-SNAPSHOT - apache-mailets-0.0.1-SNAPSHOT (this is parent -- will contain all mailet specific project info and depend on james-project-1.8.1 - all other mailets will depend on apache-mailets) apache-mailet-2.5-SNAPSHOT - apache-mailets-api-2.5.0-SNAPSHOT apache-mailet-base-1.2-SNAPSHOT - apache-mailets-base-1.2.0-SNAPHSOT apache-crypto-mailets-1.1-SNAPSHOT - apache-mailets-crypto-1.1.0-SNAPSHOT maven-mailetdocs-lugin-0.2-SNAPSHOT - changed version to 0.0.2-SNAPSHOT mailet-project-1.0-SNAPSHOT - apache-mailets-aggregator-0.01-SNAPSHOT All chages are available as a github commit [1]. Further proposed changes TBD - will go on JIRA: * change directory names to mailets-current-name (not strong opinion) * clean-up 1: agggregate all project info, dependencies and other stuff to parent apache-mailets and remove duplication -- A MUST DO * move site related content under site -- A MUST DO IMHO * aggregate JIRA tracking under the same project - going through the project I noticed each mailet has it's own JIRA project, mailinglist, etc. I think it's a lot of overhead and not worth it. The community is not that big. I also think less is more. -- also a MUST DO IMHO * move code to java 1.6 (which will be end-of-life in spring 2013) - like all other James code * make a release and publish site [+1] Yes, I agree [0] No time to review, [-1] No I don't agree - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Hupa 0.0.3
[X] +1 Please release Thanks Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Hupa 0.2
[X] +1 Please release Go for the first release. Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James App 3.0-beta4 (3rd try)
[X] +1 Please release Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Question on Apache James App 3.0-beta4
Hi all I start a separate thread to not pollute the voting thread with other stuff. I just built the the app from the svn tag (works fine) and unzipped it. Because I want to run it as common user I need to change the ports. To do so I copy the imapserver-template.conf to imapserver.conf and put a port higher than 1024. The same I do with pop3server and smtpserver. Everything starts up fine as long as I disable the pop3server and the smptserver. Enabling the smptserver I get Exception 1), enabling pop3server I get Exception 2). Should template be exactly for this? Copy the template, adapt to you needs, keep all other entires in the template unchanged (these should be the default ones) and the application works? Regards Felix 1) jvm 1| WrapperSimpleApp: Encountered an error running main: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'smtpserver': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain jvm 1| org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'smtpserver': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain 2) jvm 1| WrapperSimpleApp: Encountered an error running main: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'pop3server': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain jvm 1| org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'pop3server': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Question on Apache James App 3.0-beta4
Hi all I start a separate thread to not pollute the voting thread with other stuff. I just built the the app from the svn tag (works fine) and unzipped it. Because I want to run it as common user I need to change the ports. To do so I copy the imapserver-template.conf to imapserver.conf and put a port higher than 1024. The same I do with pop3server and smtpserver. Everything starts up fine as long as I disable the pop3server and the smptserver. Enabling the smptserver I get Exception 1), enabling pop3server I get Exception 2). Should template be exactly for this? Copy the template, adapt to you needs, keep all other entires in the template unchanged (these should be the default ones) and the application works? Regards Felix 1) jvm 1| WrapperSimpleApp: Encountered an error running main: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'smtpserver': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain jvm 1| org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'smtpserver': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain 2) jvm 1| WrapperSimpleApp: Encountered an error running main: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'pop3server': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain jvm 1| org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'pop3server': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Question on Apache James App 3.0-beta4
On 03/20/2012 12:26 PM, Eric Charles wrote: Felix, svn down atm... copy/paste of pop3-template.conf here after. Sorry, my English is too bad to understand what you mean by copy/paste here after. I copied the below conf and it works (if you meant this). BTW When touching the template files anyway I wonder if we could remove the spaces for integer/long values in the configuration, e.g. connectionLimit 0 /connectionLimit Regards Felix pop3servers !-- The POP3 server is enabled by default -- !-- Disabling blocks will stop them from listening, -- !-- but does not free as many resources as removing them would -- pop3server enabled=true jmxNamepop3server/jmxName !-- Configure this to bind to a specific inetaddress -- !-- port 995 is the well-known/IANA registered port for POP3S ie over SSL/TLS -- !-- port 110 is the well-known/IANA registered port for Standard POP3 -- bind0.0.0.0:110/bind connectionBacklog200/connectionBacklog !-- Set to true to support STARTTLS or SSL for the Socket. To use this you need to copy sunjce_provider.jar to /path/james/lib directory. -- tls socketTLS=false startTLS=false !-- To create a new keystore execute: keytool -genkey -alias james -keyalg RSA -keystore /path/to/james/conf/keystore -- keystorefile://conf/keystore/keystore secretyoursecret/secret providerorg.bouncycastle.jce.provider.BouncyCastleProvider/provider /tls !-- This is the name used by the server to identify itself in the POP3 -- !-- protocol. If autodetect is TRUE, the server will discover its -- !-- own host name and use that in the protocol. If discovery fails, -- !-- the value of 'localhost' is used. If autodetect is FALSE, James -- !-- will use the specified value. -- !-- helloName autodetect=truemyMailServer/helloName -- !-- connection timeout in secconds -- connectiontimeout1200/connectiontimeout !-- Set the maximum simultaneous incoming connections for this service -- connectionLimit 0 /connectionLimit !-- Set the maximum simultaneous incoming connections per IP for this service -- connectionLimitPerIP 0 /connectionLimitPerIP handlerchain !-- This loads the core CommandHandlers. Only remove this if you really -- !-- know what you are doing -- handler class=org.apache.james.pop3server.core.CoreCmdHandlerLoader/ /handlerchain /pop3server /pop3servers On 20/03/12 12:16, Eric Charles wrote: Hi Felix, Yes, you got both of them: The idea around template, and the issue for pop3 and stmp :) I (re)checked, and there is a remaining handler tag from previous versions. Could you retry with the template I just committed. I would like to collect more feedback before canceling and relaunch tests. Thx again for your reviews and tests! Eric On 20/03/12 11:03, Felix Knecht wrote: Hi all I start a separate thread to not pollute the voting thread with other stuff. I just built the the app from the svn tag (works fine) and unzipped it. Because I want to run it as common user I need to change the ports. To do so I copy the imapserver-template.conf to imapserver.conf and put a port higher than 1024. The same I do with pop3server and smtpserver. Everything starts up fine as long as I disable the pop3server and the smptserver. Enabling the smptserver I get Exception 1), enabling pop3server I get Exception 2). Should template be exactly for this? Copy the template, adapt to you needs, keep all other entires in the template unchanged (these should be the default ones) and the application works? Regards Felix 1) jvm 1 | WrapperSimpleApp: Encountered an error running main: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'smtpserver': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain jvm 1 | org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'smtpserver': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain 2) jvm 1 | WrapperSimpleApp: Encountered an error running main: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'pop3server': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain jvm 1 | org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'pop3server': Invocation of init method failed; nested exception is java.lang.IllegalArgumentException: Passed in key must select exactly one node: handlerchain - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail
Re: [VOTE] Release Apache James Server and App 3.0-beta4
[X] +0 No time to review It seem to work for most devs except me, so this seems to be a problem of my machine setup.. Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Server 3.0b4 artifacts
I do have test failures building the tagged code. Is this only a problem of mine? Running org.apache.james.filesystem.api.SieveFileRepositoryTestCase Tests run: 20, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 0.091 sec FAILURE! Results : Failed tests: testListScripts(org.apache.james.filesystem.api.SieveFileRepositoryTestCase): expected:... but was:...1 Tests run: 20, Failures: 1, Errors: 0, Skipped: 0 [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache James Server ... SUCCESS [0.881s] [INFO] Apache James Server Lifecycle API . SUCCESS [1.001s] [INFO] Apache James Server Filesystem API FAILURE [1.236s] [INFO] Apache James Server Data API .. SKIPPED mvn -version Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: /etc/alternatives/mvn Java version: 1.7.0_02, vendor: Oracle Corporation Java home: /usr/lib/jvm/jdk1.7.0_02/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.2.8-3.fc16.x86_64, arch: amd64, family: unix Regards Felix On 03/01/2012 04:13 PM, Eric Charles wrote: Hi there, We still need your reviews and votes now for James server 3.0b4 artifacts release. Just after, we will be able to push the long awaited app bundle. So please cast your VOTE for Apache James Server 3.0b4 artifacts release: [ ] +1 Please release [ ] +0 No time to review [ ] -1 Something is wrong Release Notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10411version=12317240 SVN tag: https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta4/ Source tarball: https://repository.apache.org/content/repositories/orgapachejames-004/org/apache/james/james-server/3.0-beta4/james-server-3.0-beta4-source-release.zip Staging repository: https://repository.apache.org/content/repositories/orgapachejames-004/ Thx. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Server and App 3.0-beta4
Still some problems/errors when building: [INFO] Surefire report directory: /tmp/james-server-3.0-beta4/data-hbase/target/surefire-reports --- T E S T S --- --- T E S T S --- Running org.apache.james.JamesServerHBaseSuiteTest 2012-03-02 20:26:48,381 [main] WARN org.apache.hadoop.metrics2.impl.MetricsSystemImpl - Metrics system not started: Cannot locate configuration: tried hadoop-metrics2-namenode.properties, hadoop-metrics2.properties Starting DataNode 0 with dfs.data.dir: /tmp/james-server-3.0-beta4/data-hbase/target/test-data/9ff31753-87d1-4a65-ad1e-2ce73affe112/dfs/data/data1,/tmp/james-server-3.0-beta4/data-hbase/target/test-data/9ff31753-87d1-4a65-ad1e-2ce73affe112/dfs/data/data2 2012-03-02 20:26:48,810 [main] WARN org.apache.hadoop.metrics2.impl.MetricsSystemImpl - Metrics system not started: Cannot locate configuration: tried hadoop-metrics2-datanode.properties, hadoop-metrics2.properties 2012-03-02 20:26:48,810 [main] WARN org.apache.hadoop.metrics2.util.MBeans - Hadoop:service=DataNode,name=MetricsSystem,sub=Control javax.management.InstanceAlreadyExistsException: MXBean already registered with name Hadoop:service=NameNode,name=MetricsSystem,sub=Control at com.sun.jmx.mbeanserver.MXBeanLookup.addReference(MXBeanLookup.java:120) at com.sun.jmx.mbeanserver.MXBeanSupport.register(MXBeanSupport.java:143) at com.sun.jmx.mbeanserver.MBeanSupport.preRegister2(MBeanSupport.java:183) And no, it's not a Windows machine: Apache Maven 3.0.4 (r1232337; 2012-01-17 09:44:56+0100) Maven home: /etc/alternatives/mvn Java version: 1.6.0_29, vendor: Sun Microsystems Inc. Java home: /usr/lib/jvm/jdk1.6.0_29/jre Default locale: en_US, platform encoding: UTF-8 OS name: linux, version: 3.2.8-3.fc16.x86_64, arch: amd64, family: unix Is it only me having these problems? Felix On 03/02/2012 04:27 PM, Eric Charles wrote: Hi there, We are ready to vote for James server application 3.0-beta4 based on the latest and greatest Protocols 1.6.2, Mailbox 0.3, IMAP 0.4 and jSieve 0.5. This vote is a conjoint vote to release server and app 3.0-beta4 projects. So please cast your VOTE for Apache James Server 3.0b4 release: [ ] +1 Please release [ ] +0 No time to review [ ] -1 Something is wrong Release Notes: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10411version=12317240 SVN tags: https://svn.apache.org/repos/asf/james/app/tags/apache-james-3.0-beta4/ https://svn.apache.org/repos/asf/james/server/tags/james-server-3.0-beta4/ Source tarballs: https://repository.apache.org/content/repositories/orgapachejames-043/org/apache/james/apache-james/3.0-beta4/apache-james-3.0-beta4-app.zip https://repository.apache.org/content/repositories/orgapachejames-042/org/apache/james/james-server/3.0-beta4/james-server-3.0-beta4-source-release.zip Staging repositories: https://repository.apache.org/content/repositories/orgapachejames-043/ https://repository.apache.org/content/repositories/orgapachejames-042/ Thx. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James IMAP 0.3
[X] +1 Please release Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [ANNOUNCE] Welcome Jochen Gazda as Apache James Committer
On 02/23/2012 11:17 AM, Felix Knecht wrote: On 02/22/2012 07:39 PM, Eric Charles wrote: Hi All, The Apache James PMC recently extended committer karma to Jochen Gazda and he has accepted. Welcome aboard Gazda! Welcome aboard and congrats Gazda! Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Mailbox 0.4
On 02/23/2012 04:36 PM, Felix Knecht wrote: [X] +1 Please release Thanks Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE][2nd] Release Apache James jSieve 0.5
On 02/23/2012 04:38 PM, Felix Knecht wrote: [X] +1 Please release Thanks Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James jSieve 0.5
[X] +1 Please release Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Project 1.8.1
[X] +1 Please release Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Protocols 1.6.2
[X] +1 Please release Thanks Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Protocols 1.6.1
[X] +0 No time to review Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Protocols 1.6.0 (second take)
[X] +1 Yes, please release Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Protocols 1.6.0
[X] +1 Yes, please release Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Mime4j 0.7.2
[X] +1 Yes please release Thanks and regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Protocols 1.6.0-RC1
[X] +1 Yes, please release Felix On 12/21/2011 09:01 PM, Norman Maurer wrote: Hi there, over the last few weeks I worked on improving the Apache James Protocols code. I think after fixing the last outstanding bug today (Stefano, yay) we are ready to release 1.6.0-RC1. The changes can be found here: https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311060version=12319160 Artifacts for review: https://repository.apache.org/content/repositories/orgapachejames-380/ [ ] +1 Yes, please release [ ] +0 No time to review [ ] -1 Something is wrong - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: I deployed mailbox site
On 12/18/2011 05:57 PM, Ioan Eugen Stan wrote: 2011/12/18 Eric Charlese...@apache.org: Hi Ioan, The current deployment does not show anymore the content (only reports are show, but not the pages defined in http://svn.apache.org/repos/asf/james/mailbox/trunk/src/site/xdoc/). Does you locally generated site look good? Thx, Eric Yes, they look good, but I think I messed up with the deployment. I guess the reports got uploaded when I did: mvn site:site -P site-reports mvn site-deploy doesn't seem to properly deploy multi-project site. This should work, if we may have a bug. IIRC mvn site-deploy should generate and deploy the documentations site to somewhere/ and mvn site-deploy -Psite-reports should deploy the reports site to somewhere/technical-reports/ (when using james-project -pom-1.8 as parent). If it doesn't we do have a special feature which needs to be fixes. Regards Felix I redeployed with mvn site:site and mvn site:deploy. I hope things will be well. As a side note, I think the information displayed by the reports is useful for developers and should be available on the site. I will like to somehow include those reports on the site, somewhere in the development section. What do you think? It will take some time until the web servers get updated. Bye, - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Protocols 1.6-beta3 (second try)
[X] +1 Please release - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James jSPF 1.0.0 (second try)
[X] +1 Yeah, please release - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James jSPF 1.0.0
[X] -1 Something is wrong I can't build using Java 1.5, looks like org.apache.felix:maven-bundle-plugin:2.3.5 has a problem using Java-1.5 [felix@asgard apache-jspf-project-1.0.0]$ svn info Path: . URL: https://svn.apache.org/repos/asf/james/jspf/tags/apache-jspf-project-1.0.0 Repository Root: https://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 1206575 Node Kind: directory Schedule: normal Last Changed Author: norman Last Changed Rev: 1206512 Last Changed Date: 2011-11-26 18:42:23 +0100 (Sat, 26 Nov 2011) [felix@asgard apache-jspf-project-1.0.0]$ [felix@asgard apache-jspf-project-1.0.0]$ java -version java version 1.5.0_22 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_22-b03, mixed mode) [felix@asgard apache-jspf-project-1.0.0]$ mvn clean install [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] Apache JAMES jSPF [INFO] Apache JAMES OpenSPF Tester [INFO] Apache JAMES jSPF Resolver [INFO] Apache JAMES jSPF Assembly [INFO] [INFO] [INFO] Building Apache JAMES jSPF 1.0.0 [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ apache-jspf-project --- [INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ apache-jspf-project --- [INFO] [INFO] --- maven-site-plugin:3.0:attach-descriptor (attach-descriptor) @ apache-jspf-project --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ apache-jspf-project --- [INFO] Installing /tmp/apache-jspf-project-1.0.0/pom.xml to /home/felix/.m2/repository/org/apache/james/apache-jspf-project/1.0.0/apache-jspf-project-1.0.0.pom [INFO] Installing /tmp/apache-jspf-project-1.0.0/target/apache-jspf-project-1.0.0-site.xml to /home/felix/.m2/repository/org/apache/james/apache-jspf-project/1.0.0/apache-jspf-project-1.0.0-site.xml [INFO] [INFO] [INFO] Building Apache JAMES OpenSPF Tester 1.0.0 [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ apache-jspf-tester --- [INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ apache-jspf-tester --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ apache-jspf-tester --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 8 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ apache-jspf-tester --- [INFO] Compiling 6 source files to /tmp/apache-jspf-project-1.0.0/tester/target/classes [INFO] [INFO] --- maven-bundle-plugin:2.3.5:manifest (bundle-manifest) @ apache-jspf-tester --- [INFO] [INFO] Reactor Summary: [INFO] [INFO] Apache JAMES jSPF . SUCCESS [0.897s] [INFO] Apache JAMES OpenSPF Tester ... FAILURE [0.847s] [INFO] Apache JAMES jSPF Resolver SKIPPED [INFO] Apache JAMES jSPF Assembly SKIPPED [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.394s [INFO] Finished at: Sat Nov 26 21:14:58 CET 2011 [INFO] Final Memory: 26M/981M [INFO] [ERROR] Failed to execute goal org.apache.felix:maven-bundle-plugin:2.3.5:manifest (bundle-manifest) on project apache-jspf-tester: Execution bundle-manifest of goal org.apache.felix:maven-bundle-plugin:2.3.5:manifest failed: An API incompatibility was encountered while executing org.apache.felix:maven-bundle-plugin:2.3.5:manifest: java.lang.NoSuchMethodError: java.lang.String.getBytes(Ljava/nio/charset/Charset;)[B [ERROR] - [ERROR] realm =pluginorg.apache.felix:maven-bundle-plugin:2.3.5 [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy [ERROR] urls[0] = file:/home/felix/.m2/repository/org/apache/felix/maven-bundle-plugin/2.3.5/maven-bundle-plugin-2.3.5.jar [ERROR] urls[1] = file:/home/felix/.m2/repository/biz/aQute/bndlib/1.43.0/bndlib-1.43.0.jar [ERROR] urls[2] = file:/home/felix/.m2/repository/org/apache/felix/org.apache.felix.bundlerepository/1.6.6/org.apache.felix.bundlerepository-1.6.6.jar [ERROR] urls[3] = file:/home/felix/.m2/repository/org/osgi/org.osgi.core/4.1.0/org.osgi.core-4.1.0.jar [ERROR] urls[4] =
Re: [VOTE] Release Apache James Protocols 1.6-beta3
[X] -1 Something is wrong Sorry, but doesn't works for me: [felix@asgard protocols-1.6-beta3]$ svn info Path: . URL: https://svn.apache.org/repos/asf/james/protocols/tags/protocols-1.6-beta3 Repository Root: https://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 1206576 Node Kind: directory Schedule: normal Last Changed Author: norman Last Changed Rev: 1206573 Last Changed Date: 2011-11-26 21:04:59 +0100 (Sat, 26 Nov 2011) [felix@asgard protocols-1.6-beta3]$ java -version java version 1.5.0_22 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_22-b03, mixed mode) [felix@asgard protocols-1.6-beta3]$ mvn clean install [INFO] Scanning for projects... [INFO] [INFO] Reactor Build Order: [INFO] [INFO] Apache James Protocols [INFO] Apache James Protocols API [INFO] Apache James Protocols SMTP [INFO] Apache James Protocols LMTP [INFO] Apache James Protocols Netty Implementation [INFO] Apache James Protocols POP3 [INFO] [INFO] [INFO] Building Apache James Protocols 1.6-beta3 [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ protocols --- [INFO] Deleting /tmp/protocols-1.6-beta3/target [INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ protocols --- [INFO] [INFO] --- maven-site-plugin:3.0:attach-descriptor (attach-descriptor) @ protocols --- [INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ protocols --- [INFO] Installing /tmp/protocols-1.6-beta3/pom.xml to /home/felix/.m2/repository/org/apache/james/protocols/1.6-beta3/protocols-1.6-beta3.pom [INFO] Installing /tmp/protocols-1.6-beta3/target/protocols-1.6-beta3-site.xml to /home/felix/.m2/repository/org/apache/james/protocols/1.6-beta3/protocols-1.6-beta3-site.xml [INFO] [INFO] [INFO] Building Apache James Protocols API 1.6-beta3 [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ protocols-api --- [INFO] Deleting /tmp/protocols-1.6-beta3/api/target [INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ protocols-api --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ protocols-api --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /tmp/protocols-1.6-beta3/api/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ protocols-api --- [INFO] Compiling 33 source files to /tmp/protocols-1.6-beta3/api/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /tmp/protocols-1.6-beta3/api/src/main/java/org/apache/james/protocols/api/handler/AbstractCommandDispatcher.java:[134,27] cannot find symbol symbol : constructor String(byte[],java.nio.charset.Charset) location: class java.lang.String [ERROR] /tmp/protocols-1.6-beta3/api/src/main/java/org/apache/james/protocols/api/ProtocolImpl.java:[38,5] method does not override a method from its superclass [ERROR] /tmp/protocols-1.6-beta3/api/src/main/java/org/apache/james/protocols/api/ProtocolImpl.java:[43,5] method does not override a method from its superclass [ERROR] /tmp/protocols-1.6-beta3/api/src/main/java/org/apache/james/protocols/api/FutureResponseImpl.java:[53,5] method does not override a method from its superclass [ERROR] /tmp/protocols-1.6-beta3/api/src/main/java/org/apache/james/protocols/api/FutureResponseImpl.java:[65,5] method does not override a method from its superclass [ERROR] /tmp/protocols-1.6-beta3/api/src/main/java/org/apache/james/protocols/api/FutureResponseImpl.java:[74,5] method does not override a method from its superclass [ERROR] /tmp/protocols-1.6-beta3/api/src/main/java/org/apache/james/protocols/api/FutureResponseImpl.java:[79,5] method does not override a method from its superclass [ERROR] /tmp/protocols-1.6-beta3/api/src/main/java/org/apache/james/protocols/api/FutureResponseImpl.java:[86,5] method does not override a method from its superclass [ERROR] /tmp/protocols-1.6-beta3/api/src/main/java/org/apache/james/protocols/api/FutureResponseImpl.java:[93,5] method does not override a method from its superclass [ERROR] /tmp/protocols-1.6-beta3/api/src/main/java/org/apache/james/protocols/api/ProtocolSessionImpl.java:[51,5] method does not override a method from its superclass [ERROR]
Re: [VOTE] Release Apache James jSPF 1.0.0
Hi Norman seems like its fixed in maven-bundle-plugin 2.3.6 https://issues.apache.org/jira/browse/FELIX-3037 Let me adjust the version and start the vote again. I don't think 2.3.6 is already available, but downgrading will fix it: [felix@asgard apache-jspf-project-1.0.0]$ svn info Path: . URL: https://svn.apache.org/repos/asf/james/jspf/tags/apache-jspf-project-1.0.0 Repository Root: https://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-ffa450edef68 Revision: 1206575 Node Kind: directory Schedule: normal Last Changed Author: norman Last Changed Rev: 1206512 Last Changed Date: 2011-11-26 18:42:23 +0100 (Sat, 26 Nov 2011) [felix@asgard apache-jspf-project-1.0.0]$ svn diff Index: pom.xml === --- pom.xml (revision 1206575) +++ pom.xml (working copy) @@ -122,4 +122,17 @@ /dependency /dependencies /dependencyManagement +build +pluginManagement +plugins +!-- Order by groupId / artifactId / scope -- +plugin +groupIdorg.apache.felix/groupId +artifactIdmaven-bundle-plugin/artifactId +version2.3.4/version +/plugin +/plugins +/pluginManagement +/build /project + Thanks, Norman 2011/11/26 Felix Knechtfel...@apache.org [X] -1 Something is wrong I can't build using Java 1.5, looks like org.apache.felix:maven-bundle-**plugin:2.3.5 has a problem using Java-1.5 [felix@asgard apache-jspf-project-1.0.0]$ svn info Path: . URL: https://svn.apache.org/repos/**asf/james/jspf/tags/apache-** jspf-project-1.0.0https://svn.apache.org/repos/asf/james/jspf/tags/apache-jspf-project-1.0.0 Repository Root: https://svn.apache.org/repos/**asfhttps://svn.apache.org/repos/asf Repository UUID: 13f79535-47bb-0310-9956-**ffa450edef68 Revision: 1206575 Node Kind: directory Schedule: normal Last Changed Author: norman Last Changed Rev: 1206512 Last Changed Date: 2011-11-26 18:42:23 +0100 (Sat, 26 Nov 2011) [felix@asgard apache-jspf-project-1.0.0]$ [felix@asgard apache-jspf-project-1.0.0]$ java -version java version 1.5.0_22 Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03) Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_22-b03, mixed mode) [felix@asgard apache-jspf-project-1.0.0]$ mvn clean install [INFO] Scanning for projects... [INFO] --**--** [INFO] Reactor Build Order: [INFO] [INFO] Apache JAMES jSPF [INFO] Apache JAMES OpenSPF Tester [INFO] Apache JAMES jSPF Resolver [INFO] Apache JAMES jSPF Assembly [INFO] [INFO] --**--** [INFO] Building Apache JAMES jSPF 1.0.0 [INFO] --**--** [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ apache-jspf-project --- [INFO] [INFO] --- maven-remote-resources-plugin:**1.2.1:process (default) @ apache-jspf-project --- [INFO] [INFO] --- maven-site-plugin:3.0:attach-**descriptor (attach-descriptor) @ apache-jspf-project --- [INFO] [INFO] --- maven-install-plugin:2.3.1:**install (default-install) @ apache-jspf-project --- [INFO] Installing /tmp/apache-jspf-project-1.0.**0/pom.xml to /home/felix/.m2/repository/**org/apache/james/apache-jspf-** project/1.0.0/apache-jspf-**project-1.0.0.pom [INFO] Installing /tmp/apache-jspf-project-1.0.** 0/target/apache-jspf-project-**1.0.0-site.xml to /home/felix/.m2/repository/**org/apache/james/apache-jspf-** project/1.0.0/apache-jspf-**project-1.0.0-site.xml [INFO] [INFO] --**--** [INFO] Building Apache JAMES OpenSPF Tester 1.0.0 [INFO] --**--** [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ apache-jspf-tester --- [INFO] [INFO] --- maven-remote-resources-plugin:**1.2.1:process (default) @ apache-jspf-tester --- [INFO] [INFO] --- maven-resources-plugin:2.5:**resources (default-resources) @ apache-jspf-tester --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] Copying 8 resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:**compile (default-compile) @ apache-jspf-tester --- [INFO] Compiling 6 source files to /tmp/apache-jspf-project-1.0.** 0/tester/target/classes [INFO] [INFO] --- maven-bundle-plugin:2.3.5:**manifest (bundle-manifest) @ apache-jspf-tester --- [INFO] --**--** [INFO] Reactor Summary: [INFO] [INFO] Apache JAMES jSPF ..**... SUCCESS [0.897s] [INFO] Apache JAMES OpenSPF Tester ... FAILURE [0.847s] [INFO] Apache JAMES jSPF Resolver SKIPPED [INFO] Apache JAMES jSPF
Re: svn commit: r1206590 - in /james/protocols/trunk: api/pom.xml lmtp/pom.xml netty/pom.xml pop3/pom.xml smtp/pom.xml
Why not doing this only once in the pluginManagement section in the top pom.xml? On 11/26/2011 10:05 PM, nor...@apache.org wrote: Author: norman Date: Sat Nov 26 21:05:01 2011 New Revision: 1206590 URL: http://svn.apache.org/viewvc?rev=1206590view=rev Log: Downgrade bundle plugin to be able to compile with java5 Modified: james/protocols/trunk/api/pom.xml james/protocols/trunk/lmtp/pom.xml james/protocols/trunk/netty/pom.xml james/protocols/trunk/pop3/pom.xml james/protocols/trunk/smtp/pom.xml Modified: james/protocols/trunk/api/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/api/pom.xml?rev=1206590r1=1206589r2=1206590view=diff == --- james/protocols/trunk/api/pom.xml (original) +++ james/protocols/trunk/api/pom.xml Sat Nov 26 21:05:01 2011 @@ -69,6 +69,8 @@ plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId +!-- See https://issues.apache.org/jira/browse/FELIX-3037 -- +version2.3.4/version executions execution idbundle-manifest/id Modified: james/protocols/trunk/lmtp/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/lmtp/pom.xml?rev=1206590r1=1206589r2=1206590view=diff == --- james/protocols/trunk/lmtp/pom.xml (original) +++ james/protocols/trunk/lmtp/pom.xml Sat Nov 26 21:05:01 2011 @@ -87,6 +87,8 @@ plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId +!-- See https://issues.apache.org/jira/browse/FELIX-3037 -- +version2.3.4/version executions execution idbundle-manifest/id Modified: james/protocols/trunk/netty/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/netty/pom.xml?rev=1206590r1=1206589r2=1206590view=diff == --- james/protocols/trunk/netty/pom.xml (original) +++ james/protocols/trunk/netty/pom.xml Sat Nov 26 21:05:01 2011 @@ -73,6 +73,8 @@ plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId +!-- See https://issues.apache.org/jira/browse/FELIX-3037 -- +version2.3.4/version executions execution idbundle-manifest/id Modified: james/protocols/trunk/pop3/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/pop3/pom.xml?rev=1206590r1=1206589r2=1206590view=diff == --- james/protocols/trunk/pop3/pom.xml (original) +++ james/protocols/trunk/pop3/pom.xml Sat Nov 26 21:05:01 2011 @@ -74,6 +74,8 @@ plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId +!-- See https://issues.apache.org/jira/browse/FELIX-3037 -- +version2.3.4/version executions execution idbundle-manifest/id Modified: james/protocols/trunk/smtp/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/smtp/pom.xml?rev=1206590r1=1206589r2=1206590view=diff == --- james/protocols/trunk/smtp/pom.xml (original) +++ james/protocols/trunk/smtp/pom.xml Sat Nov 26 21:05:01 2011 @@ -90,6 +90,8 @@ plugin groupIdorg.apache.felix/groupId artifactIdmaven-bundle-plugin/artifactId +!-- See https://issues.apache.org/jira/browse/FELIX-3037 -- +version2.3.4/version executions execution idbundle-manifest/id - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: svn commit: r1206590 - in /james/protocols/trunk: api/pom.xml lmtp/pom.xml netty/pom.xml pop3/pom.xml smtp/pom.xml
On 11/26/2011 10:09 PM, Norman Maurer wrote: Don't know ;) Adjust it if you have a few minutes ;) Done. Thanks, Norman 2011/11/26 Felix Knechtfel...@apache.org Why not doing this only once in the pluginManagement section in the top pom.xml? On 11/26/2011 10:05 PM, nor...@apache.org wrote: Author: norman Date: Sat Nov 26 21:05:01 2011 New Revision: 1206590 URL: http://svn.apache.org/viewvc?**rev=1206590view=revhttp://svn.apache.org/viewvc?rev=1206590view=rev Log: Downgrade bundle plugin to be able to compile with java5 Modified: james/protocols/trunk/api/pom.**xml james/protocols/trunk/lmtp/**pom.xml james/protocols/trunk/netty/**pom.xml james/protocols/trunk/pop3/**pom.xml james/protocols/trunk/smtp/**pom.xml Modified: james/protocols/trunk/api/pom.**xml URL: http://svn.apache.org/viewvc/**james/protocols/trunk/api/pom.** xml?rev=1206590r1=1206589r2=**1206590view=diffhttp://svn.apache.org/viewvc/james/protocols/trunk/api/pom.xml?rev=1206590r1=1206589r2=1206590view=diff ==**==** == --- james/protocols/trunk/api/pom.**xml (original) +++ james/protocols/trunk/api/pom.**xml Sat Nov 26 21:05:01 2011 @@ -69,6 +69,8 @@ plugin groupIdorg.apache.felix/**groupId artifactIdmaven-bundle-**plugin/artifactId +!-- See https://issues.apache.org/**jira/browse/FELIX-3037https://issues.apache.org/jira/browse/FELIX-3037-- +version2.3.4/version executions execution idbundle-manifest/id Modified: james/protocols/trunk/lmtp/**pom.xml URL: http://svn.apache.org/viewvc/**james/protocols/trunk/lmtp/** pom.xml?rev=1206590r1=**1206589r2=1206590view=diffhttp://svn.apache.org/viewvc/james/protocols/trunk/lmtp/pom.xml?rev=1206590r1=1206589r2=1206590view=diff ==**==** == --- james/protocols/trunk/lmtp/**pom.xml (original) +++ james/protocols/trunk/lmtp/**pom.xml Sat Nov 26 21:05:01 2011 @@ -87,6 +87,8 @@ plugin groupIdorg.apache.felix/**groupId artifactIdmaven-bundle-**plugin/artifactId +!-- See https://issues.apache.org/**jira/browse/FELIX-3037https://issues.apache.org/jira/browse/FELIX-3037-- +version2.3.4/version executions execution idbundle-manifest/id Modified: james/protocols/trunk/netty/**pom.xml URL: http://svn.apache.org/viewvc/**james/protocols/trunk/netty/** pom.xml?rev=1206590r1=**1206589r2=1206590view=diffhttp://svn.apache.org/viewvc/james/protocols/trunk/netty/pom.xml?rev=1206590r1=1206589r2=1206590view=diff ==**==** == --- james/protocols/trunk/netty/**pom.xml (original) +++ james/protocols/trunk/netty/**pom.xml Sat Nov 26 21:05:01 2011 @@ -73,6 +73,8 @@ plugin groupIdorg.apache.felix/**groupId artifactIdmaven-bundle-**plugin/artifactId +!-- See https://issues.apache.org/**jira/browse/FELIX-3037https://issues.apache.org/jira/browse/FELIX-3037-- +version2.3.4/version executions execution idbundle-manifest/id Modified: james/protocols/trunk/pop3/**pom.xml URL: http://svn.apache.org/viewvc/**james/protocols/trunk/pop3/** pom.xml?rev=1206590r1=**1206589r2=1206590view=diffhttp://svn.apache.org/viewvc/james/protocols/trunk/pop3/pom.xml?rev=1206590r1=1206589r2=1206590view=diff ==**==** == --- james/protocols/trunk/pop3/**pom.xml (original) +++ james/protocols/trunk/pop3/**pom.xml Sat Nov 26 21:05:01 2011 @@ -74,6 +74,8 @@ plugin groupIdorg.apache.felix/**groupId artifactIdmaven-bundle-**plugin/artifactId +!-- See https://issues.apache.org/**jira/browse/FELIX-3037https://issues.apache.org/jira/browse/FELIX-3037-- +version2.3.4/version executions execution idbundle-manifest/id Modified: james/protocols/trunk/smtp/**pom.xml URL: http://svn.apache.org/viewvc/**james/protocols/trunk/smtp/** pom.xml?rev=1206590r1=**1206589r2=1206590view=diffhttp://svn.apache.org/viewvc/james/protocols/trunk/smtp/pom.xml?rev=1206590r1=1206589r2=1206590view=diff ==**==** == --- james/protocols/trunk/smtp/**pom.xml (original) +++ james/protocols/trunk/smtp/**pom.xml Sat Nov 26 21:05:01 2011 @@ -90,6 +90,8 @@ plugin groupIdorg.apache.felix/**groupId artifactIdmaven-bundle-**plugin/artifactId +!-- See https://issues.apache.org/**jira/browse/FELIX-3037https://issues.apache.org/jira/browse/FELIX-3037-- +version2.3.4/version
Re: svn commit: r1206602 - in /james/protocols/trunk: api/pom.xml lmtp/pom.xml netty/pom.xml pom.xml pop3/pom.xml smtp/pom.xml
Sorry - I'm a bad boy this evening - but I don't think it's working, I still have failures :-( Regards Felix [INFO] [INFO] Building Apache James Protocols SMTP 1.6-beta3 [INFO] [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ protocols-smtp --- [INFO] Deleting /home/felix/svn/apache/james/current/protocols/smtp/target [INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ protocols-smtp --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ protocols-smtp --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/felix/svn/apache/james/current/protocols/smtp/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ protocols-smtp --- [INFO] Compiling 66 source files to /home/felix/svn/apache/james/current/protocols/smtp/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/main/java/org/apache/james/protocols/smtp/core/ReceivedDataLineFilter.java:[87,74] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/main/java/org/apache/james/protocols/smtp/core/ReceivedDataLineFilter.java:[121,58] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/main/java/org/apache/james/protocols/smtp/core/ReceivedDataLineFilter.java:[126,69] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/main/java/org/apache/james/protocols/smtp/core/ReceivedDataLineFilter.java:[139,69] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/main/java/org/apache/james/protocols/smtp/core/ReceivedDataLineFilter.java:[146,36] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/main/java/org/apache/james/protocols/smtp/core/esmtp/AuthCmdHandler.java:[69,42] cannot find symbol symbol : constructor String(byte[],java.nio.charset.Charset) location: class java.lang.String [INFO] 6 errors On 11/26/2011 10:31 PM, nor...@apache.org wrote: Author: norman Date: Sat Nov 26 21:31:46 2011 New Revision: 1206602 URL: http://svn.apache.org/viewvc?rev=1206602view=rev Log: [maven-release-plugin] prepare release protocols-1.6-beta3 Modified: james/protocols/trunk/api/pom.xml james/protocols/trunk/lmtp/pom.xml james/protocols/trunk/netty/pom.xml james/protocols/trunk/pom.xml james/protocols/trunk/pop3/pom.xml james/protocols/trunk/smtp/pom.xml Modified: james/protocols/trunk/api/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/api/pom.xml?rev=1206602r1=1206601r2=1206602view=diff == --- james/protocols/trunk/api/pom.xml (original) +++ james/protocols/trunk/api/pom.xml Sat Nov 26 21:31:46 2011 @@ -23,7 +23,7 @@ parent artifactIdprotocols/artifactId groupIdorg.apache.james/groupId -version1.6-beta4-SNAPSHOT/version +version1.6-beta3/version relativePath../pom.xml/relativePath /parent Modified: james/protocols/trunk/lmtp/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/lmtp/pom.xml?rev=1206602r1=1206601r2=1206602view=diff == --- james/protocols/trunk/lmtp/pom.xml (original) +++ james/protocols/trunk/lmtp/pom.xml Sat Nov 26 21:31:46 2011 @@ -23,7 +23,7 @@ parent artifactIdprotocols/artifactId groupIdorg.apache.james/groupId -version1.6-beta4-SNAPSHOT/version +version1.6-beta3/version relativePath../pom.xml/relativePath /parent Modified: james/protocols/trunk/netty/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/netty/pom.xml?rev=1206602r1=1206601r2=1206602view=diff == --- james/protocols/trunk/netty/pom.xml (original) +++ james/protocols/trunk/netty/pom.xml Sat Nov 26 21:31:46 2011 @@ -23,7 +23,7 @@ parent artifactIdprotocols/artifactId groupIdorg.apache.james/groupId -version1.6-beta4-SNAPSHOT/version
Re: svn commit: r1206602 - in /james/protocols/trunk: api/pom.xml lmtp/pom.xml netty/pom.xml pom.xml pop3/pom.xml smtp/pom.xml
Nope [INFO] BUILD FAILURE [INFO] [INFO] Total time: 5.405s [INFO] Finished at: Sat Nov 26 22:50:35 CET 2011 [INFO] Final Memory: 31M/981M [INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (default-testCompile) on project protocols-smtp: Compilation failure: Compilation failure: [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/test/java/org/apache/james/protocols/smtp/BaseFakeSMTPSession.java:[218,5] method does not override a method from its superclass [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/test/java/org/apache/james/protocols/smtp/BaseFakeSMTPSession.java:[224,5] method does not override a method from its superclass [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvn goals -rf :protocols-smtp On 11/26/2011 10:48 PM, Norman Maurer wrote: Hi Felix, before I re-roll the VOTE again could you check if current trunk works for you ? Thanks! Norman 2011/11/26 Norman Maurernorman.mau...@googlemail.com I see... I just download a workaround to get java 5 working again on osx lion. I think then I can test it better. Thanks again for all the testing ! Stay tuned, Norman 2011/11/26 Felix Knechtfel...@apache.org Sorry - I'm a bad boy this evening - but I don't think it's working, I still have failures :-( Regards Felix [INFO] --**--** [INFO] Building Apache James Protocols SMTP 1.6-beta3 [INFO] --**--** [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ protocols-smtp --- [INFO] Deleting /home/felix/svn/apache/james/** current/protocols/smtp/target [INFO] [INFO] --- maven-remote-resources-plugin:**1.2.1:process (default) @ protocols-smtp --- [INFO] [INFO] --- maven-resources-plugin:2.5:**resources (default-resources) @ protocols-smtp --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/felix/svn/apache/james/* *current/protocols/smtp/src/**main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:**compile (default-compile) @ protocols-smtp --- [INFO] Compiling 66 source files to /home/felix/svn/apache/james/** current/protocols/smtp/target/**classes [INFO] --**--**- [ERROR] COMPILATION ERROR : [INFO] --**--**- [ERROR] /home/felix/svn/apache/james/**current/protocols/smtp/src/** main/java/org/apache/james/**protocols/smtp/core/** ReceivedDataLineFilter.java:[**87,74] cannot find symbol symbol : method getBytes(java.nio.charset.**Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/**current/protocols/smtp/src/** main/java/org/apache/james/**protocols/smtp/core/** ReceivedDataLineFilter.java:[**121,58] cannot find symbol symbol : method getBytes(java.nio.charset.**Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/**current/protocols/smtp/src/** main/java/org/apache/james/**protocols/smtp/core/** ReceivedDataLineFilter.java:[**126,69] cannot find symbol symbol : method getBytes(java.nio.charset.**Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/**current/protocols/smtp/src/** main/java/org/apache/james/**protocols/smtp/core/** ReceivedDataLineFilter.java:[**139,69] cannot find symbol symbol : method getBytes(java.nio.charset.**Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/**current/protocols/smtp/src/** main/java/org/apache/james/**protocols/smtp/core/** ReceivedDataLineFilter.java:[**146,36] cannot find symbol symbol : method getBytes(java.nio.charset.**Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/**current/protocols/smtp/src/** main/java/org/apache/james/**protocols/smtp/core/esmtp/**AuthCmdHandler.java:[69,42] cannot find symbol symbol : constructor String(byte[],java.nio.**charset.Charset) location: class java.lang.String [INFO] 6 errors On 11/26/2011 10:31 PM, nor...@apache.org wrote: Author: norman Date: Sat Nov 26 21:31:46 2011 New Revision: 1206602 URL: http://svn.apache.org/viewvc?**rev=1206602view=revhttp://svn.apache.org/viewvc?rev=1206602view=rev Log: [maven-release-plugin]
Re: svn commit: r1206602 - in /james/protocols/trunk: api/pom.xml lmtp/pom.xml netty/pom.xml pom.xml pop3/pom.xml smtp/pom.xml
On 11/26/2011 10:57 PM, Norman Maurer wrote: I got java5 finally working on osx lion again (don't ask about it, its just a pita). Everything compiles now for me. Can you please check one last time ? So does mine :-) I need to go to sleep know, the Tennis match is just over ... Good night ;-) Felix Thanks, Norman 2011/11/26 Felix Knechtfel...@apache.org Nope [INFO] BUILD FAILURE [INFO] --**--** [INFO] Total time: 5.405s [INFO] Finished at: Sat Nov 26 22:50:35 CET 2011 [INFO] Final Memory: 31M/981M [INFO] --**--** [ERROR] Failed to execute goal org.apache.maven.plugins:** maven-compiler-plugin:2.3.2:**testCompile (default-testCompile) on project protocols-smtp: Compilation failure: Compilation failure: [ERROR] /home/felix/svn/apache/james/**current/protocols/smtp/src/** test/java/org/apache/james/**protocols/smtp/** BaseFakeSMTPSession.java:[218,**5] method does not override a method from its superclass [ERROR] /home/felix/svn/apache/james/**current/protocols/smtp/src/** test/java/org/apache/james/**protocols/smtp/** BaseFakeSMTPSession.java:[224,**5] method does not override a method from its superclass [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/**confluence/display/MAVEN/** MojoFailureExceptionhttp://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvngoals -rf :protocols-smtp On 11/26/2011 10:48 PM, Norman Maurer wrote: Hi Felix, before I re-roll the VOTE again could you check if current trunk works for you ? Thanks! Norman 2011/11/26 Norman Maurernorman.maurer@**googlemail.comnorman.mau...@googlemail.com I see... I just download a workaround to get java 5 working again on osx lion. I think then I can test it better. Thanks again for all the testing ! Stay tuned, Norman 2011/11/26 Felix Knechtfel...@apache.org Sorry - I'm a bad boy this evening - but I don't think it's working, I still have failures :-( Regards Felix [INFO] --** --** [INFO] Building Apache James Protocols SMTP 1.6-beta3 [INFO] --** --** [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ protocols-smtp --- [INFO] Deleting /home/felix/svn/apache/james/ current/protocols/smtp/target [INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ protocols-smtp --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ protocols-smtp --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/felix/svn/apache/james/* *current/protocols/smtp/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ protocols-smtp --- [INFO] Compiling 66 source files to /home/felix/svn/apache/james/ current/protocols/smtp/target/classes [INFO] --** --**- [ERROR] COMPILATION ERROR : [INFO] --** --**- [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/** main/java/org/apache/james/protocols/smtp/core/** ReceivedDataLineFilter.java:[87,74] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/** main/java/org/apache/james/protocols/smtp/core/** ReceivedDataLineFilter.java:[121,58] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/** main/java/org/apache/james/protocols/smtp/core/** ReceivedDataLineFilter.java:[126,69] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/** main/java/org/apache/james/protocols/smtp/core/** ReceivedDataLineFilter.java:[139,69] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/** main/java/org/apache/james/protocols/smtp/core/** ReceivedDataLineFilter.java:[146,36] cannot find symbol symbol : method
Re: svn commit: r1206602 - in /james/protocols/trunk: api/pom.xml lmtp/pom.xml netty/pom.xml pom.xml pop3/pom.xml smtp/pom.xml
Just switched CI server builds for protocols and jspf back to build using jdk-1.5. Regards Felix On 11/26/2011 11:00 PM, Felix Knecht wrote: On 11/26/2011 10:57 PM, Norman Maurer wrote: I got java5 finally working on osx lion again (don't ask about it, its just a pita). Everything compiles now for me. Can you please check one last time ? So does mine :-) I need to go to sleep know, the Tennis match is just over ... Good night ;-) Felix Thanks, Norman 2011/11/26 Felix Knechtfel...@apache.org Nope [INFO] BUILD FAILURE [INFO] --**--** [INFO] Total time: 5.405s [INFO] Finished at: Sat Nov 26 22:50:35 CET 2011 [INFO] Final Memory: 31M/981M [INFO] --**--** [ERROR] Failed to execute goal org.apache.maven.plugins:** maven-compiler-plugin:2.3.2:**testCompile (default-testCompile) on project protocols-smtp: Compilation failure: Compilation failure: [ERROR] /home/felix/svn/apache/james/**current/protocols/smtp/src/** test/java/org/apache/james/**protocols/smtp/** BaseFakeSMTPSession.java:[218,**5] method does not override a method from its superclass [ERROR] /home/felix/svn/apache/james/**current/protocols/smtp/src/** test/java/org/apache/james/**protocols/smtp/** BaseFakeSMTPSession.java:[224,**5] method does not override a method from its superclass [ERROR] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/**confluence/display/MAVEN/** MojoFailureExceptionhttp://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException [ERROR] [ERROR] After correcting the problems, you can resume the build with the command [ERROR] mvngoals -rf :protocols-smtp On 11/26/2011 10:48 PM, Norman Maurer wrote: Hi Felix, before I re-roll the VOTE again could you check if current trunk works for you ? Thanks! Norman 2011/11/26 Norman Maurernorman.maurer@**googlemail.comnorman.mau...@googlemail.com I see... I just download a workaround to get java 5 working again on osx lion. I think then I can test it better. Thanks again for all the testing ! Stay tuned, Norman 2011/11/26 Felix Knechtfel...@apache.org Sorry - I'm a bad boy this evening - but I don't think it's working, I still have failures :-( Regards Felix [INFO] --** --** [INFO] Building Apache James Protocols SMTP 1.6-beta3 [INFO] --** --** [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ protocols-smtp --- [INFO] Deleting /home/felix/svn/apache/james/ current/protocols/smtp/target [INFO] [INFO] --- maven-remote-resources-plugin:1.2.1:process (default) @ protocols-smtp --- [INFO] [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ protocols-smtp --- [debug] execute contextualize [INFO] Using 'UTF-8' encoding to copy filtered resources. [INFO] skip non existing resourceDirectory /home/felix/svn/apache/james/* *current/protocols/smtp/src/main/resources [INFO] Copying 3 resources [INFO] [INFO] --- maven-compiler-plugin:2.3.2:compile (default-compile) @ protocols-smtp --- [INFO] Compiling 66 source files to /home/felix/svn/apache/james/ current/protocols/smtp/target/classes [INFO] --** --**- [ERROR] COMPILATION ERROR : [INFO] --** --**- [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/** main/java/org/apache/james/protocols/smtp/core/** ReceivedDataLineFilter.java:[87,74] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/** main/java/org/apache/james/protocols/smtp/core/** ReceivedDataLineFilter.java:[121,58] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/** main/java/org/apache/james/protocols/smtp/core/** ReceivedDataLineFilter.java:[126,69] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/** main/java/org/apache/james/protocols/smtp/core/** ReceivedDataLineFilter.java:[139,69] cannot find symbol symbol : method getBytes(java.nio.charset.Charset) location: class java.lang.String [ERROR] /home/felix/svn/apache/james/current/protocols/smtp/src/** main/java/org/apache/james
[jira] [Created] (MAILETDOCS-7) Rename to mailetdocs-maven-plugin
Rename to mailetdocs-maven-plugin - Key: MAILETDOCS-7 URL: https://issues.apache.org/jira/browse/MAILETDOCS-7 Project: JAMES MailetDocs Maven Plugin Issue Type: Bug Reporter: Felix Knecht Assignee: Felix Knecht From the current maven build log: Artifact Ids of the format maven-___-plugin are reserved for plugins in the Group Id org.apache.maven.plugins. Please change your artifactId to the format ___-maven-plugin.In the future this error will break the build. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: James Website(s) and distribution management
On 11/24/2011 01:42 PM, Ioan Eugen Stan wrote: Pe 23.11.2011 11:14, Felix Knecht a scris: Hi What should be the way of deploy new documentation to the James website and where should this actual deployment goto? The website navigation has been defined as snip / but the in the distributionManagement section of the project pom.xml's (trunk) are different url's defined like e.g. - people.apache.org/www/james.apache.org/server/3/ - people.apache.org/www/james.apache.org/protocols/trunk/ - others are matching the navigation structure Can all be fix in the way that deploying the generated site via mvn site-deploy is going into the actual navigation place? A full update of the whole James website could be (wishfully) done then by $ svn co http://svn.apache.org/repos/asf/james/current current-james $ cd current-james $ mvn clean site-deploy wdot? Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org To answer Felix's question: I don't know, but something should be possible. I discussed the website state with Eric when we met at ApacheCon and agreed that we can do better, but I'm still a noob regarding how things are organized. I think there is room for improvement and we can make the site more user-friendly. One thing that I noticed is that we have no consistency in and the website is kind of crowded. Maybe we can switch to something template based? Do you have already something in mind? When thinking about a redesign of the whole site it should also be discussed if we want to stay the way it is done now having the documentation content in in each project on it's own, create a documentation project and merge all documention into ( both maven generated documentation using xdoc and apt, deploy to p.a.o) or e.g. to switch to the ASF Content Management System (http://www.apache.org/dev/cms.html) Regards Felix -- Ioan Eugen Stan - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
James Website(s) and distribution management
Hi What should be the way of deploy new documentation to the James website and where should this actual deployment goto? The website navigation has been defined as http://james.apache.org/index.html http://james.apache.org/server/index.html http://james.apache.org/hupa/index.html http://james.apache.org/protocols/index.html http://james.apache.org/imap/index.html http://james.apache.org/mailet/index.html http://james.apache.org/mailbox/index.html http://james.apache.org/mime4j/index.html http://james.apache.org/jsieve/index.html http://james.apache.org/jspf/index.html http://james.apache.org/jdkim/index.html http://james.apache.org/mpt/index.html http://james.apache.org/postage/index.html but the in the distributionManagement section of the project pom.xml's (trunk) are different url's defined like e.g. - people.apache.org/www/james.apache.org/server/3/ - people.apache.org/www/james.apache.org/protocols/trunk/ - others are matching the navigation structure Can all be fix in the way that deploying the generated site via mvn site-deploy is going into the actual navigation place? A full update of the whole James website could be (wishfully) done then by $ svn co http://svn.apache.org/repos/asf/james/current current-james $ cd current-james $ mvn clean site-deploy wdot? Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release TLP (pom.xml) Apache James Project 1.8
[X] +1 Please release - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[RESULT] [VOTE] Release TLP (pom.xml) Apache James Project 1.8
Hi the vote passed with: +1 Norman, Stefano, Eric, Robert, Felix +1 (non binding) Ioan Thanks for everyone who voted. I will push the release to maven central and the apache mirrors. Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: EMMA plugin (was svn commit: r1185659 - /james/project/trunk/pom.xml)
Implemented a) in the SNAPSHOT version. Thanks for hints an investigations. Regards Felix On 11/17/2011 05:01 PM, Stefano Bagnara wrote: 2011/11/17 Norman Maurernorman.mau...@googlemail.com: I think a) is the way to go then. I dont think we need to take special care here about the license... I just read this: http://www.apache.org/legal/resolved.html#cobertura So I'm fine with a) , too. Stefano thanks, norman Am Donnerstag, 17. November 2011 schrieb Felix Knechtfe...@otego.com: After all it looks like there are comming up some unexpected problems using the EMMA plugin instead if the cobertura plugin: - Multi module projects are not really supported (or it's simply too old or not really maven 3.x compatible). When running specific goals in a submodule for the maven-jar-plugin e.g. the instrumentation goal must be run in the submodule again and it must be executed after the additional jar-plugin goals. There are more of the same problems - that's not a clean, clear way to go - Report generation seems to be also problematical when it comes to multi-module projects. Because of the mentioned above the report generation may fail and the error says instrumentation has already been done - looks like a chicken-egg problem - The described problems above to not only have impacts on the module itself, but also for projects using a the jar of such a module as dependency (see also Normans mail [1] - thanks for bringing up this problem). Sorry about being too enhousiastic putting the EMMA-plugin into the lately released TLP pom.xml :-/ IMO we should a) either use the cobertura plugin as it is only used for report generation and code review (I'm not aware that it's needed in any James project to build a distribution) b) do code review without knowing about test code coverage c) find another suitable plugin for this (what I haven't up to now) and finally a), b) or c) will need to find the way into the next (soon) release of the TLP pom.xml WDOT? Thanks and regards Felix [1] http://www.mail-archive.com/server-dev@james.apache.org/msg36812.html On 10/20/2011 12:42 PM, Stefano Bagnara wrote: 2011/10/20 Felix Knechtfel...@apache.org: On 10/18/2011 04:42 PM, Stefano Bagnara wrote: 2011/10/18fel...@apache.org: Author: felixk Date: Tue Oct 18 13:52:43 2011 New Revision: 1185659 URL: http://svn.apache.org/viewvc?rev=1185659view=rev Log: Both (emma / cobertura) plugins are for measure of codecoverage of tests. Using only one of the plugins should fullfill the needs. If I've chosen for any reasons the wrong one please let me know. For now I left cobertura plugin. AFAIK cobertura is GPL while emma is CPL. As long as we don't bundle them and don't require them to build our products we should be fine with both, but I guess that if in doubt we should better choose emma as CPL is a category B license (http://www.apache.org/legal/3party.html). I thought the cobertura plugin to be of Apache license: http://mojo.codehaus.org/cobertura-maven-plugin/license.html The plugin is Apache Licensed but the cobertura jar is GPL It is also correctly reported in the dependency report: http://mojo.codehaus.org/cobertura-maven-plugin/dependencies.html But the right place to look for the license is here: http://cobertura.sourceforge.net/license.html The Cobertura ant tasks are licensed under the Apache Software License, Version 1.1. The rest of Cobertura is licensed under the GNU General Public License, Version 2.0. See below for detailed explanations. And as you can see the cobertura license page has a long explanation and concludes with an it all depends on how you interpret the license. AFAICS it's only used to generate reports and it's not required to build the product itself but for code review. I can find other Apache projects using this plugin also - but this doesn't means that it's the way to go for us and I'm not an expert in such things. Can anybody say more about this? What does cobertura gives us more than emma? If there is no reason to use cobertura instead of emma why don't we simply keep emma (you commit message sounds like you randomly chose one) so we don't waste time trying to give answers to the complex licensing stuff? (I believe we are safe to produce reports with a GPL product, but I'm not a lawyer, and I like emma) If, instead, we have good reasons to prefer cobertura then it makes sense to ask Robert (he's the most experienced in our team, wrt licensing) and maybe file an issue to ASF LEGAL jira project. Stefano - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Problems because of emma plugin
Hi Norman On 11/17/2011 08:18 AM, Norman Maurer wrote: Hi there, after the last changes related to the emma-plugin I see strange problems in niosmtp (which uses protocols snapshots in its unit tests). If I don't specify the emma jar as test dependency it fails to init the protocols classes. For me it seems like the protocols jar contains the emma instrumented classes and not the original one. @Felix: Could you have a look ? You can see the effect by comment the emma dependency in niosmtp and try to run mvn clean package. svn trunk of protocols uses as parent the james-project-1-8.SNAPSHOT.pom now. For me the niosmtp builds fine without any dependency of emma - after building before the james-project and the james-protocol dependency from trunk. I committed the changes in protocol also, but it will take it's time until they are via CI as SNAPSHOTs available. Thanks for heads up Felix The niosmtp source can be found here: https://github.com/normanmaurer/niosmtp Thanks, Norman - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Forking tests
Hi all What's the default preferred forkMode for test execution? I suggest always to have more independent tests. Any objections? Thanks Felix [1] http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#forkMode - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Forking tests
On 11/18/2011 08:18 PM, Manuel Carrasco Moñino wrote: I agree, this mode is better when running emma:emma though Emma will be replaced by cobertura anyway. On Fri, Nov 18, 2011 at 3:54 PM, Felix Knechtfe...@otego.com wrote: Hi all What's the default preferred forkMode for test execution? I suggest always to have more independent tests. Any objections? Thanks Felix [1] http://maven.apache.org/**plugins/maven-surefire-plugin/** test-mojo.html#forkModehttp://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#forkMode --**--**- To unsubscribe, e-mail: server-dev-unsubscribe@james.**apache.orgserver-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-help@james.apache.**orgserver-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Forking tests
On 11/18/2011 08:24 PM, Norman Maurer wrote: I habe no real preference... BtW, any plan to star the release for james-project 1.8 soon? If wanted I can start immediately. thanks, norman Am Freitag, 18. November 2011 schrieb Felix Knechtfe...@otego.com: On 11/18/2011 08:18 PM, Manuel Carrasco Mońino wrote: I agree, this mode is better when running emma:emma though Emma will be replaced by cobertura anyway. On Fri, Nov 18, 2011 at 3:54 PM, Felix Knechtfe...@otego.com wrote: Hi all What's the default preferred forkMode for test execution? I suggest always to have more independent tests. Any objections? Thanks Felix [1] http://maven.apache.org/**plugins/maven-surefire-plugin/** test-mojo.html#forkMode http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#forkMode --**--**- To unsubscribe, e-mail: server-dev-unsubscribe@james.**apache.org server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-help@james.apache.**org server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Forking tests
I'll do as soon as I have the gpg signing working again :( On 11/18/2011 09:27 PM, Norman Maurer wrote: Release often release often 2011/11/18, Felix Knechtfe...@otego.com: On 11/18/2011 08:24 PM, Norman Maurer wrote: I habe no real preference... BtW, any plan to star the release for james-project 1.8 soon? If wanted I can start immediately. thanks, norman Am Freitag, 18. November 2011 schrieb Felix Knechtfe...@otego.com: On 11/18/2011 08:18 PM, Manuel Carrasco Mońino wrote: I agree, this mode is better when running emma:emma though Emma will be replaced by cobertura anyway. On Fri, Nov 18, 2011 at 3:54 PM, Felix Knechtfe...@otego.comwrote: Hi all What's the default preferred forkMode for test execution? I suggest always to have more independent tests. Any objections? Thanks Felix [1] http://maven.apache.org/**plugins/maven-surefire-plugin/** test-mojo.html#forkMode http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html#forkMode --**--**- To unsubscribe, e-mail: server-dev-unsubscribe@james.**apache.org server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-help@james.apache.**org server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[VOTE] Release TLP (pom.xml) Apache James Project 1.8
Hi A list of main changes/fixes: - Replace the emma plugin by the cobertura plugin for review code coverage. The emma plugin causes problems when it comes to multi-module projects. Please cast you vote for release TLP (pom.xml) Apache James Project 1.8 Release for review: https://repository.apache.org/content/repositories/orgapachejames-221/ [ ] +1 Please release [ ] +0 No time to review [ ] -1 Something wrong which blocks the release. Thanks and regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Problems because of emma plugin
Hi Norman I'll find some time this afternoon. I had also strange effects in other modules - when a submodule calls e.g. any goal of the jar-plugin explicitly I needed to run the instrumentation of the emma plugin goal as well explicitly, even when already run from the parent pom. While the build seems to work this way I think to become problems when generating the reports because it tells me that emma instrumentation is already done and can't be done a second time ... I'm not the emma specialist but I'll try to find a solution for this. If I can't find one I wonder if we should either investigate more time in finding another (than emma and cobertura) code coverage plugin, don't use any code coverage plugin or investigate more time in the license problematics of cobertura. Regards Felix On 11/17/2011 08:18 AM, Norman Maurer wrote: Hi there, after the last changes related to the emma-plugin I see strange problems in niosmtp (which uses protocols snapshots in its unit tests). If I don't specify the emma jar as test dependency it fails to init the protocols classes. For me it seems like the protocols jar contains the emma instrumented classes and not the original one. @Felix: Could you have a look ? You can see the effect by comment the emma dependency in niosmtp and try to run mvn clean package. The niosmtp source can be found here: https://github.com/normanmaurer/niosmtp Thanks, Norman - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
EMMA plugin (was svn commit: r1185659 - /james/project/trunk/pom.xml)
After all it looks like there are comming up some unexpected problems using the EMMA plugin instead if the cobertura plugin: - Multi module projects are not really supported (or it's simply too old or not really maven 3.x compatible). When running specific goals in a submodule for the maven-jar-plugin e.g. the instrumentation goal must be run in the submodule again and it must be executed after the additional jar-plugin goals. There are more of the same problems - that's not a clean, clear way to go - Report generation seems to be also problematical when it comes to multi-module projects. Because of the mentioned above the report generation may fail and the error says instrumentation has already been done - looks like a chicken-egg problem - The described problems above to not only have impacts on the module itself, but also for projects using a the jar of such a module as dependency (see also Normans mail [1] - thanks for bringing up this problem). Sorry about being too enhousiastic putting the EMMA-plugin into the lately released TLP pom.xml :-/ IMO we should a) either use the cobertura plugin as it is only used for report generation and code review (I'm not aware that it's needed in any James project to build a distribution) b) do code review without knowing about test code coverage c) find another suitable plugin for this (what I haven't up to now) and finally a), b) or c) will need to find the way into the next (soon) release of the TLP pom.xml WDOT? Thanks and regards Felix [1] http://www.mail-archive.com/server-dev@james.apache.org/msg36812.html On 10/20/2011 12:42 PM, Stefano Bagnara wrote: 2011/10/20 Felix Knechtfel...@apache.org: On 10/18/2011 04:42 PM, Stefano Bagnara wrote: 2011/10/18fel...@apache.org: Author: felixk Date: Tue Oct 18 13:52:43 2011 New Revision: 1185659 URL: http://svn.apache.org/viewvc?rev=1185659view=rev Log: Both (emma / cobertura) plugins are for measure of codecoverage of tests. Using only one of the plugins should fullfill the needs. If I've chosen for any reasons the wrong one please let me know. For now I left cobertura plugin. AFAIK cobertura is GPL while emma is CPL. As long as we don't bundle them and don't require them to build our products we should be fine with both, but I guess that if in doubt we should better choose emma as CPL is a category B license (http://www.apache.org/legal/3party.html). I thought the cobertura plugin to be of Apache license: http://mojo.codehaus.org/cobertura-maven-plugin/license.html The plugin is Apache Licensed but the cobertura jar is GPL It is also correctly reported in the dependency report: http://mojo.codehaus.org/cobertura-maven-plugin/dependencies.html But the right place to look for the license is here: http://cobertura.sourceforge.net/license.html The Cobertura ant tasks are licensed under the Apache Software License, Version 1.1. The rest of Cobertura is licensed under the GNU General Public License, Version 2.0. See below for detailed explanations. And as you can see the cobertura license page has a long explanation and concludes with an it all depends on how you interpret the license. AFAICS it's only used to generate reports and it's not required to build the product itself but for code review. I can find other Apache projects using this plugin also - but this doesn't means that it's the way to go for us and I'm not an expert in such things. Can anybody say more about this? What does cobertura gives us more than emma? If there is no reason to use cobertura instead of emma why don't we simply keep emma (you commit message sounds like you randomly chose one) so we don't waste time trying to give answers to the complex licensing stuff? (I believe we are safe to produce reports with a GPL product, but I'm not a lawyer, and I like emma) If, instead, we have good reasons to prefer cobertura then it makes sense to ask Robert (he's the most experienced in our team, wrt licensing) and maybe file an issue to ASF LEGAL jira project. Stefano - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release TLP (pom.xml) Apache James Project 1.7
Almost forgot myself [X] +1 Please release - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[RESULT] [VOTE] Release TLP (pom.xml) Apache James Project 1.7
Hi the vote passed with: +1 Norman, Stefano, Eric, Manolo, Felix +1 (non binding) Ioan Thanks for everyone who voted. I will push the release to maven central and the apache mirrors. Regards Felix On 11/01/2011 03:56 PM, Felix Knecht wrote: Hi A list of main changes/fixes: - Moving legacy documentation to branches tree - Merge james-parent.pom and james-project.pom into james-project.pom - Merge pluginManagement sections of all James projects into TLP pom.xml - Update plugins to latest version - Replace weare.xml by merging developers and contributors into pom.xml and let the report be generated by the project-info-report plugin - Simplify the switch mechanism for site / technical-site generation - Remove inherited definitions - Replace cobertura-plugin with emma-plugin - Use latest apache pom as parent - Set target JDK 1.6 as default - Add wagon-ssh-external extension to make site-deploy via ssh (scp) using ssh-agents working Please cast you vote for release TLP (pom.xml) Apache James Project 1.7 Release for review: https://repository.apache.org/content/repositories/orgapachejames-135/ [ ] +1 Please release [ ] +0 No time to review [ ] -1 Something wrong which blocks the release. Thanks and regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1335) Merge project/pom.xml and project/project/pom.xml
[ https://issues.apache.org/jira/browse/JAMES-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Knecht closed JAMES-1335. --- Merge project/pom.xml and project/project/pom.xml - Key: JAMES-1335 URL: https://issues.apache.org/jira/browse/JAMES-1335 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor ATM all modules are referencing james-project as parent pom whereas james-project references james-parent as parent pom. Merging current james-project.pom into current james-parent.pom, renaming current james-parent.pom to james-project.pom, moving the project site documentation from project/project to project is probably the easiest way and will (AFAICS) not need any changes in all the other James modules. We can still after this refactoring decide a) What shall happen with the legacy code of server 2.x (project/project/server) which is still in the tree but not anymore referenced as module by any pom.xml b) If dependencyManagement / pluginManagement shall become part of the TLP pom or not See also discussion on http://www.mail-archive.com/server-dev@james.apache.org/msg36344.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-1335) Merge project/pom.xml and project/project/pom.xml
[ https://issues.apache.org/jira/browse/JAMES-1335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Knecht resolved JAMES-1335. - Resolution: Fixed Merge project/pom.xml and project/project/pom.xml - Key: JAMES-1335 URL: https://issues.apache.org/jira/browse/JAMES-1335 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor ATM all modules are referencing james-project as parent pom whereas james-project references james-parent as parent pom. Merging current james-project.pom into current james-parent.pom, renaming current james-parent.pom to james-project.pom, moving the project site documentation from project/project to project is probably the easiest way and will (AFAICS) not need any changes in all the other James modules. We can still after this refactoring decide a) What shall happen with the legacy code of server 2.x (project/project/server) which is still in the tree but not anymore referenced as module by any pom.xml b) If dependencyManagement / pluginManagement shall become part of the TLP pom or not See also discussion on http://www.mail-archive.com/server-dev@james.apache.org/msg36344.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[VOTE] Release TLP (pom.xml) Apache James Project 1.7
Hi A list of main changes/fixes: - Moving legacy documentation to branches tree - Merge james-parent.pom and james-project.pom into james-project.pom - Merge pluginManagement sections of all James projects into TLP pom.xml - Update plugins to latest version - Replace weare.xml by merging developers and contributors into pom.xml and let the report be generated by the project-info-report plugin - Simplify the switch mechanism for site / technical-site generation - Remove inherited definitions - Replace cobertura-plugin with emma-plugin - Use latest apache pom as parent - Set target JDK 1.6 as default - Add wagon-ssh-external extension to make site-deploy via ssh (scp) using ssh-agents working Please cast you vote for release TLP (pom.xml) Apache James Project 1.7 Release for review: https://repository.apache.org/content/repositories/orgapachejames-135/ [ ] +1 Please release [ ] +0 No time to review [ ] -1 Something wrong which blocks the release. Thanks and regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: NoSQL backend for James
On 10/31/2011 04:17 PM, Manuel Carrasco Moñino wrote: Hello Pepijn On Fri, Oct 28, 2011 at 3:12 PM, Pepijn de Vospepijnde...@yahoo.com wrote: Hi, I decided to stop working on the CouchDB backend. I'm sorry. Bad news, it was a good idea James supporting couchdb There is something to be said for persisting and finishing, but I do not enjoy writing it and I don't need it. I'm going to focus instead on what I set out to do, write a webmail application. I will persist in that. I learned that what I wanted to do is not a good design at all. I thought it would be easy to write my webmail application on top of CouchDB and have James fish from the same pool. This would create a tight coupling between my app and James, and leaves me at the mercy of future changes to the API. Instead, I'll just write my app on top of IMAP, and in fact, I couldn't care less how the mail server stores my email. Yeah, this is the approach used by HUPA (the webmail of James), take a look to its architecture in this presentation: http://www.slideshare.net/dodotis/apache-jameshupa-gwt Why not adding the presentation or its link to the hupa documentation? We are lacking good documentation. Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Apache James Protocols 1.6-beta2 (second take)
[X] +1 Yes do it now! Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: svn commit: r1188732 - in /james/protocols/trunk: api/pom.xml impl/pom.xml lmtp/pom.xml pom.xml smtp/pom.xml
On 10/25/2011 07:11 PM, Norman Maurer wrote: Yeah I would love to release protocols-1.6-beta2 asap ;) Just go ahead, IMO this isn't a NoGo (it's a beta). Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Protocol 1.6-beta2
[X] +1 Yes please release Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: svn commit: r1188732 - in /james/protocols/trunk: api/pom.xml impl/pom.xml lmtp/pom.xml pom.xml smtp/pom.xml
Heads up Please be aware the both site.xml (src/site | src/reporting-site) still point to maven-skin-1.7-SNAPSHOT. Any try to build the site later after the release may fail because the skin dependency can't be found anymore. We need either to wait until TLP pom.xml is released or use the release skin dependency james-skin-1.7. This is also valid for other James projects then protocols Regards Felix On 10/25/2011 05:45 PM, nor...@apache.org wrote: Author: norman Date: Tue Oct 25 15:45:01 2011 New Revision: 1188732 URL: http://svn.apache.org/viewvc?rev=1188732view=rev Log: [maven-release-plugin] prepare release protocols-1.6-beta2 Modified: james/protocols/trunk/api/pom.xml james/protocols/trunk/impl/pom.xml james/protocols/trunk/lmtp/pom.xml james/protocols/trunk/pom.xml james/protocols/trunk/smtp/pom.xml Modified: james/protocols/trunk/api/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/api/pom.xml?rev=1188732r1=1188731r2=1188732view=diff == --- james/protocols/trunk/api/pom.xml (original) +++ james/protocols/trunk/api/pom.xml Tue Oct 25 15:45:01 2011 @@ -17,16 +17,13 @@ specific language governing permissions and limitations under the License. -- -project -xmlns=http://maven.apache.org/POM/4.0.0; -xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; -xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; +project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion parent artifactIdprotocols/artifactId groupIdorg.apache.james/groupId -version1.6-beta2-SNAPSHOT/version +version1.6-beta2/version relativePath../pom.xml/relativePath /parent Modified: james/protocols/trunk/impl/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/impl/pom.xml?rev=1188732r1=1188731r2=1188732view=diff == --- james/protocols/trunk/impl/pom.xml (original) +++ james/protocols/trunk/impl/pom.xml Tue Oct 25 15:45:01 2011 @@ -17,16 +17,13 @@ specific language governing permissions and limitations under the License. -- -project -xmlns=http://maven.apache.org/POM/4.0.0; -xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; -xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; +project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion parent artifactIdprotocols/artifactId groupIdorg.apache.james/groupId -version1.6-beta2-SNAPSHOT/version +version1.6-beta2/version relativePath../pom.xml/relativePath /parent Modified: james/protocols/trunk/lmtp/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/lmtp/pom.xml?rev=1188732r1=1188731r2=1188732view=diff == --- james/protocols/trunk/lmtp/pom.xml (original) +++ james/protocols/trunk/lmtp/pom.xml Tue Oct 25 15:45:01 2011 @@ -17,16 +17,13 @@ specific language governing permissions and limitations under the License. -- -project -xmlns=http://maven.apache.org/POM/4.0.0; -xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; -xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; +project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion parent artifactIdprotocols/artifactId groupIdorg.apache.james/groupId -version1.6-beta2-SNAPSHOT/version +version1.6-beta2/version relativePath../pom.xml/relativePath /parent Modified: james/protocols/trunk/pom.xml URL: http://svn.apache.org/viewvc/james/protocols/trunk/pom.xml?rev=1188732r1=1188731r2=1188732view=diff == --- james/protocols/trunk/pom.xml (original) +++ james/protocols/trunk/pom.xml Tue Oct 25 15:45:01 2011 @@ -17,22 +17,19 @@ specific language governing permissions and limitations under the License. -- -project -xmlns=http://maven.apache.org/POM/4.0.0; -xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; -xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; +project xmlns=http://maven.apache.org/POM/4.0.0;
Re: svn commit: r1188732 - in /james/protocols/trunk: api/pom.xml impl/pom.xml lmtp/pom.xml pom.xml smtp/pom.xml
On 10/25/2011 06:06 PM, Norman Maurer wrote: Hi there, when do you expect we are ready for 1.7 ? Many things have been done, some others may still be discussed [1]. I tried to push for discussion before going to release it. But of course following release early release often we can also go for a release if you favourit. [1] http://www.mail-archive.com/server-dev@james.apache.org/msg36665.html Regards Felix Bye, Norman - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Need some help - Re: svn commit: r1189020 - /james/project/trunk/pom.xml
Hi I need some help to update and review the developers section. I updated the PMC members using data from http://people.apache.org/committer-index.html. I hope it's up to date. I also can't find any 'Emeritus' committers. Do thye not exist and all committers are still active? What is about committers listed at http://people.apache.org/committers-by-project.html#james but not in the pom.xml developers section? Thanks and regards Felix On 10/26/2011 06:14 AM, fel...@apache.org wrote: Author: felixk Date: Wed Oct 26 04:14:32 2011 New Revision: 1189020 URL: http://svn.apache.org/viewvc?rev=1189020view=rev Log: Update missing id's and role's. Id and PMC members added using data from http://people.apache.org/committer-index.html Modified: james/project/trunk/pom.xml Modified: james/project/trunk/pom.xml URL: http://svn.apache.org/viewvc/james/project/trunk/pom.xml?rev=1189020r1=1189019r2=1189020view=diff == --- james/project/trunk/pom.xml (original) +++ james/project/trunk/pom.xml Wed Oct 26 04:14:32 2011 @@ -59,6 +59,7 @@ timezone2/timezone roles roleDeveloper/role +rolePMC Member/role /roles /developer developer @@ -102,6 +103,7 @@ timezone / roles roleDeveloper/role +rolePMC Member/role /roles /developer developer @@ -111,6 +113,7 @@ timezone / roles roleDeveloper/role +rolePMC Member/role /roles /developer developer @@ -120,6 +123,7 @@ timezone / roles roleDeveloper/role +rolePMC Member/role /roles /developer developer @@ -129,6 +133,7 @@ timezone / roles roleDeveloper/role +rolePMC Member/role /roles organizationStudent Loans Company ltd/organization organizationUrlhttp://www.slc.co.uk/organizationUrl @@ -148,6 +153,7 @@ /roles /developer developer +idhbedi/id nameHarmeet Bedi/name emailharmeet at kodemuse.com/email roles @@ -155,6 +161,7 @@ /roles /developer developer +idjasonw/id nameJason Webb/name emailjw at inovem.com/email roles @@ -168,6 +175,7 @@ timezone / roles roleDeveloper/role +rolePMC Member/role /roles /developer developer @@ -177,6 +185,7 @@ timezone / roles roleDeveloper/role +rolePMC Member/role /roles /developer developer @@ -184,6 +193,10 @@ nameNiklas Therning/name emailniklas(at)apache(dot)org/email organizationTrillian AB/organization +roles +roleDeveloper/role +rolePMC Member/role +/roles /developer developer idjcheng/id @@ -220,6 +233,7 @@ timezone / roles roleDeveloper/role +rolePMC Member/role /roles /developer developer - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
DOAP file
Hi IMO the DOAP file [1] isn't up to date, e.g. IMAP isn't mentioned at all in the description. Will the DOAP file be maintained manually in future or shall it be generated via maven-doap-plugin [2]? If the latter then we should add it to TLP pom before releasing. Thanks Felix [1] http://projects.apache.org/projects/james.html [2] http://maven.apache.org/plugins/maven-doap-plugin/ - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: [VOTE] Release Apache James Skin 1.7
[X] +1 Please release Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Refactoring TLP pom
Following changes have been made up to now: - Refactored maven-skin to single project james-skin (and released) - Merged pluginManagement section from other projects including configuration - Simplified site/reporting switch - Merged weare.xml document into pom.xml - Updated to latest plugin versions Pending changes: - verify, remove or add (technical) reports (doap, dependency:analyze-report, ...) - Use APIViz for javadocs (I see a problem until it APIViz works also for poms using packagingpom/packaging - Shall the dependencyManagement go into this pom? (Not my favorit) - ? What should be done before we can think about releasing? Thanks and regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Refactoring TLP pom
On 10/21/2011 06:52 PM, Felix Knecht wrote: Following changes have been made up to now: - Refactored maven-skin to single project james-skin (and released) - Merged pluginManagement section from other projects including configuration - Simplified site/reporting switch - Merged weare.xml document into pom.xml - Updated to latest plugin versions Pending changes: Better changes in question: - verify, remove or add (technical) reports (doap, dependency:analyze-report, ...) - Use APIViz for javadocs (I see a problem until it APIViz works also for poms using packagingpom/packaging - Shall the dependencyManagement go into this pom? (Not my favorit) - ? What should be done before we can think about releasing? Thanks and regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: svn commit: r1185997 - /james/project/trunk/pom.xml
On 10/19/2011 09:04 AM, Norman Maurer wrote:
We still have some project which are jdk 1.5... Do you plan to make
1.6 the default and override this on the others ?
Thanks for head up.
I thought having read some time ago that we will prerequisit jdk 1.6,
but the one (jdk1.5) or the other (jdk1.6) needs to be overwritten.
Having jdk1.6 as default will problably motivate more to move all
projects to 1.6. If you favour to have 1.5 as default jdk it can be
switched easily as nothing is released yet.
Regards
Felix
Thanks,
Norman
2011/10/19fel...@apache.org:
Author: felixk
Date: Wed Oct 19 07:01:27 2011
New Revision: 1185997
URL: http://svn.apache.org/viewvc?rev=1185997view=rev
Log:
- Target JDK is 1-6
- No need to generate test-javadocs for site generation, only javadocs are
needed to make them available from the site
Modified:
james/project/trunk/pom.xml
Modified: james/project/trunk/pom.xml
URL:
http://svn.apache.org/viewvc/james/project/trunk/pom.xml?rev=1185997r1=1185996r2=1185997view=diff
==
--- james/project/trunk/pom.xml (original)
+++ james/project/trunk/pom.xml Wed Oct 19 07:01:27 2011
@@ -314,7 +314,7 @@
properties
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
-target.jdk1.5/target.jdk
+target.jdk1.6/target.jdk
james-skin.version1.7/james-skin.version
maven-site-plugin.siteDirectory${basedir}/src/site/maven-site-plugin.siteDirectory
maven-site-plugin.generateReportsfalse/maven-site-plugin.generateReports
@@ -753,7 +753,6 @@
phasepre-site/phase
goals
goalaggregate/goal
-goaltest-aggregate/goal
/goals
configuration
minmemory256m/minmemory
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1339) Reformat all pom.xml
Reformat all pom.xml Key: JAMES-1339 URL: https://issues.apache.org/jira/browse/JAMES-1339 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor I suggest reformat all poms, ordering according to http://maven.apache.org/ref/3.0.3/maven-model/maven.html, indent 4 spaces, split multiple attributes each on a new line if nobody objects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Commented] (JAMES-1339) Reformat all pom.xml
[ https://issues.apache.org/jira/browse/JAMES-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13130457#comment-13130457 ] Felix Knecht commented on JAMES-1339: - Add relativePath to parent Reformat all pom.xml Key: JAMES-1339 URL: https://issues.apache.org/jira/browse/JAMES-1339 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor I suggest reformat all poms, ordering according to http://maven.apache.org/ref/3.0.3/maven-model/maven.html, indent 4 spaces, split multiple attributes each on a new line if nobody objects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-1339) Reformat all pom.xml
[ https://issues.apache.org/jira/browse/JAMES-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Knecht resolved JAMES-1339. - Resolution: Fixed Fix Version/s: Trunk All module poms reformatted Reformat all pom.xml Key: JAMES-1339 URL: https://issues.apache.org/jira/browse/JAMES-1339 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor Fix For: Trunk I suggest reformat all poms, ordering according to http://maven.apache.org/ref/3.0.3/maven-model/maven.html, indent 4 spaces, split multiple attributes each on a new line if nobody objects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1339) Reformat all pom.xml
[ https://issues.apache.org/jira/browse/JAMES-1339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Knecht closed JAMES-1339. --- Reformat all pom.xml Key: JAMES-1339 URL: https://issues.apache.org/jira/browse/JAMES-1339 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor Fix For: Trunk I suggest reformat all poms, ordering according to http://maven.apache.org/ref/3.0.3/maven-model/maven.html, indent 4 spaces, split multiple attributes each on a new line if nobody objects. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1336) Missing logos for Hupa, Protocols, Mailbox
Missing logos for Hupa, Protocols, Mailbox -- Key: JAMES-1336 URL: https://issues.apache.org/jira/browse/JAMES-1336 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Felix Knecht Priority: Minor Following James modules do not have their own logo - Hupa - Protocols - Mailbox When created they should go into https://svn.apache.org/repos/asf/james/skin/trunk/src/main/resources/images/logos -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1337) Move pluginManagement to TLP pom
Move pluginManagement to TLP pom Key: JAMES-1337 URL: https://issues.apache.org/jira/browse/JAMES-1337 Project: JAMES Server Issue Type: Task Components: Build System Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor Use the TLP poms pluginManagement section to define plugin versions and common configurations -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-1338) Avoid website overwriting accidently when using -Psite-reports when deploying the site
[ https://issues.apache.org/jira/browse/JAMES-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Knecht resolved JAMES-1338. - Resolution: Fixed Avoid website overwriting accidently when using -Psite-reports when deploying the site -- Key: JAMES-1338 URL: https://issues.apache.org/jira/browse/JAMES-1338 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor Fix For: Trunk -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1338) Avoid website overwriting accidently when using -Psite-reports when deploying the site
[ https://issues.apache.org/jira/browse/JAMES-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Knecht closed JAMES-1338. --- Avoid website overwriting accidently when using -Psite-reports when deploying the site -- Key: JAMES-1338 URL: https://issues.apache.org/jira/browse/JAMES-1338 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor Fix For: Trunk -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1338) Avoid website overwriting accidently when using -Psite-reports when deploying the site
Avoid website overwriting accidently when using -Psite-reports when deploying the site -- Key: JAMES-1338 URL: https://issues.apache.org/jira/browse/JAMES-1338 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor Fix For: Trunk -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1337) Move pluginManagement to TLP pom
[ https://issues.apache.org/jira/browse/JAMES-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Knecht closed JAMES-1337. --- Move pluginManagement to TLP pom Key: JAMES-1337 URL: https://issues.apache.org/jira/browse/JAMES-1337 Project: JAMES Server Issue Type: Task Components: Build System Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor Fix For: Trunk Use the TLP poms pluginManagement section to define plugin versions and common configurations -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-1337) Move pluginManagement to TLP pom
[ https://issues.apache.org/jira/browse/JAMES-1337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Knecht resolved JAMES-1337. - Resolution: Fixed Fix Version/s: Trunk Merged the found plugin definitions from other James modules, hopefully all ... Maybe some special configurations are missing, but they can be defined/overriden in the modules pom Move pluginManagement to TLP pom Key: JAMES-1337 URL: https://issues.apache.org/jira/browse/JAMES-1337 Project: JAMES Server Issue Type: Task Components: Build System Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor Fix For: Trunk Use the TLP poms pluginManagement section to define plugin versions and common configurations -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Closed] (JAMES-1334) New module for james maven skin
[ https://issues.apache.org/jira/browse/JAMES-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Knecht closed JAMES-1334. --- New module for james maven skin --- Key: JAMES-1334 URL: https://issues.apache.org/jira/browse/JAMES-1334 Project: JAMES Server Issue Type: Task Components: Documentation Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Fix For: Trunk Hi all I propose to put the maven-skin into an own module, e.g. https://svn.apache.org/repos/asf/james/skin/[trunk|tags|branches]. This would make the ...james/project/... tree clea[n|r]er. Furthermore I don't see the need to reference a james pom as parent - there's not much benefit of doing so. We can reference directly to apache as parent. This will also avoid to run into cycling dependencies when including the skin in any James project and releasing skin may become less complicated as it doesn't depends on any james(-SNAPSHOT ?) poms and doesn't need to be released when releasing TLP pom. I'd also like to rename it from maven-skin to either - james-skin or - apache-james-skin - other suggestions to make it more obvious it's a skin for the James project. My preferred one is james-skin because - apache will be in the groupId - Many other projects [1] prefix the artifactId only using the project name (e.g. lucene, openjpa, hadoop, camel, ...) Sample can be seen @ [2]. I wonder if we should start with version 1.0 again (new artifact name), stay with 1.7 (which is still SNAPSHOT) or switch to 2.0. Feedback welcome. If nobody disagrees I'll start creating the module next Sunday or Monday (16/17th October). Thanks and regards Felix [1] http://repo1.maven.org/maven2/org/apache/ [2] https://svn.apache.org/repos/asf/james/trunk/sandbox/felixk/sample-project-layout/skin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Resolved] (JAMES-1334) New module for james maven skin
[ https://issues.apache.org/jira/browse/JAMES-1334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Felix Knecht resolved JAMES-1334. - Resolution: Fixed Fix Version/s: Trunk - Moved to its own module - Renamed artifact to james-skin - Parent pom references apache pom - version kept 1.7-SNAPSHOT New module for james maven skin --- Key: JAMES-1334 URL: https://issues.apache.org/jira/browse/JAMES-1334 Project: JAMES Server Issue Type: Task Components: Documentation Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Fix For: Trunk Hi all I propose to put the maven-skin into an own module, e.g. https://svn.apache.org/repos/asf/james/skin/[trunk|tags|branches]. This would make the ...james/project/... tree clea[n|r]er. Furthermore I don't see the need to reference a james pom as parent - there's not much benefit of doing so. We can reference directly to apache as parent. This will also avoid to run into cycling dependencies when including the skin in any James project and releasing skin may become less complicated as it doesn't depends on any james(-SNAPSHOT ?) poms and doesn't need to be released when releasing TLP pom. I'd also like to rename it from maven-skin to either - james-skin or - apache-james-skin - other suggestions to make it more obvious it's a skin for the James project. My preferred one is james-skin because - apache will be in the groupId - Many other projects [1] prefix the artifactId only using the project name (e.g. lucene, openjpa, hadoop, camel, ...) Sample can be seen @ [2]. I wonder if we should start with version 1.0 again (new artifact name), stay with 1.7 (which is still SNAPSHOT) or switch to 2.0. Feedback welcome. If nobody disagrees I'll start creating the module next Sunday or Monday (16/17th October). Thanks and regards Felix [1] http://repo1.maven.org/maven2/org/apache/ [2] https://svn.apache.org/repos/asf/james/trunk/sandbox/felixk/sample-project-layout/skin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1335) Merge project/pom.xml and project/project/pom.xml
Merge project/pom.xml and project/project/pom.xml - Key: JAMES-1335 URL: https://issues.apache.org/jira/browse/JAMES-1335 Project: JAMES Server Issue Type: Task Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Priority: Minor ATM all modules are referencing james-project as parent pom whereas james-project references james-parent as parent pom. Merging current james-project.pom into current james-parent.pom, renaming current james-parent.pom to james-project.pom, moving the project site documentation from project/project to project is probably the easiest way and will (AFAICS) not need any changes in all the other James modules. We can still after this refactoring decide a) What shall happen with the legacy code of server 2.x (project/project/server) which is still in the tree but not anymore referenced as module by any pom.xml b) If dependencyManagement / pluginManagement shall become part of the TLP pom or not See also discussion on http://www.mail-archive.com/server-dev@james.apache.org/msg36344.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
New module for james maven skin
Hi all I propose to put the maven-skin into an own module, e.g. https://svn.apache.org/repos/asf/james/skin/[trunk|tags|branches]. This would make the ...james/project/... tree clea[n|r]er. Furthermore I don't see the need to reference a james pom as parent - there's not much benefit of doing so. We can reference directly to apache as parent. This will also avoid to run into cycling dependencies when including the skin in any James project and releasing skin may become less complicated as it doesn't depends on any james(-SNAPSHOT ?) poms and doesn't need to be released when releasing TLP pom. I'd also like to rename it from maven-skin to either - james-skin or - apache-james-skin - other suggestions to make it more obvious it's a skin for the James project. My preferred one is james-skin because - apache will be in the groupId - Many other projects [1] prefix the artifactId only using the project name (e.g. lucene, openjpa, hadoop, camel, ...) Sample can be seen @ [2]. I wonder if we should start with version 1.0 again (new artifact name), stay with 1.7 (which is still SNAPSHOT) or switch to 2.0. Feedback welcome. If nobody disagrees I'll start creating the module next Sunday or Monday (16/17th October). Thanks and regards Felix [1] http://repo1.maven.org/maven2/org/apache/ [2] https://svn.apache.org/repos/asf/james/trunk/sandbox/felixk/sample-project-layout/skin - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: New module for james maven skin
On 10/13/2011 12:15 PM, Felix Knecht wrote: Hi all I propose to put the maven-skin into an own module, e.g. https://svn.apache.org/repos/asf/james/skin/[trunk|tags|branches]. This would make the ...james/project/... tree clea[n|r]er. Furthermore I don't see the need to reference a james pom as parent - there's not much benefit of doing so. We can reference directly to apache as parent. This will also avoid to run into cycling dependencies when including the skin in any James project and releasing skin may become less complicated as it doesn't depends on any james(-SNAPSHOT ?) poms and doesn't need to be released when releasing TLP pom. I'd also like to rename it from maven-skin to either - james-skin or - apache-james-skin - other suggestions to make it more obvious it's a skin for the James project. My preferred one is james-skin because - apache will be in the groupId - Many other projects [1] prefix the artifactId only using the project name (e.g. lucene, openjpa, hadoop, camel, ...) Sample can be seen @ [2]. I wonder if we should start with version 1.0 again (new artifact name), stay with 1.7 (which is still SNAPSHOT) or switch to 2.0. Feedback welcome. If nobody disagrees I'll start creating the module next Sunday or Monday (16/17th October). See also https://issues.apache.org/jira/browse/JAMES-1334 Thanks and regards Felix [1] http://repo1.maven.org/maven2/org/apache/ [2] https://svn.apache.org/repos/asf/james/trunk/sandbox/felixk/sample-project-layout/skin - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-1334) New module for james maven skin
New module for james maven skin --- Key: JAMES-1334 URL: https://issues.apache.org/jira/browse/JAMES-1334 Project: JAMES Server Issue Type: Task Components: Documentation Affects Versions: Trunk Reporter: Felix Knecht Assignee: Felix Knecht Hi all I propose to put the maven-skin into an own module, e.g. https://svn.apache.org/repos/asf/james/skin/[trunk|tags|branches]. This would make the ...james/project/... tree clea[n|r]er. Furthermore I don't see the need to reference a james pom as parent - there's not much benefit of doing so. We can reference directly to apache as parent. This will also avoid to run into cycling dependencies when including the skin in any James project and releasing skin may become less complicated as it doesn't depends on any james(-SNAPSHOT ?) poms and doesn't need to be released when releasing TLP pom. I'd also like to rename it from maven-skin to either - james-skin or - apache-james-skin - other suggestions to make it more obvious it's a skin for the James project. My preferred one is james-skin because - apache will be in the groupId - Many other projects [1] prefix the artifactId only using the project name (e.g. lucene, openjpa, hadoop, camel, ...) Sample can be seen @ [2]. I wonder if we should start with version 1.0 again (new artifact name), stay with 1.7 (which is still SNAPSHOT) or switch to 2.0. Feedback welcome. If nobody disagrees I'll start creating the module next Sunday or Monday (16/17th October). Thanks and regards Felix [1] http://repo1.maven.org/maven2/org/apache/ [2] https://svn.apache.org/repos/asf/james/trunk/sandbox/felixk/sample-project-layout/skin -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: svn commit: r1182282 - in /james/mailbox/trunk/hbase/src/test: java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java resources/hdfs-default.xml
I can finally build mailbox with all test. But it seems, that a
configuration problem exists:
Tests for module hbase and spring will only succeed when the property
dfs.datanode.data.dir.perm is set corresponding to the umask [1] set
on the local machine. Whereas fedora seems to set it to 0002 other
distributions do have 0022. This makes the difference. To set the
property correct it needs to correspond:
umask=0002 - dfs.datanode.data.dir.perm=775
umask=0022 - dfs.datanode.data.dir.perm=755
The property is ATM set in test/resources/hdfs-default.xml file.
If somebody knows how to fix it better or if it's better to change the
committed configuration from dfs.datanode.data.dir.perm=775 to
dfs.datanode.data.dir.perm=755 please do so.
Thanks and regards
Felix
[1] http://en.wikipedia.org/wiki/Umask
On 10/12/2011 11:28 AM, fel...@apache.org wrote:
Author: felixk
Date: Wed Oct 12 09:28:10 2011
New Revision: 1182282
URL: http://svn.apache.org/viewvc?rev=1182282view=rev
Log:
Move hard coded configurations into configuration file. The configuration file
originally is taken from hadoop-core-0.20-append-r1057313.jar
Added:
james/mailbox/trunk/hbase/src/test/resources/hdfs-default.xml (with
props)
Modified:
james/mailbox/trunk/hbase/src/test/java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java
Modified:
james/mailbox/trunk/hbase/src/test/java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java
URL:
http://svn.apache.org/viewvc/james/mailbox/trunk/hbase/src/test/java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java?rev=1182282r1=1182281r2=1182282view=diff
==
---
james/mailbox/trunk/hbase/src/test/java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java
(original)
+++
james/mailbox/trunk/hbase/src/test/java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java
Wed Oct 12 09:28:10 2011
@@ -50,16 +50,6 @@ public class HBaseClusterSingleton {
public HBaseClusterSingleton(boolean useMiniCluster) throws Exception {
if (useMiniCluster) {
HBaseTestingUtility htu = new HBaseTestingUtility();
-htu.getConfiguration().setBoolean(dfs.support.append, true);
-
-// TODO
-// I got wrong filepermissions on the created files. This fixes it
for me.
-// Maybe this depends on the umask settings on the local linux box?
-// IMO following line should solve this, but it doesn't ..
-// (see
http://hadoop.apache.org/hdfs/docs/r0.21.0/hdfs-default.html)
-//
-// htu.getConfiguration().set(dfs.permissions.enabled, false);
-htu.getConfiguration().set(dfs.datanode.data.dir.perm, 775);
try {
hbaseCluster = htu.startMiniCluster();
conf = hbaseCluster.getConfiguration();
Added: james/mailbox/trunk/hbase/src/test/resources/hdfs-default.xml
URL:
http://svn.apache.org/viewvc/james/mailbox/trunk/hbase/src/test/resources/hdfs-default.xml?rev=1182282view=auto
==
--- james/mailbox/trunk/hbase/src/test/resources/hdfs-default.xml (added)
+++ james/mailbox/trunk/hbase/src/test/resources/hdfs-default.xml Wed Oct 12
09:28:10 2011
@@ -0,0 +1,370 @@
+?xml version=1.0?
+?xml-stylesheet type=text/xsl href=configuration.xsl?
+
+!-- Do not modify this file directly. Instead, copy entries that you --
+!-- wish to modify from this file into hdfs-site.xml and change them --
+!-- there. If hdfs-site.xml does not already exist, create it. --
+
+configuration
+
+property
+namedfs.namenode.logging.level/name
+valueinfo/value
+descriptionThe logging level for dfs namenode. Other values are dir(trac
+e namespace mutations), block(trace block under/over replications and block
+creations/deletions), or all./description
+/property
+
+property
+namedfs.secondary.http.address/name
+value0.0.0.0:50090/value
+description
+The secondary namenode http server address and port.
+If the port is 0 then the server will start on a free port.
+/description
+/property
+
+property
+namedfs.datanode.address/name
+value0.0.0.0:50010/value
+description
+The address where the datanode server will listen to.
+If the port is 0 then the server will start on a free port.
+/description
+/property
+
+property
+namedfs.datanode.http.address/name
+value0.0.0.0:50075/value
+description
+The datanode http server address and port.
+If the port is 0 then the server will start on a free port.
+/description
+/property
+
+property
+namedfs.datanode.ipc.address/name
+value0.0.0.0:50020/value
+description
+The datanode ipc server address and port.
+If the port is 0 then the server will start on a free port.
+/description
+/property
+
+property
+namedfs.datanode.handler.count/name
+value3/value
+descriptionThe number of server threads for the datanode./description
Re: Refactoring TLP pom (was Re: Mailbox doc)
Hi Eric On 10/12/2011 11:36 AM, Eric Charles wrote: Hi Felix, Thx for launching the discussion and implementing in a sandbox :) I feel your focus is the maven-skin. Right? Well it's not that I'm focussing on maven-skin (anyway the name might be confusing ...) but I remember when started in the James project. It was really hard to figure out the hierarchy parent poms. Some where referencing james-project, others james-parent. Having a quick look at the filesystem I could not find a short answer because I found it quite a mess. Having a project/project/'james-project'.pom.xml which was mainly used as modules parent pom but referencing to project/'james.parent'.pom.xml. In fact this is the real TLP pom.xml - it must be, because referencing as parent the apache.pom. But way are some modules referencing the one and other modules the other pom as 'TLP' pom? And which is now the real source code which is work on? The conclusion is that it's historical grown and longtime members are aware of what is actual and what isn't, but still there for ?? We can have A) or B). But if we choose B) the project/project tree must be cleaned and the project/pom.xml will have as only task to build the 2 modules 'skin' and 'project' whereas project is the TLP pom to use as parent for all other James modules. I am also concerned with the way we handle the version dependencies. Example: For now, each of the project (imap, mailbox...) has freedom to define the derby version. This sometimes can give issues, as projects are implemented/tested against a specific version, and this can give issues. So, Should parent impose the version, or should we leave freedom to subprojects to do so? I don't know which is better. Having the dependencyManagement in the TLP pom it will probably mean to release often also TLP pom. OTH we don't need to fight a dependency version hell among the modules. Also, the transitive dependencies are sometimes/often declared around (example, if a project uses mailbox-jpa, it still declares openjpa altough openjpa is a transitive dependency of mailbox-jpa). For example, I'm puzzled to need to exclude jruby in all projects. If we rely on the transitive resolution, we only have to exclude once. This point is not directly related to the parent structure, but more linked to a 'transitive dependency' discussion. But I feel it's also linked to the pom hierarchy in a way... I feel the same (see above). You're talking about my latest excludes in the spring module for tests I suppose (of course others exists as well) - I'm not sure if trasitive exclusion also works for dependencies of scope test. Does anybody knows more about this? When refactoring poms we should definitely make use of the dependency:tree dependency:analyze ... goals of maven to clean it up. I don't bring answers but questions here... But they can help to clarify the problem :-) Another point is to define what to use for logging tests and where to deploy a logging implementation. We use SLF4J as facade. IMO this implicates not to deploy any logging framewoks like log4j (including slf4j-log4j12) or similar exept when packaging a distribution. Therefore all such logging frameworks should be excluded. The only dependency should be slfj4-api. For logging tests we should agree on one like slf4j-simple or slf4j-nop scoped 'test'. Regard Felix PS: Still no answers ;-) Thx, Eric On 09/10/11 16:58, Felix Knecht wrote: On 10/09/2011 11:28 AM, Felix Knecht wrote: Hi all A) I setup a small sample how this could look alike when splitting things off and discard legacy things. Have a TLP pom.xml (james-parent / james-project or ...) being a merge of the 2 former TLP/parent poms [1][2]. New the pluginManagement section will contain all the plugins with their version and their configuration so far this can be applied to each module. This is specially the case for the site generation (not only javadoc). The skin module [3] is no longer part of the TLP pom module but has its own module space lets name it james-skin which is less irritating than maven-skin at first glance. What shall happen with the existing project tree [1], which will become obsolete? Will it be replace by the proposed TLP module (when it gets named 'james-project') or does it just stays as it is and a new module 'parent' for TLP module is created? B) Another approach than splitting up in different modules is to clean up the current parent.pom [4] so it contains more or less only the definitions to build the project maven-skin and the project module. This will mean [4] will not have a parent definition (and all the other stuff like properties, developers, ...) at all and the TLP pom will be the current project.pom [5]. Definitions now in the parent.pom [4] will be merged into the new TLP pom [5]. The new TLP pom [5] will have as parent org.apache/apache. When going the 2nd way B) we should IMO move the legacy server [6] tree to somewhere else
Re: Refactoring TLP pom (was Re: Mailbox doc)
On 10/12/2011 12:31 PM, Stefano Bagnara wrote: 2011/10/12 Felix Knechtfel...@apache.org On 10/12/2011 11:36 AM, Eric Charles wrote: Thx for launching the discussion and implementing in a sandbox :) I feel your focus is the maven-skin. Right? Well it's not that I'm focussing on maven-skin (anyway the name might be confusing ...) but I remember when started in the James project. It was really hard to figure out the hierarchy parent poms. Some where referencing james-project, others james-parent. Having a quick look at the filesystem I could not find a short answer because I found it quite a mess. I am the author of the mess :-) So, I try to explain why it worked that way, but it's been a while, so I'm not sure I remember the details. I did loose a lot of time with try and error to reach the current structure and I settled to that structure because it was the only one that worked fine with maven, maven site, the skin and the release process. I remember that time being happy finally having something working :-) Now, since I did that we use a new maven version (3 vs 2) and a lot of new site-plugin versions have been released and maybe they fixed the issues that prevented me to use a simpler layout, so feel free to change it. Just remember to test also the release process as it easy to have circular dependencies between the skin and the parent using the skin (unless you want duplication of configuration between parent and the skin you will have skin to depend on parent). I'll setup a sample in my sandbox. So we have something real to discuss on it and see if it works. Regards Felix I'm sorry I have no time currently to give good answers to your other questions, feel free to go ahead if you find an easier working solution. Stefano - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: svn commit: r1182282 - in /james/mailbox/trunk/hbase/src/test: java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java resources/hdfs-default.xml
On 10/12/2011 02:56 PM, Eric Charles wrote:
Hi,
In hadoop/hbase world, you set the conf properties by defining a
*-site.xml where you override the default properties defined in
*-default.xml which is shipped in the hadoop/hbase jar.
So rather than having hdfs-default.xml in our source tree, hdfs-site.xml
with only dfs.datanode.data.dir.perm property defined will be better.
Thanks for hint. It's even written in the header comment of the file :-(
We would say Lappi mach d Ouge uuf (Open your eyes, dumb cluck!)
Felix
Thx,
Eric
On 12/10/11 11:28, fel...@apache.org wrote:
Author: felixk
Date: Wed Oct 12 09:28:10 2011
New Revision: 1182282
URL: http://svn.apache.org/viewvc?rev=1182282view=rev
Log:
Move hard coded configurations into configuration file. The
configuration file originally is taken from
hadoop-core-0.20-append-r1057313.jar
Added:
james/mailbox/trunk/hbase/src/test/resources/hdfs-default.xml (with
props)
Modified:
james/mailbox/trunk/hbase/src/test/java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java
Modified:
james/mailbox/trunk/hbase/src/test/java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java
URL:
http://svn.apache.org/viewvc/james/mailbox/trunk/hbase/src/test/java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java?rev=1182282r1=1182281r2=1182282view=diff
==
---
james/mailbox/trunk/hbase/src/test/java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java
(original)
+++
james/mailbox/trunk/hbase/src/test/java/org/apache/james/mailbox/hbase/HBaseClusterSingleton.java
Wed Oct 12 09:28:10 2011
@@ -50,16 +50,6 @@ public class HBaseClusterSingleton {
public HBaseClusterSingleton(boolean useMiniCluster) throws Exception {
if (useMiniCluster) {
HBaseTestingUtility htu = new HBaseTestingUtility();
- htu.getConfiguration().setBoolean(dfs.support.append, true);
-
- // TODO
- // I got wrong filepermissions on the created files. This fixes it
for me.
- // Maybe this depends on the umask settings on the local linux box?
- // IMO following line should solve this, but it doesn't ..
- // (see http://hadoop.apache.org/hdfs/docs/r0.21.0/hdfs-default.html)
- //
- // htu.getConfiguration().set(dfs.permissions.enabled, false);
- htu.getConfiguration().set(dfs.datanode.data.dir.perm, 775);
try {
hbaseCluster = htu.startMiniCluster();
conf = hbaseCluster.getConfiguration();
Added: james/mailbox/trunk/hbase/src/test/resources/hdfs-default.xml
URL:
http://svn.apache.org/viewvc/james/mailbox/trunk/hbase/src/test/resources/hdfs-default.xml?rev=1182282view=auto
==
--- james/mailbox/trunk/hbase/src/test/resources/hdfs-default.xml (added)
+++ james/mailbox/trunk/hbase/src/test/resources/hdfs-default.xml Wed
Oct 12 09:28:10 2011
@@ -0,0 +1,370 @@
+?xml version=1.0?
+?xml-stylesheet type=text/xsl href=configuration.xsl?
+
+!-- Do not modify this file directly. Instead, copy entries that you
--
+!-- wish to modify from this file into hdfs-site.xml and change them
--
+!-- there. If hdfs-site.xml does not already exist, create it. --
+
+configuration
+
+property
+namedfs.namenode.logging.level/name
+valueinfo/value
+descriptionThe logging level for dfs namenode. Other values are
dir(trac
+e namespace mutations), block(trace block under/over replications
and block
+creations/deletions), or all./description
+/property
+
+property
+namedfs.secondary.http.address/name
+value0.0.0.0:50090/value
+description
+ The secondary namenode http server address and port.
+ If the port is 0 then the server will start on a free port.
+/description
+/property
+
+property
+namedfs.datanode.address/name
+value0.0.0.0:50010/value
+description
+ The address where the datanode server will listen to.
+ If the port is 0 then the server will start on a free port.
+/description
+/property
+
+property
+namedfs.datanode.http.address/name
+value0.0.0.0:50075/value
+description
+ The datanode http server address and port.
+ If the port is 0 then the server will start on a free port.
+/description
+/property
+
+property
+namedfs.datanode.ipc.address/name
+value0.0.0.0:50020/value
+description
+ The datanode ipc server address and port.
+ If the port is 0 then the server will start on a free port.
+/description
+/property
+
+property
+namedfs.datanode.handler.count/name
+value3/value
+descriptionThe number of server threads for the
datanode./description
+/property
+
+property
+namedfs.http.address/name
+value0.0.0.0:50070/value
+description
+ The address and the base port where the dfs namenode web ui will
listen on.
+ If the port is 0 then the server will start on a free port.
+/description
+/property
+
+property
+namedfs.https.enable/name
+valuefalse/value
+descriptionDecide if HTTPS(SSL) is supported on HDFS
+/description
+/property
+
+property
+namedfs.https.need.client.auth/name
+valuefalse/value
+descriptionWhether SSL client certificate authentication is
Re: Refactoring TLP pom (was Re: Mailbox doc)
On 10/12/2011 03:07 PM, Eric Charles wrote: On 12/10/11 12:18, Felix Knecht wrote: Well it's not that I'm focussing on maven-skin (anyway the name might be confusing ...) but I remember when started in the James project. It was really hard to figure out the hierarchy parent poms. I remember that also :) snip We can have A) or B). But if we choose B) the project/project tree must be cleaned and the project/pom.xml will have as only task to build the 2 modules 'skin' and 'project' whereas project is the TLP pom to use as parent for all other James modules. I still need to take time to give feedback on option A) and B). I am also concerned with the way we handle the version dependencies. Example: For now, each of the project (imap, mailbox...) has freedom to define the derby version. This sometimes can give issues, as projects are implemented/tested against a specific version, and this can give issues. So, Should parent impose the version, or should we leave freedom to subprojects to do so? I don't know which is better. Having the dependencyManagement in the TLP pom it will probably mean to release often also TLP pom. OTH we don't need to fight a dependency version hell among the modules. mmh, releasing TLP pom to change a derby version for example is not nice either... maybe others can comment, I can see benefits and drawbacks in both scenarii. Also, the transitive dependencies are sometimes/often declared around (example, if a project uses mailbox-jpa, it still declares openjpa altough openjpa is a transitive dependency of mailbox-jpa). For example, I'm puzzled to need to exclude jruby in all projects. If we rely on the transitive resolution, we only have to exclude once. This point is not directly related to the parent structure, but more linked to a 'transitive dependency' discussion. But I feel it's also linked to the pom hierarchy in a way... I feel the same (see above). You're talking about my latest excludes in the spring module for tests I suppose (of course others exists as well) - I'm not sure if trasitive exclusion also works for dependencies of scope test. Does anybody knows more about this? Don't know, but I will burn a candle before trying. I guess/home it should work. When refactoring poms we should definitely make use of the dependency:tree dependency:analyze ... goals of maven to clean it up. dependency:analyze is great for post analysis, but we need some kind of general rules to know how to implement. I don't bring answers but questions here... But they can help to clarify the problem :-) One more ... Can or should we find a more consistent naming for the produced artifacts? Look the prefixes at http://repo1.maven.org/maven2/org/apache/james/ - apache-james - apache - james - maven - none Another point is to define what to use for logging tests and where to deploy a logging implementation. We use SLF4J as facade. IMO this implicates not to deploy any logging framewoks like log4j (including slf4j-log4j12) or similar exept when packaging a distribution. Therefore all such logging frameworks should be excluded. The only dependency should be slfj4-api. For logging tests we should agree on one like slf4j-simple or slf4j-nop scoped 'test'. slf4j-* is one more topic to list in our pom/dependency discussion. Very interesting! At the end, it will be good to have all those rules/practices documented on http://james.apache.org/guidelines.html (or anywhere else, but somewhere). Regard Felix PS: Still no answers ;-) Asking is already giving the half of the answer. Thx, Eric On 09/10/11 16:58, Felix Knecht wrote: On 10/09/2011 11:28 AM, Felix Knecht wrote: Hi all A) I setup a small sample how this could look alike when splitting things off and discard legacy things. Have a TLP pom.xml (james-parent / james-project or ...) being a merge of the 2 former TLP/parent poms [1][2]. New the pluginManagement section will contain all the plugins with their version and their configuration so far this can be applied to each module. This is specially the case for the site generation (not only javadoc). The skin module [3] is no longer part of the TLP pom module but has its own module space lets name it james-skin which is less irritating than maven-skin at first glance. What shall happen with the existing project tree [1], which will become obsolete? Will it be replace by the proposed TLP module (when it gets named 'james-project') or does it just stays as it is and a new module 'parent' for TLP module is created? B) Another approach than splitting up in different modules is to clean up the current parent.pom [4] so it contains more or less only the definitions to build the project maven-skin and the project module. This will mean [4] will not have a parent definition (and all the other stuff like properties, developers, ...) at all and the TLP pom will be the current project.pom [5]. Definitions now in the parent.pom [4] will be merged into the new TLP
Re: Mailbox doc
Hi Eugen Your right :-) On 10/08/2011 09:18 PM, Ioan Eugen Stan wrote: Thanks, I am not familiar with the installation for the rest of the implementations, including guice. Maybe you can put in some words about them? For now, I am trying to make APIviz docs just for mailbox, and it seems that the pom hierarchy is very complex. I have a solution for standard javadoc:javadoc but that doesn't apply for site generation. I will try to find a way to configure the site generation javadoc plugin so all is ok. I did notice that the pom files need some clean-up and refactoring. For example, for javadoc-plugin there is a lot of duplicate configuration. I suggest we move a lot of the common configuration to PluginManagement and dependencyManagement sections in the parent pom and rely on inheritance to solve the rest of the issues. IMO we could do this for all kind of reporting plugins, not only for the javadoc one. Most of are used in the maven-site-plugin anyway. This would mean, that parent pom (org.apache.james/james-project.pom) will be released quite often, e.g. when updating to the latest reporting plugin versions. I'm not aware, that we can change the version but keep the configuration in a child pom, but maybe anybody knows more about this. Doing the configurations in the parent pom would make the child poms smaller. I wonder if we could not even merge the james-parent.pom and the james-project.pom into james-parent.pom? AFAICS james.project.pom would build legacy documentation for the server what is commented anyway. Doing so the project/project/src/site would need to be moved one level up as well (into james-parent.pom) We could even clean up the directory tree and move the legacy server 2.x stuff into a branch or to attic or where ever and have the james-parent renamed to the real name 'james-parent' from 'james-project', containg only the parent pom including pluginManagement section (including configurations for plugins used be site generation such as javadoc, findbugs and others) and the stuff for general site src stuff which is located atm @project/project/src/site. wdot? Regards Felix What do you think? - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Refactoring TLP pom (was Re: Mailbox doc)
On 10/09/2011 11:28 AM, Felix Knecht wrote: Hi all A) I setup a small sample how this could look alike when splitting things off and discard legacy things. Have a TLP pom.xml (james-parent / james-project or ...) being a merge of the 2 former TLP/parent poms [1][2]. New the pluginManagement section will contain all the plugins with their version and their configuration so far this can be applied to each module. This is specially the case for the site generation (not only javadoc). The skin module [3] is no longer part of the TLP pom module but has its own module space lets name it james-skin which is less irritating than maven-skin at first glance. What shall happen with the existing project tree [1], which will become obsolete? Will it be replace by the proposed TLP module (when it gets named 'james-project') or does it just stays as it is and a new module 'parent' for TLP module is created? B) Another approach than splitting up in different modules is to clean up the current parent.pom [4] so it contains more or less only the definitions to build the project maven-skin and the project module. This will mean [4] will not have a parent definition (and all the other stuff like properties, developers, ...) at all and the TLP pom will be the current project.pom [5]. Definitions now in the parent.pom [4] will be merged into the new TLP pom [5]. The new TLP pom [5] will have as parent org.apache/apache. When going the 2nd way B) we should IMO move the legacy server [6] tree to somewhere else as it is no longer used. wdyt? Regards Felix PS @Eugen I also setup mailbox in my sandbox project [7] to see if and how it works. I'm neither able to generate the site (mvn site) nor to genrate the technical reports (mvn site -Psite-reports). In both situations I get following error which is hardly a problem of the new structure using the demo poms but resulting of the javadoc-plugin configuration somehow. Do you haven any ideas what could be wrong? [ERROR] Failed to execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.8:aggregate (default) on project apache-james-mailbox: An error has occurred in JavaDocs report generation: [ERROR] Exit code: 1 - javadoc: error - /home/felix/svn/apache/james/trunk/sandbox/felixk/mailbox/target/classes doesn't exist or is not readable. [ERROR] [ERROR] Command line was: /usr/lib/jvm/jdk1.7.0/jre/../bin/javadoc -J-Xmx1024m -J-Xms256m @options @packages [ERROR] [1] https://svn.apache.org/repos/asf/james/project/trunk [2] https://svn.apache.org/repos/asf/james/project/trunk/project [3] https://svn.apache.org/repos/asf/james/project/trunk/maven-skin [4] https://svn.apache.org/repos/asf/james/project/trunk/pom.xml [5] https://svn.apache.org/repos/asf/james/project/trunk/project/pom.xml [6] https://svn.apache.org/repos/asf/james/project/trunk/project/server [7] https://svn.apache.org/repos/asf/james/trunk/sandbox/felixk/mailbox Hi Eugen Your right :-) On 10/08/2011 09:18 PM, Ioan Eugen Stan wrote: Thanks, I am not familiar with the installation for the rest of the implementations, including guice. Maybe you can put in some words about them? For now, I am trying to make APIviz docs just for mailbox, and it seems that the pom hierarchy is very complex. I have a solution for standard javadoc:javadoc but that doesn't apply for site generation. I will try to find a way to configure the site generation javadoc plugin so all is ok. I did notice that the pom files need some clean-up and refactoring. For example, for javadoc-plugin there is a lot of duplicate configuration. I suggest we move a lot of the common configuration to PluginManagement and dependencyManagement sections in the parent pom and rely on inheritance to solve the rest of the issues. IMO we could do this for all kind of reporting plugins, not only for the javadoc one. Most of are used in the maven-site-plugin anyway. This would mean, that parent pom (org.apache.james/james-project.pom) will be released quite often, e.g. when updating to the latest reporting plugin versions. I'm not aware, that we can change the version but keep the configuration in a child pom, but maybe anybody knows more about this. Doing the configurations in the parent pom would make the child poms smaller. I wonder if we could not even merge the james-parent.pom and the james-project.pom into james-parent.pom? AFAICS james.project.pom would build legacy documentation for the server what is commented anyway. Doing so the project/project/src/site would need to be moved one level up as well (into james-parent.pom) We could even clean up the directory tree and move the legacy server 2.x stuff into a branch or to attic or where ever and have the james-parent renamed to the real name 'james-parent' from 'james-project', containg only the parent pom including pluginManagement section (including configurations for plugins used be site generation such as javadoc, findbugs and others) and the stuff
Re: svn commit: r1180096 - /james/server/trunk/queue-activemq/src/main/java/org/apache/james/queue/activemq/FileSystemBlobStrategy.java
Wouldn't it make more sense to synchronize on queueF? There's BTW the
same problem for deleteFile (see first part of diff).
Regards
Felix
Index:
src/main/java/org/apache/james/queue/activemq/FileSystemBlobStrategy.java
===
---
src/main/java/org/apache/james/queue/activemq/FileSystemBlobStrategy.java (revision
1180096)
+++
src/main/java/org/apache/james/queue/activemq/FileSystemBlobStrategy.java (working
copy)
@@ -104,8 +104,8 @@
*/
public void deleteFile(ActiveMQBlobMessage message) throws
IOException, JMSException {
File f = getFile(message);
-if (f.exists()) {
-if (f.delete() == false) {
+synchronized (f) {
+if (f.exists() !f.delete()) {
throw new IOException(Unable to delete file + f);
}
}
@@ -143,20 +143,12 @@
File queueF = fs.getFile(queueUrl);
-// check if we need to create the queue folder
-if (!queueF.exists()) {
-if (!queueF.mkdirs()) {
-// It could be that queueF.mkdirs() returned false because
-// queueF has been created
-// in the meantime (eg. by a different thread). Only
throw an
-// exception if this is
-// not the case.
-if (!queueF.exists()) {
-throw new IOException(Unable to create directory
+ queueF.getAbsolutePath());
-}
+synchronized (queueF) {
+// check if we need to create the queue folder
+if (!queueF.exists() !queueF.mkdirs()) {
+throw new IOException(Unable to create directory +
queueF.getAbsolutePath());
}
-
- }
+}
return fs.getFile(queueUrl + / + filename);
On 10/07/2011 06:42 PM, nor...@apache.org wrote:
Author: norman
Date: Fri Oct 7 16:42:36 2011
New Revision: 1180096
URL: http://svn.apache.org/viewvc?rev=1180096view=rev
Log:
Make getFile(...) method of FileSystemBlobStrategy thread-safe. Thanks to
Michael Herrmann for the patch. See JAMES-1327
Modified:
james/server/trunk/queue-activemq/src/main/java/org/apache/james/queue/activemq/FileSystemBlobStrategy.java
Modified:
james/server/trunk/queue-activemq/src/main/java/org/apache/james/queue/activemq/FileSystemBlobStrategy.java
URL:
http://svn.apache.org/viewvc/james/server/trunk/queue-activemq/src/main/java/org/apache/james/queue/activemq/FileSystemBlobStrategy.java?rev=1180096r1=1180095r2=1180096view=diff
==
---
james/server/trunk/queue-activemq/src/main/java/org/apache/james/queue/activemq/FileSystemBlobStrategy.java
(original)
+++
james/server/trunk/queue-activemq/src/main/java/org/apache/james/queue/activemq/FileSystemBlobStrategy.java
Fri Oct 7 16:42:36 2011
@@ -144,11 +144,20 @@ public class FileSystemBlobStrategy impl
File queueF = fs.getFile(queueUrl);
// check if we need to create the queue folder
-if (queueF.exists() == false) {
+if (!queueF.exists()) {
if (!queueF.mkdirs()) {
-throw new IOException(Unable to create directory +
queueF.getAbsolutePath());
+// It could be that queueF.mkdirs() returned false because
+// queueF has been created
+// in the meantime (eg. by a different thread). Only throw an
+// exception if this is
+// not the case.
+if (!queueF.exists()) {
+throw new IOException(Unable to create directory +
queueF.getAbsolutePath());
+}
}
-}
+
+ }
+
return fs.getFile(queueUrl + / + filename);
}
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Prepare for new mailbox release
On 09/28/2011 09:45 AM, Norman Maurer wrote: Hi there, I think we should get ready for a new mailbox release. This is the first step needed for the next james server release. So please let me know if you have any concerns .. Sorry for bringing up a common, well known (annoying...) problem - how about documentation? I can find many empty document templates (see below). Are they left empty when releasing or should the be taken off the menu? mailbox-guice.xml mailbox-hbase.xml mailbox-jcr.xml mailbox-jpa.xml mailbox-maildir.xml mailbox-memory.xml mailbox-spring.xml mailbox-tool.xml Regards Felix - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Mailbox-Jpa
@Norman
Hi Norman
I think the MailboxIdUidKey should be embeddable but I'm not absolutely
sure. Can you please verify this?
Thanks and regards
Felix
### Eclipse Workspace Patch 1.0
#P apache-james-mailbox-jpa
Index:
src/main/java/org/apache/james/mailbox/jpa/mail/model/openjpa/AbstractJPAMessage.java
===
---
src/main/java/org/apache/james/mailbox/jpa/mail/model/openjpa/AbstractJPAMessage.java
(revision 1178736)
+++
src/main/java/org/apache/james/mailbox/jpa/mail/model/openjpa/AbstractJPAMessage.java
(working copy)
@@ -27,6 +27,7 @@
import javax.persistence.Basic;
import javax.persistence.CascadeType;
import javax.persistence.Column;
+import javax.persistence.Embeddable;
import javax.persistence.FetchType;
import javax.persistence.Id;
import javax.persistence.IdClass;
@@ -105,6 +106,7 @@
private static final String TOSTRING_SEPARATOR = ;
/** Identifies composite key */
+@Embeddable
public static class MailboxIdUidKey implements Serializable {
private static final long serialVersionUID = 7847632032426660997L;
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Mailbox-Jpa
On 10/05/2011 02:36 PM, Eric Charles wrote:
Hi Felix,
Are you referring to
http://openjpa.apache.org/builds/latest/docs/manual/jpa_overview_meta.html#jpa_overview_meta_embeddable
?
Yes. In this sample the class is annotated as @Entity whereas we do have
an abstract class - @MappedSuperclass. Maybe it @MappedSuperclass would
also work. Or the plugin gives a false positive, see below.
http://openjpa.apache.org/embeddable-samples.html
From the second link, it seems that an extra table is created (not sure).
That's what I understood as well.
Did you try to run with @Embeddable and look at the impact on database
tables?
No. I'm still trying to get a created schema by the openjpa plugin
I was pointed to it by maven build output:
145 WARN [main] openjpa.Enhance - Type class
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage$MailboxIdUidKey
loaded by java.net.URLClassLoader@6a37ea3c has no metadata; enhancing as
persistence aware. If you intended for class
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage$MailboxIdUidKey
to be persistence-capable, then this means that OpenJPA could not find
any metadata for class
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage$MailboxIdUidKey.
This can happen if the directory containing your metadata is not in your
CLASSPATH, or if your metadata files are not named properly. See the
documentation on metadata placement for more information.
Regards
Felix
Thx
Eric
On 05/10/11 14:03, Norman Maurer wrote:
Hi there,
I'm not sure either.. Maybe someone else can confirm ?
Bye,
Norman
2011/10/5 Felix Knechtfel...@apache.org:
@Norman
Hi Norman
I think the MailboxIdUidKey should be embeddable but I'm not absolutely
sure. Can you please verify this?
Thanks and regards
Felix
### Eclipse Workspace Patch 1.0
#P apache-james-mailbox-jpa
Index:
src/main/java/org/apache/james/mailbox/jpa/mail/model/openjpa/AbstractJPAMessage.java
===
---
src/main/java/org/apache/james/mailbox/jpa/mail/model/openjpa/AbstractJPAMessage.java
(revision 1178736)
+++
src/main/java/org/apache/james/mailbox/jpa/mail/model/openjpa/AbstractJPAMessage.java
(working copy)
@@ -27,6 +27,7 @@
import javax.persistence.Basic;
import javax.persistence.CascadeType;
import javax.persistence.Column;
+import javax.persistence.Embeddable;
import javax.persistence.FetchType;
import javax.persistence.Id;
import javax.persistence.IdClass;
@@ -105,6 +106,7 @@
private static final String TOSTRING_SEPARATOR = ;
/** Identifies composite key */
+ @Embeddable
public static class MailboxIdUidKey implements Serializable {
private static final long serialVersionUID = 7847632032426660997L;
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Mailbox-Jpa
On 10/05/2011 03:11 PM, Felix Knecht wrote:
On 10/05/2011 02:36 PM, Eric Charles wrote:
Hi Felix,
Are you referring to
http://openjpa.apache.org/builds/latest/docs/manual/jpa_overview_meta.html#jpa_overview_meta_embeddable
?
Yes. In this sample the class is annotated as @Entity whereas we do have
an abstract class - @MappedSuperclass. Maybe it @MappedSuperclass would
also work. Or the plugin gives a false positive, see below.
http://openjpa.apache.org/embeddable-samples.html
From the second link, it seems that an extra table is created (not sure).
That's what I understood as well.
Did you try to run with @Embeddable and look at the impact on database
tables?
No. I'm still trying to get a created schema by the openjpa plugin
Looking at the tables created by the test cases it seems, that it's not
really relevant if it's annotated or not. No matter if @Embeddable,
@MappedSuperclass, @Entity or nothing is annotated always the same
tables are created. Only difference is that using any annotation the
warning disappears. I'd say it's a false positive and leave it as it is.
Sorry for the noise.
Regards
Felix
I was pointed to it by maven build output:
145 WARN [main] openjpa.Enhance - Type class
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage$MailboxIdUidKey
loaded by java.net.URLClassLoader@6a37ea3c has no metadata; enhancing as
persistence aware. If you intended for class
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage$MailboxIdUidKey
to be persistence-capable, then this means that OpenJPA could not find
any metadata for class
org.apache.james.mailbox.jpa.mail.model.openjpa.AbstractJPAMessage$MailboxIdUidKey.
This can happen if the directory containing your metadata is not in your
CLASSPATH, or if your metadata files are not named properly. See the
documentation on metadata placement for more information.
Regards
Felix
Thx
Eric
On 05/10/11 14:03, Norman Maurer wrote:
Hi there,
I'm not sure either.. Maybe someone else can confirm ?
Bye,
Norman
2011/10/5 Felix Knechtfel...@apache.org:
@Norman
Hi Norman
I think the MailboxIdUidKey should be embeddable but I'm not absolutely
sure. Can you please verify this?
Thanks and regards
Felix
### Eclipse Workspace Patch 1.0
#P apache-james-mailbox-jpa
Index:
src/main/java/org/apache/james/mailbox/jpa/mail/model/openjpa/AbstractJPAMessage.java
===
---
src/main/java/org/apache/james/mailbox/jpa/mail/model/openjpa/AbstractJPAMessage.java
(revision 1178736)
+++
src/main/java/org/apache/james/mailbox/jpa/mail/model/openjpa/AbstractJPAMessage.java
(working copy)
@@ -27,6 +27,7 @@
import javax.persistence.Basic;
import javax.persistence.CascadeType;
import javax.persistence.Column;
+import javax.persistence.Embeddable;
import javax.persistence.FetchType;
import javax.persistence.Id;
import javax.persistence.IdClass;
@@ -105,6 +106,7 @@
private static final String TOSTRING_SEPARATOR = ;
/** Identifies composite key */
+ @Embeddable
public static class MailboxIdUidKey implements Serializable {
private static final long serialVersionUID = 7847632032426660997L;
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
-
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Prepare for new mailbox release
Just adding the repository does works for me using the current trunk (I think I should commit it to make it compiling also when having a clean local repository...). But there may be another problem we can run into: There's no garantee, that the rawson's repository will stay when have done the release. It does also works using the hadoop-test-0.20.3-SNAPSHOT, but this will not solve the problem, because the release procedure will not perform when having SNAPSHOT dependencies included. repositories repository idhadoop-non-releases/id nameHadoop non-releases/name urlhttp://people.apache.org/~rawson/repo//url snapshots enabledfalse/enabled /snapshots releases enabledtrue/enabled /releases /repository /repositories Regards Felix PS I run it on a linux box. If ever Windows boxes may behave different because of file locking ... On 09/30/2011 06:58 PM, Ioan Eugen Stan wrote: From what I can remember, there are some issues with [1] https://issues.apache.org/jira/browse/MAILBOX-133. It's abut the tests, which require a running HBase cluster. I will try to fix it tomorrow. I think I can fix this by creating a special testing configuration for HBase mailbox (using spring testing framework and @ContextConfiguration ) in which I start a MiniHBase cluster. But this is kind of weird, that testing integration requires something like this. I tried to fix the issue without much success. I manage to create the cluster but the test seems to hang and does nothing. I attached the patch so you can follow my modifications. Things are going quite slow because I lost some stuff, including my glasses. Does the test require some information in HBase, like a table schema? Regards, - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
Re: Prepare for new mailbox release
On 10/04/2011 12:44 PM, Norman Maurer wrote: Yeah please add it back as without it its not buildable. I wonder if we may not just use normal hadoop for the tests as we don't care about append or not in tests. wdyt ? I agree, but don't know if this is possible. Thinking a bit longer about it I propose to use the SNAPSHOT alternative. It looks like a release can be performed, the snapshot dependency is resolved to the current snapshot (e.g. hadoop-test-0.20.3-20100310.105839-3.jar). Doing so the problem will stay the same, we don't know when the artifact is no longer available in the repository (snapshot or private repository), but we can keep the pom.xml cleaner. wdyt? Regards Felix Bye, Norman 2011/10/4 Felix Knechtfel...@apache.org: Just adding the repository does works for me using the current trunk (I think I should commit it to make it compiling also when having a clean local repository...). But there may be another problem we can run into: There's no garantee, that the rawson's repository will stay when have done the release. It does also works using the hadoop-test-0.20.3-SNAPSHOT, but this will not solve the problem, because the release procedure will not perform when having SNAPSHOT dependencies included. repositories repository idhadoop-non-releases/id nameHadoop non-releases/name urlhttp://people.apache.org/~rawson/repo//url snapshots enabledfalse/enabled /snapshots releases enabledtrue/enabled /releases /repository /repositories Regards Felix PS I run it on a linux box. If ever Windows boxes may behave different because of file locking ... On 09/30/2011 06:58 PM, Ioan Eugen Stan wrote: From what I can remember, there are some issues with [1] https://issues.apache.org/jira/browse/MAILBOX-133. It's abut the tests, which require a running HBase cluster. I will try to fix it tomorrow. I think I can fix this by creating a special testing configuration for HBase mailbox (using spring testing framework and @ContextConfiguration ) in which I start a MiniHBase cluster. But this is kind of weird, that testing integration requires something like this. I tried to fix the issue without much success. I manage to create the cluster but the test seems to hang and does nothing. I attached the patch so you can follow my modifications. Things are going quite slow because I lost some stuff, including my glasses. Does the test require some information in HBase, like a table schema? Regards, - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
