If you are using mvn deploy then it should upload correctly as the various
modules have the deploy plugin disabled.
Ralph
> On Apr 11, 2018, at 7:44 AM, Matt Sicker wrote:
>
> I’ve set it up to use the “mvn deploy” task to upload. Only automatic thing
> about Jenkins here is that the m2 settin
I’ve set it up to use the “mvn deploy” task to upload. Only automatic thing
about Jenkins here is that the m2 settings.xml is provided or something so
that you don’t need to configure a user to upload with (like I had to do
for the sbt build).
Anyways, if I see how to customize that in maven, I’ll
I don’t know. I have never really looked at how Jenkins does the deploy.
Ralph
> On Apr 10, 2018, at 7:16 PM, Matt Sicker wrote:
>
> Is it possible to exclude that from the deploy task? The scala api build
> only publishes the api jars, not the samples, for example.
>
> On 10 April 2018 at 17
Is it possible to exclude that from the deploy task? The scala api build
only publishes the api jars, not the samples, for example.
On 10 April 2018 at 17:12, Ralph Goers wrote:
> Note that the Jenkins deployment uploads stuff that we don’t release.
>
> Ralph
>
> > On Apr 10, 2018, at 9:57 AM, M
Note that the Jenkins deployment uploads stuff that we don’t release.
Ralph
> On Apr 10, 2018, at 9:57 AM, Matt Sicker wrote:
>
> I've added a new pipeline for Log4j <
> https://builds.apache.org/job/Log4jCore/> using a Jenkinsfile as we are
> doing in log4net, chainsaw, log4j scala api, log4j
I've added a new pipeline for Log4j <
https://builds.apache.org/job/Log4jCore/> using a Jenkinsfile as we are
doing in log4net, chainsaw, log4j scala api, log4j kotlin api, and logging
parent. Thanks to Dominik for demonstrating that this was possible and also
how to run things on Windows.
This pi
