October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15609) versionwatch should ignore when there's a folder & jar which are identical

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15609: ---------------------------------- Summary: versionwatch should ignore when there's a folder & jar which are identical Key: JBIDE-15609 URL: https://issues.jboss.org/browse/JBIDE-15609 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, qa Affects Versions: 4.1.1.Alpha2 Reporter: Nick Boldt A while ago I added a facility to jar up feature and plugin folders so they could have their md5 sums compared. Now, the vwatch tool complains when there's a folder and a jar present. Two possible solutions to this come to mind: a) ignore this - do not report as *{color:red}a problem{color}* b) whenever a folder is jarred up, delete the source folder -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15609) versionwatch should ignore when there's a folder & jar which are identical

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15609?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15609: ------------------------------- Description: A while ago I added a facility to jar up feature and plugin folders so they could have their md5 sums compared. Now, the vwatch tool complains when there's a folder and a jar present. Two possible solutions to this come to mind: a) ignore this - do not report as *{color:red}a problem{color}* b) whenever a folder is jarred up, delete the source folder, so the above condition cannot occur was: A while ago I added a facility to jar up feature and plugin folders so they could have their md5 sums compared. Now, the vwatch tool complains when there's a folder and a jar present. Two possible solutions to this come to mind: a) ignore this - do not report as *{color:red}a problem{color}* b) whenever a folder is jarred up, delete the source folder > versionwatch should ignore when there's a folder & jar which are identical > -------------------------------------------------------------------------- > > Key: JBIDE-15609 > URL: https://issues.jboss.org/browse/JBIDE-15609 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > > A while ago I added a facility to jar up feature and plugin folders so they could have their md5 sums compared. > Now, the vwatch tool complains when there's a folder and a jar present. > Two possible solutions to this come to mind: > a) ignore this - do not report as *{color:red}a problem{color}* > b) whenever a folder is jarred up, delete the source folder, so the above condition cannot occur -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15581) openshift-java-client: support PATCH http method

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15581?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15581: ------------------------------------- Git Pull Request: https://github.com/openshift/openshift-java-client/pull/77, https://github.com/openshift/openshift-java-client/pull/80 (was: https://github.com/openshift/openshift-java-client/pull/77) > openshift-java-client: support PATCH http method > ------------------------------------------------ > > Key: JBIDE-15581 > URL: https://issues.jboss.org/browse/JBIDE-15581 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift-java-client > Fix For: 4.2.x > > > OpenShift's using the PATCH http method in links for protocol 1.6 (will those links get backported?). > The OpenShift java client does not support any method that differs from GET, POST, PUT, DELETE and should support links that use the PATCH http method. > {quote} > (06:35:55 PM) clayton: we're adding PATCH methods and I'm ensuring that the client tools will be future compatible when that happens > (06:36:06 PM) clayton: they'll only be in API 1.6 but want to fix it now > {quote} -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15608) Widget shrinked after attempt to expand it

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15608?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-15608 at 10/3/13 12:22 PM: ----------------------------------------------------------------- In Eclipse (Version: Kepler Service Release 1, Build id: 20130919-0819) it works fine. It seems to were right - it's not upstream. was (Author: mlabuda): In Eclipse (Version: Kepler Service Release 1, Build id: 20130919-0819) it works fine. > Widget shrinked after attempt to expand it > ------------------------------------------ > > Key: JBIDE-15608 > URL: https://issues.jboss.org/browse/JBIDE-15608 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.1.0.Final > Reporter: Marián Labuda > Priority: Minor > Attachments: 37.png, 56.png > > > Sometimes widgets collaps or shrinked itself to line and it is impossible to expand it. Mostly if was undeterministic, but now I have found reproducible one. See attached images. > It's possible to close such widget by press Esc. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15608) Widget shrinked after attempt to expand it

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15608?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-15608: --------------------------------------- In Eclipse (Version: Kepler Service Release 1, Build id: 20130919-0819) it works fine. > Widget shrinked after attempt to expand it > ------------------------------------------ > > Key: JBIDE-15608 > URL: https://issues.jboss.org/browse/JBIDE-15608 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.1.0.Final > Reporter: Marián Labuda > Priority: Minor > Attachments: 37.png, 56.png > > > Sometimes widgets collaps or shrinked itself to line and it is impossible to expand it. Mostly if was undeterministic, but now I have found reproducible one. See attached images. > It's possible to close such widget by press Esc. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15497) Support/ignore Errai custom @Inject's

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15497?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-15497: ----------------------------------------------- Extension org.jboss.errai.cdi.server.CDIExtensionPoints (see at https://github.com/errai/errai/blob/master/errai-cdi/weld-integration) collects injections with type implementing org.jboss.errai.ioc.support.bus.client.Sender (e.g. org.jboss.errai.common.client.api.Caller<?>) and provides beans to be injected. Errai Reference Guide (see Errai_2.4.0.Beta1_Reference_Guide.pdf) does not mention CDI, but in Chapter 3. Dependency Injection/3.1. Container Wiring states that Errai IOC implements org.jboss.errai.ioc.client.api.builtin.CallerProvider that makes RPC Caller<T> objects available for injection. So, the question is, should we assume that weld-integration module with extension is available in an Errai project and implement it in JBoss CDI Tools, or we should not rely on it and just mock caller provider? > Support/ignore Errai custom @Inject's > ------------------------------------- > > Key: JBIDE-15497 > URL: https://issues.jboss.org/browse/JBIDE-15497 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi-extensions > Reporter: Max Rydahl Andersen > Assignee: Jonathan Fuerth > Attachments: Errai_2.4.0.Beta1_Reference_Guide.pdf > > > in JBDS-2358 was found that Errai has its own set of CDI inject extensions that we warn against where we probably should ignore them. > [~jfuerth] can you outline the specific CDI types/extensions in this jira and [~akazakov] can see if this fits into the kind of types/extensions we can safely/easily ignore/support. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15497) Support/ignore Errai custom @Inject's

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15497?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich updated JBIDE-15497: ------------------------------------------ Attachment: Errai_2.4.0.Beta1_Reference_Guide.pdf > Support/ignore Errai custom @Inject's > ------------------------------------- > > Key: JBIDE-15497 > URL: https://issues.jboss.org/browse/JBIDE-15497 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi-extensions > Reporter: Max Rydahl Andersen > Assignee: Jonathan Fuerth > Attachments: Errai_2.4.0.Beta1_Reference_Guide.pdf > > > in JBDS-2358 was found that Errai has its own set of CDI inject extensions that we warn against where we probably should ignore them. > [~jfuerth] can you outline the specific CDI types/extensions in this jira and [~akazakov] can see if this fits into the kind of types/extensions we can safely/easily ignore/support. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15606) build tool to regenerate component update sites from published JBT aggregate

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15606?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15606: ------------------------------------ I mean we copy the bits included in http://download.jboss.org/jbosstools/updates/stable/kepler/ to child sites like http://download.jboss.org/jbosstools/updates/stable/kepler/core/freemarke... so that future builds of JBT 4.1.x can be aggregated from the released Freemarker 1.3.100.Final bits. Point of this is so that staging folders like http://download.jboss.org/jbosstools/builds/staging/jbosstools-freemarker... don't have to be kept indefinitely, and in the event we accidentally delete one, we have a way to recreate a useful update site from the previously released binary bits w/o having to rebuild from an old tag. > build tool to regenerate component update sites from published JBT aggregate > ---------------------------------------------------------------------------- > > Key: JBIDE-15606 > URL: https://issues.jboss.org/browse/JBIDE-15606 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Beta1 > > > When we released JBT 4.1.0.Final, we didn't publish the individual projects as sites themselves, so now when we're trying to aggregate JBT 4.1.1.Alpha2 using a combination of unchanged older projects + changed newer projects, we're unable to do so. > We could rebuild the projects from source, but it would be better to simply re-aggregate the binaries in order to produce subset sites which match the content of the released JBT site, but only for those individual projects. > This would allow us to swap in/out projects like GWT, Freemarker, Birt, Hibernate and Portal, which haven't changed yet since JBT 4.1.0.Final was released. -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15608) Widget shrinked after attempt to expand it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15608?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15608: ------------------------------------ Moved to JBIDE as requested. This does look like an upstream problem. Can you verify it occurs when you have ONLY Eclipse Kepler R or SR1 installed, without JBoss Tools or JBDS ? Secure storage preferences page isn't one we contribute, AFAIK. > Widget shrinked after attempt to expand it > ------------------------------------------ > > Key: JBIDE-15608 > URL: https://issues.jboss.org/browse/JBIDE-15608 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.1.0.Final > Reporter: Marián Labuda > Priority: Minor > Attachments: 37.png, 56.png > > > Sometimes widgets collaps or shrinked itself to line and it is impossible to expand it. Mostly if was undeterministic, but now I have found reproducible one. See attached images. > It's possible to close such widget by press Esc. -- 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

1
0
0 / 0

[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 reassigned JBIDE-15599: ------------------------------------- Assignee: Max Rydahl Andersen (was: Xavier Coulon) Please review the PR > 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: Max Rydahl Andersen > 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

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 October 2013