Re: Quality level attribute during version selection process?
Great thread - with a lot going on. A significant part of the discussion is about how to make sure one's overall Maven system is in a known state with known quality. That then brings up who establishes that quality and what is the governance around it and whether all that process will limit folks ability to work within the system. In an open source community I would not expect folks to jump into all that too willingly :-). But, in a corporate environment it is much more desirable and possibly required to govern how shared components reach certain levels of quality. In such an environment it is possible to establish quality states like ALPHA, BETA, RELEASE, etc., govern how components reach those levels of quality, and to then expect the version selection process to use those states. As I mentioned I modified the version selection process in our local Maven system to match a quality qualifier but I did have to leave the "standard" algorithm in place to support how Maven finds its own components (plugins). Ultimately the answer will probably to have the version selection process be plugable or otherwise extendable. Different software development lifecycles (open source vs. corporate for example) require different component selection processes depending on how they test and manage for quality. Wayne Fay wrote: > > This should give you a start... > http://www.nabble.com/Remove-auto-resolution-of-plugin-versions-from-Maven-2.1-tf3560617s177.html#a10144515 > > Wayne > > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> Sorry to be a NewB, I'm having trouble finding the @dev discussion. >> >> A couple weeks back I downloaded and modified the 2.0.6 source to do what >> I >> need. It was nothing too complicated but since it is core code and a >> fundamental shift in how folks expect version selection to work, I can >> understand the resistance to change in that area. >> >> >> Wayne Fay wrote: >> > >> > You'll need to read the thread on dev@ to see how people have >> > responded thus far. But based on the initial response, I just don't >> > see it happening. >> > >> > Admittedly, this issue hasn't had a terribly thorough discussion etc >> > so feel free to take that on if you are seriously interested. I just >> > think its going to be a seriously uphill battle to make this happen in >> > the forseeable future. >> > >> > Wayne >> > >> > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> >> >> So, what would it take to get this sort of thing in place? It's not >> such >> >> a >> >> futuristic need - some of the big budget SCM tools allow for the >> >> component >> >> query to include a quality level and indeed Ivy allows for this as >> well. >> >> Is >> >> the reasoning in the Maven community that this is not necessary or >> that >> >> it >> >> can be accomplished in other ways? >> >> Thanks >> >> >> >> >> >> Wayne Fay wrote: >> >> > >> >> > is certainly not currently available. And I doubt it will >> >> > be available at any time in the future. It was simply a suggestion >> >> > from a user on the dev@ list. >> >> > >> >> > This is like seeing a movie on Sci Fi channel about flying cars and >> >> > asking GM where you can buy one. ;-) >> >> > >> >> > Wayne >> >> > >> >> > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> >> >> >> >> I saw a post recently that referred to a attribute being >> >> used >> >> >> during plugin resolution. The purpose of the attribute was to make >> >> sure >> >> >> that only "released" or "beta", etc. versions were selected rather >> >> than >> >> >> alpha or lower level qualtiy. >> >> >> >> >> >> As far as I can tell Maven doesn't use a quality level for version >> >> >> selection. There are version number qualifiers but that's >> different >> >> than >> >> >> using something like a attribute in conjuction with >> >> , >> >> >> etc. >> >> >> >> >> >> In any case, having something like is really important >> (at >> >> >> least >> >> >> to my company). Ivy does this and in fact allows users to set up >
Re: Quality level attribute during version selection process?
Sorry to be a NewB, I'm having trouble finding the @dev discussion. A couple weeks back I downloaded and modified the 2.0.6 source to do what I need. It was nothing too complicated but since it is core code and a fundamental shift in how folks expect version selection to work, I can understand the resistance to change in that area. Wayne Fay wrote: > > You'll need to read the thread on dev@ to see how people have > responded thus far. But based on the initial response, I just don't > see it happening. > > Admittedly, this issue hasn't had a terribly thorough discussion etc > so feel free to take that on if you are seriously interested. I just > think its going to be a seriously uphill battle to make this happen in > the forseeable future. > > Wayne > > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> So, what would it take to get this sort of thing in place? It's not such >> a >> futuristic need - some of the big budget SCM tools allow for the >> component >> query to include a quality level and indeed Ivy allows for this as well. >> Is >> the reasoning in the Maven community that this is not necessary or that >> it >> can be accomplished in other ways? >> Thanks >> >> >> Wayne Fay wrote: >> > >> > is certainly not currently available. And I doubt it will >> > be available at any time in the future. It was simply a suggestion >> > from a user on the dev@ list. >> > >> > This is like seeing a movie on Sci Fi channel about flying cars and >> > asking GM where you can buy one. ;-) >> > >> > Wayne >> > >> > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> >> >> I saw a post recently that referred to a attribute being >> used >> >> during plugin resolution. The purpose of the attribute was to make >> sure >> >> that only "released" or "beta", etc. versions were selected rather >> than >> >> alpha or lower level qualtiy. >> >> >> >> As far as I can tell Maven doesn't use a quality level for version >> >> selection. There are version number qualifiers but that's different >> than >> >> using something like a attribute in conjuction with >> , >> >> etc. >> >> >> >> In any case, having something like is really important (at >> >> least >> >> to my company). Ivy does this and in fact allows users to set up >> their >> >> own >> >> set of ordered quality levels to choose from. >> >> >> >> So: am I missing something and Maven in fact does do quality level >> >> selection >> >> (I don't see it in the code). Or, is this something Maven can do in >> the >> >> future? >> >> >> >> Thanks >> >> -- >> >> View this message in context: >> >> >> http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10146036 >> >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> >> >> >> - >> >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> >> >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > >> >> -- >> View this message in context: >> http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10150722 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10153097 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Quality level attribute during version selection process?
So, what would it take to get this sort of thing in place? It's not such a futuristic need - some of the big budget SCM tools allow for the component query to include a quality level and indeed Ivy allows for this as well. Is the reasoning in the Maven community that this is not necessary or that it can be accomplished in other ways? Thanks Wayne Fay wrote: > > is certainly not currently available. And I doubt it will > be available at any time in the future. It was simply a suggestion > from a user on the dev@ list. > > This is like seeing a movie on Sci Fi channel about flying cars and > asking GM where you can buy one. ;-) > > Wayne > > On 4/23/07, gilclark <[EMAIL PROTECTED]> wrote: >> >> I saw a post recently that referred to a attribute being used >> during plugin resolution. The purpose of the attribute was to make sure >> that only "released" or "beta", etc. versions were selected rather than >> alpha or lower level qualtiy. >> >> As far as I can tell Maven doesn't use a quality level for version >> selection. There are version number qualifiers but that's different than >> using something like a attribute in conjuction with , >> etc. >> >> In any case, having something like is really important (at >> least >> to my company). Ivy does this and in fact allows users to set up their >> own >> set of ordered quality levels to choose from. >> >> So: am I missing something and Maven in fact does do quality level >> selection >> (I don't see it in the code). Or, is this something Maven can do in the >> future? >> >> Thanks >> -- >> View this message in context: >> http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10146036 >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10150722 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Quality level attribute during version selection process?
I saw a post recently that referred to a attribute being used during plugin resolution. The purpose of the attribute was to make sure that only "released" or "beta", etc. versions were selected rather than alpha or lower level qualtiy. As far as I can tell Maven doesn't use a quality level for version selection. There are version number qualifiers but that's different than using something like a attribute in conjuction with , etc. In any case, having something like is really important (at least to my company). Ivy does this and in fact allows users to set up their own set of ordered quality levels to choose from. So: am I missing something and Maven in fact does do quality level selection (I don't see it in the code). Or, is this something Maven can do in the future? Thanks -- View this message in context: http://www.nabble.com/Quality-level-attribute-during-version-selection-process--tf3633434s177.html#a10146036 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Trying to build Maven 2.0.x - used to create uber jar, now it doens't
Not sure if this is the right forum but I'll start here. A couple weeks back I was successfully building Maven 2.0.x. The last stage of the build is to run mvn assembly:assembly in the maven-core directory. The resultant zip, gz, etc. contained the uberjar called maven-2.0.x-uber.jar which goes in the lib directory. Unzip it somewhere - everything runs fine. About 4 days ago the build mysteriously stopped building the uber jar. I've tried this on two different machines with the same result - I have no idea what changed - nothing I did (on purpose). Any help appreciated. -- View this message in context: http://www.nabble.com/Trying-to-build-Maven-2.0.x---used-to-create-uber-jar%2C-now-it-doens%27t-tf3598598s177.html#a10051099 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
