[ 
https://jira.codehaus.org/browse/MTOOLCHAINS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Herve Boutemy updated MTOOLCHAINS-6:
------------------------------------

    Description: 
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! :-)

  was:
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]
<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! :-)


> 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
>            Priority: Blocker
>
> 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)

Reply via email to