James Server
  1. James Server
  2. JAMES-876

cannot start as spring-deployment when built from trunk as described in HOW-TO.TXT

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: Trunk
    • Fix Version/s: 3.0-M1
    • Component/s: None
    • Labels:
      None

      Description

      • console snippet containing stack trace:
        [java] INFO 12:52:02,609 | org.apache.james.container.spring.beanfactory.JamesApplicationContext | 45 beans defined in application context [org.apache.james.container.spring.beanfactory.JamesApplicationContext;hashCode=26210109]
        [java] Exception in thread "main" org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class
        [org.apache.james.mailboxmanager.impl.DefaultMailboxManagerProvider] for bean with name 'mailboxmanager' defined in null; nested exception is java.lang.ClassNotFoundException: org.apache.james.mailboxmanager.impl.DefaultMailboxManagerProvider
        [java] Caused by: java.lang.ClassNotFoundException: org.apache.james.mailboxmanager.impl.DefaultMailboxManagerProvider
        [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        [java] at java.security.AccessController.doPrivileged(Native Method)
        [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        [java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
        [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        [java] at org.springframework.util.ClassUtils.forName(ClassUtils.java:177)
        [java] at org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:313)
        [java] at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:912)
        [java] at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanNamesForType(DefaultListableBeanFactory.java:165)
        [java] at org.springframework.context.support.AbstractApplicationContext.getBeanNamesForType(AbstractApplicationContext.java:687)
        [java] at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:397)
        [java] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:330)
        [java] at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:56)
        [java] at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:49)
        [java] at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:45)
        [java] at org.apache.james.container.spring.Main.main(Main.java:29)
        [java] Java Result: 1
      1. build.xml.patch
        0.6 kB
        Joerg Buchberger

        Activity

        Hide
        Joerg Buchberger added a comment -

        OK, I could track that exception down to the mailboxmanager block declaration in james-assembly.xml (current trunk version as of now), where the class is defined as
        org.apache.james.mailboxmanager.impl.DefaultMailboxManagerProvider
        which cannot be found (see exception stack trace in original description).

        This class was moved to another package in Rev. 696446 (2008-09-17).
        So this can be partially fixed by changing the classname in aforementioned block to:
        org.apache.james.mailboxmanager.torque.DefaultMailboxManagerProvider

        If we do that, this class can be found, however, this just leads to the next errors/exceptions (see stacktrace below):
        org.apache.james.mailboxmanager.manager.MailboxManagerProvider - the interface implemented by aforementioned default provider - cannot be found. The reason for this might be, that this class was deleted from SVN in Rev. 692636 (2008-09-06) along with the enclosing module "mailbox-library".

        INFO 17:09:54,578 | org.apache.james.container.spring.beanfactory.JamesApplicationContext | Bean factory for application context [org.apache.james.container.spring.beanfactory.JamesApplicationContext;hashCode=1333195]: org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [fileSystemOverride,serviceManager,logger,privilegedPortsConfigurationInterceptor,stringRemapperConfigurationInterceptor,configurationProvider,avalonContext,loggerPropagator,contextPropagator,servicePropagator,configurationManager,initializationManager,James,mailboxmanager,spoolmanager,matcherpackages,mailetpackages,dnsserver,spoolmanagement,processormanagement,bayesiananalyzermanagement,remotemanager,usermanagement,imap-connections,imapserver,pop3server,smtpserver,nntpserver,nntp-repository,fetchmail,mailstore,spoolrepository,users-store,localusersrepository,filesystem,virtualusertablemanagement,virtualusertable-store,defaultvirtualusertable,domainlist,domainlistmanagement,connections,sockets,scheduler,database-connections,thread-manager]; root of BeanFactory hierarchy
        INFO 17:09:54,593 | org.apache.james.container.spring.beanfactory.JamesApplicationContext | 45 beans defined in application context [org.apache.james.container.spring.beanfactory.JamesApplicationContext;hashCode=1333195]
        Exception in thread "main" org.springframework.beans.factory.CannotLoadBeanClassException: Error loading class [org.apache.james.mailboxmanager.torque.DefaultMailboxManagerProvider] for bean with name 'mailboxmanager' defined in null: problem with class file or dependent class; nested exception is java.lang.NoClassDefFoundError: org/apache/james/mailboxmanager/manager/MailboxManagerProvider
        Caused by: java.lang.NoClassDefFoundError: org/apache/james/mailboxmanager/manager/MailboxManagerProvider
        at java.lang.ClassLoader.defineClass1(Native Method)
        at java.lang.ClassLoader.defineClass(ClassLoader.java:620)
        at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
        at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
        at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
        at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at org.springframework.util.ClassUtils.forName(ClassUtils.java:177)
        at org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:313)
        at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:912)
        at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanNamesForType(DefaultListableBeanFactory.java:165)
        at org.springframework.context.support.AbstractApplicationContext.getBeanNamesForType(AbstractApplicationContext.java:687)
        at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:397)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:330)
        at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:56)
        at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:49)
        at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:45)
        at org.apache.james.container.spring.Main.main(Main.java:29)
        Caused by: java.lang.ClassNotFoundException: org.apache.james.mailboxmanager.manager.MailboxManagerProvider
        at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        at java.security.AccessController.doPrivileged(Native Method)
        at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
        at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
        ... 22 more

        Show
        Joerg Buchberger added a comment - OK, I could track that exception down to the mailboxmanager block declaration in james-assembly.xml (current trunk version as of now), where the class is defined as org.apache.james.mailboxmanager.impl.DefaultMailboxManagerProvider which cannot be found (see exception stack trace in original description). This class was moved to another package in Rev. 696446 (2008-09-17). So this can be partially fixed by changing the classname in aforementioned block to: org.apache.james.mailboxmanager.torque.DefaultMailboxManagerProvider If we do that, this class can be found, however, this just leads to the next errors/exceptions (see stacktrace below): org.apache.james.mailboxmanager.manager.MailboxManagerProvider - the interface implemented by aforementioned default provider - cannot be found. The reason for this might be, that this class was deleted from SVN in Rev. 692636 (2008-09-06) along with the enclosing module "mailbox-library". INFO 17:09:54,578 | org.apache.james.container.spring.beanfactory.JamesApplicationContext | Bean factory for application context [org.apache.james.container.spring.beanfactory.JamesApplicationContext;hashCode=1333195] : org.springframework.beans.factory.support.DefaultListableBeanFactory defining beans [fileSystemOverride,serviceManager,logger,privilegedPortsConfigurationInterceptor,stringRemapperConfigurationInterceptor,configurationProvider,avalonContext,loggerPropagator,contextPropagator,servicePropagator,configurationManager,initializationManager,James,mailboxmanager,spoolmanager,matcherpackages,mailetpackages,dnsserver,spoolmanagement,processormanagement,bayesiananalyzermanagement,remotemanager,usermanagement,imap-connections,imapserver,pop3server,smtpserver,nntpserver,nntp-repository,fetchmail,mailstore,spoolrepository,users-store,localusersrepository,filesystem,virtualusertablemanagement,virtualusertable-store,defaultvirtualusertable,domainlist,domainlistmanagement,connections,sockets,scheduler,database-connections,thread-manager] ; root of BeanFactory hierarchy INFO 17:09:54,593 | org.apache.james.container.spring.beanfactory.JamesApplicationContext | 45 beans defined in application context [org.apache.james.container.spring.beanfactory.JamesApplicationContext;hashCode=1333195] Exception in thread "main" org.springframework.beans.factory.CannotLoadBeanClassException: Error loading class [org.apache.james.mailboxmanager.torque.DefaultMailboxManagerProvider] for bean with name 'mailboxmanager' defined in null: problem with class file or dependent class; nested exception is java.lang.NoClassDefFoundError: org/apache/james/mailboxmanager/manager/MailboxManagerProvider Caused by: java.lang.NoClassDefFoundError: org/apache/james/mailboxmanager/manager/MailboxManagerProvider at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClass(ClassLoader.java:620) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124) at java.net.URLClassLoader.defineClass(URLClassLoader.java:260) at java.net.URLClassLoader.access$000(URLClassLoader.java:56) at java.net.URLClassLoader$1.run(URLClassLoader.java:195) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at org.springframework.util.ClassUtils.forName(ClassUtils.java:177) at org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:313) at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:912) at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanNamesForType(DefaultListableBeanFactory.java:165) at org.springframework.context.support.AbstractApplicationContext.getBeanNamesForType(AbstractApplicationContext.java:687) at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:397) at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:330) at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:56) at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:49) at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:45) at org.apache.james.container.spring.Main.main(Main.java:29) Caused by: java.lang.ClassNotFoundException: org.apache.james.mailboxmanager.manager.MailboxManagerProvider at java.net.URLClassLoader$1.run(URLClassLoader.java:200) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:188) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) at java.lang.ClassLoader.loadClass(ClassLoader.java:251) at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319) ... 22 more
        Hide
        Joerg Buchberger added a comment -

        This effectively seems to mean, that sources from trunk are compiled against a jar, which has been built from sources that do not exist anymore in trunk for quite some time.
        This jar, however, is still available at compile time (otherwise I wouln't have been able to build), yet not in a runtime distribution.
        This could possibly mean, that source and build configuration needs some fixing or that I happened to try out james-trunk in the midst of some incomplete refactoring.

        Show
        Joerg Buchberger added a comment - This effectively seems to mean, that sources from trunk are compiled against a jar, which has been built from sources that do not exist anymore in trunk for quite some time. This jar, however, is still available at compile time (otherwise I wouln't have been able to build), yet not in a runtime distribution. This could possibly mean, that source and build configuration needs some fixing or that I happened to try out james-trunk in the midst of some incomplete refactoring.
        Hide
        Stefano Bagnara added a comment -

        @Joerg: yes, imap (and mailboxmanager stuff belongs to imap) has been moved out from server tree to its own module.
        Now imap is no more in the source tree but is included with jars in stage/org.apache.james/jars/ folder. In the mean time many classes have been repackaged so it probably is incomplete yet.

        Show
        Stefano Bagnara added a comment - @Joerg: yes, imap (and mailboxmanager stuff belongs to imap) has been moved out from server tree to its own module. Now imap is no more in the source tree but is included with jars in stage/org.apache.james/jars/ folder. In the mean time many classes have been repackaged so it probably is incomplete yet.
        Hide
        Joerg Buchberger added a comment -

        Is it possible to disable/deactivate this imap/mailboxmanager via configuration, so that I can get james-trunk running?

        If yes, please give me a pointer to some resource that explains how this can be done. Perché...

        ... poi potrebberei andare la via degli a-patch-e e mandarvi la configurazione pronto per committarla

        Show
        Joerg Buchberger added a comment - Is it possible to disable/deactivate this imap/mailboxmanager via configuration, so that I can get james-trunk running? If yes, please give me a pointer to some resource that explains how this can be done. Perché... ... poi potrebberei andare la via degli a-patch-e e mandarvi la configurazione pronto per committarla
        Hide
        Robert Burrell Donkin added a comment -

        Sorry about this - it was on my agenda. i'll take a look now.

        Show
        Robert Burrell Donkin added a comment - Sorry about this - it was on my agenda. i'll take a look now.
        Hide
        Robert Burrell Donkin added a comment -

        Please try again with fresh checkout and reopen if it's not fixed

        Show
        Robert Burrell Donkin added a comment - Please try again with fresh checkout and reopen if it's not fixed
        Hide
        Joerg Buchberger added a comment -

        First of all, thanks a lot for working on this so quickly.
        Unfortunately, I still wasn't able to run successfully.

        What I did:
        1. updated SVN workfiles with latest changes (702039)
        2. ant dist in trunk root
        3. ant run in spring-deployment

        This produced a ClassNotFoundException: org.apache.james.context.AvalonFileSystem

        Note, that my platform is SunJDK-6u6 + WinXPsp2 + intel-core2duo.

        Stacktrace:
        [java] INFO 11:54:19,390 | org.apache.james.container.spring.beanfactory.JamesApplicationContext | 43 beans defined in application context [org.apache.james.container.spring.beanfactory.JamesApplicationContext;hashCode=26210109]
        [java] Exception in thread "main" org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.apache.james.context.AvalonFileSystem] for bean with name 'filesystem' defined in null; nested exception is java.lang.ClassNotFoundException: org.apache.james.context.AvalonFileSystem
        [java] Caused by: java.lang.ClassNotFoundException: org.apache.james.context.AvalonFileSystem
        [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
        [java] at java.security.AccessController.doPrivileged(Native Method)
        [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
        [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
        [java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276)
        [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
        [java] at org.springframework.util.ClassUtils.forName(ClassUtils.java:177)
        [java] at org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:313)
        [java] at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:912)
        [java] at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanNamesForType(DefaultListableBeanFactory.java:165)
        [java] at org.springframework.context.support.AbstractApplicationContext.getBeanNamesForType(AbstractApplicationContext.java:687)
        [java] at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:397)
        [java] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:330)
        [java] at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:56)
        [java] at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:49)
        [java] at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:45)
        [java] at org.apache.james.container.spring.Main.main(Main.java:29)
        [java] Java Result: 1

        Show
        Joerg Buchberger added a comment - First of all, thanks a lot for working on this so quickly. Unfortunately, I still wasn't able to run successfully. What I did: 1. updated SVN workfiles with latest changes (702039) 2. ant dist in trunk root 3. ant run in spring-deployment This produced a ClassNotFoundException: org.apache.james.context.AvalonFileSystem Note, that my platform is SunJDK-6u6 + WinXPsp2 + intel-core2duo. Stacktrace: [java] INFO 11:54:19,390 | org.apache.james.container.spring.beanfactory.JamesApplicationContext | 43 beans defined in application context [org.apache.james.container.spring.beanfactory.JamesApplicationContext;hashCode=26210109] [java] Exception in thread "main" org.springframework.beans.factory.CannotLoadBeanClassException: Cannot find class [org.apache.james.context.AvalonFileSystem] for bean with name 'filesystem' defined in null; nested exception is java.lang.ClassNotFoundException: org.apache.james.context.AvalonFileSystem [java] Caused by: java.lang.ClassNotFoundException: org.apache.james.context.AvalonFileSystem [java] at java.net.URLClassLoader$1.run(URLClassLoader.java:200) [java] at java.security.AccessController.doPrivileged(Native Method) [java] at java.net.URLClassLoader.findClass(URLClassLoader.java:188) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:306) [java] at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:276) [java] at java.lang.ClassLoader.loadClass(ClassLoader.java:251) [java] at org.springframework.util.ClassUtils.forName(ClassUtils.java:177) [java] at org.springframework.beans.factory.support.AbstractBeanDefinition.resolveBeanClass(AbstractBeanDefinition.java:313) [java] at org.springframework.beans.factory.support.AbstractBeanFactory.resolveBeanClass(AbstractBeanFactory.java:912) [java] at org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanNamesForType(DefaultListableBeanFactory.java:165) [java] at org.springframework.context.support.AbstractApplicationContext.getBeanNamesForType(AbstractApplicationContext.java:687) [java] at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:397) [java] at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:330) [java] at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:56) [java] at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:49) [java] at org.apache.james.container.spring.beanfactory.JamesApplicationContext.newJamesApplicationContext(JamesApplicationContext.java:45) [java] at org.apache.james.container.spring.Main.main(Main.java:29) [java] Java Result: 1
        Hide
        Stefano Bagnara added a comment -

        @Joerg

        AvalonFileSystem should not be needed by the spring deployment because it is in the overriden list.
        Maybe there is something wrong there and spring still to instantiate that block but use another block when resolving dependencies so if the code is not there at all it results in that error.

        I don't have time to check better but you could try removing this from your assembly.xml:


        <!-- The context FileSystem implementation -->
        <block name="filesystem" class="org.apache.james.context.AvalonFileSystem">
        </block>


        If removing it gives you an error then you could also try putting any other existing class (with empty constructor, e.g: java.util.Properties) instead of AvalonFileSystem.. this probably is instantiated but not used.

        Show
        Stefano Bagnara added a comment - @Joerg AvalonFileSystem should not be needed by the spring deployment because it is in the overriden list. Maybe there is something wrong there and spring still to instantiate that block but use another block when resolving dependencies so if the code is not there at all it results in that error. I don't have time to check better but you could try removing this from your assembly.xml: <!-- The context FileSystem implementation --> <block name="filesystem" class="org.apache.james.context.AvalonFileSystem"> </block> If removing it gives you an error then you could also try putting any other existing class (with empty constructor, e.g: java.util.Properties) instead of AvalonFileSystem.. this probably is instantiated but not used.
        Hide
        Joerg Buchberger added a comment -

        Thanks - that was fast.

        Unfortunately, neither of the approaches worked for me.
        Note, that I applied them in my spring-deployment/target/james-server-spring-deployment-3.0-SNAPSHOT/conf/james-assembly.xml.
        Was this as intended?

        Show
        Joerg Buchberger added a comment - Thanks - that was fast. Unfortunately, neither of the approaches worked for me. Note, that I applied them in my spring-deployment/target/james-server-spring-deployment-3.0-SNAPSHOT/conf/james-assembly.xml. Was this as intended?
        Hide
        Joerg Buchberger added a comment -

        Found a fix that works for me. Don't know however, if this is in accordance with original intent of this build target, since the fix relies completely on what is built in target and therefore identical to nightly build.

        See attached patch, if you want to review my approach.

        Show
        Joerg Buchberger added a comment - Found a fix that works for me. Don't know however, if this is in accordance with original intent of this build target, since the fix relies completely on what is built in target and therefore identical to nightly build. See attached patch, if you want to review my approach.
        Hide
        Joerg Buchberger added a comment -

        @Stefano: Just FYI. Found out, that I needed to apply your hints in spring-deployment\src\main\config\james - but they produce FileNotFoundExceptions. (Note, that I did this tests against the original build.xml - not my new patched version.)

        Show
        Joerg Buchberger added a comment - @Stefano: Just FYI. Found out, that I needed to apply your hints in spring-deployment\src\main\config\james - but they produce FileNotFoundExceptions. (Note, that I did this tests against the original build.xml - not my new patched version.)
        Hide
        Robert Burrell Donkin added a comment -

        'ant run' has some trinky classpath issues for me (we'll probably end up rewriting both scripts so i'm not sure how much time i want to spend trying to fix it) but the scripst in 'target/james-server-spring-deployment-3.0-SNAPSHOT/
        bin' work for me. could you try that?

        Show
        Robert Burrell Donkin added a comment - 'ant run' has some trinky classpath issues for me (we'll probably end up rewriting both scripts so i'm not sure how much time i want to spend trying to fix it) but the scripst in 'target/james-server-spring-deployment-3.0-SNAPSHOT/ bin' work for me. could you try that?
        Hide
        Joerg Buchberger added a comment -

        Thanks, Robert - I figured that in the meantime
        It's more convenient/complete, however, if I just have to "ant run".
        That's why posted a patch yesterday, which works for me (see also my previous comments).
        It twists your buildfiles runclasspath, so that it's effectively the same as starting from the bin-directory of the build in the target sub-directory.
        I'm fine with that.

        By the way, the batch file in the bin-directory doesn't work on my system. Windows can't cope with the long commandline.
        That's why I chose ant for starting up (see also issue #877, where I attached another buildfile that fixes startup for me - it works the same way, of course, since builds from target subdirectory probably == nightly builds).

        Show
        Joerg Buchberger added a comment - Thanks, Robert - I figured that in the meantime It's more convenient/complete, however, if I just have to "ant run". That's why posted a patch yesterday, which works for me (see also my previous comments). It twists your buildfiles runclasspath, so that it's effectively the same as starting from the bin-directory of the build in the target sub-directory. I'm fine with that. By the way, the batch file in the bin-directory doesn't work on my system. Windows can't cope with the long commandline. That's why I chose ant for starting up (see also issue #877, where I attached another buildfile that fixes startup for me - it works the same way, of course, since builds from target subdirectory probably == nightly builds).
        Hide
        Bernd Fondermann added a comment -

        The batch file issues on Windows are covered by JAMES-848, let's not hijack issues.

        Show
        Bernd Fondermann added a comment - The batch file issues on Windows are covered by JAMES-848 , let's not hijack issues.
        Hide
        Norman Maurer added a comment -

        pure spring deployment builds without problem now (trunk)

        Show
        Norman Maurer added a comment - pure spring deployment builds without problem now (trunk)

          People

          • Assignee:
            Robert Burrell Donkin
            Reporter:
            Joerg Buchberger
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development