[JBoss JIRA] (JBIDE-19090) Update jobs for JBDS 9 / JBT 4.3 to build with JDK 7 on RHEL6/7
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19090:
----------------------------------
Summary: Update jobs for JBDS 9 / JBT 4.3 to build with JDK 7 on RHEL6/7
Key: JBIDE-19090
URL: https://issues.jboss.org/browse/JBIDE-19090
Project: Tools (JBoss Tools)
Issue Type: Bug
Reporter: Nick Boldt
Some jobs have been known to fail when built w/ JDK 7 on RHEL5, such as this:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build.parent_master/419/}
[8mha:AAAAYB+LCAAAAAAAAP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEuhYV5Rf55ZekOlc7RKnPKH7IxMBQUcQgBdWQnJ9XnJ+TqucMoUEKGSCAEaSwAACsNFCqYAAAAA==
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site (generate-full-site) on project parent: Execution generate-full-site of goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site failed: An API incompatibility was encountered while executing org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site: java.lang.UnsupportedClassVersionError: org/json/JSONObject : Unsupported major.minor version 52.0
{code}
So, let's just update all the jobs to use JDK7 or 8, on RHEL 6 or 7.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19047) Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19047?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-19047:
-------------------------------------
Maybe you could attach an obfuscated version of your ear pom.xml (redact all sensitive names/values)
> Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19047
> URL: https://issues.jboss.org/browse/JBIDE-19047
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, server, upstream
> Environment: Ubuntu 14.04, Wildfly 8.2.0 FInal, Eclipse Luna
> Reporter: Nick .
> Assignee: Fred Bricon
> Fix For: 4.3.x
>
> Attachments: sample.zip, settings.zip
>
>
> Hi,
> I have a maven EAR project, which contains a couple of WAR and JAR files. I'm using Eclipse Luna (tried STS and IntelliJ ) IDE with JBoss Tools 1.6.0 (latest).
> When I try to deploy my EAR to Wildfly (as well as in EAP 6.2.0) with JBoss Tools from eclipse i'm facing the following issues.
> My Jars (external jars and project jar) are getting copied into WEB-INF/lib and EAR/lib, where i expected it to be only in EAR/lib.
> EAR application.xml is not getting copied into EAR/META-INF/ folder
> But when i use command line to build my project , i'm not experiencing the above issue.
> FYI : We are using <skinnyWars>true</skinnyWars>.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18752) Freemarker plugin does not work for square bracket (since JBT 4.2.0.Final)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18752?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-18752:
---------------------------------------
According to http://freemarker.org/docs/dgui_misc_alternativesyntax.html current code works as expected. Because there is no auto-detection for syntax used until 2.4.x is released.
In current version the only way to change default syntax (<#) to alternative ([#) is to have [#ftl] in the beginning of a template, that is what currently implemented.
> Freemarker plugin does not work for square bracket (since JBT 4.2.0.Final)
> --------------------------------------------------------------------------
>
> Key: JBIDE-18752
> URL: https://issues.jboss.org/browse/JBIDE-18752
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: freemarker
> Affects Versions: 4.2.0.Final
> Reporter: Nick Boldt
> Assignee: Max Rydahl Andersen
> Fix For: 4.3.0.Alpha1
>
>
> From https://github.com/jbosstools/jbosstools-freemarker/issues/26
> {quote}
> When using the plugin to edit freemarker files that use the square bracket syntax the editor fails to highlight the syntax (this is happening in JBoss Tools 4.20 Final).
> I think the file: src / org / jboss / ide / eclipse / freemarker / editor / DocumentProvider.java
> on line 70 is causing the syntax highlighting problem:
> {code}if (ch != LexicalConstants.SQUARE_SYNTAX_MARKER.charAt(i)) {
> return SyntaxMode.ANGLE;
> }
> SQUARE_SYNTAX_MARKER.charAt(i)
> {code}
> It should start in 0 and have a different index than i (the index of the file content) to have a proper string matching. Also, SQUARE_SYNTAX_MARKER is [#ftl, not all files start with a ftl tag, so I don't see the need for "ftl" at the end, so that's why in the following example fix I put j < 2.
> e.g.
> {code}
> int j =0;
> for (; i < docLength && j < 2; i++) {
> char ch = document.getChar(i);
> if (ch != LexicalConstants.SQUARE_SYNTAX_MARKER.charAt(j)) {
> return SyntaxMode.ANGLE;
> }
> j++;
> }
> {code}
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18494) Importing EAP "jboss-logging" quickstart raises errors
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18494?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-18494:
--------------------------------
Fix Version/s: 4.3.x
(was: 4.2.x)
> Importing EAP "jboss-logging" quickstart raises errors
> ------------------------------------------------------
>
> Key: JBIDE-18494
> URL: https://issues.jboss.org/browse/JBIDE-18494
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.2.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL6
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Fix For: 4.3.x
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects - select the quickstart
> The error raised is:
> The superclass "javax.servlet.http.HttpServlet" was not found on the Java Build Path home.jsp /jboss-logging/src/main/webapp line 1 JSP Problem
> (This can be fixed by adding Maven Managed Dependencies to the Java Build path)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19047) Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin
by Nick . (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19047?page=com.atlassian.jira.plugi... ]
Nick . commented on JBIDE-19047:
--------------------------------
Yeah thats right application.xml is not created under target/..., i checked the effective pom, nowhere i can see that tag value.
Let me try with the dependency stuff, even i was thinking about redoing my pom based on the archetype you have provided.
> Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19047
> URL: https://issues.jboss.org/browse/JBIDE-19047
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, server, upstream
> Environment: Ubuntu 14.04, Wildfly 8.2.0 FInal, Eclipse Luna
> Reporter: Nick .
> Assignee: Fred Bricon
> Fix For: 4.3.x
>
> Attachments: sample.zip, settings.zip
>
>
> Hi,
> I have a maven EAR project, which contains a couple of WAR and JAR files. I'm using Eclipse Luna (tried STS and IntelliJ ) IDE with JBoss Tools 1.6.0 (latest).
> When I try to deploy my EAR to Wildfly (as well as in EAP 6.2.0) with JBoss Tools from eclipse i'm facing the following issues.
> My Jars (external jars and project jar) are getting copied into WEB-INF/lib and EAR/lib, where i expected it to be only in EAR/lib.
> EAR application.xml is not getting copied into EAR/META-INF/ folder
> But when i use command line to build my project , i'm not experiencing the above issue.
> FYI : We are using <skinnyWars>true</skinnyWars>.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19089) JavaEE Batch component has no junit tests, so all-tests/pom.xml fails
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19089?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-19089.
----------------------------------
> JavaEE Batch component has no junit tests, so all-tests/pom.xml fails
> ---------------------------------------------------------------------
>
> Key: JBIDE-19089
> URL: https://issues.jboss.org/browse/JBIDE-19089
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.3.0.Alpha1
>
>
> No JUnit tests for batch? That's not good.
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-javaee_master/682/console}
> 04:03:14 [ERROR] Child module /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/all-tests/../batch/tests of /mnt/hudson_workspace/workspace/jbosstools-javaee_master/sources/all-tests/pom.xml does not exist
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19074) For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [VPE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19074?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19074:
-----------------------------------
Description:
For JBIDE 4.3.0.Alpha1 [VPE]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
was:
For JBIDE 4.3.0.Alpha1 [VPE]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [VPE]
> -------------------------------------------------------------------------------
>
> Key: JBIDE-19074
> URL: https://issues.jboss.org/browse/JBIDE-19074
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Reporter: Nick Boldt
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [VPE]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
> Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19076) For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [OpenShift]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19076?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19076:
-----------------------------------
Description:
For JBIDE 4.3.0.Alpha1 [OpenShift]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
was:
For JBIDE 4.3.0.Alpha1 [OpenShift]: Please perform the following tasks:
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> For JBIDE 4.3.0.Alpha1: Upversion plugins + features for JBT 4.3 / JBDS 9 [OpenShift]
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-19076
> URL: https://issues.jboss.org/browse/JBIDE-19076
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: openshift
> Reporter: Nick Boldt
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha1
>
>
> For JBIDE 4.3.0.Alpha1 [OpenShift]: Please perform the following tasks:
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100.
> Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months