-
Notifications
You must be signed in to change notification settings - Fork 1
/
scm.html
488 lines (463 loc) · 23.7 KB
/
scm.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
<!DOCTYPE html>
<!--
Generated by Apache Maven Doxia at 2022-02-10
Rendered using Maven Reflow Skin 1.0.0 (http://andriusvelykis.github.com/reflow-maven-skin)
-->
<html xml:lang="en" lang="en">
<head>
<meta charset="UTF-8" />
<title>Jersey - </title>
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta name="description" content="" />
<meta http-equiv="content-language" content="en" />
<link href="//netdna.bootstrapcdn.com/twitter-bootstrap/2.2.2/css/bootstrap.min.css" rel="stylesheet" />
<link href="//netdna.bootstrapcdn.com/twitter-bootstrap/2.2.2/css/bootstrap-responsive.min.css" rel="stylesheet" />
<link href=".//css/docs.css" rel="stylesheet" />
<link href=".//css/reflow-skin.css" rel="stylesheet" />
<link href="//yandex.st/highlightjs/7.3/styles/solarized_dark.min.css" rel="stylesheet" />
<link href=".//css/lightbox.css" rel="stylesheet" />
<link href=".//css/site.css" rel="stylesheet" />
<link href=".//css/print.css" rel="stylesheet" media="print" />
<!-- Le HTML5 shim, for IE6-8 support of HTML5 elements -->
<!--[if lt IE 9]>
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->
<link rel="stylesheet" href="https://netdna.bootstrapcdn.com/font-awesome/3.2.1/css/font-awesome.css"/>
<!-- Google Analytics -->
<script type="text/javascript">
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-3160303-1']);
_gaq.push(['_trackPageview']);
(function() {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
})();
</script>
</head>
<body class="page-scm project-site" data-spy="scroll" data-offset="60" data-target="#toc-scroll-target">
<div class="navbar navbar-fixed-top">
<div class="navbar-inner">
<div class="container">
<a class="btn btn-navbar" data-toggle="collapse" data-target=".nav-collapse">
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</a>
<a class="brand" href="index.html"><img src="images/jersey_logo.png" style="width:22px; margin-right:10px;" /><span class="gf-orange">Jersey</span><span> - RESTful Web Services in Java.</span></a>
<div class="nav-collapse">
<ul class="nav pull-right">
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">Jersey 3.0.4 <b class="caret"></b></a>
<ul class="dropdown-menu">
<li><a href="download.html" title="Get latest Jersey">Get latest Jersey </a></li>
</ul>
</li>
<li class="dropdown">
<a href="#" class="dropdown-toggle" data-toggle="dropdown">Documentation <b class="caret"></b></a>
<ul class="dropdown-menu">
<li class="dropdown-submenu">
<a href="documentation/latest/index.html" title="User Guide">User Guide </a>
<ul class="dropdown-menu">
<li><a href="documentation/latest/getting-started.html" title="Getting Started">Getting Started </a></li>
<li><a href="documentation/latest/modules-and-dependencies.html" title="Modules and Dependencies">Modules and Dependencies </a></li>
</ul>
</li>
<li><a href="apidocs/latest/jersey/index.html" title="API javadoc">API javadoc </a></li>
</ul>
</li>
</ul>
</div><!--/.nav-collapse -->
</div>
</div>
</div>
<div class="container">
<!-- Masthead
================================================== -->
<header class="jumbotron subhead">
<div class="row" id="banner">
<div class="span12">
<div class="pull-left">
<a href="index.html" id="bannerLeft"><h1><img src="images/jersey_logo.png" style="width:56px; margin-right:14px;" /><span class="gf-orange">Jersey</span></h1></a>
<p class="lead">RESTful Web Services in Java.</p>
</div>
<div class="pull-right">
</div>
</div>
</div>
<hr class="toc-separator" />
<div id="toc-bar" class="navbar">
<div class="navbar-inner">
<div id="toc-scroll-target" class="container">
<ul id="toc" class="nav">
<li class="dropdown">
<a href="#Checking_Out_the_Jersey_Sources" title="Checking Out the Jersey Sources" class="dropdown-toggle" role="button" data-toggle="dropdown" data-target="#">Checking Out the Jersey Sources <b class="caret"></b></a>
<ul class="dropdown-menu" role="menu">
<!-- Repeat the item, otherwise it is not clickable as the dropdown root -->
<li><a href="#Checking_Out_the_Jersey_Sources" title="Checking Out the Jersey Sources">Checking Out the Jersey Sources</a></li>
<li class="divider"></li>
<li><a href="#Checking_out_Jersey_2x_sources" title="Checking out Jersey 2.x sources">Checking out Jersey 2.x sources</a></li>
<li><a href="#Checking_out_Jersey_1x_sources" title="Checking out Jersey 1.x sources">Checking out Jersey 1.x sources</a></li>
</ul>
</li>
<li class="divider-vertical"></li>
<li class="toplevel"><a href="#Understanding_Jersey_2x_Branches_and_Tags" title="Understanding Jersey 2.x Branches and Tags">Understanding Jersey 2.x Branches and Tags</a></li>
<li class="divider-vertical"></li>
<li class="toplevel"><a href="#Submitting_Patches_and_Contribute_Code" title="Submitting Patches and Contribute Code">Submitting Patches and Contribute Code</a></li>
<li class="divider-vertical"></li>
<li class="toplevel"><a href="#GIT_Tips_and_Tricks_for_Developers" title="GIT Tips and Tricks for Developers">GIT Tips and Tricks for Developers</a></li>
</ul>
</div>
</div>
</div>
</header>
<div class="main-body">
<div class="row">
<div class="span12">
<div class="body-content">
<div class="section">
<div class="section">
<h3 id="Checking_Out_the_Jersey_Sources">Checking Out the Jersey Sources</h3>
<div class="section">
<h4 id="Checking_out_Jersey_2x_sources">Checking out Jersey 2.x sources</h4>
<p>Jersey 2.x is based on a completely new code base that has been completely revamped. As part of this effort, Jersey has moved from SVN to modern, distributed GIT version control system. This allowed us to how the project sources on <a class="externalLink" href="http://github.com/eclipse-ee4j/jersey/">GitHub</a>. The repository can be cloned in a read-only mode by invoking:</p>
<div class="source">
<pre>git clone ssh://git@github.com:jersey/jersey.git
</pre>
</div>
<p>If you’re only interested in reading the latest version of the sources and do not wish to a) contribute code back to the repository or b) do not care about the history, you can speed up the clone process by invoking:</p>
<div class="source">
<pre>git clone --depth 1 ssh://git@github.com:jersey/jersey.git
</pre>
</div>
<p>instead. This may speed up the clone process considerably.</p>
</div>
<div class="section">
<h4 id="Checking_out_Jersey_1x_sources">Checking out Jersey 1.x sources</h4>
<p>Old Jersey 1.x source code is hosted on [GitHub][jersey1gh] too. Read-only copy can be obtained by executing:</p>
<div class="source">
<pre>git clone ssh://git@github.com:jersey/jersey-1.x.git
</pre>
</div>
<p>Jersey 1.x code base has been frozen in terms of new features. Only bug fixes and other sustaining patches are currently accepted in Jersey 1.x source code repository.</p>
</div>
</div>
<div class="section">
<h3 id="Understanding_Jersey_2x_Branches_and_Tags">Understanding Jersey 2.x Branches and Tags</h3>
<p>Tag & Branch information:</p>
<table border="0" class="bodyTable table table-striped table-hover">
<thead>
<tr class="a">
<th>Tag/Branch Name</th>
<th>Details</th>
</tr>
</thead>
<tbody>
<tr class="b">
<td>master</td>
<td>This is effectively Jersey 2.x development branch. Development of new features happens here.</td>
</tr>
<tr class="a">
<td>2.29.1</td>
<td>This is the Jersey 2.29.1 release tag. A sustaining branch for Jersey 2.29.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.29</td>
<td>This is the Jersey 2.29 release tag. A sustaining branch for Jersey 2.29 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.28</td>
<td>This is the Jersey 2.28 release tag. A sustaining branch for Jersey 2.28 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.25.1</td>
<td>This is the Jersey 2.25.1 release tag. A sustaining branch for Jersey 2.25.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.25</td>
<td>This is the Jersey 2.25 release tag. A sustaining branch for Jersey 2.25 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.24.1</td>
<td>This is the Jersey 2.24.1 release tag. A sustaining branch for Jersey 2.24.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.24</td>
<td>This is the Jersey 2.24 release tag. A sustaining branch for Jersey 2.24 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.23.2</td>
<td>This is the Jersey 2.23.2 release tag. A sustaining branch for Jersey 2.23.2 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.23.1</td>
<td>This is the Jersey 2.23.1 release tag. A sustaining branch for Jersey 2.23.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.23</td>
<td>This is the Jersey 2.23 release tag. A sustaining branch for Jersey 2.23 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.22.2</td>
<td>This is the Jersey 2.22.2 release tag. A sustaining branch for Jersey 2.22.r21 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.22.1</td>
<td>This is the Jersey 2.22.1 release tag. A sustaining branch for Jersey 2.22.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.22</td>
<td>This is the Jersey 2.22 release tag. A sustaining branch for Jersey 2.22 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.21.1</td>
<td>This is the Jersey 2.21.1 release tag. A sustaining branch for Jersey 2.21.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.21</td>
<td>This is the Jersey 2.21 release tag. A sustaining branch for Jersey 2.21 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.20</td>
<td>This is the Jersey 2.20 release tag. A sustaining branch for Jersey 2.20 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.19</td>
<td>This is the Jersey 2.19 release tag. A sustaining branch for Jersey 2.19 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.18</td>
<td>This is the Jersey 2.18 release tag. A sustaining branch for Jersey 2.18 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.17</td>
<td>This is the Jersey 2.17 release tag. A sustaining branch for Jersey 2.17 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.16</td>
<td>This is the Jersey 2.16 release tag. A sustaining branch for Jersey 2.16 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.15</td>
<td>This is the Jersey 2.15 release tag. A sustaining branch for Jersey 2.15 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.14</td>
<td>This is the Jersey 2.14 release tag. A sustaining branch for Jersey 2.14 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.13</td>
<td>This is the Jersey 2.13 release tag. A sustaining branch for Jersey 2.13 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.12</td>
<td>This is the Jersey 2.12 release tag. A sustaining branch for Jersey 2.12 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.11</td>
<td>This is the Jersey 2.11 release tag. A sustaining branch for Jersey 2.11 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.10.1</td>
<td>This is the Jersey 2.10.1 release tag. A sustaining branch for Jersey 2.10.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.10</td>
<td>This is the Jersey 2.10 release tag. A sustaining branch for Jersey 2.10 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.9.1</td>
<td>This is the Jersey 2.9.1 release tag. A sustaining branch for Jersey 2.9.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.9</td>
<td>This is the Jersey 2.9 release tag. A sustaining branch for Jersey 2.9 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.8</td>
<td>This is the Jersey 2.8 release tag. A sustaining branch for Jersey 2.8 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.7</td>
<td>This is the Jersey 2.7 release tag. A sustaining branch for Jersey 2.7 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.6</td>
<td>This is the Jersey 2.6 release tag. A sustaining branch for Jersey 2.6 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.5.1</td>
<td>This is the Jersey 2.5.1 release tag. A sustaining branch for Jersey 2.5.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.5</td>
<td>This is the Jersey 2.5 release tag. A sustaining branch for Jersey 2.5 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.4.1</td>
<td>This is the Jersey 2.4.1 release tag. A sustaining branch for Jersey 2.4.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.4</td>
<td>This is the Jersey 2.4 release tag. A sustaining branch for Jersey 2.4 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.3.1</td>
<td>This is the Jersey 2.3.1 release tag. A sustaining branch for Jersey 2.3.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.3</td>
<td>This is the Jersey 2.3 release tag. A sustaining branch for Jersey 2.3 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.2</td>
<td>This is the Jersey 2.2 release tag. A sustaining branch for Jersey 2.2 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.1</td>
<td>This is the Jersey 2.1 release tag. A sustaining branch for Jersey 2.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="a">
<td>2.0.1</td>
<td>This is the Jersey 2.0.1 release tag. A sustaining branch for Jersey 2.0.1 release will be created from the tag if necessary.</td>
</tr>
<tr class="b">
<td>2.0</td>
<td>This is the Jersey 2.0 release tag. A sustaining branch for Jersey 2.0 release will be created from the tag if necessary.</td>
</tr>
</tbody>
</table>
<p>In order to check out a branch in git, you simply need to issue <tt>git checkout <branch name></tt> (e.g. <tt>git checkout master</tt>).</p>
<p>If you’re interested in working with an existing tag, you’ll first need to issue <tt>git fetch --tags</tt> in order to obtain the tag references. After successful completion of this command, you can issue <tt>git checkout <tag name></tt>. Note that when doing so, you’ll get a message about being in a detached state - this is normal and nothing to worry about. All fetched tags can be listed using <tt>git tag -l</tt> In general, we keep our tag names inline with the released version. For example, if you wanted to checkout the tag for Jersey 2.0, the tag name would be <i>2.0</i> This convention is consistent for all branches/versions/releases.</p>
</div>
<div class="section">
<h3 id="Submitting_Patches_and_Contribute_Code">Submitting Patches and Contribute Code</h3>
<p>Contributing to Jersey project can be done in various ways: bug fixes, enhancements, new features, or even whole new extension modules. In general, all contributions must comply with following requirements:</p>
<ul>
<li> <p>All contributors must sign the <a class="externalLink" href="http://www.oracle.com/technetwork/community/oca-486395.html">Oracle Contributor Agreement</a>.</p></li>
<li> <p>Any new contribution must be associated with an existing <a class="externalLink" href="https://github.com/eclipse-ee4j/jersey/issues">Jersey issue</a>. If no existing issue has been yet opened for the problem your contribution attempts to solve, please open a new one.</p></li>
<li> <p>All bug fixes must be accompanied with a new unit test (or a set of unit tests) that reproduce the fixed issue.</p></li>
<li> <p>New large feature contributions must be accompanied with:</p>
<ul>
<li>A patch for <a class="externalLink" href="https://github.com/eclipse-ee4j/jersey/tree/master/docs/src/main/docbook/">Jersey User Guide</a> that is written in DocBook 5. Either a new chapter or a new section to existing chapter must be provided as appropriate.</li>
</ul>
<ul>
<li>At least one new <a class="externalLink" href="https://github.com/eclipse-ee4j/jersey/tree/master/examples/">example</a> demonstrating the feature.</li>
</ul></li>
</ul>
<p>For small patches (minor bug fixes, correction of typos in documentation etc.), linking a <a class="externalLink" href="https://gist.github.com/">gist</a> that contains your patch with details on what you're resolving and how you've resolved it is most convenient approach. Alternatively, especially in case of larger contributions or more significant changes in code, please follow the process of opening a new <a class="externalLink" href="https://help.github.com/articles/using-pull-requests">GitHub pull request</a>.</p>
</div>
<div class="section">
<h3 id="GIT_Tips_and_Tricks_for_Developers">GIT Tips and Tricks for Developers</h3>
<p>First, for anyone not familiar with Git, before attempting to work with the repository, we highly recommend reading the <a class="externalLink" href="http://schacon.github.com/git/gittutorial.html">Git tutorial</a>.</p>
<p>When collaborating, before you push your changes to the remote repository, it’s best to issue <tt>git pull --rebase</tt> This will ‘replay’ any changes that have occurred in the remote repository since your last pull on top of your current work. If you don’t do this, Git will perform a merge for you, however, the result of the commit will look like you’ve touched files that you haven’t. This is fine, but it generally raises a few eyebrows and makes code reviews of any patches slightly more complicated. As usual, more complications means more time spent in review.</p>
<p>There are times when you may need to move changes back and forth between branches. In cases where the code bases are very similar, you can use <tt>git cherry-pick <SHA1 of the commit to pick and apply></tt> to do this quickly.</p>
</div>
</div>
</div>
</div>
</div>
</div>
</div><!-- /container -->
<!-- Footer
================================================== -->
<footer class="well">
<div class="container">
<div class="row">
<div class="span3 bottom-nav">
<ul class="nav nav-list">
<li class="nav-header">Main</li>
<li>
<a href="index.html" title="Home">Home </a>
</li>
<li>
<a href="license.html" title="License">License </a>
</li>
<li>
<a href="using.html" title="Who's Using Jersey">Who's Using Jersey </a>
</li>
<li class="nav-header">Download</li>
<li>
<a href="download.html" title="Get Jersey">Get Jersey </a>
</li>
</ul>
</div>
<div class="span3 bottom-nav">
<ul class="nav nav-list">
<li class="nav-header">Follow</li>
<li>
<a href="https://twitter.com/gf_jersey" title="Twitter" class="externalLink">Twitter </a>
</li>
<li class="nav-header">Contribute</li>
<li>
<a href="contribute.html" title="Contribute">Contribute </a>
</li>
<li>
<a href="http://stackoverflow.com/questions/tagged/jersey" title="StackOverflow" class="externalLink">StackOverflow </a>
</li>
<li>
<a href="mailing.html" title="Mailing Lists">Mailing Lists </a>
</li>
</ul>
</div>
<div class="span3 bottom-nav">
<ul class="nav nav-list">
<li class="nav-header">Project Info</li>
<li class="active">
<a href="#" title="Source Control">Source Control </a>
</li>
<li>
<a href="https://github.com/eclipse-ee4j/jersey/issues" title="Issue Tracking" class="externalLink">Issue Tracking </a>
</li>
<li>
<a href="mailing.html" title="Mailing Lists">Mailing Lists </a>
</li>
<li>
<a href="team-list.html" title="Project Team">Project Team </a>
</li>
<li>
<a href="release-notes/index.html" title="Release Notes">Release Notes </a>
</li>
</ul>
</div>
<div class="span3 bottom-description">
<center>
<a href="https://glassfish.github.io" style="border:0; display:block">
<img src="images/glassfish_logo.png" style="width:200px; margin-bottom:20px;">
</a>
Jersey is member of <a href="https://glassfish.github.io">GlassFish</a> project.
</center>
</div>
</div>
</div>
</footer>
<div class="container subfooter">
<div class="row">
<div class="span12">
<p class="pull-right"><a href="#">Back to top</a></p>
<p class="copyright">Copyright ©2010-2022 <a href="http://oracle.com">Oracle Corporation</a>. All Rights Reserved.</p>
<p class="version-date"><span class="publishDate">Last Published: 2022-02-10. </span></p>
</div>
</div>
</div>
<!-- Le javascript
================================================== -->
<!-- Placed at the end of the document so the pages load faster -->
<!-- Fallback jQuery loading from Google CDN:
http://stackoverflow.com/questions/1014203/best-way-to-use-googles-hosted-jquery-but-fall-back-to-my-hosted-library-on-go -->
<script type="text/javascript" src="//ajax.googleapis.com/ajax/libs/jquery/1.8.3/jquery.min.js"></script>
<script type="text/javascript">
if (typeof jQuery == 'undefined')
{
document.write(unescape("%3Cscript src='.//js/jquery-3.7.1.min.js' type='text/javascript'%3E%3C/script%3E"));
}
</script>
<script src="//netdna.bootstrapcdn.com/twitter-bootstrap/2.2.2/js/bootstrap.min.js"></script>
<script src=".//js/lightbox.js"></script>
<script src=".//js/jquery.smooth-scroll.min.js"></script>
<!-- back button support for smooth scroll -->
<script src=".//js/jquery.ba-bbq.min.js"></script>
<script src="//yandex.st/highlightjs/7.3/highlight.min.js"></script>
<script src=".//js/reflow-skin.js"></script>
</body>
</html>