Fair enough.
As a user of both tools I think there might be a need to distinguish between
what is available in new installs and what just works due to legacy installs.
E.g. the version drop down could hide all the 2.x versions.
But I realize that even for new installs you might have a new for
Hi Dennis,
No I see no real issue of getting them from several sources.
I want just to be sure that we are agree for the long term to be sure to
not have to update them too often
Arnaud
On Fri, May 22, 2015 at 2:16 PM, Dennis Lundberg wrote:
> Hi Arnaud,
>
> I stumbled upon that Jenkins is
Hi Arnaud,
I stumbled upon that Jenkins issue last week, and had a quick look at
the pull request available. From what I could tell, the proposed
solution was to use the (legacy) ASF dist area *and* Central to get
the best of both worlds. Do you see a problem having 2 data sources
for the Jenkins
Hi Manfred,
With my Maven committer hat I would prefer to restrict the default
choices to the latest stable releases we have.
With my Jenkins committer hat I see this as an enhancement request.
Jenkins should allow for each product to limit/classify the proposed
version. For sure the rule won
Yes I agree but I preferred to add an ack from the dev team before
proposing such upload
I need to check how it was published before 2.0.9 if I want to publish the
missing set of archives and poms
On Fri, May 22, 2015 at 12:36 AM, Jason van Zyl wrote:
> Easy enough to put them there so that it's
