You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2007/04/10 18:48:46 UTC

[jira] Created: (MASSEMBLY-196) use of repository assembly is no longer working

use of repository assembly is no longer working
-----------------------------------------------

                 Key: MASSEMBLY-196
                 URL: http://jira.codehaus.org/browse/MASSEMBLY-196
             Project: Maven 2.x Assembly Plugin
          Issue Type: Bug
    Affects Versions: 2.2-beta-1
            Reporter: Brett Porter


I have the following that works in 2.1:

  <repositories>
    <repository>
      <outputDirectory>repository/releases</outputDirectory>
      <includeMetadata>true</includeMetadata>
      <groupVersionAlignments>
        <groupVersionAlignment>
          <id>org.apache.maven</id>
          <version>2.0.5</version>
          <excludes>
            <exclude>maven-plugin-surrogate-parent</exclude>
            <exclude>maven-archetype</exclude>
            <exclude>maven-archetype-core</exclude>
            <exclude>maven-archiver</exclude>
            <exclude>maven-parent</exclude>
            <exclude>maven-jxr</exclude>
            <exclude>maven-plugin-tools-java</exclude>
            <exclude>maven-plugin-tools-beanshell</exclude>
            <exclude>maven-plugin-tools-api</exclude>
            <exclude>maven-plugin-tools</exclude>
          </excludes>
        </groupVersionAlignment>
      </groupVersionAlignments>
    </repository>
  </repositories>

However, in 2.2-beta-1 it results in an empty directory being created in the assembly instead of copying the repository contents.

-- 
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

        

Re: [jira] Created: (MASSEMBLY-196) use of repository assembly is no longer working

Posted by John Casey <ca...@gmail.com>.
looks good, I'll take a look at it.

Thanks, Brett.

-john

On 4/10/07, Brett Porter (JIRA) <ji...@codehaus.org> wrote:
>
> use of repository assembly is no longer working
> -----------------------------------------------
>
>                  Key: MASSEMBLY-196
>                  URL: http://jira.codehaus.org/browse/MASSEMBLY-196
>              Project: Maven 2.x Assembly Plugin
>           Issue Type: Bug
>     Affects Versions: 2.2-beta-1
>             Reporter: Brett Porter
>
>
> I have the following that works in 2.1:
>
>   <repositories>
>     <repository>
>       <outputDirectory>repository/releases</outputDirectory>
>       <includeMetadata>true</includeMetadata>
>       <groupVersionAlignments>
>         <groupVersionAlignment>
>           <id>org.apache.maven</id>
>           <version>2.0.5</version>
>           <excludes>
>             <exclude>maven-plugin-surrogate-parent</exclude>
>             <exclude>maven-archetype</exclude>
>             <exclude>maven-archetype-core</exclude>
>             <exclude>maven-archiver</exclude>
>             <exclude>maven-parent</exclude>
>             <exclude>maven-jxr</exclude>
>             <exclude>maven-plugin-tools-java</exclude>
>             <exclude>maven-plugin-tools-beanshell</exclude>
>             <exclude>maven-plugin-tools-api</exclude>
>             <exclude>maven-plugin-tools</exclude>
>           </excludes>
>         </groupVersionAlignment>
>       </groupVersionAlignments>
>     </repository>
>   </repositories>
>
> However, in 2.2-beta-1 it results in an empty directory being created in
> the assembly instead of copying the repository contents.
>
> --
> 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] Updated: (MASSEMBLY-196) use of repository assembly is no longer working

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MASSEMBLY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey updated MASSEMBLY-196:
---------------------------------

    Fix Version/s: 2.2-beta-2

we're cleaning up some other things related to repo's, so we should be able to knock this one out.

> use of repository assembly is no longer working
> -----------------------------------------------
>
>                 Key: MASSEMBLY-196
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-196
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-1
>            Reporter: Brett Porter
>             Fix For: 2.2-beta-2
>
>
> I have the following that works in 2.1:
>   <repositories>
>     <repository>
>       <outputDirectory>repository/releases</outputDirectory>
>       <includeMetadata>true</includeMetadata>
>       <groupVersionAlignments>
>         <groupVersionAlignment>
>           <id>org.apache.maven</id>
>           <version>2.0.5</version>
>           <excludes>
>             <exclude>maven-plugin-surrogate-parent</exclude>
>             <exclude>maven-archetype</exclude>
>             <exclude>maven-archetype-core</exclude>
>             <exclude>maven-archiver</exclude>
>             <exclude>maven-parent</exclude>
>             <exclude>maven-jxr</exclude>
>             <exclude>maven-plugin-tools-java</exclude>
>             <exclude>maven-plugin-tools-beanshell</exclude>
>             <exclude>maven-plugin-tools-api</exclude>
>             <exclude>maven-plugin-tools</exclude>
>           </excludes>
>         </groupVersionAlignment>
>       </groupVersionAlignments>
>     </repository>
>   </repositories>
> However, in 2.2-beta-1 it results in an empty directory being created in the assembly instead of copying the repository contents.

-- 
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] (MASSEMBLY-196) use of repository assembly is no longer working

Posted by "David Bernard (JIRA)" <ji...@codehaus.org>.
    [ https://jira.codehaus.org/browse/MASSEMBLY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=318137#comment-318137 ] 

David Bernard commented on MASSEMBLY-196:
-----------------------------------------

Same issue with maven 3.0.4 and maven-assembly-plugin 2.4

The jar of the project is missing (pom.xml is present) from the generated repository.
It's a crappy but I used the following work arround :

{code:xml}
<!-- WORKAROUND because <repository> doesn't copy project's artifact (jar), only the pom -->
		<fileSet>
			<directory>${project.build.directory}</directory>
			<outputDirectory>/lib/net/alchim31/runner/${project.artifactId}/${project.version}</outputDirectory>
			<includes>
				<include>${project.build.finalName}.jar</include>
			</includes>
		</fileSet>
	</fileSets>
	<repositories>
		<repository>
			<outputDirectory>/lib</outputDirectory>
			<includeMetadata>true</includeMetadata>
			<scope>runtime</scope>
		</repository>
	</repositories>
{code}
                
> use of repository assembly is no longer working
> -----------------------------------------------
>
>                 Key: MASSEMBLY-196
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-196
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-1
>            Reporter: Brett Porter
>            Assignee: John Casey
>             Fix For: 2.2-beta-3
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I have the following that works in 2.1:
>   <repositories>
>     <repository>
>       <outputDirectory>repository/releases</outputDirectory>
>       <includeMetadata>true</includeMetadata>
>       <groupVersionAlignments>
>         <groupVersionAlignment>
>           <id>org.apache.maven</id>
>           <version>2.0.5</version>
>           <excludes>
>             <exclude>maven-plugin-surrogate-parent</exclude>
>             <exclude>maven-archetype</exclude>
>             <exclude>maven-archetype-core</exclude>
>             <exclude>maven-archiver</exclude>
>             <exclude>maven-parent</exclude>
>             <exclude>maven-jxr</exclude>
>             <exclude>maven-plugin-tools-java</exclude>
>             <exclude>maven-plugin-tools-beanshell</exclude>
>             <exclude>maven-plugin-tools-api</exclude>
>             <exclude>maven-plugin-tools</exclude>
>           </excludes>
>         </groupVersionAlignment>
>       </groupVersionAlignments>
>     </repository>
>   </repositories>
> However, in 2.2-beta-1 it results in an empty directory being created in the assembly instead of copying the repository contents.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Work started: (MASSEMBLY-196) use of repository assembly is no longer working

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MASSEMBLY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on MASSEMBLY-196 started by John Casey.

> use of repository assembly is no longer working
> -----------------------------------------------
>
>                 Key: MASSEMBLY-196
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-196
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-1
>            Reporter: Brett Porter
>            Assignee: John Casey
>             Fix For: 2.2-beta-3
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I have the following that works in 2.1:
>   <repositories>
>     <repository>
>       <outputDirectory>repository/releases</outputDirectory>
>       <includeMetadata>true</includeMetadata>
>       <groupVersionAlignments>
>         <groupVersionAlignment>
>           <id>org.apache.maven</id>
>           <version>2.0.5</version>
>           <excludes>
>             <exclude>maven-plugin-surrogate-parent</exclude>
>             <exclude>maven-archetype</exclude>
>             <exclude>maven-archetype-core</exclude>
>             <exclude>maven-archiver</exclude>
>             <exclude>maven-parent</exclude>
>             <exclude>maven-jxr</exclude>
>             <exclude>maven-plugin-tools-java</exclude>
>             <exclude>maven-plugin-tools-beanshell</exclude>
>             <exclude>maven-plugin-tools-api</exclude>
>             <exclude>maven-plugin-tools</exclude>
>           </excludes>
>         </groupVersionAlignment>
>       </groupVersionAlignments>
>     </repository>
>   </repositories>
> However, in 2.2-beta-1 it results in an empty directory being created in the assembly instead of copying the repository contents.

-- 
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] Updated: (MASSEMBLY-196) use of repository assembly is no longer working

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MASSEMBLY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey updated MASSEMBLY-196:
---------------------------------

              Assignee: John Casey
    Remaining Estimate: 0 minutes
     Original Estimate: 0 minutes

> use of repository assembly is no longer working
> -----------------------------------------------
>
>                 Key: MASSEMBLY-196
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-196
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-1
>            Reporter: Brett Porter
>            Assignee: John Casey
>             Fix For: 2.2-beta-3
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I have the following that works in 2.1:
>   <repositories>
>     <repository>
>       <outputDirectory>repository/releases</outputDirectory>
>       <includeMetadata>true</includeMetadata>
>       <groupVersionAlignments>
>         <groupVersionAlignment>
>           <id>org.apache.maven</id>
>           <version>2.0.5</version>
>           <excludes>
>             <exclude>maven-plugin-surrogate-parent</exclude>
>             <exclude>maven-archetype</exclude>
>             <exclude>maven-archetype-core</exclude>
>             <exclude>maven-archiver</exclude>
>             <exclude>maven-parent</exclude>
>             <exclude>maven-jxr</exclude>
>             <exclude>maven-plugin-tools-java</exclude>
>             <exclude>maven-plugin-tools-beanshell</exclude>
>             <exclude>maven-plugin-tools-api</exclude>
>             <exclude>maven-plugin-tools</exclude>
>           </excludes>
>         </groupVersionAlignment>
>       </groupVersionAlignments>
>     </repository>
>   </repositories>
> However, in 2.2-beta-1 it results in an empty directory being created in the assembly instead of copying the repository contents.

-- 
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: (MASSEMBLY-196) use of repository assembly is no longer working

Posted by "Martin Vysny (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MASSEMBLY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115772 ] 

Martin Vysny commented on MASSEMBLY-196:
----------------------------------------

Hi guys, when do you plan to resolve this issue? Having this simple config file (taken from the assembly site repository example):
{noformat}
<assembly>
	<id>sdk</id>
	<formats>
		<format>zip</format>
	</formats>

	<includeBaseDirectory>false</includeBaseDirectory>

	<repositories>
		<repository>
			<includeMetadata>true</includeMetadata>
			<outputDirectory>maven2</outputDirectory>
		</repository>
	</repositories>
</assembly>
{noformat}
only the {{maven2}} directory is created, but it is empty, no dependencies are stored.

> use of repository assembly is no longer working
> -----------------------------------------------
>
>                 Key: MASSEMBLY-196
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-196
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-1
>            Reporter: Brett Porter
>             Fix For: 2.2-beta-2
>
>
> I have the following that works in 2.1:
>   <repositories>
>     <repository>
>       <outputDirectory>repository/releases</outputDirectory>
>       <includeMetadata>true</includeMetadata>
>       <groupVersionAlignments>
>         <groupVersionAlignment>
>           <id>org.apache.maven</id>
>           <version>2.0.5</version>
>           <excludes>
>             <exclude>maven-plugin-surrogate-parent</exclude>
>             <exclude>maven-archetype</exclude>
>             <exclude>maven-archetype-core</exclude>
>             <exclude>maven-archiver</exclude>
>             <exclude>maven-parent</exclude>
>             <exclude>maven-jxr</exclude>
>             <exclude>maven-plugin-tools-java</exclude>
>             <exclude>maven-plugin-tools-beanshell</exclude>
>             <exclude>maven-plugin-tools-api</exclude>
>             <exclude>maven-plugin-tools</exclude>
>           </excludes>
>         </groupVersionAlignment>
>       </groupVersionAlignments>
>     </repository>
>   </repositories>
> However, in 2.2-beta-1 it results in an empty directory being created in the assembly instead of copying the repository contents.

-- 
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: (MASSEMBLY-196) use of repository assembly is no longer working

Posted by "Luke Nezda (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MASSEMBLY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=165658#action_165658 ] 

Luke Nezda commented on MASSEMBLY-196:
--------------------------------------

I second Martin's comment, if you copy-paste the example from http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/using-repositories.html, it doesn't produce the output it indicates it should.  Primary element that is missing from the resulting repository seems to be the project artifact itself.  If you add an apropos explicit {{<dependencySet>}} for this artifact, it doesn't copy it (e.g., the jar) along side the metadata (pom, sha1, md5), but rather to the base dir, so it doesn't result in a valid repository.  I tried to run the integration test ({{mvn integration-test}} right?), but I don't follow the setup well enough to verify my own expectations of it.  I'm willing to help fix the documentation and/or code and/or provide a test case.  I'm using Maven 2.0.9, maven-assembly-plugin 2.2-beta-3.  Results definitely "improved" from beta1 to beta3, but still doesn't seem quite right.

> use of repository assembly is no longer working
> -----------------------------------------------
>
>                 Key: MASSEMBLY-196
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-196
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-1
>            Reporter: Brett Porter
>            Assignee: John Casey
>             Fix For: 2.2-beta-3
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I have the following that works in 2.1:
>   <repositories>
>     <repository>
>       <outputDirectory>repository/releases</outputDirectory>
>       <includeMetadata>true</includeMetadata>
>       <groupVersionAlignments>
>         <groupVersionAlignment>
>           <id>org.apache.maven</id>
>           <version>2.0.5</version>
>           <excludes>
>             <exclude>maven-plugin-surrogate-parent</exclude>
>             <exclude>maven-archetype</exclude>
>             <exclude>maven-archetype-core</exclude>
>             <exclude>maven-archiver</exclude>
>             <exclude>maven-parent</exclude>
>             <exclude>maven-jxr</exclude>
>             <exclude>maven-plugin-tools-java</exclude>
>             <exclude>maven-plugin-tools-beanshell</exclude>
>             <exclude>maven-plugin-tools-api</exclude>
>             <exclude>maven-plugin-tools</exclude>
>           </excludes>
>         </groupVersionAlignment>
>       </groupVersionAlignments>
>     </repository>
>   </repositories>
> However, in 2.2-beta-1 it results in an empty directory being created in the assembly instead of copying the repository contents.

-- 
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] Closed: (MASSEMBLY-196) use of repository assembly is no longer working

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MASSEMBLY-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MASSEMBLY-196.
--------------------------------

    Resolution: Cannot Reproduce

I've introduced an integration test at:

http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-assembly-plugin/src/it/projects/repositories/massembly-196/

and I've been unable to reproduce the problem. If you can reproduce the problem, please let me know why my integration test is wrong, and reopen this issue.

> use of repository assembly is no longer working
> -----------------------------------------------
>
>                 Key: MASSEMBLY-196
>                 URL: http://jira.codehaus.org/browse/MASSEMBLY-196
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2-beta-1
>            Reporter: Brett Porter
>            Assignee: John Casey
>             Fix For: 2.2-beta-3
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> I have the following that works in 2.1:
>   <repositories>
>     <repository>
>       <outputDirectory>repository/releases</outputDirectory>
>       <includeMetadata>true</includeMetadata>
>       <groupVersionAlignments>
>         <groupVersionAlignment>
>           <id>org.apache.maven</id>
>           <version>2.0.5</version>
>           <excludes>
>             <exclude>maven-plugin-surrogate-parent</exclude>
>             <exclude>maven-archetype</exclude>
>             <exclude>maven-archetype-core</exclude>
>             <exclude>maven-archiver</exclude>
>             <exclude>maven-parent</exclude>
>             <exclude>maven-jxr</exclude>
>             <exclude>maven-plugin-tools-java</exclude>
>             <exclude>maven-plugin-tools-beanshell</exclude>
>             <exclude>maven-plugin-tools-api</exclude>
>             <exclude>maven-plugin-tools</exclude>
>           </excludes>
>         </groupVersionAlignment>
>       </groupVersionAlignments>
>     </repository>
>   </repositories>
> However, in 2.2-beta-1 it results in an empty directory being created in the assembly instead of copying the repository contents.

-- 
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