[JBoss JIRA] (JBIDE-21602) Sonar build for openshift is failing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21602?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21602:
------------------------------------------
Current state for OpenShift is that sonar is now running but FindBugs is not able to parse java8 lambda syntax:
{code}
[INFO] [01:44:27.466] Compare to previous version (2015-01-14)
[INFO] [01:44:27.651] Initializer FindbugsMavenInitializer...
[INFO] [01:44:27.728] Initializer FindbugsMavenInitializer done: 77 ms
[INFO] [01:44:27.728] Base dir: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core
[INFO] [01:44:27.728] Working dir: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/target/sonar
[INFO] [01:44:27.729] Source dirs: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/src
[INFO] [01:44:27.729] Binary dirs: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/target/classes
[INFO] [01:44:27.729] Source encoding: UTF-8, default locale: en_US
[INFO] [01:44:27.743] Sensor JavaSourceImporter...
[INFO] [01:44:28.038] Sensor JavaSourceImporter done: 295 ms
[INFO] [01:44:28.038] Sensor JavaSquidSensor...
[INFO] [01:44:28.104] Java AST scan...
[ERROR] [01:44:28.242] Unable to parse source file : /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/src/org/jboss/tools/openshift/egit/core/EGitUtils.java
[ERROR] [01:44:28.246] Parse error at line 1549 column 14 failed to match all of: INC DEC BANG TILDA PLUS MINUS LPAR LPAR LPOINT THIS SUPER TRUE FALSE NULL CHARACTER_LITERAL LITERAL FLOAT_LITERAL DOUBLE_LITERAL LONG_LITERAL INTEGER_LITERAL NEW ENUM BYTE SHORT CHAR INT LONG FLOAT DOUBLE BOOLEAN VOID
1539: if (ORIGIN.equals(o1.getName())) {
1540: return -1;
1541: }
1542: if (ORIGIN.equals(o2.getName())) {
1543: return 1;
1544: }
1545: return o1.getName().compareToIgnoreCase(o2.getName());
1546: }
1547: });
1548: return remoteConfigs.stream()
1549: .map(rc -> getFetchURI(rc))
^
1550: .filter(uri -> uri != null && uri.toString().startsWith("http"))
1551: .map(URIish::toString);
1552: }
1553: }
1554:
{cdoe}
> Sonar build for openshift is failing
> ------------------------------------
>
> Key: JBIDE-21602
> URL: https://issues.jboss.org/browse/JBIDE-21602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta2
> Reporter: Andre Dietisheim
> Assignee: Mickael Istria
> Attachments: sonar-build-output.txt
>
>
> Sonar for openshift is currently failing in our jenkins at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo...
> I see it complaining in the build about an incompatible bytecode version:
> {code}
> Caused by: java.lang.UnsupportedClassVersionError: org/eclipse/tycho/core/p2/P2ArtifactRepositoryLayout : Unsupported major.minor version 51.0
> {code}
> The full build output is attached [^sonar-build-output.txt]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-571) Error loading file switchyard.xml. Unable to load the generated resource.
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-571?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky updated JBTIS-571:
------------------------------------
Attachment: jbtis-571_2.png
jbtis-571_1.png
> Error loading file switchyard.xml. Unable to load the generated resource.
> -------------------------------------------------------------------------
>
> Key: JBTIS-571
> URL: https://issues.jboss.org/browse/JBTIS-571
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: switchyard
> Reporter: nicolas duminil
> Assignee: Brian Fitzpatrick
> Priority: Blocker
> Attachments: jbtis-571_1.png, jbtis-571_2.png
>
>
> After creating a new switchyard project, next time it starts up JBDS is not able to open its own generated siwtchyard.xml file. The error "Error loading file switchyard.xml. Unable to load the generated resource" is displayed. The only choice is the OK button. Pressing it, the JBDS screen doesn't display but JBDS seems to be started and the LCK file created. The only option the user has is to kill the process.
> Tested on Windows 7 and Windows 10 with Java 8.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-19933) Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19933?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19933:
---------------------------------------
[~nickboldt], reading through this JIRA again (it's been a long time, so I forgot everything :) ), I think that is correct.
Exactly like you say - when you branch for 4.4.0.Alpha1x from master, it would be nice to copy over the content from master update sites to 4.4.neon.
> Copy master snapshot to 4.3.mars (or similar) update site at code freeze to initiate it
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-19933
> URL: https://issues.jboss.org/browse/JBIDE-19933
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.4.x
>
>
> When we code freeze for e.g. 4.3.0.Beta1, jbosstools-build is branched as Beta1x and the parent pom starts point at 4.3.mars as the site stream (instead of master).
> Currently, this update site will contain the previous milestone (Alpha2 in this case) until we get a first build on this branch.
> It would be nice if we could initiate the 4.3.mars update site with the contents of master update site - it would be consistent with how git branches work - when we branch for Beta1x, it starts exactly where master left off at that point.
> For those interested: The reason I'm bringing this up is that our build of jbosstools-integration-tests just got broken now - because it uses Beta1 parent pom which now points to the 4.3.mars site stream which currently contains Alpha2 bits. But at the same time, the TP defined in this parent pom is much newer. The workaround for us would be to use -Djbosstools_site_stream=4.3.mars until the Beta1x branch is built for the first time.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years