Hi Bartosz,
Bartosz Oudekerk wrote:
Reinier van den Born wrote:
When I try to build maven fails on an 301 http error (permanently
moved) for the jtds-1.2.jar from
http://www.ibiblio.org/maven/net.sourceforge.jtds/jars/jtds-1.2.jar
It apparently has moved to
http://mirrors.ibiblio.org/pub/mirrors/maven2/net/sourceforge/jtds/jtds/1.2/jtds-1.2.jar
Looked around a bit and found comments that Maven1 doesn't know how to
handle 301s.
This is only true for maven 1.0.x.
See below.
So it does seem a bit odd that this big maven repository is moving
maven1 jars around?
They're probably assuming that if you're still using 1.x, you're using
1.1.x, not 1.0.x.
I am using maven 1.0.2 because, at least a couple of months ago, that was the
only version that would build the CMS.
Maybe that has changed in newer versions of the CMS, but I have seen no mention
of that.
Which reflects on the reliability of the Hippo build process?
I want my builds to be reproducable, not just today but also for the
next couple of years.
It is.
Not really. Say that I created and built a project 1/2 year ago, and stored my stuff in subversion. Now I want to
rebuild, so I restore my tooling environment (including maven 1.0.2), extract from subversion, and try to build.
If jars have moved, like above, the new build will fail.
Maybe I can adjust the build to make it work, maybe by switching to another
version of maven,
but that means I modify the project and the build is no longer the same.
Rebuilding an old project is most often done to fix some problem. To be able to do that you want the build to resemble
the original as closely as possible. Changed build scripts or new tooling allows, inadvertently but still, the
introduction of changes and thus complicates identifying the problem.
Suppose the problem doesn't reproduce in the new build. Does that mean it is fixed, or just that because of the new
build the same problem happens in a different place? Because of the changed build you may very well lose the handle to
get to the problem.
So maybe when freezing a version, the jars should also be frozen. Ie. copied to a safe place. Maybe the only proper way
to use maven is to set up a local repository. Always.
Anyway, is there a way to get around this?
Yes, do not use ibibilio anymore, but access the new repository
directly, see:
http://maven.apache.org/maven-1.x/news.html#ibiblio_redirect
Doesn't seem to help. See answer to Bart.
Tried to find some documentation, but all seems to be maven 2 now.
http://maven.apache.org/maven-1.x/index.html
Tried to drop the jar in the Maven repository on my disk, but to no
avail...
IIRC this should work, if the location is correct. I'm not a 100% sure
though.
A while ago I saw some mention of moving Hippo building to maven 2,
but I haven't seen announcements of it being available.
Maybe it was moving to maven 1.1, don't remember exactly.
Was mentioned in the context of maven version 1.0.2 no longer being available
for download.
Reinier
--
Reinier van den Born
HintTech B.V.
Rotterdamseweg 183c, 2629 HD Delft
T: +31(0)15 268 2573
F: +31(0)15 268 2567
M: +31(0)6 494 171 36
--
HintTech levert specialisten op het gebied van softwareontwikkeling (.NET en
Java),
projectmanagement, informatiebeveiliging en business consulting.
KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01
begin:vcard
fn:Reinier van den Born
n:van den Born;Reinier
org:HintTech B.V.
adr:;;Rotterdamseweg 183c;Delft;;2629HD;Netherlands
email;internet:[EMAIL PROTECTED]
tel;work:+31-15-268 2573
tel;fax:+31-15-268 2567
tel;cell:+31-6 494 171 36
note;quoted-printable:KvK Den Haag nr. 27242282 | BTW nr. NL8062.16.396.B01=0D=0A=
=0D=0A=
HintTech levert specialisten op het gebied van softwareontwikkeling (.NET=
en Java), projectmanagement, informatiebeveiliging en business consulting=
.=0D=0A=
=0D=0A=
url:www.hinttech.com
version:2.1
end:vcard
********************************************
Hippocms-dev: Hippo CMS development public mailinglist
Searchable archives can be found at:
MarkMail: http://hippocms-dev.markmail.org
Nabble: http://www.nabble.com/Hippo-CMS-f26633.html
