JBoss Java EE Specs Project a.k.a. JBEE-15
by Shelly McGowan
The first phase of the JBoss Java EE API specs project has been completed.
The APIs that existed in:
http://svn.jboss.org/repos/jbossas/projects/javaee/
have been moved to a new svn repo:
http://svn.jboss.org/repos/jbossas/projects/specs/
with a new naming convention as previously discussed on this email list and
here:
http://community.jboss.org/thread/146657
The releases of the APIs are versioned as 1.0.0.Beta1 and have been integrated
into JBoss AS 6. The API signature tests were run against these versions and some
issues were identified. JIRAs were filed and assigned accordingly.
The goals of this project can be seen here:
http://community.jboss.org/wiki/JBossJavaEEAPIProject
Phase 2 of this task will be to review the 1.0.0.Beta1 releases and prepare
for final releases including any JavaDoc edits that are needed.
Additional APIs have been identified to be brought into this project and filed as sub-tasks of JBEE-15.
I can bring those into the project and integrate into AS when ready
but would like to coordinate with project leads.
If you have any questions about the project restructure or adding your APIs, please let me know.
Shelly
14 years, 1 month
VFS3 update breaks MC update
by Ales Justin
VFS3 update to CR4 breaks my recent MC updates:
Caused by: java.lang.NoSuchMethodError: org.jboss.vfs.VFS.mountTemp(Lorg/jboss/vfs/VirtualFile;Lorg/jboss/vfs/TempFileProvider;)Ljava/io/Closeable;
at org.jboss.deployers.vfs.plugins.classloader.InMemoryClassesDeployer.deploy(InMemoryClassesDeployer.java:88)
Can we revert the VFS or do I need to revert all MC changes?
14 years, 1 month
Tattletale 1.1 released
by Jesper Pedersen
Tattletale 1.1 released [1]
I'm very happy to announce the availability of the Tattletale 1.1, the Java
dependency analyzer, release.
A lot of features have been added over the last year, so I'll give a brief
run-down of some of them. See our documentation for full details.
Profiles
Tattletale now features known "profiles", which are well-known APIs targeting
the Java Standard or Java Enterprise platforms.
The list of profiles are
* Java 5 and Java 6
* Java Enterprise Edition 5 and Java Enterprise Edition 6
* Spring 2.5 and Spring 3.0
* Contexts and Dependency Injection (CDI) 1.0 (JSR-299)
* JBoss Seam 2.2
Adding profiles to your configuration will resolve any dependencies on the
specified profiles.
New reports
Tattletale 1.1 also features new reports.
* Sealed information
* Signed information
* Unused Jar archives
* Circular Dependency
which should help you make your product/project distribution even better.
Other enhancements
A lot of small/large enhancements also went in the release.
* Ability to exclude directories from the scan
* Ability to filter results from the reports
* Apache Ant support
* Apache Maven support
These features will allow you to integrate Tattletale into your QA environment
and automate getting daily reports.
I want to thank the people that helped out with the release over the last
year, especially Torben Jaeger who did a lot of work :)
Best regards,
Jesper
[1] http://jboss.org/tattletale/
14 years, 1 month
Reminder: One Week Till Component Freeze
by Jason T. Greene
$SUBJECT
We still have 2 major integrations to perform (R3 & HornetQ), and only
one week to do them. Let me know as soon as you know we can't make that.
I would rather adjust the schedule sooner than later.
--
Jason T. Greene
JBoss, a division of Red Hat
14 years, 1 month
org.jboss.net.protocol handlers?
by Dimitris Andreadis
So with the switch to VFS3 are the URL protocol handlers in
common-core:org.jboss.net.protocol.* still in use?
E.g
org.jboss.net.protocol.file.Handler/FileURLConnection
Cheers
/D
14 years, 1 month
Regressions in making JPA optional
by Jason T. Greene
Hi Remy,
I'm not sure if you noticed this, but it looks like making the JPA
deployer optional causes some regressions:
http://fisheye.jboss.org/changelog/JBossAS/?cs=101922
Carlo and I were discussing this on #jboss-dev, and where thinking a
simple fix for this problem would be to switch it back to explicit and
have a "NotImplemented/NotAvailable/NotSupported/Noop" service that
would use the same name. That service would be used in your standalone
config.
Any thoughts on this?
--
Jason T. Greene
JBoss, a division of Red Hat
14 years, 1 month
