I was wondering if there has been any development on the bug http://jira.codehaus.org/browse/GRAILS-2685 ? It says that it's resolved but when I try to use it in 1.3.1 (latest at the time of writing as far as I know) it still does not work.
Great news! With the emergence of Grails 1.3.3 the views provided by plugins in a way described here works again! So the actual solution is to upgrade to 1.3.3 and life is good :D
Related
I want to upgrade a Bootstrap 4 html/css website from Bootstrap 4.0.0 to the latest version (currently 4.3.1). I have googled this and only see instructions for upgrading from 3.x.x to 4.x.x. Can anyone point me in the right direction?
I agree with the lack of resources provided. However unlike the migration from 3.x.x to 4.x.x, there isn't any loss of component here. But you will see some nasty changes, that will just break things. I would suggest going through the examples for version 4.0.0 and then cross referencing them with the ones for 4.3.1 .This will not solve your problems but it will definitely point you in the right direction.
You found nothing, because there is not much to say (There should be no breaking changes).
So you simple need to update (replace) the library files (CSS, JS, Probably Fonts).
Note: In current days we use Package Managers like NPM and install our frameworks as Packages. In case of NPM, you can find bootstrap here.
I have an application using JRuby 1.6.7, Ruby 1.9.2, Rails 3.1.3 and Warbler 1.4.0.beta2
For a while now, I have been trying to update the application to use JRuby 1.7.x. Every time I tried (with versions 1.7.3, 1.7.4, and most recently 1.7.6) I would get the following error:
org.jruby.rack.RackInitializationException: No such file or directory - /home/production/var/tmp/Jetty_0_0_.war/webapp/WEB-INF/lib/gems.jar!/gems/activesupport-3.1.3/lib/active_support/locale/en.yml
After some help from this question here: Warble not including active support locale files, pin pointed that that issue was with the warbler configuration in my application. We had enabled the following configuration:
config.features = %w(gemjar executable compiled)
Specifically, the gemjar feature was the one causing the issue. With that feature disabled, everything works fine (the WAR deploys perfectly)
I am wondering, if anyone else has run into this, or if anyone knows what the issue might be?
And then more specifically, what are the disadvantages to disabling the gemjar feature of Warbler? From what I can tell, there shouldn't theoretically be anything devastating by disabling it... but I may be overlooking something.
(I do also wonder if the full warbler 1.4.0 release might fix this... but I can't find anything about when a release might be coming out)
there are none - actually running a .war with gemjar might have issues on some servers (esp. if they do not expand the deployed .war, since then it's quite hard to reference files/resources packaged in a .war while still inside a .jar). on the other hand it should roll fine if things are expanded (even with gemjar) ...
you should definitely report this with Warbler's repository (if not reported already).
it should not be hard to fix - likely a one liner, I know a PR would be most welcome :)
NOTE: on the other hand if it worked in a previous JRuby and updating 1.7.x is the issue, than it might be a "regression" on JRuby's side and they might actually fix this if they knew about it ...
The default language version for ruby on IronWorkers is 1.9.3. When will it be bumped to 2.0?
http://dev.iron.io/worker/reference/environment/#default_languages_versions
Is there an easy way to upgrade to ruby 2.0 without too much delay when launching a task?
Thanks,
Dimitri
[edit] You can now use multiple different language packs using our Stacks functionality as specified above. Also here's more info in the Iron.io dev center: http://dev.iron.io/worker/reference/environment/#default_language_versions
Currently no there is no way to use Ruby 2. We are working on a way to give users the ability to choose their language versions much easier, but there's no ETA at this point.
If you need any help or support don't hesitate to jump into our live chat http://get.iron.io/chat
Iron Worker is finally supporting custom environments, one of which is Ruby 2.1:
http://blog.iron.io/2014/03/ironio-launches-custom-runtime.html
doesn't play framework 2.0.4 support some consoles?
when i was using 1.x, i could use the console "play eclipsify"
and "play dependencies" to fbconnect and fbgraph modules
but from when i chaged the version, it's not working.
then how can i connect those modules? i've no idea to do that
i think the new version doesn't support those consoles for modules
is it correct?
is the way totally different? if then please let me know.
also juz awhile ago i checked the 1.2.5 version
and there is no dependencies.yml and module folder
would you let me know what changed and how can i apply and adjust?
Thank you for your time
https://github.com/playframework/Play20/wiki/Play-2.0-for-Play-1.x-developers
check this out
and i wanna tell you some people who evaluate my question
what if there is no begginer who really want to learn and ask, how developing survives?
i hate reputations!
Yes, it's TOTALY different, although some ideas are the same, Play 2.x is quite new product (as stated in many topics and questions since many months), there's (fortunately) no backward compatibility between Play 1.x and 2.x!
When you'll visit Play 1.x (only) modules page the first thing you'll see will be that disclaimer:
These modules are for the Play 1.x series only. Play 2.0 modules can be hosted anywhere on any Ivy, Maven or Git repository. We will add a directory for them here shortly.
Thanx to Pere Villega you can also search for Play 2.0 for Java or Scala modules on PlayModules.net site, however you need carefully choose between Play 1.x and Play 2.x series.
For working with eclipse, check the Play's 2.0 IDE documentation.
I am using the extension tag in my xsd to validate XML, this works fine in the .Net framework in my windows local machine. But in Mono 1.9 machine the extension tag does not work, it does not validate the xml. I did some R & D on this issue and in one site it was given this problem as a bug and gave the solution to it referring to install some patch to mono.Here is the link
http://www.mail-archive.com/mono-bugs#lists.ximian.com/msg62811.html
I completely do not understand how to solve this issue and how the above link would help me. I would be glad if anyone helps me in solving this issue.
Thanks in advance
Mono 1.9 is ~3 years old. The patch is already included in more modern versions of Mono. Upgrading is probably your best bet.