wicketstuff.org is down (HTTP)
Hi guys, just in case you haven't noticed: wicketstuff.org answers on HTTP, but gives a 503 error message immediately. -- Edvin
Could AbstractTab#isVisible() be backported to 1.3-branch?
Hi, I see that AbstractTab has gotten an isVisible() method in the 1.4-branch, would it be possible to backport this to 1.3? I can't upgrade to 1.4 yet, and need this functionality :) Sincerely, Edvin Syse
Re: Could AbstractTab#isVisible() be backported to 1.3-branch?
Igor Vaynberg wrote: it is actually ITab#isVisible() which is an api break not allowed in 1.3.x releases. Saw that it was ITab after i posted and felt kind of stupid :)) hehe we can possibbly add it just to AbstractTab and then do an instanceof check, but that is quiet ugly. this is what 1.4 release is for. Agree, that's ugly :) you can easily roll your own panel until you can update to 1.4 OK, thanks, I'll do that! -- Edvin
Re: Create release of wicketstuff-jquery
OK, thanks for all the help :)) -- Edvin Maurice Marrink skrev: On Wed, Jun 4, 2008 at 11:32 PM, Edvin Syse [EMAIL PROTECTED] wrote: Thanks for the quick reply! A few more questions. 1. Bamboo is out of the picture now, right? TC is the replacement CI system? Correct. 2. Will the release be propagated to http://sourceforge.net/project/showfiles.php?group_id=134391, or do I have to perform additional steps to do that? No you have to do that manually. Also our repository is not synched with the standard maven repo. You already should have the required permissions to create a release on sourceforge, just follow there documentation. 3. Where should I create the branch? Any conventions I should honor? Is /releases/wicket-stuff-1.3.3/wicketstuff-jquery a good place? (Since /releases/wicket-stuff-1.3.3 already exists) Either /branches or /releases is fine by me. if you create a branch from eclipse it will automatically place it under /branches. I am not aware of any conventions on this point. So go ahead and use /releases/wicket-stuff-1.3.3/wicketstuff-jquery (well as long as that release is build against wicket 1.3.3 :)) Maurice -- Edvin Maurice Marrink skrev: Typically if you do a release: You make sure everything on trunk is as you want to release it. version number etc. commit that. Let tc build the artifacts. create a branch. update version of trunk to a new snapshot version (or your release will get overwritten every time you make a new commit). commit new version. Note maven has a release plugin that probably does something like the above but i have no experience with it. As for the /releases svn path, i don't think there is anything special to it. but i could be wrong :). Anyway i have never used it myself. If you plan to continue development on a branch (bugfixes or something like that) we can set up a new build for that branch on tc. Maurice On Wed, Jun 4, 2008 at 9:32 PM, Edvin Syse [EMAIL PROTECTED] wrote: Hi, I'd like to create a release for wicketstuff-jquery, as it is still 0.1-SNAPSHOT, and I've gotten feedback from people saying they won't rely on it until there is a release available. Can someone point me to some info on how I can create a release? Is there some convention that branches created on /releases will be automatically kept or something? I created an account on teamcity (username edvinsyse) and it recognizes me as a committer, btw. Also, can I get access in wicketstuff.org/jira so I can close some outstanding WSJQUERY tickets there? I'm sorry for my ignorance :)) -- Edvin
Create release of wicketstuff-jquery
Hi, I'd like to create a release for wicketstuff-jquery, as it is still 0.1-SNAPSHOT, and I've gotten feedback from people saying they won't rely on it until there is a release available. Can someone point me to some info on how I can create a release? Is there some convention that branches created on /releases will be automatically kept or something? I created an account on teamcity (username edvinsyse) and it recognizes me as a committer, btw. Also, can I get access in wicketstuff.org/jira so I can close some outstanding WSJQUERY tickets there? I'm sorry for my ignorance :)) -- Edvin
Re: Create release of wicketstuff-jquery
Thanks for the quick reply! A few more questions. 1. Bamboo is out of the picture now, right? TC is the replacement CI system? 2. Will the release be propagated to http://sourceforge.net/project/showfiles.php?group_id=134391, or do I have to perform additional steps to do that? 3. Where should I create the branch? Any conventions I should honor? Is /releases/wicket-stuff-1.3.3/wicketstuff-jquery a good place? (Since /releases/wicket-stuff-1.3.3 already exists) -- Edvin Maurice Marrink skrev: Typically if you do a release: You make sure everything on trunk is as you want to release it. version number etc. commit that. Let tc build the artifacts. create a branch. update version of trunk to a new snapshot version (or your release will get overwritten every time you make a new commit). commit new version. Note maven has a release plugin that probably does something like the above but i have no experience with it. As for the /releases svn path, i don't think there is anything special to it. but i could be wrong :). Anyway i have never used it myself. If you plan to continue development on a branch (bugfixes or something like that) we can set up a new build for that branch on tc. Maurice On Wed, Jun 4, 2008 at 9:32 PM, Edvin Syse [EMAIL PROTECTED] wrote: Hi, I'd like to create a release for wicketstuff-jquery, as it is still 0.1-SNAPSHOT, and I've gotten feedback from people saying they won't rely on it until there is a release available. Can someone point me to some info on how I can create a release? Is there some convention that branches created on /releases will be automatically kept or something? I created an account on teamcity (username edvinsyse) and it recognizes me as a committer, btw. Also, can I get access in wicketstuff.org/jira so I can close some outstanding WSJQUERY tickets there? I'm sorry for my ignorance :)) -- Edvin
Re: Lost commit access to wicketstuff-jquery
Ah.. tried again now, and it works. Guess it was a sync between two databases or something when I changed the password :) -- Edvin Edvin Syse skrev: I logged in and changed my password but still no luck. Is there a synchronization that needs to take place first or something? I'll try again later today. -- Edvin Martijn Dashorst skrev: sf.net recently has disabled all accounts due to a security breach. You have to log in through the site and update your password. Also if you have checked out http://wicket-stuff.svn.sourceforge.net you have to update your local copy to use https:// Martijn On 5/9/08, Edvin Syse [EMAIL PROTECTED] wrote: Hi, I've started working on some new plugins for wicketstuff-jquery but I seem to have lost my commit access. I supply my username edvinsyse and my password (which works at sourceforge.net), but I get access denied. User ID: 1984572 Can someone check for me? Thanks, Edvin
Lost commit access to wicketstuff-jquery
Hi, I've started working on some new plugins for wicketstuff-jquery but I seem to have lost my commit access. I supply my username edvinsyse and my password (which works at sourceforge.net), but I get access denied. User ID: 1984572 Can someone check for me? Thanks, Edvin
Re: Move WICKET-1307 to 1.3.1?
If you end up with rebuilding because of this, it would be really nice to get the fix for AjaxEditableLabel in as well, Gerolf just fixed it (WICKET-1239). -- Edvin Erik van Oosten skrev: Hello, Could WICKET-1307 be moved to release 1.3.1? Regards, Erik. -- Erik van Oosten http://day-to-day-stuff.blogspot.com/
