February 2015 - jbosstools-issues

[JBoss JIRA] (JBDS-3328) generate/edit jboss modules content for easily deployment/config of jdbc driver

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3328?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3328: ----------------------------------- @rruss rejected JBDS-3291 > generate/edit jboss modules content for easily deployment/config of jdbc driver > ------------------------------------------------------------------------------- > > Key: JBDS-3328 > URL: https://issues.jboss.org/browse/JBDS-3328 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: server > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > > in EAP7-56 its asked: > "I can easily generate and deploy a JBoss Module from existing jars including JDBC Drivers and shared libraries. (Tooling to automatically generate module.xml and related artifacts by scanning classes from a library jar file, or pom.xml if provided e.g real life use case: creating modules for JDBC Type 4 Drivers )" > this would be nice to have and linked with our datasource wizards. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3291) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3291?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3291: ----------------------------- CDW release: - (was: ?) > Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project > --------------------------------------------------------------------------------------------------- > > Key: JBDS-3291 > URL: https://issues.jboss.org/browse/JBDS-3291 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: integration, requirements, server > Affects Versions: 8.0.0.GA > Reporter: Mustafa Musaji > Assignee: Max Rydahl Andersen > > If you have a POM for a project that defines the following > {code} > <project> > ... > <dependencyManagement> > <dependencies> > <dependency> > <groupId>org.jboss.bom</groupId> > <artifactId>eap6-supported-artifacts</artifactId> > <version>6.3.1.GA</version> > <scope>import</scope> > <type>pom</type> > </dependency> > </dependencies> > </dependencyManagement> > ... > <dependencies> > <dependency> > <groupId>commons-beanutils</groupId> > <artifactId>commons-beanutils</artifactId> > <scope>provided</scope> > </dependency> > </dependencies> > </project> > {code} > The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3291) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3291?page=com.atlassian.jira.plugin.... ] Burr Sutter updated JBDS-3291: ------------------------------ CDW pm_ack: - (was: ?) Status: New (was: New) > Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project > --------------------------------------------------------------------------------------------------- > > Key: JBDS-3291 > URL: https://issues.jboss.org/browse/JBDS-3291 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: integration, requirements, server > Affects Versions: 8.0.0.GA > Reporter: Mustafa Musaji > Assignee: Max Rydahl Andersen > > If you have a POM for a project that defines the following > {code} > <project> > ... > <dependencyManagement> > <dependencies> > <dependency> > <groupId>org.jboss.bom</groupId> > <artifactId>eap6-supported-artifacts</artifactId> > <version>6.3.1.GA</version> > <scope>import</scope> > <type>pom</type> > </dependency> > </dependencies> > </dependencyManagement> > ... > <dependencies> > <dependency> > <groupId>commons-beanutils</groupId> > <artifactId>commons-beanutils</artifactId> > <scope>provided</scope> > </dependency> > </dependencies> > </project> > {code} > The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3291) Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3291?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-3291: ----------------------------------- At this this time, based on my understanding, considering the fact that there is no 1-to-1 mapping between a Maven artifact declared in the pom.xml and a JBoss Module running in the app server, it would be very difficult to have a correctly generated jboss-deployment-structure.xml. Furthermore, it seems to me that the end-user should only populate the jboss-deployment-structure.xml to address non-normal scenarios (overriding an app server jar or using a jar that goes beyond Java EE and public API). Rejecting. > Support for auto generating jboss-deployment-structure based on JBoss Modules selected in a project > --------------------------------------------------------------------------------------------------- > > Key: JBDS-3291 > URL: https://issues.jboss.org/browse/JBDS-3291 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: integration, requirements, server > Affects Versions: 8.0.0.GA > Reporter: Mustafa Musaji > Assignee: Max Rydahl Andersen > > If you have a POM for a project that defines the following > {code} > <project> > ... > <dependencyManagement> > <dependencies> > <dependency> > <groupId>org.jboss.bom</groupId> > <artifactId>eap6-supported-artifacts</artifactId> > <version>6.3.1.GA</version> > <scope>import</scope> > <type>pom</type> > </dependency> > </dependencies> > </dependencyManagement> > ... > <dependencies> > <dependency> > <groupId>commons-beanutils</groupId> > <artifactId>commons-beanutils</artifactId> > <scope>provided</scope> > </dependency> > </dependencies> > </project> > {code} > The tooling should create a jboss-deployment-structure.xml that contains the "org.apache.commons.beanutils" dependency automatically. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18813) Convert JBoss Central to an HTML5 page

by Catherine Robson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18813?page=com.atlassian.jira.plugi... ] Catherine Robson commented on JBIDE-18813: ------------------------------------------ Updated Design Option A to include how it could downsize, remove the "add tooling capabilities" tab (that info is in "Learn about JBoss"). > Convert JBoss Central to an HTML5 page > -------------------------------------- > > Key: JBIDE-18813 > URL: https://issues.jboss.org/browse/JBIDE-18813 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.3.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.3.0.Beta1 > > Attachments: Central Design Concept A.bmml, Central Design Concept A.bmml, Central Design Concept A.bmml, Central Design Concept A.png, Central Design Concept B.bmml, Central Design Concept B.bmml, Central Design Concept B.png, Design concept C - Search centric layout.bmml, Design concept C - Search centric layout.png, Design Concept D - categories across top.bmml, Design Concept D - categories across top.bmml, Design Concept D - categories across top.png, JBoss Access Panel Concept.bmml, JBoss Access Panel Concept.png, JBoss Central User Stories and Flows.gliffy, Screen Shot 2015-01-16 at 4.38.58 PM.png > > > Central Page requires new capabilities : > - needs more customization (display content depending on user preferences) > - needs to scale with JBDS-IS, Fuse content > - access to more examples, with filtering capabilities > Given that the existing page is pretty hard to maintain and suffers from scalability/UI bugs, we're heading towards an HTML5 approach : > - use an embedded SWT Browser widget (or Java FX), depending on the platform compatibility > - webpage and its content could be served remotely (as zip), and downloaded locally for offline use. this would give us more flexibility to update the content. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19254) Include FeedHenry feature in Mobile Category

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19254?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19254 at 2/19/15 11:44 AM: -------------------------------------------------------------- FH added to 4.2.x JBT/JBDS aggregates here: https://github.com/jbosstools/jbosstools-build-sites/commit/20713ec35dd3f... https://github.com/jbdevstudio/jbdevstudio-product/commit/1ce0da73136fff5... New PR for adding feedhenry feature into existing JBT/JBDS Central connectors applied in 4.2.x branch: https://github.com/jbosstools/jbosstools-discovery/pull/265 was (Author: nickboldt): New PR for adding feedhenry feature into existing JBT/JBDS Central connectors applied in 4.2.x branch: https://github.com/jbosstools/jbosstools-discovery/pull/265 > Include FeedHenry feature in Mobile Category > -------------------------------------------- > > Key: JBIDE-19254 > URL: https://issues.jboss.org/browse/JBIDE-19254 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, updatesite > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.2.3.Beta1 > > > Currently the code base for FeedHenry integration is in github repository, but the build artefacts are not picked up by nightly job. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18846: ------------------------------------ Do you mean like having a yaml page listing all the projects / versions / streams ? If so, sure, but then we can't host it in github. It would have to move to tools.jboss.org, right? > create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs > ----------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18846 > URL: https://issues.jboss.org/browse/JBIDE-18846 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, website > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as: > builds (nightly, staging, dev, stable) > updates (nightly, staging, dev, stable) > Jenkins jobs > discovery sites (nightly, staging, dev, stable) > target platforms > etc. > And for each component, we can list: > build > update > Jenkins job > etc. > The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html > Unsure whether generated HTML (via script) or simple .adoc is better for this. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19330) Arquillian is missing icon in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19330?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19330: ------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Arquillian is missing icon in Central > ------------------------------------- > > Key: JBIDE-19330 > URL: https://issues.jboss.org/browse/JBIDE-19330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.3.0.Alpha1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Arquillian is missing icon in JBT in Central: > http://i.imgur.com/Lwwbovy.png -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3258) Docker Tooling (Advanced Integration)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3258: ------------------------------------------- to be clear - 0-4 is in my mind *nice to haves* not *must haves* for initial tooling. > Docker Tooling (Advanced Integration) > ------------------------------------- > > Key: JBDS-3258 > URL: https://issues.jboss.org/browse/JBDS-3258 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift, requirements > Reporter: Burr Sutter > Assignee: Xavier Coulon > > Once significant delta between the "basic" and advanced scenarios is that here I wish to custom craft my own docker images instead of using an existing one - where my custom crafted image includes my .war or .ear. > In addition to the basic integrations of pull, run, stop, commit and push > boot2docker init > boot2docker up > boot2docker down > boot2docker ip > docker run -d > docker ps > docker rm > docker rmi > docker build > End-user steps: > 0) assumes boot2docker has been dowloaded and installed > 1) boot2docker init : required to to insure boot2docker-vm is properly initialized > 2) boot2docker up : starts the VirtualBox boot2docker-vm > 3) boot2docker ip : returns the IP address - this will be vital when it comes to testing - it would need to be integrated with our Run - As on Docker capability. > 4) docker run -i -t -p 80:8080 jboss/wildfly -d : the -d means detached, I may need to run N containers simultaneously > 5) docker ps : allows me to see all my currently running containers > 6) docker rm : allows me to kill a currently running container > 7) docker rmi : allows me to remove a local image > 8) docker build : assumes that I have crafted a Dockerfile - this will create the local image - with my .war or .ear embedded > 9) docker run : this new created image > The docker build scenario can be triggered via a Maven plugin > The docker build scenario can also be triggered via an Eclipse menu option (like a Maven install) > We need to figure out the file-system layout so that the Dockerfile and the maven project are all nicely checked into git/svn. So that Jenkins can pick up this repository and perform an automated "docker build" (post Maven install) and then run all the appropriate unit, integration and functional tests. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19330) Arquillian is missing icon in Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19330?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19330: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 > Arquillian is missing icon in Central > ------------------------------------- > > Key: JBIDE-19330 > URL: https://issues.jboss.org/browse/JBIDE-19330 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.3.0.Alpha1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > Arquillian is missing icon in JBT in Central: > http://i.imgur.com/Lwwbovy.png -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 February 2015