maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@codehaus.org>
Subject [jira] (MASSEMBLY-369) Assembly plugin process it's commands from it's pom (in addition to an external file)
Date Fri, 02 Nov 2012 10:57:13 GMT

     [ https://jira.codehaus.org/browse/MASSEMBLY-369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Dennis Lundberg updated MASSEMBLY-369:
--------------------------------------

    Description: 
Currently the plugin requires an external file to get it's configuration from.
Can we simply not have this expressed inside the pom itself?

What we currently have:
{code:xml}
            <plugin>
                <artifactId>maven-assembly-plugin</artifactId>
                <configuration>
                    <descriptors>
                        <descriptor>assembly.xml</descriptor>
                    </descriptors>
                </configuration>
                <executions>
                    <execution>
                        <id>make-assembly</id>
                        <phase>package</phase>
                        <goals>
                            <goal>attached</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
{code}

and assembly.xml:

{code:xml}
<assembly>
    <id></id>
    <formats>
        <format>zip</format>
    </formats>
    <includeBaseDirectory>false</includeBaseDirectory>
    <dependencySets>
        <dependencySet>
            <outputDirectory></outputDirectory>
            <outputFileNameMapping></outputFileNameMapping>
            <unpack>true</unpack>
            <unpackOptions>
                <includes>
                    <include>*.jar</include>
                </includes>
            </unpackOptions>
            <scope>runtime</scope>
        </dependencySet>
    </dependencySets>
</assembly>
{code}

What I'd like:

{code:xml}
            <plugin>
                <artifactId>maven-assembly-plugin</artifactId>
                <configuration>
                    <assembly>
                        <id></id>
                        <formats>
                            <format>zip</format>
                        </formats>
                        <includeBaseDirectory>false</includeBaseDirectory>
                        <dependencySets>
                            <dependencySet>
                                <outputDirectory></outputDirectory>
                                <outputFileNameMapping></outputFileNameMapping>
                                <unpack>true</unpack>
                                <unpackOptions>
                                    <includes>
                                        <include>*.jar</include>
                                    </includes>
                                </unpackOptions>
                                <scope>runtime</scope>
                            </dependencySet>
                        </dependencySets>
                    </assembly>
                </configuration>
                <executions>
                    <execution>
                        <id>make-assembly</id>
                        <phase>package</phase>
                        <goals>
                            <goal>attached</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
{code}

I do find it strange that it is a plugin that does *not* take it's input from a pom.

Even a managed artifact would be fine (put assembly.xml in a resource jar and list it as a
dependency - that would also work for me).

-Chris


  was:
Currently the plugin requires an external file to get it's configuration from.
Can we simply not have this expressed inside the pom itself?

What we currently have:

            <plugin>
                <artifactId>maven-assembly-plugin</artifactId>
                <configuration>
                    <descriptors>
                        <descriptor>assembly.xml</descriptor>
                    </descriptors>
                </configuration>
                <executions>
                    <execution>
                        <id>make-assembly</id>
                        <phase>package</phase>
                        <goals>
                            <goal>attached</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

and assembly.xml:

<assembly>
    <id></id>
    <formats>
        <format>zip</format>
    </formats>
    <includeBaseDirectory>false</includeBaseDirectory>
    <dependencySets>
        <dependencySet>
            <outputDirectory></outputDirectory>
            <outputFileNameMapping></outputFileNameMapping>
            <unpack>true</unpack>
            <unpackOptions>
                <includes>
                    <include>*.jar</include>
                </includes>
            </unpackOptions>
            <scope>runtime</scope>
        </dependencySet>
    </dependencySets>
</assembly>

What I'd like:

            <plugin>
                <artifactId>maven-assembly-plugin</artifactId>
                <configuration>
                    <assembly>
                        <id></id>
                        <formats>
                            <format>zip</format>
                        </formats>
                        <includeBaseDirectory>false</includeBaseDirectory>
                        <dependencySets>
                            <dependencySet>
                                <outputDirectory></outputDirectory>
                                <outputFileNameMapping></outputFileNameMapping>
                                <unpack>true</unpack>
                                <unpackOptions>
                                    <includes>
                                        <include>*.jar</include>
                                    </includes>
                                </unpackOptions>
                                <scope>runtime</scope>
                            </dependencySet>
                        </dependencySets>
                    </assembly>
                </configuration>
                <executions>
                    <execution>
                        <id>make-assembly</id>
                        <phase>package</phase>
                        <goals>
                            <goal>attached</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>

I do find it strange that it is a plugin that does *not* take it's input from a pom.

Even a managed artifact would be fine (put assembly.xml in a resource jar and list it as a
dependency - that would also work for me).

-Chris


    
> Assembly plugin process it's commands from it's pom (in addition to an external file)
> -------------------------------------------------------------------------------------
>
>                 Key: MASSEMBLY-369
>                 URL: https://jira.codehaus.org/browse/MASSEMBLY-369
>             Project: Maven 2.x Assembly Plugin
>          Issue Type: New Feature
>         Environment: N/A
>            Reporter: Chris Graham
>
> Currently the plugin requires an external file to get it's configuration from.
> Can we simply not have this expressed inside the pom itself?
> What we currently have:
> {code:xml}
>             <plugin>
>                 <artifactId>maven-assembly-plugin</artifactId>
>                 <configuration>
>                     <descriptors>
>                         <descriptor>assembly.xml</descriptor>
>                     </descriptors>
>                 </configuration>
>                 <executions>
>                     <execution>
>                         <id>make-assembly</id>
>                         <phase>package</phase>
>                         <goals>
>                             <goal>attached</goal>
>                         </goals>
>                     </execution>
>                 </executions>
>             </plugin>
> {code}
> and assembly.xml:
> {code:xml}
> <assembly>
>     <id></id>
>     <formats>
>         <format>zip</format>
>     </formats>
>     <includeBaseDirectory>false</includeBaseDirectory>
>     <dependencySets>
>         <dependencySet>
>             <outputDirectory></outputDirectory>
>             <outputFileNameMapping></outputFileNameMapping>
>             <unpack>true</unpack>
>             <unpackOptions>
>                 <includes>
>                     <include>*.jar</include>
>                 </includes>
>             </unpackOptions>
>             <scope>runtime</scope>
>         </dependencySet>
>     </dependencySets>
> </assembly>
> {code}
> What I'd like:
> {code:xml}
>             <plugin>
>                 <artifactId>maven-assembly-plugin</artifactId>
>                 <configuration>
>                     <assembly>
>                         <id></id>
>                         <formats>
>                             <format>zip</format>
>                         </formats>
>                         <includeBaseDirectory>false</includeBaseDirectory>
>                         <dependencySets>
>                             <dependencySet>
>                                 <outputDirectory></outputDirectory>
>                                 <outputFileNameMapping></outputFileNameMapping>
>                                 <unpack>true</unpack>
>                                 <unpackOptions>
>                                     <includes>
>                                         <include>*.jar</include>
>                                     </includes>
>                                 </unpackOptions>
>                                 <scope>runtime</scope>
>                             </dependencySet>
>                         </dependencySets>
>                     </assembly>
>                 </configuration>
>                 <executions>
>                     <execution>
>                         <id>make-assembly</id>
>                         <phase>package</phase>
>                         <goals>
>                             <goal>attached</goal>
>                         </goals>
>                     </execution>
>                 </executions>
>             </plugin>
> {code}
> I do find it strange that it is a plugin that does *not* take it's input from a pom.
> Even a managed artifact would be fine (put assembly.xml in a resource jar and list it
as a dependency - that would also work for me).
> -Chris

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

        

Mime
View raw message