[jira] Commented: (MINSTALL-28) Error in Project Attempting to Use maven-install-plugin with 'lib' Packaging

["Dennis Lundberg (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MINSTALL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_125817 ] 

Dennis Lundberg commented on MINSTALL-28:
-----------------------------------------

I don't think this should work.

In _Introduction to the Build Lifecycle_ at http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html it says

bq. Note that for some packaging types to be available, you may also need to include a particular plugin in your build section of your POM (as described in the next section). One example of a plugin that requires this is the Plexus plugin, which provides a plexus-application  and plexus-service  packaging.

Since the packaging *lib* is not a standard packaging I suspect that you need extra code to define what should happen for such a packaging during the lifecycle.

> Error in Project Attempting to Use maven-install-plugin with 'lib' Packaging
> ----------------------------------------------------------------------------
>
>                 Key: MINSTALL-28
>                 URL: http://jira.codehaus.org/browse/MINSTALL-28
>             Project: Maven 2.x Install Plugin
>          Issue Type: Bug
>    Affects Versions: 2.2
>         Environment: Win2003, running mvn 2.04 in Cygwin bash shell
> Locally built version maven-install-plugin 2.2-SNAPSHOT
>            Reporter: Brad Harper
>
> I'm using M2 'maven-native-plugin' to build C++ libraries and apps. Within the
> overall project structure I have a module to handle a set of 3rd-party (library) artifacts. Some of these are native libraries (without source) and some are
> built from open source.
> I'd like to run
>    % mvn install
> in the 3rd-party module and have the pre-built libraries simply copied
> into the local repository with an </artifactId> that can be expressed in
> the </dependencyManagement> part elsewhere.
> The POM descriptor for one of these native library sub-modules contains
>   <packaging>lib</packaging>
>   <build>
>     <plugins>
>       <plugin>
>         <artifactId>maven-install-plugin</artifactId>
>         <executions>
>           <execution>
>             <id>install-library</id>
>             <phase>install</phase>
>             <configuration>
>               <groupId>com-epsiia-dxr-third-party</groupId>
>               <artifactId>dxr-third-party-com-emc-\
>                             centera-fplibrary-WINDOWS-X86</artifactId>
>               <version>2.0SP1</version>
>               <packaging>lib</packaging>
>               <file>FPLibrary.lib</file>
>             </configuration>
>           </execution>
>         </executions>
>       </plugin>
>     </plugins>
>   </build>
> but maven complains
>   [ERROR] BUILD ERROR
>   [INFO] ----
>   [INFO] Cannot find lifecycle mapping for packaging: 'lib'
>   Component descriptor cannot be found in the component \
>   repository: org.apache.maven.lifecyle.mapping.LifecycleMappinglib.
> The 'maven-native-plugin' is supplied by codehaus.org and the plugin's
> use is declared in an ancestor POM descriptor. In modules where C++
> source is compiled/linked, the 'install' goal moves the resulting
> artifact into the repository.
> Shouldn't this work?

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