JBoss AS 6.0.0.Final Tagged today at 20:00
by Shelly McGowan
The final release of JBoss AS 6 will be tagged today, December 23 at 20:00.
I'll reply to this list when jbossas/trunk is OPEN again.
Shelly McGowan
JBoss, by Red Hat
13 years, 4 months
Meet Byteman at JBoss Asylum
by Andrew Dinn
Not to be confused with Arkham Asylum, JBoss Community Asylum is a
podcast about, for and by the JBoss Community. It provides news about
what the JBoss community is up, including interviews with JBoss
developers. The latest sensational podcast reveals the identity of the
man behind the mask, Byteman lead developer Andrew Dinn. If you want to
hear how Byteman chases down and banishes evil bugs or find out how
Byteman was conceived and grew into one of software's toughest enforcers
then tune in to the JBoss Asylum Byteman Christmas Special at
http://in.relation.to/Bloggers/Podcast16BytemanBegins
regards,
Andrew Dinn
-----------
13 years, 4 months
AS6 trunk + MC libs update
by Ales Justin
I've just updated AS6_trunk' MC libs: JBAS-8686.
Since this changes the "rug" completely,
(all MC sub-projects were given a slight facelift :-)
let me know if you find any issues related to this change.
13 years, 4 months
Re: [jboss-dev] AS 6 Final Code Freeze: Friday, December 17
by Shelly McGowan
Finish line in sight . . .
. . . few days left and a many component upgrades expected.
Be sure to test and test before committing to jbossas/trunk.
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Shelly McGowan" <smcgowan(a)redhat.com>
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Tuesday, December 7, 2010 10:14:00 AM GMT -05:00 US/Canada Eastern
Subject: AS 6 Final Code Freeze: 10 Days and Counting
The Final code freeze is scheduled for Friday, December 17. There are still component upgrades planned and bug fixes
identified for inclusion. The test suites have remained stable in this final phase with only 10 failures
in the overall AS integration suite.
If there are issues that you plan to resolve by the freeze be sure there is a JBAS JIRA filed.
One other goal of the release is to be sure that our AS 6 documentation represents the functionality
provided in the Final distribution.
AS 6 documentation is being tracked here:
https://jira.jboss.org/browse/JBAS-8005
If you have contributions to the documentation, be sure to comment there.
The documentation for AS 6 and/or references using specific technologies with AS 6 can
be seen here:
http://community.jboss.org/wiki/JBossApplicationServerOfficialDocumentati...
Let's wrap this up in time for the holidays.
Shelly McGowan
JBoss, by Red Hat
13 years, 4 months
Re: [jboss-dev] AS 6 Final Code Freeze: Friday, December 17
by Shelly McGowan
Max,
Updated:
https://issues.jboss.org/browse/JBIDE-7876?focusedCommentId=12569994&page...
For JBAS-8734, Rob states that this worked with JBoss 5 but only after a 'patch' was applied to it:
https://issues.jboss.org/browse/JBIDE-7822?focusedCommentId=12569536&page...
So is the issue your patch does not work on AS 6?
Let's discuss off-line?
Shelly McGowan
JBoss, by Red Hat
----- Original Message -----
From: "Max Rydahl Andersen" <max.andersen(a)redhat.com>
To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
Sent: Tuesday, December 14, 2010 8:39:32 AM GMT -05:00 US/Canada Eastern
Subject: Re: [jboss-dev] AS 6 Final Code Freeze: Friday, December 17
Hi Shelly,
Just wanted to make you aware of two issues we've spotted with respect to different behavior from AS 5 to AS 6
https://jira.jboss.org/browse/JBIDE-7876
AS 6 no longer seem to pick up jdbc drivers from server/lib but now expects them in server/<configname>/lib - is this expected ? We can change
this behavior - but it means we will have to deploy the jar to *every* <configname>/lib for AS 6 to be sure we hit the right one and I don't want to change
it if its just a "bug" in later AS 6's.
https://issues.jboss.org/browse/JBAS-8734
AS 6 can't handle deployment URL's with spaces (even encoded ones); AS 5 can.
These are rather annoying bugs/changes causing problems for newbies (jdbc driver deploy) and especially Windows users which
default installation will have spaces in the names.
Thanks!
/max
On Dec 13, 2010, at 20:32, Shelly McGowan wrote:
>
>
> Finish line in sight . . .
>
> . . . few days left and a many component upgrades expected.
>
> Be sure to test and test before committing to jbossas/trunk.
>
>
> Shelly McGowan
> JBoss, by Red Hat
>
> ----- Original Message -----
> From: "Shelly McGowan" <smcgowan(a)redhat.com>
> To: "JBoss.org development list" <jboss-development(a)lists.jboss.org>
> Sent: Tuesday, December 7, 2010 10:14:00 AM GMT -05:00 US/Canada Eastern
> Subject: AS 6 Final Code Freeze: 10 Days and Counting
>
>
>
>
> The Final code freeze is scheduled for Friday, December 17. There are still component upgrades planned and bug fixes
> identified for inclusion. The test suites have remained stable in this final phase with only 10 failures
> in the overall AS integration suite.
>
> If there are issues that you plan to resolve by the freeze be sure there is a JBAS JIRA filed.
>
> One other goal of the release is to be sure that our AS 6 documentation represents the functionality
> provided in the Final distribution.
>
> AS 6 documentation is being tracked here:
> https://jira.jboss.org/browse/JBAS-8005
>
> If you have contributions to the documentation, be sure to comment there.
>
> The documentation for AS 6 and/or references using specific technologies with AS 6 can
> be seen here:
>
> http://community.jboss.org/wiki/JBossApplicationServerOfficialDocumentati...
>
>
> Let's wrap this up in time for the holidays.
>
>
> Shelly McGowan
> JBoss, by Red Hat
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development
13 years, 4 months
tmp/ delete
by Ales Justin
So that I'm not searching for a needle in the haystack,
who could tell me how exactly we used to do this (https://issues.jboss.org/browse/JBAS-8718) in the past.
(as it looks like we're missing that functionality atm in AS6 ...)
1) Where did we create tmp/ dir?
Or was this done per each custom sub-dir via File::makedirs?
2) Where and when did we delete it?
* at startup -- simply deleting old tmp/; which is probably more bullet proof than at shutdown
* at shutdown
* ...
Thanks for any help / tip.
13 years, 4 months
VFS3 (in AS trunk) - Non .jar file handling
by Jaikiran Pai
I see a new behaviour with VFS3 in JBoss AS. Earlier in AS-5/6 (with
VFS2) and AS-4 (without any VFS), to try out some quick fixes, i used to
rename existing jar files to end with .bak name and replace them with
the new patched jar file. So for example, if i had a fix in
jboss-ejb3-core.jar, i would:
1) Rename the JBOSS_HOME/common/lib/jboss-ejb3-core.jar to
JBOSS_HOME/common/lib/jboss-ejb3-core.jar.orig.bak
2) Place a patched jboss-ejb3-core.jar in JBOSS_HOME/common/lib
3) Restart the server
The server would then pickup the new patched jar file and ignore the
.bak file. After testing the fix, i would then revert back to the
original jar file by renaming it back to its original name.
However, with the recent upgrade to VFS3 in AS trunk, i notice that even
the .bak is used for classloading (following is the output from
-verbose:class JVM argument):
[Loaded org.jboss.ejb3.EJBContainer from
file:/NotBackedUp/jpai/business/jboss/wc/jbossas/trunk/build/target/jboss-6.0.0-SNAPSHOT/common/lib/jboss-ejb3-core.jar.orig.bak/]
Looks like VFS3 picks up this non .jar suffix file for classloading. Is
this expected? Shouldn't it be looking for only .jar files (atleast in
this context)?
regards,
-Jaikiran
13 years, 4 months
as6 build logging and warnings
by Alexey Loubyansky
It logs an enormous amount of info (mostly at INFO level). So much that
it seems like warnings might not catch attention anymore and have to be
searched.
Here are a few that might be useful.
[WARNING] Some problems were encountered while building the effective
model for org.jboss.jbossas:jboss-as-webservices:jar:6.0.0-SNAPSHOT
[WARNING] The expression ${version} is deprecated. Please use
${project.version} instead.
[WARNING]
[WARNING] Some problems were encountered while building the effective
model for org.jboss.jbossas:weld-int-deployer:jar:6.0.0-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: org.jboss.metadata:jboss-metadata-ejb:jar -> duplicate
declaration of version (?) @ line 517, column 17
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
There is a lot of this one (the build was launched with ./build.sh, not
my mvn install)
[WARNING] This rule is not compatible with the current version of Maven.
The rule is not able to perform any checks.
[WARNING] Warning in manifest for
org.jboss.jbossas:jboss-as-resteasy:jar:6.0.0-SNAPSHOT : Superfluous
export-package instructions: [org.jboss.resteasy.integration, org.jboss,
org.jboss.resteasy, org]
[INFO] Processing DependencySet (output=resteasy.deployer)
[WARNING] Cannot include project artifact:
org.jboss.jbossas:resteasy-int-dist:pom:6.0.0-SNAPSHOT; it doesn't have
an associated file or directory.
...
[INFO] Reading assembly descriptor: src/assembly/xmlentitymgr.xml
[WARNING] The assembly id deployment-service is used more than once.
[WARNING] The assembly id snmp-adaptor is used more than once.
13 years, 4 months
