jbossas trunk/ejb3 broke
by Scott Stark
I copied over the ejb3 iiop integration code so if you update the
trunk/ejb3 contents your build will be broken. In the process of fixing it.
17 years, 12 months
Why is common-core dependent on jboss-common-logging-spi 2.0.5-SNAPSHOT?
by Scott Stark
Currently the common-core trunk depends on 2.0.5-SNAPSHOT of
jboss-common-logging-spi. This requires pulling down the current
jboss-common-logging-spi and building it. Are we trying to update the
group id of this to org.jboss from jboss?
Can't we just release jboss:jboss-common-logging-spi as
org:jboss:jboss-common-logging-spi with a new tagged release?
I'll have to release the 2.0.5.GA of jboss-common-logging-spi for the
2.0.5.GA release of jboss-common-core otherwise.
18 years
Delivery Failure
by Postmaster
---------------------------------------------------------------------------------
The message you sent to bosmulder.nl/ubosmu68 was rejected because it would exceed the quota for the mailbox.
The subject of the message follows:
Subject: Hermes
---------------------------------------------------------------------------------
18 years
Moving AS5 trunk away from snapshots
by Dimitris Andreadis
To test the effectiveness of the maven thirdparty build and to increase the stability of AS
trunk, we need to move away from snapshot versions and avoid introducing new ones, asap.
It's doesn't have to be the final version that will go in AS5 CR1, any intermediate tagged
release would do.
There are currently quite a few snapshots:
- ejb3
- security
- jbossws
- javaee-ee
- vfs
- metadata
We monitor component updates here:
http://jira.jboss.com/jira/browse/JBAS-5121
Another important on-going and potentially longer term effort is to keep creating
integration SPIs, wherever are missing, in order to remove any remaining cyclical dependencies.
Cheers
/Dimitris
18 years
maven artifact cleanup
by Heiko Braun
Currently there are redundant jbossws-spi artifacts in the maven
repository, which basically use different group-id's.
What I am wondering about is, how do we cleanup the mess?
According to the naming convention I need to rename current artifacts,
but how can I identify the components that depend on it?
Especially the ones that are tagged (as of released) versions?
/Heiko
18 years
mapped-name is required for context of deployment
by Thomas Diesler
Folks,
http://jira.jboss.org/jira/browse/JBAS-5359
FYI any webapp deployment that uses
@Resource
public WebServiceContext context;
currently fails with
14:36:47,407 ERROR [BaseModelMBean] Exception invoking method addChild
java.lang.RuntimeException: mapped-name is required for context of
deployment jaxws-binding.war
at
org.jboss.injection.ResourceHandler.loadXmlResourceEnvRefs(ResourceHandler.java:228)
at
org.jboss.injection.ResourceHandler.loadXml(ResourceHandler.java:268)
at
org.jboss.web.tomcat.service.TomcatInjectionContainer.processMetadata(TomcatInjectionContainer.java:348)
at
org.jboss.web.tomcat.service.WebCtxLoader.start(WebCtxLoader.java:158)
Is it really required to have a mapped-name?
cheers
-thomas
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thomas Diesler
Web Service Lead
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
18 years
