[JBoss JIRA] (JBIDE-23386) add code freeze notification to staging build email notification template
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23386?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-23386.
--------------------------------
Closing this issue. This change will be verified during next code freeze.
> add code freeze notification to staging build email notification template
> -------------------------------------------------------------------------
>
> Key: JBIDE-23386
> URL: https://issues.jboss.org/browse/JBIDE-23386
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.2.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.AM3
>
>
> So that devs know when code freeze is in effect, we need to add a reminder to the '...is available for QE testing' emails so that:
> * for master branch / AMx builds, code freeze is in effect until QE signoff on Tues/Wed after the build is available
> * for 4.a.x (or 4.a.b.x) branches / GA builds, code freeze applies only to the 4.a.x branch, not to master. master is wide open for new dev as soon as the branch is created
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4146) Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4146?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4146:
----------------------------------
So... AERI submissions [1] still work when devstudio is installed via RPM - but on my most recent start of Eclipse I didn't see the above error.
[1] https://aer.ctrlflow.com/redhat/reporters/#!/submissions/2Pw9Nv3iAkLhJC4m...
> Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4146
> URL: https://issues.jboss.org/browse/JBDS-4146
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, rpm, webservices
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Jeff MAURY
> Priority: Blocker
> Fix For: 10.2.0.AM3
>
> Attachments: rh-eclipse46-devstudio10.2.log.20161102-1855.txt
>
>
> As of the latest rpm build [1] I'm only getting this one error now:
> {code}!ENTRY org.eclipse.epp.logging.aeri.ide 2 10 2016-10-28 14:32:25.075
> !MESSAGE Updating the index from remote ‘https://aer.ctrlflow.com/downloads/redhat/problems.zip’ failed with exception: org.apache.lucene.index.IndexFormatTooOldException: Format version is not supported (resource BufferedChecksumIndexInput(MMapIndexInput(path="/tmp/1477679545041-0/segments_1"))): -11 (needs to be between 1071082519 and 1071082519). This version of Lucene only supports indexes created with release 4.0 and later. ; version: 2.0.3.201610111629
> !STACK 0
> org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException
> at org.eclipse.epp.logging.aeri.core.util.Logs$LogTraceException.newTrace(Logs.java:387)
> at org.eclipse.epp.logging.aeri.core.util.Logs.log(Logs.java:134)
> at org.eclipse.epp.internal.logging.aeri.ide.server.mars.ServerProblemsHistory$UpdateIndexJob.run(ServerProblemsHistory.java:322)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4158) batch.ui.hyperlink.BatchPropertyHyperlinkDetector :: java.lang.NoClassDefFoundError: org/eclipse/jdt/core/JavaModelException
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4158?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4158:
---------------------------------
Fix Version/s: 10.2.0.AM3
> batch.ui.hyperlink.BatchPropertyHyperlinkDetector :: java.lang.NoClassDefFoundError: org/eclipse/jdt/core/JavaModelException
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4158
> URL: https://issues.jboss.org/browse/JBDS-4158
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: batch, rpm
> Affects Versions: 10.2.0.AM3
> Environment: Installed rpm:
> {code}
> Installed Packages
> Name : rh-eclipse46-devstudio
> Arch : x86_64
> Epoch : 0
> Version : 10.2
> Release : 0.20161102.2255.el7
> {code}
> {code}
> $➔ uname -a && java -version
> Linux t540p-f24-vm01 4.8.4-200.fc24.x86_64 #1 SMP Tue Oct 25 13:06:04 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> {code}
> {code}
> openjdk version "1.8.0_65"
> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> {code}
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 10.2.0.AM3
>
> Attachments: batch.ui.hyperlink.error.txt, batch.ui.hyperlink.png
>
>
> Whenever I click on text in a .java file editor in Eclipse, I get this error thrown:
> !batch.ui.hyperlink.png|thumbnail!
> [^batch.ui.hyperlink.error.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4158) batch.ui.hyperlink.BatchPropertyHyperlinkDetector :: java.lang.NoClassDefFoundError: org/eclipse/jdt/core/JavaModelException
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4158?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-4158:
--------------------------------------
Looks like Eclipse sapphire can't access JDT bundles. Wondering if they are using classloaders directly to load bundles somewhere in their code... So it might be a similar problem to BrowserSim and Maven.
> batch.ui.hyperlink.BatchPropertyHyperlinkDetector :: java.lang.NoClassDefFoundError: org/eclipse/jdt/core/JavaModelException
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4158
> URL: https://issues.jboss.org/browse/JBDS-4158
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: batch, rpm
> Affects Versions: 10.2.0.AM3
> Environment: Installed rpm:
> {code}
> Installed Packages
> Name : rh-eclipse46-devstudio
> Arch : x86_64
> Epoch : 0
> Version : 10.2
> Release : 0.20161102.2255.el7
> {code}
> {code}
> $➔ uname -a && java -version
> Linux t540p-f24-vm01 4.8.4-200.fc24.x86_64 #1 SMP Tue Oct 25 13:06:04 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> {code}
> {code}
> openjdk version "1.8.0_65"
> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> {code}
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Fix For: 10.2.0.AM3
>
> Attachments: batch.ui.hyperlink.error.txt, batch.ui.hyperlink.png
>
>
> Whenever I click on text in a .java file editor in Eclipse, I get this error thrown:
> !batch.ui.hyperlink.png|thumbnail!
> [^batch.ui.hyperlink.error.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4158) batch.ui.hyperlink.BatchPropertyHyperlinkDetector :: java.lang.NoClassDefFoundError: org/eclipse/jdt/core/JavaModelException
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-4158?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-4158:
---------------------------------
Priority: Critical (was: Major)
> batch.ui.hyperlink.BatchPropertyHyperlinkDetector :: java.lang.NoClassDefFoundError: org/eclipse/jdt/core/JavaModelException
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-4158
> URL: https://issues.jboss.org/browse/JBDS-4158
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: batch, rpm
> Affects Versions: 10.2.0.AM3
> Environment: Installed rpm:
> {code}
> Installed Packages
> Name : rh-eclipse46-devstudio
> Arch : x86_64
> Epoch : 0
> Version : 10.2
> Release : 0.20161102.2255.el7
> {code}
> {code}
> $➔ uname -a && java -version
> Linux t540p-f24-vm01 4.8.4-200.fc24.x86_64 #1 SMP Tue Oct 25 13:06:04 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
> {code}
> {code}
> openjdk version "1.8.0_65"
> OpenJDK Runtime Environment (build 1.8.0_65-b17)
> OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode)
> {code}
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Critical
> Fix For: 10.2.0.AM3
>
> Attachments: batch.ui.hyperlink.error.txt, batch.ui.hyperlink.png
>
>
> Whenever I click on text in a .java file editor in Eclipse, I get this error thrown:
> !batch.ui.hyperlink.png|thumbnail!
> [^batch.ui.hyperlink.error.txt]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBDS-4136) Uses constraint violation - org.slf4j.api vs. slf4j.api
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4136?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4136.
------------------------------
Verified in 10.2.0.AM3 (10.2-0.20161103.0904.el7.x86_64). The error mentioned in description is not longer in the log.
> Uses constraint violation - org.slf4j.api vs. slf4j.api
> -------------------------------------------------------
>
> Key: JBDS-4136
> URL: https://issues.jboss.org/browse/JBDS-4136
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: build, maven, rpm, target-platform
> Affects Versions: 10.2.0.AM2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM3
>
> Attachments: ds4610AM1.p2diff.txt, enabled-sites-wtp-update.png, jbt4602AM1.p2diff.txt, new-m2e.egit.png
>
>
> Latest bit of rpm madness...
> This conflict occurred:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931]
> Bundle was not resolved because of a uses contraint violation.
> org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"] because it is exposed to package 'org.slf4j' from resources org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"] and slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"] via two dependency chains.
> Chain 1:
> org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"]
> require: (osgi.wiring.bundle=org.slf4j.api)
> |
> provide: osgi.wiring.bundle: org.slf4j.api
> org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"]
> Chain 2:
> org.eclipse.m2e.wtp.jpa [osgi.identity; type="osgi.bundle"; version:Version="1.3.1.20160831-1005"; osgi.identity="org.eclipse.m2e.wtp.jpa"; singleton:="true"]
> require: (osgi.wiring.bundle=org.slf4j.api)
> |
> provide: osgi.wiring.bundle; bundle-version:Version="1.7.2.v20121108-1250"; osgi.wiring.bundle="org.slf4j.api"
> org.slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.2.v20121108-1250"; osgi.identity="org.slf4j.api"]
> require: (&(osgi.wiring.bundle=ch.qos.logback.classic)(&(bundle-version>=1.0.7)(!(bundle-version>=1.0.8))))
> |
> provide: osgi.wiring.bundle; bundle-version:Version="1.0.7.v20121108-1250"; osgi.wiring.bundle="ch.qos.logback.classic"
> ch.qos.logback.classic [osgi.identity; type="osgi.bundle"; version:Version="1.0.7.v20121108-1250"; osgi.identity="ch.qos.logback.classic"]
> import: (&(osgi.wiring.package=org.slf4j)(version>=1.7.0))
> |
> export: osgi.wiring.package: org.slf4j
> slf4j.api [osgi.identity; type="osgi.bundle"; version:Version="1.7.4"; osgi.identity="slf4j.api"]
> at org.eclipse.osgi.container.Module.start(Module.java:444)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1620)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1599)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1571)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1514)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340){code}
> So, since slf4j.api is installed via 5 upstream projects (5 symlinks, actually, to rh-java-common):
> {code}
> $➔ find . -name "*slf4j.api*jar" -exec ls -l {} \;
> lrwxrwxrwx 1 root root 81 Oct 11 13:00 ./share/eclipse/droplets/jgit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 81 Oct 12 05:19 ./share/eclipse/droplets/linuxtools-docker/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-egit/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> lrwxrwxrwx 1 root root 75 Oct 21 09:58 ./share/eclipse/droplets/mylyn-versions-git/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/api.jar
> lrwxrwxrwx 1 root root 81 Oct 11 14:46 ./share/eclipse/droplets/egit-mylyn/eclipse/plugins/slf4j.api_1.7.4.jar -> ../../../../../../../../../rh-java-common/root/usr/share/java/slf4j/slf4j-api.jar
> {code}
> ... I removed it from the RPM in favour of the other bundle, which was already installed into the fedora/rhel eclipse.
> BUT... since this RH SCL rh-java-common *slf4j-api.jar* exports a different, incompatible bundle name:
> {code}Bundle-SymbolicName: slf4j.api{code}
> than the one in devstudio's update site / target platform
> {code}Bundle-SymbolicName: org.slf4j.api{code}
> NOW, I'm getting this:
> {code}
> org.osgi.framework.BundleException: Could not resolve module: org.eclipse.m2e.wtp.jpa [931]
> Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2"
> {code}
> Snjezana got this too in m2e.core:
> {code}BundleException: Could not resolve module: org.eclipse.m2e.core.ui [866]
> Unresolved requirement: Require-Bundle: org.eclipse.m2e.maven.runtime; bundle-version="[1.7.0,1.8.0)"
> -> Bundle-SymbolicName: org.eclipse.m2e.maven.runtime; bundle-version="1.7.0.20160603-1931"; singleton:="false"
> org.eclipse.m2e.maven.runtime [876]
> Unresolved requirement: Require-Bundle: org.slf4j.api; bundle-version="1.6.2"{code}
> So... not sure what to do to solve this. :(
> I suppose the best case would be for the m2e and w2e-wtp bundles to depend on the slf4j.api PACKAGES instead of BUNDLES, so that they can run on the fedora/rhel versions instead of those from the devstudio update site / target platform.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23368) Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23368?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-23368:
---------------------------------------
So, what about whole port mapping wizard page in Deploy Docker Image wizard? If we dont want to propagate ports to lower levels from the wizard, we have mapped ports which have no purpose. Or did I miss something?
> Deploy Docker Image: Replication controller does not contain mapped ports from Deploy Image Wizard
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23368
> URL: https://issues.jboss.org/browse/JBIDE-23368
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Labels: deploy_docker_wizard, openshift_v3
> Fix For: 4.4.2.AM3
>
>
> When deploying a docker image via Deploy Docker Wizard to an OpenShift instance, there is a wizard page with mapping of pod ports to service ports. If I add a new port mapping there, it is propagated to a created Service. But created replication controller does not contain those new mappings (results into creating pods without those ports available)
> Either way this should be fixed, to also Replication Controller should contain mapped ports, because having a service which has mapped pod ports to service ports but pods itself does not have this port exposes is useless. Or having Add... button does not make sense there, or there is no known use case where it would be useful (existing mapping could be edited but a new one would be useless).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months
[JBoss JIRA] (JBIDE-23184) Add Capability to Watch Projects
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23184?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23184:
------------------------------------------
merged [#1359|https://github.com/jbosstools/jbosstools-openshift/pull/1359] into master
> Add Capability to Watch Projects
> --------------------------------
>
> Key: JBIDE-23184
> URL: https://issues.jboss.org/browse/JBIDE-23184
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Jeff Cantrill
> Assignee: Dmitrii Bocharov
> Fix For: 4.4.2.AM3
>
>
> Origin now allows watching of projects for adds and delete. Add capability to watch projects. Need to take into consideration how one might use the latest code against an older server version since older servers did not support project watch
> $ curl -k -H "Authorization: Bearer LU3A1EyTOdnRhkLqe8Gqkgk850eTNlljz18NwLA-108" https://192.168.1.13:8443/oapi/v1/projects?watch=true&&resourceVersion=
> {"type":"ADDED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","uid":"41f418fc-7ea3-11e6-803b-507b9dfa4ab3","resourceVersion":"942","creationTimestamp":"2016-09-19T19:57:13Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/requester":"developer","openshift.io/sa.scc.mcs":"s0:c7,c4","openshift.io/sa.scc.supplemental-groups":"1000050000/10000","openshift.io/sa.scc.uid-range":"1000050000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}}
> {"type":"DELETED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","creationTimestamp":null},"spec":{},"status":{}}}
> openshift-origin PR that made it available: https://github.com/openshift/origin/pull/6828
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 5 months