[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Compiling Java code -- Nothing to compile - all classes are up to date

+++ Jan Pazdziora [01/10/13 17:28 +0800]:


I'm using OpenShift Enterprise 1.2 and I try to get maven compilation
working for my EAP applications.

I start with the default template and when I download


compile that one .java manually and commit the src/ content including
the manually-built .class to my git repository and push, things
works. However, when I remove the .class and just want OpenShift to
take care of the compilation, nothing happens:

This seems odd.

rhc app create -a spnego -t jbosseap-6.0
cd spnego
git remote add upstream git://github.com/kwart/spnego-demo.git
git fetch upstream
git merge -X theirs upstream/demo-for-adelton
git push

At this point everything compiled and deployed.  However it seemed
like ROOT.war was still around because when I curl'd the app I saw the
default welcome text.

I then diff'd with the original template pom and saw that the
'openshift' maven profile is what set the war name.  Once I readed at
and pushed the code I would see that the new application was

Was the process you tried different than the steps above?


	remote: [INFO] --- maven-compiler-plugin:2.0.2:compile (default-compile) @ eap17542 ---
	remote: [INFO] Nothing to compile - all classes are up to date

I've also tried to manually add the maven-compiler-plugin
specification via

diff --git a/pom.xml b/pom.xml
index e8b8d1c..b59468c 100755
--- a/pom.xml
+++ b/pom.xml
@@ -74,6 +74,15 @@ jboss-eap-*-maven-repository/org/jboss/spec/jboss-javaee-6.0
+                       <plugin>
+                               <groupId>org.apache.maven.plugins</groupId>
+                               <artifactId>maven-compiler-plugin</artifactId>
+                               <version>2.0.2</version>
+                               <configuration>
+                                       <source>1.6</source>
+                                       <target>1.6</target>
+                               </configuration>
+                       </plugin>

but with no effect.

The documentation at


is not very clear about the necessary changes to the vanilla git
repo (and pom.xml) that a user gets with rhc app create.

What is the mechanism which makes the maven-compiler-plugin run the
search for .java bits and how should I tell it that there is a


which I'd like compiled into .class and added to ROOT.war?

Thank you,

Jan Pazdziora | adelton at #ipa*, #brno
Principal Software Engineer, Identity Management Engineering, Red Hat

users mailing list
users lists openshift redhat com

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]