[JBoss JIRA] (JBDS-4763) Rename installer devstudio binary files name to CodeReadyStudio
by Ondrej Dockal (Jira)
[ https://issues.jboss.org/browse/JBDS-4763?page=com.atlassian.jira.plugin.... ]
Ondrej Dockal edited comment on JBDS-4763 at 3/11/19 8:30 AM:
--------------------------------------------------------------
[~nickboldt] I am not saying we have to, but I am rather naming places we should consider as well.
Ah, ok, I guess we can use either of them. I thought it was decided already.
was (Author: odockal):
[~nickboldt] I am not saying we have to, but rather naming places we should consider as well.
Ah, ok, I guess we can use either of them. I thought it was decided already.
> Rename installer devstudio binary files name to CodeReadyStudio
> ---------------------------------------------------------------
>
> Key: JBDS-4763
> URL: https://issues.jboss.org/browse/JBDS-4763
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: install-tests, installer, updatesite
> Affects Versions: 12.11.0.AM1
> Reporter: Ondrej Dockal
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 12.11.0.GA
>
>
> As mentioned on 5x5 meetings, please rename binary files of developer studio installer to new branded CodeReady Studio. I am not sure about proper naming, probably codereadystudio or crstudio? As [~nickboldt] mentioned in linked jira, should be crstudio.
> Also, how about other places that contains old branded name?
> * market place entry - https://marketplace.eclipse.org/content/red-hat-developer-studio
> * download server - https://devstudio.redhat.com/12/
> * binary files - https://devstudio.redhat.com/12/snapshots/builds/devstudio.product_master...
> * devstudio occurencies on developers.redhat.com - https://developers.redhat.com/products/devstudio/overview
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBIDE-26571) Java 11: An internal error occurred during: "Identify jrt-fs.jar".
by Emond Papegaaij (Jira)
Emond Papegaaij created JBIDE-26571:
---------------------------------------
Summary: Java 11: An internal error occurred during: "Identify jrt-fs.jar".
Key: JBIDE-26571
URL: https://issues.jboss.org/browse/JBIDE-26571
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Environment: eclipse.buildId=4.10.0.I20181206-0815
java.version=11.0.1
java.vendor=Oracle Corporation
BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_GB
Framework arguments: -product org.eclipse.epp.package.java.product
Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.java.product
Reporter: Emond Papegaaij
When running Eclipse with Java 11, I keep getting the following error: An internal error occurred during: "Identify jrt-fs.jar". This happens when trying to open a class from the JRE in the editor. Looking at the stacktrace, this seems to originate from the JBoss Tools Maven Source Lookup. I'm using version 1.9.2.v20181211-1326.
{code}
java.lang.NoClassDefFoundError: javax/xml/bind/JAXBContext
at org.jboss.tools.maven.core.internal.identification.NexusRepositoryIdentifier.searchArtifactFromRemoteNexusRepository(NexusRepositoryIdentifier.java:96)
at org.jboss.tools.maven.core.internal.identification.NexusRepositoryIdentifier.getArtifactFromRemoteNexusRepository(NexusRepositoryIdentifier.java:78)
at org.jboss.tools.maven.core.internal.identification.NexusRepositoryIdentifier.identify(NexusRepositoryIdentifier.java:50)
at org.jboss.tools.maven.core.internal.identification.FileIdentificationManager.identify(FileIdentificationManager.java:91)
at org.jboss.tools.maven.sourcelookup.ui.actions.AttachSourcesActionDelegate$1.run(AttachSourcesActionDelegate.java:114)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:63)
{code}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBIDE-26570) WildFly 15 and 16 do not allow JEE8 deployments
by Emond Papegaaij (Jira)
Emond Papegaaij created JBIDE-26570:
---------------------------------------
Summary: WildFly 15 and 16 do not allow JEE8 deployments
Key: JBIDE-26570
URL: https://issues.jboss.org/browse/JBIDE-26570
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Reporter: Emond Papegaaij
This issue seems to be the same as I reported before for WildFly 14: JBIDE-26390. I'm getting the same error trying to deploy a JEE8 ear on WildFly 15 and 16. My version of JBoss AS, WildFly & EAP Server Tools is 3.6.2.v20190304-1841.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years
[JBoss JIRA] (JBIDE-26565) Update 4.11.0.Final TP
by Jeff MAURY (Jira)
[ https://issues.jboss.org/browse/JBIDE-26565?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-26565:
------------------------------------
* SimRel 2019-03RC1
* Orbit R20190226160451
* m2e-apt 1.5.1
* mylyn-github 5.3.0
* DTP 1.14.104.201903081442
* tm 4.5.100.201901312305
* Jetty 9.4.15
* Docker 4.3.0.201903062211
* SWTBot 2.7.0
* TestNG 6.14.3
* SpringIDE 3.9.7
> Update 4.11.0.Final TP
> ----------------------
>
> Key: JBIDE-26565
> URL: https://issues.jboss.org/browse/JBIDE-26565
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: target-platform
> Affects Versions: 4.11.0.AM1
> Reporter: Jeff MAURY
> Assignee: Jeff MAURY
> Priority: Major
> Fix For: 4.11.0.Final
>
> Attachments: p2diff.txt, p2diff_log_jbosstools_2019-03-08_06-47.txt
>
>
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years