[jira] Commented: (MAVENUPLOAD-2463) Synchronize Spring ME Maven Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=176768#action_176768 ] Wilfred Springer commented on MAVENUPLOAD-2463: --- BTW, this is the link to the project's page, and here's a list of the contributors; just to prove that I am involved. Synchronize Spring ME Maven Repository -- Key: MAVENUPLOAD-2463 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2463 Project: Maven Upload Requests Issue Type: Wish Reporter: Wilfred Springer Please synchronize this repository with Spring ME releases with the central Maven repository. me.springframework,mavens...@web.sourceforge.net:/home/groups/s/sp/springme/htdocs/repository,rsync_ssh,Wilfred Springer,wilf...@flotsam.nl,, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Issue Comment Edited: (MAVENUPLOAD-2463) Synchronize Spring ME Maven Repository
[ http://jira.codehaus.org/browse/MAVENUPLOAD-2463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=176768#action_176768 ] Wilfred Springer edited comment on MAVENUPLOAD-2463 at 5/16/09 1:11 PM: BTW, this is the link to the project's page, and here's a list of the contributors; just to prove that I am involved. http://springframework.me/team-list.html was (Author: springerw): BTW, this is the link to the project's page, and here's a list of the contributors; just to prove that I am involved. Synchronize Spring ME Maven Repository -- Key: MAVENUPLOAD-2463 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2463 Project: Maven Upload Requests Issue Type: Wish Reporter: Wilfred Springer Please synchronize this repository with Spring ME releases with the central Maven repository. me.springframework,mavens...@web.sourceforge.net:/home/groups/s/sp/springme/htdocs/repository,rsync_ssh,Wilfred Springer,wilf...@flotsam.nl,, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-2463) Synchronize Spring ME Maven Repository
Synchronize Spring ME Maven Repository -- Key: MAVENUPLOAD-2463 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2463 Project: Maven Upload Requests Issue Type: Wish Reporter: Wilfred Springer Please synchronize this repository with Spring ME releases with the central Maven repository. me.springframework,mavens...@web.sourceforge.net:/home/groups/s/sp/springme/htdocs/repository,rsync_ssh,Wilfred Springer,wilf...@flotsam.nl,, -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1870) Sync docbkx-tools.sourceforge.net/repository
Sync docbkx-tools.sourceforge.net/repository Key: MAVENUPLOAD-1870 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1870 Project: maven-upload-requests Issue Type: Task Reporter: Wilfred Springer Attachments: com.agilejava.docbkx.sh Please synchronize the docbkx-tools.sourceforge.net/repository with the central maven repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MAVENUPLOAD-1743) Sync blammo.sourceforge.net/repository
Sync blammo.sourceforge.net/repository -- Key: MAVENUPLOAD-1743 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1743 Project: maven-upload-requests Issue Type: Task Reporter: Wilfred Springer Attachments: com.agilejava.blammo.sh Please synchronize the blammo.sourceforge.net/repository with the central maven repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-509) Ability to process scheduled builds the same as forced builds.
[ http://jira.codehaus.org/browse/CONTINUUM-509?page=comments#action_78207 ] Wilfred Springer commented on CONTINUUM-509: +1 I would also love to have the ability to force the site build. In fact, it seems that most of us want this because we either run a different lifecycle (site build vs. software build) or let it run up to different phases (test vs. integration-test). IMHO, it makes sense that Continuum would be able to understand that having a build that ran up to the test phase didn't include the integration-test phase; as a result, Continuum should be able to recognize that a midnight integration test still requires the build to run, even if the test build already ran and there were no changes in the repository. The same applies for the difference between a site build and a software build. You would expect Continuum would be able to see the difference between the different lifecycles. Because of that, it should simply be running the nightly site build, even if the software build already completed successfully during the day. Ability to process scheduled builds the same as forced builds. -- Key: CONTINUUM-509 URL: http://jira.codehaus.org/browse/CONTINUUM-509 Project: Continuum Issue Type: Improvement Components: Core system Affects Versions: 1.0.2 Reporter: Shinobu Kawai Priority: Minor Fix For: 1.1 It would be great if you could configure a build schedule to act like a forced build on the scheduled build. The use case for this is when you have two build definitions: - One will be set to default for a forced, light build. For example, install the artifact. - Another will be set to a scheduled, heavy build. For example, deploy the artifact and the project site. If the default build is triggered, the other build will be skipped since nothing has been updated since the forced build. And we do not want to do heavy stuff in the default build. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MRM-183) Archiva Plexus Runtime works only when copying tools.jar to the core directory
[ http://jira.codehaus.org/browse/MRM-183?page=comments#action_75778 ] Wilfred Springer commented on MRM-183: -- I think I was running plexus.sh directly. Archiva Plexus Runtime works only when copying tools.jar to the core directory -- Key: MRM-183 URL: http://jira.codehaus.org/browse/MRM-183 Project: Archiva Issue Type: Bug Components: web application Reporter: Wilfred Springer Archiva Plexus Runtime works only when copying tools.jar to the core directory. Othwerwise it will complain about the fact that is unable to find the compiler classes from the JDK, and suggests to set JAVA_HOME. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-183) Archiva Plexus Runtime works only when copying tools.jar to the core directory
Archiva Plexus Runtime works only when copying tools.jar to the core directory -- Key: MRM-183 URL: http://jira.codehaus.org/browse/MRM-183 Project: Archiva Issue Type: Bug Components: web application Reporter: Wilfred Springer Archiva Plexus Runtime works only when copying tools.jar to the core directory. Othwerwise it will complain about the fact that is unable to find the compiler classes from the JDK, and suggests to set JAVA_HOME. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-181) Codehaus Snapshots Repository missing in POM
Codehaus Snapshots Repository missing in POM Key: MRM-181 URL: http://jira.codehaus.org/browse/MRM-181 Project: Archiva Issue Type: Bug Affects Versions: 1.0 Environment: Linux, Java 1.5.* Reporter: Wilfred Springer Attachments: repository.patch The Codehaus Snapshots Repository is missing from the root POM. As a result, the build fails to locate certain Plexus artifacts. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (MRM-182) Archiva-plexus-runtime doesn't run
Archiva-plexus-runtime doesn't run -- Key: MRM-182 URL: http://jira.codehaus.org/browse/MRM-182 Project: Archiva Issue Type: Bug Environment: Linux, Java 1.5 Reporter: Wilfred Springer Priority: Critical Without changing any of the configuration files, I get the log included belog. Fiddling with the database configuration doesn't really help at all. Running jetty:run in archiva-webapp gives a java.lang.NoSuchMethodError: org.codehaus.plexus.DefaultPlexusContainer.init(Ljava/lang/String;Ljava/lang/ClassLoader;Ljava/io/Reader;Ljava/util/Map;)V Using PLEXUS_HOME: /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva Using PLEXUS_CONF: /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/conf Using PLEXUS_TMPDIR: /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/temp Using JAVA_HOME: /usr/java/jdk1.5.0_06 [INFO] Services will be deployed in: '/home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/services'. [INFO] Applications will be deployed in: '/home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps'. [INFO] Service Supervisor is deploying plexus-appserver-service-jetty-2.0-alpha-3-SNAPSHOT. [INFO] Loading on start [role,roleHint]: [org.codehaus.plexus.appserver.service.PlexusService,jetty] Sep 21, 2006 9:44:37 PM org.mortbay.http.HttpServer doStart INFO: Version Jetty/5.1.10 Sep 21, 2006 9:44:37 PM org.mortbay.util.Container start INFO: Started [EMAIL PROTECTED] [INFO] Application Supervisor is deploying archiva-plexus-application-1.0-SNAPSHOT. [INFO] Extracting /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva-plexus-application-1.0-SNAPSHOT.jar to '/home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva'. [INFO] Deploying application 'archiva' at '/home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva'. [INFO] Using application configurator file /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva/conf/application.xml. [INFO] Using appDir = /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva [INFO] Deploying /home/wilfred/workspace/maven-repository-manager/archiva-plexus-runtime/target/archiva/apps/archiva/webapp with context path of / [INFO] Using standard webapp classloader for webapp. [INFO] Deploying appserver 'archiva'. [INFO] Adding HTTP listener on *:8080 Sep 21, 2006 9:44:40 PM org.mortbay.http.SocketListener start INFO: Started SocketListener on 0.0.0.0:8080 [INFO] Starting Jetty Context / Sep 21, 2006 9:44:41 PM org.mortbay.util.FileResource clinit INFO: Checking Resource aliases Sep 21, 2006 9:44:41 PM org.mortbay.util.Container start INFO: Started [EMAIL PROTECTED] Sep 21, 2006 9:44:41 PM org.mortbay.jetty.servlet.ServletHandler$Context log INFO: Loading plexus context properties from: '/WEB-INF/plexus.properties' Sep 21, 2006 9:44:42 PM org.mortbay.jetty.servlet.ServletHandler$Context log INFO: Could not load plexus context properties from: '/WEB-INF/plexus.properties' 2006-09-21 21:44:42,447 [main] INFO PlexusContainer- Loading on start [role]: [org.apache.maven.archiva.scheduler.RepositoryTaskScheduler] 2006-09-21 21:44:42,633 [main] INFO RAMJobStore- RAMJobStore initialized. 2006-09-21 21:44:42,634 [main] INFO StdSchedulerFactory- Quartz scheduler 'defaultScheduler' initialized from an externally provided properties instance. 2006-09-21 21:44:42,634 [main] INFO StdSchedulerFactory- Quartz scheduler version: 1.4.5 2006-09-21 21:44:42,634 [main] INFO QuartzScheduler- Scheduler defaultScheduler_$_NON_CLUSTERED started. 2006-09-21 21:44:43,085 [main] WARN ConfigurationStore - Configuration file: /home/wilfred/.m2/archiva.xml not found. Using defaults. 2006-09-21 21:44:43,086 [main] INFO RepositoryTaskScheduler- Not scheduling indexer - index path is not configured 2006-09-21 21:44:43,086 [main] INFO PlexusContainer- Loading on start [role]: [org.apache.maven.archiva.web.ArchivaSecurityDefaults] Sep 21, 2006 9:44:43 PM org.mortbay.jetty.servlet.ServletHandler$Context log INFO: ** FATAL ERROR STARTING UP PLEXUS-WEBWORK INTEGRATION ** Looks like the Plexus listener was not configured for your web app! You need to add the following to web.xml: listener listener-classorg.codehaus.plexus.xwork.PlexusLifecycleListener/listener-class /listener [ERROR] Error while deploying appserver archiva-plexus-application-1.0-SNAPSHOT.jar. org.codehaus.plexus.appserver.ApplicationServerException:
[jira] Created: (MAVENUPLOAD-1090) Upload of Maven Docbkx Plugin
Upload of Maven Docbkx Plugin - Key: MAVENUPLOAD-1090 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1090 Project: maven-upload-requests Issue Type: Task Reporter: Wilfred Springer http://www.agilejava.com/downloads/docbkx-builder-maven-plugin-0.8-bundle.jar http://www.agilejava.com/downloads/docbkx-maven-base-0.8-bundle.jar http://www.agilejava.com/downloads/docbkx-maven-plugin-1.69.1.7-bundle.jar An alternative for the Maven DocBook plugin found at mojo.codehaus.org. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
