[
http://jira.codehaus.org/browse/MINSTALL-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MINSTALL-28.
-------------------------------------
Assignee: Benjamin Bentmann
Resolution: Not A Bug
Yep, this appears to be beyond the scope of the Install Plugin itself. A
packaging can't be chosen at will but must have been registered with the core
(via extensions). So this more a configuration/best practice issue to be solved
by the [user list|http://maven.apache.org/mail-lists.html].
> 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
> Assignee: Benjamin Bentmann
>
> 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
> {code:xml}
> <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>
> {code}
> but maven complains
> {noformat}
> [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.
> {noformat}
> 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
