This is still a problem with the appassembler-maven-plugin.

I've stubled upon this a couple of times before, but have never been able to wrap my head around what the problem really is. This time I finally made som progress - I've got a work-around.

The work-around

You need to add a dependency to maven-dependency-plugin in the project that uses appassembler-maven-plugin, like this:

<build>
    <plugins>
      <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-deploy-plugin</artifactId>
        <version>2.7</version>
        <dependencies>
          <dependency>
            <groupId>org.codehaus.mojo</groupId>
            <artifactId>appassembler-maven-plugin</artifactId>
            <version>1.1.1</version>
          </dependency>
        </dependencies>
      </plugin>
    </plugins>
  </build>

The problem

The appassembler-maven-plugin some way injects a new ArtifactRepositoryLayout as a component into Plexus, namely the FlatRepositoryLayout. I think that this is still there after appassembler-maven-plugin has finished, i.e. it isn't clean up properly (no, I don't know how to do that). When maven-deploy-plugin runs after this it finds the reference to FlatRepositoryLayout, but it has no such class in its class path, resulting in the error message:

[INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-deploy-plugin:2.7:deploy': Unable to find the mojo 'deploy' (or one of its required components) in the plugin 'org.apache.maven.plugins:maven-deploy-plugin'
Component descriptor cannot be found in the component repository: org.apache.maven.artifact.repository.layout.ArtifactRepositoryLayoutflat.

By adding appassembler-maven-plugin as a dependency for deploy-maven-plugin that class is put into its class path and it can go about doing its business.

The solution

We need the help of someone who knows his or her way around Plexus components to be able to fix this properly. Anyone?

Change By: Dennis Lundberg (17/Jul/12 2:43 PM)
Status: Closed Reopened
Resolution: Cannot Reproduce
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to