On Sat, Jul 12, 2014 at 12:16 AM, 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? > We use Git for the code and Subversion for the site/guide (because Apache infrastructure). The main Git repo is https://git-wip-us.apache.org/repos/asf/wicket.git. It is being synchronized/mirrored to https://github.com/apache/wicket (every 2 hours, I think). * 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. > The SNAPSHOTs repo is https://repository.apache.org/content/repositories/snapshots/ After every push to https://git-wip-us.apache.org/repos/asf/wicket.git the CI server (http://ci.apache.org/builders/wicket-master) uploads the new -SNAPSHOTs to https://repository.apache.org/content/repositories/snapshots/ > * 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? > This should be enough. > > (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. > Just to make it clear: - Wicket 7.x is Git master branch - Wicket 6.x is Git 'wicket-6.x' branch > > Best, > > Garret >
