Re: We may need to rethink unversioned dependencies among server plans...

2006-04-20 Thread Matt Hogstrom
I agree with Jencks that dates are too unpredictable. If there are patches as you described below (1.1.1-patch-aaron-5 or 1.1.1-2345-fix-by-dain) those are not welformed so the results are undefined. Aaron Mulder wrote: My problem with the "version with well-explained scheme" is that it basic

Re: We may need to rethink unversioned dependencies among server plans...

2006-04-20 Thread Aaron Mulder
My problem with the "version with well-explained scheme" is that it basically means there can only be one source of updates. I mean, it's probably OK if you figure you won't be able to apply a WAS CE patch to Geronimo or vice versa. Are we sure we're not going to want to have test patches and stu

Re: We may need to rethink unversioned dependencies among server plans...

2006-04-20 Thread David Jencks
On Apr 20, 2006, at 4:25 AM, Aaron Mulder wrote: First, can you rev the version of the plugin so we can eliminate that as a possible source of the problem? will do Second, what happens when we go to upgrade j2ee-server from 1.1(.0) to 1.1.1 at runtime? During that redeploy operation, both

Re: We may need to rethink unversioned dependencies among server plans...

2006-04-20 Thread Aaron Mulder
First, can you rev the version of the plugin so we can eliminate that as a possible source of the problem? Second, what happens when we go to upgrade j2ee-server from 1.1(.0) to 1.1.1 at runtime? During that redeploy operation, both 1.1.0 and 1.1.1 will be present in the config store, and the con

Re: We may need to rethink unversioned dependencies among server plans...

2006-04-19 Thread David Jencks
On Apr 19, 2006, at 6:27 PM, Aaron Mulder wrote: So I'm having a build problem. The root cause appears to be that my local Maven repo has both 1.1-SNAPSHOT and 1.2-SNAPSHOT artifacts. One of the server artifacts (say, j2ee-system) has a dependency on another (say, rmi-naming), and that depend

Re: We may need to rethink unversioned dependencies among server plans...

2006-04-19 Thread Matt Hogstrom
This is behaving as designed isn't it? I would expect the highest level version to be selected in the absence of a restriction (another dependency indicated that it required 1.1-SNAPSHOT) or a specific dependency (some dependency indicated it needed naming-1.1-SNAPSHOT). Does this sound right?

We may need to rethink unversioned dependencies among server plans...

2006-04-19 Thread Aaron Mulder
So I'm having a build problem. The root cause appears to be that my local Maven repo has both 1.1-SNAPSHOT and 1.2-SNAPSHOT artifacts. One of the server artifacts (say, j2ee-system) has a dependency on another (say, rmi-naming), and that dependency has no version. So when the packaging plugin pa