Jean-François Lecomte created MECLIPSE-746:
----------------------------------------------
Summary: Non-Jar type dependency generates invalid entry in
.classpath file
Key: MECLIPSE-746
URL: https://jira.codehaus.org/browse/MECLIPSE-746
Project: Maven Eclipse Plugin
Issue Type: Bug
Affects Versions: 2.9
Reporter: Jean-François Lecomte
Priority: Minor
Not sure if it is a good practice, but when a JAR requires a DLL at runtime, I
add it in the maven repo. It usually works fine, I use the dependency plugin to
copy the dll in my working directory and when I generate my eclipse project,
they are not included in the classpath... except for one case: the javax.comm's
dll.
I refer to my DLL like this:
{code:xml}
<dependency>
<groupId>javax.comm</groupId>
<artifactId>win32com</artifactId>
<version>3.0-u1</version>
<type>dll</type>
<scope>runtime</scope>
</dependency>
{code}
When I generate the eclipse project using the command:
{noformat}
mvn eclipse:eclipse
{noformat}
the generated .classpath file contains:
{code:xml}
<classpathentry kind="var"
path="M2_REPO/javax/comm/win32com/3.0-u1/win32com-3.0-u1.dll"/>
{code}
When loading the project in Eclipse, I get the following error:
"Archive for required library:
'.m2/repository/javax/comm/win32com/3.0-u1/win32com-3.0-u1.dll' in project
'...' cannot be read or is not a valid ZIP file"
--
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
