[ http://jira.codehaus.org/browse/MNGECLIPSE-26?page=all ]
Eugene Kuleshov closed MNGECLIPSE-26:
-------------------------------------
Resolution: Fixed
Fix Version: 0.0.10
It should be possible to use Maven's profiles mechanism and system dependencies
to declare specific system jars. See:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
That should cover dependency resolution for build Maven classpatch container.
Compiler source and target is picked from pom.xml and set for project settings
when "Update Source Folders" action is invoked.
Maven launcher allows to select JDK used to launch Maven.
I guess that cover everything. Feel free to reopen if I missed something, but
attach project that would allow to reproduce issue.
> Handling system dependencies
> ----------------------------
>
> Key: MNGECLIPSE-26
> URL: http://jira.codehaus.org/browse/MNGECLIPSE-26
> Project: Maven 2.x Extension for Eclipse
> Type: New Feature
> Versions: 0.0.3
> Environment: Eclipse 3.1, MyEclipse, Java 5.0
> Reporter: Leonardo Quijano Vincenzi
> Assignee: Eugene Kuleshov
> Fix For: 0.0.10
>
>
> The Maven plugin uses the JRE/JDK used to launch Eclipse. It would be useful
> to include a dialog that allows people to change that default JDK (mostly due
> to problems when specifying system jars in pom files), probably just
> selecting the appropiate Eclipse-configured JDK.
> At least the plugin could use the default Eclipse JDK.
--
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
