META-INF/maven/org.apache.maven.core.test/test-lifecycle-and-artifactHandler/pom.xml 4.0.0 org.apache.maven.core.test test-lifecycle-and-artifactHandler jar 1 test-lifecycle-and-artifactHandler maven-assembly-plugin 2.2-beta-2-SNAPSHOT repo-assembly package single repo.xml test-extension true ${pom.basedir}/../../resources/org/apache/maven/extension true dummy file:///tmp/dummy-repo META-INF/maven/org.apache.maven.core.test/test-lifecycle-and-artifactHandler/pom.properties #Generated by Maven #Thu...

Guillaume Nodet <******@****.***> 1664700085 +0200

Guillaume Nodet <******@****.***> 1664700085 +0200

  <modelVersion>4.0.0</modelVersion>
  <groupId>org.apache.maven.core.test</groupId>
  <artifactId>test-lifecycle-and-artifactHandler</artifactId>
  <packaging>jar</packaging>
  <version>1</version>
  <name>test-lifecycle-and-artifactHandler</name>

  <build>
    <plugins>
      <plugin>
        <artifactId>maven-assembly-plugin</artifactId>
        <version>2.2-beta-2-SNAPSHOT</version>

 could encapsulate everything we need about the project in the POM including
 plugin parameters and anything else.

 We once had a document that Vincent and I agreed upon and I was about to
 implement it and then I disappeared for 8 months so it never came to pass.

 So I guess it's important to figure out what people are using properties
 files for and see if we can't incorporate it all into the POM. Or if we do

* having packed or unpacked plugins, and positioning resources if necessary
* maven can work out of the classloader, nexus plugins probably couldn't give the js and image resources

h3. Other issues

We need to look at Maven, and Nexus as use cases and figure out what each of them needs to be able to do

* now what is really the difference between this and loading a component in plexus

         * Issue is "user actionable", is internal to the currently built project and is reparable from scope of it
         * by doing some change (for example by changing POM and fixing the problematic plugin configuration).
         */
        INTERNAL,

        /**
         * Issue (present in some plugin) is "developer actionable" (of given plugin, by changing code and doing

  provided both in terms of static expressions that are just looked up, and
  in terms of user-provided configuration from properties or the POM).
  If these mojos are to be first-class components, the configuration from these
  various sources must be consolidated and injected using the container.

  Currently, mojo configuration is done externally to the container, in the

Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION 1. Definitions. "License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. "Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. "Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are...

        // Alright, here's the justification for all the regexp wizardry below...
        //
        // Continuum and other server-like apps may need to locate the user-level and
        // global-level settings somewhere other than ${user.home} and ${maven.home},
        // respectively. Using a simple replacement of these patterns will allow them