[HAP-44] "Gradle-Artifactory Plugin" does not work with M3 (do deployment, no console output) Created: 21/Jun/10 Updated: 26/Aug/10 Resolved: 26/Aug/10
|Project:||Jenkins Artifactory Plug-in|
|Reporter:||Michael Huettermann||Assignee:||Yossi Shaul|
The Hudson Artifactory Plug-in does not work.
Expected result: Maven build artifacts are deployed to Artifactory
As far as I know, there is no workaround available. Thus, for our situation, this issue is a blocker.
|Comment by Yoav Landman [ 21/Jun/10 ]|
I am sorry - M3 is not yet supported - the free-style project Gradle-Artifactory Plugin is Gradle only. What may be misleading here is the naming of the options:
We still have some work to do in order to have M3 support in the plugin, since when invoking Maven we need to have Hudson register our plugin to the build and collect the build events for constructing the build info. This is trickier with M3 since Hudson does not taking control over the Maven invocation yet as it does with M2, so we need to figure out a way to do this with a free style project when Maven is invoked from the command line or wait for the Hudson-M3 project type integration.
|Comment by Michael Huettermann [ 21/Jun/10 ]|
ah, I see, thanks for the information. Yep, some re-naming and help is helpful. Thanks for that !!
Do you have a rough schedule for the M3 support? M3 (alpha, beta) is already on the market for some time now, and it is close to 3.0 final state. Many users already switched, and many more will follow. Beside that, if the project is strictly depending on Maven 3, you have no chance to use the Hudson/Artifactory-feature, at the moment.
if you need an alpha tester for the M3 support, please let me know