[jbosstools-issues] [JBoss JIRA] (JBIDE-11738) Solve/workaround the issue of needing endorsed libraries on Java 6

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-11738?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12691323#comment-12691323 ] 

Fred Bricon commented on JBIDE-11738:
-------------------------------------

* javac uses jars from java.endorsed.dirs before those from endorseddirs (I checked). 
* maven-compiler-plugin is pretty bad at handling spaces in compilerArguments. It currently surrounds the whole <compilerArgument> value with quotes, regardless of the number of actual arguments in it. Dunno how <endorseddirs> behaves. yet. 
* Maybe add a warning marker on the project if the endorsed dirs are missing and ask him to run a CLI build manually. 

Corner case : given that maven-dependency-plugin can have several configurations spanned over several maven execution lifecycle mappings, it's gonna be tricky to know which one to execute/ point the user to : 
{code:xml}
<plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-dependency-plugin</artifactId>
    <version>2.1</version>
    <executions>
        <execution>
        <id>validate</id>
            <phase>validate</phase>
            <goals>
                <goal>copy</goal>
            </goals>
            <configuration>
                <outputDirectory>${endorsed.dir}</outputDirectory>
                <silent>true</silent>
                <artifactItems>
                    <artifactItem>
                        <groupId>javax</groupId>
                        <artifactId>javaee-endorsed-api</artifactId>
                        <version>6.0</version>
                        <type>jar</type>
                    </artifactItem>
                    <artifactItem>
                        <groupId>foo.bar</groupId>
                        <artifactId>endorsed</artifactId>
                        <version>0.0.1</version>
                        <type>jar</type>
                    </artifactItem>
                </artifactItems>
            </configuration>
        </execution>
        <execution>
        <id>generate-sources</id>
            <phase>generate-resources</phase>
            <goals>
                <goal>copy</goal>
            </goals>
            <configuration>
                <outputDirectory>${endorsed.dir2}</outputDirectory>
                <silent>true</silent>
                <artifactItems>
                    <artifactItem>
                        <groupId>foo.bar</groupId>
                        <artifactId>endorsed</artifactId>
                        <version>0.0.2</version>
                        <type>jar</type>
                    </artifactItem>
                </artifactItems>
            </configuration>
        </execution>                    
    </executions>
</plugin>
{code}
                
> Solve/workaround the issue of needing endorsed libraries on Java 6
> ------------------------------------------------------------------
>
>                 Key: JBIDE-11738
>                 URL: https://issues.jboss.org/browse/JBIDE-11738
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>            Reporter: Max Rydahl Andersen
>            Assignee: Fred Bricon
>            Priority: Critical
>             Fix For: 3.3.0.CR1
>
>
> JAX-WS has non-backwards compatible API changes requiring you to put specific jars on to endorsed libraries.
> Could we write a configurator that reacts to common ways of working around it in eclipse.
> m2e issue: https://bugs.eclipse.org/bugs/show_bug.cgi?id=363237
> Related to JBIDE-11348

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira