|
View:
New views
20 Messages
—
Rating Filter:
Alert me
|
| < Prev | 1 - 2 | Next > |
|
|
Seam 2.1.2 releaseIt's out. I'm still waiting on IT to updated the latest/latest-2/
latest-2.1 docs links, but otherwise the release process should be done. _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseGreat! :)
On Mon, Jun 8, 2009 at 10:17 AM, Norman Richards<orb@...> wrote: > It's out. I'm still waiting on IT to updated the latest/latest-2/latest-2.1 > docs links, but otherwise the release process should be > done._______________________________________________ > seam-dev mailing list > seam-dev@... > https://lists.jboss.org/mailman/listinfo/seam-dev > -- Gavin King gavin.king@... http://in.relation.to/Bloggers/Gavin http://hibernate.org http://seamframework.org _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseYes, really good timing on this. I told a lot of people to look for the release early this week. Hopefully we'll see some good numbers.
-Dan On Mon, Jun 8, 2009 at 10:48 AM, Gavin King <gavin.king@...> wrote: Great! :) -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention. _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 release----- "Norman Richards" <orb@...> wrote:
> It's out. I'm still waiting on IT to updated the latest/latest-2/ > latest-2.1 docs links, but otherwise the release process should be > done. There seems to have been a small glitch with the naming of the 2.1.2 release in maven: http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ I would expect '2.1.2.GA' rather than '2.1.2'? Congrats on the release! cheers, asgeir _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseNope, JBoss has changed their versioning guidelines, and no longer
applies .GA to final releases... Going forward, there will be no more GA suffix (but we still use .CRX, .BETAX etc.) On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: > ----- "Norman Richards" <orb@...> wrote: >> It's out. I'm still waiting on IT to updated the latest/latest-2/ >> latest-2.1 docs links, but otherwise the release process should be >> done. > > There seems to have been a small glitch with the naming of the 2.1.2 > release in maven: > http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ > > I would expect '2.1.2.GA' rather than '2.1.2'? > > Congrats on the release! > > cheers, > asgeir > _______________________________________________ > seam-dev mailing list > seam-dev@... > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseI thought this renaming did not apply for maven bundles as the maven
resolution mechanism was retarded. On Jun 9, 2009, at 08:43, Pete Muir wrote: > Nope, JBoss has changed their versioning guidelines, and no longer > applies .GA to final releases... > > Going forward, there will be no more GA suffix (but we still > use .CRX, .BETAX etc.) > > On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: > >> ----- "Norman Richards" <orb@...> wrote: >>> It's out. I'm still waiting on IT to updated the latest/latest-2/ >>> latest-2.1 docs links, but otherwise the release process should be >>> done. >> >> There seems to have been a small glitch with the naming of the >> 2.1.2 release in maven: >> http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ >> >> I would expect '2.1.2.GA' rather than '2.1.2'? >> >> Congrats on the release! >> >> cheers, >> asgeir >> _______________________________________________ >> seam-dev mailing list >> seam-dev@... >> https://lists.jboss.org/mailman/listinfo/seam-dev > > _______________________________________________ > seam-dev mailing list > seam-dev@... > https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseWell to be maven compatible we should switch to -CRX, -BETAX etc.
Actually, I think it was OSGi, not maven that has the problem you describe. Anyway, we always use explicit versions (and recommend this to people using our poms) so it should be ok... Do people think we should just switch to the maven standard? On 9 Jun 2009, at 15:12, Emmanuel Bernard wrote: > I thought this renaming did not apply for maven bundles as the maven > resolution mechanism was retarded. > > On Jun 9, 2009, at 08:43, Pete Muir wrote: > >> Nope, JBoss has changed their versioning guidelines, and no longer >> applies .GA to final releases... >> >> Going forward, there will be no more GA suffix (but we still >> use .CRX, .BETAX etc.) >> >> On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: >> >>> ----- "Norman Richards" <orb@...> wrote: >>>> It's out. I'm still waiting on IT to updated the latest/latest-2/ >>>> latest-2.1 docs links, but otherwise the release process should be >>>> done. >>> >>> There seems to have been a small glitch with the naming of the >>> 2.1.2 release in maven: >>> http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ >>> >>> I would expect '2.1.2.GA' rather than '2.1.2'? >>> >>> Congrats on the release! >>> >>> cheers, >>> asgeir >>> _______________________________________________ >>> seam-dev mailing list >>> seam-dev@... >>> https://lists.jboss.org/mailman/listinfo/seam-dev >> >> _______________________________________________ >> seam-dev mailing list >> seam-dev@... >> https://lists.jboss.org/mailman/listinfo/seam-dev > _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseosgi standard is the one that actually is consistent.
Maven 3 will be using osgi. Really don't think we were told to remove GA from the technical names. /max Pete Muir wrote: > Well to be maven compatible we should switch to -CRX, -BETAX etc. > > Actually, I think it was OSGi, not maven that has the problem you > describe. Anyway, we always use explicit versions (and recommend this > to people using our poms) so it should be ok... > > Do people think we should just switch to the maven standard? > > On 9 Jun 2009, at 15:12, Emmanuel Bernard wrote: > >> I thought this renaming did not apply for maven bundles as the maven >> resolution mechanism was retarded. >> >> On Jun 9, 2009, at 08:43, Pete Muir wrote: >> >>> Nope, JBoss has changed their versioning guidelines, and no longer >>> applies .GA to final releases... >>> >>> Going forward, there will be no more GA suffix (but we still use >>> .CRX, .BETAX etc.) >>> >>> On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: >>> >>>> ----- "Norman Richards" <orb@...> wrote: >>>>> It's out. I'm still waiting on IT to updated the latest/latest-2/ >>>>> latest-2.1 docs links, but otherwise the release process should be >>>>> done. >>>> >>>> There seems to have been a small glitch with the naming of the >>>> 2.1.2 release in maven: >>>> http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ >>>> >>>> I would expect '2.1.2.GA' rather than '2.1.2'? >>>> >>>> Congrats on the release! >>>> >>>> cheers, >>>> asgeir >>>> _______________________________________________ >>>> seam-dev mailing list >>>> seam-dev@... >>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>> >>> _______________________________________________ >>> seam-dev mailing list >>> seam-dev@... >>> https://lists.jboss.org/mailman/listinfo/seam-dev > > _______________________________________________ > seam-dev mailing list > seam-dev@... > https://lists.jboss.org/mailman/listinfo/seam-dev seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 release:-)
If someone would update the JBossVersioningGuideline wiki page, we'll be sure to follow it! On 9 Jun 2009, at 16:38, Max Rydahl Andersen wrote: > osgi standard is the one that actually is consistent. > > Maven 3 will be using osgi. > > Really don't think we were told to remove GA from the technical names. > > /max > > Pete Muir wrote: >> Well to be maven compatible we should switch to -CRX, -BETAX etc. >> >> Actually, I think it was OSGi, not maven that has the problem you >> describe. Anyway, we always use explicit versions (and recommend >> this to people using our poms) so it should be ok... >> >> Do people think we should just switch to the maven standard? >> >> On 9 Jun 2009, at 15:12, Emmanuel Bernard wrote: >> >>> I thought this renaming did not apply for maven bundles as the >>> maven resolution mechanism was retarded. >>> >>> On Jun 9, 2009, at 08:43, Pete Muir wrote: >>> >>>> Nope, JBoss has changed their versioning guidelines, and no >>>> longer applies .GA to final releases... >>>> >>>> Going forward, there will be no more GA suffix (but we still >>>> use .CRX, .BETAX etc.) >>>> >>>> On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: >>>> >>>>> ----- "Norman Richards" <orb@...> wrote: >>>>>> It's out. I'm still waiting on IT to updated the latest/ >>>>>> latest-2/ >>>>>> latest-2.1 docs links, but otherwise the release process should >>>>>> be >>>>>> done. >>>>> >>>>> There seems to have been a small glitch with the naming of the >>>>> 2.1.2 release in maven: >>>>> http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ >>>>> >>>>> I would expect '2.1.2.GA' rather than '2.1.2'? >>>>> >>>>> Congrats on the release! >>>>> >>>>> cheers, >>>>> asgeir >>>>> _______________________________________________ >>>>> seam-dev mailing list >>>>> seam-dev@... >>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>> >>>> _______________________________________________ >>>> seam-dev mailing list >>>> seam-dev@... >>>> https://lists.jboss.org/mailman/listinfo/seam-dev >> >> _______________________________________________ >> seam-dev mailing list >> seam-dev@... >> https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseOn Tue, Jun 9, 2009 at 8:43 AM, Pete Muir <pmuir@...> wrote: :-) Is this the page to which you are referring? http://www.jboss.org/community/wiki/JBossProductVersioning -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention. _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseThe versioning guidelines is osgi afaik.
/max Pete Muir wrote: > :-) > > If someone would update the JBossVersioningGuideline wiki page, we'll > be sure to follow it! > > On 9 Jun 2009, at 16:38, Max Rydahl Andersen wrote: > >> osgi standard is the one that actually is consistent. >> >> Maven 3 will be using osgi. >> >> Really don't think we were told to remove GA from the technical names. >> >> /max >> >> Pete Muir wrote: >>> Well to be maven compatible we should switch to -CRX, -BETAX etc. >>> >>> Actually, I think it was OSGi, not maven that has the problem you >>> describe. Anyway, we always use explicit versions (and recommend >>> this to people using our poms) so it should be ok... >>> >>> Do people think we should just switch to the maven standard? >>> >>> On 9 Jun 2009, at 15:12, Emmanuel Bernard wrote: >>> >>>> I thought this renaming did not apply for maven bundles as the >>>> maven resolution mechanism was retarded. >>>> >>>> On Jun 9, 2009, at 08:43, Pete Muir wrote: >>>> >>>>> Nope, JBoss has changed their versioning guidelines, and no longer >>>>> applies .GA to final releases... >>>>> >>>>> Going forward, there will be no more GA suffix (but we still use >>>>> .CRX, .BETAX etc.) >>>>> >>>>> On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: >>>>> >>>>>> ----- "Norman Richards" <orb@...> wrote: >>>>>>> It's out. I'm still waiting on IT to updated the latest/latest-2/ >>>>>>> latest-2.1 docs links, but otherwise the release process should be >>>>>>> done. >>>>>> >>>>>> There seems to have been a small glitch with the naming of the >>>>>> 2.1.2 release in maven: >>>>>> http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ >>>>>> >>>>>> I would expect '2.1.2.GA' rather than '2.1.2'? >>>>>> >>>>>> Congrats on the release! >>>>>> >>>>>> cheers, >>>>>> asgeir >>>>>> _______________________________________________ >>>>>> seam-dev mailing list >>>>>> seam-dev@... >>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>> >>>>> _______________________________________________ >>>>> seam-dev mailing list >>>>> seam-dev@... >>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>> >>> _______________________________________________ >>> seam-dev mailing list >>> seam-dev@... >>> https://lists.jboss.org/mailman/listinfo/seam-dev seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseRight, but they don't reflect that we were asked to drop the GA
qualifier. So, should we add it back in? On 9 Jun 2009, at 23:17, Max Rydahl Andersen wrote: > The versioning guidelines is osgi afaik. > > /max > > Pete Muir wrote: >> :-) >> >> If someone would update the JBossVersioningGuideline wiki page, >> we'll be sure to follow it! >> >> On 9 Jun 2009, at 16:38, Max Rydahl Andersen wrote: >> >>> osgi standard is the one that actually is consistent. >>> >>> Maven 3 will be using osgi. >>> >>> Really don't think we were told to remove GA from the technical >>> names. >>> >>> /max >>> >>> Pete Muir wrote: >>>> Well to be maven compatible we should switch to -CRX, -BETAX etc. >>>> >>>> Actually, I think it was OSGi, not maven that has the problem you >>>> describe. Anyway, we always use explicit versions (and recommend >>>> this to people using our poms) so it should be ok... >>>> >>>> Do people think we should just switch to the maven standard? >>>> >>>> On 9 Jun 2009, at 15:12, Emmanuel Bernard wrote: >>>> >>>>> I thought this renaming did not apply for maven bundles as the >>>>> maven resolution mechanism was retarded. >>>>> >>>>> On Jun 9, 2009, at 08:43, Pete Muir wrote: >>>>> >>>>>> Nope, JBoss has changed their versioning guidelines, and no >>>>>> longer applies .GA to final releases... >>>>>> >>>>>> Going forward, there will be no more GA suffix (but we still >>>>>> use .CRX, .BETAX etc.) >>>>>> >>>>>> On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: >>>>>> >>>>>>> ----- "Norman Richards" <orb@...> wrote: >>>>>>>> It's out. I'm still waiting on IT to updated the latest/ >>>>>>>> latest-2/ >>>>>>>> latest-2.1 docs links, but otherwise the release process >>>>>>>> should be >>>>>>>> done. >>>>>>> >>>>>>> There seems to have been a small glitch with the naming of the >>>>>>> 2.1.2 release in maven: >>>>>>> http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ >>>>>>> >>>>>>> I would expect '2.1.2.GA' rather than '2.1.2'? >>>>>>> >>>>>>> Congrats on the release! >>>>>>> >>>>>>> cheers, >>>>>>> asgeir >>>>>>> _______________________________________________ >>>>>>> seam-dev mailing list >>>>>>> seam-dev@... >>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>>> >>>>>> _______________________________________________ >>>>>> seam-dev mailing list >>>>>> seam-dev@... >>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>> >>>> _______________________________________________ >>>> seam-dev mailing list >>>> seam-dev@... >>>> https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseSo apparently, I misremembered the outcome of this discussion (which
was that not having a GA qualifier breaks all sorts of stuff), and we should go back to numbering them with the GA qualifier. Max, will it break your stuff with this no-qualifier release in there? Do we have to redo the release? On 10 Jun 2009, at 11:48, Pete Muir wrote: > Right, but they don't reflect that we were asked to drop the GA > qualifier. So, should we add it back in? > > On 9 Jun 2009, at 23:17, Max Rydahl Andersen wrote: > >> The versioning guidelines is osgi afaik. >> >> /max >> >> Pete Muir wrote: >>> :-) >>> >>> If someone would update the JBossVersioningGuideline wiki page, >>> we'll be sure to follow it! >>> >>> On 9 Jun 2009, at 16:38, Max Rydahl Andersen wrote: >>> >>>> osgi standard is the one that actually is consistent. >>>> >>>> Maven 3 will be using osgi. >>>> >>>> Really don't think we were told to remove GA from the technical >>>> names. >>>> >>>> /max >>>> >>>> Pete Muir wrote: >>>>> Well to be maven compatible we should switch to -CRX, -BETAX etc. >>>>> >>>>> Actually, I think it was OSGi, not maven that has the problem >>>>> you describe. Anyway, we always use explicit versions (and >>>>> recommend this to people using our poms) so it should be ok... >>>>> >>>>> Do people think we should just switch to the maven standard? >>>>> >>>>> On 9 Jun 2009, at 15:12, Emmanuel Bernard wrote: >>>>> >>>>>> I thought this renaming did not apply for maven bundles as the >>>>>> maven resolution mechanism was retarded. >>>>>> >>>>>> On Jun 9, 2009, at 08:43, Pete Muir wrote: >>>>>> >>>>>>> Nope, JBoss has changed their versioning guidelines, and no >>>>>>> longer applies .GA to final releases... >>>>>>> >>>>>>> Going forward, there will be no more GA suffix (but we still >>>>>>> use .CRX, .BETAX etc.) >>>>>>> >>>>>>> On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: >>>>>>> >>>>>>>> ----- "Norman Richards" <orb@...> wrote: >>>>>>>>> It's out. I'm still waiting on IT to updated the latest/ >>>>>>>>> latest-2/ >>>>>>>>> latest-2.1 docs links, but otherwise the release process >>>>>>>>> should be >>>>>>>>> done. >>>>>>>> >>>>>>>> There seems to have been a small glitch with the naming of >>>>>>>> the 2.1.2 release in maven: >>>>>>>> http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ >>>>>>>> >>>>>>>> I would expect '2.1.2.GA' rather than '2.1.2'? >>>>>>>> >>>>>>>> Congrats on the release! >>>>>>>> >>>>>>>> cheers, >>>>>>>> asgeir >>>>>>>> _______________________________________________ >>>>>>>> seam-dev mailing list >>>>>>>> seam-dev@... >>>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>>>> >>>>>>> _______________________________________________ >>>>>>> seam-dev mailing list >>>>>>> seam-dev@... >>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>> >>>>> _______________________________________________ >>>>> seam-dev mailing list >>>>> seam-dev@... >>>>> https://lists.jboss.org/mailman/listinfo/seam-dev > _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releasePete Muir wrote: > So apparently, I misremembered the outcome of this discussion (which > was that not having a GA qualifier breaks all sorts of stuff), and we > should go back to numbering them with the GA qualifier. > > Max, will it break your stuff with this no-qualifier release in there? > Do we have to redo the release? I dont have it downloaded yet, but just try and add it as a runtime in JBossTools if you can do that it works...if not something gotta change ;) But more importantly, maven repo needs it doesn't it ? -max > > On 10 Jun 2009, at 11:48, Pete Muir wrote: > >> Right, but they don't reflect that we were asked to drop the GA >> qualifier. So, should we add it back in? >> >> On 9 Jun 2009, at 23:17, Max Rydahl Andersen wrote: >> >>> The versioning guidelines is osgi afaik. >>> >>> /max >>> >>> Pete Muir wrote: >>>> :-) >>>> >>>> If someone would update the JBossVersioningGuideline wiki page, >>>> we'll be sure to follow it! >>>> >>>> On 9 Jun 2009, at 16:38, Max Rydahl Andersen wrote: >>>> >>>>> osgi standard is the one that actually is consistent. >>>>> >>>>> Maven 3 will be using osgi. >>>>> >>>>> Really don't think we were told to remove GA from the technical >>>>> names. >>>>> >>>>> /max >>>>> >>>>> Pete Muir wrote: >>>>>> Well to be maven compatible we should switch to -CRX, -BETAX etc. >>>>>> >>>>>> Actually, I think it was OSGi, not maven that has the problem you >>>>>> describe. Anyway, we always use explicit versions (and recommend >>>>>> this to people using our poms) so it should be ok... >>>>>> >>>>>> Do people think we should just switch to the maven standard? >>>>>> >>>>>> On 9 Jun 2009, at 15:12, Emmanuel Bernard wrote: >>>>>> >>>>>>> I thought this renaming did not apply for maven bundles as the >>>>>>> maven resolution mechanism was retarded. >>>>>>> >>>>>>> On Jun 9, 2009, at 08:43, Pete Muir wrote: >>>>>>> >>>>>>>> Nope, JBoss has changed their versioning guidelines, and no >>>>>>>> longer applies .GA to final releases... >>>>>>>> >>>>>>>> Going forward, there will be no more GA suffix (but we still >>>>>>>> use .CRX, .BETAX etc.) >>>>>>>> >>>>>>>> On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: >>>>>>>> >>>>>>>>> ----- "Norman Richards" <orb@...> wrote: >>>>>>>>>> It's out. I'm still waiting on IT to updated the >>>>>>>>>> latest/latest-2/ >>>>>>>>>> latest-2.1 docs links, but otherwise the release process >>>>>>>>>> should be >>>>>>>>>> done. >>>>>>>>> >>>>>>>>> There seems to have been a small glitch with the naming of the >>>>>>>>> 2.1.2 release in maven: >>>>>>>>> http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ >>>>>>>>> >>>>>>>>> I would expect '2.1.2.GA' rather than '2.1.2'? >>>>>>>>> >>>>>>>>> Congrats on the release! >>>>>>>>> >>>>>>>>> cheers, >>>>>>>>> asgeir >>>>>>>>> _______________________________________________ >>>>>>>>> seam-dev mailing list >>>>>>>>> seam-dev@... >>>>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> seam-dev mailing list >>>>>>>> seam-dev@... >>>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>>> >>>>>> _______________________________________________ >>>>>> seam-dev mailing list >>>>>> seam-dev@... >>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseOn Wed, Jun 10, 2009 at 9:43 AM, Max Rydahl Andersen <max.andersen@...> wrote:
My concern here is that we really didn't give the community any warning. Granted, the idea of the community release is to test out these things, but still, I think we should either go with a dual-naming release (so have both) or we use .GA and announce that 2.2.0 will be w/o the .GA. It really isn't going to break Maven 2. If anything, the .GA was breaking Maven 2 conventions because most projects just have a numeric version. But going back to my first point, there could be a lot of scripts out there that are appending .GA to a version number loaded from a property because they assume that JBoss adds this extension when doing a final release. -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention. _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseOn 10 Jun 2009, at 14:43, Max Rydahl Andersen wrote: > > > Pete Muir wrote: >> So apparently, I misremembered the outcome of this discussion >> (which was that not having a GA qualifier breaks all sorts of >> stuff), and we should go back to numbering them with the GA >> qualifier. >> >> Max, will it break your stuff with this no-qualifier release in >> there? Do we have to redo the release? > I dont have it downloaded yet, but just try and add it as a runtime > in JBossTools if you can do that it works...if not something gotta > change ;) That works :-) > > But more importantly, maven repo needs it doesn't it ? Assuming version ranges aren't used, then it's fine. > > > -max > >> >> On 10 Jun 2009, at 11:48, Pete Muir wrote: >> >>> Right, but they don't reflect that we were asked to drop the GA >>> qualifier. So, should we add it back in? >>> >>> On 9 Jun 2009, at 23:17, Max Rydahl Andersen wrote: >>> >>>> The versioning guidelines is osgi afaik. >>>> >>>> /max >>>> >>>> Pete Muir wrote: >>>>> :-) >>>>> >>>>> If someone would update the JBossVersioningGuideline wiki page, >>>>> we'll be sure to follow it! >>>>> >>>>> On 9 Jun 2009, at 16:38, Max Rydahl Andersen wrote: >>>>> >>>>>> osgi standard is the one that actually is consistent. >>>>>> >>>>>> Maven 3 will be using osgi. >>>>>> >>>>>> Really don't think we were told to remove GA from the technical >>>>>> names. >>>>>> >>>>>> /max >>>>>> >>>>>> Pete Muir wrote: >>>>>>> Well to be maven compatible we should switch to -CRX, -BETAX >>>>>>> etc. >>>>>>> >>>>>>> Actually, I think it was OSGi, not maven that has the problem >>>>>>> you describe. Anyway, we always use explicit versions (and >>>>>>> recommend this to people using our poms) so it should be ok... >>>>>>> >>>>>>> Do people think we should just switch to the maven standard? >>>>>>> >>>>>>> On 9 Jun 2009, at 15:12, Emmanuel Bernard wrote: >>>>>>> >>>>>>>> I thought this renaming did not apply for maven bundles as >>>>>>>> the maven resolution mechanism was retarded. >>>>>>>> >>>>>>>> On Jun 9, 2009, at 08:43, Pete Muir wrote: >>>>>>>> >>>>>>>>> Nope, JBoss has changed their versioning guidelines, and no >>>>>>>>> longer applies .GA to final releases... >>>>>>>>> >>>>>>>>> Going forward, there will be no more GA suffix (but we still >>>>>>>>> use .CRX, .BETAX etc.) >>>>>>>>> >>>>>>>>> On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: >>>>>>>>> >>>>>>>>>> ----- "Norman Richards" <orb@...> wrote: >>>>>>>>>>> It's out. I'm still waiting on IT to updated the latest/ >>>>>>>>>>> latest-2/ >>>>>>>>>>> latest-2.1 docs links, but otherwise the release process >>>>>>>>>>> should be >>>>>>>>>>> done. >>>>>>>>>> >>>>>>>>>> There seems to have been a small glitch with the naming of >>>>>>>>>> the 2.1.2 release in maven: >>>>>>>>>> http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ >>>>>>>>>> >>>>>>>>>> I would expect '2.1.2.GA' rather than '2.1.2'? >>>>>>>>>> >>>>>>>>>> Congrats on the release! >>>>>>>>>> >>>>>>>>>> cheers, >>>>>>>>>> asgeir >>>>>>>>>> _______________________________________________ >>>>>>>>>> seam-dev mailing list >>>>>>>>>> seam-dev@... >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> seam-dev mailing list >>>>>>>>> seam-dev@... >>>>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>>>> >>>>>>> _______________________________________________ >>>>>>> seam-dev mailing list >>>>>>> seam-dev@... >>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 release> Assuming version ranges aren't used, then it's fine. version ranges are very useful and i bet some is using it with seam...so I would say that it should be fixed. /max > >> -max >> >>> On 10 Jun 2009, at 11:48, Pete Muir wrote: >>> >>>> Right, but they don't reflect that we were asked to drop the GA >>>> qualifier. So, should we add it back in? >>>> >>>> On 9 Jun 2009, at 23:17, Max Rydahl Andersen wrote: >>>> >>>>> The versioning guidelines is osgi afaik. >>>>> >>>>> /max >>>>> >>>>> Pete Muir wrote: >>>>>> :-) >>>>>> >>>>>> If someone would update the JBossVersioningGuideline wiki page, >>>>>> we'll be sure to follow it! >>>>>> >>>>>> On 9 Jun 2009, at 16:38, Max Rydahl Andersen wrote: >>>>>> >>>>>>> osgi standard is the one that actually is consistent. >>>>>>> >>>>>>> Maven 3 will be using osgi. >>>>>>> >>>>>>> Really don't think we were told to remove GA from the technical >>>>>>> names. >>>>>>> >>>>>>> /max >>>>>>> >>>>>>> Pete Muir wrote: >>>>>>>> Well to be maven compatible we should switch to -CRX, -BETAX etc. >>>>>>>> >>>>>>>> Actually, I think it was OSGi, not maven that has the problem >>>>>>>> you describe. Anyway, we always use explicit versions (and >>>>>>>> recommend this to people using our poms) so it should be ok... >>>>>>>> >>>>>>>> Do people think we should just switch to the maven standard? >>>>>>>> >>>>>>>> On 9 Jun 2009, at 15:12, Emmanuel Bernard wrote: >>>>>>>> >>>>>>>>> I thought this renaming did not apply for maven bundles as the >>>>>>>>> maven resolution mechanism was retarded. >>>>>>>>> >>>>>>>>> On Jun 9, 2009, at 08:43, Pete Muir wrote: >>>>>>>>> >>>>>>>>>> Nope, JBoss has changed their versioning guidelines, and no >>>>>>>>>> longer applies .GA to final releases... >>>>>>>>>> >>>>>>>>>> Going forward, there will be no more GA suffix (but we still >>>>>>>>>> use .CRX, .BETAX etc.) >>>>>>>>>> >>>>>>>>>> On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: >>>>>>>>>> >>>>>>>>>>> ----- "Norman Richards" <orb@...> wrote: >>>>>>>>>>>> It's out. I'm still waiting on IT to updated the >>>>>>>>>>>> latest/latest-2/ >>>>>>>>>>>> latest-2.1 docs links, but otherwise the release process >>>>>>>>>>>> should be >>>>>>>>>>>> done. >>>>>>>>>>> >>>>>>>>>>> There seems to have been a small glitch with the naming of >>>>>>>>>>> the 2.1.2 release in maven: >>>>>>>>>>> http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ >>>>>>>>>>> >>>>>>>>>>> I would expect '2.1.2.GA' rather than '2.1.2'? >>>>>>>>>>> >>>>>>>>>>> Congrats on the release! >>>>>>>>>>> >>>>>>>>>>> cheers, >>>>>>>>>>> asgeir >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> seam-dev mailing list >>>>>>>>>>> seam-dev@... >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> seam-dev mailing list >>>>>>>>>> seam-dev@... >>>>>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> seam-dev mailing list >>>>>>>> seam-dev@... >>>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseI don't think version ranges work anyway with the . separator between
the micro and qualifier (see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4139850#4139850) but we can fix by using a pom redirect thing. Norman can you look at this? On 11 Jun 2009, at 12:23, Max Rydahl Andersen wrote: > >> Assuming version ranges aren't used, then it's fine. > version ranges are very useful and i bet some is using it with > seam...so I would say that it should be fixed. > > /max >> >>> -max >>> >>>> On 10 Jun 2009, at 11:48, Pete Muir wrote: >>>> >>>>> Right, but they don't reflect that we were asked to drop the GA >>>>> qualifier. So, should we add it back in? >>>>> >>>>> On 9 Jun 2009, at 23:17, Max Rydahl Andersen wrote: >>>>> >>>>>> The versioning guidelines is osgi afaik. >>>>>> >>>>>> /max >>>>>> >>>>>> Pete Muir wrote: >>>>>>> :-) >>>>>>> >>>>>>> If someone would update the JBossVersioningGuideline wiki >>>>>>> page, we'll be sure to follow it! >>>>>>> >>>>>>> On 9 Jun 2009, at 16:38, Max Rydahl Andersen wrote: >>>>>>> >>>>>>>> osgi standard is the one that actually is consistent. >>>>>>>> >>>>>>>> Maven 3 will be using osgi. >>>>>>>> >>>>>>>> Really don't think we were told to remove GA from the >>>>>>>> technical names. >>>>>>>> >>>>>>>> /max >>>>>>>> >>>>>>>> Pete Muir wrote: >>>>>>>>> Well to be maven compatible we should switch to -CRX, -BETAX >>>>>>>>> etc. >>>>>>>>> >>>>>>>>> Actually, I think it was OSGi, not maven that has the >>>>>>>>> problem you describe. Anyway, we always use explicit >>>>>>>>> versions (and recommend this to people using our poms) so it >>>>>>>>> should be ok... >>>>>>>>> >>>>>>>>> Do people think we should just switch to the maven standard? >>>>>>>>> >>>>>>>>> On 9 Jun 2009, at 15:12, Emmanuel Bernard wrote: >>>>>>>>> >>>>>>>>>> I thought this renaming did not apply for maven bundles as >>>>>>>>>> the maven resolution mechanism was retarded. >>>>>>>>>> >>>>>>>>>> On Jun 9, 2009, at 08:43, Pete Muir wrote: >>>>>>>>>> >>>>>>>>>>> Nope, JBoss has changed their versioning guidelines, and >>>>>>>>>>> no longer applies .GA to final releases... >>>>>>>>>>> >>>>>>>>>>> Going forward, there will be no more GA suffix (but we >>>>>>>>>>> still use .CRX, .BETAX etc.) >>>>>>>>>>> >>>>>>>>>>> On 9 Jun 2009, at 00:41, Asgeir Frimannsson wrote: >>>>>>>>>>> >>>>>>>>>>>> ----- "Norman Richards" <orb@...> wrote: >>>>>>>>>>>>> It's out. I'm still waiting on IT to updated the latest/ >>>>>>>>>>>>> latest-2/ >>>>>>>>>>>>> latest-2.1 docs links, but otherwise the release process >>>>>>>>>>>>> should be >>>>>>>>>>>>> done. >>>>>>>>>>>> >>>>>>>>>>>> There seems to have been a small glitch with the naming >>>>>>>>>>>> of the 2.1.2 release in maven: >>>>>>>>>>>> http://repository.jboss.org/maven2/org/jboss/seam/jboss-seam/ >>>>>>>>>>>> >>>>>>>>>>>> I would expect '2.1.2.GA' rather than '2.1.2'? >>>>>>>>>>>> >>>>>>>>>>>> Congrats on the release! >>>>>>>>>>>> >>>>>>>>>>>> cheers, >>>>>>>>>>>> asgeir >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> seam-dev mailing list >>>>>>>>>>>> seam-dev@... >>>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> seam-dev mailing list >>>>>>>>>>> seam-dev@... >>>>>>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> seam-dev mailing list >>>>>>>>> seam-dev@... >>>>>>>>> https://lists.jboss.org/mailman/listinfo/seam-dev _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseOn Jun 11, 2009, at 6:35 AM, Pete Muir wrote: > I don't think version ranges work anyway with the . separator > between the micro and qualifier (see http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4139850#4139850) > but we can fix by using a pom redirect thing. Norman can you look > at this? What is a pom redirect? _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
|
|
Re: Seam 2.1.2 releaseOn Thu, Jun 11, 2009 at 1:45 PM, Norman Richards <orb@...> wrote:
The same really as an HTTP 303 except w/ a Maven 2 POM. <project xmlns="http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> <modelVersion>4.0.0</modelVersion> <groupId>org.jboss.seam</groupId> <artifactId>jboss-seam</artifactId> <version>2.1.2.GA</version> <distributionManagement> <relocation> <version>2.1.2</version> </relocation> </distributionManagement> </project> I'm not sure how many elements are required in <relocation> (just version or is groupId and artifactId required too). -Dan -- Dan Allen Senior Software Engineer, Red Hat | Author of Seam in Action http://mojavelinux.com http://mojavelinux.com/seaminaction http://in.relation.to/Bloggers/Dan NOTE: While I make a strong effort to keep up with my email on a daily basis, personal or other work matters can sometimes keep me away from my email. If you contact me, but don't hear back for more than a week, it is very likely that I am excessively backlogged or the message was caught in the spam filters. Please don't hesitate to resend a message if you feel that it did not reach my attention. _______________________________________________ seam-dev mailing list seam-dev@... https://lists.jboss.org/mailman/listinfo/seam-dev |
| < Prev | 1 - 2 | Next > |
| Free embeddable forum powered by Nabble | Forum Help |