[JBoss JIRA] (JBDS-2915) Change default server type to EAP 6.1+
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBDS-2915?page=com.atlassian.jira.plugin.... ]
Rob Stryker resolved JBDS-2915.
-------------------------------
Resolution: Done
pushed to master. It was a one line change and not very notable so no pull request. Basically just used a different constant.
> Change default server type to EAP 6.1+
> --------------------------------------
>
> Key: JBDS-2915
> URL: https://issues.jboss.org/browse/JBDS-2915
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: server
> Affects Versions: 8.0.0.Alpha2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 8.0.0.Beta1
>
>
> I noticed that when I create a new server (Server View -> New -> New Server), the default server type selected when you open the dialog for the first time is EAP 6.0. It should be updated to EAP 6.1+ which is the latest.
--
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, 2 months
[JBoss JIRA] (JBDS-2852) Database/source/connection Usability
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ]
Barry LaFond edited comment on JBDS-2852 at 2/20/14 9:14 AM:
-------------------------------------------------------------
Teiid Designer utilizes DTP by:
* relying on the Connection Profile data persistence for basic data source properties
* DTP's JDBC connection framework for data preview (query execution, SQL Editor and SQL results display)
However we've found that to our data sources typically include a finer definition of the source metadata. For instance,
* Our JDBC importer is typically used to pull partial or selected tables, views and procedures from within a schema. In Teiid Designer, we persist this additional information within the source model metadata. Ideally additional metadata should probably be persisted with the data source definition. The JDBC CP's do have a simple "filter" option, but overall it's insufficient.
* For LDAP, WS, XML and flat file data sources, the DTP CP's are simplistic. Our importers require additional user inputs to set-up/define a useable data source. For these sources, we have yet to persist this additional data.
The Teiid Connection import option involves utilizing a deployed data source which Teiid connects to, pulls in the schema defined for that source and converts it into a common Teiid DDL format. This is a DDL dialect tailored to needs of the Teiid runtime metadata. Teiid Designer can then consume the DDL and convert directly to our EMF metamodels.
A part of that importer framework *does* provide generic Data Source deployment functionality and it is currently not tied to connection profiles.
was (Author: blafond):
Teiid Designer utilizes DTP by:
* relying on the Connection Profile data persistence for basic data source properties
* DTP's JDBC connection framework for data preview (query execution, SQL Editor and SQL results display)
However we've found that to our data sources typically include a finer definition of the source metadata. For instance, out JDBC importer is typically used to pull partial or selected tables, views and procedures from within a schema. In Teiid Designer, we persist this additional information within the source model metadata. This additional metadata should probably JDBC sources tyipcally require define a data source
*
> 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
> 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 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, 2 months
[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:
-----------------------------
Epic Name: Datasource Usability (was: Datasource usability)
> 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
> 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 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, 2 months
[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-16355 at 2/20/14 9:04 AM:
-------------------------------------------------------------
Everywhere you refer to a $\{version} variable, could you also set a suggested value right above it, so users know what to use?
Thus:
{code}
version=4.2.0.Alpha2 # no a, b, c suffix here
branch=4.2.0.x # for Final builds, use 4.2.x
/home/fts/project/jboss/JBossTools/JBossTools$\{branch}/zz_Release_Notes_$\{version}.readme.html
{code}
was (Author: nickboldt):
Everywhere you refer to a \${version} variable, could you also set a suggested value right above it, so users know what to use?
Thus:
{code}
version=4.2.0.Alpha2 # no a, b, c suffix here
branch=4.2.0.x # for Final builds, use 4.2.x
/home/fts/project/jboss/JBossTools/JBossTools\${branch}/zz_Release_Notes_${version}.readme.html
{code}
> replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-16355
> URL: https://issues.jboss.org/browse/JBIDE-16355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> Re: files like:
> http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/...
> {quote}
> (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees
> (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;)
> (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these.
> (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean.
> (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;)
> (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this.
> {quote}
> Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query.
> That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final).
> We can also produce a query for both JBT and JBDS.
--
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, 2 months
[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-16355 at 2/20/14 9:03 AM:
-------------------------------------------------------------
Everywhere you refer to a \${version} variable, could you also set a suggested value right above it, so users know what to use?
Thus:
{code}
version=4.2.0.Alpha2 # no a, b, c suffix here
branch=4.2.0.x # for Final builds, use 4.2.x
/home/fts/project/jboss/JBossTools/JBossTools\${branch}/zz_Release_Notes_${version}.readme.html
{code}
was (Author: nickboldt):
Everywhere you refer to a \${version} variable, could you also set a suggested value right above it, so users know what to use?
Thus:
{code}
version=4.2.0.Alpha2 # no a, b, c suffix here
/home/fts/project/jboss/JBossTools/JBossTools${branch}/zz_Release_Notes_${version}.readme.html
{code}
> replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-16355
> URL: https://issues.jboss.org/browse/JBIDE-16355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> Re: files like:
> http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/...
> {quote}
> (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees
> (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;)
> (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these.
> (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean.
> (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;)
> (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this.
> {quote}
> Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query.
> That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final).
> We can also produce a query for both JBT and JBDS.
--
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, 2 months
[JBoss JIRA] (JBDS-2852) Database/source/connection Usability
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/JBDS-2852?page=com.atlassian.jira.plugin.... ]
Barry LaFond commented on JBDS-2852:
------------------------------------
Teiid Designer utilizes DTP by:
* relying on the Connection Profile data persistence for basic data source properties
* DTP's JDBC connection framework for data preview (query execution, SQL Editor and SQL results display)
However we've found that to our data sources typically include a finer definition of the source metadata. For instance, out JDBC importer is typically used to pull partial or selected tables, views and procedures from within a schema. In Teiid Designer, we persist this additional information within the source model metadata. This additional metadata should probably JDBC sources tyipcally require define a data source
*
> 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
> 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 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, 2 months
[JBoss JIRA] (JBIDE-16355) replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16355?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16355:
------------------------------------
Everywhere you refer to a \${version} variable, could you also set a suggested value right above it, so users know what to use?
Thus:
{code}
version=4.2.0.Alpha2 # no a, b, c suffix here
/home/fts/project/jboss/JBossTools/JBossTools${branch}/zz_Release_Notes_${version}.readme.html
{code}
> replace release_notes*.html files posted to sourceforge w/ link directly to JIRA query
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-16355
> URL: https://issues.jboss.org/browse/JBIDE-16355
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.2.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> Re: files like:
> http://sourceforge.net/projects/jboss/files/JBossTools/JBossTools4.2.0.x/...
> {quote}
> (2014-01-14 13:55:54) nickboldt: desire to produce the file is clearly no longer urgent, so I could open a JIRA asking to trash it from the rel guide requirement for JBT 4.2 and see who disagrees
> (2014-01-14 13:56:04) maxandersen: yeah - and I keep saying: please dont use mixed camelcases but they keep occuring ;)
> (2014-01-14 13:56:25) maxandersen: yeah I would just post a jira query IMO for these.
> (2014-01-14 13:56:56) maxandersen: dont use mixed camelcases for artifacts urls I mean.
> (2014-01-14 13:57:58) maxandersen: interesting - *1* hit on google for jbide zz_release_notes ;)
> (2014-01-14 13:58:34) maxandersen: so yeah, jira query ftw for this.
> {quote}
> Instead of producing a snapshot from JIRA as a canned HTML page, we should for JBT 4.2 / JBDS 8 simply link to a query.
> That way too we can have a query for "just this milestone" and "all changes in the 4.2.x stream (alpha1, alpha2, beta1, cr1, final).
> We can also produce a query for both JBT and JBDS.
--
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, 2 months
[JBoss JIRA] (JBIDE-16604) JBoss BIRT Integration isn't compatible with BIRT 4.3
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16604?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-16604:
---------------------------------------
I still can't reproduce the issue.
It is possible that you have a problem with your server (a read-only directory or something similar that).
Could you try to deploy your application on some other server - JBoss AS 4.2.3 or SOA 5.3.1 installed from scratch, for instance?
What OS do you use?
> JBoss BIRT Integration isn't compatible with BIRT 4.3
> -----------------------------------------------------
>
> Key: JBIDE-16604
> URL: https://issues.jboss.org/browse/JBIDE-16604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: birt
> Affects Versions: 4.2.0.Alpha2
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Fix For: 4.2.0.Beta1
>
> Attachments: components.xml, faces-config.xml, jboss-web.xml, pages.xml, test.rptdesign, test1.rptdesign, viewer.properties, web.xml
>
>
--
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, 2 months