summaryrefslogtreecommitdiffstats
path: root/.classpath
Commit message (Collapse)AuthorAgeFilesLines
...
* Update to Guice 4.0-beta5James Moger2014-11-041-1/+1
|
* Update to SSHD 0.13.0James Moger2014-11-041-1/+1
|
* Merge branch 'ticket/205' into developJames Moger2014-10-141-2/+2
|\
| * Update to JGit 3.5.1James Moger2014-10-141-2/+2
| |
* | Merge branch 'ticket/200' into developJames Moger2014-09-301-1/+1
|\|
| * Update to Jetty 9.2.3.v20140905James Moger2014-09-301-1/+1
| |
| * Update to SSHD 0.12.0James Moger2014-09-301-1/+1
| |
* | Merge branch 'ticket/198' into developJames Moger2014-09-301-2/+2
|\|
| * Update to JGit 3.5.0.201409260305-rJames Moger2014-09-301-2/+2
| |
* | Merge branch 'ticket/164' into developJames Moger2014-09-071-0/+1
|\|
| * Create infrastructure for XSS sanitizationJames Moger2014-09-071-0/+1
| |
| * Update to SSHD 0.11.1-atlassian1James Moger2014-09-041-1/+1
| |
* | Allow Plugins to have injected members and Extensions to be constructedJames Moger2014-09-041-1/+1
| |
* | Merged #158 "Update Jetty version to 9.2.2"James Moger2014-09-041-2/+2
|\ \
| * | Update jetty version to 9.2.2David Ostrovsky2014-09-041-2/+2
| | |
* | | Update lucene version to 4.10David Ostrovsky2014-09-051-7/+7
|/ /
* | Update SSHD version to 0.12David Ostrovsky2014-09-041-2/+2
| | | | | | | | Also switch back to Maven Central repository.
* | Update to Guava 17James Moger2014-07-031-1/+1
| |
* | Use forked guice-servlet jar rather than stock jar from GoogleJames Moger2014-07-031-1/+1
| |
* | Temporarily depend on patched guice-servlet (guice-807)James Moger2014-07-031-1/+1
| |
* | Use Guice-Servlet rather than custom code and expose the InjectorJames Moger2014-07-031-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This is a fairly functional variation of Gitblit with one notable exception: The security filters are not working properly. This is a design flaw in Guice that I have reported upstream [1]. The general idea is that Guice-Servlet filters are not properly wrapping the ServletRequest. This has historically been a problem for Guice-Servlet servlets but Google has fixed most of those issues. Unfortunately, all the same flaws reported against the servlet delegation also exist in Guice-Servlet filter delegation. :( [1]: https://code.google.com/p/google-guice/issues/detail?id=807
* | Replace Dagger with Guice 4.0 beta and update Guava to 16.0.1James Moger2014-07-031-4/+3
| |
* | Update to Dagger 1.2.1 and Guava 15James Moger2014-07-031-4/+4
| |
* | Switch apt folder from 'dagger' to 'gen'James Moger2014-07-031-1/+1
| |
* | Update to SSHD 0.11.1-atlassian-1James Moger2014-07-031-1/+1
| |
* | Update to JGit 3.4.1James Moger2014-07-031-2/+2
| |
* | Update to Groovy 2.3.3James Moger2014-07-031-1/+1
| |
* | Update to SLF4j 1.7.7James Moger2014-07-031-2/+2
| |
* | Update to Freemarker 2.3.20James Moger2014-07-021-3/+3
| |
* | Update to gson 2.2.2James Moger2014-07-021-1/+1
| |
* | Update to SLF4j 1.7.7James Moger2014-07-021-2/+2
| |
* | DocumentationJames Moger2014-06-171-10/+10
|/
* Update to javax.mail 1.5.1James Moger2014-05-051-1/+1
|
* Split pages servlet into a raw branch servlet and a gh-pages servletJames Moger2014-05-041-0/+1
|
* Update to Apache MINA/SSHD 0.11.0James Moger2014-04-231-3/+3
|
* Update to SLF4J 1.7.5James Moger2014-04-151-2/+2
|
* Update to pf4j 0.8.0James Moger2014-04-151-1/+1
|
* Update to Jetty 9, drop AJPJames Moger2014-04-111-3/+2
|
* Update to pf4j 0.7.1 for a bug fixJames Moger2014-04-111-1/+1
|
* Improve plugin manager based on upstreamed contributions to pf4jJames Moger2014-04-101-1/+1
|
* Add plugins/extension infrastructureDavid Ostrovsky2014-04-101-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | Plugins are stored in `${baseFolder}/plugins` and are loaded during startup by the PluginManager. A plugin defines it's metadata in META-INF/MANIFEST.MF: Plugin-Class: com.gitblit.plugins.cookbook.CookbookPlugin Plugin-Dependencies: foo, bar Plugin-Id: gitblit-plugin Plugin-Provider: John Doe Plugin-Version: 1.0 Plugins can define extension points that can be implemented by other plugins and they can depend on other plugins: Plugin-Dependencies: foo, bar During the load phase, a directed acyclic graph is built and the loading order of the dependency chain is reversed using a topological sort; parent followed by children. The parent plugin classloader is the combined classloader of all parent plugins. Change-Id: I738821fa2bff02a5dbe339a944cc7e3c4dd8e299
* Bump SSHD version to 0.10.1David Ostrovsky2014-04-101-2/+2
| | | | Change-Id: Ic7e204fb7ee2eb172f4c8424fc3d4b7e6c631ddd
* Support serving repositories over the SSH transportEric Myhre2014-04-101-0/+2
| | | | | | | Gitblit would greatly benefit from an integrated SSH server. This would complete the transport trifecta. Change-Id: I6fb95abe65655fa74d47ea71522d8d9a1541450c
* Remove remaining GoogleCharts code and update documentationJames Moger2014-04-101-1/+0
|
* Update to JGit 3.3.1James Moger2014-03-271-3/+3
|
* Replace JCommander with args4jJames Moger2014-03-271-1/+1
|
* Update to JGit 3.3.0James Moger2014-03-051-7/+7
|
* Ticket tracker with patchset contributionsJames Moger2014-03-031-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A basic issue tracker styled as a hybrid of GitHub and BitBucket issues. You may attach commits to an existing ticket or you can push a single commit to create a *proposal* ticket. Tickets keep track of patchsets (one or more commits) and allow patchset rewriting (rebase, amend, squash) by detecing the non-fast-forward update and assigning a new patchset number to the new commits. Ticket tracker -------------- The ticket tracker stores tickets as an append-only journal of changes. The journals are deserialized and a ticket is built by applying the journal entries. Tickets are indexed using Apache Lucene and all queries and searches are executed against this Lucene index. There is one trade-off to this persistence design: user attributions are non-relational. What does that mean? Each journal entry stores the username of the author. If the username changes in the user service, the journal entry will not reflect that change because the values are hard-coded. Here are a few reasons/justifications for this design choice: 1. commit identifications (author, committer, tagger) are non-relational 2. maintains the KISS principle 3. your favorite text editor can still be your administration tool Persistence Choices ------------------- **FileTicketService**: stores journals on the filesystem **BranchTicketService**: stores journals on an orphan branch **RedisTicketService**: stores journals in a Redis key-value datastore It should be relatively straight-forward to develop other backends (MongoDB, etc) as long as the journal design is preserved. Pushing Commits --------------- Each push to a ticket is identified as a patchset revision. A patchset revision may add commits to the patchset (fast-forward) OR a patchset revision may rewrite history (rebase, squash, rebase+squash, or amend). Patchset authors should not be afraid to polish, revise, and rewrite their code before merging into the proposed branch. Gitblit will create one ref for each patchset. These refs are updated for fast-forward pushes or created for rewrites. They are formatted as `refs/tickets/{shard}/{id}/{patchset}`. The *shard* is the last two digits of the id. If the id < 10, prefix a 0. The *shard* is always two digits long. The shard's purpose is to ensure Gitblit doesn't exceed any filesystem directory limits for file creation. **Creating a Proposal Ticket** You may create a new change proposal ticket just by pushing a **single commit** to `refs/for/{branch}` where branch is the proposed integration branch OR `refs/for/new` or `refs/for/default` which both will use the default repository branch. git push origin HEAD:refs/for/new **Updating a Patchset** The safe way to update an existing patchset is to push to the patchset ref. git push origin HEAD:refs/heads/ticket/{id} This ensures you do not accidentally create a new patchset in the event that the patchset was updated after you last pulled. The not-so-safe way to update an existing patchset is to push using the magic ref. git push origin HEAD:refs/for/{id} This push ref will update an exisitng patchset OR create a new patchset if the update is non-fast-forward. **Rebasing, Squashing, Amending** Gitblit makes rebasing, squashing, and amending patchsets easy. Normally, pushing a non-fast-forward update would require rewind (RW+) repository permissions. Gitblit provides a magic ref which will allow ticket participants to rewrite a ticket patchset as long as the ticket is open. git push origin HEAD:refs/for/{id} Pushing changes to this ref allows the patchset authors to rebase, squash, or amend the patchset commits without requiring client-side use of the *--force* flag on push AND without requiring RW+ permission to the repository. Since each patchset is tracked with a ref it is easy to recover from accidental non-fast-forward updates. Features -------- - Ticket tracker with status changes and responsible assignments - Patchset revision scoring mechanism - Update/Rewrite patchset handling - Close-on-push detection - Server-side Merge button for simple merges - Comments with Markdown syntax support - Rich mail notifications - Voting - Mentions - Watch lists - Querying - Searches - Partial miletones support - Multiple backend options
* Update to JGit 3.2.0James Moger2013-12-201-2/+2
| | | | Change-Id: I77475dedfecbdc7ba3c065886a51b7a70b7ece48
* Support Markdown image links relative to the repository root (issue-324)James Moger2013-12-091-3/+3
| | | | Change-Id: I8bad02b26a20636e4fc3d1f0ab0a16f0bacc7bf1
generated by cgit v1.2.3 (git 2.39.1) at 2024-12-23 01:52:18 +0000