[JBoss JIRA] (JBIDE-18472) For JBIDE 4.2.0.CR2: Prepare for CR2 release [Base]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18472?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-18472.
----------------------------------
Assignee: Alexey Kazakov
Resolution: Done
> For JBIDE 4.2.0.CR2: Prepare for CR2 release [Base]
> ---------------------------------------------------
>
> Key: JBIDE-18472
> URL: https://issues.jboss.org/browse/JBIDE-18472
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core, usage
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR2
>
>
> For JBIDE 4.2.0.CR2 [Base]: 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 Base 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-18492) Incorrect Qualifier Target validation
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18492?page=com.atlassian.jira.plugi... ]
Vsevolod Golovanov updated JBIDE-18492:
---------------------------------------
Affects Version/s: 4.1.2.Final
> 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-18492) Incorrect Qualifier Target validation
by Vsevolod Golovanov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18492?page=com.atlassian.jira.plugi... ]
Vsevolod Golovanov updated JBIDE-18492:
---------------------------------------
Environment: Eclipse Kepler, JBoss Tools 4.1 for Kepler (Context and Dependency Injection Tools 1.5.1.Final-v20140303-0347-B156). (was: Eclipse Kepler, latest JBoss Tools (Context and Dependency Injection Tools 1.5.1.Final-v20140303-0347-B156).)
> Incorrect Qualifier Target validation
> -------------------------------------
>
> Key: JBIDE-18492
> URL: https://issues.jboss.org/browse/JBIDE-18492
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdi
> 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-18476) For JBIDE 4.2.0.CR2: Prepare for CR2 release [Forge]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18476?page=com.atlassian.jira.plugi... ]
Koen Aers closed JBIDE-18476.
-----------------------------
Assignee: Koen Aers
Resolution: Done
> For JBIDE 4.2.0.CR2: Prepare for CR2 release [Forge]
> ----------------------------------------------------
>
> Key: JBIDE-18476
> URL: https://issues.jboss.org/browse/JBIDE-18476
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: forge
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR2
>
>
> For JBIDE 4.2.0.CR2 [Forge]: 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 Forge 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-18471) For JBIDE 4.2.0.CR2: Prepare for CR2 release [Hibernate]
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18471?page=com.atlassian.jira.plugi... ]
Koen Aers closed JBIDE-18471.
-----------------------------
Assignee: Koen Aers
Resolution: Done
> For JBIDE 4.2.0.CR2: Prepare for CR2 release [Hibernate]
> --------------------------------------------------------
>
> Key: JBIDE-18471
> URL: https://issues.jboss.org/browse/JBIDE-18471
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: hibernate
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR2
>
>
> For JBIDE 4.2.0.CR2 [Hibernate]: 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 Hibernate 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] (JBDS-3170) Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3170?page=com.atlassian.jira.plugin.... ]
Len DiMaggio commented on JBDS-3170:
------------------------------------
Nothing is written to the eclipse .log file when this error occurs.
> Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
> -----------------------------------------------------------------------------------------------
>
> Key: JBDS-3170
> URL: https://issues.jboss.org/browse/JBDS-3170
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 8.0.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL 6
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 8.0.0.CR2
>
> Attachments: Screenshot.png
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects the "jts" quickstart
> These errors are raised (see attached screenshot):
> No marketplace entries found to handle Connector org.eclipse.m2e.wtp.jpa.internal.configurator.wtp in Eclipse. Please see Help for more information.
> No marketplace entries found to handle null in Eclipse. Please see Help for more information.
> No marketplace entries found to handle maven-ejb-plugin:2.3:ejb in Eclipse. Please see Help for more information.
> No marketplace entries found to handle /jboss-jts-application-component-2/pom.xml in Eclipse. Please see Help for more information.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3170) Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3170?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3170:
--------------------------------------
Priority: Blocker (was: Critical)
> Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
> -----------------------------------------------------------------------------------------------
>
> Key: JBDS-3170
> URL: https://issues.jboss.org/browse/JBDS-3170
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 8.0.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL 6
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 8.0.0.CR2
>
> Attachments: Screenshot.png
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects the "jts" quickstart
> These errors are raised (see attached screenshot):
> No marketplace entries found to handle Connector org.eclipse.m2e.wtp.jpa.internal.configurator.wtp in Eclipse. Please see Help for more information.
> No marketplace entries found to handle null in Eclipse. Please see Help for more information.
> No marketplace entries found to handle maven-ejb-plugin:2.3:ejb in Eclipse. Please see Help for more information.
> No marketplace entries found to handle /jboss-jts-application-component-2/pom.xml in Eclipse. Please see Help for more information.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3170) Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3170?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3170:
--------------------------------------
Fix Version/s: 8.0.0.CR2
> Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
> -----------------------------------------------------------------------------------------------
>
> Key: JBDS-3170
> URL: https://issues.jboss.org/browse/JBDS-3170
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 8.0.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL 6
> Reporter: Len DiMaggio
> Priority: Critical
> Fix For: 8.0.0.CR2
>
> Attachments: Screenshot.png
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects the "jts" quickstart
> These errors are raised (see attached screenshot):
> No marketplace entries found to handle Connector org.eclipse.m2e.wtp.jpa.internal.configurator.wtp in Eclipse. Please see Help for more information.
> No marketplace entries found to handle null in Eclipse. Please see Help for more information.
> No marketplace entries found to handle maven-ejb-plugin:2.3:ejb in Eclipse. Please see Help for more information.
> No marketplace entries found to handle /jboss-jts-application-component-2/pom.xml in Eclipse. Please see Help for more information.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3170) Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3170?page=com.atlassian.jira.plugin.... ]
Len DiMaggio reassigned JBDS-3170:
----------------------------------
Assignee: Fred Bricon
> Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
> -----------------------------------------------------------------------------------------------
>
> Key: JBDS-3170
> URL: https://issues.jboss.org/browse/JBDS-3170
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 8.0.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL 6
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Priority: Critical
> Fix For: 8.0.0.CR2
>
> Attachments: Screenshot.png
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects the "jts" quickstart
> These errors are raised (see attached screenshot):
> No marketplace entries found to handle Connector org.eclipse.m2e.wtp.jpa.internal.configurator.wtp in Eclipse. Please see Help for more information.
> No marketplace entries found to handle null in Eclipse. Please see Help for more information.
> No marketplace entries found to handle maven-ejb-plugin:2.3:ejb in Eclipse. Please see Help for more information.
> No marketplace entries found to handle /jboss-jts-application-component-2/pom.xml in Eclipse. Please see Help for more information.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months
[JBoss JIRA] (JBDS-3170) Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3170?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3170:
-------------------------------
Attachment: Screenshot.png
> Importing EAP "jts" quickstart raises "No marketplace entries found to handle Connector" errors
> -----------------------------------------------------------------------------------------------
>
> Key: JBDS-3170
> URL: https://issues.jboss.org/browse/JBDS-3170
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 8.0.0.CR1
> Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL 6
> Reporter: Len DiMaggio
> Priority: Critical
> Attachments: Screenshot.png
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects the "jts" quickstart
> These errors are raised (see attached screenshot):
> No marketplace entries found to handle Connector org.eclipse.m2e.wtp.jpa.internal.configurator.wtp in Eclipse. Please see Help for more information.
> No marketplace entries found to handle null in Eclipse. Please see Help for more information.
> No marketplace entries found to handle maven-ejb-plugin:2.3:ejb in Eclipse. Please see Help for more information.
> No marketplace entries found to handle /jboss-jts-application-component-2/pom.xml in Eclipse. Please see Help for more information.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 6 months