It looks like you have one of those problems that requires multiple sets of expertise and is more complicated than a volunteer can solve in a few minutes.

Is this an important problem?
Do you have a consulting budget to fix it?

One of the problems of getting your support from a community of volunteers is that you are depending on the kindness and interest of strangers.

If your problem is not clearly within the main area of interest of the community or is wrapped up in a development methodology that is not widely shared, you may have difficulty finding someone with the time, the interest and skill to fix your problem. We all have our own dragons to slay.

Perhaps you should start with a small "Hello World" and extend it to the point where the "compiled classes are useless". It is hard to see how compiled classes would be defective in any way but your tests will soon point to the thing that makes this happen.

Ron

On 04/11/2013 11:18 AM, [email protected] wrote:
Sorry this answer is not helpful.

m2e tells me, it's not their problem, it's maven and you tell me the
opposite!

I think it's neither IBM, because changing the Glassfish project to use
the IBM J9 VM instead of oracle jdk 1.6.0_45 compiles to correct classes,
as with the oracle jdk!

In opposition compiling within the WebSphere project on the command line
with:
mvn -X clean package -Dmaven.test.skip=true -Pdefault-profile
doesn't show any Error and the classes are defective independent of the
JAVA_HOME setting, either IBM J9 VM or the oracle jdk!

Further the jdk to use is declared within the pom with:

<plugin>
                                         <artifactId>maven-compiler-plugin
</artifactId>
                                         <version>
${version.maven-compiler-plugin}</version>
                                         <configuration>
                                                 <source>
${version.java.jdk}</source>
                                                 <target>
${version.java.jdk}</target>
                                                 <executable>
"${env.WAS8_HOME}/java/bin/javac.exe"</executable>
                                                 <showWarnings>true</
showWarnings>
                                                 <fork>true</fork>
                                         </configuration>
                                 </plugin>

The environment variable has been verified and is correct. Confirmed by
the logged output:

[DEBUG] properties used {env.INTEL64_HOME=C:\Program Files\Intel,
env.CONFIGSETROOT=C:\Windows\ConfigSetRoot,
java.home=C:\programs\ibm\WebSphere\AppServer\java\jre,
version.java.jdk=1.6, env.INTEL_MGMT_ENG_COMP=Intel(R) Management Engine
Components,
classworlds.conf=C:\daten\projects\junoWorkspace\MonteRosaWAS\.metadata\.plugins\org.eclipse.m2e.launching\launches\m2conf1670186333626179780.tmp,
version.org.jboss.arquillian.graphene=2.0.0.Final, env.COMMPATH=C:\Program
Files\Lenovo\Communications Utility, version.maven-assembly-plugin=2.4,
java.endorsed.dirs=C:\programs\ibm\WebSphere\AppServer\java\jre\lib\endorsed,
java.assistive=ON, env.USERNAME=juerg, java.fullversion=JRE 1.6.0 IBM J9
2.6 Windows 7 amd64-64 Compressed References 20130301_140166 (JIT enabled,
AOT enabled)
J9VM - R26_Java626_SR5_FP1_20130301_0937_B140166
JIT  - r11.b03_20130131_32403
GC   - R26_Java626_SR5_FP1_20130301_0937_B140166_CMPRSS
J9CL - 20130301_140166, java.vendor.url=http://www.ibm.com/,
env.INCLUDE=C:\programs\ibm\SQLLIB\INCLUDE;C:\programs\ibm\SQLLIB\LIB,
env.COMPUTERNAME=MIRA,
site.pmd.rulesets=C:\daten\projects\junoWorkspace\MonteRosaWAS\Reports\..\Site\src\pmd\rulesets,
java.version=1.6.0, env.APP_WAS_HOME=C:\programs\ibm\WebSphere\AppServer,
....
  The whole concludes with:

[INFO] Reactor Summary:
[INFO]
[INFO] Site - Agile Storyboard Editor/Document-generator . SUCCESS
[0.000s]
[INFO] MonteRosaCommon ................................... SUCCESS
[2.464s]
[INFO] MonteRosa CCC ..................................... SUCCESS
[0.812s]
[INFO] MonteRosa EJB ..................................... SUCCESS
[1.716s]
[INFO] Monterosa GUI ..................................... SUCCESS
[2.948s]
[INFO] Reports ........................................... SUCCESS
[0.764s]
[INFO] MonteRosa Application ............................. SUCCESS
[0.718s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 9.766s
[INFO] Finished at: Mon Nov 04 17:02:06 CET 2013
[INFO] Final Memory: 11M/20M
[INFO]
------------------------------------------------------------------------

But the compiled classes are not usable at all. Of course, it's a
multi-module project, which may be the origin of the problem. I can only
say, it works with the glassfish configuration, but it don't with the
WebSphere configuration! It' worked for a while with WAS too but then it
stopped to work for an unknown reason.

I don't know what is going on behind the scenes, hence I need a little
help to resolve the issue. Being sent from one to the next is not exactly
the expected kind of help.




--
Ron Wheeler
President
Artifact Software Inc
email: [email protected]
skype: ronaldmwheeler
phone: 866-970-2435, ext 102


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to