[JBoss JIRA] (JBIDE-18482) For JBIDE 4.2.0.CR2: Prepare for CR2 release [Freemarker]
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18482?page=com.atlassian.jira.plugi... ]
Denis Golovin resolved JBIDE-18482.
-----------------------------------
Assignee: Denis Golovin
Resolution: Rejected
> For JBIDE 4.2.0.CR2: Prepare for CR2 release [Freemarker]
> ---------------------------------------------------------
>
> Key: JBIDE-18482
> URL: https://issues.jboss.org/browse/JBIDE-18482
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: freemarker
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR2
>
>
> For JBIDE 4.2.0.CR2 [Freemarker]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
> [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
> mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
> {code}
> 5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 4. 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 Freemarker task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18465) For JBIDE 4.2.0.CR2: Prepare for CR2 release [Aerogear]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18465?page=com.atlassian.jira.plugi... ]
Gorkem Ercan closed JBIDE-18465.
--------------------------------
Resolution: Done
> For JBIDE 4.2.0.CR2: Prepare for CR2 release [Aerogear]
> -------------------------------------------------------
>
> Key: JBIDE-18465
> URL: https://issues.jboss.org/browse/JBIDE-18465
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid
> Reporter: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR2
>
>
> For JBIDE 4.2.0.CR2 [Aerogear]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
> [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JB...]
> 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR2-SNAPSHOT
> mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
> {code}
> 5. If you did not already do so, *{color:orange}IN YOUR MASTER BRANCH{color}*:
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha1-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 4. 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 Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18454) Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18454?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18454:
------------------------------------------
We decided to provide a flag to turn cipher filtering on and of. The library now provides a system property
{code}
-Ddisable_bad_sslciphers=yes|no|auto
{code}
The default for the system property is *no*
> Cant connect to OpenShift running on RHEL 6.6 (javax.net.ssl.SSLException: Could not generate DH keypair)
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18454
> URL: https://issues.jboss.org/browse/JBIDE-18454
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 4.2.0.CR2
>
> Attachments: ssl-error-on-connect.png
>
>
> In https://bugzilla.redhat.com/show_bug.cgi?id=1145848 openshift-java-client cant connect to OpenShift running on RHEL 6.6 when using jdks (openjdk and sun) < 1.8 on linux. We have to verify that this affects the Eclipse based tooling (that's also using openshift-java-client)
> {code}
> java.io.IOException: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
> at hudson.plugins.openshift.OpenShiftCloud.getOpenShiftConnection(OpenShiftCloud.java:186)
> at hudson.plugins.openshift.OpenShiftCloud.getSlaves(OpenShiftCloud.java:877)
> at hudson.plugins.openshift.OpenShiftCloud.provisionSlave(OpenShiftCloud.java:451)
> at hudson.plugins.openshift.OpenShiftCloud.provision(OpenShiftCloud.java:413)
> at hudson.slaves.NodeProvisioner.update(NodeProvisioner.java:281)
> at hudson.slaves.NodeProvisioner.access$000(NodeProvisioner.java:51)
> at hudson.slaves.NodeProvisioner$NodeProvisionerInvoker.doRun(NodeProvisioner.java:368)
> at hudson.triggers.SafeTimerTask.run(SafeTimerTask.java:54)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
> at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: com.openshift.client.OpenShiftEndpointException: Could not request https://broker.ose21z-auto.com.cn/broker/rest/api: javax.net.ssl.SSLException: java.lang.RuntimeException: Could not generate DH keypair
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18492) Incorrect Qualifier Target validation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18492?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18492:
-----------------------------------
Fix Version/s: 4.3.0.Alpha1
> Incorrect Qualifier Target validation
> -------------------------------------
>
> Key: JBIDE-18492
> URL: https://issues.jboss.org/browse/JBIDE-18492
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.2.Final
> Environment: Eclipse Kepler, JBoss Tools 4.1 for Kepler (Context and Dependency Injection Tools 1.5.1.Final-v20140303-0347-B156).
> Reporter: Vsevolod Golovanov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha1
>
>
> The warning states:
> {code}
> Qualifier annotation type must be annotated with @Target({TYPE, METHOD, FIELD, PARAMETER}) or @Target({FIELD, PARAMETER}) [JSR-299 §2.3.2, §10.1]
> {code}
> Both referenced specification articles say "typically defined as", not "must be one of". Weld 2.2.5.Final doesn't have any issues with the Targets, that are deemed incorrect by CDI Tools.
> It's invalid to put any restriction on a Target at all.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18492) Incorrect Qualifier Target validation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18492?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-18492:
--------------------------------------
Assignee: Viacheslav Kabanovich
> Incorrect Qualifier Target validation
> -------------------------------------
>
> Key: JBIDE-18492
> URL: https://issues.jboss.org/browse/JBIDE-18492
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.2.Final
> Environment: Eclipse Kepler, JBoss Tools 4.1 for Kepler (Context and Dependency Injection Tools 1.5.1.Final-v20140303-0347-B156).
> Reporter: Vsevolod Golovanov
> Assignee: Viacheslav Kabanovich
> Fix For: 4.3.0.Alpha1
>
>
> The warning states:
> {code}
> Qualifier annotation type must be annotated with @Target({TYPE, METHOD, FIELD, PARAMETER}) or @Target({FIELD, PARAMETER}) [JSR-299 §2.3.2, §10.1]
> {code}
> Both referenced specification articles say "typically defined as", not "must be one of". Weld 2.2.5.Final doesn't have any issues with the Targets, that are deemed incorrect by CDI Tools.
> It's invalid to put any restriction on a Target at all.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBIDE-18492) Incorrect Qualifier Target validation
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18492?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-18492:
----------------------------------------
{quote}
Both referenced specification articles say "typically defined as", not "must be one of".
{quote}
This is true for JSR-346 (CDI 1.1) but not for JSR-299 (CDI 1.0) which that message references to.
The problem is that this old (CDI 1.0) validation rule should not be enabled for CDI 1.1/1.2 projects. We did miss this change in CDI 1.1 spec, when implemented CDI 1.1 support.
> Incorrect Qualifier Target validation
> -------------------------------------
>
> Key: JBIDE-18492
> URL: https://issues.jboss.org/browse/JBIDE-18492
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> Affects Versions: 4.1.2.Final
> Environment: Eclipse Kepler, JBoss Tools 4.1 for Kepler (Context and Dependency Injection Tools 1.5.1.Final-v20140303-0347-B156).
> Reporter: Vsevolod Golovanov
>
> The warning states:
> {code}
> Qualifier annotation type must be annotated with @Target({TYPE, METHOD, FIELD, PARAMETER}) or @Target({FIELD, PARAMETER}) [JSR-299 §2.3.2, §10.1]
> {code}
> Both referenced specification articles say "typically defined as", not "must be one of". Weld 2.2.5.Final doesn't have any issues with the Targets, that are deemed incorrect by CDI Tools.
> It's invalid to put any restriction on a Target at all.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 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:
--------------------------------
Workaround Description:
In the <dependencies> section, you need to add
<dependency>
<groupId>org.jboss.spec.javax.servlet</groupId>
<artifactId>jboss-servlet-api_3.0_spec</artifactId>
<scope>provided</scope>
</dependency>
Workaround: Workaround Exists
Component/s: upstream
The JSP validator/builder needs the Servlet API in the classpath whenever JSPs are found in a project.
The example needs to be fixed to add jboss-servlet-api_3,0_spec to the project dependencies. In the <dependencies> (not <dependencyManagement>!), one should add :
{noformat}
<dependency>
<groupId>org.jboss.spec.javax.servlet</groupId>
<artifactId>jboss-servlet-api_3.0_spec</artifactId>
<scope>provided</scope>
</dependency>
{noformat}
> 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.2.0.Final
>
>
> 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.1#6329)
11 years, 6 months