maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergei Ivanov (JIRA)" <j...@codehaus.org>
Subject [jira] (MTOOLCHAINS-6) Cannot create custom toolchain type
Date Tue, 10 Feb 2015 11:58:24 GMT

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

Sergei Ivanov commented on MTOOLCHAINS-6:
-----------------------------------------

@Hervé: I've just stumbled upon this issue. It's good to know that my little plugin deserved
a mention and was used as a reference implementation for documenting the use of toolchains.
Back in the day I had to learn it the hard way, piecing together disparate bits of documentation
and using the built-in implementation of java toolchain as a reference. I took a look at your
latest documentation and the examples, and I can only say big thank you for the work you've
done there. I see you even worked around MNG-5718, which I was hit with today after updating
to Maven 3.2.5. That will be of a great to me in fixing my plugin for compatibility with the
latest versions of Maven. Thanks a lot for that.

> Cannot create custom toolchain type
> -----------------------------------
>
>                 Key: MTOOLCHAINS-6
>                 URL: https://jira.codehaus.org/browse/MTOOLCHAINS-6
>             Project: Maven Toolchains Plugin
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: Win 7 Pro SP1 64 Bit, mvn 3.0.4, JDK 1.7.0_45
>            Reporter: Markus KARG
>            Assignee: Herve Boutemy
>            Priority: Blocker
>             Fix For: 1.1
>
>
> The web site says that it is possible to use other toolchains besides <jdk>.
> Actually the site links to a nonexistent TBD page. This is very ugly.
> Please tell the truth on the web page: It is simply impossible to use any other toolschain
type besides <jdk>!
> It would be really cool, if someone could simply write:
> {code:xml}
> <toolchains>
>   <type>installshield</type>
>   <provides>
>     <id>isx</id>
>     <version>10.0</version>
>     <vendor>macrovision</vendor>
>   </provides>
>   <configuration>
>     <installshieldHome>C:\Program Files (x86)\InstallShield X</installshieldHome>
>   </configuration>
> </toolchains>
> {code}
> ...and the plugin would in turn simply provide a property that one can read in the POM
using {{$\{installshieldHome}}} -- without any need to write Java code, register custom types,
provide more xml, whatever!
> This seems to be such an obvious need that I just cannot believe that it does not already
work exactly that way in the 1.0 release of the toolchains plugin...! :-)
> I really beg for that! :-)



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message