I am exploring a development scenario using M2 within an IDE and would
like some thoughts on it.

 

The use case is a follows:

 

Given a multi module build with 2 modules, A and B.   B has a declared
dependency on A.  My repository has a snapshot of A as well as a
corresponding source jar.

 

A developer with an empty workspace checks out project B from version
control.    He builds it (against the A snapshot from the repository),
he encounters an error.   Because he has used the eclipse plugin, and
configured his pom's accordingly, the source in project A is linked, and
he can step through and debug it.   

 

The developer finds an issue in project A which he would like to fix.
At this point I assume he would have to manually check out that project,
make the change, rebuild it, and then redeploy it with a new version
number (or just update the snapshot).

 

Is there not an easier way to address this?   Such as some sort of
mechanism which would attempt to check out project A from SCM if the SCM
information was defined in it's pom?

 

Does this make sense or sound theasible?

 

 

 

Ruel Loehr

JBoss QA

 

Reply via email to