I found 2.0.x sources in SVN but I don't remember at all how we packaged
them
For now I prepared an update of the Jenkins script to use apache archives +
maven central
On Tue, May 26, 2015 at 1:08 PM, Arnaud Héritier aherit...@gmail.com
wrote:
I will see if we can easily upload the missing
I will see if we can easily upload the missing versions on central (I don't
remember why we didn't do it previously) otherwise I'll aggregate central +
apache archives
On Mon, May 25, 2015 at 7:18 PM, Dennis Lundberg denn...@apache.org wrote:
Right, the future proof source for Maven distros
Right, the future proof source for Maven distros should be the central
repo. Primarily because the coordinates will not change.
Den 23 maj 2015 18:53 skrev Hervé BOUTEMY herve.bout...@free.fr:
notice that with Maven 4, in xxx monthes/years..., we probably will have
another /dist/ directory, but
notice that with Maven 4, in xxx monthes/years..., we probably will have
another /dist/ directory, but distribution artifact coordinates in central
should not change
Regards,
Hervé
Le vendredi 22 mai 2015 15:05:13 Arnaud Héritier a écrit :
Hi Dennis,
No I see no real issue of getting
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
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 ja...@takari.io wrote:
Easy enough to put them
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 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 denn...@apache.org wrote:
Hi Arnaud,
I stumbled upon
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
Jason,
It don't find binaries of 2.0.9 in central. Did I miss something ?
I would like (for jenkins) to not remove old releases from the catalog
without a real reason ...
Arnaud
On Fri, May 22, 2015 at 12:04 AM, Jason van Zyl ja...@takari.io wrote:
Why don't you just use Maven Central.
Resurrecting this thread.
Having a standardised place to find all versions was a good thing
Because of the change jenkins doesn't propose anything 3.2.2 because it
is checking only in http://archive.apache.org/dist/maven/binaries/
And it doesn't see the content of
Easy enough to put them there so that it's complete.
On May 21, 2015, at 6:21 PM, Arnaud Héritier aherit...@gmail.com wrote:
Jason,
It don't find binaries of 2.0.9 in central. Did I miss something ?
I would like (for jenkins) to not remove old releases from the catalog
without a real
Hm ... isnt the fact that Maven 2.x is deprecated reason enough to NOT offer it
in Jenkins. From my memory 2.0.8 and 2.0.9 had some severe problems and only
2.0.10 sort of fixed things.
Personally I would think that you should restrict the list in Jenkins even
excluding 2.x altogether. Or
Why don't you just use Maven Central. Those copies are not going anywhere.
On May 21, 2015, at 6:02 PM, Arnaud Héritier aherit...@gmail.com wrote:
Resurrecting this thread.
Having a standardised place to find all versions was a good thing
Because of the change jenkins doesn't propose anything
On Mon, Dec 29, 2014 at 6:25 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
we generally switched Maven release canonical download area to
https://dist.apache.org/repos/dist/release/maven/maven-3/
IIRC, http://archive.apache.org/dist/maven/binaries/ was used by Jenkins
folks
for automatic
good catch: fixed :)
http://svn.apache.org/r1648412
Regards,
Hervé
Le lundi 29 décembre 2014 18:59:23 Milos Kleint a écrit :
On Mon, Dec 29, 2014 at 6:25 PM, Hervé BOUTEMY herve.bout...@free.fr
wrote:
we generally switched Maven release canonical download area to
Hello,
for some reason 3.2.3 is not available in the archives, is that intentional
or something went wrong with the 3.2.5 release?
Thanks
Milos
we generally switched Maven release canonical download area to
https://dist.apache.org/repos/dist/release/maven/maven-3/
IIRC, http://archive.apache.org/dist/maven/binaries/ was used by Jenkins folks
for automatic Maven version discovery and download, before the change
seems like we didn't
Why do you need it there?
The way binaries are kept at Apache is inconsistent. How it evolved over time
where things disappear from one place to another (official distribution to
archives) I don't find makes much sense but that's the way it is. If you
require a distribution in a standard place
19 matches
Mail list logo
