June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21850) Maven project has wrong context root set up after import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21850?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-21850. ------------------------------------ Resolution: Done Resolved with parent issue JBIDE-20687 > Maven project has wrong context root set up after import > -------------------------------------------------------- > > Key: JBIDE-21850 > URL: https://issues.jboss.org/browse/JBIDE-21850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, maven > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > Fix For: 4.4.0.Final > > > Importing maven project (in my case "servlet-security" from EAP quickstarts) via easymport has wrong context root (right click on project->Properties->Web Project Settings) configured. > Name of project is servlet-security, but web context root is jboss-servlet-security > This results into 404 when this project gets deployed to server. IDE opens url http://localhost:8080/jboss-servlet-security, but correct url is http://localhost:8080/servlet-security. > Note, that this does not happen when importing this project as existing maven project (not using easymport). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21850) Maven project has wrong context root set up after import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21850?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-21850: ---------------------------------------- A bunch of awesomeness. I'll make this one as resolved, put the links to JBIDE-20687 then. I'll keep it resolved and not closed to give the opportunity to [~rhopp] to verify on his favorite scenrii. > Maven project has wrong context root set up after import > -------------------------------------------------------- > > Key: JBIDE-21850 > URL: https://issues.jboss.org/browse/JBIDE-21850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > > Importing maven project (in my case "servlet-security" from EAP quickstarts) via easymport has wrong context root (right click on project->Properties->Web Project Settings) configured. > Name of project is servlet-security, but web context root is jboss-servlet-security > This results into 404 when this project gets deployed to server. IDE opens url http://localhost:8080/jboss-servlet-security, but correct url is http://localhost:8080/servlet-security. > Note, that this does not happen when importing this project as existing maven project (not using easymport). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21850) Maven project has wrong context root set up after import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21850?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-21850: ----------------------------------- Component/s: maven > Maven project has wrong context root set up after import > -------------------------------------------------------- > > Key: JBIDE-21850 > URL: https://issues.jboss.org/browse/JBIDE-21850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, maven > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > > Importing maven project (in my case "servlet-security" from EAP quickstarts) via easymport has wrong context root (right click on project->Properties->Web Project Settings) configured. > Name of project is servlet-security, but web context root is jboss-servlet-security > This results into 404 when this project gets deployed to server. IDE opens url http://localhost:8080/jboss-servlet-security, but correct url is http://localhost:8080/servlet-security. > Note, that this does not happen when importing this project as existing maven project (not using easymport). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20687) Deployed war is NOT the specified war name

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20687?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20687. --------------------------------- Resolution: Done Seems to work as expected now > Deployed war is NOT the specified war name > ------------------------------------------ > > Key: JBIDE-20687 > URL: https://issues.jboss.org/browse/JBIDE-20687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: ehsavoie Hugonnet > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.0.Final > > > The deployed war name is the *artifactId* and not the specified *warName* from the war plugin nor the *finalName*. > Sample pom.xml which exibits the issue > {code:xml}<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>org.glassfish-samples</groupId> > <artifactId>auction</artifactId> > <version>4.0-SNAPSHOT</version> > <packaging>war</packaging> > <name>WebSocket Auction Sample Application</name> > > <dependencies> > <dependency> > <groupId>javax</groupId> > <artifactId>javaee-api</artifactId> > <version>7.0</version> > <scope>provided</scope> > </dependency> > </dependencies> > > <build> > <finalName>websocket-auction</finalName> > <plugins> > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <version>3.1</version> > <configuration> > <source>1.8</source> > <target>1.8</target> > </configuration> > </plugin> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-war-plugin</artifactId> > <version>2.3</version> > <configuration> > <failOnMissingWebXml>false</failOnMissingWebXml> > <warName>websocket-auction</warName> > </configuration> > </plugin> > </plugins> > </build> > </project> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21850) Maven project has wrong context root set up after import

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21850?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21850: ------------------------------------- Looks like it's working now, at least with the helloworld project (which doesn't require setup on EAP). Smart import creates the helloworld project, context root is jboss-helloworld, deployment is jboss-helloworld.war, web page opens as expected > Maven project has wrong context root set up after import > -------------------------------------------------------- > > Key: JBIDE-21850 > URL: https://issues.jboss.org/browse/JBIDE-21850 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.1.CR1 > Reporter: Radim Hopp > > Importing maven project (in my case "servlet-security" from EAP quickstarts) via easymport has wrong context root (right click on project->Properties->Web Project Settings) configured. > Name of project is servlet-security, but web context root is jboss-servlet-security > This results into 404 when this project gets deployed to server. IDE opens url http://localhost:8080/jboss-servlet-security, but correct url is http://localhost:8080/servlet-security. > Note, that this does not happen when importing this project as existing maven project (not using easymport). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22508) compile failed in org.jboss.tools.wtp.server.launchbar

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22508?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22508: ---------------------------------------- Here is a PR for the server side - https://github.com/jbosstools/jbosstools-server/pull/421 > compile failed in org.jboss.tools.wtp.server.launchbar > -------------------------------------------------------- > > Key: JBIDE-22508 > URL: https://issues.jboss.org/browse/JBIDE-22508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > {code} > 02:32:22 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.25.0:compile (default-compile) on project org.jboss.tools.wtp.server.launchbar: Compilation failure: Compilation failure: > 02:32:22 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/wtp/plugins/org.jboss.tools.wtp.server.launchbar/src/org/jboss/tools/wtp/server/launchbar/ModuleObjectProvider.java:[325] > 02:32:22 [ERROR] boolean enabled = store.getBoolean(Activator.PREF_ENABLE_LAUNCHBAR); > 02:32:22 [ERROR] ^^^^^^^^^^^^^^^^^^^^^ > 02:32:22 [ERROR] PREF_ENABLE_LAUNCHBAR cannot be resolved or is not a field > {code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22508) compile failed in org.jboss.tools.wtp.server.launchbar

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22508?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22508: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-server/pull/421, https://github.com/jbosstools/jbosstools-target-platforms/pull/220 (was: https://github.com/jbosstools/jbosstools-server/pull/421) > compile failed in org.jboss.tools.wtp.server.launchbar > -------------------------------------------------------- > > Key: JBIDE-22508 > URL: https://issues.jboss.org/browse/JBIDE-22508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > {code} > 02:32:22 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.25.0:compile (default-compile) on project org.jboss.tools.wtp.server.launchbar: Compilation failure: Compilation failure: > 02:32:22 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/wtp/plugins/org.jboss.tools.wtp.server.launchbar/src/org/jboss/tools/wtp/server/launchbar/ModuleObjectProvider.java:[325] > 02:32:22 [ERROR] boolean enabled = store.getBoolean(Activator.PREF_ENABLE_LAUNCHBAR); > 02:32:22 [ERROR] ^^^^^^^^^^^^^^^^^^^^^ > 02:32:22 [ERROR] PREF_ENABLE_LAUNCHBAR cannot be resolved or is not a field > {code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22176) [thym] Implement Engines Management in config.xml editor

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22176?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-22176: ----------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Final) > [thym] Implement Engines Management in config.xml editor > -------------------------------------------------------- > > Key: JBIDE-22176 > URL: https://issues.jboss.org/browse/JBIDE-22176 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Pavol Srna > Assignee: Angel Misevski > Fix For: 4.4.x > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=491580 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22241) OpenShift Explorer: Cascade resource deletion

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22241?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22241: ------------------------------------ Here is my reverse engineering from the OC client. ||Resource type||Delete processing|| |ReplicationController|check other compatible ReplicationControllers (selector is compatible with own selector), if compatible ReplicationControllers selector have the same number of elements then they are considered as exact match otherwise as overlapping. If there are overlapping cascaded delete is refused, otherwise if there is a single exact match ReplicationController, it is scaled down to 0 and then deleted. Code logic is available here: https://github.com/kubernetes/kubernetes/blob/master/pkg/kubectl/stop.go#... |DeploymentConfig|delete linked ReplicationControllers using labelSelector *openshift.io/deployment-config.name=dcName*. Code logic is available here: https://github.com/openshift/origin/blob/master/pkg/deploy/reaper/reaper.... |Route|simple delete| |Service|simple delete| |BuildConfig|first set the annotation *openshift.io/build-config.paused* to *true* then delete linked Builds using labelSelector *openshift.io/build-config.name=bcName* then delete linked Builds using labelSelector *buildconfig=bcName* then delete the BuildConfig is no error in previous steps. Code logic is available here: https://github.com/openshift/origin/blob/master/pkg/build/reaper/reaper.g... |Build|simple delete| |ImageStream|simple delete| |Pod|simple delete| |Project|simple delete| > OpenShift Explorer: Cascade resource deletion > --------------------------------------------- > > Key: JBIDE-22241 > URL: https://issues.jboss.org/browse/JBIDE-22241 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: explorer, openshift_v3, ux > Fix For: 4.4.0.Final > > > It would be nice to have a possibility to allow cascading deletion, deletion of related resource/resource managed by the resource which is about to be deleted. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22508) compile failed in org.jboss.tools.wtp.server.launchbar

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22508?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22508: ------------------------------------ We don't currently include launchbar.remote. Here's a PR to include the feature instead of the 2 plugins, which will pull in the 3rd missing plugin. https://github.com/jbosstools/jbosstools-target-platforms/pull/220 > compile failed in org.jboss.tools.wtp.server.launchbar > -------------------------------------------------------- > > Key: JBIDE-22508 > URL: https://issues.jboss.org/browse/JBIDE-22508 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, target-platform > Affects Versions: 4.4.0.Alpha2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > {code} > 02:32:22 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.25.0:compile (default-compile) on project org.jboss.tools.wtp.server.launchbar: Compilation failure: Compilation failure: > 02:32:22 [ERROR] /mnt/hudson_workspace/workspace/jbosstools-server_master/sources/wtp/plugins/org.jboss.tools.wtp.server.launchbar/src/org/jboss/tools/wtp/server/launchbar/ModuleObjectProvider.java:[325] > 02:32:22 [ERROR] boolean enabled = store.getBoolean(Activator.PREF_ENABLE_LAUNCHBAR); > 02:32:22 [ERROR] ^^^^^^^^^^^^^^^^^^^^^ > 02:32:22 [ERROR] PREF_ENABLE_LAUNCHBAR cannot be resolved or is not a field > {code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 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 June 2016