June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17493) Duplicate certification ids not permitted in Core and EA plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17493?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17493: ------------------------------- Fix Version/s: 4.2.0.Beta2 > Duplicate certification ids not permitted in Core and EA plugins > ---------------------------------------------------------------- > > Key: JBIDE-17493 > URL: https://issues.jboss.org/browse/JBIDE-17493 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: respin-b > Fix For: 4.2.0.Beta2 > > > {code} > Duplicate certification id 'com.jboss.jbds.discovery.certification.earlyaccess': declaring sources: org.jboss.tools.central.discovery.earlyaccess_4.2.0.Beta3_v20140601_2325_B2769.jar_3125701552832129620.jar, org.jboss.tools.central.discovery_4.2.0.Beta3_v20140601_2325_B2769.jar_7047926761596595680.jar > Duplicate category id 'org.jboss.tools.central.discovery.a.web': declaring sources: org.jboss.tools.central.discovery.earlyaccess_4.2.0.Beta3_v20140601_2325_B2769.jar_3125701552832129620.jar, org.jboss.tools.central.discovery_4.2.0.Beta3_v20140601_2325_B2769.jar_7047926761596595680.jar > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17493) Duplicate certification ids not permitted in Core and EA plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17493?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-17493: ---------------------------------- Assignee: Nick Boldt > Duplicate certification ids not permitted in Core and EA plugins > ---------------------------------------------------------------- > > Key: JBIDE-17493 > URL: https://issues.jboss.org/browse/JBIDE-17493 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: respin-b > Fix For: 4.2.0.Beta2 > > > {code} > Duplicate certification id 'com.jboss.jbds.discovery.certification.earlyaccess': declaring sources: org.jboss.tools.central.discovery.earlyaccess_4.2.0.Beta3_v20140601_2325_B2769.jar_3125701552832129620.jar, org.jboss.tools.central.discovery_4.2.0.Beta3_v20140601_2325_B2769.jar_7047926761596595680.jar > Duplicate category id 'org.jboss.tools.central.discovery.a.web': declaring sources: org.jboss.tools.central.discovery.earlyaccess_4.2.0.Beta3_v20140601_2325_B2769.jar_3125701552832129620.jar, org.jboss.tools.central.discovery_4.2.0.Beta3_v20140601_2325_B2769.jar_7047926761596595680.jar > {code} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3055) cannot install Arquillian into JBDS because of missing Sapphire dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3055?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3055. ---------------------------- Fix Version/s: 8.0.0.Beta2 Resolution: Done New Central EA TP contains Arquillian dependencies: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget... > cannot install Arquillian into JBDS because of missing Sapphire dependency > -------------------------------------------------------------------------- > > Key: JBDS-3055 > URL: https://issues.jboss.org/browse/JBDS-3055 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: discovery > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 8.0.0.Beta2 > > > JBT TP contains org.eclipse.sapphire, because Arquillian depends on it. > JBDS TP does not (it also lacks Tern). > So, when we create a TP for JBoss Central Early Access, it must include: > * Arquillian > ** Sapphire + org.objectweb.asm > * AngularJS > ** Tern.java > * VJET > ** org.w3c.dom.events > Because we don't have a mirror of Sapphire (it's included in Luna), we need to either create a TP now and publish it here [1], or create a mirror site in requirements/, and link that mirror from [1]. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17278) Add AngularJS-eclipse 0.2.0 to Central Early Access

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17278?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-17278. -------------------------------- Resolution: Done Added to TP site: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget... Added to EA Discovery plugin for JBT & JBDS: https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools... https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... To see this in Central, you may need these options: {code} -vmargs -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/jbosstools-directory.xml -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/nightly/core/4.2.luna/ -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/ {code} > Add AngularJS-eclipse 0.2.0 to Central Early Access > --------------------------------------------------- > > Key: JBIDE-17278 > URL: https://issues.jboss.org/browse/JBIDE-17278 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central, target-platform > Affects Versions: 4.2.0.Beta2 > Reporter: Victor Rubezhny > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.2.0.Beta2 > > Attachments: AngularJS16x16.png, AngularJS32x32.png > > > We should provide an ability to install AngularJS-eclipse v.0.2.0 through Central > There is no released or latest stable version, so we should take a copy from http://oss.opensagres.fr/angularjs-eclipse/0.2.0-SNAPSHOT/ Update Site. > [~nickboldt], please let me know if you need something more that just a link to Update Site. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3055) cannot install Arquillian into JBDS because of missing Sapphire dependency

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3055?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3055: ----------------------------- Description: JBT TP contains org.eclipse.sapphire, because Arquillian depends on it. JBDS TP does not (it also lacks Tern). So, when we create a TP for JBoss Central Early Access, it must include: * Arquillian ** Sapphire + org.objectweb.asm * AngularJS ** Tern.java * VJET ** org.w3c.dom.events Because we don't have a mirror of Sapphire (it's included in Luna), we need to either create a TP now and publish it here [1], or create a mirror site in requirements/, and link that mirror from [1]. [1] http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget... was: JBT TP contains org.eclipse.sapphire, because Arquillian depends on it. JBDS TP does not (it also lacks Tern). So, when we create a TP for JBoss Central Early Access, it must include: * Arquillian ** Sapphire + org.objectweb.asm * AngularJS ** Tern.java * VJET Because we don't have a mirror of Sapphire (it's included in Luna), we need to either create a TP now and publish it here [1], or create a mirror site in requirements/, and link that mirror from [1]. [1] http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget... > cannot install Arquillian into JBDS because of missing Sapphire dependency > -------------------------------------------------------------------------- > > Key: JBDS-3055 > URL: https://issues.jboss.org/browse/JBDS-3055 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: discovery > Affects Versions: 8.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > > JBT TP contains org.eclipse.sapphire, because Arquillian depends on it. > JBDS TP does not (it also lacks Tern). > So, when we create a TP for JBoss Central Early Access, it must include: > * Arquillian > ** Sapphire + org.objectweb.asm > * AngularJS > ** Tern.java > * VJET > ** org.w3c.dom.events > Because we don't have a mirror of Sapphire (it's included in Luna), we need to either create a TP now and publish it here [1], or create a mirror site in requirements/, and link that mirror from [1]. > [1] http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget... -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2852) Database/source/connection Usability

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2852: ---------------------------------- Just got spammed by Jiralint because this issue has no owner. Who should own this issue? Is it something in scope for JBDS 8? Assigning to [~burrsutter] for now. If that's wrong and it should be assigned to Server (Rob), Forge (Koen), or Teiid Designer (Barry), please adjust it accordingly. > Database/source/connection Usability > ------------------------------------ > > Key: JBDS-2852 > URL: https://issues.jboss.org/browse/JBDS-2852 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: integration, requirements > Reporter: Burr Sutter > Assignee: Burr Sutter > Labels: QE_JBDS80_needinfo > > Connecting to a database from within JBDS/Eclipse is a multi-step, multi-screen, potentially error-prone challenge. > Forge is involved as it can generate entities from schema > Datasources are needed in/on AS/Wildfly/EAP in order for the project deploy > Persistence.xml may needed to be tweaked for the datasource > End-user would like to navigate the schema in the DTP/Hibernate Tools, interactively review the data and there was once a feature for viewing an ORM diagram that I seem to have forgotten how it is displayed. > What happens when a project that needs a database connection is imported into the IDE? > This was partially addressed with > https://issues.jboss.org/browse/JBIDE-15263 > Let's see if we can continue to improve the workflow by reducing steps, making it more obvious what steps are required (e.g. hey developer, get the mysql driver .jar), auto generating the -ds.xml, with a decent explanation for the end-user to follow. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2852) Database/source/connection Usability

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2852: ----------------------------- Assignee: Burr Sutter > Database/source/connection Usability > ------------------------------------ > > Key: JBDS-2852 > URL: https://issues.jboss.org/browse/JBDS-2852 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Security Level: Public(Everyone can see) > Components: integration, requirements > Reporter: Burr Sutter > Assignee: Burr Sutter > Labels: QE_JBDS80_needinfo > > Connecting to a database from within JBDS/Eclipse is a multi-step, multi-screen, potentially error-prone challenge. > Forge is involved as it can generate entities from schema > Datasources are needed in/on AS/Wildfly/EAP in order for the project deploy > Persistence.xml may needed to be tweaked for the datasource > End-user would like to navigate the schema in the DTP/Hibernate Tools, interactively review the data and there was once a feature for viewing an ORM diagram that I seem to have forgotten how it is displayed. > What happens when a project that needs a database connection is imported into the IDE? > This was partially addressed with > https://issues.jboss.org/browse/JBIDE-15263 > Let's see if we can continue to improve the workflow by reducing steps, making it more obvious what steps are required (e.g. hey developer, get the mysql driver .jar), auto generating the -ds.xml, with a decent explanation for the end-user to follow. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-280) Update JBT IS TP build to latest tycho (and discover missing dependencies!)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-280?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-280 at 6/1/14 1:35 PM: ---------------------------------------------------------- Updated the PR, and I'm closer to a win, but have realized that newer Tycho doesn't like 0.0.0 versions in .target files: {code} [ERROR] You requested to install 'org.hibernate.eclipse.feature.feature.group [0.0.0]' but it could not be found {code} So... need to pre-process the .target files to embed correct version numbers in them., ie., like this: {code} targetFile=integration-stack-base.target mvn -U org.jboss.tools.tycho-plugins:target-platform-utils:0.19.0-SNAPSHOT:fix-versions -DtargetFile=${targetFile} rm -f ${targetFile} *_update_hints.txt mv -f ${targetFile}{_fixedVersion.target,} {code} was (Author: nickboldt): Updated the PR, and I'm closer to a win, but have realized that newer Tycho doesn't like 0.0.0 versions in .target files: {code} [ERROR] You requested to install 'org.hibernate.eclipse.feature.feature.group [0.0.0]' but it could not be found {code} So... need to pre-process the .target files to embed correct version numbers in them., ie., like this: {code} targetFile=integration-stack-base.target mvn -U org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions -DtargetFile=${targetFile} rm -f ${targetFile} *_update_hints.txt mv -f ${targetFile}{_fixedVersion.target,} {code} > Update JBT IS TP build to latest tycho (and discover missing dependencies!) > --------------------------------------------------------------------------- > > Key: JBTIS-280 > URL: https://issues.jboss.org/browse/JBTIS-280 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.2.0.Alpha1-TP > Reporter: Nick Boldt > > Wanted to see if the JBT IS TP could fetch sources, and it can. As it was building, I noticed that you're using Tycho 0.18.1 (not 0.20.0 or 0.21.0-SNAPSHOT) and a very old version of org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0.CR2. > So, I bumped you up to 0.20.0 and 0.19.0-SNAPSHOT, and got this error: > {code} > Unable to satisfy dependency from > org.springframework.osgi.io 1.2.1 to > package org.springframework.util [2.5.6,4.0.0).; > No solution found because the > problem is unsatisfiable. > {code} > Attached is a PR which shows what I tried, how it failed, and what I tried to do to fix it. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-280) Update JBT IS TP build to latest tycho (and discover missing dependencies!)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-280?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-280: ---------------------------------- Updated the PR, and I'm closer to a win, but have realized that newer Tycho doesn't like 0.0.0 versions in .target files: {code} [ERROR] You requested to install 'org.hibernate.eclipse.feature.feature.group [0.0.0]' but it could not be found {code} So... need to pre-process the .target files to embed correct version numbers in them., ie., like this: {code} targetFile=integration-stack-base.target mvn -U org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0-SNAPSHOT:fix-versions -DtargetFile=${targetFile} rm -f ${targetFile} *_update_hints.txt mv -f ${targetFile}{_fixedVersion.target,} {code} > Update JBT IS TP build to latest tycho (and discover missing dependencies!) > --------------------------------------------------------------------------- > > Key: JBTIS-280 > URL: https://issues.jboss.org/browse/JBTIS-280 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.2.0.Alpha1-TP > Reporter: Nick Boldt > > Wanted to see if the JBT IS TP could fetch sources, and it can. As it was building, I noticed that you're using Tycho 0.18.1 (not 0.20.0 or 0.21.0-SNAPSHOT) and a very old version of org.jboss.tools.tycho-plugins:target-platform-utils:0.16.0.CR2. > So, I bumped you up to 0.20.0 and 0.19.0-SNAPSHOT, and got this error: > {code} > Unable to satisfy dependency from > org.springframework.osgi.io 1.2.1 to > package org.springframework.util [2.5.6,4.0.0).; > No solution found because the > problem is unsatisfiable. > {code} > Attached is a PR which shows what I tried, how it failed, and what I tried to do to fix it. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3033) Missing RichFaces maven archetypes

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3033?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3033: ------------------------------ Fix Version/s: 8.0.0.Beta3 > Missing RichFaces maven archetypes > ---------------------------------- > > Key: JBDS-3033 > URL: https://issues.jboss.org/browse/JBDS-3033 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: central, maven > Affects Versions: 8.0.0.Beta1 > Reporter: Juraj Húska > Fix For: 8.0.0.Beta3 > > > There is no RichFaces archetype available for selection, when trying to create a maven project. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2014