[
https://jira.codehaus.org/browse/MECLIPSE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=317123#comment-317123
]
Maik Riechert commented on MECLIPSE-482:
----------------------------------------
I support this very much! It would make things much easier and the [maven
natives eclipse integration plugin|http://code.google.com/p/mavennatives/]
redundant (see the bottom of the page).
But I think the patch might not be optimal. The path entry is relative to the
*workspace*, not the project. Therefore we would have to include the project
name in the pom file. But as this can be freely chosen via "name templates"
when importing maven projects, it should rather not belong there. I think, the
new parameter should consist of the path relative to the project (e.g.
"target\natives"), and the Maven Eclipse Plugin would then prepend that with
the project part, e.g. "project1\target\natives".
By the way, why does this get no attention? Is nobody using natives these days?
> Add a new parameter "native libraries path"
> -------------------------------------------
>
> Key: MECLIPSE-482
> URL: https://jira.codehaus.org/browse/MECLIPSE-482
> Project: Maven 2.x Eclipse Plugin
> Issue Type: New Feature
> Components: Core : Workspace settings
> Affects Versions: 2.5.1
> Reporter: Vincent Behar
> Priority: Minor
> Attachments: nativeLibrariesPath.patch
>
>
> Hi,
> Here is a small patch that enables a new parameter "nativeLibrariesPath".
> If a path is provided, the
> "org.eclipse.jdt.launching.CLASSPATH_ATTR_LIBRARY_PATH_ENTRY" parameter in
> the .classpath file is set with the given path.
--
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
