[
https://jira.codehaus.org/browse/MTOOLCHAINS-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355601#comment-355601
]
Herve Boutemy commented on MTOOLCHAINS-6:
-----------------------------------------
oh, yes, it seems there is a fork with custom toolchains support:
http://sergei-ivanov.github.io/maven-protoc-plugin/examples/protobuf-toolchain.html
/ https://github.com/sergei-ivanov/maven-protoc-plugin
thank you for the pointer (notice the plugin is not published to central: this
is an extension not maintained by core protobuf project)
I'll add it to our list of toolchain's aware plugins
http://maven.apache.org/guides/mini/guide-using-toolchains.html, to list not
only jdk-toolchain-aware plugins, but other toolchains too
and in protobuf, there is a good idea I'll integrate into the IT: have the
plugin provide both the plugin and the toolchain, and mark it as extension,
since I suppose custom toochains will often be tied to one plugin only (like
protobuf), and not multiple (like jdk)
> 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)
