Re: [weld-dev] Weld-int in AS question
Hey Kabir,
Some time ago we decided to move the weld-int stuff (whatever is
specific to JBAS) into JBAS itself, for making the integration between
the two a bit more straightforward.
So the stuff that is now inside JBAS is a copy of the former weld-int
project (with the poms modified to match JBAS). I made some changes to
JSF stuff and JNDI registration.
Following a comment made by Ales, the deployer-mc-int stuff stayed in
its old location (as it is not currently packaged inside the JBAS
distro), and is mainly untouched. Since it seems to depend on other
modules, it may make sense to extract the common stuff and make it a
dependency to both the JBAS weld-int and the extraneous mc-weld-int. For
now, I just made sure that the clone works, and perhaps this is a step
that is hard to complete before M4.
I think that you can use the deployer-mc-int as is for now, if you're
not affected by the current duplication issues. Or, let me know if I can
help working something out.
Marius
On 10-06-11 9:42 AM, Kabir Khan wrote:
I am about to revisit the MC/Weld integration for Ales's and my
talk at JUDCon.
The work was done under https://svn.jboss.org/repos/jbossas/projects/weld-int/trunk, more
specificially under
https://svn.jboss.org/repos/jbossas/projects/weld-int/trunk/deployer-mc-int.
Updating AS trunk now I see a new weld-int project with the following sub directories;
assembly/
deployer/
ejb/
pom.xml/
webtier/
In https://svn.jboss.org/repos/jbossas/projects/weld-int/trunk I see
assembly/
deployer/
deployer-mc-int/
ejb/
pom.xml/
webtier/
The https://svn.jboss.org/repos/jbossas/projects/weld-int/trunk/deployer-mc-int are
working, and the next step is to try this out in AS, but I am confused how the two
locations relate to each other and where my deployer-mc-int/ stuff should go?
Cheers,
Kabir
_______________________________________________
weld-dev mailing list
weld-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev