Re: License issue with wicket-debug-drag?

2007-04-10 Thread Matej Knopp
I've removed wicket-debug-drag.js, replaced it with code from modal.js. -Matej On 4/8/07, Matej Knopp [EMAIL PROTECTED] wrote: the dragging code is already in moda,js (Wicket.Drag). It shouldn't be much work to replace, I'll replace the code as soon as I find some free time. -Matej On

Getting things done before new wicket 1.3 attempt

2007-04-10 Thread Martijn Dashorst
Before we (I?) build a new release, we need to get some things done: - unit tests should run at 100% - wicket-ajax-debug-drag.js license issue should be resolved (done by Matej) - license headers in threadtest should be resolved (done by Eelco) - notice/license files in source/javadoc jars (done

Re: Movement of notice files in wicket-1.x

2007-04-10 Thread Martijn Dashorst
There is one caveat: the file should (probably) be committed in the release branch, to show in svn what we have released. It may be some gray area though since it is generated from source (we don't commit the javadoc and class files as well). The grayness imo is based on the legal status of the

Names of projects: to brand or not to brand... that is the question

2007-04-10 Thread Martijn Dashorst
Currently our core projects are referenced as 'Wicket [insert project]' in the pom's. One of the plus points of becoming an Apache project is the ability to use the Apache brand in the product name. Should we update our pom's and rename the projects to 'Apache Wicket [insert project]'? This

Re: Movement of notice files in wicket-1.x

2007-04-10 Thread Jean-Baptiste Quenot
* Martijn Dashorst: There is a NOTICE file in the project root. Don't edit this file, it is generated with each release, but edit the NOTICE file for the corresponding project. Perhaps this one should go into svn:ignore, but I am not sure if that will work for only one file. Yes I

Re: Names of projects: to brand or not to brand... that is the question

2007-04-10 Thread Johan Compagner
what do other apache projects do in that area? On 4/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote: Currently our core projects are referenced as 'Wicket [insert project]' in the pom's. One of the plus points of becoming an Apache project is the ability to use the Apache brand in the product

Re: Getting things done before new wicket 1.3 attempt

2007-04-10 Thread Martijn Dashorst
On 4/10/07, Johan Compagner [EMAIL PROTECTED] wrote: Ok i did the rename should i check this in? Perhaps best to wait until everyone has their outstanding changes committed. I suggest at least waiting until the US is awake and able to respond. Martijn -- Learn Wicket at ApacheCon Europe:

Re: Getting things done before new wicket 1.3 attempt

2007-04-10 Thread Johan Compagner
Ok then i wait, but please don't commit anything say it to me because i see that merging (updating) doesn't work correctly now so i have to do it by hand.. johan On 4/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote: On 4/10/07, Johan Compagner [EMAIL PROTECTED] wrote: Ok i did the rename

Please hold off commits until we either decide to go forward with the package rename

2007-04-10 Thread Martijn Dashorst
Johan has a working org.apache.wicket workspace (only for the core project's packages) and wants to commit that to our dev branch. Committing other changes to subversion on the wicket core and other projects will make his (and hence our) live significantly unpleasant. Therefore, until Johan has

Re: Names of projects: to brand or not to brand... that is the question

2007-04-10 Thread Frank Bille
On 4/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote: Currently our core projects are referenced as 'Wicket [insert project]' in the pom's. One of the plus points of becoming an Apache project is the ability to use the Apache brand in the product name. +1, since it will also avoid any

Re: Names of projects: to brand or not to brand... that is the question

2007-04-10 Thread Frank Bille
On 4/10/07, Frank Bille [EMAIL PROTECTED] wrote: On 4/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote: Currently our core projects are referenced as 'Wicket [insert project]' in the pom's. One of the plus points of becoming an Apache project is the ability to use the Apache brand in the

Re: Getting things done before new wicket 1.3 attempt

2007-04-10 Thread Gwyn Evans
Hi Martijn, Tuesday, April 10, 2007, 10:41:37 AM, you wrote: IIUC this would solve the issues uncovered by the IPMC. Does anyone else have something I missed? Did you need to do something with wicket-threadtest, as wasn't the source showing up at '/src' in the release? /Gwyn

Re: [jira] Closed: (WICKET-454) Make wicket.Component.renderClosingComponentTag() protected

2007-04-10 Thread Jean-Baptiste Quenot
* Johan Compagner (JIRA): [ https://issues.apache.org/jira/browse/WICKET-454?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johan Compagner closed WICKET-454. -- Resolution: Fixed Do you mean Won't Fix? Otherwise it

Re: Getting things done before new wicket 1.3 attempt

2007-04-10 Thread Jean-Baptiste Quenot
* Johan Compagner: Ok i did the rename should i check this in? Please make sure you didn't loose the SVN history ;-) -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/

Re: Getting things done before new wicket 1.3 attempt

2007-04-10 Thread Martijn Dashorst
On 4/10/07, Gwyn Evans [EMAIL PROTECTED] wrote: Tuesday, April 10, 2007, 10:41:37 AM, you wrote: IIUC this would solve the issues uncovered by the IPMC. Does anyone else have something I missed? Did you need to do something with wicket-threadtest, as wasn't the source showing up at '/src' in

Re: Please hold off commits until we either decide to go forward with the package rename

2007-04-10 Thread Igor Vaynberg
do it -igor On 4/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote: Johan has a working org.apache.wicket workspace (only for the core project's packages) and wants to commit that to our dev branch. Committing other changes to subversion on the wicket core and other projects will make his (and

Re: Please hold off commits until we either decide to go forward with the package rename

2007-04-10 Thread Johan Compagner
ok On 4/10/07, Igor Vaynberg [EMAIL PROTECTED] wrote: do it -igor On 4/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote: Johan has a working org.apache.wicket workspace (only for the core project's packages) and wants to commit that to our dev branch. Committing other changes to

Re: Please hold off commits until we either decide to go forward with the package rename

2007-04-10 Thread Eelco Hillenius
And please ping when you're done :) Eelco On 4/10/07, Johan Compagner [EMAIL PROTECTED] wrote: ok On 4/10/07, Igor Vaynberg [EMAIL PROTECTED] wrote: do it -igor On 4/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote: Johan has a working org.apache.wicket workspace (only for the core

Re: Please hold off commits until we either decide to go forward with the package rename

2007-04-10 Thread Johan Compagner
hmmm see cvs commit logs many projects are done now but now my pc east 100% cpu constant voor 15 minutes now... johan On 4/10/07, Eelco Hillenius [EMAIL PROTECTED] wrote: And please ping when you're done :) Eelco On 4/10/07, Johan Compagner [EMAIL PROTECTED] wrote: ok On 4/10/07,

Re: Getting things done before new wicket 1.3 attempt

2007-04-10 Thread Eelco Hillenius
The issue was that Eelco committed license headers with Teachscape copyright in them. Those have been fixed to show the proper Apache license headers. Yeah. Wasn't even real copyright, but just my default setting in Eclipse to start new Java files with that notice. Fixed now. Eelco

Re: Please hold off commits until we either decide to go forward with the package rename

2007-04-10 Thread Jonathan Locke
do it. johan: can you email me when you're done? thanks! igor.vaynberg wrote: do it -igor On 4/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote: Johan has a working org.apache.wicket workspace (only for the core project's packages) and wants to commit that to our dev branch.

Re: Names of projects: to brand or not to brand... that is the question

2007-04-10 Thread Eelco Hillenius
+1 Eelco On 4/10/07, Frank Bille [EMAIL PROTECTED] wrote: On 4/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote: Currently our core projects are referenced as 'Wicket [insert project]' in the pom's. One of the plus points of becoming an Apache project is the ability to use the Apache brand

Re: Please hold off commits until we either decide to go forward with the package rename

2007-04-10 Thread Eelco Hillenius
It died? All projects changed except for the core project it seems... Eelco On 4/10/07, Johan Compagner [EMAIL PROTECTED] wrote: hmmm see cvs commit logs many projects are done now but now my pc east 100% cpu constant voor 15 minutes now... johan On 4/10/07, Eelco Hillenius [EMAIL

Re: Please hold off commits until we either decide to go forward with the package rename

2007-04-10 Thread Jonathan Locke
i think now you are beginning to experience my wicket eclipse pain... ;-) Johan Compagner wrote: hmmm see cvs commit logs many projects are done now but now my pc east 100% cpu constant voor 15 minutes now... johan On 4/10/07, Eelco Hillenius [EMAIL PROTECTED] wrote: And

Re: Names of projects: to brand or not to brand... that is the question

2007-04-10 Thread Bertrand Delacretaz
On 4/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote: ...Should we update our pom's and rename the projects to 'Apache Wicket [insert project]'?.. I think it'd be good. ..And if we do this, should all documentation mention 'Apache Wicket' instead of 'Wicket'?.. I don't think *all*

Package rename at SourceForge

2007-04-10 Thread Jean-Baptiste Quenot
I'm trying to do the package rename on SourceForge, but commit fails: Adding wicket-contrib-dojo/src/main/java/org Adding wicket-contrib-dojo/src/main/java/org/apache Adding wicket-contrib-dojo/src/main/java/org/apache/wicket svn: Commit failed (details follow): svn: COPY

Re: Package rename at SourceForge

2007-04-10 Thread Martijn Dashorst
Dojo and the other projects should *not* rename their packages to the org.apache.wicket namespace. In fact, they would better be renamed to org.wicketstuff.* Martijn On 4/10/07, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote: I'm trying to do the package rename on SourceForge, but commit fails:

Re: Package rename at SourceForge

2007-04-10 Thread Jean-Baptiste Quenot
* Jean-Baptiste Quenot: I'm trying to do the package rename on SourceForge, but commit fails: Adding wicket-contrib-dojo/src/main/java/org Adding wicket-contrib-dojo/src/main/java/org/apache Adding wicket-contrib-dojo/src/main/java/org/apache/wicket svn: Commit

Re: Package rename at SourceForge

2007-04-10 Thread Jean-Baptiste Quenot
* Martijn Dashorst: Dojo and the other projects should *not* rename their packages to the org.apache.wicket namespace. In fact, they would better be renamed to org.wicketstuff.* Indeed you may be right, but as nothing was compiling anymore I applied the same renaming than what was

Re: Package rename at SourceForge

2007-04-10 Thread Jean-Baptiste Quenot
I'm thinking of renaming to org.wicketstuff.dojo instead. WDYT? -- Jean-Baptiste Quenot aka John Banana Qwerty http://caraldi.com/jbq/

Re: Package rename at SourceForge

2007-04-10 Thread Ryan Sonnek
I like that idea and think it would make sense for the other wicket-contrib-* projects to do the same. along with the package renaming, i think it's important for the project artifact to be updated as well. groupID = org.wicketstuff artifactID = dojo ??? On 4/10/07, Jean-Baptiste Quenot [EMAIL

Re: Package rename at SourceForge

2007-04-10 Thread Martijn Dashorst
On 4/10/07, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote: I'm thinking of renaming to org.wicketstuff.dojo instead. WDYT? +1 When/if wicket dojo moves to Apache that would also go through the incubator so a rename would be prudent at that time. Before that, any 'branding issue' should be

Re: Package rename at SourceForge

2007-04-10 Thread Jean-Baptiste Quenot
* Ryan Sonnek: I like that idea and think it would make sense for the other wicket-contrib-* projects to do the same. along with the package renaming, i think it's important for the project artifact to be updated as well. groupID = org.wicketstuff artifactID = dojo ??? Done, thanks for

Re: Package rename at SourceForge

2007-04-10 Thread Vincent Demay
Ryan Sonnek a écrit : I like that idea and think it would make sense for the other wicket-contrib-* projects to do the same. along with the package renaming, i think it's important for the project artifact to be updated as well. groupID = org.wicketstuff artifactID = dojo ??? +1 Hope every

Re: Package rename at SourceForge

2007-04-10 Thread Martijn Dashorst
Al and I have been contemplating introducing a Wicket stuff parent pom that gives all projects the same stuff for group id, lists, svn. I think that would be a very nice thing to have. Martijn On 4/11/07, Jean-Baptiste Quenot [EMAIL PROTECTED] wrote: * Ryan Sonnek: I like that idea and think

Re: Package rename at SourceForge

2007-04-10 Thread Ryan Sonnek
On 4/10/07, Martijn Dashorst [EMAIL PROTECTED] wrote: Al and I have been contemplating introducing a Wicket stuff parent pom that gives all projects the same stuff for group id, lists, svn. +1 for a common parent pom.

wicket-examples test broken again

2007-04-10 Thread Eelco Hillenius
Hey, If I remember correctly, Jean-Baptiste made a fix yesterday that repaired the WordGeneratorTest from wicket-examples. After the package rename changes it is broken again it seems. Rolling back to the older version doesn't seem to fix it unfortunately. Any idea Jean-Baptiste or Johan? Eelco