search

stigkj / gradle-executable-jar-plugin

ABANDONED - use something like the gradle-capsule-plugin instead
24 stars 3 forks source link

Should not add SourceForge as a repository #4

Open stigkj opened 12 years ago

stigkj commented 12 years ago

This can severly affect build time, so should be something the programmer decides on when setting up the build

stigkj commented 12 years ago

Before solving #5, the best that can be done is to only add the repository when the default version of One-JAR is used

stigkj commented 12 years ago

A better implementation of only adding the repository when the default version of One-JAR is used is done for GH-7

wernsen commented 11 years ago

Hi,

Any progress on this issue? Is see some code related to this in the repository but it is unclear to me if it works or how it should be used. Disabling the SourceForge repository is really important for us since our build environment is not allowed access to the internet.

regards,

P.S.

Love the plugin so far btw :-)

stigkj commented 10 years ago

@wernsen Sorry for the late answer! Not sure if you have found out, but if you define your own dependency on One-JAR, SourceForge will not be used for downloading the dependency. I guess you have a Maven repo inhouse? Just upload a One-JAR version to this and specify a dependency to this version in the build with scope 'executableJar'.