[JBoss JIRA] (JBIDE-16651) Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding the RedHat Maven repo
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16651?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-16651:
-------------------------------------
PR to add essentialDependencies to stacks instead https://github.com/jboss-jdf/jdf-stack/pull/36
> Remove hard-coded enterprise dependency resolution for upcoming archetypes embedding the RedHat Maven repo
> ----------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-16651
> URL: https://issues.jboss.org/browse/JBIDE-16651
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven, project-examples
> Affects Versions: 4.1.1.Final
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 4.1.2.CR1
>
>
> In JBoss Central, when an Enterprise runtime is selected for any given Archetype, we check if the Red Hat Enterprise repository is available by trying to resolve a redhat version of org.jboss.spec:jboss-javaee-web-6.0. Then, if some essential dependencies are defined in stacks.yaml, we also try to resolve these. If the dependencies can't be resolved, a warning message appears with a link allowing users to add the RH repo to their Maven settings.xml
> Upcoming archetypes will have the Red Hat repository already added to the generated pom.xml, so adding it to settings.xml becomes unnecessary. However, we'd get false positive warning by trying to resolve org.jboss.spec:jboss-javaee-web-6.0 from the settings.xml *before* generating the archetype.
> Our goal is to remove the hardcoded check from MavenArtifactHelper and, when necessary, declare org.jboss.spec:jboss-javaee-web-6.0 as an essential dependency in stacks.yaml for *old* archetypes that do not add the RH repo to the gen'd pom.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, 1 month
[JBoss JIRA] (JBDS-2776) Support quickstarts in OpenShift UI
by Burr Sutter (JIRA)
[ https://issues.jboss.org/browse/JBDS-2776?page=com.atlassian.jira.plugin.... ]
Burr Sutter commented on JBDS-2776:
-----------------------------------
[~ldimaggio]There are no "default quickstarts" (at this time) - as each end-customer can establish the ones they wish to promote within their userbase. In other words, the customer will create his own list when he is setting up/configuring OpenShift itself - this step is completely outside of JBDS.
Think of it like this, the customer has the ability to upload his own custom projects into his own SVN, Git or CVS repo - when JBDS queries those repos - we will show the customer's list of projects. In this case, the customer will determine what quickstarts he wants, he will manually "upload" them during OpenShift installation/configuration and that is the list JBDS will query and display.
> Support quickstarts in OpenShift UI
> -----------------------------------
>
> Key: JBDS-2776
> URL: https://issues.jboss.org/browse/JBDS-2776
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: QE_JBDS80_needinfo
> Fix For: 8.0.0.GA
>
> Attachments: new-application-2.png
>
>
> OpenShift offers a comprehensive list of available cartridges and quickstarts In the Web-UI:
> !new-application-2.png!
> JBoss Tools/JBDS should offer the same to provide a smoother experience for newbie users.
--
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, 1 month
[JBoss JIRA] (JBIDE-13312) Unnecessary code generated in web.xml
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13312?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13312:
-------------------------------------------
[~petemuir] I have the code now working so that it generates the cleaner application class with the annotation as specified in JBIDE-13309. If the user WANTS to update the web.xml, how much of this stuff is necessary? It seems to run just fine with it in there and without it.
> Unnecessary code generated in web.xml
> -------------------------------------
>
> Key: JBIDE-13312
> URL: https://issues.jboss.org/browse/JBIDE-13312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.0.0.Final
> Reporter: Pete Muir
> Assignee: Brian Fitzpatrick
> Fix For: 4.2.x
>
>
> The new RESTful Webservice wizard is generating a load of unnecessary stuff in the endpoint
> {code}
> <servlet>
> <servlet-name>Resteasy</servlet-name>
> <servlet-class>org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher</servlet-class>
> </servlet>
> <servlet-mapping>
> <servlet-name>Resteasy</servlet-name>
> <url-pattern>/*</url-pattern>
> </servlet-mapping>
> <context-param>
> <param-name>javax.ws.rs.Application</param-name>
> <param-value>org.jboss.samples.rs.webservices.MyRESTApplication</param-value>
> </context-param>
> <listener>
> <listener-class>org.jboss.resteasy.plugins.server.servlet.ResteasyBootstrap</listener-class>
> </listener>
> {code}
> None of this is needed
--
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, 1 month
[JBoss JIRA] (JBIDE-16636) allow drop without dialog from palette
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16636?page=com.atlassian.jira.plugi... ]
Daniel Azarov commented on JBIDE-16636:
---------------------------------------
[~maxandersen], I faced some troubles when I tried to read Alt key:
There are two ways which I tried:
1. method dragOperationChanged in DropTargetListener - it works fine with Ctrl and Shift keys. It does not work with Alt key at all.
2. KeyListener - it works fine with any kind of key combinations, but it does not work during drag&drop at all.
One more thing - on Ubuntu if you press Alt and start dragging element from palette - Ubuntu will move current window. It looks like there is nothing we can do about it.
My suggestion is to use Shift instead.
WDYT?
> allow drop without dialog from palette
> --------------------------------------
>
> Key: JBIDE-16636
> URL: https://issues.jboss.org/browse/JBIDE-16636
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Daniel Azarov
> Fix For: 4.2.0.Beta1
>
>
> sometimes when demoing or just trying a few things quickly or dragging trivial elements it would be nice being able to not have the wizard dialog show up.
> could we make it so when holding in Alt it will not show the dialog but just do whatever clicking the finish button would directly do ?
--
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, 1 month
[JBoss JIRA] (JBDS-2862) During install, I should be able to create a new directory to install into
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-2862.
---------------------------------
Resolution: Done
> During install, I should be able to create a new directory to install into
> --------------------------------------------------------------------------
>
> Key: JBDS-2862
> URL: https://issues.jboss.org/browse/JBDS-2862
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Environment: Mac OS X
> Reporter: Jim Tyrrell
> Assignee: Denis Golovin
> Labels: jbds711
> Fix For: 7.1.1.CR1
>
> Attachments: 2013-12-19_1512.png, Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png
>
>
> See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install 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, 1 month
[JBoss JIRA] (JBDS-2862) During install, I should be able to create a new directory to install into
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2862?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2862:
-------------------------------------
Well, I cannot change anything, but workaround would be not using New Folder button. Just select folder where you want create new folder and type a name of new folder in File field. Select should be available after that and installer will create new folder for you.
It is not pretty ether, but at least there is no need to jump back and forth.
> During install, I should be able to create a new directory to install into
> --------------------------------------------------------------------------
>
> Key: JBDS-2862
> URL: https://issues.jboss.org/browse/JBDS-2862
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.CR1
> Environment: Mac OS X
> Reporter: Jim Tyrrell
> Assignee: Denis Golovin
> Labels: jbds711
> Fix For: 7.1.1.CR1
>
> Attachments: 2013-12-19_1512.png, Screen shot 2013-12-10 at 12.34.20 PM.png, Screen Shot 2013-12-10 at 3.11.08 PM.png, Select Target Folder_015.png
>
>
> See the attached screen shot, a create new folder button does not seem to exist anywhere to create a new folder/directory to install 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, 1 month