Return-Path: Delivered-To: apmail-maven-dev-archive@www.apache.org Received: (qmail 46387 invoked from network); 30 Jun 2006 02:46:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 30 Jun 2006 02:46:06 -0000 Received: (qmail 28991 invoked by uid 500); 30 Jun 2006 02:46:05 -0000 Delivered-To: apmail-maven-dev-archive@maven.apache.org Received: (qmail 28917 invoked by uid 500); 30 Jun 2006 02:46:04 -0000 Mailing-List: contact dev-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Developers List" Reply-To: "Maven Developers List" Delivered-To: mailing list dev@maven.apache.org Received: (qmail 28904 invoked by uid 99); 30 Jun 2006 02:46:04 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jun 2006 19:46:04 -0700 X-ASF-Spam-Status: No, hits=1.0 required=10.0 tests=DNS_FROM_RFC_ABUSE,NO_REAL_NAME X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [63.246.20.114] (HELO 63-246-20-114.contegix.com) (63.246.20.114) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 29 Jun 2006 19:46:01 -0700 Received: (qmail 15464 invoked by uid 89); 30 Jun 2006 02:45:40 -0000 Received: from unknown (HELO codehaus01.managed.contegix.com) (127.0.0.1) by smtp.domain.com with SMTP; 30 Jun 2006 02:45:40 -0000 Message-ID: <86086600.1151635540323.JavaMail.haus-jira@codehaus01.managed.contegix.com> Date: Thu, 29 Jun 2006 21:45:40 -0500 (CDT) From: jira@codehaus.org To: dev@maven.apache.org Subject: [jira] Subscription: Design & Best Practices MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Issue Subscription Filter: Design & Best Practices (37 issues) Subscriber: mavendevlist Key Summary MNG-2184 Possible problem with @aggregator and forked lifecycles http://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques http://jira.codehaus.org/browse/MNG-612 MNG-1508 Need a process-test-classes phase http://jira.codehaus.org/browse/MNG-1508 MNG-1305 Document Maven's own development process http://jira.codehaus.org/browse/MNG-1305 MNG-1950 Ability to introduce new lifecycles phases http://jira.codehaus.org/browse/MNG-1950 MNG-1381 best practices: testing strategies http://jira.codehaus.org/browse/MNG-1381 MNG-474 performance improvement for forked lifecycles http://jira.codehaus.org/browse/MNG-474 MNG-1931 add a reportingManagement section http://jira.codehaus.org/browse/MNG-1931 MNG-1936 pattern: for mojo parameters which have default values in the POM we need standard usage http://jira.codehaus.org/browse/MNG-1936 MNG-2129 generated source repo page is misleading when added to the "general site". http://jira.codehaus.org/browse/MNG-2129 MNG-1563 how to write integration tests http://jira.codehaus.org/browse/MNG-1563 MNG-2125 [doc] when and how to define plugins in a pom http://jira.codehaus.org/browse/MNG-2125 MNG-2381 improved control over the repositories in the POM http://jira.codehaus.org/browse/MNG-2381 MNG-1634 move maven-core-it to integration-tests http://jira.codehaus.org/browse/MNG-1634 MNG-1867 deprecate system scope, analyse other use cases http://jira.codehaus.org/browse/MNG-1867 MNG-939 specify maven settings from command line http://jira.codehaus.org/browse/MNG-939 MNG-367 best practices: multi-user installation http://jira.codehaus.org/browse/MNG-367 MNG-140 refactor maven-artifact http://jira.codehaus.org/browse/MNG-140 MNG-41 best practices: site management http://jira.codehaus.org/browse/MNG-41 MNG-139 server definitions should be reusable http://jira.codehaus.org/browse/MNG-139 MNG-1440 Developer Object Model (DOM) http://jira.codehaus.org/browse/MNG-1440 MNG-657 possible chicken and egg problem with extensions http://jira.codehaus.org/browse/MNG-657 MNG-125 guarded mojo execution http://jira.codehaus.org/browse/MNG-125 MNG-1439 Organization Object Model (OOM) http://jira.codehaus.org/browse/MNG-1439 MNG-905 review clean repo install of m2 for download trimming http://jira.codehaus.org/browse/MNG-905 MNG-1569 Make build process info read-only to mojos, and provide mechanism for explicit out-params for mojos to declare http://jira.codehaus.org/browse/MNG-1569 MNG-868 Use uniform format for and other tags http://jira.codehaus.org/browse/MNG-868 MNG-1885 Uniquely identify modules by module name and version number http://jira.codehaus.org/browse/MNG-1885 MNG-647 Allow Maven 2 to be monitored using JMX. http://jira.codehaus.org/browse/MNG-647 MNG-1441 Starting thinking about a proper distributed repository mechanism a la CPAN http://jira.codehaus.org/browse/MNG-1441 MNG-1463 best practices: plugin inheritance for a multi project build http://jira.codehaus.org/browse/MNG-1463 MNG-1437 How to make additions to the POM and have it be backward/forward compatible http://jira.codehaus.org/browse/MNG-1437 MNG-1468 best practices: version management in multi project builds http://jira.codehaus.org/browse/MNG-1468 MNG-1452 best practices: deployment of aggregate JARs produced by the assembly plug-in http://jira.codehaus.org/browse/MNG-1452 MNG-1425 best practices: the location of configuration files vs resources http://jira.codehaus.org/browse/MNG-1425 MNG-1423 best practices: setting up multi-module build http://jira.codehaus.org/browse/MNG-1423 MNG-416 best practices: multiple profile deployments http://jira.codehaus.org/browse/MNG-416 --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org For additional commands, e-mail: dev-help@maven.apache.org