2:28 a.m.
Hi,
I am trying to build wildfly locally. I am facing the errors mentioned
below. I had sent a similar mail three weeks ago and got no response.
Yesterday, I had posted this on jboss forum
https://developer.jboss.org/message/906929. Jaikiran suggested to re-post
it to with the latest wildfly code.
Environment:
*OS* : Ubuntu 12.04(64bit)
*Java* : version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
Is there something obvious that I am missing? Please let me know.
*Error *
sandeep@sandeep:~/development/grails-project/wildfly$ ./build.sh
Maven already exists
Maven is correct version
./tools/maven/bin/mvn -s tools/maven/conf/settings.xml install
[INFO] Scanning for projects...
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Build Order:
[INFO]
[INFO] WildFly: Parent Aggregator
[INFO] WildFly: Naming Subsystem
[[[ truncated some of the unrelated logs ]]]]
[INFO] WildFly Test Suite: Integration - Smoke
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building WildFly: Parent Aggregator 9.0.0.Alpha2-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (ban-bad-dependencies) @
wildfly-parent ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @
wildfly-parent ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @
wildfly-parent ---
[INFO]
[INFO] --- buildnumber-maven-plugin:1.3:create-timestamp
(get-build-timestamp) @ wildfly-parent ---
[INFO]
[INFO] --- buildnumber-maven-plugin:1.3:create (get-scm-revision) @
wildfly-parent ---
[INFO] Executing: /bin/sh -c cd
/home/sandeep/development/grails-project/wildfly && git rev-parse --verify
HEAD
[INFO] Working directory: /home/sandeep/development/grails-project/wildfly
[INFO] Storing buildNumber: 206ad185abcaec3dc00ab87e07e23829bd0baee2 at
timestamp: 1413270863566
[INFO] Storing buildScmBranch: master
[INFO]
[INFO] --- maven-checkstyle-plugin:2.12.1:checkstyle (check-style) @
wildfly-parent ---
[INFO]
[INFO] --- maven-source-plugin:2.3:jar-no-fork (attach-sources) @
wildfly-parent ---
[INFO]
[INFO] --- maven-install-plugin:2.5.1:install (default-install) @
wildfly-parent ---
[INFO] Installing /home/sandeep/development/grails-project/wildfly/pom.xml
to
/home/sandeep/.m2/repository/org/wildfly/wildfly-parent/9.0.0.Alpha2-SNAPSHOT/wildfly-parent-9.0.0.Alpha2-SNAPSHOT.pom
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building WildFly: Naming Subsystem 9.0.0.Alpha2-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (ban-bad-dependencies) @
wildfly-naming ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-java-version) @
wildfly-naming ---
[INFO]
[INFO] --- maven-enforcer-plugin:1.3.1:enforce (enforce-maven-version) @
wildfly-naming ---
[INFO]
[INFO] --- buildnumber-maven-plugin:1.3:create-timestamp
(get-build-timestamp) @ wildfly-naming ---
[INFO]
[INFO] --- buildnumber-maven-plugin:1.3:create (get-scm-revision) @
wildfly-naming ---
[INFO]
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @
wildfly-naming ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 9 resources
[INFO]
[INFO] --- maven-compiler-plugin:3.1:compile (default-compile) @
wildfly-naming ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 87 source files to
/home/sandeep/development/grails-project/wildfly/naming/target/classes
[INFO] -------------------------------------------------------------
[WARNING] COMPILATION WARNING :
[INFO] -------------------------------------------------------------
[WARNING]
/home/sandeep/development/grails-project/wildfly/naming/src/main/java/org/jboss/as/naming/subsystem/RemoteNamingAdd.java:[30,31]
org.jboss.as.controller.ServiceVerificationHandler in
org.jboss.as.controller has been deprecated
[WARNING]
/home/sandeep/development/grails-project/wildfly/naming/src/main/java/org/jboss/as/naming/subsystem/NamingBindingAdd.java:[41,31]
org.jboss.as.controller.ServiceVerificationHandler in
org.jboss.as.controller has been deprecated
[WARNING]
/home/sandeep/development/grails-project/wildfly/naming/src/main/java/org/jboss/as/naming/subsystem/NamingSubsystemAdd.java:[27,31]
org.jboss.as.controller.ServiceVerificationHandler in
org.jboss.as.controller has been deprecated
[WARNING]
/home/sandeep/development/grails-project/wildfly/naming/src/main/java/org/jboss/as/naming/subsystem/RemoteNamingAdd.java:[30,31]
org.jboss.as.controller.ServiceVerificationHandler in
org.jboss.as.controller has been deprecated
[WARNING]
/home/sandeep/development/grails-project/wildfly/naming/src/main/java/org/jboss/as/naming/subsystem/NamingBindingAdd.java:[41,31]
org.jboss.as.controller.ServiceVerificationHandler in
org.jboss.as.controller has been deprecated
[WARNING]
/home/sandeep/development/grails-project/wildfly/naming/src/main/java/org/jboss/as/naming/subsystem/NamingSubsystemAdd.java:[27,31]
org.jboss.as.controller.ServiceVerificationHandler in
org.jboss.as.controller has been deprecated
[INFO] 6 warnings
[INFO] -------------------------------------------------------------
[INFO] -------------------------------------------------------------
[ERROR] COMPILATION ERROR :
[INFO] -------------------------------------------------------------
[ERROR] Cannot read org.jboss.as.naming.logging package files, cause :
java.io.FileNotFoundException: org.jboss.as.naming.logging/NamingLogger
at
com.sun.tools.javac.processing.JavacFiler.getResource(JavacFiler.java:464)
at
org.jboss.logging.processor.apt.TranslationClassGenerator.findTranslationFiles(TranslationClassGenerator.java:152)
at
org.jboss.logging.processor.apt.TranslationClassGenerator.processTypeElement(TranslationClassGenerator.java:115)
at
org.jboss.logging.processor.apt.LoggingToolsProcessor.process(LoggingToolsProcessor.java:145)
at
com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793)
at
com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:722)
at
com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1700(JavacProcessingEnvironment.java:97)
at
com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1029)
at
com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1163)
at
com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1106)
at com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824)
at com.sun.tools.javac.main.Main.compile(Main.java:417)
at com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:132)
at
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126)
at
org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)
at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785)
at
org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[INFO] 1 error
[INFO] -------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] WildFly: Parent Aggregator ......................... SUCCESS [
5.533 s]
[INFO] WildFly: Naming Subsystem .......................... FAILURE [
5.495 s]
[INFO] WildFly: EE ........................................ SKIPPED
[[[ truncated some of the unrelated logs ]]]]
[INFO] WildFly Test Suite: Integration - Smoke ............ SKIPPED
[INFO]
------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 20.434 s
[INFO] Finished at: 2014-10-14T12:44:31+05:30
[INFO] Final Memory: 170M/465M
[INFO]
------------------------------------------------------------------------
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
(default-compile) on project wildfly-naming: Compilation failure
[ERROR] Cannot read org.jboss.as.naming.logging package files, cause :
java.io.FileNotFoundException: org.jboss.as.naming.logging/NamingLogger
[ERROR] at
com.sun.tools.javac.processing.JavacFiler.getResource(JavacFiler.java:464)
[ERROR] at
org.jboss.logging.processor.apt.TranslationClassGenerator.findTranslationFiles(TranslationClassGenerator.java:152)
[ERROR] at
org.jboss.logging.processor.apt.TranslationClassGenerator.processTypeElement(TranslationClassGenerator.java:115)
[ERROR] at
org.jboss.logging.processor.apt.LoggingToolsProcessor.process(LoggingToolsProcessor.java:145)
[ERROR] at
com.sun.tools.javac.processing.JavacProcessingEnvironment.callProcessor(JavacProcessingEnvironment.java:793)
[ERROR] at
com.sun.tools.javac.processing.JavacProcessingEnvironment.discoverAndRunProcs(JavacProcessingEnvironment.java:722)
[ERROR] at
com.sun.tools.javac.processing.JavacProcessingEnvironment.access$1700(JavacProcessingEnvironment.java:97)
[ERROR] at
com.sun.tools.javac.processing.JavacProcessingEnvironment$Round.run(JavacProcessingEnvironment.java:1029)
[ERROR] at
com.sun.tools.javac.processing.JavacProcessingEnvironment.doProcessing(JavacProcessingEnvironment.java:1163)
[ERROR] at
com.sun.tools.javac.main.JavaCompiler.processAnnotations(JavaCompiler.java:1106)
[ERROR] at
com.sun.tools.javac.main.JavaCompiler.compile(JavaCompiler.java:824)
[ERROR] at com.sun.tools.javac.main.Main.compile(Main.java:417)
[ERROR] at
com.sun.tools.javac.api.JavacTaskImpl.call(JavacTaskImpl.java:132)
[ERROR] at
org.codehaus.plexus.compiler.javac.JavaxToolsCompiler.compileInProcess(JavaxToolsCompiler.java:126)
[ERROR] at
org.codehaus.plexus.compiler.javac.JavacCompiler.performCompile(JavacCompiler.java:169)
[ERROR] at
org.apache.maven.plugin.compiler.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:785)
[ERROR] at
org.apache.maven.plugin.compiler.CompilerMojo.execute(CompilerMojo.java:129)
[ERROR] at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:132)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
[ERROR] at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
[ERROR] at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
[ERROR] at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:120)
[ERROR] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347)
[ERROR] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154)
[ERROR] at org.apache.maven.cli.MavenCli.execute(MavenCli.java:582)
[ERROR] at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:214)
[ERROR] at org.apache.maven.cli.MavenCli.main(MavenCli.java:158)
[ERROR] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[ERROR] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
[ERROR] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
[ERROR] at java.lang.reflect.Method.invoke(Method.java:601)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
[ERROR] at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR] mvn <goals> -rf :wildfly-naming
Thanks,
Sandeep.
4:17 a.m.
On Tue, Oct 14, 2014 at 9:28 AM, Sandeep Samdaria <sandyridgeracer(a)gmail.com
wrote:
*Java* : version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
Not completely sure what is your problem, but it would start with updating
JDK 7 to something more recent.
you are running u5, while latest is u67
7:38 a.m.
Yup, that worked for me. In addition to updating the jdk from u5 to u67, I
also had to point JAVA_HOME to the latest.
I wanted to contribute to wildfly project. Any minor/trivial ticket which I
can take a look into it as a newbie?
-Sandeep.
On Tue, Oct 14, 2014 at 2:47 PM, Tomaž Cerar <tomaz.cerar(a)gmail.com> wrote:
On Tue, Oct 14, 2014 at 9:28 AM, Sandeep Samdaria <
sandyridgeracer(a)gmail.com> wrote:
> *Java* : version "1.7.0"
> Java(TM) SE Runtime Environment (build 1.7.0-b147)
> Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
>
Not completely sure what is your problem, but it would start with updating
JDK 7 to something more recent.
you are running u5, while latest is u67
10:48 p.m.
Sandeep,
The WFLY JIRA has some issues which have been marked as "Awaiting for
volunteers". Here's a link to such unresolved issues
https://issues.jboss.org/issues/?jql=fixVersion%20%3D%20%22Awaiting%20Vol....
You can choose from one of them that interests you. You might want to
hang around in the #wildfly-dev channel on IRC (irc.freenode.net server)
where the WildFly developers can help you in getting started or working
on the issue that you pick.
-Jaikiran
On Tuesday 14 October 2014 06:08 PM, Sandeep Samdaria wrote:
Yup, that worked for me. In addition to updating the jdk from u5 to
u67, I also had to point JAVA_HOME to the latest.
I wanted to contribute to wildfly project. Any minor/trivial ticket
which I can take a look into it as a newbie?
-Sandeep.
On Tue, Oct 14, 2014 at 2:47 PM, Tomaž Cerar <tomaz.cerar(a)gmail.com
<mailto:tomaz.cerar@gmail.com>> wrote:
On Tue, Oct 14, 2014 at 9:28 AM, Sandeep Samdaria
<sandyridgeracer(a)gmail.com <mailto:sandyridgeracer@gmail.com>> wrote:
_Java_ : version "1.7.0"
Java(TM) SE Runtime Environment (build 1.7.0-b147)
Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
Not completely sure what is your problem, but it would start with
updating JDK 7 to something more recent.
you are running u5, while latest is u67
_______________________________________________
wildfly-dev mailing list
wildfly-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/wildfly-dev
2:10 p.m.
Hi Jaikiran,
As you suggested I have picked up a JIRA from the list. I think that I can
work on this issue WFLY-694
<https://issues.jboss.org/browse/WFLY-694>.(multi-line
log output makes munging logs difficult).
For the jira description, I found out that
EjbJndiBindingsDeploymentUnitProcessor.java needs to be changed, which
lists the JNDI Bindings. The *logBinding* function appends a new line
character. I believe this hard-coded new line character needs to be
replaced with a configurable property.
Please let me know if this approach is correct, so that I can proceed to
find a suitable solution for the same.
Thanks,
Sandeep.
P.S. : I had posted the same on IRC, but I guess that my timing was not
right as not many developers were present at that moment.
On Thu, Oct 16, 2014 at 9:18 AM, Jaikiran Pai <jai.forums2013(a)gmail.com>
wrote:
Sandeep,
The WFLY JIRA has some issues which have been marked as "Awaiting for
volunteers". Here's a link to such unresolved issues
https://issues.jboss.org/issues/?jql=fixVersion%20%3D%20%22Awaiting%20Vol....
You can choose from one of them that interests you. You might want to hang
around in the #wildfly-dev channel on IRC (irc.freenode.net server) where
the WildFly developers can help you in getting started or working on the
issue that you pick.
-Jaikiran
On Tuesday 14 October 2014 06:08 PM, Sandeep Samdaria wrote:
Yup, that worked for me. In addition to updating the jdk from u5 to u67, I
also had to point JAVA_HOME to the latest.
I wanted to contribute to wildfly project. Any minor/trivial ticket
which I can take a look into it as a newbie?
-Sandeep.
On Tue, Oct 14, 2014 at 2:47 PM, Tomaž Cerar <tomaz.cerar(a)gmail.com>
wrote:
>
> On Tue, Oct 14, 2014 at 9:28 AM, Sandeep Samdaria <
> sandyridgeracer(a)gmail.com> wrote:
>
>> *Java* : version "1.7.0"
>> Java(TM) SE Runtime Environment (build 1.7.0-b147)
>> Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
>>
>
>
> Not completely sure what is your problem, but it would start with
> updating JDK 7 to something more recent.
> you are running u5, while latest is u67
>
_______________________________________________
wildfly-dev mailing
listwildfly-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/wildfly-dev
4:10 p.m.
The approach that should be taken is the one mentioned by David, about
adding support for a script consumable format that strips spaces to the
logmanager project.
We really don't want to just have some kind of configurable property to
control the delimiter. Putting this in the management model would be
massive overkill, and we don't generally go in for using random system
properties to control behaviour.
Also when this is desirable depends a lot on the logger that is being used.
If may be that the spaces are required for the console output and not
wanted for the file based logger.
Stuart
On Tue, Oct 21, 2014 at 6:10 AM, Sandeep Samdaria <sandyridgeracer(a)gmail.com
wrote:
> Hi Jaikiran,
> As you suggested I have picked up a JIRA from the list. I think that I can
> work on this issue WFLY-694
<https://issues.jboss.org/browse/WFLY-694>.(multi-line
> log output makes munging logs difficult).
>
> For the jira description, I found out that
> EjbJndiBindingsDeploymentUnitProcessor.java needs to be changed, which
> lists the JNDI Bindings. The *logBinding* function appends a new line
> character. I believe this hard-coded new line character needs to be
> replaced with a configurable property.
> Please let me know if this approach is correct, so that I can proceed to
> find a suitable solution for the same.
>
> Thanks,
> Sandeep.
>
> P.S. : I had posted the same on IRC, but I guess that my timing was not
> right as not many developers were present at that moment.
>
> On Thu, Oct 16, 2014 at 9:18 AM, Jaikiran Pai <jai.forums2013(a)gmail.com>
wrote:
>
>> Sandeep,
>>
>> The WFLY JIRA has some issues which have been marked as "Awaiting for
>> volunteers". Here's a link to such unresolved issues
>>
https://issues.jboss.org/issues/?jql=fixVersion%20%3D%20%22Awaiting%20Vol....
>> You can choose from one of them that interests you. You might want to hang
>> around in the #wildfly-dev channel on IRC (irc.freenode.net server)
>> where the WildFly developers can help you in getting started or working on
>> the issue that you pick.
>>
>> -Jaikiran
>>
>> On Tuesday 14 October 2014 06:08 PM, Sandeep Samdaria wrote:
>>
>> Yup, that worked for me. In addition to updating the jdk from u5 to u67,
>> I also had to point JAVA_HOME to the latest.
>>
>>
>> I wanted to contribute to wildfly project. Any minor/trivial ticket
>> which I can take a look into it as a newbie?
>>
>> -Sandeep.
>>
>> On Tue, Oct 14, 2014 at 2:47 PM, Tomaž Cerar <tomaz.cerar(a)gmail.com>
> wrote:
>>
>>>
>>> On Tue, Oct 14, 2014 at 9:28 AM, Sandeep Samdaria <
>>> sandyridgeracer(a)gmail.com wrote:
>>>
>>>> *Java* : version "1.7.0"
>>>> Java(TM) SE Runtime Environment (build 1.7.0-b147)
>>>> Java HotSpot(TM) 64-Bit Server VM (build 21.0-b17, mixed mode)
>>>>
>>>
>>>
>>> Not completely sure what is your problem, but it would start with
>>> updating JDK 7 to something more recent.
>>> you are running u5, while latest is u67
>>>
>>
>>
>>
>> _______________________________________________
>> wildfly-dev mailing
listwildfly-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/wildfly-dev
>>
>>
>>
>
> _______________________________________________
> wildfly-dev mailing list
> wildfly-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/wildfly-dev
>
3722
days inactive
3728
days old
5 comments
4 participants
participants (4)
-
Jaikiran Pai -
Sandeep Samdaria -
Stuart Douglas -
Tomaž Cerar