January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19034) Bump org.jboss.tools.forge.m2e version

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19034?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19034: ----------------------------------- Fix Version/s: 4.2.2.Final (was: 4.3.0.Alpha1) > Bump org.jboss.tools.forge.m2e version > --------------------------------------- > > Key: JBIDE-19034 > URL: https://issues.jboss.org/browse/JBIDE-19034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.2.Final > > > org.jboss.tools.forge.m2e version needs to become 1.1.2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19034) Bump org.jboss.tools.forge.m2e version

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19034?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19034: ---------------------------------------- This is actually was committed to 4.2.x today - https://github.com/jbosstools/jbosstools-forge/commit/c33c78a65bc243aac73... > Bump org.jboss.tools.forge.m2e version > --------------------------------------- > > Key: JBIDE-19034 > URL: https://issues.jboss.org/browse/JBIDE-19034 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.1.Final > Reporter: Koen Aers > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.2.2.Final > > > org.jboss.tools.forge.m2e version needs to become 1.1.2 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3275) Add wildfly archetypes to JBoss Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3275?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3275: ----------------------------------- when deploying the html5 project, http://localhost:8080/html5/img/wildfly_400x130.jpg is missing > Add wildfly archetypes to JBoss Central > --------------------------------------- > > Key: JBDS-3275 > URL: https://issues.jboss.org/browse/JBDS-3275 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: central, requirements > Reporter: Burr Sutter > Assignee: Fred Bricon > Fix For: 8.1.0.GA > > > Supporting Wildfly archetypes with JBoss Central. As an Java EE developer, I need to be able to switch between EAP and Wildfly, when I select Wildfly, the archetype needs to correctly include the right BOMs, where all artifacts are available only on Maven Central. > This should include both the Java EE Web Project, Java EE EAR Project, and HTML5 Project -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-360) earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-360?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-360. ----------------------------------- Verified with JBDSIS 8.0.0.Beta1 and JBTIS 4.2.0.Beta2 > earlyaccess setup leaks jboss.org and development urls into stable/devstudio urls > --------------------------------------------------------------------------------- > > Key: JBTIS-360 > URL: https://issues.jboss.org/browse/JBTIS-360 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > Fix For: 8.0.0.Beta1 > > Attachments: ea-jbdsis-fix.png, ea-jbdsis.png, ea-jbtis-fix.png, ea-jbtis.png > > > using IS earlyacces from jbosstools stable release I get: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > That should never get into stable. > Only the earlyaccess site should be added here. > For developer studio it gets even messier. > https://www.dropbox.com/s/3wlmw9hd6pey4mc > /Screenshot%202014-11-12%2013.13.34.png?dl=0 > https://devstudio.redhat.com/earlyaccess/8.0/ is correct, but then there are these two added sites that should not be present: > http://download.jboss.org/jbosstools/updates/development/luna/central/int... > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/ > This should be rolledback ASAP since users that install these will now get all the latest development updates instead of just the tested and verified to be in earlyaccess bits. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-361) JBDS IS 8 Beta1 features not showing up in EA view

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-361?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-361. ----------------------------------- Verified with JBDS-IS 8.0.0.Beta2 > JBDS IS 8 Beta1 features not showing up in EA view > -------------------------------------------------- > > Key: JBTIS-361 > URL: https://issues.jboss.org/browse/JBTIS-361 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 8.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.Beta1 > > Attachments: JBDS800-marketplace+JBDSIS800Beta1_EA-empty.png, JBDS800-marketplace+JBDSIS800Beta1_EA-found.png, JBT420-marketplace+JBTIS420Beta1_EA-empty.png, JBT420-marketplace+JBTIS420Beta1_EA-found.png > > > 0. Install JBDS 8 from Marketplace. Restart. > 1. Open Central > Software Update tab > [x] Enable Early Access > Yes > 2. Install the JBDS IS connectors, including: > * JBoss Business Process and Rules Development > * JBoss Data Virtualization Development > * JBoss Integration and SOA Development > * JBoss SOA 5.x Development > 3. Restart. Open Central and uncheck the [ ] Enable Early Access box - note the 4 connectors listed as being EA are: > * JBoss Business Process and Rules Development > * JBoss Data Virtualization Development > * JBoss Integration and SOA Development > * JBoss SOA 5.x Development > Hit OK. > 4. Open Help > About and verify the Fuse, Teiid, Modeshape and SwitchYard icons are shown, among others. > 5. Click Installation Details > Installed Software and verify Fuse, BPMN2, BPEL, Drools, Guvnor, etc. are all installed. > 6. Select the JBoss Central tab. Note that the list of EA features installed is empty. > !JBDS800-marketplace+JBDSIS800Beta1_EA-empty.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19035) Fix Connection refactor to support v2 and v3 connections

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19035?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-19035: ------------------------------------- Assignee: Jeff Cantrill > Fix Connection refactor to support v2 and v3 connections > -------------------------------------------------------- > > Key: JBIDE-19035 > URL: https://issues.jboss.org/browse/JBIDE-19035 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19035) Fix Connection refactor to support v2 and v3 connections

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19035: ------------------------------------- Summary: Fix Connection refactor to support v2 and v3 connections Key: JBIDE-19035 URL: https://issues.jboss.org/browse/JBIDE-19035 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Reporter: Jeff Cantrill -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-381) Update JDV components for JBDSIS 8.0.0.GA/ 4.2.0.Final

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-381?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-381: ---------------------------------- ModeShape update: https://github.com/jbosstools/jbosstools-integration-stack/commit/76479bc... > Update JDV components for JBDSIS 8.0.0.GA/ 4.2.0.Final > ------------------------------------------------------ > > Key: JBTIS-381 > URL: https://issues.jboss.org/browse/JBTIS-381 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: modeshape, teiid > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.0.GA, 4.2.0.Final > > > Update the stack with .Final versions of JBoss Data Virtualization components. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3256) JBoss specific Docker Tooling (Basic Integration)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3256?page=com.atlassian.jira.plugin.... ] Andre Dietisheim reassigned JBDS-3256: -------------------------------------- Assignee: Xavier Coulon (was: Andre Dietisheim) > JBoss specific Docker Tooling (Basic Integration) > ------------------------------------------------- > > Key: JBDS-3256 > URL: https://issues.jboss.org/browse/JBDS-3256 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Reporter: Burr Sutter > Assignee: Xavier Coulon > > Goal: to allow the Eclipse user to easily discover, pull, run, deploy my .war or .ear to it, stop, commit, push for docker images/containers. > Expected end-user flow 1: > 0) Installation - assumes boot2docker pre-installed on the end-user's machine > 1) I, the Java developer, need to browse a docker registry (either DockerHub or private registry), identify the image that I wish to have local and download (docker pull) for that image+tag. > 2) Assumption: the docker image includes not only the operating system + JVM but also the EAP, Wildfly or Tomcat installed in a 'known' location. > 3) I start (docker run) the image which auto-starts the embedded app server > 4) I can then deploy my .war or .ear to the running app server > 5) I can restart the running app server in debug mode and run the debugger > 6) I can undeploy and redeploy my .war or .ear > 7) I can stop/restart the running, embedded app server > 8) I can then commit (docker commit) > 9) then I can publish my changes (docker push) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 3 months

1
0
0 / 0

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

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-3258?page=com.atlassian.jira.plugin.... ] Andre Dietisheim reassigned JBDS-3258: -------------------------------------- Assignee: Xavier Coulon (was: Max Rydahl Andersen) > 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 > 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, 3 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 January 2015