Commit Graph

15 Commits

Author SHA1 Message Date
Ian Wienand 234ed85a92 Retire repo
Change-Id: I7d68f82c75cbc4dc7e843198593846e19cf88f14
2022-04-05 13:20:00 +10:00
Nico Sallembien c6e695f482 Add standard eclipse generated files to .gitignore
These files keep showing up when I run git add . and it's throwing off
the release script, so I am telling git to forget about them.

Change-Id: I4c12e9c4d72acf8e8dc1345b6903cfa224e621ed
2010-01-29 16:53:05 -08:00
Shawn O. Pearce 955d00eb81 Completely remove GerritServer.properties
We now load our database settings in hosted development mode from
the $site_path/etc/gerrit.config, just like we would under daemon.
This reduces the number of weird configurations that are supported.

Change-Id: I0a13f16dd74bdb034d05650eadd5e36771109f3e
Signed-off-by: Shawn O. Pearce <sop@google.com>
2009-12-19 13:38:19 -08:00
Shawn O. Pearce dbbca8bf56 daemon: Run correctly under Eclipse debugger
We now can launch the daemon correctly from within the Eclipse debugger
without having to switch to using the WAR in our CLASSPATH.  This works
by allowing Eclipse to supply all of the CLASSPATH, but we have to go
find our WAR resource content in gerrit-gwtui/target.

Bug: 340
Change-Id: I7dfbc0654cdc10099fb3de3041e615a9fda5fdb4
Signed-off-by: Shawn O. Pearce <sop@google.com>
2009-12-07 15:23:16 -08:00
Shawn O. Pearce 44671f5c69 Rewrite our build as modular maven components
This refactoring splits the code up into different components, with
their own per-component CLASSPATH.  By moving all of our classes
into isolated components we can better isolate the classpaths and
try to avoid unexpected dependency problems.  It also allows us to
more clearly define which components are used by the GWT UI and
thus must be compiled under GWT, and which components are run on
the server and can therefore use more of the J2SE API.

Change-Id: I833cc22bacc5655d1c9099ed7c2b0e0a5b08855a
Signed-off-by: Shawn O. Pearce <sop@google.com>
2009-11-11 16:54:06 -08:00
Shawn O. Pearce 8d2f184389 Switch to GWT 1.6's new HostedMode debugging utility
The pain in the neck thing is, we have to use their new WAR style
output, which requires us to run "mvn war:inplace" before we can
start debugging, or if any dependencies change, but we also need
to clean that out.

All RPC handles also moved inside of the module directory, which
makes it easier to debug in the hosted mode browser but breaks any
existing browser client, even though the JSON payloads have not
changed in format.

Bug: GERRIT-75
Signed-off-by: Shawn O. Pearce <sop@google.com>
2009-05-13 12:02:25 -07:00
Shawn O. Pearce 8cbf4dc01d Ignore GerritServer.properties at the top level
This might exist if the developer is trying to test directly from
the source directory by running something like:

  mvn package && java -jar target/gerrit-*.war foo

and the "foo" subcommand requires GerritServer.properties to speak
to the database.

Signed-off-by: Shawn O. Pearce <sop@google.com>
2009-03-07 16:49:22 -08:00
Shawn O. Pearce 263786e2fd Move appjar contents up one level to normalize our structure
In general we map one Maven project description to one Git
repository, as each Maven project has its own unique version
number for its artifact.

This change pulls everything up one level so its a much more
typical directory layout, where the pom.xml is at the root
of the directory structure.

Signed-off-by: Shawn O. Pearce <sop@google.com>
2009-02-02 16:04:52 -08:00
Shawn O. Pearce f14a1ded65 Switch build system to use Maven 2
This way we can easily depend upon other projects which also use
Maven, without needing to embed all of their dependencies directly
within our repository.

Signed-off-by: Shawn O. Pearce <sop@google.com>
2008-12-20 17:48:48 -08:00
Shawn O. Pearce 38270b642d Import all patch data again from Git to ensure it is accurate
We've made some schema changes about how patch data is stored and
represented in the Gerrit 2 database, so we need to import all of
the patch entities over again.  This change includes a CLI tool
that can be run to re-import one or more patch set entities from
the corresponding Git commit.

Signed-off-by: Shawn O. Pearce <sop@google.com>
2008-12-12 18:25:12 -08:00
Shawn O. Pearce 5f95e2d5db Add JGit to the build path so we can access Git repositories
This gives us server-side access to Git repositories,
without forking external processes.

Signed-off-by: Shawn O. Pearce <sop@google.com>
2008-12-12 14:44:43 -08:00
Shawn O. Pearce 1176f4538d Build a standard .war file for Gerrit
We also include .gz versions of every static resource, because
this allows Jetty (and possibly other servers) to efficiently
send the pre-compressed static resource to the client.

Signed-off-by: Shawn O. Pearce <sop@google.com>
2008-12-01 11:25:57 -08:00
Shawn O. Pearce 2f09570d60 export_safe: A script to scrub and export a Gerrit2 database
This script is just a simple tool to help me export the current
PostgreSQL database into a format that is safe to send to a 3rd
party.  All of the data is public on Gerrit's website, except for
the user's physical address contact information.  We scrub that
out because we do not have consent from our users to disclose
that information.

Signed-off-by: Shawn O. Pearce <sop@google.com>
2008-11-26 16:19:24 -08:00
Shawn O. Pearce 1d638cec61 Ignore hs_err_pid*.log as they are created by JRE crashes
We don't need to track these files from hosted mode crashes.
Keeping them in .gitignore makes it easier to "git add ." and
not worry about them being included into the project.

Signed-off-by: Shawn O. Pearce <sop@google.com>
2008-11-22 21:17:55 -08:00
Shawn O. Pearce 23571ab1fa Initial project setup of Gerrit 2
Gerrit 2 is a ground-up rewrite of Gerrit, using GWT (Google Web
Toolkit) for the client side user interface and a Java servlet
based backend.

Signed-off-by: Shawn O. Pearce <sop@google.com>
2008-11-14 16:59:34 -08:00