[jira] Commented: (MPNATIVE-10) move from hardcoded lib_.so library name

[ji...@codehaus.org]

The following comment has been added to this issue:

     Author: Joachim Bader
    Created: Tue, 21 Sep 2004 3:43 PM
       Body:
Yes, it's hardcoded to so. It should be possible to edit the plugin.jelly file for supporting dlls and other files. 

Give me a few days. I'll try it.


---------------------------------------------------------------------
View this comment:
  http://jira.codehaus.org/browse/MPNATIVE-10?page=comments#action_24338

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MPNATIVE-10

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MPNATIVE-10
    Summary: move from hardcoded lib_.so library name
       Type: Improvement

     Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven-native-plugin

   Assignee: 
   Reporter: Rune Fauske

    Created: Tue, 21 Sep 2004 2:01 PM
    Updated: Tue, 21 Sep 2004 3:43 PM
Environment: msvc win32

Description:
Seems like both native:compile and native:install goals are hardcoded with .so library names. Any plans on making this more general in order to support other target platforms such as win32?


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org