Message from Dimitris Andreadis Most recent post: 7/7/2006 2 authors and 2 replies. Hello, JBossAS-4.0.5.CR1 is scheduled for release on the 21st of August. We really want to keep this release minimal, driven by the most important user/customer needs, since we've higher priorities (i.e. JB5). The list of pending JIRA issues is quite long at this point (138, due to overflow from the previous 4.0.4 release) but we will shamelessly reduce it by deferring stuff until we get to a manageable set that can be implemented within the next 4 weeks, in parallel to whatever else you do. August 4th will be the *LAST* day for any new feature/bug fix, after that it's integration/test tasks only. Please, try to make it for the target date, we simply can not afford the cost of introducing last minutes changes (and it has happened quite a few times before). If there are dependencies we should be aware of (your project A, depends on project B, that needs unfinished project X), make it clear in JIRA. If there are other issues (technical or otherwise) make them known early. So the action points: 1) Developers/Leads - Browse the JBossAS-4.0.5.CR1 tasks, decide what can be solved by Aug/4th, reject or defer everything else to 4.0.6.CR1: http://jira.jboss.com/jira/browse/JBAS 2) Support - Help us define priorities. Raise priorities (Critical) to the issues that *MUST* make it for the release. Create issues, if there is something missing. Cheers /Dimitris-- xxxxxxxxxxxxxxxxxxxxxxxxxxxx Dimitris Andreadis AS Development Manager JBoss, a Div read more about JBossAS-4.0.5.CR1
Message from Heiko Braun Most recent post: 6/29/2006 2 authors and 2 replies. The latest XB version introduced a dependency towards JAF and JAVA Mail. Currently these jars reside under <JBOSS>/server/<config>/lib and are not visible to the XB classloader. Moving them to <JBOSS>/lib does not work, because the bootstrap process uses a hard coded set of libraries. The current workaround is to move JAF & Mail to lib/endorsed, in order to have them available at bootstrap time. Does someone have an idea how to solve this problem without a) modifying the bootstrap classes b) using that workaround ? /HeikoUsing Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 read more about JBossXB dependencies
Message from Ryan Campbell Most recent post: 6/28/2006 2 authors and 3 replies. --===============0010311878== Content-class: urn:content-classes:message This is complete; the JIRA server is online. Please report any issues to jira-admin@xxxxxxxxxxx . _____________________________________________ From: Ryan Campbell=20 Sent: Tuesday, June 27, 2006 8:15 AM To: The Core; jboss-development@xxxxxxxxxxx Cc: QA; IT Ops Subject: JIRA Downtime/Upgrade at 8 PM EDT Today We are upgrading the JIRA instance to a faster box, and the latest version of JIRA. The main purpose of this upgrade is reduced downtime and improved performance. JIRA will go down at 8 PM EDT. It'll remain offline until the migration is complete. I expect it to be back online early in the morning, EDT, and will send out a notice once the new server is live. See below for the new features you can expect from this upgrade: http://confluence.atlassian.com/display/JIRA/JIRA+3.3+Release+Notes=20 http://confluence.atlassian.com/display/JIRA/JIRA+3.4+and+3.4.1+Release+ Notes=20 http://confluence.atlassian.com/display/JIRA/JIRA+3.5+Release+Notes=20 http://confluence.atlassian.com/display/JIRA/JIRA+3.6+Release+Notes In addition to this, we'll be deploying the Fisheye plugin for more reliable integration with CVS and SVN. As a note, this deployment will only include the "Release Notes Report" custom plugin. The additional Global Reports (developer involvement, issues closed, developers per project, etc) will be deployed at a later, to be determined time. read more about JIRA back online (was RE: JIRA Downtime/Upgrade at 8 PMEDT Today)
Message from Tim Fox Most recent post: 6/26/2006 3 authors and 5 replies. I'm getting the following after doing a cvs update -C in HEAD and then a build clean: BUILD FAILED C:\dev\jboss-head\build\build.xml:999: The following error occurred while execut ing this line: C:\dev\jboss-head\build\build-thirdparty.xml:140: A versioning problem exists: Component: jboss/jbossxb is at version: 1.0.0.CR4 but it is also required to be compatible with: [Compatible@xxxxxxxxxxx{id=null, ver sion=1.0.0.CR5}, Compatible@xxxxxxxxxxx{id=null, version=snapshot}] by: jboss/jbossws14 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 read more about can not build
Message from Tim Fox Most recent post: 6/24/2006 2 authors and 2 replies. I have noticed that some (most?) of the library entries on the JAVA build path (Eclipse) for many of the projects start with a leading slash: /thirdparty/jboss/profiler/jvmti/lib. This means on my system that the libraries cannot be found since I do not checkout jboss head into the root of the volume. So, every time I update from CVS I have to remove all the leading slashes so eclipse relative to the top of my workspace where the libraries will be found. Is there any reason for having the leading slashes? Or perhaps I am doing something wrong and somehow I can get eclipse to interpret the leading slash as being at the root of my workspace. Any ideas? Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 read more about Leading slashes on jars in build path