Continuum Build Server Set Up
Devs, In response to the problems with TeamCity and Sourceforge, I installed a Continuum instance on my server last night. I added Wicket and several Wicket Stuff projects. It seems to be running fine, except that most projects are missing the SCM tag from their POM, or have it incorrectly configured. I don't mind going in and fixing or adding the SCM tag on all of the projects that are currently on TeamCity and setting them up on this Continuum server. But since those aren't my projects, I wanted to run it past the group first. What do you think? We could do this and let it run for a while as a test. http://www.wickettraining.com/continuum -- Jeremy Thomerson http://www.wickettraining.com
Re: Continuum Build Server Set Up
Could you structure the parent pom such that it sets up all child poms correctly? Then it is just a matter of inheriting from the parent pom for all projects. Martijn On Tue, Nov 18, 2008 at 5:21 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Devs, In response to the problems with TeamCity and Sourceforge, I installed a Continuum instance on my server last night. I added Wicket and several Wicket Stuff projects. It seems to be running fine, except that most projects are missing the SCM tag from their POM, or have it incorrectly configured. I don't mind going in and fixing or adding the SCM tag on all of the projects that are currently on TeamCity and setting them up on this Continuum server. But since those aren't my projects, I wanted to run it past the group first. What do you think? We could do this and let it run for a while as a test. http://www.wickettraining.com/continuum -- Jeremy Thomerson http://www.wickettraining.com -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
Re: Continuum Build Server Set Up
When you create a tag/branch of the child, the SCM setup wouldn't inherit correctly, though. Right? On Tue, Nov 18, 2008 at 11:44 AM, Martijn Dashorst [EMAIL PROTECTED] wrote: Could you structure the parent pom such that it sets up all child poms correctly? Then it is just a matter of inheriting from the parent pom for all projects. Martijn On Tue, Nov 18, 2008 at 5:21 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Devs, In response to the problems with TeamCity and Sourceforge, I installed a Continuum instance on my server last night. I added Wicket and several Wicket Stuff projects. It seems to be running fine, except that most projects are missing the SCM tag from their POM, or have it incorrectly configured. I don't mind going in and fixing or adding the SCM tag on all of the projects that are currently on TeamCity and setting them up on this Continuum server. But since those aren't my projects, I wanted to run it past the group first. What do you think? We could do this and let it run for a while as a test. http://www.wickettraining.com/continuum -- Jeremy Thomerson http://www.wickettraining.com -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
Re: Continuum Build Server Set Up
Yes - and I think that's the best thing to do. To make this work, I would do this: - Create a pom.xml in wicketstuff trunk that sets up the SCM correctly and relies on wicket 1.4-SNAPSHOT - Delete the wicket-parent folder under trunk because it's not really needed if we do this - Each project then needs the pom changed to show that the parent of the project is wicketstuff-parent (the pom I created in trunk) - We can also remove the SCM config in each child pom because it will be set up correctly in the parent. Other things could also probably be deleted later - but that's not the goal of this, so we can wait on that. Please review and let me know if you approve. If several of the core committers are okay with this, I'll go ahead and do it. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 10:44 AM, Martijn Dashorst [EMAIL PROTECTED] wrote: Could you structure the parent pom such that it sets up all child poms correctly? Then it is just a matter of inheriting from the parent pom for all projects. Martijn On Tue, Nov 18, 2008 at 5:21 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Devs, In response to the problems with TeamCity and Sourceforge, I installed a Continuum instance on my server last night. I added Wicket and several Wicket Stuff projects. It seems to be running fine, except that most projects are missing the SCM tag from their POM, or have it incorrectly configured. I don't mind going in and fixing or adding the SCM tag on all of the projects that are currently on TeamCity and setting them up on this Continuum server. But since those aren't my projects, I wanted to run it past the group first. What do you think? We could do this and let it run for a while as a test. http://www.wickettraining.com/continuum -- Jeremy Thomerson http://www.wickettraining.com -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.
Re: Continuum Build Server Set Up
The problem is that the entire tree isn't copied over together, so the SCM links get messed up when you do that. On Tue, Nov 18, 2008 at 11:57 AM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Tough to be sure - we could experiment. On Tue, Nov 18, 2008 at 10:50 AM, James Carman [EMAIL PROTECTED]wrote: When you create a tag/branch of the child, the SCM setup wouldn't inherit correctly, though. Right? On Tue, Nov 18, 2008 at 11:44 AM, Martijn Dashorst [EMAIL PROTECTED] wrote: Could you structure the parent pom such that it sets up all child poms correctly? Then it is just a matter of inheriting from the parent pom for all projects. Martijn On Tue, Nov 18, 2008 at 5:21 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Devs, In response to the problems with TeamCity and Sourceforge, I installed a Continuum instance on my server last night. I added Wicket and several Wicket Stuff projects. It seems to be running fine, except that most projects are missing the SCM tag from their POM, or have it incorrectly configured. I don't mind going in and fixing or adding the SCM tag on all of the projects that are currently on TeamCity and setting them up on this Continuum server. But since those aren't my projects, I wanted to run it past the group first. What do you think? We could do this and let it run for a while as a test. http://www.wickettraining.com/continuum -- Jeremy Thomerson http://www.wickettraining.com -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. -- Jeremy Thomerson http://www.wickettraining.com
Re: Continuum Build Server Set Up
Tough to be sure - we could experiment. On Tue, Nov 18, 2008 at 10:50 AM, James Carman [EMAIL PROTECTED]wrote: When you create a tag/branch of the child, the SCM setup wouldn't inherit correctly, though. Right? On Tue, Nov 18, 2008 at 11:44 AM, Martijn Dashorst [EMAIL PROTECTED] wrote: Could you structure the parent pom such that it sets up all child poms correctly? Then it is just a matter of inheriting from the parent pom for all projects. Martijn On Tue, Nov 18, 2008 at 5:21 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Devs, In response to the problems with TeamCity and Sourceforge, I installed a Continuum instance on my server last night. I added Wicket and several Wicket Stuff projects. It seems to be running fine, except that most projects are missing the SCM tag from their POM, or have it incorrectly configured. I don't mind going in and fixing or adding the SCM tag on all of the projects that are currently on TeamCity and setting them up on this Continuum server. But since those aren't my projects, I wanted to run it past the group first. What do you think? We could do this and let it run for a while as a test. http://www.wickettraining.com/continuum -- Jeremy Thomerson http://www.wickettraining.com -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. -- Jeremy Thomerson http://www.wickettraining.com
Re: Continuum Build Server Set Up
I'm talking about the SCM url itself. It needs to change in the child when a branch/tag is created (because it now lives in a different place). Of course it would be able to find its parent (as long as it's in the local repository). On Tue, Nov 18, 2008 at 12:04 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: I don't think it would if you defined it like this in each child... right? parent * * groupId*org.apache.wicket*/groupId * * artifactId*wicket-parent*/artifactId * * version*1.4-SNAPSHOT*/version * * /parent Because it doesn't have a relative path, Maven just looks up the parent pom like it looks up any other dependency. If you had a relative path, like wicket does to its parent pom, then it would mess up. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 10:59 AM, James Carman [EMAIL PROTECTED]wrote: The problem is that the entire tree isn't copied over together, so the SCM links get messed up when you do that. On Tue, Nov 18, 2008 at 11:57 AM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Tough to be sure - we could experiment. On Tue, Nov 18, 2008 at 10:50 AM, James Carman [EMAIL PROTECTED]wrote: When you create a tag/branch of the child, the SCM setup wouldn't inherit correctly, though. Right? On Tue, Nov 18, 2008 at 11:44 AM, Martijn Dashorst [EMAIL PROTECTED] wrote: Could you structure the parent pom such that it sets up all child poms correctly? Then it is just a matter of inheriting from the parent pom for all projects. Martijn On Tue, Nov 18, 2008 at 5:21 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Devs, In response to the problems with TeamCity and Sourceforge, I installed a Continuum instance on my server last night. I added Wicket and several Wicket Stuff projects. It seems to be running fine, except that most projects are missing the SCM tag from their POM, or have it incorrectly configured. I don't mind going in and fixing or adding the SCM tag on all of the projects that are currently on TeamCity and setting them up on this Continuum server. But since those aren't my projects, I wanted to run it past the group first. What do you think? We could do this and let it run for a while as a test. http://www.wickettraining.com/continuum -- Jeremy Thomerson http://www.wickettraining.com -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. -- Jeremy Thomerson http://www.wickettraining.com
Re: Continuum Build Server Set Up
Oh, gotcha! I'll try a test with one of my projects and see, but I think you're right. If so, I am still willing to add the SCM info to each pom if necessary - but I still want approval of the crowd since those aren't my projects to alter. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 11:07 AM, James Carman [EMAIL PROTECTED]wrote: I'm talking about the SCM url itself. It needs to change in the child when a branch/tag is created (because it now lives in a different place). Of course it would be able to find its parent (as long as it's in the local repository). On Tue, Nov 18, 2008 at 12:04 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: I don't think it would if you defined it like this in each child... right? parent * * groupId*org.apache.wicket*/groupId * * artifactId*wicket-parent*/artifactId * * version*1.4-SNAPSHOT*/version * * /parent Because it doesn't have a relative path, Maven just looks up the parent pom like it looks up any other dependency. If you had a relative path, like wicket does to its parent pom, then it would mess up. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 10:59 AM, James Carman [EMAIL PROTECTED]wrote: The problem is that the entire tree isn't copied over together, so the SCM links get messed up when you do that. On Tue, Nov 18, 2008 at 11:57 AM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Tough to be sure - we could experiment. On Tue, Nov 18, 2008 at 10:50 AM, James Carman [EMAIL PROTECTED]wrote: When you create a tag/branch of the child, the SCM setup wouldn't inherit correctly, though. Right? On Tue, Nov 18, 2008 at 11:44 AM, Martijn Dashorst [EMAIL PROTECTED] wrote: Could you structure the parent pom such that it sets up all child poms correctly? Then it is just a matter of inheriting from the parent pom for all projects. Martijn On Tue, Nov 18, 2008 at 5:21 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Devs, In response to the problems with TeamCity and Sourceforge, I installed a Continuum instance on my server last night. I added Wicket and several Wicket Stuff projects. It seems to be running fine, except that most projects are missing the SCM tag from their POM, or have it incorrectly configured. I don't mind going in and fixing or adding the SCM tag on all of the projects that are currently on TeamCity and setting them up on this Continuum server. But since those aren't my projects, I wanted to run it past the group first. What do you think? We could do this and let it run for a while as a test. http://www.wickettraining.com/continuum -- Jeremy Thomerson http://www.wickettraining.com -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. -- Jeremy Thomerson http://www.wickettraining.com
Re: Continuum Build Server Set Up
If all of wicketstuff was branched/tagged together, this would work and you could let the release plugin automagically change it for you. But, since they all have their own lifecycle (their own trunk/branches/tags), then you need to configure them individually. On Tue, Nov 18, 2008 at 12:12 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Oh, gotcha! I'll try a test with one of my projects and see, but I think you're right. If so, I am still willing to add the SCM info to each pom if necessary - but I still want approval of the crowd since those aren't my projects to alter. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 11:07 AM, James Carman [EMAIL PROTECTED]wrote: I'm talking about the SCM url itself. It needs to change in the child when a branch/tag is created (because it now lives in a different place). Of course it would be able to find its parent (as long as it's in the local repository). On Tue, Nov 18, 2008 at 12:04 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: I don't think it would if you defined it like this in each child... right? parent * * groupId*org.apache.wicket*/groupId * * artifactId*wicket-parent*/artifactId * * version*1.4-SNAPSHOT*/version * * /parent Because it doesn't have a relative path, Maven just looks up the parent pom like it looks up any other dependency. If you had a relative path, like wicket does to its parent pom, then it would mess up. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 10:59 AM, James Carman [EMAIL PROTECTED]wrote: The problem is that the entire tree isn't copied over together, so the SCM links get messed up when you do that. On Tue, Nov 18, 2008 at 11:57 AM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Tough to be sure - we could experiment. On Tue, Nov 18, 2008 at 10:50 AM, James Carman [EMAIL PROTECTED]wrote: When you create a tag/branch of the child, the SCM setup wouldn't inherit correctly, though. Right? On Tue, Nov 18, 2008 at 11:44 AM, Martijn Dashorst [EMAIL PROTECTED] wrote: Could you structure the parent pom such that it sets up all child poms correctly? Then it is just a matter of inheriting from the parent pom for all projects. Martijn On Tue, Nov 18, 2008 at 5:21 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Devs, In response to the problems with TeamCity and Sourceforge, I installed a Continuum instance on my server last night. I added Wicket and several Wicket Stuff projects. It seems to be running fine, except that most projects are missing the SCM tag from their POM, or have it incorrectly configured. I don't mind going in and fixing or adding the SCM tag on all of the projects that are currently on TeamCity and setting them up on this Continuum server. But since those aren't my projects, I wanted to run it past the group first. What do you think? We could do this and let it run for a while as a test. http://www.wickettraining.com/continuum -- Jeremy Thomerson http://www.wickettraining.com -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. -- Jeremy Thomerson http://www.wickettraining.com
Re: Continuum Build Server Set Up
Yes - you're right. Overall, I think it will be much less intrusive to just add or fix the SCM tag in each project. Once I hear back whether anyone is in agreement with this or not, I can proceed (or not). At some point in the future we should probably discuss some way of creating at least a group of the core projects in wicket-stuff that all build and release together, on the same schedule as Wicket. But I don't want to muddy this build server discussion with that, and I don't have the mental or time bandwidth to work through that right now. So, what does everyone think? Can I update pom files to have correct SCM info and add them to Continuum on my server? -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 11:15 AM, James Carman [EMAIL PROTECTED]wrote: If all of wicketstuff was branched/tagged together, this would work and you could let the release plugin automagically change it for you. But, since they all have their own lifecycle (their own trunk/branches/tags), then you need to configure them individually. On Tue, Nov 18, 2008 at 12:12 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Oh, gotcha! I'll try a test with one of my projects and see, but I think you're right. If so, I am still willing to add the SCM info to each pom if necessary - but I still want approval of the crowd since those aren't my projects to alter. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 11:07 AM, James Carman [EMAIL PROTECTED]wrote: I'm talking about the SCM url itself. It needs to change in the child when a branch/tag is created (because it now lives in a different place). Of course it would be able to find its parent (as long as it's in the local repository). On Tue, Nov 18, 2008 at 12:04 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: I don't think it would if you defined it like this in each child... right? parent * * groupId*org.apache.wicket*/groupId * * artifactId*wicket-parent*/artifactId * * version*1.4-SNAPSHOT*/version * * /parent Because it doesn't have a relative path, Maven just looks up the parent pom like it looks up any other dependency. If you had a relative path, like wicket does to its parent pom, then it would mess up. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 10:59 AM, James Carman [EMAIL PROTECTED]wrote: The problem is that the entire tree isn't copied over together, so the SCM links get messed up when you do that. On Tue, Nov 18, 2008 at 11:57 AM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Tough to be sure - we could experiment. On Tue, Nov 18, 2008 at 10:50 AM, James Carman [EMAIL PROTECTED]wrote: When you create a tag/branch of the child, the SCM setup wouldn't inherit correctly, though. Right? On Tue, Nov 18, 2008 at 11:44 AM, Martijn Dashorst [EMAIL PROTECTED] wrote: Could you structure the parent pom such that it sets up all child poms correctly? Then it is just a matter of inheriting from the parent pom for all projects. Martijn On Tue, Nov 18, 2008 at 5:21 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Devs, In response to the problems with TeamCity and Sourceforge, I installed a Continuum instance on my server last night. I added Wicket and several Wicket Stuff projects. It seems to be running fine, except that most projects are missing the SCM tag from their POM, or have it incorrectly configured. I don't mind going in and fixing or adding the SCM tag on all of the projects that are currently on TeamCity and setting them up on this Continuum server. But since those aren't my projects, I wanted to run it past the group first. What do you think? We could do this and let it run for a while as a test. http://www.wickettraining.com/continuum -- Jeremy Thomerson http://www.wickettraining.com -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.3.4 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3. -- Jeremy Thomerson http://www.wickettraining.com
Re: Continuum Build Server Set Up
Sure fine by me, and good initiative! I'll try to see if I can fix my own projects, can you provide a sniplet on how it should look? regards Nino Jeremy Thomerson wrote: Yes - you're right. Overall, I think it will be much less intrusive to just add or fix the SCM tag in each project. Once I hear back whether anyone is in agreement with this or not, I can proceed (or not). At some point in the future we should probably discuss some way of creating at least a group of the core projects in wicket-stuff that all build and release together, on the same schedule as Wicket. But I don't want to muddy this build server discussion with that, and I don't have the mental or time bandwidth to work through that right now. So, what does everyone think? Can I update pom files to have correct SCM info and add them to Continuum on my server? -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684
Re: Continuum Build Server Set Up
Send me a list of which are yours and I'll try them as samples. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 1:20 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: Sure fine by me, and good initiative! I'll try to see if I can fix my own projects, can you provide a sniplet on how it should look? regards Nino Jeremy Thomerson wrote: Yes - you're right. Overall, I think it will be much less intrusive to just add or fix the SCM tag in each project. Once I hear back whether anyone is in agreement with this or not, I can proceed (or not). At some point in the future we should probably discuss some way of creating at least a group of the core projects in wicket-stuff that all build and release together, on the same schedule as Wicket. But I don't want to muddy this build server discussion with that, and I don't have the mental or time bandwidth to work through that right now. So, what does everyone think? Can I update pom files to have correct SCM info and add them to Continuum on my server? -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684
Re: Continuum Build Server Set Up
And, as an example, look at this pom: https://wicket-stuff.svn.sourceforge.net/svnroot/wicket-stuff/trunk/wicketstuff-calendarviews/pom.xml The important part that is messed up or missing from most is that connection URL in the SCM tag. Take the one from that pom and modify accordingly (change your project folder). -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 1:47 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Send me a list of which are yours and I'll try them as samples. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 1:20 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: Sure fine by me, and good initiative! I'll try to see if I can fix my own projects, can you provide a sniplet on how it should look? regards Nino Jeremy Thomerson wrote: Yes - you're right. Overall, I think it will be much less intrusive to just add or fix the SCM tag in each project. Once I hear back whether anyone is in agreement with this or not, I can proceed (or not). At some point in the future we should probably discuss some way of creating at least a group of the core projects in wicket-stuff that all build and release together, on the same schedule as Wicket. But I don't want to muddy this build server discussion with that, and I don't have the mental or time bandwidth to work through that right now. So, what does everyone think? Can I update pom files to have correct SCM info and add them to Continuum on my server? -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684
Re: Continuum Build Server Set Up
http://wicketstuff.org/confluence/display/STUFFWIKI/Project+Maintainers I think those are some of them (where my name are on), there could be more cant remember.. I think I've upgraded all to use 1-4 snapshot of wicket... Jeremy Thomerson wrote: Send me a list of which are yours and I'll try them as samples. -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684
Re: Continuum Build Server Set Up
Nino, I'm updating your poms and adding yours. I ran into a problem - you have wicket-persistence-template and wicket-iolite - both have the same group and artifact IDs. I'm going to wait to add them to the build server - can you tell me what the difference is? Maybe one should be renamed? On Tue, Nov 18, 2008 at 1:51 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: http://wicketstuff.org/confluence/display/STUFFWIKI/Project+Maintainers I think those are some of them (where my name are on), there could be more cant remember.. I think I've upgraded all to use 1-4 snapshot of wicket... Jeremy Thomerson wrote: Send me a list of which are yours and I'll try them as samples. -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 -- Jeremy Thomerson http://www.wickettraining.com
Re: Drop wicket:link
+1, what about moving it to an optional package? wicket-tags ? On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl [EMAIL PROTECTED] wrote: -1, too: I use it just the way Igor describes. I usually set up a mock html page, then wicket:link the css and javascript. So I can easily test the page in preview mode and in wicket, too. Once the application evolves I tend to remove wicket:link again and replace it with ResourceReference inside the pages and base pages. Let it there, it's really useful. If people tend to be stupid no framework on earth will stop them from doing so. Cheers Peter Am 17.11.2008 um 21:06 schrieb Igor Vaynberg: -1. this stuff is very useful for linking to css/js/image files. if people want to abuse it, it is their problem. people will find a way to abuse anything though. -igor 2008/11/17 Bruno Cesar Borges [EMAIL PROTECTED]: This might sound crazy, but what about dropping the support for the tag wicket:link ? :-) People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that. Example: # Java AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer(menus); # HTML ul wicket:id=menus lia href=Users.htmlUsers/a/li lia href=Departments.htmlDepartments/a/li /ul What do you guys think? Cheers, Bruno *** Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s), podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema. Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas. Warning: This message was sent for exclusive use of the addressees above identified, possibly containing information and or privileged/confidential documents whose content is protected by law. In case you have mistakenly received it, please notify the sender and delete it from your system. Be noticed that the law forbids the retention, dissemination, distribution, copy or use without express authorization from the sender. Personal opinions of the sender do not necessarily reflect CETIP's point of view, which is only divulged by authorized personnel. ***
Re: Continuum Build Server Set Up
Also: wicket-contrib-accordian is named Wicket Contrib Openlayers On Tue, Nov 18, 2008 at 2:20 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Nino, I'm updating your poms and adding yours. I ran into a problem - you have wicket-persistence-template and wicket-iolite - both have the same group and artifact IDs. I'm going to wait to add them to the build server - can you tell me what the difference is? Maybe one should be renamed? On Tue, Nov 18, 2008 at 1:51 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: http://wicketstuff.org/confluence/display/STUFFWIKI/Project+Maintainers I think those are some of them (where my name are on), there could be more cant remember.. I think I've upgraded all to use 1-4 snapshot of wicket... Jeremy Thomerson wrote: Send me a list of which are yours and I'll try them as samples. -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 -- Jeremy Thomerson http://www.wickettraining.com -- Jeremy Thomerson http://www.wickettraining.com
Re: Drop wicket:link
The markup parser has to know how to deal with it I would think. That would be quite an undertaking to split that functionality out and make it able to be plugged back in. On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen [EMAIL PROTECTED] wrote: +1, what about moving it to an optional package? wicket-tags ? On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl [EMAIL PROTECTED] wrote: -1, too: I use it just the way Igor describes. I usually set up a mock html page, then wicket:link the css and javascript. So I can easily test the page in preview mode and in wicket, too. Once the application evolves I tend to remove wicket:link again and replace it with ResourceReference inside the pages and base pages. Let it there, it's really useful. If people tend to be stupid no framework on earth will stop them from doing so. Cheers Peter Am 17.11.2008 um 21:06 schrieb Igor Vaynberg: -1. this stuff is very useful for linking to css/js/image files. if people want to abuse it, it is their problem. people will find a way to abuse anything though. -igor 2008/11/17 Bruno Cesar Borges [EMAIL PROTECTED]: This might sound crazy, but what about dropping the support for the tag wicket:link ? :-) People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that. Example: # Java AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer(menus); # HTML ul wicket:id=menus lia href=Users.htmlUsers/a/li lia href=Departments.htmlDepartments/a/li /ul What do you guys think? Cheers, Bruno *** Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s), podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema. Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas. Warning: This message was sent for exclusive use of the addressees above identified, possibly containing information and or privileged/confidential documents whose content is protected by law. In case you have mistakenly received it, please notify the sender and delete it from your system. Be noticed that the law forbids the retention, dissemination, distribution, copy or use without express authorization from the sender. Personal opinions of the sender do not necessarily reflect CETIP's point of view, which is only divulged by authorized personnel. ***
Re: Continuum Build Server Set Up
Okay, all of yours are added (includeing the persistence-template / iolite). wicket-contrib-openlayers-examples doesn't compile The rest are all building fine. -- Jeremy Thomerson http://www.wickettraining.com On Tue, Nov 18, 2008 at 2:25 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Also: wicket-contrib-accordian is named Wicket Contrib Openlayers On Tue, Nov 18, 2008 at 2:20 PM, Jeremy Thomerson [EMAIL PROTECTED] wrote: Nino, I'm updating your poms and adding yours. I ran into a problem - you have wicket-persistence-template and wicket-iolite - both have the same group and artifact IDs. I'm going to wait to add them to the build server - can you tell me what the difference is? Maybe one should be renamed? On Tue, Nov 18, 2008 at 1:51 PM, Nino Saturnino Martinez Vazquez Wael [EMAIL PROTECTED] wrote: http://wicketstuff.org/confluence/display/STUFFWIKI/Project+Maintainers I think those are some of them (where my name are on), there could be more cant remember.. I think I've upgraded all to use 1-4 snapshot of wicket... Jeremy Thomerson wrote: Send me a list of which are yours and I'll try them as samples. -- -Wicket for love Nino Martinez Wael Java Specialist @ Jayway DK http://www.jayway.dk +45 2936 7684 -- Jeremy Thomerson http://www.wickettraining.com -- Jeremy Thomerson http://www.wickettraining.com
Re: Drop wicket:link
it is already all pluggable and wicketlink handler is just a plugin into the parser :) -igor On Tue, Nov 18, 2008 at 12:29 PM, James Carman [EMAIL PROTECTED] wrote: The markup parser has to know how to deal with it I would think. That would be quite an undertaking to split that functionality out and make it able to be plugged back in. On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen [EMAIL PROTECTED] wrote: +1, what about moving it to an optional package? wicket-tags ? On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl [EMAIL PROTECTED] wrote: -1, too: I use it just the way Igor describes. I usually set up a mock html page, then wicket:link the css and javascript. So I can easily test the page in preview mode and in wicket, too. Once the application evolves I tend to remove wicket:link again and replace it with ResourceReference inside the pages and base pages. Let it there, it's really useful. If people tend to be stupid no framework on earth will stop them from doing so. Cheers Peter Am 17.11.2008 um 21:06 schrieb Igor Vaynberg: -1. this stuff is very useful for linking to css/js/image files. if people want to abuse it, it is their problem. people will find a way to abuse anything though. -igor 2008/11/17 Bruno Cesar Borges [EMAIL PROTECTED]: This might sound crazy, but what about dropping the support for the tag wicket:link ? :-) People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that. Example: # Java AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer(menus); # HTML ul wicket:id=menus lia href=Users.htmlUsers/a/li lia href=Departments.htmlDepartments/a/li /ul What do you guys think? Cheers, Bruno *** Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s), podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema. Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas. Warning: This message was sent for exclusive use of the addressees above identified, possibly containing information and or privileged/confidential documents whose content is protected by law. In case you have mistakenly received it, please notify the sender and delete it from your system. Be noticed that the law forbids the retention, dissemination, distribution, copy or use without express authorization from the sender. Personal opinions of the sender do not necessarily reflect CETIP's point of view, which is only divulged by authorized personnel. ***
Re: Drop wicket:link
Would the user have to register the plugin manually or would it be picked up merely by the jar being on the classpath? On Tue, Nov 18, 2008 at 4:01 PM, Igor Vaynberg [EMAIL PROTECTED] wrote: it is already all pluggable and wicketlink handler is just a plugin into the parser :) -igor On Tue, Nov 18, 2008 at 12:29 PM, James Carman [EMAIL PROTECTED] wrote: The markup parser has to know how to deal with it I would think. That would be quite an undertaking to split that functionality out and make it able to be plugged back in. On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen [EMAIL PROTECTED] wrote: +1, what about moving it to an optional package? wicket-tags ? On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl [EMAIL PROTECTED] wrote: -1, too: I use it just the way Igor describes. I usually set up a mock html page, then wicket:link the css and javascript. So I can easily test the page in preview mode and in wicket, too. Once the application evolves I tend to remove wicket:link again and replace it with ResourceReference inside the pages and base pages. Let it there, it's really useful. If people tend to be stupid no framework on earth will stop them from doing so. Cheers Peter Am 17.11.2008 um 21:06 schrieb Igor Vaynberg: -1. this stuff is very useful for linking to css/js/image files. if people want to abuse it, it is their problem. people will find a way to abuse anything though. -igor 2008/11/17 Bruno Cesar Borges [EMAIL PROTECTED]: This might sound crazy, but what about dropping the support for the tag wicket:link ? :-) People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that. Example: # Java AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer(menus); # HTML ul wicket:id=menus lia href=Users.htmlUsers/a/li lia href=Departments.htmlDepartments/a/li /ul What do you guys think? Cheers, Bruno *** Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s), podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema. Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas. Warning: This message was sent for exclusive use of the addressees above identified, possibly containing information and or privileged/confidential documents whose content is protected by law. In case you have mistakenly received it, please notify the sender and delete it from your system. Be noticed that the law forbids the retention, dissemination, distribution, copy or use without express authorization from the sender. Personal opinions of the sender do not necessarily reflect CETIP's point of view, which is only divulged by authorized personnel. ***
Re: Drop wicket:link
What's the problem with just leaving it where it is? If you don't like it ignore it - or am I missing something important here? Am 18.11.2008 um 22:12 schrieb James Carman: Would the user have to register the plugin manually or would it be picked up merely by the jar being on the classpath? On Tue, Nov 18, 2008 at 4:01 PM, Igor Vaynberg [EMAIL PROTECTED] wrote: it is already all pluggable and wicketlink handler is just a plugin into the parser :) -igor On Tue, Nov 18, 2008 at 12:29 PM, James Carman [EMAIL PROTECTED] wrote: The markup parser has to know how to deal with it I would think. That would be quite an undertaking to split that functionality out and make it able to be plugged back in. On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen [EMAIL PROTECTED] wrote: +1, what about moving it to an optional package? wicket-tags ? On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl [EMAIL PROTECTED] wrote: -1, too: I use it just the way Igor describes. I usually set up a mock html page, then wicket:link the css and javascript. So I can easily test the page in preview mode and in wicket, too. Once the application evolves I tend to remove wicket:link again and replace it with ResourceReference inside the pages and base pages. Let it there, it's really useful. If people tend to be stupid no framework on earth will stop them from doing so. Cheers Peter Am 17.11.2008 um 21:06 schrieb Igor Vaynberg: -1. this stuff is very useful for linking to css/js/image files. if people want to abuse it, it is their problem. people will find a way to abuse anything though. -igor 2008/11/17 Bruno Cesar Borges [EMAIL PROTECTED]: This might sound crazy, but what about dropping the support for the tag wicket:link ? :-) People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that. Example: # Java AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer(menus); # HTML ul wicket:id=menus lia href=Users.htmlUsers/a/li lia href=Departments.htmlDepartments/a/li /ul What do you guys think? Cheers, Bruno *** Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s), podendo conter informações e/ou documentos confidencias/ privilegiados e seu sigilo é protegido por lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema. Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas. Warning: This message was sent for exclusive use of the addressees above identified, possibly containing information and or privileged/confidential documents whose content is protected by law. In case you have mistakenly received it, please notify the sender and delete it from your system. Be noticed that the law forbids the retention, dissemination, distribution, copy or use without express authorization from the sender. Personal opinions of the sender do not necessarily reflect CETIP's point of view, which is only divulged by authorized personnel. ***
Re: Drop wicket:link
That's my opinion, also. I voted -1 to removing wicket:link. I was more just curious about the inner workings of the parser at this point :) On Tue, Nov 18, 2008 at 4:59 PM, Peter Ertl [EMAIL PROTECTED] wrote: What's the problem with just leaving it where it is? If you don't like it ignore it - or am I missing something important here? Am 18.11.2008 um 22:12 schrieb James Carman: Would the user have to register the plugin manually or would it be picked up merely by the jar being on the classpath? On Tue, Nov 18, 2008 at 4:01 PM, Igor Vaynberg [EMAIL PROTECTED] wrote: it is already all pluggable and wicketlink handler is just a plugin into the parser :) -igor On Tue, Nov 18, 2008 at 12:29 PM, James Carman [EMAIL PROTECTED] wrote: The markup parser has to know how to deal with it I would think. That would be quite an undertaking to split that functionality out and make it able to be plugged back in. On Tue, Nov 18, 2008 at 3:23 PM, Rodolfo Hansen [EMAIL PROTECTED] wrote: +1, what about moving it to an optional package? wicket-tags ? On Tue, Nov 18, 2008 at 2:09 PM, Peter Ertl [EMAIL PROTECTED] wrote: -1, too: I use it just the way Igor describes. I usually set up a mock html page, then wicket:link the css and javascript. So I can easily test the page in preview mode and in wicket, too. Once the application evolves I tend to remove wicket:link again and replace it with ResourceReference inside the pages and base pages. Let it there, it's really useful. If people tend to be stupid no framework on earth will stop them from doing so. Cheers Peter Am 17.11.2008 um 21:06 schrieb Igor Vaynberg: -1. this stuff is very useful for linking to css/js/image files. if people want to abuse it, it is their problem. people will find a way to abuse anything though. -igor 2008/11/17 Bruno Cesar Borges [EMAIL PROTECTED]: This might sound crazy, but what about dropping the support for the tag wicket:link ? :-) People are starting to use it frequently, and because of that, features will be requested. And then we might end with a tag library. But, to not freak everybody out, I suggest develop a markup container to do that. Example: # Java AutoLinkMarkupContainer autolinks = new AutoLinkMarkupContainer(menus); # HTML ul wicket:id=menus lia href=Users.htmlUsers/a/li lia href=Departments.htmlDepartments/a/li /ul What do you guys think? Cheers, Bruno *** Atenção: Esta mensagem foi enviada para uso exclusivo do(s) destinatários(s) acima identificado(s), podendo conter informações e/ou documentos confidencias/privilegiados e seu sigilo é protegido por lei. Caso você tenha recebido por engano, por favor, informe o remetente e apague-a de seu sistema. Notificamos que é proibido por lei a sua retenção, disseminação, distribuição, cópia ou uso sem expressa autorização do remetente. Opiniões pessoais do remetente não refletem, necessariamente, o ponto de vista da CETIP, o qual é divulgado somente por pessoas autorizadas. Warning: This message was sent for exclusive use of the addressees above identified, possibly containing information and or privileged/confidential documents whose content is protected by law. In case you have mistakenly received it, please notify the sender and delete it from your system. Be noticed that the law forbids the retention, dissemination, distribution, copy or use without express authorization from the sender. Personal opinions of the sender do not necessarily reflect CETIP's point of view, which is only divulged by authorized personnel. ***
