"scott.stark(a)jboss.org" wrote : org.jboss:jboss-parent is too general for that.
Yes, this is what I'm getting at.
"scott.stark(a)jboss.org" wrote : We still need to get a handle on whether there
is an acceptable version range policy (only minor version, custom jboss policy, etc.).
Though related, and will affect the values of a shared parent, I don't think this is a
requirement to move forward in centralizing the dependencies.
"scott.stark(a)jboss.org" wrote : I would also suggest that snapshot version
cannot be introduced into the common parent. It has to be done in the project.
|
What is the reasoning behind this? If snapshots are done only at the project level,
then:
1) AS increments to snapshot of project A
2) EJB3 remains on release 1 of project A
3) AS requires release 2 of project A, updates shared parent
4) EJB3 implicitly gets release 2 now, and has version conflict because it hasn't been
seeing snapshot changes all along. Possible compile and runtime problems.
S,
ALR
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4136458#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...