maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Adrian Wilkins (JIRA)" <j...@codehaus.org>
Subject [jira] (MANTRUN-91) Cannot run javac from tasks
Date Mon, 01 Jul 2013 12:17:05 GMT

    [ https://jira.codehaus.org/browse/MANTRUN-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=327716#comment-327716
] 

Adrian Wilkins commented on MANTRUN-91:
---------------------------------------

I too have just wasted a few hours on this problem, and applied the horrible workaround.

What's the design rationale behind mangling the JAVA_HOME variable / classpath / whatever
for plugin executions? To me it seems silly to do this - Maven is a build system... why would
you want to hobble it's plugins by preventing them from building things (without special measures)?

In my opinion this completely violates the principle of least surprise - if I set JAVA_HOME
to a JDK, I expect plugins to behave in a way consistent with that, unless I explicitly state
otherwise.
                
> Cannot run javac from tasks
> ---------------------------
>
>                 Key: MANTRUN-91
>                 URL: https://jira.codehaus.org/browse/MANTRUN-91
>             Project: Maven 2.x Antrun Plugin
>          Issue Type: Bug
>            Reporter: Thomas Diesler
>            Assignee: Benson Margulies
>
> Embedded error: The following error occurred while executing this line:
> /home/tdiesler/svn/jbossws/stack/native/trunk/modules/testsuite/native-tests/scripts/antrun-wstools.xml:65:
Unable to find a javac compiler;
> com.sun.tools.javac.Main is not on the classpath.
> Perhaps JAVA_HOME does not point to the JDK

--
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

Mime
View raw message