I have a use case where i am developing two projects, and project A
depends on project B.
What i want to do is a mvn clean compile under project A directory and
it will also compile project B and use it's classes as a dependency.
Sounds simple enough but i can't seem to be able to get this
I presume you have this use-case in your IDE, since Maven will NEVER use the
source-code of another project and always refers to the packaged version in
your repository.
What you need is a 'build-project', which contains both projects as modules.
Then Maven will recognize they need eachother
It's actually not about IDE integration. It's about continous integration.
I have my ci server run the goal clean cobertura:check every hour.
This allows me to know within the hour if anyone committed any code that
fails the tests. I only want to generate an artifact for my project once
a
You can't.
You can only see if a single projects runs with the latestest installed
version of another project. This means that you either have to change the
command you run in ci to 'clean install' or live with the fact that updates
are only deployed at night.
Is it a problem tyo run
Well, the main reason for me not wanting to install is related to a
behaviour in the cobertura plugin. Basically if i do install
cobertura:check my tests are run twice. If i just do cobertura:check
the tests are only run once. I reported this here
That doesn't run the check goal of the cobertura plugin. And if i add
the check goal to executions section in the cobertura plugin
configuration then i get my tests run twice.
Roland Asmann wrote:
And just running 'clean install'? Since it triggers cobertura as well,
shouldn't that be enough?
And just running 'clean install'? Since it triggers cobertura as well,
shouldn't that be enough?
On Friday 09 November 2007 13:37, Hugo Palma wrote:
Well, the main reason for me not wanting to install is related to a
behaviour in the cobertura plugin. Basically if i do install
Just read that in the plugin documentation. Too bad, should've been a little
bit better to configure imo.
That means you're stuck to running it twice I guess... If you trust your
developers enough and your ci is a pretty much isolated machine, you could
maybe run 2 maven-calls: 'mvn clean
Until this problem in cobertura is solved i think i will do that.
Thanks for you help..
Cheers
Roland Asmann wrote:
Just read that in the plugin documentation. Too bad, should've been a little
bit better to configure imo.
That means you're stuck to running it twice I guess... If you trust
