Test scope to avoid cyclic dependency

I have ProjectOuter which depends on ProjectCore. However, many of the tests of ProjectCore are placed in ProjectOuter. ProjectOuter has a large bunch of enterprise level initializations and dependencies, etc which is utilized by the BaseTestCase(present in ProjectOuter). Every test case then exten

Re: Selective repo purge after clean install

Thank you for the reply Wayne! I will try modifying the plugin for my use. I just wanted to ensure I wasn't re-inventing the wheel. Thanks, Zeba -- View this message in context: http://maven.40175.n5.nabble.com/Selective-repo-purge-after-clean-install-tp5603961p5606133.html Sent from the Maven -

Selective repo purge after clean install

I have a parent pom with a module that assembles from 3 other modules. ParentA ---| ModuleB ---| AssembledModuleC (depends on ModuleC1,ModuleC2,ModuleC3) ---| ModuleC1 ---| ModuleC2 ---| ModuleC3 ---| ModuleD (depends on ModuleC1) When I invoke clean install on ParentA from Jen

Re: maven-clean-plugin to clean up dependencies in assembly project

It looks like the default directory clean was responsible for removing all the jars. It works now, after adding this: true . . . . Thanks, Zeba -- View this message in context: http://maven.40175.n5.nabble.com/maven-clean-plugin-to-clean-up-dependencies-in-assembly-pr

Re: maven-clean-plugin to clean up dependencies in assembly project

Yeah, doesn't work :( Thanks, Zeba -- View this message in context: http://maven.40175.n5.nabble.com/maven-clean-plugin-to-clean-up-dependencies-in-assembly-project-tp5600724p5602388.html Sent from the Maven - Users mailing list archive at Nabble.com. ---

Re: maven-clean-plugin to clean up dependencies in assembly project

Actually, I'm able to delete the jars now. But the exclude is not working still :( My plugin configuration in pom.xml is: maven-clean-plugin 2.4.1 auto-clean install

maven-clean-plugin to clean up dependencies in assembly project

I have a maven project with a parent pom that builds the child modules. One of the child modules is an assembly project that simply assembles other child modules ParentA |---ModuleA |---AssembledModuleB |---ModuleB1 |---ModuleB2 |---ModuleC Here, ParentA only contains a p

RE: Assembly plugin with multiple XMLs - appending assembly ID

Awesome you are! Thank you, using different executions works just great. Regards, Zeba -- View this message in context: http://maven.40175.n5.nabble.com/Assembly-plugin-with-multiple-XMLs-appending-assembly-ID-tp5591772p5594575.html Sent from the Maven - Users mailing list archive at Nabble.com.

Assembly plugin with multiple XMLs - appending assembly ID

I'm using the assembly plugin to create two assemblies for a deliverable - one for the binary and one for sources DeliverableX --| ProjectA --| ProjectB So on invoking maven build of DeliverableX, projects A & B will be built and assembly plugin is used to create two artifacts DeliverableX-bin.ja

Re: Building multi-module project with cross-references

Thanks for the info & advice, Ron..Will keep in mind! Btw, using all of them as projects will not ensure the artifact structure to be maintained for deliverables - I need the deliverable to have the source contents of the other projects to be brought in .. Thanks, Zeba -- View this message in con

Re: Building multi-module project with cross-references

Thanks much for the pointer, Barrie! The assembly plugin looks to be exactly what I needed! Zeba -- View this message in context: http://maven.40175.n5.nabble.com/Building-multi-module-project-with-cross-references-tp437p596.html Sent from the Maven - Users mailing list archive at Nabble

Building multi-module project with cross-references

Hi, I am currently migrating my projects from my company's in-house build system based on ant, to maven. We have a concept of deliverable, where a deliverable may be a combination of projects. Two or more projects are basically merged, to create a deliverable. The projects may be part of more than