Thanks for the comments.
> Looks like the commons skin is not applied to the above site -- its > LnF should be similar to the site on c.a.o. > I've tried to address the issue and refreshed RC1 but the published site is not the same as the one I get by generating locally through 'mvn site'. > When you were using version 2-0-RC1, I was under the impression you > were doing so while you were working out the release mechanics. Unless > we actually decide to release a version "2.0-RC1" (for broader > feedback from users etc.) the version in the artifacts we vote on > should simply be "2.0". > My original intent was indeed to publish the 2.0-RC1 to get broad user feedback. I could not find cases of votes on releasing an RC so I swayed; however, with the amount of changes that went in and the long time since previous release, it certainly would make sense... > Another thing I'd like to get feedback on from the Commons developer > community (I did bring this up a week or two ago though I think it was > part of another thread and therefore less conspicuous) is the package > name for the 2.0 release > I've seen your comment about the package name; should the question be raised through the mailing list? IMHO, although there are many changes, the scope of the project is still the same and despite the incompatible changes in the lower level classes, casual use is preserved (taking Jelly or commons configuration as reference). On the other hand, the rename would allow both JEXL and JEXL2 in the same application; not sure how often this can be useful. > -- perhaps you could post the clirr report > (IIRC, you looked at it) so everyone can form an opinion. > I've added the clirr report generation to the build but none of the reports show up in the published site... -- View this message in context: http://old.nabble.com/-VOTE--Release-JEXL-2.0-based-on-RC1-tp26362771p26375857.html Sent from the Commons - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
