Re: [JBoss-dev] Need a head svn/migration death march list
Yes, we need this. The list of tasks is growing as we prototype. I'm free on after the webex. On Apr 14, 2006, at 11:10 AM, Scott M Stark wrote: I want to put together a list of tasks that will get head migrated to maven/svn by the end of this quarter. All wailing and gnashing of teeth will be ignored. Meaningful input during the definition of the task list will most likely be accepted, but depends on its inertial drag to the march. Can we do a call with Ruel, Damon, Ryan + interested parties this coming Tuesday after the productization webex? Scott Stark VP Architecture Technology JBoss Inc. --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnkkid0944bid$1720dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: Ongoing build changes: was RE: [JBoss-dev] OntheedgeoftheMaven cliff
You know my vote. On Feb 11, 2006, at 5:47 AM, Adrian Brock wrote: On Sat, 2006-02-11 at 04:33, Adrian Brock wrote: On Fri, 2006-02-10 at 13:28, Scott M Stark wrote: Let's do that. Do you want to couple this to maven? It would help Ruel I suppose. We may as well go Big Bang!. :-) Speaking of Big Bang. It might be idea to convert to subversion at the same time. Given we want to refactor the project structures to native Maven we could: 1) Import CVS into SVN 2) Use SVN rename to rework the project structure 3) Keep the history attached to those files! http://weblogs.java.net/blog/joshy/archive/2005/03/ subversion_rena.html -- Adrian Brock Chief Scientist JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel? cmd=lnkkid=103432bid=230486dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid=103432bid=230486dat=121642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: Ongoing build changes: was RE: [JBoss-dev] OntheedgeoftheMavencliff
Adding them now... ;-) On Feb 11, 2006, at 2:38 PM, Scott M Stark wrote: That would be a way to actually start with a 4.0 branch fork which might be more manageable due to fewer changes to merge between the cvs and svn repositories. Can we get the jboss-4.0.x and jboss-head contents moved into svn Damon? -Original Message- From: Adrian Brock Sent: Saturday, February 11, 2006 3:48 AM To: Scott M Stark Cc: jboss-development@lists.sourceforge.net; QA Subject: RE: Ongoing build changes: was RE: [JBoss-dev] OntheedgeoftheMavencliff On Sat, 2006-02-11 at 04:33, Adrian Brock wrote: On Fri, 2006-02-10 at 13:28, Scott M Stark wrote: Let's do that. Do you want to couple this to maven? It would help Ruel I suppose. We may as well go Big Bang!. :-) Speaking of Big Bang. It might be idea to convert to subversion at the same time. Given we want to refactor the project structures to native Maven we could: 1) Import CVS into SVN 2) Use SVN rename to rework the project structure 3) Keep the history attached to those files! http://weblogs.java.net/blog/joshy/archive/2005/03/ subversion_rena.html -- Adrian Brock Chief Scientist JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: Ongoing build changes: was RE: [JBoss-dev] OntheedgeoftheMavencliff
Yes, svn:externals are a good way to go. It all depends on how much interdependency you have between your subcomponents and whether or not you've decided to offer those subcomponents as independent projects. It's something we definitely need to talk about. On Feb 11, 2006, at 3:08 PM, Scott M Stark wrote: Tim is suggesting that if we plan on moving modules around, Subversion's svn:externals facility might be something we want to examine as a mechanism for relating components (and different versions of those components) to large deliverables. You end up storing each distinct component in a normal trunk, tags, branches directory that subversion users are used to, and you aggregate components into larger releases using the svn:externals property on a directory. He found this method to be helpful becuase it allows you to create releases of independently versioned subcomponents. Maven uses it here: http://svn.apache.org/repos/asf/maven/trunks/ Jakarta Commons uses it here: http://svn.apache.org/repos/asf/jakarta/commons/trunks-proper/ -Original Message- From: Adrian Brock Sent: Saturday, February 11, 2006 3:48 AM To: Scott M Stark Cc: jboss-development@lists.sourceforge.net; QA Subject: RE: Ongoing build changes: was RE: [JBoss-dev] OntheedgeoftheMavencliff On Sat, 2006-02-11 at 04:33, Adrian Brock wrote: On Fri, 2006-02-10 at 13:28, Scott M Stark wrote: Let's do that. Do you want to couple this to maven? It would help Ruel I suppose. We may as well go Big Bang!. :-) Speaking of Big Bang. It might be idea to convert to subversion at the same time. Given we want to refactor the project structures to native Maven we could: 1) Import CVS into SVN 2) Use SVN rename to rework the project structure 3) Keep the history attached to those files! http://weblogs.java.net/blog/joshy/archive/2005/03/ subversion_rena.html -- Adrian Brock Chief Scientist JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
Re: Ongoing build changes: was RE: [JBoss-dev] OntheedgeoftheMavencliff
OK... Seriously... It will take me about 15 mins to do the import, but more importantly, I'll need to get the list of committers added to the proper branch structures in svn. This will take me a bit of time to do first, but, I'll start now. After they are added, you can easily coordinate people using the new repo at your leisure. Do you have a list of committers, and only those committers, you want for these branches? Is there a subset of all the committers? Since we have directory level access controls, we can do this, and I recommend it. Also, I'd recommend making the switch.. officially... after Eric and TomBen get the anonsvn off the fisheye, committer, cvs, and [insert- every-other-app-here] machine. It's currently running at a load of 10 on a single proc machine (or something close). Eric? On Feb 11, 2006, at 2:38 PM, Scott M Stark wrote: That would be a way to actually start with a 4.0 branch fork which might be more manageable due to fewer changes to merge between the cvs and svn repositories. Can we get the jboss-4.0.x and jboss-head contents moved into svn Damon? -Original Message- From: Adrian Brock Sent: Saturday, February 11, 2006 3:48 AM To: Scott M Stark Cc: jboss-development@lists.sourceforge.net; QA Subject: RE: Ongoing build changes: was RE: [JBoss-dev] OntheedgeoftheMavencliff On Sat, 2006-02-11 at 04:33, Adrian Brock wrote: On Fri, 2006-02-10 at 13:28, Scott M Stark wrote: Let's do that. Do you want to couple this to maven? It would help Ruel I suppose. We may as well go Big Bang!. :-) Speaking of Big Bang. It might be idea to convert to subversion at the same time. Given we want to refactor the project structures to native Maven we could: 1) Import CVS into SVN 2) Use SVN rename to rework the project structure 3) Keep the history attached to those files! http://weblogs.java.net/blog/joshy/archive/2005/03/ subversion_rena.html -- Adrian Brock Chief Scientist JBoss Inc. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnkkid3432bid#0486dat1642 ___ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
[JBoss-dev] SVN Commit Email List
Dev,Just a reminder, as I keep getting asked how to subscribe to the svn commit email list, here's the link to the SF page to subscribe:https://lists.sourceforge.net/lists/listinfo/jboss-svn-commitsSincerely,Damon --- [EMAIL PROTECTED] JBoss Labs Lead 214-883-6733 36FD 368C 38E4 2DA2 6E2C C0A6 FA7F 8A87 EA10 65A9 Public Key: http://keys.sicore.org/jboss.txt
[JBoss-dev] JBoss Labs 1.0.8 Released
Labs,Yesterday we upgraded Labs to release 1.0.8. I've included the release notes below, but I wanted to tell everyone about a few of the key updates. With the exception of myself, the Labs team is in the middle of finals (remember college?) in Poland, so, I'm really pleased with the work Adam, Tomek, Pawel, and Ryseik are doing. As usual, they've managed to push out more portlets, functionality, and stability enhancements in a timely manner.This release includes the following new features:* Project Polls - Each project now has the ability to create a number of polls to be displayed on their project information pages. In addition to being displayed on their own project page, the main JBoss Labs page aggregates all the Polls and displays a random subset. If you are a project lead and want to place a poll on your project page, you can view the poll wiki page at:http://labs.jboss.com/wiki/Polls* The JEMS Maturity Matrix, Alpha Version - One of Labs' goals is to help track open source projects' statistics. We're trying to aggregate various categories of data and put them into some form of ranking mechanism. This means that statistics like community interaction (i.e., downloads, forum posts, and JIRA issues), QA Statistics (test suite integration and automated builds), and Productization Metrics (JEMS Integration) are placed together in a single matrix with weighted scores. This release shows us the framework is in place for gathering and presenting these statistics. Now, the next several releases will be a tuning effort to correlate the numbers, visualization, and rankings. You can view the alpha of this effort on our Development Dashboard:http://labs.jboss.com/portal/index.html?ctrl:id=page.default.statusnoproject=trueWe are specifically looking for feedback on how to enhance this portlet.* Feeds and Podcast enhancements - It's really a snap to create a feed of any type of content in JBoss Labs. With this release, we can basically remove the use of Blojsom and have a single integrated mechanism to generate feeds using our content repository. With this release, we've enhanced some of the portlets to use more information contained within feeds, such as the episode images you now see on Labs (i.e., Marshall holding the "Will Use JBoss IDE for Food" sign.) Each project can have their own feeds for any type of content. If you want a feed for your project, you can request one using the [EMAIL PROTECTED] email alias.Other news is that JBoss AS, JBoss AOP, JBoss Clustering, and JBossCache have certified their projects to be hosted on JBoss Labs. This means that all their project information pages and links to things like downloads, jira, and documentation are correct and ready to be hosted on Labs. Also JBoss Rules is actively using Subversion on Labs as well as building out their project information pages. We're still working on importing the Arjuna code base because they want an entire set of history, but they will be online in Subversion soon.We're pleased to announce that JBoss Wiki supports Japanese now. Ben Wang and crew are also trying out Chinese. We've some community interest in translating wiki pages to Japanese. Thanks to the Portal team for a great product that allows us to do this easily within a portlet.Sincerest Regards,DamonRelease Notes for JBoss Labs Includes versions: Labs 1.0.8 ** Bug * [ JBLAB-571 ] Investigate incorrect date parsing of atom feeds by Rome * [ JBLAB-576 ] ResourceWatcher doesn't notice file delete. ** Feature Request * [ JBLAB-407 ] Create a Poll Portlet manageable by the project-lead * [ JBLAB-540 ] Itunes tags parsing in Podcast Portlet. ** Task * [ JBLAB-399 ] Fix Colors in Open Issues By Priority * [ JBLAB-403 ] Development Dashboard: SVN stats should be by project not dir location * [ JBLAB-415 ] High Level Project Status Snapshot Dashboard Portlet * [ JBLAB-493 ] Write a wiki page explaining how to use and configure the podcast portlet * [ JBLAB-554 ] Adding new primates. * [ JBLAB-562 ] Investigate Creating Maven Repository Hosted by Labs * [ JBLAB-572 ] Make the blog portlet configurable through cms * [ JBLAB-577 ] Create a Downloads Plugin for JEMS Matrix * [ JBLAB-580 ] Weighted score plugin for JEMS Matrix * [ JBLAB-581 ] DownloadCounters features of setting visibility and sorting * [ JBLAB-582 ] Move dynamicly changed files outside of portal-content * [ JBLAB-584 ] Better buttons for the contributor links * [ JBLAB-585 ] Prepare release of 1.0.8 * [ JBLAB-592 ] Create Polls wiki page and update of DownloadCounters' wiki page * [ JBLAB-594 ] Labs 1.0.8 Promote --- [EMAIL PROTECTED] JBoss Labs Lead 214-883-6733 36FD 368C 38E4 2DA2 6E2C C0A6 FA7F 8A87 EA10 65A9 Public Key: http://keys.sicore.org/jboss.txt
[JBoss-dev] Subversion Repo Maintenance - Arjuna Import
JBoss Developers,The Subversion repositories at https://svn.labs.jboss.com and http://anonsvn.labs.jboss.com will be down tonight for the import of the Arjuna (as the jbosstm project) code base and revision history into our repository. This will begin at 9pm GMT-5 (EST) tonight (11Jan06) and will last for approx one hour.Sincerely,Damon--- [EMAIL PROTECTED] JBoss Labs Lead 214-883-6733 36FD 368C 38E4 2DA2 6E2C C0A6 FA7F 8A87 EA10 65A9 Public Key: http://keys.sicore.org/jboss.txt
[JBoss-dev] [JBoss JIRA] Created: (JBPORTAL-194) When using an IP that isn't localhost, the Admin CMS Portlet is empty due to incorrect portlet.xml entry
When using an IP that isn't localhost, the Admin CMS Portlet is empty due to incorrect portlet.xml entry Key: JBPORTAL-194 URL: http://jira.jboss.com/jira/browse/JBPORTAL-194 Project: JBoss Portal Type: Bug Components: Portal Core Versions: 2.0 Alpha Environment: RedHat 2.4.21-27.0.2.ELsmp , jdk 1.4.2_06, Reporter: Damon Sicore Assigned to: Julien Viet Whenever a portal is deployed on an IP that doesn't resolve to localhost, the Admin CMS Portlet is empty. A Connection Refused will appear in STDOUT as an exception related to WebDAV. It's not exactly clear that one needs to change the 'localhost' in portlets.xml to the IP that you are binding to in your 'run.sh -b whateverip -c standard'. 16:30:17,402 INFO [STDOUT] /portal 16:30:17,416 INFO [STDOUT] java.net.ConnectException: Connection refused 16:30:17,417 INFO [STDOUT] at java.net.PlainSocketImpl.socketConnect(Native Method) 16:30:17,417 INFO [STDOUT] at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:305) 16:30:17,417 INFO [STDOUT] at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:171) 16:30:17,418 INFO [STDOUT] at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:158) 16:30:17,418 INFO [STDOUT] at java.net.Socket.connect(Socket.java:452) 16:30:17,418 INFO [STDOUT] at java.net.Socket.connect(Socket.java:402) 16:30:17,418 INFO [STDOUT] at java.net.Socket.init(Socket.java:309) 16:30:17,418 INFO [STDOUT] at java.net.Socket.init(Socket.java:124) 16:30:17,418 INFO [STDOUT] at org.apache.commons.httpclient.protocol.DefaultProtocolSocketFactory.createSocket(DefaultProtocolSocketFactory.java:105) 16:30:17,418 INFO [STDOUT] at org.apache.commons.httpclient.HttpConnection.open(HttpConnection.java:683) 16:30:17,418 INFO [STDOUT] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:661) 16:30:17,418 INFO [STDOUT] at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:529) 16:30:17,419 INFO [STDOUT] at org.apache.webdav.lib.WebdavResource.propfindMethod(WebdavResource.java:3457) 16:30:17,419 INFO [STDOUT] at org.apache.webdav.lib.WebdavResource.propfindMethod(WebdavResource.java:3423) 16:30:17,419 INFO [STDOUT] at org.apache.webdav.lib.WebdavResource.setNamedProp(WebdavResource.java:967) 16:30:17,419 INFO [STDOUT] at org.apache.webdav.lib.WebdavResource.setBasicProperties(WebdavResource.java:912) 16:30:17,419 INFO [STDOUT] at org.apache.webdav.lib.WebdavResource.setProperties(WebdavResource.java:1894) 16:30:17,419 INFO [STDOUT] at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1301) 16:30:17,419 INFO [STDOUT] at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1320) 16:30:17,419 INFO [STDOUT] at org.apache.webdav.lib.WebdavResource.setHttpURL(WebdavResource.java:1408) 16:30:17,419 INFO [STDOUT] at org.apache.webdav.lib.WebdavResource.setPath(WebdavResource.java:1469) 16:30:17,420 INFO [STDOUT] at org.jboss.portal.core.portlet.cms.WebDAVUtil.setCurrentPath(WebDAVUtil.java:103) 16:30:17,420 INFO [STDOUT] at org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet$1.perform(AdminCMSPortlet.java:128) 16:30:17,420 INFO [STDOUT] at org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.perform(AdminCMSPortlet.java:88) 16:30:17,420 INFO [STDOUT] at org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.doView(AdminCMSPortlet.java:115) 16:30:17,420 INFO [STDOUT] at javax.portlet.GenericPortlet.doDispatch(GenericPortlet.java:51) 16:30:17,420 INFO [STDOUT] at org.jboss.portal.core.portlet.cms.admin.AdminCMSPortlet.render(AdminCMSPortlet.java:851) 16:30:17,420 INFO [STDOUT] at org.jboss.portal.portlet.invocation.DispatcherInterceptor.invokeRequest(DispatcherInterceptor.java:143) 16:30:17,420 INFO [STDOUT] at org.jboss.portal.portlet.invocation.DispatcherInterceptor.invoke(DispatcherInterceptor.java:171) 16:30:17,420 INFO [STDOUT] at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:214) 16:30:17,421 INFO [STDOUT] at org.jboss.portal.core.portlet.cms.CMSInterceptor.invoke(CMSInterceptor.java:78) 16:30:17,421 INFO [STDOUT] at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:214) 16:30:17,421 INFO [STDOUT] at org.jboss.portal.portlet.invocation.PreferencesInterceptor.invoke(PreferencesInterceptor.java:93) 16:30:17,421 INFO [STDOUT] at org.jboss.portal.server.impl.invocation.InvocationImpl.invokeNext(InvocationImpl.java:214) 16:30:17,421 INFO [STDOUT] at org.jboss.portal.server.invocation.component.ContextDispatcherInterceptor$InvokeNextCommand.execute(ContextDispatcherInterceptor.java:94) 16:30:17,421 INFO [STDOUT
