[JBoss JIRA] (JBDS-3293) Marketplace Entry: Integration Stack (Fuse Focused)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3293?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3293:
-------------------------------------------
Moved this back to JBDS since this is a requirement for JBDS 8.0.next to be tracked for release notes and not just a JBTIS issue.
> Marketplace Entry: Integration Stack (Fuse Focused)
> ---------------------------------------------------
>
> Key: JBDS-3293
> URL: https://issues.jboss.org/browse/JBDS-3293
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
>
> As a Fuse Focused, integration + Java developer, I have had troubles in finding the Camel and supportive Eclipse plugins. An Eclipse Marketplace entry that advertises those capabilities will help me to find the right tooling and to successfully install it into my pre-installed and currently running Eclipse.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3293) Marketplace Entry: Integration Stack (Fuse Focused)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3293?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3293:
--------------------------------------
Project: Developer Studio (JBoss Developer Studio) (was: JBoss Tools Integration Stack)
Key: JBDS-3293 (was: JBTIS-373)
Workflow: CDW v1 (was: GIT Pull Request workflow )
Docs QE Status: NEW
Target Release: 8.0.2.GA (was: 8.0.0.GA)
> Marketplace Entry: Integration Stack (Fuse Focused)
> ---------------------------------------------------
>
> Key: JBDS-3293
> URL: https://issues.jboss.org/browse/JBDS-3293
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Reporter: Burr Sutter
>
> As a Fuse Focused, integration + Java developer, I have had troubles in finding the Camel and supportive Eclipse plugins. An Eclipse Marketplace entry that advertises those capabilities will help me to find the right tooling and to successfully install it into my pre-installed and currently running Eclipse.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3259) Markdown Viewer
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3259?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3259:
--------------------------------------
Component/s: 3rd-party-certification
> Markdown Viewer
> ---------------
>
> Key: JBDS-3259
> URL: https://issues.jboss.org/browse/JBDS-3259
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: 3rd-party-certification
> Reporter: Burr Sutter
> Priority: Critical
> Attachments: markdowneditor.gif
>
>
> Most of our quickstarts and example applications come with a Markdown readme.md that provides the end-user with key instructions on how to execute the example. In today's Eclipse/JBDS, this markdown file is normally displayed as pure source/text. Ideally, the file would render just as it does for github, including with "clickable links".
> The current poor "wrapping" is problematic for readability
> http://www.screencast.com/t/n4Zvwv0W
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3267) JSON Editor
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3267?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3267:
--------------------------------------
Component/s: jsp/jsf/xml/html source editing
> JSON Editor
> -----------
>
> Key: JBDS-3267
> URL: https://issues.jboss.org/browse/JBDS-3267
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
>
> As a Java or Java EE developer, who wishes to test my JAX-RS endpoints as well as edit various JSON files, I need an editor that formats the nested curly braces, helps me to insure that I am not missing (nor have extra) curly braces, missing quotes, helps me to know when to use square brackets, etc. Ideally, the Eclipse Outline view would also work if I am editing a .json file.
> Ideally, we would support both a full JSON editor as well as working within the Web Services Tester.
> http://screencast.com/t/hWAtlMytghV6
> http://screencast.com/t/h4VWGyAuqw
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[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 updated JBDS-3258:
--------------------------------------
Component/s: openshift
> 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: Max Rydahl Andersen
>
> 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, 4 months
[JBoss JIRA] (JBDS-3279) Screencasts: Maven
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3279?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-3279:
--------------------------------------
Component/s: documentation
maven
> Screencasts: Maven
> ------------------
>
> Key: JBDS-3279
> URL: https://issues.jboss.org/browse/JBDS-3279
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, maven
> Reporter: Burr Sutter
>
> As a Java EE developer, new to using Eclipse + Maven, I need short, sub-6 minute screencasts of individual key Maven focused use cases, so that I can better understand how Maven is integrated into the Eclipse + Java EE development workflow.
> Use cases include:
> - creation of a new project and its pom.xml, with the pom.xml editor
> - dependencies adds/removes
> - Import maven projects - from a SVN or Git repo
> - multi-module maven projects
> - run on server
> - package vs install
> - update - the magic "update project" that helps get Eclipse and Maven back into agreement
> - adjust profiles - address the Arquillian profile
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3289) JBoss Central proxy wizards need to recognize early access.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3289?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3289:
-------------------------------------------
ouch - thats bad. real bad ;/
does this also happen if you use the install via drag'n'drop of install links ?
> JBoss Central proxy wizards need to recognize early access.
> -----------------------------------------------------------
>
> Key: JBDS-3289
> URL: https://issues.jboss.org/browse/JBDS-3289
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 8.0.2.GA
> Reporter: Paul Leacu
> Assignee: Fred Bricon
> Priority: Blocker
> Attachments: ea1.png
>
>
> Using a JBoss Central proxy wizard that references an early access feature will install that feature correctly even if the "Early Access Enabled" checkbox is unchecked.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18954) JAX-RS Web Services in Project Explorer does not show properly inherited metadata
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18954?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-18954:
----------------------------------
Description:
I have an interface with annotated JAX-RS methods (HTTP method type, path, consumes...) CarResourceInterface and implementation of this interface CarResourceImpl. Inheriting all metadata related to one method should affect processing of this JAX-RS web services - new values from Impl should be used and probably it would be good to show it also in JAX-RS Web Services node in Project Explorer view. Currently there are shown only interface JAX-RS web services and any change in Impl is ignored in this view.
There are chunk of codes for interface and implementation. At first I was having only interface and it's web service has been shown in JAX-RS Web Services. Then I have added implementation and overrode interface but still in JAX-RS Web Services the interface is shown.
{code:title=CarResource.java}
@Path("car")
public interface CarResource {
@GET
@Path("/{id:[0-9][0-9]*}")
@Produces({ "application/xml", "application/json" })
public Response findById(@PathParam("id") final Long id);
}
{code}
{code:title=CarResourceImpl.java}
public class CarResourceImpl implements CarResource {
@GET
@Path("/{carid:a[0-9]*}")
@Produces({ "text", "application/json" })
public Response findById(@PathParam("carid") final Long id) {
//TODO: retrieve the car
return null;
}
}
{code}
was:
I have an interface with annotated JAX-RS methods (HTTP method type, path, consumes...) CarResourceInterface and implementation of this interface CarResourceImpl. Inheriting all metadata related to one method should affect processing of this JAX-RS web services - new values from Impl should be used and probably it would be good to show it also in JAX-RS Web Services node in Project Explorer view. Currently there are shown only interface JAX-RS web services and any change in Impl is ignored in this view.
> JAX-RS Web Services in Project Explorer does not show properly inherited metadata
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-18954
> URL: https://issues.jboss.org/browse/JBIDE-18954
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.1.Final
> Reporter: Marián Labuda
> Assignee: Xavier Coulon
> Labels: jax-rs
> Fix For: 4.3.x
>
>
> I have an interface with annotated JAX-RS methods (HTTP method type, path, consumes...) CarResourceInterface and implementation of this interface CarResourceImpl. Inheriting all metadata related to one method should affect processing of this JAX-RS web services - new values from Impl should be used and probably it would be good to show it also in JAX-RS Web Services node in Project Explorer view. Currently there are shown only interface JAX-RS web services and any change in Impl is ignored in this view.
> There are chunk of codes for interface and implementation. At first I was having only interface and it's web service has been shown in JAX-RS Web Services. Then I have added implementation and overrode interface but still in JAX-RS Web Services the interface is shown.
> {code:title=CarResource.java}
> @Path("car")
> public interface CarResource {
>
> @GET
> @Path("/{id:[0-9][0-9]*}")
> @Produces({ "application/xml", "application/json" })
> public Response findById(@PathParam("id") final Long id);
> }
> {code}
> {code:title=CarResourceImpl.java}
> public class CarResourceImpl implements CarResource {
> @GET
> @Path("/{carid:a[0-9]*}")
> @Produces({ "text", "application/json" })
> public Response findById(@PathParam("carid") final Long id) {
> //TODO: retrieve the car
> return null;
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months