This is an automated email from the ASF dual-hosted git repository. dashorst pushed a commit to branch infra-28383-github-issues in repository https://gitbox.apache.org/repos/asf/wicket-site.git
commit c38d56b9af4b9dc9f2591b747fd911501688b058 Author: Martijn Dashorst <[email protected]> AuthorDate: Thu Sep 10 10:11:31 2026 +0200 Point contributors at GitHub Issues instead of JIRA (INFRA-28383) Apache Infrastructure is closing down the WICKET JIRA project, so the site should no longer send people there to file bugs. The tracker for Apache Wicket is now GitHub Issues at https://github.com/apache/wicket/issues. Source changes: * doap.rdf: <bug-database> now points at GitHub Issues. This one also feeds the project metadata on projects.apache.org. * help/index.md: both issue tracker links; "attach the output to the JIRA" becomes "to the issue". * _includes/security.md: heading renamed. The warning not to file security reports in the tracker is unchanged -- GitHub Issues are just as public as JIRA was. * contribute/patch.md: rewritten around GitHub Issues, and the "Create a patch" section is gone. Attaching a .patch file to an issue is not something GitHub supports, so pull requests are now the only route. The paragraph about git-wip-us.apache.org went with it; that host has been dead for years and only existed to explain the patch flow. * contribute/release.md: releasing a version in JIRA becomes closing the GitHub milestone, and the changelog comes from the milestone or from generated release notes. * help/reportabug.md is removed rather than updated. Nothing on the site has linked to it for years, and it described checking Wicket out of Subversion with Subclipse on Eclipse 3.4. help/index.html #reportbug covers the same ground. A 301 in .htaccess keeps the old URL working. The JIRA project stays readable as an archive, so the news archive and its thousands of WICKET-NNNN links are deliberately left alone. The two pages that tell people to search for an existing report now mention the archive alongside GitHub Issues. The generated pages under content/ are updated by hand to match. The site does not currently build from a clean checkout -- _config.yml has no url: key, which makes jekyll-target-blank 2.0.2 call URI.parse(nil) and abort -- so each regenerated page was instead verified byte for byte against a real Jekyll build. That build failure predates this change and is left for a separate fix. Co-Authored-By: Claude Opus 5 (1M context) <[email protected]> --- .htaccess | 1 + _includes/security.md | 2 +- content/.htaccess | 1 + content/contribute/patch.html | 60 +++----- content/contribute/release.html | 7 +- content/doap.rdf | 2 +- content/help/email.html | 4 +- content/help/index.html | 14 +- content/help/reportabug.html | 333 ---------------------------------------- content/help/security.html | 2 +- contribute/patch.md | 55 +++---- contribute/release.md | 6 +- doap.rdf | 2 +- help/index.md | 10 +- help/reportabug.md | 134 ---------------- 15 files changed, 70 insertions(+), 563 deletions(-) diff --git a/.htaccess b/.htaccess index 0aa68bcc..c22dc934 100644 --- a/.htaccess +++ b/.htaccess @@ -1,2 +1,3 @@ Redirect 301 /2018/05/22/wicket-8-released.html /news/2018/05/22/wicket-8-released.html +Redirect 301 /help/reportabug.html /help/#reportbug diff --git a/_includes/security.md b/_includes/security.md index e0d4a7ac..c970f564 100644 --- a/_includes/security.md +++ b/_includes/security.md @@ -24,7 +24,7 @@ private without leaking the info to any bad guys. We treat all security issues seriously and will try to fix them as soon as possible in all affected versions that we still support. -### Report normal bugs in JIRA +### Report normal bugs in our issue tracker The Security Team cannot accept regular bug reports or other queries, we ask that you use our [bug reporting page]({{site.baseurl}}/help/#reportbug) diff --git a/content/.htaccess b/content/.htaccess index 0aa68bcc..c22dc934 100644 --- a/content/.htaccess +++ b/content/.htaccess @@ -1,2 +1,3 @@ Redirect 301 /2018/05/22/wicket-8-released.html /news/2018/05/22/wicket-8-released.html +Redirect 301 /help/reportabug.html /help/#reportbug diff --git a/content/contribute/patch.html b/content/contribute/patch.html index 5451dce6..03b312ca 100644 --- a/content/contribute/patch.html +++ b/content/contribute/patch.html @@ -119,12 +119,9 @@ <div id="toc" class="toc"> <div id="toc-title"><h2>Table of Contents</h2></div> <ul> -<li class="toc--level-1 toc--section-1"><a href="#create-and-set-an-issue-on-jira"><span class="toc-number">1</span> <span class="toc-text">Create and set an issue on JIRA</span></a></li> +<li class="toc--level-1 toc--section-1"><a href="#create-an-issue"><span class="toc-number">1</span> <span class="toc-text">Create an issue</span></a></li> <li class="toc--level-1 toc--section-2"> -<a href="#time-for-some-coding"><span class="toc-number">2</span> <span class="toc-text">Time for some coding</span></a><ul> -<li class="toc--level-2 toc--section-3"><a href="#github"><span class="toc-number">2.1</span> <span class="toc-text">Create a pull request</span></a></li> -<li class="toc--level-2 toc--section-4"><a href="#create-a-patch"><span class="toc-number">2.2</span> <span class="toc-text">Create a patch</span></a></li> -</ul> +<a href="#time-for-some-coding"><span class="toc-number">2</span> <span class="toc-text">Time for some coding</span></a><ul><li class="toc--level-2 toc--section-3"><a href="#github"><span class="toc-number">2.1</span> <span class="toc-text">Create a pull request</span></a></li></ul> </li> </ul> </div> @@ -134,10 +131,9 @@ <p>As developers we all strive to produce a flawless software. However, in the real world we might find that our code contains errors or bugs. -Wicket like many other Apache projects uses -<a href="https://issues.apache.org/jira/browse/WICKET"; target="_blank" rel="noopener noreferrer">JIRA</a> to track bugs and -new feature. If you think you have found a bug follow these simple -steps before opening a new issue on JIRA:</p> +Wicket tracks bugs and new features in <a href="https://github.com/apache/wicket/issues"; target="_blank" rel="noopener noreferrer">GitHub +Issues</a>. If you think you have +found a bug follow these simple steps before opening a new issue:</p> <ul> <li> @@ -145,8 +141,11 @@ steps before opening a new issue on JIRA:</p> fixed</p> </li> <li> - <p>Search <a href="https://issues.apache.org/jira/browse/WICKET"; target="_blank" rel="noopener noreferrer">JIRA</a> and the -mailing list to see if it’s already been discussed</p> + <p>Search <a href="https://github.com/apache/wicket/issues?q=is%3Aissue"; target="_blank" rel="noopener noreferrer">our issues</a> +and the mailing list to see if it’s already been discussed. Issues +reported before 2026 live in our read-only <a href="https://issues.apache.org/jira/browse/WICKET"; target="_blank" rel="noopener noreferrer">JIRA +archive</a>, which is worth +searching too.</p> </li> <li> <p>Simply ask to the <a href="mailto:[email protected]";>devs</a> mailing list @@ -154,17 +153,15 @@ if you are unsure.</p> </li> </ul> -<h2 id="create-and-set-an-issue-on-jira">Create and set an issue on JIRA</h2> +<h2 id="create-an-issue">Create an issue</h2> <p>Either you have spotted a bug or you want to propose a new feature, the -first thing to do is to create and set an issue on JIRA with the -following steps:</p> +first thing to do is to create an issue with the following steps:</p> <ul> <li> - <p>Create a new <a href="https://issues.apache.org/jira/browse/WICKET"; target="_blank" rel="noopener noreferrer">JIRA -issue</a>. The issue might -alredy exist if you have found a regression.</p> + <p>Create a new <a href="https://github.com/apache/wicket/issues/new"; target="_blank" rel="noopener noreferrer">issue</a>. The +issue might already exist if you have found a regression.</p> </li> <li> <p>Write a short description of the issue. If this one is a bug, report @@ -180,12 +177,9 @@ prototyping the feature or demonstrating the bug.</p> <p>Wicket uses <a href="http://git-scm.com/"; target="_blank" rel="noopener noreferrer">Git</a> as versioning system, so you need to have it properly installed and configured to start work on -Wicket code base. The main git repository is hosted on <a href="https://git-wip-us.apache.org/repos/asf/wicket.git"; target="_blank" rel="noopener noreferrer">Apache git -server</a> but is -mirrored on <a href="https://github.com/apache/wicket"; target="_blank" rel="noopener noreferrer">GitHub</a>. To work on -Wicket code you can decide to create a pull request forking the GitHub -mirror or you can clone the official repository and generate a patch -file.</p> +Wicket code base. The repository lives on +<a href="https://github.com/apache/wicket"; target="_blank" rel="noopener noreferrer">GitHub</a>, and contributions reach us +as pull requests against it.</p> <p><strong>NOTE:</strong> when you are working on Wicket code, please follow our code format rules. You can find them inside wicket-core module as Eclipse code formatter profile.</p> @@ -197,28 +191,16 @@ the format rules.</p> <h3 id="github">Create a pull request</h3> <p>To create a pull request on GitHub follow the instructions you can find -<a href="https://help.github.com/articles/creating-a-pull-request/"; target="_blank" rel="noopener noreferrer">here</a>. Once -you have finished to work on you pull request, send us an email using +<a href="https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork"; target="_blank" rel="noopener noreferrer">here</a>. +Mention the issue your work addresses in the description, so that the +pull request and the issue link up. Once you have finished to work on +your pull request, send us an email using the <a href="mailto:[email protected]";>devs</a> mailing list.</p> <p>All Pull Requests are automatically tested at <a href="https://github.com/apache/wicket/actions"; target="_blank" rel="noopener noreferrer">Github Actions</a> on AMD64 and at <a href="https://travis-ci.com/github/apache/wicket/"; target="_blank" rel="noopener noreferrer">TravisCI</a> on ARM64 platform.</p> -<h3 id="create-a-patch">Create a patch</h3> - -<p>If you prefer to work on our main repository, <a href="../start/download.html#snapshots-and-latest-bleeding-edge-code">clone it with -Git</a> -and when you have finished your work create a patch with the following -commands:</p> - -<figure class="highlight"><pre><code class="language-console" data-lang="console"><span class="go">git add any_files_you_created_modified_or_deleted -</span><span class="gp">git diff --cached ></span><span class="w"> </span>/tmp/WICKET-NNNN.patch</code></pre></figure> - -<p>where NNNN is the issue number. Finally, attach that file -(/tmp/WICKET-NNNN.patch) to the -<a href="https://issues.apache.org/jira/browse/WICKET"; target="_blank" rel="noopener noreferrer">JIRA</a></p> - </section> </div> diff --git a/content/contribute/release.html b/content/contribute/release.html index 0ed21610..7d3d1273 100644 --- a/content/contribute/release.html +++ b/content/contribute/release.html @@ -324,11 +324,10 @@ cd .. <h4 id="preparing-1">Preparing</h4> <ul> - <li>Ask the dev@ mailing list if there are any issues that still need to be in the release (looking at JIRA is a good start)</li> - <li> -<a href="https://issues.apache.org/jira/plugins/servlet/project-config/WICKET/versions"; target="_blank" rel="noopener noreferrer">Release</a> the version in JIRA</li> + <li>Ask the dev@ mailing list if there are any issues that still need to be in the release (the <a href="https://github.com/apache/wicket/milestones"; target="_blank" rel="noopener noreferrer">milestone</a> for the version is a good start)</li> + <li>Close the <a href="https://github.com/apache/wicket/milestones"; target="_blank" rel="noopener noreferrer">milestone</a> for the version once its issues are done</li> <li>Assuming there are none, and you are now in build mode, update the CHANGELOG-x.y file -(you can use JIRA for this list: go to “releases”, and under “unreleased”, next to your version, there’s a release notes link)</li> +(you can use the closed milestone for this list, or let GitHub generate release notes for the release tag)</li> </ul> <p>Make sure your <code class="language-plaintext highlighter-rouge">~/.m2/settings.xml</code> contains the following definition</p> diff --git a/content/doap.rdf b/content/doap.rdf index 6a9239fb..6750f772 100644 --- a/content/doap.rdf +++ b/content/doap.rdf @@ -17,7 +17,7 @@ <asfext:pmc rdf:resource="https://wicket.apache.org/"/> <shortdesc>Apache Wicket is an open source Java component oriented web application framework.</shortdesc> <description>Write maintainable, secure and scalable web applications using just Java and HTML. Invented in 2004, Wicket is one of the few survivors of the Java serverside web framework wars of the mid 2000's, and a proud member of the Apache Software Foundation.</description> - <bug-database rdf:resource="https://issues.apache.org/jira/browse/WICKET"/> + <bug-database rdf:resource="https://github.com/apache/wicket/issues"/> <mailing-list rdf:resource="https://wicket.apache.org"/> <download-page rdf:resource="https://wicket.apache.org"/> <programming-language>Java</programming-language> diff --git a/content/help/email.html b/content/help/email.html index d7b63250..bf4f22fa 100644 --- a/content/help/email.html +++ b/content/help/email.html @@ -128,7 +128,7 @@ <li class="toc--level-1 toc--section-6"> <a href="#security"><span class="toc-number">6</span> <span class="toc-text">Report a security issue</span></a><ul> <li class="toc--level-2 toc--section-7"><a href="#contact-the-wicket-pmc-privately"><span class="toc-number">6.1</span> <span class="toc-text">Contact the Wicket PMC privately</span></a></li> -<li class="toc--level-2 toc--section-8"><a href="#report-normal-bugs-in-jira"><span class="toc-number">6.2</span> <span class="toc-text">Report normal bugs in JIRA</span></a></li> +<li class="toc--level-2 toc--section-8"><a href="#report-normal-bugs-in-our-issue-tracker"><span class="toc-number">6.2</span> <span class="toc-text">Report normal bugs in our issue tracker</span></a></li> </ul> </li> </ul> @@ -286,7 +286,7 @@ private without leaking the info to any bad guys.</p> <p>We treat all security issues seriously and will try to fix them as soon as possible in all affected versions that we still support.</p> -<h3 id="report-normal-bugs-in-jira">Report normal bugs in JIRA</h3> +<h3 id="report-normal-bugs-in-our-issue-tracker">Report normal bugs in our issue tracker</h3> <p>The Security Team cannot accept regular bug reports or other queries, we ask that you use our <a href="/help/#reportbug">bug reporting page</a> diff --git a/content/help/index.html b/content/help/index.html index 0ff1644f..c9a200e0 100644 --- a/content/help/index.html +++ b/content/help/index.html @@ -124,7 +124,7 @@ <li class="toc--level-1 toc--section-2"> <a href="#security"><span class="toc-number">2</span> <span class="toc-text">Report A Security Problem</span></a><ul> <li class="toc--level-2 toc--section-3"><a href="#contact-the-wicket-pmc-privately"><span class="toc-number">2.1</span> <span class="toc-text">Contact the Wicket PMC privately</span></a></li> -<li class="toc--level-2 toc--section-4"><a href="#report-normal-bugs-in-jira"><span class="toc-number">2.2</span> <span class="toc-text">Report normal bugs in JIRA</span></a></li> +<li class="toc--level-2 toc--section-4"><a href="#report-normal-bugs-in-our-issue-tracker"><span class="toc-number">2.2</span> <span class="toc-text">Report normal bugs in our issue tracker</span></a></li> </ul> </li> <li class="toc--level-1 toc--section-5"> @@ -221,7 +221,7 @@ private without leaking the info to any bad guys.</p> <p>We treat all security issues seriously and will try to fix them as soon as possible in all affected versions that we still support.</p> -<h3 id="report-normal-bugs-in-jira">Report normal bugs in JIRA</h3> +<h3 id="report-normal-bugs-in-our-issue-tracker">Report normal bugs in our issue tracker</h3> <p>The Security Team cannot accept regular bug reports or other queries, we ask that you use our <a href="/help/#reportbug">bug reporting page</a> @@ -232,7 +232,7 @@ for normal, non-security bugs.</p> <h2 id="reportbug">Report a Bug for Apache Wicket</h2> <p>If you are experiencing problems using Wicket please report your -problem via the <a href="https://issues.apache.org/jira/browse/WICKET"; target="_blank" rel="noopener noreferrer">Issue +problem via the <a href="https://github.com/apache/wicket/issues"; target="_blank" rel="noopener noreferrer">Issue Tracker</a>. You may also find it useful to discuss your issues with the community on one of the Mailing Lists.</p> @@ -264,7 +264,11 @@ anyway, so you might as well get them out of the way.</p> encountered your issue. So please search for some keywords of your problem using a search engine, <a href="http://stackoverflow.com/questions/tagged/wicket"; target="_blank" rel="noopener noreferrer">stackoverflow</a> and our -<a href="https://issues.apache.org/jira/browse/WICKET"; target="_blank" rel="noopener noreferrer">issue tracker</a>.</p> +<a href="https://github.com/apache/wicket/issues?q=is%3Aissue"; target="_blank" rel="noopener noreferrer">issue tracker</a>.</p> + +<p>Note that issues reported before 2026 live in our read-only <a href="https://issues.apache.org/jira/browse/WICKET"; target="_blank" rel="noopener noreferrer">JIRA +archive</a>, so it is worth +searching there as well.</p> <p>If someone already found your bug, look at how the bug was resolved. If it wasn’t resolved, note what they already tried and add your own @@ -384,7 +388,7 @@ demonstrate the bug?</li> <li>Submit a patch fixing the bug! (We also buy you beer when we meet you if you submit bug fixes for memory leaks or performance related issues, if you can run a profiler on your test case and attach the -output as a file (or zipped file if its huge) to the JIRA we can +output as a file (or zipped file if its huge) to the issue we can normally fix things much faster. e.g. run JProfiler or YourKit on your code and send us the output. To find memory leaks its quicker to resolve if you can tell us what classes are taking up all of the RAM; diff --git a/content/help/reportabug.html b/content/help/reportabug.html deleted file mode 100644 index 37f058f9..00000000 --- a/content/help/reportabug.html +++ /dev/null @@ -1,333 +0,0 @@ -<!DOCTYPE html> -<html lang="en"> - <head> - <meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1"> - <meta charset="utf-8"> - - - - <title>Report a bug | Apache Wicket</title> - <meta name="viewport" content="width=device-width, initial-scale=1" /> - - <link rel="shortcut icon" href="/favicon.ico" type="image/vnd.microsoft.icon" /> - <link rel="stylesheet" href="/css/style.css" type="text/css" media="screen" /> - <link href="/css/font-awesome.min.css" rel="stylesheet" /> - - <script src="/javascript/jquery-3.7.1.min.js"></script> - - - </head> - <body class=""> - <div class="header default"> - <div class="l-container"> - -<nav class="mainmenu"> - <div class="nav-logo"> - <a href="/"><img src="/img/logo-apachewicket.svg" alt="Apache Wicket"></a> -</div> - - <div class="nav-container"> - - - - - - <!-- /start/quickstart.html || /help/reportabug --> - - - - <a href="/start/quickstart.html" class=" nav-items">Quick Start</a> - - - - - - <!-- /start/download.html || /help/reportabug --> - - - - <a href="/start/download.html" class=" nav-items">Download</a> - - - - - - <!-- /learn || /help/reportabug --> - - - - <a href="/learn" class=" nav-items">Documentation</a> - - - - - - <!-- /help || /help/reportabug --> - - - - <a href="/help" class=" nav-items">Support</a> - - - - - - <!-- /contribute || /help/reportabug --> - - - - <a href="/contribute" class=" nav-items">Contribute</a> - - - - - - <!-- /community || /help/reportabug --> - - - - <a href="/community" class=" nav-items">Community</a> - - - - - - <!-- /apache || /help/reportabug --> - - - - <a href="/apache" class=" nav-items">Apache</a> - - </div> - <div class="nav-container "> - <a href="https://github.com/apache/wicket"; rel="noreferrer noopener noreferrer" target="_blank"><i class="fa fa-github nav-items"></i></a> - <a href="https://builtwithwicket.tumblr.com"; rel="noreferrer noopener noreferrer" target="_blank"><i class="fa fa-tumblr nav-items"></i></a> - </div> -</nav> - - </div> -</div> -<main> - <div class="l-container"> - <header class="l-full preamble"> - <h1>Report a bug</h1> - - - - </header> - <section class="toc left default "> - <div id="toc" class="toc"> -<div id="toc-title"><h2>Table of Contents</h2></div> -<ul> -<li class="toc--level-1 toc--section-1"><a href="#build-a-quickstart"><span class="toc-number">1</span> <span class="toc-text">Build a Quickstart</span></a></li> -<li class="toc--level-1 toc--section-2"> -<a href="#submit-a-patch"><span class="toc-number">2</span> <span class="toc-text">Submit a patch</span></a><ul> -<li class="toc--level-2 toc--section-3"><a href="#setting-up"><span class="toc-number">2.1</span> <span class="toc-text">Setting up</span></a></li> -<li class="toc--level-2 toc--section-4"><a href="#checking-out-wicket-from-subversion"><span class="toc-number">2.2</span> <span class="toc-text">Checking out Wicket from Subversion</span></a></li> -<li class="toc--level-2 toc--section-5"><a href="#kick-the-tires"><span class="toc-number">2.3</span> <span class="toc-text">Kick the tires</span></a></li> -<li class="toc--level-2 toc--section-6"><a href="#proving-a-bug-exists"><span class="toc-number">2.4</span> <span class="toc-text">Proving a bug exists</span></a></li> -<li class="toc--level-2 toc--section-7"><a href="#submitting-a-patch"><span class="toc-number">2.5</span> <span class="toc-text">Submitting a patch</span></a></li> -</ul> -</li> -</ul> -</div> - </section> - <section> - <p>Wicket manages bug reports via the <a href="http://issues.apache.org/jira/browse/WICKET"; target="_blank" rel="noopener noreferrer">Apache Jira site</a></p> - -<p>It requires you to register with the site, to avoid spamming, and attribute -credit where its due. It’s relatively painless. Much harder is writing a -clear and concise bug report.</p> - -<p>Etiquette for a bug report is:</p> - -<ol> - <li> -<strong>Always search for an existing bug report about the issue before adding -your own.</strong> This can be tricky, but several duplicate bug reports just -cause an administration headache for developers. If in doubt you can -always post the details of the bug to the <a href="email.html">mailing list</a>, and -wait to be asked to submit a bug report by a dev. But the jira search -functionality is pretty good, so do have go.</li> - <li> -<strong>Be clear and concise in your language.</strong> Wording a short but useful -summary, with a description that contains all the steps leading up to the -error plus any extra circumstantial evidence, is not always easy, but its -vital to getting the issue resolved, and really valuable.</li> - <li> -<strong>Watch the bug.</strong> The developers may ask you for more information via the -issue comments, so its good practices to check in on the issue whilst its -still open.</li> - <li> -<strong>Don’t be shy of maintaining the issue.</strong> If you find its a duplicate of -some other issue that was reported before yours, then mark it as a -duplicate, and watch the original. If you get more info on the bug, add it -as a comment. If it doesnt get noticed by a dev, try submitting a -quickstart or better still a patch. Ask for it to be reviewed via the -mailing list.</li> -</ol> - -<p>You will be rewarded with <a href="https://issues.apache.org/jira/secure/ConfigureReport.jspa?versionId=-1&issueStatus=all&selectedProjectId=12310561&reportKey=com.sourcelabs.jira.plugin.report.contributions%3Acontributionreport&Next=Next"; target="_blank" rel="noopener noreferrer">subtle kudos</a> -and the bug is much more likely to be fixed promptly.</p> - -<h2 id="build-a-quickstart">Build a Quickstart</h2> - -<p>See <a href="/start/quickstart.html">getting started</a> for a good introduction to -building a barebone Wicket project from one command. There is even a tool to -let you customise the command for your project.</p> - -<p>Or you can watch Al Maw’s excellent -<a href="http://herebebeasties.com/2007-10-07/wicket-quickstart"; target="_blank" rel="noopener noreferrer">screencast</a> covering -the whole process of installing and running Maven, and getting your Eclipse -workspace set up.</p> - -<p>The Maven command provided there is the quickest way to get a working Wicket -project that you can use to clearly demonstrate a bug.</p> - -<p>Once you have an example that shows the minimum conditions under which the -issue occurs, then you can zip up the project and attach it to the relevant -issue.</p> - -<p>When a Wicket dev <a href="https://issues.apache.org/jira/browse/WICKET-497?focusedCommentId=12521870&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12521870"; target="_blank" rel="noopener noreferrer">asks you to submit a quickstart</a>, -that is what they mean.</p> - -<p>That is far more useful than posting reams of your application code and -telling everyone it doesn’t work. The former will help diagnose the problem, -the latter will mainly get you abused on the mailing list.</p> - -<h2 id="submit-a-patch">Submit a patch</h2> - -<p>This is the most involved, but the most rewarding route ;-). -In a nutshell this involves:</p> -<ul> - <li>Checking out the Wicket source code from the Subversion repository.</li> - <li>Building it via mvn or IDE plugin.</li> - <li>Proving the bug exists, either via a Quickstart, or writing a unit test.</li> - <li>Submitting your fix as a Subversion patch file.</li> -</ul> - -<p>This guide will outline how to do it with Eclipse + Subclipse + m2eclipse. -If you prefer the command line, then start here: <a href="/contribute/build.html">building from source</a> -If you can provide a walk through for your IDE of choice then please do add it.</p> - -<h3 id="setting-up">Setting up</h3> - -<p>Using an Eclipse 3.4.x flavour of your choice add install the following plugins</p> - -<ul> - <li> -<a href="http://subclipse.tigris.org/"; target="_blank" rel="noopener noreferrer">Subclipse for accessing Subversion</a> - Eclipse update site URL http://subclipse.tigris.org/update_1.6.x</li> - <li> -<a href="http://m2eclipse.sonatype.org/"; target="_blank" rel="noopener noreferrer">m2eclipse for maven support</a> - Eclipse update site: http://m2eclipse.sonatype.org/update/</li> -</ul> - -<p>I usually install the entire Subclipse plugin, and all of m2eclipse except the Project configurators unless I am using a J2EE version of Eclipse. -I had a spurious error when adding the m2eclipse update site, “No repository found at http://www.md.pp.ru/~eu/12/” but it didn’t cause any problems with the install.</p> - -<h3 id="checking-out-wicket-from-subversion">Checking out Wicket from Subversion</h3> - -<ul> - <li> - <p><strong>Add the Wicket Subversion repository</strong> - Navigate to Window > Show -Perspective > Other… > SVN Repository Exploring (eclipse uses the term -perspective to mean a collection of views, and a view is one single panel -with some specific function like the navigator view or the editor view) In -the SVN Repositories tab on the left, right click > New > Repository -Location… and paste in the repository url: -http://svn.apache.org/repos/asf/wicket</p> - </li> - <li> -<strong>Checkout the code</strong> - Click on the new Repository and navigate to: trunk - <blockquote> - <p>right click > checkout as maven project. Some serious churning will now -occur as you download of Wicket source, and then maven crawls the internet -for all the required libraries. Seriously, go for a stroll in the sunshine; -the checkout and build took about 6minutes on my machine, and thats without -maven needing to download anything.</p> - </blockquote> - </li> - <li> -<strong>Building Wicket</strong> - All that waiting wasn’t in vain, as you should now -have a fully checked out, dependency managed, built, possibly working, -Wicket code base.</li> -</ul> - -<h3 id="kick-the-tires">Kick the tires</h3> - -<ul> - <li>Create a Quickstart via the wicket-archetype-quickstart</li> - <li>Navigate to the pom.xml in your Quickstart project.</li> - <li>Set version element to the same value as the one found in the Wicket project pom.xml (e.g. 1.4-SNAPSHOT)</li> - <li>The plugin should automagically resolve the quickstart’s Wicket dependency from the project rather than a .jar</li> - <li>Find WicketApplication.java</li> - <li>Click through to WebApplication class from the extends section of the class definition.</li> - <li>If all is well, you should be taken to the Wicket project .java version of WebApplication rather than a .class file from a .jar</li> -</ul> - -<h3 id="proving-a-bug-exists">Proving a bug exists</h3> - -<ul> - <li><strong>Writing a unit test with WicketTester</strong></li> -</ul> - -<h3 id="submitting-a-patch">Submitting a patch</h3> - -<ul> - <li> - <p><strong>Extract your changeset into a patch file</strong> - As we don’t all have commit -access to the svn repository, we need some other way of getting our changes -to the developers. This is done by making an svn patch file, essentially a -plain text diff, with some subversion specific formatting. With the -Subclipse plug-in creating a patch file is as simple as:</p> - - <ol> - <li>Right click on the project root (e.g. wicket)</li> - <li> - <blockquote> - <p>Team > Create Patch…</p> - </blockquote> - </li> - <li>Save In File System (and provide a filename, of the form <strong>WICKET-<bug id number>-fix.patch</strong>)</li> - <li> - <blockquote> - <p>Next ></p> - </blockquote> - </li> - <li>Patch Root: Project</li> - <li>Finish, you now have your patch file where you chose to put it in step 3</li> - <li>Attach it to the relevant bug report with any further information you have</li> - </ol> - </li> -</ul> - - - </section> - </div> -</main> - - <footer> - <div class="l-container l-flex"> - <div class="l-one-third left"> - <a href="https://www.apache.org"; target="_blank" rel="noopener noreferrer">Apache</a><br> - <a href="https://www.apache.org/licenses/"; target="_blank" rel="noopener noreferrer">License</a><br> - <a href="https://events.apache.org/x/current-event"; target="_blank" rel="noopener noreferrer">Events</a><br> - </div> - <div class="l-one-third"> - <a href="https://www.apache.org/foundation/sponsorship"; target="_blank" rel="noopener noreferrer">Sponsorships</a><br> - <a href="https://www.apache.org/foundation/thanks"; target="_blank" rel="noopener noreferrer">Thanks</a><br> - </div> - <div class="l-one-third"> - <a href="https://www.apache.org/security"; target="_blank" rel="noopener noreferrer">Security</a><br> - <a href="https://privacy.apache.org/policies/privacy-policy-public.html"; target="_blank" rel="noopener noreferrer">Privacy</a><br> - </div> -</div> -<div class="l-container"> - <div class="left"> - <img src="https://www.apache.org/img/asf_logo.png"; style="height:90px; float:left; margin-right:10px;"> - <div style="margin-top:12px;">Copyright © 2026 — The Apache Software Foundation. Apache Wicket, Wicket, Apache, the Apache feather logo, and the Apache Wicket project logo are trademarks of The Apache Software Foundation. All other marks mentioned may be trademarks or registered trademarks of their respective owners.</div> - </div> -</div> - - </footer> - </body> -</html> diff --git a/content/help/security.html b/content/help/security.html index c9062849..4e16b124 100644 --- a/content/help/security.html +++ b/content/help/security.html @@ -147,7 +147,7 @@ private without leaking the info to any bad guys.</p> <p>We treat all security issues seriously and will try to fix them as soon as possible in all affected versions that we still support.</p> -<h3 id="report-normal-bugs-in-jira">Report normal bugs in JIRA</h3> +<h3 id="report-normal-bugs-in-our-issue-tracker">Report normal bugs in our issue tracker</h3> <p>The Security Team cannot accept regular bug reports or other queries, we ask that you use our <a href="/help/#reportbug">bug reporting page</a> diff --git a/contribute/patch.md b/contribute/patch.md index b19dbf9f..9d75fda9 100644 --- a/contribute/patch.md +++ b/contribute/patch.md @@ -7,29 +7,29 @@ title: Improve Wicket with fixes and new features! As developers we all strive to produce a flawless software. However, in the real world we might find that our code contains errors or bugs. -Wicket like many other Apache projects uses -[JIRA](https://issues.apache.org/jira/browse/WICKET) to track bugs and -new feature. If you think you have found a bug follow these simple -steps before opening a new issue on JIRA: +Wicket tracks bugs and new features in [GitHub +Issues](https://github.com/apache/wicket/issues). If you think you have +found a bug follow these simple steps before opening a new issue: * Test the very last version of Wicket to see if the bug was already fixed -* Search [JIRA](https://issues.apache.org/jira/browse/WICKET) and the - mailing list to see if it's already been discussed +* Search [our issues](https://github.com/apache/wicket/issues?q=is%3Aissue) + and the mailing list to see if it's already been discussed. Issues + reported before 2026 live in our read-only [JIRA + archive](https://issues.apache.org/jira/browse/WICKET), which is worth + searching too. * Simply ask to the [devs](mailto:[email protected]) mailing list if you are unsure. -## Create and set an issue on JIRA ## +## Create an issue ## Either you have spotted a bug or you want to propose a new feature, the -first thing to do is to create and set an issue on JIRA with the -following steps: +first thing to do is to create an issue with the following steps: -* Create a new [JIRA - issue](https://issues.apache.org/jira/browse/WICKET). The issue might - alredy exist if you have found a regression. +* Create a new [issue](https://github.com/apache/wicket/issues/new). The + issue might already exist if you have found a regression. * Write a short description of the issue. If this one is a bug, report the affected version as well. @@ -41,12 +41,9 @@ following steps: Wicket uses [Git](http://git-scm.com/) as versioning system, so you need to have it properly installed and configured to start work on -Wicket code base. The main git repository is hosted on [Apache git -server](https://git-wip-us.apache.org/repos/asf/wicket.git) but is -mirrored on [GitHub](https://github.com/apache/wicket). To work on -Wicket code you can decide to create a pull request forking the GitHub -mirror or you can clone the official repository and generate a patch -file. +Wicket code base. The repository lives on +[GitHub](https://github.com/apache/wicket), and contributions reach us +as pull requests against it. **NOTE:** when you are working on Wicket code, please follow our code format rules. You can find them inside wicket-core module as Eclipse code formatter profile. @@ -58,26 +55,12 @@ the format rules. ### Create a pull request {#github} To create a pull request on GitHub follow the instructions you can find -[here](https://help.github.com/articles/creating-a-pull-request/). Once -you have finished to work on you pull request, send us an email using +[here](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request-from-a-fork). +Mention the issue your work addresses in the description, so that the +pull request and the issue link up. Once you have finished to work on +your pull request, send us an email using the [devs](mailto:[email protected]) mailing list. All Pull Requests are automatically tested at [Github Actions](https://github.com/apache/wicket/actions) on AMD64 and at [TravisCI](https://travis-ci.com/github/apache/wicket/) on ARM64 platform. - -### Create a patch ### - -If you prefer to work on our main repository, [clone it with -Git](../start/download.html#snapshots-and-latest-bleeding-edge-code) -and when you have finished your work create a patch with the following -commands: - -{% highlight console %} -git add any_files_you_created_modified_or_deleted -git diff --cached > /tmp/WICKET-NNNN.patch -{% endhighlight %} - -where NNNN is the issue number. Finally, attach that file -(/tmp/WICKET-NNNN.patch) to the -[JIRA](https://issues.apache.org/jira/browse/WICKET) diff --git a/contribute/release.md b/contribute/release.md index 1792d656..74aaaea1 100644 --- a/contribute/release.md +++ b/contribute/release.md @@ -189,10 +189,10 @@ See also [managing nexus](#nexus) for the steps needed to publish the artifacts #### Preparing ##### -* Ask the dev@ mailing list if there are any issues that still need to be in the release (looking at JIRA is a good start) -* [Release](https://issues.apache.org/jira/plugins/servlet/project-config/WICKET/versions) the version in JIRA +* Ask the dev@ mailing list if there are any issues that still need to be in the release (the [milestone](https://github.com/apache/wicket/milestones) for the version is a good start) +* Close the [milestone](https://github.com/apache/wicket/milestones) for the version once its issues are done * Assuming there are none, and you are now in build mode, update the CHANGELOG-x.y file -(you can use JIRA for this list: go to "releases", and under "unreleased", next to your version, there's a release notes link) +(you can use the closed milestone for this list, or let GitHub generate release notes for the release tag) Make sure your ```~/.m2/settings.xml``` contains the following definition diff --git a/doap.rdf b/doap.rdf index bee3f663..3c5b4328 100644 --- a/doap.rdf +++ b/doap.rdf @@ -20,7 +20,7 @@ layout: null <asfext:pmc rdf:resource="https://wicket.apache.org/"/> <shortdesc>Apache Wicket is an open source Java component oriented web application framework.</shortdesc> <description>Write maintainable, secure and scalable web applications using just Java and HTML. Invented in 2004, Wicket is one of the few survivors of the Java serverside web framework wars of the mid 2000's, and a proud member of the Apache Software Foundation.</description> - <bug-database rdf:resource="https://issues.apache.org/jira/browse/WICKET"/> + <bug-database rdf:resource="https://github.com/apache/wicket/issues"/> <mailing-list rdf:resource="https://wicket.apache.org"/> <download-page rdf:resource="https://wicket.apache.org"/> <programming-language>Java</programming-language> diff --git a/help/index.md b/help/index.md index 14ece2be..c1549501 100644 --- a/help/index.md +++ b/help/index.md @@ -62,7 +62,7 @@ way](http://www.catb.org/esr/faqs/smart-questions.html). If you are experiencing problems using Wicket please report your problem via the [Issue -Tracker](https://issues.apache.org/jira/browse/WICKET). You may also +Tracker](https://github.com/apache/wicket/issues). You may also find it useful to discuss your issues with the community on one of the Mailing Lists. @@ -91,7 +91,11 @@ A lot of developers use Wicket, and chances are someone already encountered your issue. So please search for some keywords of your problem using a search engine, [stackoverflow](http://stackoverflow.com/questions/tagged/wicket) and our -[issue tracker](https://issues.apache.org/jira/browse/WICKET). +[issue tracker](https://github.com/apache/wicket/issues?q=is%3Aissue). + +Note that issues reported before 2026 live in our read-only [JIRA +archive](https://issues.apache.org/jira/browse/WICKET), so it is worth +searching there as well. If someone already found your bug, look at how the bug was resolved. If it wasn't resolved, note what they already tried and add your own @@ -195,7 +199,7 @@ We can help you much quicker if you try the following * Submit a patch fixing the bug! (We also buy you beer when we meet you if you submit bug fixes for memory leaks or performance related issues, if you can run a profiler on your test case and attach the - output as a file (or zipped file if its huge) to the JIRA we can + output as a file (or zipped file if its huge) to the issue we can normally fix things much faster. e.g. run JProfiler or YourKit on your code and send us the output. To find memory leaks its quicker to resolve if you can tell us what classes are taking up all of the RAM; diff --git a/help/reportabug.md b/help/reportabug.md deleted file mode 100644 index e308c7ce..00000000 --- a/help/reportabug.md +++ /dev/null @@ -1,134 +0,0 @@ ---- -layout: default -title: Report a bug ---- - -Wicket manages bug reports via the [Apache Jira site](http://issues.apache.org/jira/browse/WICKET) - -It requires you to register with the site, to avoid spamming, and attribute -credit where its due. It's relatively painless. Much harder is writing a -clear and concise bug report. - -Etiquette for a bug report is: - -1. **Always search for an existing bug report about the issue before adding - your own.** This can be tricky, but several duplicate bug reports just - cause an administration headache for developers. If in doubt you can - always post the details of the bug to the [mailing list](email.html), and - wait to be asked to submit a bug report by a dev. But the jira search - functionality is pretty good, so do have go. -2. **Be clear and concise in your language.** Wording a short but useful - summary, with a description that contains all the steps leading up to the - error plus any extra circumstantial evidence, is not always easy, but its - vital to getting the issue resolved, and really valuable. -3. **Watch the bug.** The developers may ask you for more information via the - issue comments, so its good practices to check in on the issue whilst its - still open. -4. **Don't be shy of maintaining the issue.** If you find its a duplicate of - some other issue that was reported before yours, then mark it as a - duplicate, and watch the original. If you get more info on the bug, add it - as a comment. If it doesnt get noticed by a dev, try submitting a - quickstart or better still a patch. Ask for it to be reviewed via the - mailing list. - -You will be rewarded with [subtle kudos](https://issues.apache.org/jira/secure/ConfigureReport.jspa?versionId=-1&issueStatus=all&selectedProjectId=12310561&reportKey=com.sourcelabs.jira.plugin.report.contributions%3Acontributionreport&Next=Next) -and the bug is much more likely to be fixed promptly. - -## Build a Quickstart - -See [getting started](/start/quickstart.html) for a good introduction to -building a barebone Wicket project from one command. There is even a tool to -let you customise the command for your project. - -Or you can watch Al Maw's excellent -[screencast](http://herebebeasties.com/2007-10-07/wicket-quickstart) covering -the whole process of installing and running Maven, and getting your Eclipse -workspace set up. - -The Maven command provided there is the quickest way to get a working Wicket -project that you can use to clearly demonstrate a bug. - -Once you have an example that shows the minimum conditions under which the -issue occurs, then you can zip up the project and attach it to the relevant -issue. - -When a Wicket dev [asks you to submit a quickstart](https://issues.apache.org/jira/browse/WICKET-497?focusedCommentId=12521870&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12521870), -that is what they mean. - -That is far more useful than posting reams of your application code and -telling everyone it doesn't work. The former will help diagnose the problem, -the latter will mainly get you abused on the mailing list. - -## Submit a patch ## - -This is the most involved, but the most rewarding route ;-). -In a nutshell this involves: - * Checking out the Wicket source code from the Subversion repository. - * Building it via mvn or IDE plugin. - * Proving the bug exists, either via a Quickstart, or writing a unit test. - * Submitting your fix as a Subversion patch file. - -This guide will outline how to do it with Eclipse + Subclipse + m2eclipse. -If you prefer the command line, then start here: [building from source](/contribute/build.html) -If you can provide a walk through for your IDE of choice then please do add it. - -### Setting up ### - -Using an Eclipse 3.4.x flavour of your choice add install the following plugins - -* [Subclipse for accessing Subversion](http://subclipse.tigris.org/) - Eclipse update site URL http://subclipse.tigris.org/update_1.6.x -* [m2eclipse for maven support](http://m2eclipse.sonatype.org/) - Eclipse update site: http://m2eclipse.sonatype.org/update/ - -I usually install the entire Subclipse plugin, and all of m2eclipse except the Project configurators unless I am using a J2EE version of Eclipse. -I had a spurious error when adding the m2eclipse update site, "No repository found at http://www.md.pp.ru/~eu/12/"; but it didn't cause any problems with the install. - -### Checking out Wicket from Subversion ### - -* **Add the Wicket Subversion repository** - Navigate to Window > Show - Perspective > Other... > SVN Repository Exploring (eclipse uses the term - perspective to mean a collection of views, and a view is one single panel - with some specific function like the navigator view or the editor view) In - the SVN Repositories tab on the left, right click > New > Repository - Location... and paste in the repository url: - http://svn.apache.org/repos/asf/wicket - -* **Checkout the code** - Click on the new Repository and navigate to: trunk - > right click > checkout as maven project. Some serious churning will now - occur as you download of Wicket source, and then maven crawls the internet - for all the required libraries. Seriously, go for a stroll in the sunshine; - the checkout and build took about 6minutes on my machine, and thats without - maven needing to download anything. - -* **Building Wicket** - All that waiting wasn't in vain, as you should now - have a fully checked out, dependency managed, built, possibly working, - Wicket code base. - -### Kick the tires ### - -* Create a Quickstart via the wicket-archetype-quickstart -* Navigate to the pom.xml in your Quickstart project. -* Set version element to the same value as the one found in the Wicket project pom.xml (e.g. 1.4-SNAPSHOT) -* The plugin should automagically resolve the quickstart's Wicket dependency from the project rather than a .jar -* Find WicketApplication.java -* Click through to WebApplication class from the extends section of the class definition. -* If all is well, you should be taken to the Wicket project .java version of WebApplication rather than a .class file from a .jar - -### Proving a bug exists ### - -* **Writing a unit test with WicketTester** - -### Submitting a patch ### - -* **Extract your changeset into a patch file** - As we don't all have commit - access to the svn repository, we need some other way of getting our changes - to the developers. This is done by making an svn patch file, essentially a - plain text diff, with some subversion specific formatting. With the - Subclipse plug-in creating a patch file is as simple as: - - 1. Right click on the project root (e.g. wicket) - 2. > Team > Create Patch... - 3. Save In File System (and provide a filename, of the form **WICKET-<bug id number>-fix.patch**) - 4. > Next > - 5. Patch Root: Project - 6. Finish, you now have your patch file where you chose to put it in step 3 - 7. Attach it to the relevant bug report with any further information you have
![https://www.apache.org/img/asf_logo.png"](https://www.apache.org/img/asf_logo.png"){kind=link}