[JBoss JIRA] (JBIDE-25308) Cannot start CDK server adapter with different minishift home
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25308?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-25308.
---------------------------------
Itests CDKLaunchConfigurationTest added checking this (propagation of values from server editor into launch config) via UI.
Verified in devstudio 11.2.0.AM2-v20171207-1702-B1735. Closing.
> Cannot start CDK server adapter with different minishift home
> -------------------------------------------------------------
>
> Key: JBIDE-25308
> URL: https://issues.jboss.org/browse/JBIDE-25308
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.Final
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
> Labels: Regression
> Fix For: 4.5.2.AM1
>
>
> It is not possible to change minishift home path in CDK 3.2.+ server adapter's launch config. User is not capable of using MINISHIFT_HOME env. variable.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25192) Error when eclipse environment has MINISHIFT_HOME different from adapter
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25192?page=com.atlassian.jira.plugi... ]
Ondrej Dockal closed JBIDE-25192.
---------------------------------
Verified in devstudio 11.2.0.AM2-v20171207-1702-B1735. Closing.
> Error when eclipse environment has MINISHIFT_HOME different from adapter
> ------------------------------------------------------------------------
>
> Key: JBIDE-25192
> URL: https://issues.jboss.org/browse/JBIDE-25192
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.5.1.AM3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.5.1.Final
>
>
> Steps to reproduce:
> 1) Start eclipse with an environment that has a MINISHIFT_HOME set to one value
> 2) Create a server adapter with the default minishift home ~/.minishift (ie make no changes)
> 3) via cmdline, try to setup cdk using cdk 3.2a and the .minishift home folder
> 4) Try to start the server
> Expected results: Server starts as expected
> Actual results: No minishift_home is set. The eclipse environment's minishift home is used. The server attempts to start and tells you to call setup-cdk. The user gets very confused, because the server editor clearly is using ~/.minishift as the home.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25438) Refactor CDK itests to be more stable against CDK starts that fail sometimes
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25438?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25438:
----------------------------------
Fix Version/s: 4.5.2.AM3
(was: 4.5.2.AM2)
> Refactor CDK itests to be more stable against CDK starts that fail sometimes
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25438
> URL: https://issues.jboss.org/browse/JBIDE-25438
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.5.2.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.5.2.Final
>
>
> Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs.
> * repair discovery itests
> * finish adding of mocking cdk binaries in unsupported cdk versions
> * update suites to run faster test classes
> * remove deprecated test cases
> * think of skipping registration and adding one test case that will start cdk with registration
> * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations
> Issues to be addressed or incidents that cause fail of job run:
> * CDK-216
> * JBIDE-25443
> * https://status.redhat.com/incidents/s7tzh47440f5
> * JBIDE-25446
> * CDK-220 (cdk-3.3.0)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25438) Refactor CDK itests to be more stable against CDK starts that fail sometimes
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25438?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-25438:
----------------------------------
Fix Version/s: 4.5.2.Final
(was: 4.5.2.AM3)
> Refactor CDK itests to be more stable against CDK starts that fail sometimes
> ----------------------------------------------------------------------------
>
> Key: JBIDE-25438
> URL: https://issues.jboss.org/browse/JBIDE-25438
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.5.2.AM2
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.5.2.Final
>
>
> Refactor cdk itests to avoid starting cdk over and over again in each test case which will result in better performance and health of jenkins jobs.
> * repair discovery itests
> * finish adding of mocking cdk binaries in unsupported cdk versions
> * update suites to run faster test classes
> * remove deprecated test cases
> * think of skipping registration and adding one test case that will start cdk with registration
> * extends shellisavailable condition to accept other error dialogs as well ("Multiple problems have occured") during adapter operations
> Issues to be addressed or incidents that cause fail of job run:
> * CDK-216
> * JBIDE-25443
> * https://status.redhat.com/incidents/s7tzh47440f5
> * JBIDE-25446
> * CDK-220 (cdk-3.3.0)
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25441) Problems with CDI Builder and scanning Jars which support Java 9
by Iran Marcius (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25441?page=com.atlassian.jira.plugi... ]
Iran Marcius commented on JBIDE-25441:
--------------------------------------
About the workaround, I disabled CDI support on the project's properties page.
But if I have to reconfigure my project (Alt+F5) it's turned on again, wich is the expected behaviour I think.
Waiting for news.
> Problems with CDI Builder and scanning Jars which support Java 9
> ----------------------------------------------------------------
>
> Key: JBIDE-25441
> URL: https://issues.jboss.org/browse/JBIDE-25441
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, common
> Affects Versions: 4.5.1.Final, 4.5.2.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.5.x
>
>
> As reported in https://developer.jboss.org/message/978446?et=watches.email.thread#978446:
> {quote}
> Setup:
> * Eclipse Oxygen 4.7.1
> * JBoss Tools 4.5.1.Final (also tested with latest development version 4.5.2.AM1)
> * An maven web application with certain dependencies
> ** So far, we found two dependencies, which lead to this jandex scaning error after upgrading to latest version
> ** org.apache.logging.log4j version 2.10.0
> ** org.ow2.asm version 6.0
>
> This leads to an CDI Builder IllegalStateException - see exception trace below.
> Both dependencies started support for Java 9, which seems to cause this exception.
>
> *Apache Log4j 2.10.0 released*: http://mail-archives.apache.org/mod_mbox/www-announce/201711.mbox/%3Cdf95...
>
> {code}
> !MESSAGE Errors running builder 'CDI (Contexts and Dependency Injection) Builder' on project 'Webapp'.
> !STACK 0
> java.lang.IllegalStateException: Unknown tag! pos=4 poolCount = 24
> at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:665)
> at org.jboss.jandex.Indexer.index(Indexer.java:699)
> at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56)
> at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-25441) Problems with CDI Builder and scanning Jars which support Java 9
by Iran Marcius (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25441?page=com.atlassian.jira.plugi... ]
Iran Marcius commented on JBIDE-25441:
--------------------------------------
Is there any workaround for this?
I just reinstalled my entire eclise platform and started to import project by project. At the first project having CDI as dependency the error started to occur and I think it's the same.
I'm using the same eclipse and jboss tools as reported in this issue.
Errors occurred during the build.
Errors running builder 'CDI (Contexts and Dependency Injection) Builder' on project 'my.project'.
Unknown tag! pos=4 poolCount = 24
Thanks in advance.
> Problems with CDI Builder and scanning Jars which support Java 9
> ----------------------------------------------------------------
>
> Key: JBIDE-25441
> URL: https://issues.jboss.org/browse/JBIDE-25441
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi, common
> Affects Versions: 4.5.1.Final, 4.5.2.AM1
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Fix For: 4.5.x
>
>
> As reported in https://developer.jboss.org/message/978446?et=watches.email.thread#978446:
> {quote}
> Setup:
> * Eclipse Oxygen 4.7.1
> * JBoss Tools 4.5.1.Final (also tested with latest development version 4.5.2.AM1)
> * An maven web application with certain dependencies
> ** So far, we found two dependencies, which lead to this jandex scaning error after upgrading to latest version
> ** org.apache.logging.log4j version 2.10.0
> ** org.ow2.asm version 6.0
>
> This leads to an CDI Builder IllegalStateException - see exception trace below.
> Both dependencies started support for Java 9, which seems to cause this exception.
>
> *Apache Log4j 2.10.0 released*: http://mail-archives.apache.org/mod_mbox/www-announce/201711.mbox/%3Cdf95...
>
> {code}
> !MESSAGE Errors running builder 'CDI (Contexts and Dependency Injection) Builder' on project 'Webapp'.
> !STACK 0
> java.lang.IllegalStateException: Unknown tag! pos=4 poolCount = 24
> at org.jboss.jandex.Indexer.processConstantPool(Indexer.java:665)
> at org.jboss.jandex.Indexer.index(Indexer.java:699)
> at org.jboss.tools.common.core.jandex.JandexUtil.createJarIndex(JandexUtil.java:56)
> at org.jboss.tools.common.core.jandex.JandexUtil.hasAnnotation(JandexUtil.java:104)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.hasAnnotatedBeans(BeanArchiveDetector.java:276)
> at org.jboss.tools.cdi.internal.core.scanner.lib.BeanArchiveDetector.resolve(BeanArchiveDetector.java:203)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.detectBeanModule(ClassPathMonitor.java:150)
> at org.jboss.tools.cdi.internal.core.scanner.lib.ClassPathMonitor.process(ClassPathMonitor.java:106)
> at org.jboss.tools.cdi.core.CDICoreBuilder.build(CDICoreBuilder.java:215)
> at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:735)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:206)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:246)
> at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:301)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:304)
> at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:360)
> at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:383)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:142)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:232)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> {quote}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months
[JBoss JIRA] (JBIDE-18654) run jdeps on our jars to see how dependent we are on api that might go away in Java 9
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18654?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18654:
------------------------------------
{quote}there is a Maven plugin for that{quote}
Yes: https://maven.apache.org/plugins/maven-jdeps-plugin/
So, I've added a jdeps profile to the parent pom for version 4.5.2.AM3-SNAPSHOT.
https://github.com/jbosstools/jbosstools-build/commit/4821b55ddc14247a525...
Now, you can build any jbosstools-* project like this...
1. Create a toolchains.xml file that looks like this, ideally in your ~/.m2 folder:
{code}<?xml version="1.0" encoding="UTF8"?>
<toolchains>
<toolchain>
<type>jdk</type>
<provides>
<version>1.8</version>
<vendor>openjdk</vendor>
</provides>
<configuration>
<jdkHome>/usr/lib/jvm/java-1.8.0-openjdk/</jdkHome>
</configuration>
</toolchain>
<toolchain>
<type>jdk</type>
<provides>
<version>9</version>
<vendor>openjdk</vendor>
</provides>
<configuration>
<jdkHome>/usr/lib/jvm/java-9-openjdk/</jdkHome>
</configuration>
</toolchain>
</toolchains>{code}
2. Update to latest parent pom:
{code}
cd /path/to/jbosstools-openshift
sed -i -e "s/4.5.2.AM1-SNAPSHOT/4.5.2.AM3-SNAPSHOT/" pom.xml # grab parent pom 4.5.2.AM3-SNAPSHOT
{code}
3. Run
{code}
mvn clean install -Pjdeps -Djdeps-jdk-version=1.8 -Djdeps-jdk-vendor=openjdk --global-toolchains ~/.m2/toolchains.xml
# or
mvn clean install -Pjdeps -Djdeps-jdk-version=9 -Djdeps-jdk-vendor=openjdk --global-toolchains ~/.m2/toolchains.xml
{code}
We could also set up Jenkins jobs to do these checks, if we wanted.
WDYT, [~mmalina] [~psrna] [~jeffmaury] [~rob.stryker]
> run jdeps on our jars to see how dependent we are on api that might go away in Java 9
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-18654
> URL: https://issues.jboss.org/browse/JBIDE-18654
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.2.0.Final
> Reporter: Max Rydahl Andersen
> Assignee: Jeff MAURY
> Fix For: 4.3.x, 4.5.2.Final
>
>
> Java 9 JDK team have been pinging various teams to check if they got depedency on API that is scheduled to disappear in Java 9.
> There is a tool called jdeps that we can use to check for this using the -jdkinternals flag.
> https://wiki.openjdk.java.net/display/JDK8/Java+Dependency+Analysis+Tool
> The sooner the better we get this done as it is feedback to the Java 9 team.
> If we can we should try run it on *all* jars, even eclipse ones to see what will be affected - but first of all jboss tools plugins.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 3 months