I am using Grails 1.2.x (Tried both 1.2.0 and 1.2.2- same behavior)
I am able to create the application fine by using the command grails create-app
But, when I try any command within the project- it "freezes" after printing the Base Directory
I have tried grails clean, grails war, grails run-app, grails created-domain-class
Grails 1.1.x works just fine for me
UPDATE : 1.2-M2 worked as well. but not the other "stable" Grails 1.2.x releases
Any help would be welcome
C:\mylab\testhostc>grails war
Welcome to Grails 1.2.0 - http://grails.org/
Licensed under Apache Standard License2.0
Grails home is set to: C:\Programs\grails-1.2.0
Base Directory: C:\mylab\testhostc
I got it working now
I had an environment variable JAVA_OPTS with value as -Xms64M -Xmx128M -Xss128M -XX:MaxPermSize=128M
Once I removed that- the scripts work fine now
I have opened a defect for this- in case someone is interested
http://jira.codehaus.org/browse/GRAILS-6111
Related
I need to build https://mvnrepository.com/artifact/org.apache.poi/poi-ooxml-schemas/4.1.2 project from sources. Since I didn't find any sources except these https://archive.apache.org/dist/poi/release/src/poi-src-4.1.2-20200217.zip I am trying to build them.
gradle build
...
* What went wrong:
Execution failed for task ':ooxml:ant-fetch-ooxml-xsds'.
> Can't get https://www.ecma-international.org/publications/files/ECMA-ST/Office%20Open%20XML%201st%20edition%20Part%204%20(PDF).zip to /home/katya/tmp_work/poi-4.1.2/ooxml-lib/OfficeOpenXML-Part4.zip
Could you tell me where to get working sources of Apache POI version 4.1.2? I must build this library from sources version 4.1.2 .
Apache POI's source code can be obtained from the official SVN reposoitory or from the mirror GIT repository on GitHub.
Apache POI Developer Guide should give you enough information to get started. There's also a general readme on GitHub.
The "Apache POI - How To Build" section from the Apache POI Developer Guide:
Apache POI - How To Build
JDK Version
POI 4.0 and later require JDK version 1.8 or later.
POI 3.11 and later 3.x versions require JDK version 1.6 or later.
POI 3.5 to 3.10 required the JDK version 1.5 or later. Versions prior to 3.5 required JDK 1.4+.
Install Apache Ant
The POI build system requires Apache Ant version 1.8 - 1.9.x for Java 1.6 and higher. Newer versions (1.10.x) require Java 8 or higher.
The current source code has been tested to work with Ant version 1.9.x and 1.10.x.
Remember to set the ANT_HOME environment variable to where Ant was installed/extracted and add ANT_HOME/bin to your shell's PATH.
If you are unsure about the correct value for ANT_HOME, search your file system for "ant.jar". This file will be in the directory %ANT_HOME%/lib." For example, if the path to ant.jar is "C:/Programs/Ant/lib/ant.jar", then set ANT_HOME to "C:/Progams/Ant".
Install Apache Forrest
The POI build system requires Apache Forrest to build the documentation.
Specifically, the build has been tested to work with Forrest 0.90.
Remember to set the FORREST_HOME environment variable.
Building Targets with Ant
The main targets of interest to our users are:
Ant Target
Description
clean
Erase all build work products (ie. everything in the build directory).
compile
Compiles all files from main, ooxml and scratchpad.
test
Run all unit tests from main, ooxml and scratchpad.
jar
Produce jar files.
assemble
Produce .zip and tar.gz distribution packages.
docs
Generate all documentation (Requires Apache Forrest).
jenkins
Runs the tests which Jenkins, our Continuous Integration system, does. This includes the unit tests and various code quality checks.
Working with Eclipse
Apache POI includes a pre-defined Eclipse project file which can be used to quickly get set up in the Eclipse IDE.
First make sure that Java is set up properly and that you can execute the 'javac' executable in your shell.
Next, open Eclipse and create either a local SVN repository, or a copy of the Git repository, and import the project into Eclipse.
Right-click on "build.xml", and select "Run As / Ant Build...". The "Edit Configuration" dialog should appear. In the "Targets" tab, select the "Compile" target and click on "Run".
Note: when executing junit tests from within Eclipse, you might need to set the system property "POI.testdata.path" to the actual location of the 'test-data' directory to make the test framework find the required test-files. A simple value of 'test-data' usually works.
Working with IntelliJ Idea
Import the Gradle project into your IDE. Execute a build to get all the dependencies and generated code in place.
Note: when executing junit tests from within IntelliJ, you might need to set the system property "POI.testdata.path" to the actual location of the 'test-data' directory to make the test framework find the required test-files. A simple value of 'test-data' usually works.
Using Maven
Building Apache POI using Maven is not currently officially supported, and we strongly suggest continuing to use the official Ant build.
However, including Apache POI within your own Maven project is fully supported, and widely used. Please see the Components Page for details of the Maven artifacts available.
Setting environment variables
Linux: help.ubuntu.com, unix.stackexchange.com
Windows: en.wikipedia.org
by Glen Stampoultzis, Tetsuya Kitahata, David Fisher
-- https://poi.apache.org/devel/#Using+Maven
Hi we have to use JBoss 6.4, But when I try to execute my code it fails due to missing method and works fine with JBoss 6.3 and JBoss 7
the setSSLContext method became available in v4.5 of HttpClientBuiler.
JBOSS 6.4 comes bundled with v4.3.6JBOSS 6.4 comes bundled with v4.3.6
So if I use version 4.5.2 via maven, does it override all the JBoss methods. If not what is the solution?
I want to use JBoss 6.4 only.
If you want to want to use any other version of components which is not bundled with specific Jboss release, then you can create it as module dependencies and use it. Make sure that you should exclude the particular version of components which bundle with JBoss inside jboss-deployment-structure.xml file
see the link: https://docs.jboss.org/author/display/AS7/Class+Loading+in+AS7
I am using the soapUI maven in Jenkins (am at the latest and greatest release)
There seems to be an issue with the groovy 1.8.5 which is fixed in the later versions of Groovy (2.1.5 for example).
Is there a way to change the underlying groovy library for Jenkins to 2.1.5.
I tried replacing the 1.8.5 in WEB-INF/lib with the 2.1.5 version and jenkins does not even start up
Appreciate any ideas/pointers.
I have been using the following to set up a jBPM/JBoss server on a remote machine (linux)
http://docs.jboss.org/jbpm/v5.1/userguide/ch03.html
The above linked worked fine locally on my windows box, without any hitches. However, I am having numerous errors with starting/shutting-down the server, and having the drools-guvnor page run completely (or any other than the JBoss AS splash page on localhost:8080). Should this be working fine on linux as well, or are there any other references that I can seek? Also, I have no desire to install eclipse, just to get the jBPM designer going.
Or am I better off attempting to load jBPM into a separate JBoss install?
Running Red Hate Enterprise Linux Server release 5.8
Thank you for your time
I was unable to get the jBPM installer demo (packaged with jboss) to work. Instead I did a separate installation of jBPM and JBoss and set the JBoss home in the build.xml file. Then performed the individual installation of guvnor and designer using
ant install.guvnor.into.jboss
ant install.designer.into.jboss
Still having errors, but the designer/guvnor are up and running, now it is a database problem :(
I just package my JavaFX app using the provided tool. But when I try to run it using java -jar app.jar I get a message asking me to install a newer Java version. I'm using 6u33 withfx 2.2beta` in development environment and is running fine. So, my question is, what is the required config to run under Java 6?
Here is my package command:
\javafx-sdk2.2.0-beta\bin\javafxpackager.exe -createjar -appClass gui.principal.FrmPrincipal -classpath lib\jfxrt.jar;lib\antlr-2.7.7.jar;lib\dom4j-1.6.1.jar;lib\hibernate-commons-annotations-4.0.1.Final.jar;lib\hibernate-core-4.1.4.Final.jar -srcdir classes -outdir dist -outfile Etransporte.jar -V
Thanks!
Well, a couple of hours later I downloaded the final version of JavaFX SDK and installed it over my Java 6u33 SDK and everything worked fine since then. So, upgrade is the rule.
No need to use the beta sdk, use the production sdk. The beta sdk may have unresolved bugs and is not suitable for packaging applications for general deployment.
Just some general info, I think you probably have most of this covered already, but something might be useful.
Here is a sample batch script for packaging a javafx application with javafxpackager.exe. Offhand the command you are running looks fine.
Ensure that the java system and javafx installation on your test machine are both the same bit architectures (e.g. 32bit or 64bit). Also jre6+javafx2.2 is only supported on Windows machines, not Linux or Mac.
Note that if your client machine only has jre 6 installed and not the JavaFX runtime, then it is expected when you run your packaged app on that system that it will provide some prompt and help to allow the user to install the JavaFX runtime on the client.
Also note, that not all versions of jre6 are supported by JavaFX 2.2, it must be a recent version of jre6 (2.2 requires Java SE 6 Update 33). It does seem that you are running the right minimum version.