[JBoss JIRA] (JBIDE-13609) 'Show in Forge Console' option is missing in context menu
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13609?page=com.atlassian.jira.plugi... ]
Koen Aers commented on JBIDE-13609:
-----------------------------------
Hi Vlado, your findings are correct. The 'Show In Forge' functionality is only available in the 'Java EE', 'Java' and 'JBoss' perspectives. It's easy to add them to the 'Resource' and 'Web Development' perspectives but that would be a new feature (or an extension of an existing feature) rather than a bug.
I can see the usefulness of the feature in the 'Web Development' perspective (and maybe also in the 'Resource' perspective, but I would not hold back the Beta1 release for this and postpone it to Beta2. WDYT?
> 'Show in Forge Console' option is missing in context menu
> ---------------------------------------------------------
>
> Key: JBIDE-13609
> URL: https://issues.jboss.org/browse/JBIDE-13609
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.1.0.Alpha1
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Fix For: 4.1.0.Beta1
>
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14654) org.jboss.tools.openshift.egit.test: remove forked MockSytemReader
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-14654:
----------------------------------------
Summary: org.jboss.tools.openshift.egit.test: remove forked MockSytemReader
Key: JBIDE-14654
URL: https://issues.jboss.org/browse/JBIDE-14654
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.1.0.Beta1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.0.Beta2
When testing egits operations (commit, push, etc.) we're using a MockSystemReader we forked from jgit.
The MockSystemReader in jgit is now perfectly suitable for us, we should kill our fork and switch to the one provided in jgit.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBDS-2642) h2 database driver creation problems/questions
by Tomas Remes (JIRA)
Tomas Remes created JBDS-2642:
---------------------------------
Summary: h2 database driver creation problems/questions
Key: JBDS-2642
URL: https://issues.jboss.org/browse/JBDS-2642
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 7.0.0.Beta1
Reporter: Tomas Remes
Attachments: error.log
I am quite confused about creating driver definition for h2 database. First question is: Shouldn't be h2 part of "Available driver templates" (or Vendor filter or whatsoever) list ???
I tried to use "Generic JDBC driver" otion for this and basically I wasn't able to do that, because of following error:
{noformat}
An error has occurred. See error log for more details.
Widget is disposed
{noformat}
Reproducible by following steps:
1. Choose "Generic JDBC driver"
2. Click "Add" button. (you need to choose db type again)
3. Switch to "JAR list" tab.
4. Add h2 driver jar (e.g. the one from EAP 6.1).
5. You need to specify "Drive class definiton".
6. Go with "org.h2.Driver".
7. Notice the error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBDS-2642) h2 database driver creation problems/questions
by Tomas Remes (JIRA)
[ https://issues.jboss.org/browse/JBDS-2642?page=com.atlassian.jira.plugin.... ]
Tomas Remes updated JBDS-2642:
------------------------------
Attachment: error.log
Attaching error log. This could be Eclipse issue. I am not really sure...
> h2 database driver creation problems/questions
> ----------------------------------------------
>
> Key: JBDS-2642
> URL: https://issues.jboss.org/browse/JBDS-2642
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 7.0.0.Beta1
> Reporter: Tomas Remes
> Attachments: error.log
>
>
> I am quite confused about creating driver definition for h2 database. First question is: Shouldn't be h2 part of "Available driver templates" (or Vendor filter or whatsoever) list ???
> I tried to use "Generic JDBC driver" otion for this and basically I wasn't able to do that, because of following error:
> {noformat}
> An error has occurred. See error log for more details.
> Widget is disposed
> {noformat}
> Reproducible by following steps:
> 1. Choose "Generic JDBC driver"
> 2. Click "Add" button. (you need to choose db type again)
> 3. Switch to "JAR list" tab.
> 4. Add h2 driver jar (e.g. the one from EAP 6.1).
> 5. You need to specify "Drive class definiton".
> 6. Go with "org.h2.Driver".
> 7. Notice the error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBDS-2642) h2 database driver creation problems/questions
by Tomas Remes (JIRA)
[ https://issues.jboss.org/browse/JBDS-2642?page=com.atlassian.jira.plugin.... ]
Tomas Remes updated JBDS-2642:
------------------------------
Description:
I am quite confused about creating driver definition for h2 database. First question is: Shouldn't be h2 part of "Available driver templates" (or Vendor filter or whatsoever) list ???
I tried to use "Generic JDBC driver" option for this and basically I wasn't able to do that, because of following error:
{noformat}
An error has occurred. See error log for more details.
Widget is disposed
{noformat}
Reproducible by following steps:
1. Choose "Generic JDBC driver"
2. Click "Add" button. (you need to choose db type again)
3. Switch to "JAR list" tab.
4. Add h2 driver jar (e.g. the one from EAP 6.1).
5. You need to specify "Drive class definiton".
6. Go with "org.h2.Driver".
7. Notice the error.
was:
I am quite confused about creating driver definition for h2 database. First question is: Shouldn't be h2 part of "Available driver templates" (or Vendor filter or whatsoever) list ???
I tried to use "Generic JDBC driver" otion for this and basically I wasn't able to do that, because of following error:
{noformat}
An error has occurred. See error log for more details.
Widget is disposed
{noformat}
Reproducible by following steps:
1. Choose "Generic JDBC driver"
2. Click "Add" button. (you need to choose db type again)
3. Switch to "JAR list" tab.
4. Add h2 driver jar (e.g. the one from EAP 6.1).
5. You need to specify "Drive class definiton".
6. Go with "org.h2.Driver".
7. Notice the error.
> h2 database driver creation problems/questions
> ----------------------------------------------
>
> Key: JBDS-2642
> URL: https://issues.jboss.org/browse/JBDS-2642
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 7.0.0.Beta1
> Reporter: Tomas Remes
> Attachments: error.log
>
>
> I am quite confused about creating driver definition for h2 database. First question is: Shouldn't be h2 part of "Available driver templates" (or Vendor filter or whatsoever) list ???
> I tried to use "Generic JDBC driver" option for this and basically I wasn't able to do that, because of following error:
> {noformat}
> An error has occurred. See error log for more details.
> Widget is disposed
> {noformat}
> Reproducible by following steps:
> 1. Choose "Generic JDBC driver"
> 2. Click "Add" button. (you need to choose db type again)
> 3. Switch to "JAR list" tab.
> 4. Add h2 driver jar (e.g. the one from EAP 6.1).
> 5. You need to specify "Drive class definiton".
> 6. Go with "org.h2.Driver".
> 7. Notice the error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14653) Feature and plugins info is incorrect
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14653?page=com.atlassian.jira.plugi... ]
Vlado Pakan updated JBIDE-14653:
--------------------------------
Attachment: aerogearfeature.png
aerogearplugins.png
> Feature and plugins info is incorrect
> -------------------------------------
>
> Key: JBIDE-14653
> URL: https://issues.jboss.org/browse/JBIDE-14653
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.0.Beta1
> Environment: JBT 4.1.0.Beta1-v20130526-0812-B258
> Reporter: Vlado Pakan
> Priority: Critical
> Fix For: 4.1.0.Beta1
>
> Attachments: aerogearfeature.png, aerogearplugins.png
>
>
> 1. Open Help > About Eclipse > Installation Details
> 2. Select Installed Software tab
> 3. Select either org.jboss.tools.aerogear.hybrid.feature.feature.group or org.jboss.tools.aerogear.hybrid.feature.source.feature.group
> ERROR: Feature description should contain "based mobile" instead "basedmobile"
> !aerogearfeature.png!
> 4. Select Plug-ins tab
> 5. Type aerogear ni filter
> ERROR: Aerogear plugins has neither provider or Plug-in name. Version of org.jboss.tools.aerogear.hybrid.cordova is 2.7.0 all the others plug-ins has version 1.0.0.Beta1... I don't know if this is correct
> !aerogearplugins.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months
[JBoss JIRA] (JBIDE-14653) Feature and plugins info is incorrect
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-14653:
-----------------------------------
Summary: Feature and plugins info is incorrect
Key: JBIDE-14653
URL: https://issues.jboss.org/browse/JBIDE-14653
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.1.0.Beta1
Environment: JBT 4.1.0.Beta1-v20130526-0812-B258
Reporter: Vlado Pakan
Priority: Critical
Fix For: 4.1.0.Beta1
Attachments: aerogearfeature.png, aerogearplugins.png
1. Open Help > About Eclipse > Installation Details
2. Select Installed Software tab
3. Select either org.jboss.tools.aerogear.hybrid.feature.feature.group or org.jboss.tools.aerogear.hybrid.feature.source.feature.group
ERROR: Feature description should contain "based mobile" instead "basedmobile"
!aerogearfeature.png!
4. Select Plug-ins tab
5. Type aerogear ni filter
ERROR: Aerogear plugins has neither provider or Plug-in name. Version of org.jboss.tools.aerogear.hybrid.cordova is 2.7.0 all the others plug-ins has version 1.0.0.Beta1... I don't know if this is correct
!aerogearplugins.png!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 11 months