[shrinkwrap-issues] [JBoss JIRA] (SHRINKRES-205) Try to fork and use javac from path in MavenImporter if compiler is not found

[Karel Piwko (JIRA)]

     [ https://issues.jboss.org/browse/SHRINKRES-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karel Piwko resolved SHRINKRES-205.
-----------------------------------
         Assignee: Karel Piwko
    Fix Version/s: 2.2.0-alpha-3
       Resolution: Done


Landed in https://github.com/shrinkwrap/resolver/commit/8aa0d2be9303b4b1a792de6a474d79832ceed621

> Try to fork and use javac from path in MavenImporter if compiler is not found
> -----------------------------------------------------------------------------
>
>                 Key: SHRINKRES-205
>                 URL: https://issues.jboss.org/browse/SHRINKRES-205
>             Project: ShrinkWrap Resolvers
>          Issue Type: Enhancement
>          Components: impl-maven
>    Affects Versions: 2.2.0-alpha-2
>            Reporter: Karel Piwko
>            Assignee: Karel Piwko
>             Fix For: 2.2.0-alpha-3
>
>
> In cases MavenImporter does not find Javac class, IDE is probably set to run on top of JRE instead of JDK. In such cases, MavenImporter can emit a warning and modify configuration to fork and use javac from $PATH. 
> Such approach will make compilation more robust.
> See https://gist.github.com/kpiwko/626ed1c04ac28354137d for a quick idea how it could work.



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)