IcedTea6 compilation issue (JBMETA-224)
by Richard Opalka
Hi folks,
JBMETA-224 is closed but I'm still not able to
build jboss-metadata-common with OpenJDK :(
Should I reopen it or create new one?
Thanks,
Rio
-- Richard Opalka ropalka(a)redhat.com JBoss, by Red Hat Office: +420 222
365 200 Mobile: +420 731 186 942
14 years, 3 months
Project Versions in jbossas/trunk
by Shelly McGowan
Referencing this wiki:
http://community.jboss.org/wiki/JBossProjectVersioning
A Candidate Release qualifier is for releases that we anticipate can be the GA release.
The 6.0.0.CR1 release is anticipated to be *the* GA release with a few additional bug fixes.
There are currently 32 components in jbossas/trunk/component-matrix/pom.xml that are versioned with
the Alpha qualifier, 18 Beta.
>From the same wiki:
The use of Alpha is for early releases that are not API complete.
The use of Beta qualifier is for releases where the release is API complete, but its not completely tested,
or there may even be questions about the API itself that may change, even though the implementation is complete.
Is this convention being followed? If so, jbossas/trunk has 50 components that are not API complete or may change?
Trying to get a clear roadmap of the upgrades expected. There are only 6 identified in https://jira.jboss.org/browse/JBAS-8253.
Appreciate if the project leads can add a subtask if an upgrade is planned for 6.0.0.CR1.
14 years, 3 months
JBoss AS 6.0 Roadmap
by Shelly McGowan
The time line for the final releases of JBoss AS 6 as follows:
6.0.0.CR1:
Code Freeze: November 10
Release Target: November 15
Component Upgrades: https://jira.jboss.org/browse/JBAS-8253
This release will focus on the remaining work needed for EE 6 Web Profile compliance.
6.0.0.Final:
Code Freeze: December 10
Release Target: December 17
Component Upgrades: https://jira.jboss.org/browse/JBAS-8086
The Final release time is limited and is intended to Resolve Major JIRA issues and finalize community documentation.
Be sure to file a subtask if you are planning on a component upgrade. Component upgrades will be reverted due
to regression, destabilization, or impact to the certification effort.
Shelly McGowan
JBoss, by Red Hat
14 years, 3 months
VHosts in AS 6 and naming
by Remy Maucherat
Hi,
In AS 5 (I believe), we added the capability to deploy a webapp to
multiple vhosts. While nice in practice, this causes the need for a
hack where one webapp can be deployed multiple times to each specified
vhost, as well as automagic vhost creation. I've never liked this
behavior (I think vhost creation should require some administrator
intervention), and this hack is now causing problems with the new
naming. It should be possible to drop this feature to a large extent.
Instead, what could happen is that the list of specified vhosts would
now need to either point to one single existing host (any non existing
vhosts would be added as aliases to that vhost). If nothing exists,
they would be added as aliases to the default host.
This should actually cover most reasonable use cases.
Rémy
14 years, 3 months
