[JBoss JIRA] (JBIDE-19612) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Central Discovery]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19612?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19612.
------------------------------
Assignee: Nick Boldt
Resolution: Done
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Central Discovery]
> ----------------------------------------------------------------
>
> Key: JBIDE-19612
> URL: https://issues.jboss.org/browse/JBIDE-19612
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: discovery
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [Central Discovery]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 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 from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. 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 Central Discovery 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
[JBoss JIRA] (JBIDE-19610) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JBT Update Sites]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19610?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-19610.
------------------------------
Assignee: Nick Boldt
Resolution: Done
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JBT Update Sites]
> ---------------------------------------------------------------
>
> Key: JBIDE-19610
> URL: https://issues.jboss.org/browse/JBIDE-19610
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [JBT Update Sites]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 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 from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. 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 JBT Update Sites 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
[JBoss JIRA] (JBIDE-19620) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Birt]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19620?page=com.atlassian.jira.plugi... ]
Snjezana Peco closed JBIDE-19620.
---------------------------------
Resolution: Done
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Birt]
> ---------------------------------------------------
>
> Key: JBIDE-19620
> URL: https://issues.jboss.org/browse/JBIDE-19620
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [Birt]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 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 from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. 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 Birt 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
[JBoss JIRA] (JBDS-3413) Central Software/Update Connectors View is empty after installation
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3413?page=com.atlassian.jira.plugin.... ]
Daniel Azarov updated JBDS-3413:
--------------------------------
Attachment: NoConnectors.png
> Central Software/Update Connectors View is empty after installation
> -------------------------------------------------------------------
>
> Key: JBDS-3413
> URL: https://issues.jboss.org/browse/JBDS-3413
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.Alpha2
> Environment: Windows 8, jboss-devstudio-9.0.0.Alpha1-v20150216-1042-B11-installer-eap.jar
> Reporter: Daniel Azarov
> Attachments: NoConnectors.png
>
>
> {code}!ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:22.841
> !MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> !ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:22.875
> !MESSAGE All attempts to discover connectors have failed
> !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2015-04-16 09:48:22.875
> !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> !STACK 0
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(Unknown Source)
> at java.net.URI.<init>(Unknown Source)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:61)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:28.417
> !MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3413) Central Software/Update Connectors View is empty after installation
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3413?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3413:
-----------------------------
CDW docs_ack: ?
CDW devel_ack: ?
CDW pm_ack: +
CDW qa_ack: ?
CDW release: ?
> Central Software/Update Connectors View is empty after installation
> -------------------------------------------------------------------
>
> Key: JBDS-3413
> URL: https://issues.jboss.org/browse/JBDS-3413
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.0.Alpha2
> Environment: Windows 8, jboss-devstudio-9.0.0.Alpha1-v20150216-1042-B11-installer-eap.jar
> Reporter: Daniel Azarov
>
> {code}!ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:22.841
> !MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> !ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:22.875
> !MESSAGE All attempts to discover connectors have failed
> !SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2015-04-16 09:48:22.875
> !MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
> !STACK 0
> java.lang.NullPointerException
> at java.net.URI$Parser.parse(Unknown Source)
> at java.net.URI.<init>(Unknown Source)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
> at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
> at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:61)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:28.417
> !MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3413) Central Software/Update Connectors View is empty after installation
by Daniel Azarov (JIRA)
Daniel Azarov created JBDS-3413:
-----------------------------------
Summary: Central Software/Update Connectors View is empty after installation
Key: JBDS-3413
URL: https://issues.jboss.org/browse/JBDS-3413
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: central
Affects Versions: 8.0.0.Alpha2
Environment: Windows 8, jboss-devstudio-9.0.0.Alpha1-v20150216-1042-B11-installer-eap.jar
Reporter: Daniel Azarov
{code}!ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:22.841
!MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
!ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:22.875
!MESSAGE All attempts to discover connectors have failed
!SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2015-04-16 09:48:22.875
!MESSAGE Failed to get connectors from RemoteProxyWizardDiscoveryStrategy
!STACK 0
java.lang.NullPointerException
at java.net.URI$Parser.parse(Unknown Source)
at java.net.URI.<init>(Unknown Source)
at org.jboss.tools.discovery.core.internal.connectors.xpl.RemoteExternalBundleDiscoveryStrategy.loadRegistry(RemoteExternalBundleDiscoveryStrategy.java:90)
at org.jboss.tools.discovery.core.internal.connectors.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:117)
at org.jboss.tools.discovery.core.internal.connectors.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:61)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:107)
at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:45)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
!ENTRY org.jboss.tools.discovery.core 4 0 2015-04-16 09:48:28.417
!MESSAGE No URL set for discovery catalog. Property jboss.discovery.directory.url is missing!
{code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19623) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Arquillian]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19623?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-19623:
-------------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Arquillian]
> ---------------------------------------------------------
>
> Key: JBIDE-19623
> URL: https://issues.jboss.org/browse/JBIDE-19623
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: arquillian
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [Arquillian]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 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 from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. 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 Arquillian 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
[JBoss JIRA] (JBIDE-18460) 'Add type to deployment' quickfix doesn't work with abstract classes
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18460?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-18460:
----------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.Alpha2)
> 'Add type to deployment' quickfix doesn't work with abstract classes
> --------------------------------------------------------------------
>
> Key: JBIDE-18460
> URL: https://issues.jboss.org/browse/JBIDE-18460
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.2.0.CR1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: 4.3.x
>
>
> Steps to reproduce:
> - create an abstract Arquillian JUnit test with a deployment method
> - create an Arquillian JUnit test extending the previous created abstract class
> - add a type not included in the deployment method to the test created in the step 2
> The "Type is not included in any deployment" marker will be created properly
> - call the "Add type to deployment" quickfix
> You will get the "Cannot find a deployment method" dialog.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18587) Error when opening a java file that is not in the project build path
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18587?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-18587:
----------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Alpha2)
> Error when opening a java file that is not in the project build path
> --------------------------------------------------------------------
>
> Key: JBIDE-18587
> URL: https://issues.jboss.org/browse/JBIDE-18587
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Beta1
>
>
> I had the following error in the Error Logs when opening a Java file that was not in the build path:
> {code}
> Java Model Exception: Java Model Status [src/test/generated/com/sample [in sample is not on its project's build path]
> at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:544)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:247)
> at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
> at org.eclipse.jdt.internal.core.Openable.openAncestors(Openable.java:505)
> at org.eclipse.jdt.internal.core.CompilationUnit.openAncestors(CompilationUnit.java:1173)
> at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:241)
> at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:557)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:294)
> at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:280)
> at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:235)
> at org.eclipse.jdt.internal.core.JavaElement.getChildrenOfType(JavaElement.java:249)
> at org.eclipse.jdt.internal.core.CompilationUnit.getTypes(CompilationUnit.java:920)
> at org.eclipse.jdt.internal.core.CompilationUnit.getAllTypes(CompilationUnit.java:605)
> at org.jboss.tools.arquillian.ui.internal.commands.ArquillianPropertyTester.test(ArquillianPropertyTester.java:53)
> at org.eclipse.core.internal.expressions.Property.test(Property.java:58)
> at org.eclipse.core.internal.expressions.TestExpression.evaluate(TestExpression.java:99)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.AdaptExpression.evaluate(AdaptExpression.java:106)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateOr(CompositeExpression.java:68)
> at org.eclipse.core.internal.expressions.OrExpression.evaluate(OrExpression.java:21)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.IterateExpression.evaluate(IterateExpression.java:189)
> at org.eclipse.core.internal.expressions.CompositeExpression.evaluateAnd(CompositeExpression.java:53)
> at org.eclipse.core.internal.expressions.WithExpression.evaluate(WithExpression.java:72)
> at org.eclipse.e4.ui.internal.workbench.ContributionsAnalyzer.isVisible(ContributionsAnalyzer.java:256)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.computeVisibility(ContributionRecord.java:166)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.updateVisibility(ContributionRecord.java:96)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:188)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRendererFilter.updateElementVisibility(MenuManagerRendererFilter.java:199)
> at org.eclipse.ui.internal.WorkbenchWindow$8.run(WorkbenchWindow.java:699)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3983)
> at org.eclipse.swt.widgets.Display.observerProc(Display.java:3573)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:4989)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5367)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1101)
> at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2044)
> at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1093)
> at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2563)
> at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2012)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5627)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:221)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2105)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2329)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5691)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5128)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5277)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3655)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:484)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19620) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Birt]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19620?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-19620:
-------------------------------------
Assignee: Snjezana Peco
> For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Birt]
> ---------------------------------------------------
>
> Key: JBIDE-19620
> URL: https://issues.jboss.org/browse/JBIDE-19620
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Alpha2
>
>
> For JBIDE 4.3.0.Alpha2 [Birt]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha2
> [Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
> 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 from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
> mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Alpha2x
> git push origin jbosstools-4.3.0.Alpha2x
> {code}
> 5. 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 Birt 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