[JBoss JIRA] (JBIDE-27052) New Quarkus project wizard is not correctly rendered
by Oleksii Korniienko (Jira)
[ https://issues.redhat.com/browse/JBIDE-27052?page=com.atlassian.jira.plug... ]
Oleksii Korniienko closed JBIDE-27052.
--------------------------------------
Bug was fixed. Checked with:
CodeReady Studio
Version: 12.14.0.GA
Build id: GA-v20200225-1016-B5997
Build date: 20200225-1016
Java
openjdk version "1.8.0_232"
OpenJDK Runtime Environment (build 1.8.0_232-b09)
OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)
OS
RHEL 8.0
64-bit
GNOME
Version: 3.28.2
> New Quarkus project wizard is not correctly rendered
> -----------------------------------------------------
>
> Key: JBIDE-27052
> URL: https://issues.redhat.com/browse/JBIDE-27052
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: quarkus
> Affects Versions: 4.14.0.Final
> Reporter: Oleksii Korniienko
> Assignee: Stephane Bouchet
> Priority: Major
> Fix For: 4.14.0.Final
>
> Attachments: Screenshot from 2020-02-13 15-07-17.png
>
>
> Red Hat CodeReady Studio
> Version: 12.14.0.GA
> Build id: GA-v20200213-1019-B5905
> Build date: 20200213-1019
> Java
> openjdk version "1.8.0_232"
> OpenJDK Runtime Environment (build 1.8.0_232-b09)
> OpenJDK 64-Bit Server VM (build 25.232-b09, mixed mode)
> OS
> RHEL 8.0
> 64-bit
> GNOME
> Version: 3.28.2
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-27073) Set User-Agent when sending request to code.quarkus.io
by Jeff MAURY (Jira)
Jeff MAURY created JBIDE-27073:
----------------------------------
Summary: Set User-Agent when sending request to code.quarkus.io
Key: JBIDE-27073
URL: https://issues.redhat.com/browse/JBIDE-27073
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: quarkus
Affects Versions: 4.14.0.Final
Reporter: Jeff MAURY
Fix For: 4.15.0.AM1
code.quarkus.io expects user agent with a form like:
{code:java}
../.. (...;...;...)
{code}
so we should send something like:
{code:java}
product name/version (${System.getProperty("os.name")}; ${System.getProperty("os.version")}; ${System.getProperty("os.arch")}, Java ${System.getProperty("java.version")})
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-27072) Enable developer to use existing MW examples to create new application from IDE
by Parag Dave (Jira)
Parag Dave created JBIDE-27072:
----------------------------------
Summary: Enable developer to use existing MW examples to create new application from IDE
Key: JBIDE-27072
URL: https://issues.redhat.com/browse/JBIDE-27072
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Parag Dave
As a developer, I want to find Red Hat's curated example code and import it into my git repo so I can create a new application faster using the example as a starting point.
h3. Acceptance Criteria
* The following list of runtimes and examples will be available to the developer in their IDE.
* Example A, Example B
* Developer should have an easy way to find and import these runtimes and examples.
* Developers should be able to import these examples using IntelliJ, Eclipse, VS Code, Eclipse Che.
* Each runtime + example should have the appropriate metadata to enable developers to quickly find it in the IDE.
* An icon that represents the associated runtime should be displayed where applicable.
* Each runtime+example description should provide details about how to configure, build, test, run the runtimes and example applications. The description can be inline in the window or a clickable link to an external source.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-27072) Enable developer to use existing MW examples to create new application from IDE
by Parag Dave (Jira)
[ https://issues.redhat.com/browse/JBIDE-27072?page=com.atlassian.jira.plug... ]
Parag Dave resolved JBIDE-27072.
--------------------------------
Resolution: Duplicate
> Enable developer to use existing MW examples to create new application from IDE
> -------------------------------------------------------------------------------
>
> Key: JBIDE-27072
> URL: https://issues.redhat.com/browse/JBIDE-27072
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Parag Dave
> Priority: Major
> Labels: e2e
>
> As a developer, I want to find Red Hat's curated example code and import it into my git repo so I can create a new application faster using the example as a starting point.
> h3. Acceptance Criteria
> * The following list of runtimes and examples will be available to the developer in their IDE.
> * Example A, Example B
> * Developer should have an easy way to find and import these runtimes and examples.
> * Developers should be able to import these examples using IntelliJ, Eclipse, VS Code, Eclipse Che.
> * Each runtime + example should have the appropriate metadata to enable developers to quickly find it in the IDE.
> * An icon that represents the associated runtime should be displayed where applicable.
> * Each runtime+example description should provide details about how to configure, build, test, run the runtimes and example applications. The description can be inline in the window or a clickable link to an external source.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-27071) Enable developer to use existing MW examples to create new application from IDE
by Parag Dave (Jira)
[ https://issues.redhat.com/browse/JBIDE-27071?page=com.atlassian.jira.plug... ]
Parag Dave resolved JBIDE-27071.
--------------------------------
Resolution: Duplicate Issue
> Enable developer to use existing MW examples to create new application from IDE
> -------------------------------------------------------------------------------
>
> Key: JBIDE-27071
> URL: https://issues.redhat.com/browse/JBIDE-27071
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Reporter: Parag Dave
> Priority: Major
> Labels: e2e
>
> As a developer, I want to find Red Hat's curated example code and import it into my git repo so I can create a new application faster using the example as a starting point.
> h3. Acceptance Criteria
> * The following list of runtimes and examples will be available to the developer in their IDE.
> * Example A, Example B
> * Developer should have an easy way to find and import these runtimes and examples.
> * Developers should be able to import these examples using IntelliJ, Eclipse, VS Code, Eclipse Che.
> * Each runtime + example should have the appropriate metadata to enable developers to quickly find it in the IDE.
> * An icon that represents the associated runtime should be displayed where applicable.
> * Each runtime+example description should provide details about how to configure, build, test, run the runtimes and example applications. The description can be inline in the window or a clickable link to an external source.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-27071) Enable developer to use existing MW examples to create new application from IDE
by Tiffany Jacob (Jira)
[ https://issues.redhat.com/browse/JBIDE-27071?page=com.atlassian.jira.plug... ]
Tiffany Jacob updated JBIDE-27071:
----------------------------------
An error occurred whilst rendering this message. Please contact the administrators, and inform them of this bug.
Details:
-------
org.apache.velocity.exception.MethodInvocationException: Invocation of method 'printChangelog' in class com.atlassian.jira.util.JiraVelocityHelper threw exception com.atlassian.jira.issue.customfields.impl.FieldValidationException: Invalid priority name 'Urgent (not available)'. at templates/email/macros.vm[line 46, column 19]
at org.apache.velocity.runtime.parser.node.ASTMethod.handleInvocationException(ASTMethod.java:337)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:284)
at org.apache.velocity.runtime.parser.node.ASTReference.execute(ASTReference.java:262)
at org.apache.velocity.runtime.parser.node.ASTReference.render(ASTReference.java:342)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at org.apache.velocity.runtime.parser.node.ASTIfStatement.render(ASTIfStatement.java:87)
at org.apache.velocity.runtime.parser.node.ASTBlock.render(ASTBlock.java:72)
at org.apache.velocity.runtime.directive.VelocimacroProxy.render(VelocimacroProxy.java:212)
at org.apache.velocity.runtime.directive.RuntimeMacro.render(RuntimeMacro.java:247)
at org.apache.velocity.runtime.parser.node.ASTDirective.render(ASTDirective.java:175)
at org.apache.velocity.runtime.parser.node.SimpleNode.render(SimpleNode.java:336)
at org.apache.velocity.runtime.RuntimeInstance.render(RuntimeInstance.java:1276)
at org.apache.velocity.runtime.RuntimeInstance.evaluate(RuntimeInstance.java:1215)
at org.apache.velocity.runtime.RuntimeInstance.evaluate(RuntimeInstance.java:1164)
at org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:219)
at com.atlassian.velocity.DefaultVelocityManager.writeEncodedBodyForContent(DefaultVelocityManager.java:86)
at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest.toWriterImpl(DefaultVelocityTemplatingEngine.java:129)
at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest.asPlainText(DefaultVelocityTemplatingEngine.java:108)
at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest$1.with(DefaultVelocityTemplatingEngine.java:92)
at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest$StringRepresentation.toString(DefaultVelocityTemplatingEngine.java:77)
at com.atlassian.jira.template.velocity.DefaultVelocityTemplatingEngine$DefaultRenderRequest.asPlainText(DefaultVelocityTemplatingEngine.java:94)
at com.atlassian.jira.mail.builder.EmailRenderer.renderEmailBody(EmailRenderer.java:106)
at com.atlassian.jira.mail.builder.EmailRenderer.render(EmailRenderer.java:150)
at com.atlassian.jira.mail.builder.EmailBuilder.renderNow(EmailBuilder.java:155)
at com.atlassian.jira.mail.builder.EmailBuilder.renderNowAsQueueItem(EmailBuilder.java:145)
at com.atlassian.jira.mail.MailingListCompiler$1.evaluateEmailForRecipient(MailingListCompiler.java:336)
at com.atlassian.jira.mail.NotificationRecipientProcessor.evaluateEmails(NotificationRecipientProcessor.java:39)
at com.atlassian.jira.mail.MailingListCompiler.evaluateEmails(MailingListCompiler.java:267)
at com.atlassian.jira.mail.MailingListCompiler.access$300(MailingListCompiler.java:49)
at com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.lambda$addEmailsToQueue$0(MailingListCompiler.java:466)
at java.util.stream.ReferencePipeline$3$1.accept(ReferencePipeline.java:193)
at java.util.HashMap$EntrySpliterator.forEachRemaining(HashMap.java:1696)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.AbstractPipeline.wrapAndCopyInto(AbstractPipeline.java:471)
at java.util.stream.ReduceOps$ReduceOp.evaluateSequential(ReduceOps.java:708)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:234)
at java.util.stream.ReferencePipeline.collect(ReferencePipeline.java:499)
at com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.addEmailsToQueue(MailingListCompiler.java:468)
at com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendLists(MailingListCompiler.java:438)
at com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.sendNoLevelsIgnoreGroup(MailingListCompiler.java:414)
at com.atlassian.jira.mail.MailingListCompiler$NotificationCompiler.evaluateForAll(MailingListCompiler.java:410)
at com.atlassian.jira.mail.MailingListCompiler.prepareEmail(MailingListCompiler.java:170)
at com.atlassian.jira.mail.MailingListCompiler.sendLists(MailingListCompiler.java:101)
at com.atlassian.jira.mail.IssueMailQueueItem.send(IssueMailQueueItem.java:128)
at com.atlassian.mail.queue.MailQueueImpl.sendBufferUnderLock(MailQueueImpl.java:103)
at com.atlassian.mail.queue.MailQueueImpl.sendBuffer(MailQueueImpl.java:56)
at com.atlassian.jira.mail.JiraMailQueue$1.apply(JiraMailQueue.java:51)
at com.atlassian.jira.mail.JiraMailQueue$1.apply(JiraMailQueue.java:48)
at com.atlassian.jira.util.velocity.DefaultVelocityRequestContextFactory.runWithStaticBaseUrl(DefaultVelocityRequestContextFactory.java:110)
at com.atlassian.jira.util.DefaultBaseUrl.runWithStaticBaseUrl(DefaultBaseUrl.java:50)
at com.atlassian.jira.mail.JiraMailQueue.sendBuffer(JiraMailQueue.java:48)
at com.atlassian.jira.service.services.mail.MailQueueService.run(MailQueueService.java:21)
at com.atlassian.jira.service.JiraServiceContainerImpl.run(JiraServiceContainerImpl.java:68)
at com.atlassian.jira.service.ServiceRunner.runService(ServiceRunner.java:62)
at com.atlassian.jira.service.ServiceRunner.runServiceId(ServiceRunner.java:44)
at com.atlassian.jira.service.ServiceRunner.runJob(ServiceRunner.java:32)
at com.atlassian.scheduler.core.JobLauncher.runJob(JobLauncher.java:153)
at com.atlassian.scheduler.core.JobLauncher.launchAndBuildResponse(JobLauncher.java:118)
at com.atlassian.scheduler.core.JobLauncher.launch(JobLauncher.java:97)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.launchJob(CaesiumSchedulerService.java:443)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeLocalJob(CaesiumSchedulerService.java:410)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService.executeQueuedJob(CaesiumSchedulerService.java:388)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:285)
at com.atlassian.scheduler.caesium.impl.CaesiumSchedulerService$1.consume(CaesiumSchedulerService.java:282)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeJob(SchedulerQueueWorker.java:65)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.executeNextJob(SchedulerQueueWorker.java:59)
at com.atlassian.scheduler.caesium.impl.SchedulerQueueWorker.run(SchedulerQueueWorker.java:34)
at java.lang.Thread.run(Thread.java:748)
Caused by: com.atlassian.jira.issue.customfields.impl.FieldValidationException: Invalid priority name 'Urgent (not available)'.
at com.atlassian.jira.issue.fields.PrioritySystemField.getPriorityTypeIdByName(PrioritySystemField.java:218)
at com.atlassian.jira.issue.fields.PrioritySystemField.prettyPrintChangeHistory(PrioritySystemField.java:479)
at com.atlassian.jira.util.JiraVelocityHelper.getPrettyFieldString(JiraVelocityHelper.java:220)
at com.atlassian.jira.util.JiraVelocityHelper.printChangelog(JiraVelocityHelper.java:156)
at sun.reflect.GeneratedMethodAccessor3099.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.doInvoke(UberspectImpl.java:385)
at org.apache.velocity.util.introspection.UberspectImpl$VelMethodImpl.invoke(UberspectImpl.java:374)
at com.atlassian.velocity.htmlsafe.introspection.UnboxingMethod.invoke(UnboxingMethod.java:30)
at org.apache.velocity.runtime.parser.node.ASTMethod.execute(ASTMethod.java:270)
... 66 more
6 years, 1 month
[JBoss JIRA] (JBIDE-26582) Add support for Quarkus based applications
by Jeff MAURY (Jira)
[ https://issues.redhat.com/browse/JBIDE-26582?page=com.atlassian.jira.plug... ]
Jeff MAURY updated JBIDE-26582:
-------------------------------
Labels: e2e (was: )
> Add support for Quarkus based applications
> ------------------------------------------
>
> Key: JBIDE-26582
> URL: https://issues.redhat.com/browse/JBIDE-26582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Reporter: Jeff MAURY
> Priority: Major
> Labels: e2e
> Fix For: 4.14.0.Final
>
>
> We should support JBoss Tools based inner loop for Quarkus based applications.
> In the first time support only OpenJDK based deployments as I'm not sure native image based deployments can support inner loop.
> That would also probably means an update of the openJDK base image
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month
[JBoss JIRA] (JBIDE-26582) Add support for Quarkus based applications
by Tiffany Jacob (Jira)
[ https://issues.redhat.com/browse/JBIDE-26582?page=com.atlassian.jira.plug... ]
Tiffany Jacob commented on JBIDE-26582:
---------------------------------------
[~jeffmaury]would you mind adding an 'e2e' labels on this ticket, as this is being tracked as part of a runtime/gitops+ interlock, and we would like to filter on it.
> Add support for Quarkus based applications
> ------------------------------------------
>
> Key: JBIDE-26582
> URL: https://issues.redhat.com/browse/JBIDE-26582
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.11.0.Final
> Reporter: Jeff MAURY
> Priority: Major
> Fix For: 4.14.0.Final
>
>
> We should support JBoss Tools based inner loop for Quarkus based applications.
> In the first time support only OpenJDK based deployments as I'm not sure native image based deployments can support inner loop.
> That would also probably means an update of the openJDK base image
--
This message was sent by Atlassian Jira
(v7.13.8#713008)
6 years, 1 month