[JBoss JIRA] (JBIDE-14018) OpenShift commit message references JBoss Tools
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14018?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-14018:
------------------------------------------
Sure no doubt, we'll implement this very soon.
In the meantime I suggest that you try using EGit to not have to drop to the cmd line. It works very nicely, that's what I'm using very frequently.
> OpenShift commit message references JBoss Tools
> -----------------------------------------------
>
> Key: JBIDE-14018
> URL: https://issues.jboss.org/browse/JBIDE-14018
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Michelle Murray
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: commit_from_JBT.png, Customized Git Commit on Publish.png
>
>
> In Servers tab, when you right-click on an OpenShift server adapter and click Publish, an automatic commit message is generated: "Commit from JBoss Tools".
> This message references JBoss Tools - for JBDS it should mention JBDS. I realise it is difficult to have a different message for JBT and JBDS so I guess the message needs to be changed to not reference either.
--
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, 6 months
[JBoss JIRA] (JBIDE-15602) openshift-java-client: ApplicationResource#sshExecCmd is throwing with wrong msg
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15602?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-15602:
-------------------------------------
Description:
The message that is used when throwing an exception is wrong, it's reporting a failure to list forwardable ports where it's failing to execute an ssh-command:
{code:title=ApplicationResource#sshExecCmd}
try {
session.openChannel("exec");
channel = session.openChannel("exec");
((ChannelExec) channel).setCommand(command);
channel.connect();
return sshStream.getLines(channel);
} catch (JSchException e) {
throw new OpenShiftSSHOperationException(e, "Failed to list forwardable ports for application \"{0}\"",
this.getName());
} catch (IOException e) {
throw new OpenShiftSSHOperationException(e, "Failed to list forwardable ports for application \"{0}\"",
this.getName());
} finally {
{code}
was:
The message that is used when throwing an exception is wrong, it's reporting a failure to list forwardable ports where it's failing to execute an ssh-command:
{code:ApplicationResource#sshExecCmd}
try {
session.openChannel("exec");
channel = session.openChannel("exec");
((ChannelExec) channel).setCommand(command);
channel.connect();
return sshStream.getLines(channel);
} catch (JSchException e) {
throw new OpenShiftSSHOperationException(e, "Failed to list forwardable ports for application \"{0}\"",
this.getName());
} catch (IOException e) {
throw new OpenShiftSSHOperationException(e, "Failed to list forwardable ports for application \"{0}\"",
this.getName());
} finally {
{code}
> openshift-java-client: ApplicationResource#sshExecCmd is throwing with wrong msg
> --------------------------------------------------------------------------------
>
> Key: JBIDE-15602
> URL: https://issues.jboss.org/browse/JBIDE-15602
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.2.x
>
>
> The message that is used when throwing an exception is wrong, it's reporting a failure to list forwardable ports where it's failing to execute an ssh-command:
> {code:title=ApplicationResource#sshExecCmd}
> try {
> session.openChannel("exec");
> channel = session.openChannel("exec");
> ((ChannelExec) channel).setCommand(command);
> channel.connect();
> return sshStream.getLines(channel);
> } catch (JSchException e) {
> throw new OpenShiftSSHOperationException(e, "Failed to list forwardable ports for application \"{0}\"",
> this.getName());
> } catch (IOException e) {
> throw new OpenShiftSSHOperationException(e, "Failed to list forwardable ports for application \"{0}\"",
> this.getName());
> } finally {
> {code}
--
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, 6 months
[JBoss JIRA] (JBIDE-15602) openshift-java-client: ApplicationResource#sshExecCmd is throwing with wrong msg
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-15602:
----------------------------------------
Summary: openshift-java-client: ApplicationResource#sshExecCmd is throwing with wrong msg
Key: JBIDE-15602
URL: https://issues.jboss.org/browse/JBIDE-15602
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.Alpha1
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.2.x
The message that is used when throwing an exception is wrong, it's reporting a failure to list forwardable ports where it's failing to execute an ssh-command:
{code:ApplicationResource#sshExecCmd}
try {
session.openChannel("exec");
channel = session.openChannel("exec");
((ChannelExec) channel).setCommand(command);
channel.connect();
return sshStream.getLines(channel);
} catch (JSchException e) {
throw new OpenShiftSSHOperationException(e, "Failed to list forwardable ports for application \"{0}\"",
this.getName());
} catch (IOException e) {
throw new OpenShiftSSHOperationException(e, "Failed to list forwardable ports for application \"{0}\"",
this.getName());
} finally {
{code}
--
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, 6 months
[JBoss JIRA] (JBIDE-15600) MatrixParam and QueryParam field names are used instead of the annotation values
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15600?page=com.atlassian.jira.plugi... ]
Xavier Coulon resolved JBIDE-15600.
-----------------------------------
Resolution: Rejected
The bug was introduced while working on JBIDE-12029 and was fixed in the latest PR of JBIDE-12029 as well. The bug could not be reproduced on jbosstools-4.1.x branch without the patch for JBIDE-12029
> MatrixParam and QueryParam field names are used instead of the annotation values
> --------------------------------------------------------------------------------
>
> Key: JBIDE-15600
> URL: https://issues.jboss.org/browse/JBIDE-15600
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.1.1.Beta1
>
>
> Take the following classes:
> {code}
> @Path("/products")
> public class ProductResourceLocator {
> @QueryParam("foo1")
> private String foo2;
> @Path("/{productType}")
> public Object getProductResourceLocator() {
> return new BookResource();
> }
> }
> {code}
> and
> {code}
> @Produces({ MediaType.APPLICATION_XML, "application/json" })
> public class BookResource {
> @GET
> @Path("/{id}")
> @Produces({ "application/xml", "application/json" })
> public Book getProduct(@PathParam("id") Integer id) {
> return null;
> }
> }
> {code}
> ASSERT: the URL Template for the Endpoint should be something like
> {code}
> /products/{productType}/{id}?foo1={String}
> {code}
> FAIL: the URL Template for the Endpoint should be something like
> {code}
> /products/{productType}/{id}?foo2={String}
> {code}
--
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, 6 months
[JBoss JIRA] (JBIDE-15599) Changes on a subresource locator fields are not propagated to the JAX-RS Explorer
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15599?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-15599:
----------------------------------
Description:
Take the following classes:
{code}
@Path("/products")
public class ProductResourceLocator {
@QueryParam("foo")
private String foo;
@Path("/{productType}")
public Object getProductResourceLocator() {
return new BookResource();
}
}
{code}
and
{code}
@Produces({ MediaType.APPLICATION_XML, "application/json" })
public class BookResource {
@GET
@Path("/{id}")
@Produces({ "application/xml", "application/json" })
public Book getProduct(@PathParam("id") Integer id) {
return null;
}
}
{code}
and modify the @QueryParam value of the "foo" field.
ASSERT: the changes appear in the Project Explorer
FAIL: the old @QueryParam annotation value is still used
WORKAROUND: Refresh the JAX-RS Web Services node.
was:
Take the following classes:
{code}
@Path("/products")
public class ProductResourceLocator {
@QueryParam("foo")
private String foo;
@Path("/{productType}")
public Object getProductResourceLocator() {
return new BookResource();
}
}
{code}
and
{code}
@Produces({ MediaType.APPLICATION_XML, "application/json" })
public class BookResource {
@GET
@Path("/{id}")
@Produces({ "application/xml", "application/json" })
public Book getProduct(@PathParam("id") Integer id) {
return null;
}
}
{code}
and modify the @QueryParam value of the "foo" field.
ASSERT: the changes appear in the Project Explorer
FAIL: the old @QueryParam annotation value is still used
WORKAROUND: Clean/build the project then refresh the JAX-RS Web Services node.
> Changes on a subresource locator fields are not propagated to the JAX-RS Explorer
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-15599
> URL: https://issues.jboss.org/browse/JBIDE-15599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.1.1.Beta1
>
>
> Take the following classes:
> {code}
> @Path("/products")
> public class ProductResourceLocator {
> @QueryParam("foo")
> private String foo;
> @Path("/{productType}")
> public Object getProductResourceLocator() {
> return new BookResource();
> }
> }
> {code}
> and
> {code}
> @Produces({ MediaType.APPLICATION_XML, "application/json" })
> public class BookResource {
> @GET
> @Path("/{id}")
> @Produces({ "application/xml", "application/json" })
> public Book getProduct(@PathParam("id") Integer id) {
> return null;
> }
> }
> {code}
> and modify the @QueryParam value of the "foo" field.
> ASSERT: the changes appear in the Project Explorer
> FAIL: the old @QueryParam annotation value is still used
> WORKAROUND: Refresh the JAX-RS Web Services node.
--
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, 6 months
[JBoss JIRA] (JBDS-2471) JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf
by Douglas Palmer (JIRA)
[ https://issues.jboss.org/browse/JBDS-2471?page=com.atlassian.jira.plugin.... ]
Douglas Palmer reassigned JBDS-2471:
------------------------------------
Assignee: Paul Leacu (was: Douglas Palmer)
> JBDS6 sets lower default memory settings for SOA server start than are defined in SOA run.conf
> ----------------------------------------------------------------------------------------------
>
> Key: JBDS-2471
> URL: https://issues.jboss.org/browse/JBDS-2471
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: integration-platform
> Affects Versions: 5.0.2.GA, 7.0.0.GA
> Environment: Version: 5.0.2.GA
> Build id: v20130119-0035-H249-GA
> Build date: 20130119-0035
> http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.3.GA.soa-to...
> Reporter: Len DiMaggio
> Assignee: Paul Leacu
> Fix For: 5.0.6.GA-SOA, 6.0.2.GA
>
>
> JBDS6:
> "-Dprogram.name=JBossTools: JBoss SOA 531_ER4 Runtime"
> -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=true
> -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 "-Djava.endorsed.dirs=/jboss/local/SOA_servers/531_ER4/jboss-soa-p-5/jboss-as/lib/endorsed"
> SOA 5.3.1 run.conf:
> if [ "x$JAVA_OPTS" = "x" ]; then
> JAVA_OPTS="-Xms1303m -Xmx1303m -XX:MaxPermSize=256m -Djava.awt.headless=true -Dorg.apache.xml.dtm.DTMManager=org.apache.xml.dtm.ref.DTMManagerDefault -Dorg.jboss.net.protocol.file.useURI=false -Dorg.jboss.resolver.warning
> =true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Dsun.lang.ClassLoader.allowArraySyntax=true"
> fi
--
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, 6 months
[JBoss JIRA] (JBDS-2421) Missing modeshape.jcr.feature after install SOA Tooling from central
by Douglas Palmer (JIRA)
[ https://issues.jboss.org/browse/JBDS-2421?page=com.atlassian.jira.plugin.... ]
Douglas Palmer reassigned JBDS-2421:
------------------------------------
Assignee: Paul Leacu (was: Douglas Palmer)
> Missing modeshape.jcr.feature after install SOA Tooling from central
> --------------------------------------------------------------------
>
> Key: JBDS-2421
> URL: https://issues.jboss.org/browse/JBDS-2421
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central
> Affects Versions: 5.0.1.GA-SOA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Fix For: 6.0.0.Alpha1-SOA
>
>
> After installing SOA Tooling from central the following feature is missing
> ModeShape Tools JCR CND Editor for Eclipsw
> 1.1.0.v20120717-1107-H6-GA-SOA
> org.jboss.tools.modeshape.jcr.feature.feature.group
> This is due to missing the feature at
> -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/5.0.2.GA.soa-tooling/devstudio-directory.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, 6 months