August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26283) Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26283?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26283: ------------------------------------ ok, so because com.jboss.devstudio.core.cheatsheets won't build now... {code} [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata-default (default-p2-metadata-default) on project com.jboss.devstudio.core.cheatsheets: baseline and build artifacts have same version but different contents [ERROR] classifier-sources: not present in baseline {code} the workarounds are either upversion is again (it's already stupidly on 12.9.1), or use baselineMode=warn [1]. So, I've set baselineMode=warn. I believe this is what we had 2 weeks ago when I first started working on this issue. [1] https://github.com/jbosstools/jbosstools-build/commit/f665d9b2f3e63078c69... Hope this works. > Baseline and reactor have same fully qualified version, but with different content in jbosstools-base plugins/features > ---------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-26283 > URL: https://issues.jboss.org/browse/JBIDE-26283 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.9.0.AM2 > > Attachments: diff-baseline-with-local-build-commented-timestamps.png, diff-baseline-with-local-build-sourcereferences-cause-problem.png > > > Job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is red for one week. > More info: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/build_... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26244) Fuse Tools New and Noteworthy for 4.9.0.AM2

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26244?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-26244: ------------------------------------------- Added new PR for details - https://github.com/jbosstools/jbosstools-website/pull/847 > Fuse Tools New and Noteworthy for 4.9.0.AM2 > --------------------------------------------------- > > Key: JBIDE-26244 > URL: https://issues.jboss.org/browse/JBIDE-26244 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: fusetools, fusetools-extras > Reporter: Jeff MAURY > Assignee: Lars Heinemann > Priority: Critical > Labels: task > Fix For: 4.9.0.AM2 > > > Lars Heinemann, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Fuse Tools JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Fuse Tools, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Fuse Tools by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-26236 #comment Create N&N for Fuse Tools 4.9.0.AM2 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Fuse Tools for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26180: ------------------------------------ [~odockal] Please consider asking for stuff before the code freeze. :D Had you told me about this on Wednesday, I could have picked it up (and we'd have seen all the places that a new RD breaks Docker Tooling and JBoss Tools tests plugins. Anyway, I'll grab newer RD for the next TP update planned for M3. `For sprint 154 / AM3: simrel M3` > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final > > Attachments: am1-vs-am2.p2diff.txt > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26305) Jars inside an EAR application are not compressed

by Rick Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26305?page=com.atlassian.jira.plugi... ] Rick Wagner commented on JBIDE-26305: ------------------------------------- Hi [~mmalina], [~rob.stryker] Ok, that helps explains things. Thanks for that. The support case is closed, but the customer has been given the link to this tracker, so the above has been communicated through this channel. I'll investigate further and will pursue future remedies via EAP. Rick > Jars inside an EAR application are not compressed > ------------------------------------------------- > > Key: JBIDE-26305 > URL: https://issues.jboss.org/browse/JBIDE-26305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Martin Malina > Assignee: Rob Stryker > > A customer has reported an issue where an ear project, when deployed to EAP 7.1, contains exploded jars which then breaks his app. It seems that in his case it happens both in the case of a jar inside a war inside an ear, as well as just a jar inside an ear. > Also, when the customer deploys the same app in the same workspace and same eclipse to EAP 6.4, it works fine - all the jars are zipped. > The customer reports that he can change this behavior in the Deployments tab of the server editor, but it would be nice to be able to define this beforehand in a config file. > I tried to reproduce this in devstudio 12 and in my case the behavior was the same with both EAP 6.4 and 7.1 - in both cases an included jar was exploded which I think is wrong. > So two main things to consider: > 1. Is this a bug? I believe it is - a jar lib should always be zipped by default. Or do you disagree? > 2. Is there a way to specify if a module of an EAP is zipped or not in a config file? If not, can this be added? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26180) TP: create target platform based on Eclipse 4.9 (Simrel 2018-09)

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26180?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-26180: --------------------------------------- [~nickboldt] Please, also consider adding RedDeer 2.3.0.Beta milestone available since 2018-08-15 at [1]. RedDeer was build and tested with 2018-09 (4.9) M2 build. Thanks! [1]: http://download.eclipse.org/reddeer/milestones/2.3.0.Beta > TP: create target platform based on Eclipse 4.9 (Simrel 2018-09) > ---------------------------------------------------------------- > > Key: JBIDE-26180 > URL: https://issues.jboss.org/browse/JBIDE-26180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.9.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.9.0.AM1, 4.9.0.AM2, 4.9.0.AM3, 4.9.0.Final > > Attachments: am1-vs-am2.p2diff.txt > > > In order to start Eclipse 4.9-based builds, we need an updated target platform. > For sprint 152 / AM1: simrel M1 > For sprint 153 / AM2: simrel M2 > For sprint 154 / AM3: simrel M3 > For sprint 155 / GA: simrel RC2/GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26276) Create PR check job for RSP (Runtime Server Protocol)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26276?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-26276: --------------------------------------- Thanks, [~rob.stryker]. In theory that should be it. But for some reason it doesn't seem to work. [~jrichter1], can you help us? The job is here: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Adapter... It's configured to use the new repo and here's a testing PR: https://github.com/redhat-developer/rsp-server/pull/4 The job got triggered. But there is nothing displayed on the PR page. >From the console output it seems that the user does not have permissions, but Rob says he's added the user as a collaborator: {code} FileNotFoundException means that the credentials Jenkins is using is probably wrong. Or the user account does not have write access to the repo. org.kohsuke.github.GHFileNotFoundException: {"message":"Not Found","documentation_url":"https://developer.github.com/v3/repos/statuses/#create-a-status"} at org.kohsuke.github.Requester.handleApiError(Requester.java:686) at org.kohsuke.github.Requester._to(Requester.java:293) at org.kohsuke.github.Requester.to(Requester.java:234) at org.kohsuke.github.GHRepository.createCommitStatus(GHRepository.java:1075) at org.jenkinsci.plugins.ghprb.extensions.status.GhprbSimpleStatus.createCommitStatus(GhprbSimpleStatus.java:272) at org.jenkinsci.plugins.ghprb.extensions.status.GhprbSimpleStatus.onBuildComplete(GhprbSimpleStatus.java:231) at org.jenkinsci.plugins.ghprb.GhprbBuilds.onCompleted(GhprbBuilds.java:192) at org.jenkinsci.plugins.ghprb.GhprbBuildListener.onCompleted(GhprbBuildListener.java:26) at hudson.model.listeners.RunListener.fireCompleted(RunListener.java:211) at hudson.model.Run.execute(Run.java:1780) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:405) Caused by: java.io.FileNotFoundException: https://api.github.com/repos/redhat-developer/rsp-server/statuses/b8de445... at sun.reflect.GeneratedConstructorAccessor1805.newInstance(Unknown Source) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:423) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1926) at sun.net.www.protocol.http.HttpURLConnection$10.run(HttpURLConnection.java:1921) at java.security.AccessController.doPrivileged(Native Method) at sun.net.www.protocol.http.HttpURLConnection.getChainedException(HttpURLConnection.java:1920) at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1490) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:254) at org.kohsuke.github.Requester.parse(Requester.java:612) at org.kohsuke.github.Requester.parse(Requester.java:594) at org.kohsuke.github.Requester._to(Requester.java:272) ... 11 more Caused by: java.io.FileNotFoundException: https://api.github.com/repos/redhat-developer/rsp-server/statuses/b8de445... at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1872) at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1474) at java.net.HttpURLConnection.getResponseCode(HttpURLConnection.java:480) at sun.net.www.protocol.https.HttpsURLConnectionImpl.getResponseCode(HttpsURLConnectionImpl.java:338) at org.kohsuke.github.Requester.parse(Requester.java:602) ... 13 more success {code} Do you have a clue what could be wrong here? > Create PR check job for RSP (Runtime Server Protocol) > ----------------------------------------------------- > > Key: JBIDE-26276 > URL: https://issues.jboss.org/browse/JBIDE-26276 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-server-protocol > Reporter: Pavol Srna > Assignee: Martin Malina > Fix For: 4.9.0.AM2 > > > https://github.com/robstryker/org.jboss.tools.ssp/blob/master/Jenkinsfile -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26305) Jars inside an EAR application are not compressed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26305?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-26305: --------------------------------------- Thanks, [~rob.stryker], for the detailed explanation. Note that I was merely trying to present what the customer was struggling with. And at the first sight it seemed wrong that a jar would ever be exploded, my intuition said it was wrong. If it indeed was wrong, then the default should be always zipped for jars. But since you say that WildFly should support deployment of exploded jars with no problem, then I agree with you that if the deployment indeed breaks for exploded jar and works with zipped jar for the customer, then that seems like a problem with the app server and not devstudio. [~rick_wagner], can you relay Rob's explanation to the customer and let us know if there's anything we can do? Right now it seems like it could be a problem with EAP itself. > Jars inside an EAR application are not compressed > ------------------------------------------------- > > Key: JBIDE-26305 > URL: https://issues.jboss.org/browse/JBIDE-26305 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Martin Malina > Assignee: Rob Stryker > > A customer has reported an issue where an ear project, when deployed to EAP 7.1, contains exploded jars which then breaks his app. It seems that in his case it happens both in the case of a jar inside a war inside an ear, as well as just a jar inside an ear. > Also, when the customer deploys the same app in the same workspace and same eclipse to EAP 6.4, it works fine - all the jars are zipped. > The customer reports that he can change this behavior in the Deployments tab of the server editor, but it would be nice to be able to define this beforehand in a config file. > I tried to reproduce this in devstudio 12 and in my case the behavior was the same with both EAP 6.4 and 7.1 - in both cases an included jar was exploded which I think is wrong. > So two main things to consider: > 1. Is this a bug? I believe it is - a jar lib should always be zipped by default. Or do you disagree? > 2. Is there a way to specify if a module of an EAP is zipped or not in a config file? If not, can this be added? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26282) Plugin org.jboss.tools.common.reddeer has wrong Execution environment

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26282?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-26282: ---------------------------------- Fix Version/s: 4.9.0.AM2 > Plugin org.jboss.tools.common.reddeer has wrong Execution environment > --------------------------------------------------------------------- > > Key: JBIDE-26282 > URL: https://issues.jboss.org/browse/JBIDE-26282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common, integration-tests > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.9.0.AM2 > > > Plugin org.jboss.tools.common.reddeer has wrong value for "Bundle-RequiredExecutionEnvironment:" in Manifest file. There is JavaSE-1.6, but there should be at least JavaSE-1.7, because in file "org.jboss.tools.common.reddeer.utils.FileUtils" is used packege "java.nio.file", which was introduced in JavaSE-1.7 - https://docs.oracle.com/javase/7/docs/api/java/nio/file/package-summary.html . > With JavaSE-1.6 it shows an error under devstudio with JDK 9. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26282) Plugin org.jboss.tools.common.reddeer has wrong Execution environment

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26282?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-26282. --------------------------------- Resolution: Done Closing, PR is merged. > Plugin org.jboss.tools.common.reddeer has wrong Execution environment > --------------------------------------------------------------------- > > Key: JBIDE-26282 > URL: https://issues.jboss.org/browse/JBIDE-26282 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common, integration-tests > Affects Versions: 4.9.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.9.0.AM2 > > > Plugin org.jboss.tools.common.reddeer has wrong value for "Bundle-RequiredExecutionEnvironment:" in Manifest file. There is JavaSE-1.6, but there should be at least JavaSE-1.7, because in file "org.jboss.tools.common.reddeer.utils.FileUtils" is used packege "java.nio.file", which was introduced in JavaSE-1.7 - https://docs.oracle.com/javase/7/docs/api/java/nio/file/package-summary.html . > With JavaSE-1.6 it shows an error under devstudio with JDK 9. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25207) Integration Tests: PortForwardingTest

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25207?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25207: ---------------------------------- Fix Version/s: 4.9.0.AM2 (was: 4.9.x) > Integration Tests: PortForwardingTest > ------------------------------------- > > Key: JBIDE-25207 > URL: https://issues.jboss.org/browse/JBIDE-25207 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM3 > Environment: Windows 10 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests > Fix For: 4.9.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2018