HI All,

I'm trying to get aquinted with  Hippo CMS 7, but I already ran in to trouble: 
when trying to compile from the source code with the command 

mvn package

I get an error:

Provider message:
The svn command failed.
Command output:
svn: '.' is not a working copy

[INFO] ---------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ---------------------------------------------------------------------
[INFO] Cannot get the revision information from the scm repository :
Error!

[INFO] ---------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ---------------------------------------------------------------------
[INFO] Total time: 9 seconds
[INFO] Finished at: Thu Feb 05 15:20:58 CET 2009
[INFO] Final Memory: 18M/254M
[INFO] ---------------------------------------------------------------------

What is wrong?

drs. M S.P.(Mischa) Andriesse
Consultant
 
KPMG CT Information Technology B.V.
Handelsregister 33294091
 
Churchillplein 6
2517 JW Den Haag
 
Tel       +31 70 338 2249
Fax      +31 70 338 2177
Mobile  +31 6 26086836
 
[email protected]

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of Arje Cahn
Sent: maandag 2 februari 2009 13:12
To: Hippo CMS development public mailinglist
Subject: [HippoCMS-dev] Hippo CMS 7 is live!

Go get Hippo CMS 7 at
http://www.onehippo.org/cms7/delve_into/quickstart.html, try out the
distro and knock yourself out :)
--------------------------


To all Hippo CMS 6 users and developers,

Almost 2 years after we started talking about plans for a new version
of Hippo CMS, I'm proud to say that we finally got there and released
Hippo CMS 7 !

Almost five years ago, in June 2004, the first stable distribution of
Hippo CMS version 6 was released. With this new release, we introduced
a fresh architecture where the CMS and its content repository were
separated components running as different server applications. This
separation of concerns on setup level has been one of the main drivers
for the success of Hippo CMS 6. It allowed for complex integrations
with external systems while keeping a strong focus on an easy to
understand user interface for the end-user.

The focus on standardized protocols and XML technologies opened up the
possibilities needed for enterprise wide CMS usage. Scalability and
load balancing functionalities have added to the stability of the
platform and allowed it to be used in the largest, content rich
environments.

We received wide user acceptance with our familiar user interface,
driven by early AJAX technologies to update only those parts of the
application that really needed updating.

On the developer's side, the concept of deployments and custom builds
allowed external developers to setup and use the Hippo CMS platform
for a diverse set of applications. All of these developments combined
have led to the current stable v6.05 release. And it's loaded with
functionalities and possibilities.

In their turn, these possibilities have inspired developers and
customers to raise ideas and wishes that go far beyond what's possible
today. But the architectural concept has proven itself, and we're
sticking with the separation between the CMS, repository and delivery
layers in CMS 7. Actually, the difference between Hippo Repository,
the CMS and the Portal will become even clearer: combined, they are a
perfect match for large-scale content environments. On their own, they
can be used as building blocks to form an entirely different
application.

Hippo CMS 7 was built on Apache Jackrabbit, Lucene, Wicket and many
other Apache projects. In the core of the new Hippo Repository 2,
we've built an incredibly powerful mechanism that creates faceted
representations of physical folders in Jackrabbit. Those virtual trees
are again exposed as 'normal' JCR nodes, and can be used to represent
all kinds of data in all kinds of different structures purely defined
by their meta information. For a quick demo, see my blog [1]. Combine
these really powerful Apache components, add that little bit of
faceted navigation, a touch of plugin framework and 36 person years of
development [2] and you have Hippo CMS 7 :-)

Go get our code from http://svn.onehippo.org/repos/hippo/hippo-ecm/,
check out the Hello World example, and start your own plugin project
at the Hippo Forge. The first 25 people to build a really neat plugin
on the forge will receive one of those funky Hippo T-shirts! What's
neat? A Google Maps location picker is neat, and maybe a Flickr image
plugin is neat, too :)

If you have questions, or would like to share some feedback, feel free
to sign up to our CMS 7 User list [3]. Your comments are very well
appreciated.
This mailinglist ([email protected]) will be kept in
place for community support on Hippo CMS 6. Also, Hippo will keep
working on CMS 6 fixes and updates. If you're relying on the
continuity of Hippo CMS 6 development, you might want to consider
buying a support contract with us [4] which will give you all the
guarantees you need.

Thanks to everyone on this list for your support, and I hope to see
you all on the CMS 7 list!

-- 

Kind regards,

Arjé Cahn
CTO, Hippo

[1] Demo of the faceted repository:
http://blogs.hippo.nl/arje/2007/09/status_update_defining_facets.html
[2] Stats from Ohloh http://www.ohloh.net/p/hippoecm
[3] CMS 7 User list: http://www.onehippo.org/cms7/mail-lists.html
[4] Hippo support contracts: http://www.onehippo.com/en/support


[email protected] / [email protected]

Amsterdam - Hippo B.V. Oosteinde 11 1017 WT Amsterdam +31(0)20-5224466
San Francisco - Hippo USA Inc. 101 H Street, suite Q Petaluma CA
94952-3329 +1 (707) 773-4646

www.onehippo.com [email protected]

---------------------------------------------------------------------
 Get Hippo CMS 7 at http://www.onehippo.org
 My blog: http://blogs.hippo.nl/arje
---------------------------------------------------------------------
********************************************
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

The information in this e-mail (and any attachments) is intended exclusively 
for the addressee(s). Any use by a party other than the addressee(s) is 
prohibited. The information may be confidential in nature and fall under a duty 
of non-disclosure. If you are not the addressee, please notify the sender and 
delete this e-mail.
KPMG cannot guarantee that e-mail communications are secure and error-free and 
does not accept any liability for damages resulting from the use of e-mail. Our 
services and other work are carried out under an agreement of instruction 
(overeenkomst van opdracht) that is subject to the general terms and conditions 
of the contracting KPMG firm. These general terms and conditions are available 
on our website (www.kpmg.nl/algemenevoorwaarden) and will be forwarded upon 
request.The statutory names of the KPMG-firms and the trade register numbers 
are also stated on our website, on the same page as the general terms.

Agreements with and statements from KPMG are only legally binding upon KPMG if 
they are confirmed in writing and signed by an authorized person.


********************************************
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

Reply via email to