I have finally made a production worthy app with play, and use the play war -o foo command to create an exploded war. However, its size goes on to 30 MB and there are a lot of folders included. I develop in eclipse, so there are some eclipse folders too. Below is a list of the folders I have. Can anyone help me out with the unnecessary folders? I have zeroed in on the app, conf, public and lib folders. Is my assumption correct?
├── app
│ ├── controllers
│ ├── jobs
│ │ ├── daily
│ │ └── monthly
│ ├── models
│ │ ├── encrypt
│ │ ├── file
│ │ ├── login
│ │ └── mail
│ ├── playground
│ └── views
│ ├── Application
│ └── errors
├── conf
├── eclipse
│ └── classes
│ ├── controllers
│ ├── jobs
│ │ ├── daily
│ │ └── monthly
│ ├── models
│ │ ├── encrypt
│ │ ├── file
│ │ ├── login
│ │ └── mail
│ └── playground
├── lib
├── logs
├── public
│ ├── bootstrap
│ │ ├── css
│ │ ├── img
│ │ ├── js
│ │ │ └── tests
│ │ │ ├── unit
│ │ │ └── vendor
│ │ └── less
│ ├── images
│ ├── javascripts
│ └── stylesheets
├── test
└── tmp
├── bytecode
│ └── DEV
└── classes
├── controllers
├── helpers
├── jobs
│ ├── daily
│ └── monthly
├── models
│ ├── encrypt
│ ├── file
│ ├── login
│ └── mail
└── playground
You need to delete your tmp folder as well, try to use play clean on your project.
All folders in app, conf, lib and public should be kept in your war. Maybe should add precompiled
Related
I don't know if there's a name for this kind of behavior.
I've seen it in IntelliJ, where single-folder folders are unified or flattened in the project tree pane, where instead of:
.
├── pom.xml
├── src
│ ├── main
│ │ ├── java
│ │ │ └── com
│ │ │ └── somepkg
│ │ │ └── coreapi
│ │ │ ├── controllers
│ │ │ │ ├── AssetMutations.java
│ │ │ │ ├── HomeController.java
│ │ │ │ └── SessionsQuery.java
│ │ │ ├── CoreApiApplication.java
You see:
.
├── pom.xml
├── src
│ ├── main
│ │ ├── java
│ │ │ └── com.somepkg.coreapi
│ │ │ ├── controllers
│ │ │ │ ├── AssetMutations.java
│ │ │ │ ├── HomeController.java
│ │ │ │ └── SessionsQuery.java
│ │ │ ├── CoreApiApplication.java
Is there a way to make vs code tree-view file explorer to show subfolders this way?
It looks like it is in the iteration plan for June, 2019.
See Iteration plan for June, 2019: release in July, 2019 and issue: merging single child directories.
Update: making it into v1.41 to be released in December, 2019. See https://github.com/microsoft/vscode-docs/blob/vnext/release-notes/v1_41.md#compact-folders-in-explorer
Compact folders in Explorer
In the File Explorer, we now render single child folders in a compact
form. In such a form, single child folders will be compressed in a
combined tree element. Useful for Java package structures, for
example.
Setting explorer.compactFolders controls this behavior. By default,
this setting is turned on.
So "explorer.compactFolders": false, will disable the feature.
I'm using jruby 1.7.12 (1.9.3p392) and I want to take advantage of the Scala Akka library. I'm aware of the Mikka gem, but I want to do this manually.
I've downloaded the Akka library "2.3.8" from http://akka.io/downloads/ (specifically the link "Akka 2.3.8 distribution for Scala 2.11").
Below is the file structure (one app.rb JRuby file and the rest is the downloaded Akka library)...
├── akka-2.3.8
| ├── bin
| ├── config
| ├── deploy
| ├── doc
│ ├── lib
│ │ ├── akka
│ │ │ ├── akka-actor_2.11-2.3.8.jar
│ │ │ ├── akka-agent_2.11-2.3.8.jar
│ │ │ ├── akka-camel_2.11-2.3.8.jar
│ │ │ ├── akka-cluster_2.11-2.3.8.jar
│ │ │ ├── akka-contrib_2.11-2.3.8.jar
│ │ │ ├── akka-dataflow_2.11-2.3.8.jar
│ │ │ ├── akka-durable-mailboxes-2.3.8.jar
│ │ │ ├── akka-file-mailbox_2.11-2.3.8.jar
│ │ │ ├── akka-kernel_2.11-2.3.8.jar
│ │ │ ├── akka-mailboxes-common_2.11-2.3.8.jar
│ │ │ ├── akka-multi-node-testkit_2.11-2.3.8.jar
│ │ │ ├── akka-persistence-experimental_2.11-2.3.8.jar
│ │ │ ├── akka-persistence-tck-experimental_2.11-2.3.8.jar
│ │ │ ├── akka-remote-tests_2.11-2.3.8.jar
│ │ │ ├── akka-remote_2.11-2.3.8.jar
│ │ │ ├── akka-slf4j_2.11-2.3.8.jar
│ │ │ ├── akka-testkit_2.11-2.3.8.jar
│ │ │ ├── akka-transactor_2.11-2.3.8.jar
│ │ │ ├── akka-zeromq_2.11-2.3.8.jar
│ │ │ ├── camel-core-2.10.3.jar
│ │ │ ├── config-1.2.1.jar
│ │ │ ├── guava-12.0.jar
│ │ │ ├── hamcrest-core-1.3.jar
│ │ │ ├── hawtjni-runtime-1.8.jar
│ │ │ ├── jna-3.0.9.jar
│ │ │ ├── jnr-constants-0.8.2.jar
│ │ │ ├── jsr305-1.3.9.jar
│ │ │ ├── junit-4.11.jar
│ │ │ ├── leveldb-0.5.jar
│ │ │ ├── leveldb-api-0.5.jar
│ │ │ ├── leveldbjni-1.7.jar
│ │ │ ├── leveldbjni-all-1.7.jar
│ │ │ ├── leveldbjni-linux32-1.5.jar
│ │ │ ├── leveldbjni-linux64-1.5.jar
│ │ │ ├── leveldbjni-osx-1.5.jar
│ │ │ ├── leveldbjni-win32-1.5.jar
│ │ │ ├── leveldbjni-win64-1.5.jar
│ │ │ ├── netty-3.8.0.Final.jar
│ │ │ ├── protobuf-java-2.5.0.jar
│ │ │ ├── scala-continuations-library_2.11-1.0.2.jar
│ │ │ ├── scala-reflect-2.11.0.jar
│ │ │ ├── scala-stm_2.11-0.7.jar
│ │ │ ├── scalatest_2.11-2.1.3.jar
│ │ │ ├── slf4j-api-1.7.5.jar
│ │ │ ├── uncommons-maths-1.2.2a.jar
│ │ │ └── zeromq-scala-binding_2.11-0.0.7-spark.jar
│ │ └── scala-library-2.11.4.jar
│ └── src
│ └── akka
│ ├── akka-actor_2.11-2.3.8-sources.jar
│ ├── akka-agent_2.11-2.3.8-sources.jar
│ ├── akka-camel_2.11-2.3.8-sources.jar
│ ├── akka-cluster_2.11-2.3.8-sources.jar
│ ├── akka-contrib_2.11-2.3.8-sources.jar
│ ├── akka-dataflow_2.11-2.3.8-sources.jar
│ ├── akka-durable-mailboxes-2.3.8-sources.jar
│ ├── akka-file-mailbox_2.11-2.3.8-sources.jar
│ ├── akka-kernel_2.11-2.3.8-sources.jar
│ ├── akka-mailboxes-common_2.11-2.3.8-sources.jar
│ ├── akka-multi-node-testkit_2.11-2.3.8-sources.jar
│ ├── akka-persistence-experimental_2.11-2.3.8-sources.jar
│ ├── akka-persistence-tck-experimental_2.11-2.3.8-sources.jar
│ ├── akka-remote-tests_2.11-2.3.8-sources.jar
│ ├── akka-remote_2.11-2.3.8-sources.jar
│ ├── akka-slf4j_2.11-2.3.8-sources.jar
│ ├── akka-testkit_2.11-2.3.8-sources.jar
│ ├── akka-transactor_2.11-2.3.8-sources.jar
│ └── akka-zeromq_2.11-2.3.8-sources.jar
└── app.rb
The contents of the app.rb file is...
require "java"
$CLASSPATH << "akka-2.3.8"
$: << File.join(File.dirname(__FILE__), "akka-2.3.8")
java_import java.lang.System
java_import "akka.actor.ActorRegistry"
java_import "akka.actor.Actors"
java_import "akka.actor.UntypedActor"
...I appreciate that (in JRuby) $CLASSPATH and the load path $: are mapped, but I thought I would try both.
Running app.rb causes the following error (importing java.lang.System is fine, the akka.actor.ActorRegistry is the first line that breaks)...
NameError: cannot load Java class akka.actor.ActorRegistry
for_name at org/jruby/javasupport/JavaClass.java:1250
get_proxy_class at org/jruby/javasupport/JavaUtilities.java:34
java_import at file:/Users/markmcdonnell/.rubies/jruby-1.7.12/lib/jruby.jar!/jruby/java/core_ext/object.rb:26
map at org/jruby/RubyArray.java:2409
java_import at file:/Users/markmcdonnell/.rubies/jruby-1.7.12/lib/jruby.jar!/jruby/java/core_ext/object.rb:22
(root) at size.rb:7
What is the problem here. Have I not downloaded the right files or am I not referencing them properly?
Maybe the << does not add all the individual jars to the classpath? You might have to look for something else to include all jars in lib and lib/akka. Unfortunately I don't know enough JRuby to tell you how to do it.
Also: you are importing classes (ActorRegistry, Actors) that don't exist in Akka 2.3.8. Please check the latest API docs, and make sure you are not trying an Akka 1.x example (as ActorRegistry would indicate).
So, the following seems to work, maybe you can use that as a starting point:
require "java"
$CLASSPATH << "akka-2.3.8/lib/scala-library-2.11.4.jar"
$CLASSPATH << "akka-2.3.8/lib/akka/akka-actor_2.11-2.3.8.jar"
$CLASSPATH << "akka-2.3.8/lib/akka/config-1.2.1.jar"
java_import java.lang.System
java_import "akka.actor.ActorRef"
java_import "akka.actor.ActorSystem"
java_import "akka.actor.Props"
java_import "akka.actor.UntypedActor"
I was asking on #arquillian Freenode IRC channel about question
Arquillian JPA tutorial: Could not create new instance of class org.jboss.arquillian.test.impl.EventTestRunnerAdaptor
when a user told me that he successfully runned
https://github.com/arquillian/arquillian-examples/tree/master/arquillian-persistence-tutorial
so I did
git clone https://github.com/arquillian/arquillian-examples.git
then in Eclipse, I clicked File->Import->Existing Maven Projects and selecte the subdirectory
arquillian-examples/arquillian-persistence-tutorial
Once Eclipse finished importing the project, I obtain in file
/src/test/java/org/arquillian/example/GamePersistenceTest.java
line 146, the error message
Game_ cannot be resolved to a variable
What can I do? In my attempt at the link at beginning of the page, this did not happpen.
I did not change any file downloaded from git repo.
Folder tree
.
├── pom.xml
├── src
│ ├── main
│ │ ├── java
│ │ │ └── org
│ │ │ └── arquillian
│ │ │ └── example
│ │ │ └── Game.java
│ │ └── resources
│ │ └── META-INF
│ │ └── persistence.xml
│ └── test
│ ├── java
│ │ └── org
│ │ └── arquillian
│ │ └── example
│ │ └── GamePersistenceTest.java
│ ├── resources
│ │ ├── arquillian.launch
│ │ ├── arquillian.xml
│ │ └── jbossas-ds.xml
│ ├── resources-glassfish-embedded
│ │ ├── glassfish-resources.xml
│ │ ├── logging.properties
│ │ └── test-persistence.xml
│ ├── resources-glassfish-remote
│ │ └── test-persistence.xml
│ └── resources-jbossas-managed
│ └── test-persistence.xml
└── target
├── classes
│ ├── META-INF
│ │ ├── MANIFEST.MF
│ │ ├── maven
│ │ │ └── org.arquillian.example
│ │ │ └── arquillian-persistence-tutorial
│ │ │ ├── pom.properties
│ │ │ └── pom.xml
│ │ └── persistence.xml
│ └── org
│ └── arquillian
│ └── example
│ └── Game.class
└── test-classes
├── arquillian.launch
├── arquillian.xml
├── glassfish-resources.xml
├── jbossas-ds.xml
├── logging.properties
├── org
│ └── arquillian
│ └── example
│ └── GamePersistenceTest.class
└── test-persistence.xml
30 directories, 24 files
The _Game class in that example is generated by the Hibernate JPA 2 metamodel generator (hibernate-jpamodelgen) that is defined as a dependency in the project POM. You'll now need to generate the metamodel by employing one the options outlined in the metamodel generator reference guide.
You could use Eclipse itself by configuring the annotation processing phase. Or you could modify the POM to use the maven-compiler-plugin configuration specified in the guide, to run as part of your build.
I have installed spring-security-facebook to a test grail application. This was done after installing spring-security-core and running s2-quickstart.
I am just a novice and was trying to integrate the facebook login button into my test app. But, the problem is that when I run s2-init-facebook the plugin is not generating the default Dao as it was told in the documentation in http://grails.org/plugin/spring-security-facebook
Use your own authentication dao
Plugin generates an Dao, after calling s2-init-facebook#, and put it
into your #conf/spring/resources.groovy and #Config.groovy#. Actually
it's an 'dumb' dao implementations, you have to rewrite it to follow
your data structures:
The shortened tree output of my app directory is given below:
.
├── application.properties
├── grails-app
│ ├── conf
│ │ ├── ApplicationResources.groovy
│ │ ├── BootStrap.groovy
│ │ ├── BuildConfig.groovy
│ │ ├── Config.groovy
│ │ ├── DataSource.groovy
│ │ ├── hibernate
│ │ ├── spring
│ │ │ └── resources.groovy
│ │ └── UrlMappings.groovy
│ ├── controllers
│ │ ├── LoginController.groovy
│ │ └── LogoutController.groovy
│ ├── domain
│ │ └── com
│ │ └── fbtest
│ │ └── webapp
│ │ └── auth
│ │ ├── FacebookUser.groovy
│ │ ├── SecRole.groovy
│ │ ├── SecUser.groovy
│ │ └── SecUserSecRole.groovy
│ ├── i18n
│ │ ├── ...
│ ├── services
│ ├── taglib
│ ├── utils
│ └── views
│ ├── error.gsp
│ ├── index.gsp
│ ├── layouts
│ │ └── main.gsp
│ └── login
│ ├── auth.gsp
│ └── denied.gsp
├── lib
├── scripts
├── src
│ ├── groovy
│ └── java
├── test
│ ├── integration
│ └── unit
└── web-app
├── ...
resource.groovy file is also empty.
// Place your Spring DSL code here
beans = {
}
Please, help me in understanding if I am doing any thing wrong.
I am using Grails version: 2.0.4 and spring-security-facebook's version is 0.8.
Thanks in advance.
Oh, it should be removed from documentation. For last versions it's not necessary to have own DAO, now it have default very flexible dao. And now it's not generated during install. Try to run your app, it should works, if everything is configured correctly.
You can still use own DAO, if you have implemented it by yourself. But for versions since 0.7 nearly everything can be extending with optional FacebookAuthService, that you can implement if you wish (it's described in documentation as well).
For my first steps into Lift I just started with this tutorial but it won't work for me. Instead of the simple chat app I only get these two exceptions:
Error processing snippet: comet
Reason: Comet Component not found
and
Error processing snippet: ChatIn
Reason: Class Not Found
Here is the directory structure of my compiled webapp:
target/chat-1.0-SNAPSHOT/
├── index.html
├── META-INF
└── WEB-INF
├── classes
│ └── code
│ ├── comet
│ │ ├── Chat$$anonfun$lowPriority$1.class
│ │ ├── Chat.class
│ │ ├── ChatServer$$anonfun$lowPriority$1.class
│ │ ├── ChatServer.class
│ │ └── ChatServer$.class
│ └── snippet
│ ├── ChatIn$$anonfun$render$1.class
│ ├── ChatIn.class
│ └── ChatIn$.class
├── lib
│ ├── activation-1.1.jar
│ ├── commons-codec-1.4.jar
│ ├── commons-fileupload-1.2.2.jar
│ ├── derby-10.7.1.1.jar
│ ├── h2-1.2.147.jar
│ ├── htmlparser-1.2.1.jar
│ ├── joda-time-1.6.2.jar
│ ├── lift-actor_2.9.0-2.4-M3.jar
│ ├── lift-common_2.9.0-2.4-M3.jar
│ ├── lift-db_2.9.0-2.4-M3.jar
│ ├── lift-json_2.9.0-2.4-M3.jar
│ ├── lift-mapper_2.9.0-2.4-M3.jar
│ ├── lift-proto_2.9.0-2.4-M3.jar
│ ├── lift-util_2.9.0-2.4-M3.jar
│ ├── lift-webkit_2.9.0-2.4-M3.jar
│ ├── mail-1.4.4.jar
│ ├── paranamer-2.3.jar
│ ├── scala-compiler-2.9.0.jar
│ ├── scala-library-2.9.0.jar
│ ├── scalap-2.9.0.jar
│ └── slf4j-api-1.6.1.jar
└── web.xml
But as you can see, there are the compiled .class files for Chat, ChatServer and ChatIn, so what's wrong?
Please bring this question to the Lift Google group: https://groups.google.com/forum/#!forum/liftweb
It's likely that your Boot.scala doesn't contain the correct information, but without the source, it's tough to figure out the issue.