locale settings
Hello, I just installed the beta-4 of continuum. We run it standalone as a windows service (on windows server 2003). In previous releases (1.0.3 but also beta 3 and 2) continuum web pages were always displayed in English. Now (as of beta 4) they are in french. We still have the old version running on the same machine, and there the webapp is in English. Has anything changed in this release. How is the locale retrieved/determined? I'll check with our system admins to find out the specific settings for the user we use when running the service. I'll keep you informed, but any ideas are welcome.
Re: [maven-release-plugin] version as command line argument ?
The following post may contain an answer to your question (but it's rather a workaround): http://mail-archives.apache.org/mod_mbox/maven-users/200706.mbox/[EMAIL PROTECTED] On 9/14/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > Hi, > > Is it possible to give the version as command line parameter of the > release:prepare maven goal ? > > For example: > > mvn release:prepare -Dversion=1.2.0 -DnextVersion=1.3.0-SNAPSHOT > --batch-mode > > Thanks for your help ! > Olivier
Re: [m2][maven-surefire-plugin] using ClassLoader.getSystemResourceAsStream
Below you find the actual code I use.
In order to get the error, you just need a JUnit testCase that constructs
the PropertyReader class.
Note that I can not change the line ClassLoader.getSystemResourceAsStream("
log.properties"); as it's part of a library we use.
The file log.properties is present in the directory src/test/resources.
package test.surefire;
import java.io.IOException;
import java.io.InputStream;
import java.util.Properties;
public class PropertyReader {
private Properties systemLogProps;
public PropertyReader() throws IOException {
this.systemLogProps = new Properties();
InputStream is = ClassLoader.getSystemResourceAsStream("
log.properties");
// the following works
// InputStream is = this.getClass
().getClassLoader().getResourceAsStream("log.properties");
if (is == null) {
throw new RuntimeException("log.properties not found on the
classpath");
}
this.systemLogProps.load(is);
}
public String getProperty(String key) {
return this.systemLogProps.getProperty(key);
}
}
So the problem is that the file log.properties can not be found on the
system classpath.
Any help is appreciated.
On 7/1/07, Andrew Williams <[EMAIL PROTECTED]> wrote:
Perhaps posting the actual code will help. When it comes to
classloading many loaders such as eclipse
are very liberal whereas the surefire loader is more strict to the
java spec.
Andy
On 27 Jun 2007, at 14:05, Erik Ruisma wrote:
> Hello,
>
> I've been trying out several options on the maven-surefire-plugin
> (useSystemClassLoader, forkMode, childDelegation), but without any
> succes.
>
> We have some library that does a
> ClassLoader.getSystemResourceAsStream in
> order to read a property file.
> I've added that property file under src/test/resources but 'Maven'
> is unable
> to find it (seems to have to do with the IsolatedClassLoader).
> I can not change the getSystemResourceAsStream, as mentioned
> several times
> in this forum into something like this.getClass
> ().getClassLoader().getResourceAsStream(...
>
> I'm not quite sure what useSystemClassLoader is meant to do
> exactly. If I
> try to use it I get the following error:
>
> [INFO] Building jar: C:\DOCUME~1\mfr\LOCALS~1\Temp
> \surefirebooter58425.jar
> Forking command line: C:\javadev\tools\java\sdk\1.4.2_04\jre\bin
> \java -jar
> C:\DOCUME~1\mfr\LOCALS~1\Temp\surefirebooter58425.jar
> C:\DOCUME~1\mfr\LOCALS~1\Temp\surefire58423tmp
> C:\DOCUME~1\mfr\LOCALS~1\Temp\surefire58424tmp
> java.lang.NoClassDefFoundError: org/apache/maven/surefire/booter/
> SurefireBooter
> Exception in thread "main"
>
>
> Any clue on how to solve this error, or on how to get the
> getSystemResourceAsStream method working with Maven ?
>
>
> Thanks in advance !
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2][maven-surefire-plugin] using ClassLoader.getSystemResourceAsStream
Hello, I've been trying out several options on the maven-surefire-plugin (useSystemClassLoader, forkMode, childDelegation), but without any succes. We have some library that does a ClassLoader.getSystemResourceAsStream in order to read a property file. I've added that property file under src/test/resources but 'Maven' is unable to find it (seems to have to do with the IsolatedClassLoader). I can not change the getSystemResourceAsStream, as mentioned several times in this forum into something like this.getClass ().getClassLoader().getResourceAsStream(... I'm not quite sure what useSystemClassLoader is meant to do exactly. If I try to use it I get the following error: [INFO] Building jar: C:\DOCUME~1\mfr\LOCALS~1\Temp\surefirebooter58425.jar Forking command line: C:\javadev\tools\java\sdk\1.4.2_04\jre\bin\java -jar C:\DOCUME~1\mfr\LOCALS~1\Temp\surefirebooter58425.jar C:\DOCUME~1\mfr\LOCALS~1\Temp\surefire58423tmp C:\DOCUME~1\mfr\LOCALS~1\Temp\surefire58424tmp java.lang.NoClassDefFoundError: org/apache/maven/surefire/booter/ SurefireBooter Exception in thread "main" Any clue on how to solve this error, or on how to get the getSystemResourceAsStream method working with Maven ? Thanks in advance !
[M2][maven-ejb-plugin] dependencies for generated client
Hey all, I do not completely agree with some of the principles used in this [maven-ejb-plugin] plugin when generating the client-jar for the EJB. Currently when you tell Maven to create a client jar, it uses the same dependencies as defined for the EJB. I think this is fundamentally wrong. Clients for a service (EJB) should have as few dependencies as possible. If inside the implementation of the EJB one uses Spring, or Hibernate, or commons-logging, clients should not be aware of that. I think that typically the dependencies on the client are a subset of those of the service. Client dependencies should be kept minimal. So imagine an ideal solution: - while generating the client, Maven inspects the signature of the services offered by the EJB and adds all classes/libraries needed (I think some ant task did this using the BCEL lib). - additional classes/libs can be explicitly added. Would it be possible to implement this? Another option is to let the developer decide which libs/classes must be added as dependency for the client jar. Both options seem (to me) more usable than the current solution. But maybe I'm seeing things too simple? I'm looking forward to have some reactions on this. Currently we're having a problem where a project uses several client-ejb jar. All transitive dependencies are package with the project. The project now contains more than 100MB, due to all transitive dependencies. What are the options to solve this? Create a client jar file separately with the maven-jar-plugin ?
Re: build failures, warnings and continuum
Thanks a lot for the answer. I think we will wait for the 1.1 to be released (and hoping this will be anytime soon :-) ) Erik. On 4/5/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: In 1.1, you can force a build without changes (and re-do a complete checkout) And if you have 2 build definitions, the second build definition won't look if you have changes since the latest update of the working copy but since the latest execution of the current build definition to prevent to skip a build because an other build definition has already updated the working copy. Emmanuel David Roussel a écrit : > It's a bit of a hack, but you can see earlier posts in this list for how > to force a build with no changes, but it won't honour your dependency. > BTW it just uses curl and cron. > > As for the bug in 1.0.3, I think only bugs in 1.1-alpha are being fixed > by the commiters, so your best bet is to test on 1.1. Not great. > > BTW, you can do all this stuff in luntbuild. > > David > > On Wed, 4 Apr 2007 12:29:21 +0200, "Erik Ruisma" > <[EMAIL PROTECTED]> said: >> Indeed we use continuum 1.0.3. >> >> Ok we now got them running seperately, BUT only the first build is >> actually >> executed, the second build does not start as there are no changes in CVS. >> Is there any way to force a build even if there are no changes? In fact >> what >> I really want is that the second build is only executed if the first >> build >> has been launched. >> >> So scheduling two builds for the same project at the same time does not >> work, I believe that's a bug. >> >> On 4/3/07, David Roussel <[EMAIL PROTECTED]> wrote: >>> I take it you've got them to run ok separately? Do then run ok when >>> not scheduled together? >>> >>> Is this in continuum 1.0.3? >>> >>> >>> On 3 Apr 2007, at 16:28, Erik Ruisma wrote: >>> >>>> Thanks for your proposal. That's what we did. >>>> However this seems to create some new problems. >>>> So what we have are two build definitions for one project: one >>>> launching the >>>> tests, one creating and deploying the site. >>>> >>>> We have scheduled both builds to run at the same moment. BUT only one >>>> actually runs. >>>> Why ? >>>> I can find the following in our logs: >>>> INFO | jvm 1| 2007/04/02 20:00:00 | 2007-04-02 20:00:00,156 >>>> [defaultScheduler_Worker-2] INFO Continuum - >>>> Enqueuing >>>> 'MyProject' (Build definition id=116). >>>> INFO | jvm 1| 2007/04/02 20:00:00 | 2007-04-02 20:00:00,156 >>>> [defaultScheduler_Worker-2] INFO Continuum - >>>> Enqueuing >>>> 'MyProject' (Build definition id=118). >>>> >>>> Only the last one is executed. Is it possible that this is a bug in >>>> continuum ? ie that MyProject is somehow used as the key and only >>>> the last >>>> element from the queue remains? >>>> >>>> What if we would use 2 different build times (to make things more >>>> complex, I >>>> don't prefer it): is it possible to force the last scheduled build >>>> definition to run even if their are no modifications?? This seems >>>> to be also >>>> an issue...? >>>> >>>> >>>> Any feedback welcome. >>>> >>>> >>>> >>>> On 3/15/07, David Roussel <[EMAIL PROTECTED]> wrote: >>>>> Define two builds, one just to run the tests and report them. The >>>>> second build to just do the site. >>>>> >>>>> On Wed, 14 Mar 2007 11:47:07 +0100, "Erik Ruisma" >>>>> <[EMAIL PROTECTED]> said: >>>>>> Hello all, >>>>>> >>>>>> I'm not quite sure if this is a continuum or a Maven question, >>>>> but I >>>>>> thought >>>>>> to post first on the Continuum mailing list. >>>>>> >>>>>> In our company-wide settings I want that project sites are >>>>> generated, >>>>> and >>>>>> artifacts get deployed to our internal repository even when >>>>> there are >>>>>> some >>>>>> unit tests that fail. We also want that a mail is send when >>>>> there are >>>>>> test >>>>>> failures, with some kind of indication that their was a problem >>>>> during >>>>>> the >>>>>> build. >>>>>> >>>>>> How would you set this up ? >>>>>> >>>>>> >>> > > >
Re: build failures, warnings and continuum
Indeed we use continuum 1.0.3. Ok we now got them running seperately, BUT only the first build is actually executed, the second build does not start as there are no changes in CVS. Is there any way to force a build even if there are no changes? In fact what I really want is that the second build is only executed if the first build has been launched. So scheduling two builds for the same project at the same time does not work, I believe that's a bug. On 4/3/07, David Roussel <[EMAIL PROTECTED]> wrote: I take it you've got them to run ok separately? Do then run ok when not scheduled together? Is this in continuum 1.0.3? On 3 Apr 2007, at 16:28, Erik Ruisma wrote: > Thanks for your proposal. That's what we did. > However this seems to create some new problems. > So what we have are two build definitions for one project: one > launching the > tests, one creating and deploying the site. > > We have scheduled both builds to run at the same moment. BUT only one > actually runs. > Why ? > I can find the following in our logs: > INFO | jvm 1| 2007/04/02 20:00:00 | 2007-04-02 20:00:00,156 > [defaultScheduler_Worker-2] INFO Continuum - > Enqueuing > 'MyProject' (Build definition id=116). > INFO | jvm 1| 2007/04/02 20:00:00 | 2007-04-02 20:00:00,156 > [defaultScheduler_Worker-2] INFO Continuum - > Enqueuing > 'MyProject' (Build definition id=118). > > Only the last one is executed. Is it possible that this is a bug in > continuum ? ie that MyProject is somehow used as the key and only > the last > element from the queue remains? > > What if we would use 2 different build times (to make things more > complex, I > don't prefer it): is it possible to force the last scheduled build > definition to run even if their are no modifications?? This seems > to be also > an issue...? > > > Any feedback welcome. > > > > On 3/15/07, David Roussel <[EMAIL PROTECTED]> wrote: >> >> Define two builds, one just to run the tests and report them. The >> second build to just do the site. >> >> On Wed, 14 Mar 2007 11:47:07 +0100, "Erik Ruisma" >> <[EMAIL PROTECTED]> said: >> > Hello all, >> > >> > I'm not quite sure if this is a continuum or a Maven question, >> but I >> > thought >> > to post first on the Continuum mailing list. >> > >> > In our company-wide settings I want that project sites are >> generated, >> and >> > artifacts get deployed to our internal repository even when >> there are >> > some >> > unit tests that fail. We also want that a mail is send when >> there are >> > test >> > failures, with some kind of indication that their was a problem >> during >> > the >> > build. >> > >> > How would you set this up ? >> > >> > >>
Re: build failures, warnings and continuum
Thanks for your proposal. That's what we did. However this seems to create some new problems. So what we have are two build definitions for one project: one launching the tests, one creating and deploying the site. We have scheduled both builds to run at the same moment. BUT only one actually runs. Why ? I can find the following in our logs: INFO | jvm 1| 2007/04/02 20:00:00 | 2007-04-02 20:00:00,156 [defaultScheduler_Worker-2] INFO Continuum - Enqueuing 'MyProject' (Build definition id=116). INFO | jvm 1| 2007/04/02 20:00:00 | 2007-04-02 20:00:00,156 [defaultScheduler_Worker-2] INFO Continuum - Enqueuing 'MyProject' (Build definition id=118). Only the last one is executed. Is it possible that this is a bug in continuum ? ie that MyProject is somehow used as the key and only the last element from the queue remains? What if we would use 2 different build times (to make things more complex, I don't prefer it): is it possible to force the last scheduled build definition to run even if their are no modifications?? This seems to be also an issue...? Any feedback welcome. On 3/15/07, David Roussel <[EMAIL PROTECTED]> wrote: Define two builds, one just to run the tests and report them. The second build to just do the site. On Wed, 14 Mar 2007 11:47:07 +0100, "Erik Ruisma" <[EMAIL PROTECTED]> said: > Hello all, > > I'm not quite sure if this is a continuum or a Maven question, but I > thought > to post first on the Continuum mailing list. > > In our company-wide settings I want that project sites are generated, and > artifacts get deployed to our internal repository even when there are > some > unit tests that fail. We also want that a mail is send when there are > test > failures, with some kind of indication that their was a problem during > the > build. > > How would you set this up ? > >
build failures, warnings and continuum
Hello all, I'm not quite sure if this is a continuum or a Maven question, but I thought to post first on the Continuum mailing list. In our company-wide settings I want that project sites are generated, and artifacts get deployed to our internal repository even when there are some unit tests that fail. We also want that a mail is send when there are test failures, with some kind of indication that their was a problem during the build. How would you set this up ? We've had some ideas but none of them seems the respond to our questions. Perhaps we're missing something here? Currently, the nightly build is fails if there are test failures, so the site is not published, the artifact is not deployed, ... I think these are the default settings. -1- One idea was to use the variable "maven.test.failure.ignore=true" for all continuum builds => if the test fails, the site is published and the artifact is deployed. BUT the build result is successfull and no mail is sent to the development team => The development team doesn't know they are test failures ... unless they look at the surefire report. We prefer to send a mail in this case with a clear indications that there is a problem. -2- Another idea was to use the command line parameter --fail-at-end in all continuum build definitions example: mvn clean deploy site --fail-at-end. BUT this is not a good solution as the tests are also executed when calling the site goal, so this goal fails before it's able to do the deployment. -3- Another idea was to provide an extra build definition inside continuum. A) clean deploy site site:deploy --batch-mode - Dmaven.test.failure.ignore=true Result: the artifact is deployed and the site is generated, but the build is successfull (no mail sent) B) clean test --batch-mode Result: nothing is done, and the build fails when there are test failures (mail is sent to development team) Any other ideas are highly appreciated.
Re: software bundles and maven repositories
Thanks a lot for your replies. This solved my problem. This is what we did. We've added JAXP 1.3.2 to our internal repo using the following POM (by executing 'mvn deploy'): > 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";> > 4.0.0 > > javax.xml > jaxp > 1.3.2 > jaxp bundle > placeholder for software bundle JAXP > > pom > > > > org.w3c.dom > dom > 2.5.2 > > > javax.xml.parsers > jaxp-api > 1.3.2 > > > sax > sax > 2.0.1 > > > xalan > xalan > 2.5.2 > > > xerces > xercesImpl > 2.5.2 > > > > > > central > our internal company repository > file:///\\ourRepoServer > > > > > This seems to work fine when using it in other projects, don't forget the to mention the dependency type: javax.xml jaxp 1.3.2 pom
software bundles and maven repositories
Hello, what does Maven2 recommend when you have projects that depend on software bundles à la JAXP, JWSDP, ... or others? In general these software bundles are a collection of other libraries (eg JAXP 1.3 contains version X of xercesImpl, version Y of xalan,..). So how do you define a dependency to those packages, or how do you add them to your internal repository? I don't seem to find these packages (I'm especially looking for JAXP 1.3 at this moment) on the public repositories. I assume there are a lot of people out there who have encountered these questions before. Our internal repository already contains some of the jaxp dependencies. So I was thinking about adding a POM for jaxp version 1.3 that uses that links to the correct versions of the other libraries. I assume that this should do the job correctly? Any feedback would be greatly appreciated.
Re: Exception while registering Interceptor class pssForceAdminUserInterceptor
Seems like some update have been submitted to the archiva project I got it up and running know: As mentionned on the site Deploying in Plexus is broken at the moment. This works fine for me: - cd archiva-webapp - mvn jetty:run On 11/9/06, Erik Ruisma <[EMAIL PROTECTED]> wrote: Hello, I've followed the archiva installation instruction as described on: http://maven.apache.org/archiva/guides/getting-started/index.html However I keep getting the same errors over and over. The first problem I encountered was when running plexus.bat (I'm on Windows XP), which resulted in: -> Error 500 Unable to compile class for JSP I figured out quite quickly I had to add tools.jar to %archiva_home%\core, which solves that problem. Remark (when using %archiva_home%\bin\win32\run.bat I don't need the tools.jar). With both run.bat and plexus.bat (and also installed with tomcat) I always get the following stacktrace: Error 404 Caught Exception while registering Interceptor class pssForceAdminUserInterceptor HTTP ERROR: 404 Caught Exception while registering Interceptor class pssForceAdminUserInterceptor RequestURI=/index.action This results in an enormous log file (see bottom). The cause of this all seems to be: Caused by: org.codehaus.plexus.component.composition.CompositionException: Component Composition failed. No field of name: 'config' exists in component: role: ' org.codehaus.plexus.security.policy.UserSecurityPolicy', implementation: ' org.codehaus.plexus.security.policy.DefaultUserSecurityPolicy', role hint: 'default' How can I fix this? I already cleaned my local repository, but I got the same exception again. Any help would be appreciated. Thanks, Erik C:\javadev\tools\archiva\1.0.0-SNAPSHOT\bin\win32> run.bat wrapper | --> Wrapper Started as Console wrapper | Launching a JVM... jvm 1| Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org jvm 1| jvm 1| [INFO] Loading on start [role,roleHint]: [ org.codehaus.plexus.naming.Naming,dataSources] jvm 1| [INFO] Services will be deployed in: '..\..\services'. jvm 1| [INFO] Applications will be deployed in: '..\..\apps'. jvm 1| [INFO] Service Supervisor is deploying plexus-appserver-service-jetty-2.0-alpha-3. jvm 1| [INFO] Removing old service. jvm 1| [INFO] Loading on start [role,roleHint]: [ org.codehaus.plexus.appserver.service.PlexusService ,jetty] jvm 1| 09-Nov-2006 12:40:54 org.mortbay.http.HttpServer doStart jvm 1| INFO: Version Jetty/5.1.10 jvm 1| 09-Nov-2006 12:40:54 org.mortbay.util.Container start jvm 1| INFO: Started [EMAIL PROTECTED] jvm 1| [INFO] Application Supervisor is deploying archiva-plexus-application-1.0-SNAPSHOT. jvm 1| [INFO] Application 'archiva' already extracted. jvm 1| [INFO] Deploying application 'archiva' at 'C:\javadev\tools\archiva\1.0.0-SNAPSHOT\apps\archiva'. jvm 1| [INFO] Using application configurator file ..\..\apps\archiva\conf\application.xml. jvm 1| [INFO] Using appDir = ..\..\apps\archiva jvm 1| [INFO] Deploying C:\javadev\tools\archiva\1.0.0-SNAPSHOT\apps\archiva\webapp with context path of / jvm 1| [INFO] Using standard webapp classloader for webapp. jvm 1| [INFO] Deploying appserver 'archiva'. jvm 1| [INFO] Adding HTTP listener on *:8080 jvm 1| 09-Nov-2006 12:40:55 org.mortbay.http.SocketListener start jvm 1| INFO: Started SocketListener on 0.0.0.0:8080 jvm 1| [INFO] Starting Jetty Context / jvm 1| 09-Nov-2006 12:40:55 org.mortbay.util.FileResource jvm 1| INFO: Checking Resource aliases jvm 1| 09-Nov-2006 12:40:55 org.mortbay.xml.XmlParser jvm 1| WARNING: Schema validation may not be supported jvm 1| 09-Nov-2006 12:40:55 org.mortbay.util.Container start jvm 1| INFO: Started [EMAIL PROTECTED] jvm 1| 09-Nov-2006 12:40:55 org.mortbay.jetty.servlet.ServletHandler$Context log jvm 1| INFO: Loading plexus context properties from: '/WEB-INF/plexus.properties' jvm 1| 09-Nov-2006 12:40:55 org.mortbay.jetty.servlet.ServletHandler$Context log jvm 1| INFO: Could not load plexus context properties from: '/WEB-INF/plexus.properties' jvm 1| 2006-11-09 12:40:56,047 [WrapperSimpleAppMain] INFO PlexusContainer- Loading on start [role]: [ org.apache.maven.archiva.scheduler.RepositoryTaskScheduler] jvm 1| 2006-11-09 12:40:56,312 [WrapperSimpleAppMain] INFO RAMJobStore- RAMJobStore initialized. jvm 1| 2006-11-09 12:40:56,312 [WrapperSimpleAppMain] INFO StdSchedulerFactory- Quartz scheduler 'defaultScheduler' initialized from an externally provided properties instance. jvm 1| 2006-11-09 12:40:56,312 [WrapperSimpleAppMain] INFO StdSchedulerFactory- Quartz scheduler version: 1.4.5 jvm 1| 2006-11-09 12:40:56,312 [WrapperSimpleAppMain] INFO QuartzS
Exception while registering Interceptor class pssForceAdminUserInterceptor
Hello, I've followed the archiva installation instruction as described on: http://maven.apache.org/archiva/guides/getting-started/index.html However I keep getting the same errors over and over. The first problem I encountered was when running plexus.bat (I'm on Windows XP), which resulted in: -> Error 500 Unable to compile class for JSP I figured out quite quickly I had to add tools.jar to %archiva_home%\core, which solves that problem. Remark (when using %archiva_home%\bin\win32\run.bat I don't need the tools.jar). With both run.bat and plexus.bat (and also installed with tomcat) I always get the following stacktrace: Error 404 Caught Exception while registering Interceptor class pssForceAdminUserInterceptor HTTP ERROR: 404 Caught Exception while registering Interceptor class pssForceAdminUserInterceptor RequestURI=/index.action This results in an enormous log file (see bottom). The cause of this all seems to be: Caused by: org.codehaus.plexus.component.composition.CompositionException: Component Composition failed. No field of name: 'config' exists in component: role: ' org.codehaus.plexus.security.policy.UserSecurityPolicy', implementation: ' org.codehaus.plexus.security.policy.DefaultUserSecurityPolicy', role hint: 'default' How can I fix this? I already cleaned my local repository, but I got the same exception again. Any help would be appreciated. Thanks, Erik C:\javadev\tools\archiva\1.0.0-SNAPSHOT\bin\win32>run.bat wrapper | --> Wrapper Started as Console wrapper | Launching a JVM... jvm 1| Wrapper (Version 3.1.2) http://wrapper.tanukisoftware.org jvm 1| jvm 1| [INFO] Loading on start [role,roleHint]: [ org.codehaus.plexus.naming.Naming,dataSources] jvm 1| [INFO] Services will be deployed in: '..\..\services'. jvm 1| [INFO] Applications will be deployed in: '..\..\apps'. jvm 1| [INFO] Service Supervisor is deploying plexus-appserver-service-jetty-2.0-alpha-3. jvm 1| [INFO] Removing old service. jvm 1| [INFO] Loading on start [role,roleHint]: [ org.codehaus.plexus.appserver.service.PlexusService,jetty] jvm 1| 09-Nov-2006 12:40:54 org.mortbay.http.HttpServer doStart jvm 1| INFO: Version Jetty/5.1.10 jvm 1| 09-Nov-2006 12:40:54 org.mortbay.util.Container start jvm 1| INFO: Started [EMAIL PROTECTED] jvm 1| [INFO] Application Supervisor is deploying archiva-plexus-application-1.0-SNAPSHOT. jvm 1| [INFO] Application 'archiva' already extracted. jvm 1| [INFO] Deploying application 'archiva' at 'C:\javadev\tools\archiva\1.0.0-SNAPSHOT\apps\archiva'. jvm 1| [INFO] Using application configurator file ..\..\apps\archiva\conf\application.xml. jvm 1| [INFO] Using appDir = ..\..\apps\archiva jvm 1| [INFO] Deploying C:\javadev\tools\archiva\1.0.0-SNAPSHOT\apps\archiva\webapp with context path of / jvm 1| [INFO] Using standard webapp classloader for webapp. jvm 1| [INFO] Deploying appserver 'archiva'. jvm 1| [INFO] Adding HTTP listener on *:8080 jvm 1| 09-Nov-2006 12:40:55 org.mortbay.http.SocketListener start jvm 1| INFO: Started SocketListener on 0.0.0.0:8080 jvm 1| [INFO] Starting Jetty Context / jvm 1| 09-Nov-2006 12:40:55 org.mortbay.util.FileResource jvm 1| INFO: Checking Resource aliases jvm 1| 09-Nov-2006 12:40:55 org.mortbay.xml.XmlParser jvm 1| WARNING: Schema validation may not be supported jvm 1| 09-Nov-2006 12:40:55 org.mortbay.util.Container start jvm 1| INFO: Started [EMAIL PROTECTED] jvm 1| 09-Nov-2006 12:40:55 org.mortbay.jetty.servlet.ServletHandler$Context log jvm 1| INFO: Loading plexus context properties from: '/WEB-INF/plexus.properties' jvm 1| 09-Nov-2006 12:40:55 org.mortbay.jetty.servlet.ServletHandler$Context log jvm 1| INFO: Could not load plexus context properties from: '/WEB-INF/plexus.properties' jvm 1| 2006-11-09 12:40:56,047 [WrapperSimpleAppMain] INFO PlexusContainer- Loading on start [role]: [ org.apache.maven.archiva.scheduler.RepositoryTaskScheduler] jvm 1| 2006-11-09 12:40:56,312 [WrapperSimpleAppMain] INFO RAMJobStore- RAMJobStore initialized. jvm 1| 2006-11-09 12:40:56,312 [WrapperSimpleAppMain] INFO StdSchedulerFactory- Quartz scheduler 'defaultScheduler' initialized from an externally provided properties instance. jvm 1| 2006-11-09 12:40:56,312 [WrapperSimpleAppMain] INFO StdSchedulerFactory- Quartz scheduler version: 1.4.5 jvm 1| 2006-11-09 12:40:56,312 [WrapperSimpleAppMain] INFO QuartzScheduler- Scheduler defaultScheduler_$_NON_CLUSTERED started. jvm 1| 2006-11-09 12:40:56,750 [WrapperSimpleAppMain] WARN ConfigurationStore - Configuration file: C:\Documents and Settings\mfr\.m2\archiva.xml not found. Using defaults. jvm 1| 2006-11-09 12:40:56,750 [WrapperSimpleAppMain] INFO RepositoryTaskScheduler- Not scheduling indexer - index path is not configured jvm 1| 2006-11-09 12:40:56,750 [Wrapp
