Reinier van den Born wrote:
Hi Bartosz,
Bartosz Oudekerk wrote:
Reinier van den Born wrote:
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.
That's correct, you should use 1.0.2 with the Hippo CMS.
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.
The ibiblio repository is out of Hippo's control. The fix is documented
on the maven site itsself and you can add as many repositories to your
custom project.properties as you like.
Like you mention in your previous e-mail, the project.properties of the
CMS have been modified accordingly by Hippo. If you wouldn't have had a
custom configuration of maven, the CMS would in all probability have
build without error.
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.
You don't need to modify the project, nor switch to another version of
maven, it's your custom configuration of maven that needs changing.
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.
Not relevant in this case, see above.
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.
That would totally defeat the advantage of using a build system with
distributed dependencies. Not to mention the fact, that there might be
jars which have a license which prohibit them being distributed by 3rd
parties.
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.
It's still available, like most (if not all) previous releases:
http://maven.apache.org/maven-1.x/start/download.html
Regards,
--
Bartosz Oudekerk
.---------------------------------.-----------------------------------.
| Hippo B.V. | Hippo USA Inc. |
| Oosteinde 11 | 101 H Street, suite Q Petaluma CA |
| 1017 WT Amsterdam | 94952-3329 San Francisco |
| The Netherlands | United States |
| Tel +31 (0)20 5224466 | +1 (707) 773-4646 |
+---------------------------------+-----------------------------------+
| [EMAIL PROTECTED] | http://www.onehippo.com |
`---------------------------------^-----------------------------------'
********************************************
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
