[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ]
Snjezana Peco edited comment on JBIDE-15499 at 11/1/13 1:01 PM:
----------------------------------------------------------------
[~rhopp] Are you sure you don't use an older version of the JBoss Central plugin?
To check the version of the central plugin, you can try the following:
- open the Console view
- select the Host OSGi console
- enter
ss org.jboss.tools.central
JBDS 7.1.0 Beta1a includes org.jboss.tools.central_1.2.2.Beta1-v20131025-1922-B102
Do you get an exception when dropping the URL into the Eclipse/JBDS toolbar or into the Eclipse/JBDS menu area?
[~nickboldt] What Linux distribution are you using?
was (Author: snjeza):
<a href="https://issues.jboss.org/secure/ViewProfile.jspa?name=rhopp" class="user-hover" rel="rhopp">Radim Hopp</a> Are you sure you don't use an older version of the JBoss Central plugin?
To check the version of the central plugin, you can try the following:
- open the Console view
- select the Host OSGi console
- enter
ss org.jboss.tools.central
JBDS 7.1.0 Beta1a includes org.jboss.tools.central_1.2.2.Beta1-v20131025-1922-B102
Do you get an exception when dropping the URL into the Eclipse/JBDS toolbar or into the Eclipse/JBDS menu area?
<a href="https://issues.jboss.org/secure/ViewProfile.jspa?name=nickboldt " class="user-hover" rel="rhopp">Nick Boldt</a> What Linux distribution are you using?
> Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-15499
> URL: https://issues.jboss.org/browse/JBIDE-15499
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Max Rydahl Andersen
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.1.1.Beta1
>
>
> usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds.
> Similar to eclipse marketplace for marketplace urls something like:
> * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or
> * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra...
> would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e"
> This would allow drag'n'drop install from html docs.
> Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing.
--
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, 5 months
[JBoss JIRA] (JBIDE-15764) NPE while generating entities in JPA project
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15764?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15764:
----------------------------------
Labels: respin-b (was: )
> NPE while generating entities in JPA project
> --------------------------------------------
>
> Key: JBIDE-15764
> URL: https://issues.jboss.org/browse/JBIDE-15764
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS 7.1.0.Beta1, L64, OpenJDK 1.6
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
>
> java.lang.NullPointerException
> at org.jboss.tools.hibernate.jpt.core.internal.context.AddGeneratedClassesJob$2.evaluate(AddGeneratedClassesJob.java:133)
> at org.jboss.tools.hibernate.jpt.core.internal.context.AddGeneratedClassesJob$2.evaluate(AddGeneratedClassesJob.java:1)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.loadNext(FilteringIterator.java:80)
> at org.eclipse.jpt.common.utility.internal.iterator.FilteringIterator.<init>(FilteringIterator.java:56)
> at org.eclipse.jpt.common.utility.internal.iterator.IteratorTools.filter(IteratorTools.java:758)
> at org.eclipse.jpt.common.utility.internal.iterable.FilteringIterable.iterator(FilteringIterable.java:48)
> at org.eclipse.jpt.common.utility.internal.iterable.TransformationIterable.iterator(TransformationIterable.java:50)
> at org.eclipse.jpt.common.utility.internal.iterable.IterableTools.size(IterableTools.java:301)
> at org.jboss.tools.hibernate.jpt.core.internal.context.AddGeneratedClassesJob.addNewClassRefs(AddGeneratedClassesJob.java:99)
> at org.jboss.tools.hibernate.jpt.core.internal.context.AddGeneratedClassesJob.runInWorkspace(AddGeneratedClassesJob.java:90)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
--
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, 5 months
[JBoss JIRA] (JBIDE-12860) JAX-RS validation problems are not linked
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12860?page=com.atlassian.jira.plugi... ]
Xavier Coulon commented on JBIDE-12860:
---------------------------------------
hello [~akazakov] !
thanks for the time you spent on tracing the problem down into WST !
Can you open an issue for the common validator refactoring you need to to and link that issue with this one, so that we can keep track of it ?
Thanks !
Best regards,
> JAX-RS validation problems are not linked
> -----------------------------------------
>
> Key: JBIDE-12860
> URL: https://issues.jboss.org/browse/JBIDE-12860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.0.0.Beta1
> Reporter: Jaroslav Jankovič
> Assignee: Alexey Kazakov
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
>
> This case now fails:
> STEP: Create jaxrs problem with Application problem (Multiple application definition - one class extending Application and one application servlet definition in web.xml)
> STEP: comment servlet definition in web.xml
> ASSERT: problem marker in web.xml disappears
> ASSERT: problem marker in application class disappears
> FAIL: problem marker in application class doesn't disappear, because problem markers are not linked now -> project has to be built to correctly remove both problem markers
--
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, 5 months
[JBoss JIRA] (JBIDE-15833) Cannot import multiple quickstarts at once
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15833?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-15833:
-----------------------------------
Component/s: project-examples
> Cannot import multiple quickstarts at once
> ------------------------------------------
>
> Key: JBIDE-15833
> URL: https://issues.jboss.org/browse/JBIDE-15833
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.1.Beta1
> Reporter: Peter Palaga
>
> Steps to reproduce:
> * Go to New > Example > JBoss Tools > Project Examples > Portal Applications
> * Select two or more quickstarts, e.g. Simplest Hello World Portlet and JSF2 Hello World Portlet
> * Click Next
> Issue 1:
> * Not OK: the screen contains just empty form controls
> * Expected: The screen should probably show the requirements of the first of the selected quickstarts.
> Issue 2, after clicking Next for the second time:
> * Not OK: There is one more empty screen
> * Expected: no idea
> Issue 3, after clicking Next for the third time:
> * Not OK: There is a screen which has some meaningful entries in the Requirements list, but the Description is empty
> * Expected: There should be some description in the Description field.
> Issue 4, after clicking Next for the fourth time:
> * Not OK: the Finish button is disabled and there is no sign of a message why.
> * Expected: The Finish button should either be enabled or the form should say what is missing to enable the Button
> This is also reproducible on JBDS 7.1.0.Beta1-v20131026-0928-B470.
--
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, 5 months