Simplest way to get started is to create a Github account, which is where wicket is hosted, setup the github app on your PC if using windows. Then just fork wicket to your personal github account. After that just use the app to download to your PC make changes push the changes back to your fork, then create a pull request.
On Fri, Jul 11, 2014 at 5:16 PM, Garret Wilson <gar...@globalmentor.com> wrote: > On 7/11/2014 2:25 AM, Martin Grigorov wrote: > >> ... >> >> I recommend you to use Wicket 7.0.0-M2 for new development. >> It is quite stable! I use it for a personal applications. >> > > That sounds great! I'm going to update my client's project to the 7.0 > release stream and go from there. I've already signed up on JIRA today. > > I have a few clarification questions: > > * Do we only have access to the source via Git, or is there a Subversion > repository as well? > * How often is the Maven SNAPSHOT repository updated? Is there a nightly > or weekly build pushed to Maven? I ask because it would be nice if my > client's official build would pull Wicket from some Maven repository rather > than being linked to the actual source code, and if make a contribution it > would be nice for it to propagate quickly to some official download, even > if only a nightly. > * If I just set my POM to point to the SNAPSHOT repository, will it just > automatically pull down new versions, or is there something else I need to > do? > > (I don't want to take this thread too far off topic; feel free to respond > privately if you wish.) > > > > The benefit is that some of these things are improved there (e.g. p.1) and >> it is possible to make more radical changes. Changing the default behavior >> for p.2 will make Wicket's HTML not so *ugly* but will break many >> applications in production. No matter how ugly is the generated code I'll >> veto such change in 6.x. >> > > Yes, I favor such an approach. I only now learned that there is a 7.x > development stream---I'll direct my contributions there. > > Best, > > Garret >
