-
1. Re: Maven Dependencies Real Problem
ropalka Nov 12, 2008 7:14 AM (in response to ropalka)We're reusing deployment macros because of:
* easily integration
* native stack integration changes gets to the AS without need for review and patching the different build process (if such would be introduced) -
2. Re: Maven Dependencies Real Problem
ropalka Nov 13, 2008 9:07 AM (in response to ropalka)To don't it be such an easy problem many of JBossWS deployed jars are overwritten by JBossAS build distribution process. Hence we really have no control over the files that will get to the AS once we're integrated to the AS :(
-
3. Re: Maven Dependencies Real Problem
starksm64 Nov 13, 2008 9:18 AM (in response to ropalka)The first thing I would suggest is that the webservices integration layer not be trying to do the install of its dependencies. If it does not fully contain the dependency, the dependency has to be installed by the layer that is bringing webservices into itself.
If there are dependencies that do need to be installed into the webservices deployment, the wildcard patterns need to be replaced with integration target specific properties files that can be set to the correct location of each dependency reference by the project that is integrating webservices. -
4. Re: Maven Dependencies Real Problem
ropalka Nov 13, 2008 9:31 AM (in response to ropalka)Thanks for opinions Scott.
From my understanding of the problem reusing the deployment macro isn't nice idea because it's magic and we don't have the control over the integration process with the AS now. I'm thinking about removing the JBossWS deployment macro call from AS build process and reuse the JBossAS build distribution logic instead. -
5. Re: Maven Dependencies Real Problem
starksm64 Nov 13, 2008 9:37 AM (in response to ropalka)Yes, that is the only thing I can see working in general. You need to declare your dependencies and whatever project is integrating the webservices deployments has to install these.
-
6. Re: Maven Dependencies Real Problem
ropalka Nov 13, 2008 10:40 AM (in response to ropalka)Yes, we decided to go this way because it's the least error prone approach for our integration.
-
7. Re: Maven Dependencies Real Problem
ropalka Nov 13, 2008 10:48 AM (in response to ropalka)Cross reference: JBAS-6195