Vamsi,
I'm not sure if this is correct but I think if you want a module (jar)
level dependency that is added to the assembly repo but not included in
the config plan you can do the folllowing:
- add a dependency entry in geronimo-dependency.xml under that module's
src/main/resources/META-INF/ (see modules/tomcat for an example). IIUC
this will result in the dependency being inserted into the repo (if it
is not already present) at the time any configuration which includes the
module is deployed.
Joe
Vamsavardhana Reddy wrote:
Hi,
I want to know how the following can be achieved in branches\1.1 and
trunk builds.
When I build a configuration, I want a certain dependency to be copied
to repository at assembly time. I do not want the build to add this
dependency directly to the configuration that is built. It is better
explained with the following example:
When I build a configuration (say configs\myapp) which is for an EAR
application, I want to add a dependency "foo/bar/1.0/jar". When I
include this configuration in an assembly, I want "foo/bar/1.0/jar" to
be copied to the repository. I do not want the build process
automatically adding a dependency on "foo/bar/1.0/jar" in my application
plan since I want to add this dependency explicitly at a certain module
level.
In branches\1.1, adding true
under the tag in the dependency declared in
configs\myapp\project.xml is making the jar to be copied to repo at
assembly time. But then the build is adding a dependency at application
level in the application plan. Is there a property that I can enable
under dependency properties in project.xml that will prevent
"foo/bar/1.0/jar" from being added to my application plan?
I want to achieve the same in the trunk too.
Thanks,
vamsi
