[JBoss JIRA] (JBIDE-19605) Avoid need for multiple javax.servlet
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19605?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-19605.
-----------------------------------
Resolution: Done
[~bfitzpat],
Kicked another build job and it passed. The errors during the previous build were due to some files not properly removed on an NFS partition. This kind of problem happens from time to time, sadly.
> Avoid need for multiple javax.servlet
> -------------------------------------
>
> Key: JBIDE-19605
> URL: https://issues.jboss.org/browse/JBIDE-19605
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform, webservices
> Affects Versions: 4.3.0.Alpha2
> Reporter: Mickael Istria
> Assignee: Brian Fitzpatrick
> Fix For: LATER
>
> Attachments: org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JavaElement11ChangedProcessingTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.JaxrsMetamodelChangedProcessorTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.builder.ResourceChangedProcessingTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs11ElementFactoryTestCase.txt, org.jboss.tools.ws.jaxrs.core.internal.metamodel.domain.Jaxrs20EndpointTestCase.txt
>
>
> We currently use 2 different version of javax.servlet bundle. We'd rather decide on sticking to 1.
> {code}
> On 04/15/2015 11:56 PM, Nick Boldt wrote:
> > Just wondering if anyone knows WHY we include javax.servlet 3.0.0 and
> > 3.1.0 in JBDS.
> > More importantly... SHOULD we be including both? Or can we just include
> > 3.1.0 and drop 3.0.0?
> I have JBDS installed from installer, which basically ran a p2 director. And I get jetty 3.0.0 and jetty 3.1.0. Than means that while resolving what to installed, p2 has to keep both versions of javax.servlet. That's definitely a sign that our dependency chain currently need both (or p2 wouldn't have installed both).
> So I've tried the ultimate test:
> $ cd jbdevstudio-9.0.0.Alpha2/studio
> $ rm plugins/javax.servlet_3.0.0*
> $ ./jbdevstudio
> And saw
> !ENTRY org.jboss.tools.ws.ui 4 0 2015-04-16 10:35:49.110
> !MESSAGE FrameworkEvent ERROR
> !STACK 0
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.ws.ui [967]
> Unresolved requirement: Import-Package: javax.servlet; version="[2.4.0,3.0.0)"
> at org.eclipse.osgi.container.Module.start(Module.java:434)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Fun thing is that the javax.servlet_3.0.0 actually exports packages in version 2.6.0, whereas javax.servlet_3.1.0 exports them in version 3.1.0.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19728) Easy Import - The first and second screens in the dialog should be merged into one
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19728?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-19728.
------------------------------------
Resolution: Done
The new version of easymport, which is available in nightlies since mid-last week, has an improved wizard dialog which should be easier to understand.
> Easy Import - The first and second screens in the dialog should be merged into one
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-19728
> URL: https://issues.jboss.org/browse/JBIDE-19728
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: easymport
> Affects Versions: 4.3.0.Alpha2
> Reporter: Len DiMaggio
> Assignee: Mickael Istria
> Attachments: import_1.png, import_2.png
>
>
> See the attached screenshots - in the first dialog screen (1/6), the user is presented with a largely blank display. After he/she selects "next" the dialog (2/6) shows the projects that are eligible to be imported.
> Why not simply skip the first screen and start with the second?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19346) jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19346?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19346:
----------------------------------------
Thanks for this good change!
> jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-19346
> URL: https://issues.jboss.org/browse/JBIDE-19346
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> While promoting JBT 4.3.0.Alpha1 to /development/ I realized that jbosstools-earlyaccess.properties contains old versions. We should have tern/angular 0.8 in there, right [~dgolovin] ?
> {code}
> $➔ cat jbosstools-earlyaccess.properties
> #Mon Sep 01 18:54:14 CEST 2014
> org.eclipse.vjet.rt.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> org.jboss.tools.arquillian.feature.feature.group=[1.1.2.CR1-v20140830-0003-B63,1.1.2.CR1-v20140830-0003-B63]
> org.eclipse.vjet.extmod.jsdt.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> org.eclipse.vjet.web.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> org.eclipse.vjet.extmod.dltk.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> org.eclipse.vjet.codegen.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> tern-server-nodejs-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110]
> org.eclipse.vjet.eclipse.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> tern.eclipse.ide.tools.feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110]
> tern.eclipse.ide.server.nodejs.embed.feature.group=[0.5.0.201408272110,0.5.0.201408272110]
> org.eclipse.vjet.vsf.domkit.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> org.eclipse.equinox.server.jetty.feature.group=[1.1.100.v20140416-1649,1.1.100.v20140416-1649]
> org.eclipse.vjet.extmod.rhino.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> tern-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110]
> org.eclipse.vjet.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656]
> tern-jsdt-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110]
> angularjs-eclipse-feature.feature.group=[0.5.0.201408281218,0.5.0.201408281218]
> {code}
> -- http://download.jboss.org/jbosstools/discovery/staging/4.3.0.Alpha1/jboss...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19784) Make runtime detection available from server view ?
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-19784:
-------------------------------------------
Summary: Make runtime detection available from server view ?
Key: JBIDE-19784
URL: https://issues.jboss.org/browse/JBIDE-19784
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Reporter: Max Rydahl Andersen
Assignee: Max Rydahl Andersen
runtime detection is great but it's rather hidden.
Idea is to add a search glass to server view to trigger runtime detection.
Wdyt?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months