[JBoss JIRA] (JBIDE-24328) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [browsersim]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24328:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [browsersim]
Key: JBIDE-24328
URL: https://issues.jboss.org/browse/JBIDE-24328
Project: Tools (JBoss Tools)
Issue Type: Task
Components: browsersim
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 4.4.4.Final
For JBIDE 4.4.4.Final [browsersim]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
[Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.4.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.4.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
{code}
git checkout master;
git pull origin master;
git checkout -b jbosstools-4.4.x;
git push origin jbosstools-4.4.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
{code}
mvn clean verify -Dtpc.version=4.60.2.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final-SNAPSHOT
{code}
mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for browsersim task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24325) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24325:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
Key: JBIDE-24325
URL: https://issues.jboss.org/browse/JBIDE-24325
Project: Tools (JBoss Tools)
Issue Type: Task
Components: aerogear-hybrid
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 4.4.4.Final
For JBIDE 4.4.4.Final [aerogear-hybrid]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
[Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.4.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.4.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
{code}
git checkout master;
git pull origin master;
git checkout -b jbosstools-4.4.x;
git push origin jbosstools-4.4.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
{code}
mvn clean verify -Dtpc.version=4.60.2.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final-SNAPSHOT
{code}
mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24326) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [arquillian]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24326:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [arquillian]
Key: JBIDE-24326
URL: https://issues.jboss.org/browse/JBIDE-24326
Project: Tools (JBoss Tools)
Issue Type: Task
Components: arquillian
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 4.4.4.Final
For JBIDE 4.4.4.Final [arquillian]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
[Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.4.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.4.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
{code}
git checkout master;
git pull origin master;
git checkout -b jbosstools-4.4.x;
git push origin jbosstools-4.4.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
{code}
mvn clean verify -Dtpc.version=4.60.2.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final-SNAPSHOT
{code}
mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24327) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [foundation]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24327:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [foundation]
Key: JBIDE-24327
URL: https://issues.jboss.org/browse/JBIDE-24327
Project: Tools (JBoss Tools)
Issue Type: Task
Components: foundation
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 4.4.4.Final
For JBIDE 4.4.4.Final [foundation]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
[Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.4.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.4.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
{code}
git checkout master;
git pull origin master;
git checkout -b jbosstools-4.4.x;
git push origin jbosstools-4.4.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
{code}
mvn clean verify -Dtpc.version=4.60.2.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final-SNAPSHOT
{code}
mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for foundation task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24325) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24325?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24325:
----------------------------------
Assignee: Gorkem Ercan
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24325
> URL: https://issues.jboss.org/browse/JBIDE-24325
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aerogear-hybrid
> Reporter: Jeff MAURY
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [aerogear-hybrid]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24326) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [arquillian]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24326?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24326:
----------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [arquillian]
> -----------------------------------------------------------------------
>
> Key: JBIDE-24326
> URL: https://issues.jboss.org/browse/JBIDE-24326
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: arquillian
> Reporter: Jeff MAURY
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [arquillian]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for arquillian task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24324) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24324:
----------------------------------
Summary: For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
Key: JBIDE-24324
URL: https://issues.jboss.org/browse/JBIDE-24324
Project: Tools (JBoss Tools)
Issue Type: Task
Components: aerogear-hybrid
Reporter: Jeff MAURY
Priority: Blocker
Fix For: 4.4.4.Final
For JBIDE 4.4.4.Final [aerogear-hybrid]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
[Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
1. Check out your existing *{color:orange}master{color}* branch:
{code}
git checkout master
{code}
2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.4.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.4.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
{code}
git checkout master;
git pull origin master;
git checkout -b jbosstools-4.4.x;
git push origin jbosstools-4.4.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
{code}
mvn clean verify -Dtpc.version=4.60.2.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final-SNAPSHOT
{code}
mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
{code}
5. Close (do not resolve) this JIRA when done.
6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24324) For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24324?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-24324:
----------------------------------
Assignee: Gorkem Ercan
> For JBIDE 4.4.4.Final: Prepare for 4.4.4.Final / 10.4.0.GA [aerogear-hybrid]
> ----------------------------------------------------------------------------
>
> Key: JBIDE-24324
> URL: https://issues.jboss.org/browse/JBIDE-24324
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: aerogear-hybrid
> Reporter: Jeff MAURY
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.4.4.Final
>
>
> For JBIDE 4.4.4.Final [aerogear-hybrid]: Please perform the following tasks:
>
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.4.Final or 10.4.0.GA
>
> [Unresolved JIRAs with fixVersion = 4.4.4.Final, 10.4.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
>
> 1. Check out your existing *{color:orange}master{color}* branch:
>
> {code}
> git checkout master
> {code}
>
> 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.4.Final-SNAPSHOT{color}*:
>
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.4.4.Final-SNAPSHOT</version>
> </parent>
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:orange}4.4.4.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch
>
> 3. Branch from your existing master branch into a new *{color:blue}jbosstools-4.4.x{color}* branch:
>
> {code}
> git checkout master;
> git pull origin master;
> git checkout -b jbosstools-4.4.x;
> git push origin jbosstools-4.4.x
> {code}
>
> Now, your root pom will use parent pom version:
>
> * *{color:blue}4.4.4.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.x{color}* branch, too.
>
> 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final
>
> {code}
> mvn clean verify -Dtpc.version=4.60.2.Final
> {code}
>
> 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.63.0.Final-SNAPSHOT
>
> {code}
> mvn clean verify -Dtpc.version=4.63.0.Final-SNAPSHOT
> {code}
>
> 5. Close (do not resolve) this JIRA when done.
>
> 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next.
>
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for aerogear-hybrid task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4321:
-----------------------------
Attachment: rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt
rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt
> Unable to start Devstudio without -clean after install of any stuff from RH Central
> -----------------------------------------------------------------------------------
>
> Key: JBDS-4321
> URL: https://issues.jboss.org/browse/JBDS-4321
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM2
> Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.AM3
>
> Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt, rpm-installed-everything-from-central.png, rpm-installed-everything-from-central.update.rpm.deps.txt
>
>
> When I install something from Red Hat Central and then start Devstudio without -clean then I get this error:
> {code}
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689
> !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi
> !STACK 0
> java.lang.NullPointerException
> {code}
> There are multiple errors but this one seems to be common for multiple items.
> And this window appear:
> !Start_without_clean.png|thumbnail!
> There is easy workaround but user won't start Devstudio with -clean and many of them could be upset.
> Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean.
> CC: [~psrna] [~vkadlcik]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBDS-4321) Unable to start Devstudio without -clean after install of any stuff from RH Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4321?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4321:
-----------------------------
Attachment: rpm-installed-everything-from-central.update.rpm.deps.txt
> Unable to start Devstudio without -clean after install of any stuff from RH Central
> -----------------------------------------------------------------------------------
>
> Key: JBDS-4321
> URL: https://issues.jboss.org/browse/JBDS-4321
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: rpm
> Affects Versions: 10.4.0.AM2
> Environment: RHEL7, RHSCL 2.4 Beta 1.1, Devstudio 10.4-0.20170320.0955.el7
> Reporter: Lukáš Valach
> Assignee: Nick Boldt
> Fix For: 10.4.0.AM3
>
> Attachments: Start_without_clean.png, rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict.txt, rh-eclipse46-devstudio10.4-0.20170425.1442.el7.log.20170426-0913_strict_FILTERED.txt, rpm-installed-everything-from-central.png, rpm-installed-everything-from-central.update.rpm.deps.txt
>
>
> When I install something from Red Hat Central and then start Devstudio without -clean then I get this error:
> {code}
> !ENTRY org.eclipse.e4.ui.workbench 4 0 2017-03-23 07:51:22.689
> !MESSAGE Unable to load resource platform:/plugin/org.eclipse.platform/LegacyIDE.e4xmi
> !STACK 0
> java.lang.NullPointerException
> {code}
> There are multiple errors but this one seems to be common for multiple items.
> And this window appear:
> !Start_without_clean.png|thumbnail!
> There is easy workaround but user won't start Devstudio with -clean and many of them could be upset.
> Please see the log: [^rh-eclipse46-devstudio10.4-0.20170320.0955.el7.log.Without_clean_test_strict.txt] There is what I got when I installed FindBugs. I put some comments there so you can find sections installation/start without clean/start with clean.
> CC: [~psrna] [~vkadlcik]
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months