[JBoss JIRA] (JBIDE-23080) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [JavaEE]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23080:
-------------------------------------------
Summary: For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [JavaEE]
Key: JBIDE-23080
URL: https://issues.jboss.org/browse/JBIDE-23080
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: seam2, cdi, cdi-extensions, jsf
Reporter: Friendly Jira Robot
Priority: Blocker
For JBIDE 4.4.1.Final [JavaEE]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
[Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.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.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.1.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.1.x{color}* branch:
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.4.1.x
git push origin jbosstools-4.4.1.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{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 JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-4040) For JBDS 10.1.0.GA: Prepare for 4.4.1.Final / 10.1.0.GA
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBDS-4040:
-----------------------------------------
Summary: For JBDS 10.1.0.GA: Prepare for 4.4.1.Final / 10.1.0.GA
Key: JBDS-4040
URL: https://issues.jboss.org/browse/JBDS-4040
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Task
Components: installer
Reporter: Friendly Jira Robot
Priority: Blocker
Fix For: 10.1.0.GA
For JBDS 10.1.0.GA: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
[Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.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.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.1.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.1.x{color}* branch:
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.4.1.x
git push origin jbosstools-4.4.1.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{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...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23070) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23070:
-------------------------------------------
Summary: For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA
Key: JBIDE-23070
URL: https://issues.jboss.org/browse/JBIDE-23070
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Friendly Jira Robot
Priority: Blocker
Fix For: 4.4.1.Final
For JBIDE 4.4.1.Final: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
[Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.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.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.1.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.1.x{color}* branch:
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.4.1.x
git push origin jbosstools-4.4.1.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{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...]
See also: JBDS-4040
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23071) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Aerogear]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23071:
-------------------------------------------
Summary: For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Aerogear]
Key: JBIDE-23071
URL: https://issues.jboss.org/browse/JBIDE-23071
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid, cordovasim
Reporter: Friendly Jira Robot
Priority: Blocker
For JBIDE 4.4.1.Final [Aerogear]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
[Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.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.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.1.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.1.x{color}* branch:
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.4.1.x
git push origin jbosstools-4.4.1.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{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 task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23072) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Central Discovery]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23072:
-------------------------------------------
Summary: For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [Central Discovery]
Key: JBIDE-23072
URL: https://issues.jboss.org/browse/JBIDE-23072
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: central-update
Reporter: Friendly Jira Robot
Priority: Blocker
For JBIDE 4.4.1.Final [Central Discovery]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
[Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.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.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.1.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.1.x{color}* branch:
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.4.1.x
git push origin jbosstools-4.4.1.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{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 Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23073) For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [VPE]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created JBIDE-23073:
-------------------------------------------
Summary: For JBIDE 4.4.1.Final: Prepare for 4.4.1.Final / 10.1.0.GA [VPE]
Key: JBIDE-23073
URL: https://issues.jboss.org/browse/JBIDE-23073
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Friendly Jira Robot
Priority: Blocker
For JBIDE 4.4.1.Final [VPE]: Please perform the following tasks:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.4.1.Final or 10.1.0.GA
[Unresolved JIRAs with fixVersion = 4.4.1.Final, 10.1.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.1.Final-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.4.1.Final-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:orange}4.4.1.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.1.x{color}* branch:
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.4.1.x
git push origin jbosstools-4.4.1.x
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.4.1.Final-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.4.1.x{color}* branch, too.
4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{code}
4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.1.Final
{code}
mvn clean verify -Dtpc.version=4.60.1.Final
{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 VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23068) Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23068?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-23068:
----------------------------------------
@Dimitrii: Do you use the target platform as explained in https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... ? Do you have the other necessary components (such jbosstools-base) also available in your workspace as projects? Those are necessary to resolve all bundles and extension points.
> Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23068
> URL: https://issues.jboss.org/browse/JBIDE-23068
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Dmitrii Bocharov
>
> Builds in terminal (mvn clean install) run successfully. However in eclipse i have 3 errors for jjbt-base and 3 for jbt-server:
> jbt-base:
> Unknown extension point: 'org.eclipse.mylyn.tasks.bugs.support' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.mylyn.tasks.core.templates' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.ui.activities' plugin.xml in /org.jboss.tools.common.model.ui.capabilities
> jbt-server:
> Bundle 'org.jboss.ide.eclipse.as.management.eap61plus' cannot be resolved in /org.jboss.tools.as.management.itests/META-INF
> Unknown extension point: 'org.eclipse.help.contexts' in /org.jboss.ide.eclipse.as.doc.user
> Unknown extension point: 'org.eclipse.help.toc' in /org.jboss.ide.eclipse.as.doc.user
> [dbocharo@dbocharo jbosstools-target-platforms]$ git pull upstream 4.60.x
> From https://github.com/jbosstools/jbosstools-target-platforms
> * branch 4.60.x -> FETCH_HEAD
> Already up-to-date.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23008) openshift.cdk.feature.source missing from JBT site; causes baseline check to fail
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23008?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-23008.
---------------------------------
JBT update site contains CDK feature now, closing.
> openshift.cdk.feature.source missing from JBT site; causes baseline check to fail
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23008
> URL: https://issues.jboss.org/browse/JBIDE-23008
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift, updatesite
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> Since the weekend (after I published an AM3 build into /neon/staging/updates/):
> {code}
> [INFO] --- tycho-source-plugin:0.25.0:plugin-source (plugin-source) @ org.jboss.tools.openshift.cdk.server ---
> [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT-sources.jar
> [INFO]
> [INFO] --- target-platform-configuration:0.25.0:target-platform (default-target-platform) @ org.jboss.tools.openshift.cdk.server ---
> [INFO]
> [INFO] --- tycho-packaging-plugin:0.25.0:package-plugin (default-package-plugin) @ org.jboss.tools.openshift.cdk.server ---
> [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- tycho-p2-plugin:0.25.0:p2-metadata-default (default-p2-metadata-default) @ org.jboss.tools.openshift.cdk.server ---
> [WARNING] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml: baseline and build artifacts have same version but different contents
> [INFO] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml
> The main artifact has been replaced with the baseline version.
> The following attached artifacts are not present in the baseline and have been removed: [sources]{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23068) Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23068?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-23068:
----------------------------------------
Looks like a TP issue? Either something wrong in Dmitrii dev environment or in our TP I guess.
> Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23068
> URL: https://issues.jboss.org/browse/JBIDE-23068
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Dmitrii Bocharov
>
> Builds in terminal (mvn clean install) run successfully. However in eclipse i have 3 errors for jjbt-base and 3 for jbt-server:
> jbt-base:
> Unknown extension point: 'org.eclipse.mylyn.tasks.bugs.support' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.mylyn.tasks.core.templates' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.ui.activities' plugin.xml in /org.jboss.tools.common.model.ui.capabilities
> jbt-server:
> Bundle 'org.jboss.ide.eclipse.as.management.eap61plus' cannot be resolved in /org.jboss.tools.as.management.itests/META-INF
> Unknown extension point: 'org.eclipse.help.contexts' in /org.jboss.ide.eclipse.as.doc.user
> Unknown extension point: 'org.eclipse.help.toc' in /org.jboss.ide.eclipse.as.doc.user
> [dbocharo@dbocharo jbosstools-target-platforms]$ git pull upstream 4.60.x
> From https://github.com/jbosstools/jbosstools-target-platforms
> * branch 4.60.x -> FETCH_HEAD
> Already up-to-date.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23068) Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23068?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-23068:
-----------------------------------
Component/s: target-platform
> Unknown extension points and bundles can't be resolved in jbt-base and jbt-server
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23068
> URL: https://issues.jboss.org/browse/JBIDE-23068
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Reporter: Dmitrii Bocharov
>
> Builds in terminal (mvn clean install) run successfully. However in eclipse i have 3 errors for jjbt-base and 3 for jbt-server:
> jbt-base:
> Unknown extension point: 'org.eclipse.mylyn.tasks.bugs.support' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.mylyn.tasks.core.templates' in /org.jboss.tools.common.mylyn
> Unknown extension point: 'org.eclipse.ui.activities' plugin.xml in /org.jboss.tools.common.model.ui.capabilities
> jbt-server:
> Bundle 'org.jboss.ide.eclipse.as.management.eap61plus' cannot be resolved in /org.jboss.tools.as.management.itests/META-INF
> Unknown extension point: 'org.eclipse.help.contexts' in /org.jboss.ide.eclipse.as.doc.user
> Unknown extension point: 'org.eclipse.help.toc' in /org.jboss.ide.eclipse.as.doc.user
> [dbocharo@dbocharo jbosstools-target-platforms]$ git pull upstream 4.60.x
> From https://github.com/jbosstools/jbosstools-target-platforms
> * branch 4.60.x -> FETCH_HEAD
> Already up-to-date.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months