This content has been marked as final.
Show 2 replies
-
1. Re: Requirements - Top level build - components + potential
adrian.brock May 17, 2005 2:51 PM (in response to adrian.brock)The main issue as to whether this applies to the build
is whether such a notion can be understood at the ant/repository level.
e.g. can I go from<project> <component name="mdb"/> </project>
and understand that the current jms1.1 implementation is jbossmq by default
or if you want to override it<project> <component name="mdb"/> <component name="jbossmessaging"/> </project>
This also has issues where the implementation is external, e.g. the jms1.1
implementation is actually provided by an external jms. -
2. Re: Requirements - Top level build - components + potential
ryan.campbell May 24, 2005 5:42 PM (in response to adrian.brock)"adrian@jboss.org" wrote:
The main issue as to whether this applies to the build is whether such a notion can be understood at the ant/repository level.
Perhaps extension points could use the same repository structure as components, but have a different descriptor:
/jms/1.1/extension-info.xml:<project> <extension-point name="jms" version="1.1"> <implementation default="true" name="jbossmq" version="4.0.2"/> <implementation name="jbossmq" version="4.0.1"/> <implementation name="jbossmessaging" version="4.0.2"/> </extension-point> </project>