[JBoss JIRA] (JBIDE-13275) SSH Keys wizard: colum with key content has wrong title, should "Content", shows "Title"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13275?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13275:
-------------------------------------
Attachment: wrong-ssh-keys-columng.png
> SSH Keys wizard: colum with key content has wrong title, should "Content", shows "Title"
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-13275
> URL: https://issues.jboss.org/browse/JBIDE-13275
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.0.0.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.1.x, 4.0.x
>
> Attachments: wrong-ssh-keys-columng.png
>
>
> In the SSH keys wizard, where the user can manage it's SSH keys on openshift, we're listing the keys that are already added to the platform. We're providing details and show the key name in the column "Name", the key type in the column "Type" and we're also showing the key content. This very last column is called "Type" where it should be called "Content"
> !wrong-ssh-keys-columng.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13275) SSH Keys wizard: colum with key content has wrong title, should "Content", shows "Title"
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-13275:
----------------------------------------
Summary: SSH Keys wizard: colum with key content has wrong title, should "Content", shows "Title"
Key: JBIDE-13275
URL: https://issues.jboss.org/browse/JBIDE-13275
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.0.0.Final
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.x, 4.0.x
In the SSH keys wizard, where the user can manage it's SSH keys on openshift, we're listing the keys that are already added to the platform. We're providing details and show the key name in the column "Name", the key type in the column "Type" and we're also showing the key content. This very last column is called "Type" where it should be called "Content"
!wrong-ssh-keys-columng.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13059) test the RichFaces Kitchensink archetype upgrade
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13059?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-13059:
-------------------------------------
[~rhopp]: can you please try {quote}-Dorg.jboss.examples.stacks.url==https://github.com/fbricon/jdf-stack/blob/7b8c1d6e0a3752385b2eccbc7f16c5484c3cbcfc/stacks.yaml{quote}? Looked good to me on my initial test, but I'd rather have JBT QA actually vet the new archetype.
> test the RichFaces Kitchensink archetype upgrade
> ------------------------------------------------
>
> Key: JBIDE-13059
> URL: https://issues.jboss.org/browse/JBIDE-13059
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: central
> Affects Versions: 4.0.0.Beta1
> Reporter: Brian Leathem
> Assignee: Fred Bricon
> Priority: Critical
> Labels: exampleswarnings
> Fix For: 4.0.0.Final
>
> Attachments: richfaces.png, richfaces1.png
>
>
> RichFaces kitchensink archetype 4.2.3.Final-1 is currently in a JBoss staging repository.
> The archetype will be promoted out of staging when JBoss tools QA is complete.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13249) Improve MDB support
by Hiram Chirino (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13249?page=com.atlassian.jira.plugi... ]
Hiram Chirino commented on JBIDE-13249:
---------------------------------------
+1 for anything that helps end users properly wire up their MDBs.
> Improve MDB support
> -------------------
>
> Key: JBIDE-13249
> URL: https://issues.jboss.org/browse/JBIDE-13249
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: ejb3
> Reporter: Clebert Suconic
> Assignee: Rob Stryker
>
> I have recently tried creating an MDB and it seems out of date.
> It's not adding any annotations and not asking the user for any parameters.
> You could do something like this:
> - Ask what provider is going to be used...
> Ask what's the queue name to be used
> What Resource Adapter's name. (It would be great if you could inspect the server being used here for the RA's names. Each hornetq pooled connection factory will be a resource adapter name BTW).
> What Queue Name
> you could also provide additional activation properties by either selecting a list of providers. Or even better you could inspect the list of available activation properties, so it would be more generic.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13237) Use "suggested-value" from faces-config.xml for JSF attribute suggestion
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13237?page=com.atlassian.jira.plugi... ]
Lukáš Fryč commented on JBIDE-13237:
------------------------------------
We have discussed format of the {{suggested-value}} and it seems it should likely be comma-separated list of string values.
Make sure to do not validate against the list of suggested values - actual options does not have to be bound by this list.
> Use "suggested-value" from faces-config.xml for JSF attribute suggestion
> ------------------------------------------------------------------------
>
> Key: JBIDE-13237
> URL: https://issues.jboss.org/browse/JBIDE-13237
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JSF
> Reporter: Paul Dijou
> Assignee: Viacheslav Kabanovich
> Labels: new_and_noteworthy
> Fix For: 4.1.0.Alpha1
>
>
> After reading [this wiki entry|https://community.jboss.org/wiki/NewKBPlug-inAndCodeAssistInJBossTo...], it looks like one property of the faces-config.xml isn't used so far, it's the *"suggested-value"* (see http://horstmann.com/corejsf/faces-config.html#suggested-value ). Its description is quite small and I couldn't find any real documentation about it. But we can read: "This value is advisory only and is intended for tools", and JBoss Tools is... a tool, right? :-)
> So it would be great that JBoss Tools check the presence of such a "suggested-value" inside faces-config.xml and population an "enumeration" proposal type for the corresponding attribute.
> Since "suggested-value" is a string, it cannot support natively a list of suggestions, so, right now, RichFaces is using "," as a separator. Which mean having:
> {code}
> <property-name>severity</property-name>
> <property-class>java.lang.String</property-class>
> <suggested-value>success,info,warning,important,inverse</suggested-value>
> {code}
> Should be equivalent to:
> {code}
> <attribute name="severity">
> <proposal type="enumeration">
> <param value="success" />
> <param value="info" />
> <param value="warning" />
> <param value="important" />
> <param value="inverse" />
> </proposal>
> </attribute>
> {code}
> What do you think?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13198) BrowserSim incorrect behaviour on Mac OS
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13198?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-13198:
------------------------------------------------
It is a surprise for me, but it looks like that fix for this issue is included in PR for JBIDE-10554. So, this issue will be resolved when PR will be applied.
> BrowserSim incorrect behaviour on Mac OS
> ----------------------------------------
>
> Key: JBIDE-13198
> URL: https://issues.jboss.org/browse/JBIDE-13198
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Environment: Mac OS
> Reporter: Konstantin Marmalyukov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.1.0.Alpha1
>
>
> Precondition:
> Open at least two windows(open in new window action).
> Condition:
> When we make right-click on inactive browsersim window, on Windows and Ubuntu this window activates. The same does not happens on Mac OS.
> Because of that when we close inactive window, active window closes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13273) Cannot deploy EAR project to AS5.1/EAP5.1
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13273?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-13273:
---------------------------------------
Oh, right, that will probably be it. It could have occurred to me...
Eclipse always selects Java 7 for everything by default. So in order to be able to start EAP5 I always change the runtime to use Java 6. But I didn't change the jdk for projects - my bad.
I set the compiler settings to use java 1.6 and now it works.
Thanks, Snjezana!
> Cannot deploy EAR project to AS5.1/EAP5.1
> -----------------------------------------
>
> Key: JBIDE-13273
> URL: https://issues.jboss.org/browse/JBIDE-13273
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: JBoss AS 5.1.0.GA
> JBoss EAP 5.1.2
> JBDS 6.0.0.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> The default ear project cannot be deployed on EAP5/AS5.
> {code}
> 15:54:54,610 INFO [ServerImpl] JBoss (Microcontainer) [5.1.2 (build: SVNTag=JBPAPP_5_1_2 date=201111102209)] Started in 18s:223ms
> 15:55:16,929 WARN [ClassLoaderManager] Unexpected error during load of:Main
> java.lang.UnsupportedClassVersionError: Main : Unsupported major.minor version 51.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:67)
> at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:633)
> at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:592)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:591)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:568)
> at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:135)
> at org.jboss.classloader.spi.filter.FilteredDelegateLoader.loadClass(FilteredDelegateLoader.java:131)
> at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:455)
> at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:267)
> at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:166)
> at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:287)
> at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1163)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:862)
> at org.jboss.classloader.spi.base.BaseClassLoader.doLoadClass(BaseClassLoader.java:502)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:447)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at org.jboss.deployment.OptAnnotationMetaDataDeployer.processJBossClientMetaData(OptAnnotationMetaDataDeployer.java:130)
> at org.jboss.deployment.OptAnnotationMetaDataDeployer.processMetaData(OptAnnotationMetaDataDeployer.java:82)
> at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:206)
> at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:122)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1225)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> 15:55:16,931 ERROR [AbstractKernelController] Error installing to PostClassLoader: name=vfsfile:/Users/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/earproj.ear/ state=ClassLoader mode=Manual requiredState=PostClassLoader
> org.jboss.deployers.spi.DeploymentException: Cannot process metadata
> at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
> at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:210)
> at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:122)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1225)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.ClassNotFoundException: Unexpected error during load of: Main, msg=Main : Unsupported major.minor version 51.0
> at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:181)
> at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:287)
> at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1163)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:862)
> at org.jboss.classloader.spi.base.BaseClassLoader.doLoadClass(BaseClassLoader.java:502)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:447)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at org.jboss.deployment.OptAnnotationMetaDataDeployer.processJBossClientMetaData(OptAnnotationMetaDataDeployer.java:130)
> at org.jboss.deployment.OptAnnotationMetaDataDeployer.processMetaData(OptAnnotationMetaDataDeployer.java:82)
> at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:206)
> ... 27 more
> Caused by: java.lang.UnsupportedClassVersionError: Main : Unsupported major.minor version 51.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:67)
> at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:633)
> at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:592)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:591)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:568)
> at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:135)
> at org.jboss.classloader.spi.filter.FilteredDelegateLoader.loadClass(FilteredDelegateLoader.java:131)
> at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:455)
> at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:267)
> at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:166)
> ... 36 more
> 15:55:16,937 WARN [HDScanner] Failed to process changes
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/Users/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/earproj.ear/ -> org.jboss.deployers.spi.DeploymentException: Cannot process metadata
> DEPLOYMENTS IN ERROR:
> Deployment "vfsfile:/Users/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/earproj.ear/" is in error due to the following reason(s): java.lang.UnsupportedClassVersionError: Main : Unsupported major.minor version 51.0
> at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1008)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:954)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:870)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:416)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13273) Cannot deploy EAR project to AS5.1/EAP5.1
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13273?page=com.atlassian.jira.plugi... ]
Martin Malina resolved JBIDE-13273.
-----------------------------------
Resolution: Rejected
Compiled with java 1.7 and deployed on a server running on java 1.6 - not a bug.
> Cannot deploy EAR project to AS5.1/EAP5.1
> -----------------------------------------
>
> Key: JBIDE-13273
> URL: https://issues.jboss.org/browse/JBIDE-13273
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Affects Versions: 4.0.0.Final
> Environment: JBoss AS 5.1.0.GA
> JBoss EAP 5.1.2
> JBDS 6.0.0.GA
> Reporter: Martin Malina
> Assignee: Rob Stryker
>
> The default ear project cannot be deployed on EAP5/AS5.
> {code}
> 15:54:54,610 INFO [ServerImpl] JBoss (Microcontainer) [5.1.2 (build: SVNTag=JBPAPP_5_1_2 date=201111102209)] Started in 18s:223ms
> 15:55:16,929 WARN [ClassLoaderManager] Unexpected error during load of:Main
> java.lang.UnsupportedClassVersionError: Main : Unsupported major.minor version 51.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:67)
> at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:633)
> at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:592)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:591)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:568)
> at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:135)
> at org.jboss.classloader.spi.filter.FilteredDelegateLoader.loadClass(FilteredDelegateLoader.java:131)
> at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:455)
> at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:267)
> at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:166)
> at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:287)
> at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1163)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:862)
> at org.jboss.classloader.spi.base.BaseClassLoader.doLoadClass(BaseClassLoader.java:502)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:447)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at org.jboss.deployment.OptAnnotationMetaDataDeployer.processJBossClientMetaData(OptAnnotationMetaDataDeployer.java:130)
> at org.jboss.deployment.OptAnnotationMetaDataDeployer.processMetaData(OptAnnotationMetaDataDeployer.java:82)
> at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:206)
> at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:122)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1225)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> 15:55:16,931 ERROR [AbstractKernelController] Error installing to PostClassLoader: name=vfsfile:/Users/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/earproj.ear/ state=ClassLoader mode=Manual requiredState=PostClassLoader
> org.jboss.deployers.spi.DeploymentException: Cannot process metadata
> at org.jboss.deployers.spi.DeploymentException.rethrowAsDeploymentException(DeploymentException.java:49)
> at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:210)
> at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:122)
> at org.jboss.deployers.plugins.deployers.DeployerWrapper.deploy(DeployerWrapper.java:179)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doDeploy(DeployersImpl.java:1454)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1172)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.doInstallParentFirst(DeployersImpl.java:1225)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.install(DeployersImpl.java:1113)
> at org.jboss.dependency.plugins.AbstractControllerContext.install(AbstractControllerContext.java:348)
> at org.jboss.dependency.plugins.AbstractController.install(AbstractController.java:1652)
> at org.jboss.dependency.plugins.AbstractController.incrementState(AbstractController.java:938)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:1082)
> at org.jboss.dependency.plugins.AbstractController.resolveContexts(AbstractController.java:988)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:826)
> at org.jboss.dependency.plugins.AbstractController.change(AbstractController.java:556)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.process(DeployersImpl.java:789)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.process(MainDeployerImpl.java:699)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.process(MainDeployerAdapter.java:117)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:409)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> Caused by: java.lang.ClassNotFoundException: Unexpected error during load of: Main, msg=Main : Unsupported major.minor version 51.0
> at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:181)
> at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:287)
> at org.jboss.classloader.spi.base.BaseClassLoaderDomain.loadClass(BaseClassLoaderDomain.java:1163)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassFromDomain(BaseClassLoader.java:862)
> at org.jboss.classloader.spi.base.BaseClassLoader.doLoadClass(BaseClassLoader.java:502)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClass(BaseClassLoader.java:447)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
> at org.jboss.deployment.OptAnnotationMetaDataDeployer.processJBossClientMetaData(OptAnnotationMetaDataDeployer.java:130)
> at org.jboss.deployment.OptAnnotationMetaDataDeployer.processMetaData(OptAnnotationMetaDataDeployer.java:82)
> at org.jboss.deployment.AnnotationMetaDataDeployer.deploy(AnnotationMetaDataDeployer.java:206)
> ... 27 more
> Caused by: java.lang.UnsupportedClassVersionError: Main : Unsupported major.minor version 51.0
> at java.lang.ClassLoader.defineClass1(Native Method)
> at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:615)
> at org.jboss.classloader.spi.base.BaseClassLoader.access$200(BaseClassLoader.java:67)
> at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:633)
> at org.jboss.classloader.spi.base.BaseClassLoader$2.run(BaseClassLoader.java:592)
> at java.security.AccessController.doPrivileged(Native Method)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:591)
> at org.jboss.classloader.spi.base.BaseClassLoader.loadClassLocally(BaseClassLoader.java:568)
> at org.jboss.classloader.spi.base.BaseDelegateLoader.loadClass(BaseDelegateLoader.java:135)
> at org.jboss.classloader.spi.filter.FilteredDelegateLoader.loadClass(FilteredDelegateLoader.java:131)
> at org.jboss.classloader.spi.base.ClassLoadingTask$ThreadTask.run(ClassLoadingTask.java:455)
> at org.jboss.classloader.spi.base.ClassLoaderManager.nextTask(ClassLoaderManager.java:267)
> at org.jboss.classloader.spi.base.ClassLoaderManager.process(ClassLoaderManager.java:166)
> ... 36 more
> 15:55:16,937 WARN [HDScanner] Failed to process changes
> org.jboss.deployers.client.spi.IncompleteDeploymentException: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
> *** DEPLOYMENTS IN ERROR: Name -> Error
> vfsfile:/Users/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/earproj.ear/ -> org.jboss.deployers.spi.DeploymentException: Cannot process metadata
> DEPLOYMENTS IN ERROR:
> Deployment "vfsfile:/Users/rasp/jbossqa/runtimes/jboss-eap-5.1.2/jboss-as/server/default/deploy/earproj.ear/" is in error due to the following reason(s): java.lang.UnsupportedClassVersionError: Main : Unsupported major.minor version 51.0
> at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:1008)
> at org.jboss.deployers.plugins.deployers.DeployersImpl.checkComplete(DeployersImpl.java:954)
> at org.jboss.deployers.plugins.main.MainDeployerImpl.checkComplete(MainDeployerImpl.java:870)
> at org.jboss.system.server.profileservice.repository.MainDeployerAdapter.checkComplete(MainDeployerAdapter.java:128)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.scan(HDScanner.java:416)
> at org.jboss.system.server.profileservice.hotdeploy.HDScanner.run(HDScanner.java:294)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:439)
> at java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:317)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:150)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$101(ScheduledThreadPoolExecutor.java:98)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.runPeriodic(ScheduledThreadPoolExecutor.java:180)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:204)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> at java.lang.Thread.run(Thread.java:680)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months