June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20147) Batch Property mapping issue with reference

by Cody Lerum (JIRA)

Cody Lerum created JBIDE-20147: ---------------------------------- Summary: Batch Property mapping issue with reference Key: JBIDE-20147 URL: https://issues.jboss.org/browse/JBIDE-20147 Project: Tools (JBoss Tools) Issue Type: Bug Components: batch Affects Versions: 4.3.0.Beta1 Environment: Mars Tools 4.3.0 Beta1 Reporter: Cody Lerum After upgrading to Mars and JBT I started getting a validation warning on my batch configuration If I have the following I get an error {{Property "INVOICE_JOB_ID" is not found in artifact "invoiceCreateBatchlet" and is not used in other properties.}} {code} @Inject @BatchProperty(name = InvoiceCreatePartitionMapper.INVOICE_JOB_ID_KEY) private String invoiceJobId; {code} In a different class {code} public static final String INVOICE_JOB_ID_KEY = "INVOICE_JOB_ID"; {code} However if have the following there is no warning. {code} @Inject @BatchProperty(name = "INVOICE_JOB_ID") private String invoiceJobId; {code} It appears that the validation logic cannot follow the reference -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19800) use maven to generate zip and jar md5/sha1 digests at build time instead of when publishing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19800?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19800. ------------------------------ Yes, closing. Future work in JBIDE-20143 (because SHA256 is better than SHA1). > use maven to generate zip and jar md5/sha1 digests at build time instead of when publishing > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19800 > URL: https://issues.jboss.org/browse/JBIDE-19800 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > [~maxandersen] said: {quote} > That we even have bash code for creating md5sum when maven supports it natively is for me the weird part (http://nicoulaj.github.io/checksum-maven-plugin/index.html) > {quote} -- JBIDE-13835 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3462) remove /development/ and /staging/ URLs from JBDS artifacts

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3462?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3462: ---------------------------------- Thx for the feedback - yes, I'm only talking about this internal page, build-info.html. Nothing would change here w.r.t public facing pages on devstudio.redhat.com I've added more/better redirects: https://github.com/jbdevstudio/jbdevstudio-website/pull/185 * https://devstudio.redhat.com/9.0/staging/ (Beta1, nice webpage) * https://devstudio.redhat.com/9.0/development/ (Beta1, nice webpage) * https://devstudio.redhat.com/9.0/stable/ (empty; I could put a "coming soon" page here, with a link to JBDS JIRA w/ schedule?) > remove /development/ and /staging/ URLs from JBDS artifacts > ----------------------------------------------------------- > > Key: JBDS-3462 > URL: https://issues.jboss.org/browse/JBDS-3462 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > There's a TODO in the JBDS 9 release guide which says: > {quote} > when releasing GA make sure to :%s/development/stable/g and :%s/9.0-staging/9.0/g{quote} > Here are a couple files which still need to be tweaked so they don't have to change between milestone releases and GA: > {code} > ./results/build.xml ** > 224-  > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20036) As I user I want to be able to add image streams to my project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20036?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20036: ------------------------------------------ setting fixVersion to 4.3.x since there are currently means to achieve this but we'd want to have this explicitly handled in maintenance. > As I user I want to be able to add image streams to my project > -------------------------------------------------------------- > > Key: JBIDE-20036 > URL: https://issues.jboss.org/browse/JBIDE-20036 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.3.x > > > When creating a new application via templates I am required to have the docker images (base builder image etc.) to be available. Otherwise the build wont succeed. > You can see this in the instrcutions for the eap templates where the steps to create an app via those templates are 2: create the image streams & create the app via the templates: > https://github.com/adietish/application-templates/blob/master/README.md > {code} > $ osc create -n yourproject -f jboss-image-streams.json > $ osc process -n yourproject -f eap/eap6-basic-sti.json -v APPLICATION_NAME=helloworld,APPLICATION_HOSTNAME=helloworld.yourproject.l... | osc create -n yourproject -f - > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20036) As I user I want to be able to add image streams to my project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20036?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20036: ------------------------------------- Fix Version/s: 4.3.x (was: 4.3.0.Beta2) > As I user I want to be able to add image streams to my project > -------------------------------------------------------------- > > Key: JBIDE-20036 > URL: https://issues.jboss.org/browse/JBIDE-20036 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.3.x > > > When creating a new application via templates I am required to have the docker images (base builder image etc.) to be available. Otherwise the build wont succeed. > You can see this in the instrcutions for the eap templates where the steps to create an app via those templates are 2: create the image streams & create the app via the templates: > https://github.com/adietish/application-templates/blob/master/README.md > {code} > $ osc create -n yourproject -f jboss-image-streams.json > $ osc process -n yourproject -f eap/eap6-basic-sti.json -v APPLICATION_NAME=helloworld,APPLICATION_HOSTNAME=helloworld.yourproject.l... | osc create -n yourproject -f - > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20050) Explorer: As a user I want to be able to refresh projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20050?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-20050: ------------------------------------- Summary: Explorer: As a user I want to be able to refresh projects (was: Explorer: Cannot refresh project) > Explorer: As a user I want to be able to refresh projects > --------------------------------------------------------- > > Key: JBIDE-20050 > URL: https://issues.jboss.org/browse/JBIDE-20050 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > Attachments: no-refresh.png > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20003) Explorer: Add Refresh context menu item to OpenShift v3 projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20003?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-20003. -------------------------------------- Resolution: Duplicate Issue > Explorer: Add Refresh context menu item to OpenShift v3 projects > ---------------------------------------------------------------- > > Key: JBIDE-20003 > URL: https://issues.jboss.org/browse/JBIDE-20003 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > > There could be Refresh context menu item on project for OpenShift v3 connections. Similar as the one in context menu of OpenShift v3 connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20003) Explorer: Add Refresh context menu item to OpenShift v3 projects

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20003?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-20003: ------------------------------------------ [~jcantrill] yes we do, we now have a functional "Refresh" in the context menu for projects. resolving as done. > Explorer: Add Refresh context menu item to OpenShift v3 projects > ---------------------------------------------------------------- > > Key: JBIDE-20003 > URL: https://issues.jboss.org/browse/JBIDE-20003 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Minor > Labels: openshift_v3 > Fix For: 4.3.0.Beta2 > > > There could be Refresh context menu item on project for OpenShift v3 connections. Similar as the one in context menu of OpenShift v3 connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-452) Unable to pull the Fuse Plugins directly from JBDS

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-452?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-452: ---------------------------------- Hi [~rogerhui] - I'm having trouble identifying exactly how you attempted to install. Please give exact actions. [~apodhrad] - any idea how this occurred? - I can't seem to reproduce it. Roger - here are the installation instructions for JBDSIS: Installation Instructions: 1. If installing from Eclipse Luna: Help > Eclipse Marketplace... - in the 'Search' tab enter 'jbds' in the 'Find' input widget - select the 'Go' button - install 'Red Hat JBoss Developer Studio 8.1.0.GA' 2. Start jbdevstudio or eclipse (with jbds from step 1) 3. Select the Software/Update tab in the JBoss Central view. done! The standard p2 installer is available for JBDSIS (.GA): 1. If installing from Eclipse Luna: Help > Eclipse Marketplace... - in the 'Search' tab enter 'jbds' in the 'Find' input widget - select the 'Go' button - install 'Red Hat JBoss Developer Studio 8.1.0.GA' 2. Start jbdevstudio or eclipse-with-jbds from step 1, then: Help > Install New Software... Add... - use this for 'Location:' for the production integration stack: https://devstudio.redhat.com/updates/8.0/integration-stack/ - use this for 'Location:' for the early access integration stack: https://devstudio.redhat.com/updates/8.0/integration-stack/earlyaccess/ > Unable to pull the Fuse Plugins directly from JBDS > -------------------------------------------------- > > Key: JBTIS-452 > URL: https://issues.jboss.org/browse/JBTIS-452 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE > Affects Versions: 8.0.2.GA > Reporter: Roger Hui > Attachments: JBDSError.png > > > JBDS 8.1 and can't install the fuse plugins see attachment. > Looks like the plugin are not pushed to the public site. > The work around is to download the integration zip from access.redhat.com (CSP) and install it from there, but then I won't get auto update.. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20099) enable a logstream for Openshift Pods

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20099?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-20099 at 6/24/15 10:46 AM: -------------------------------------------------------------------- setting 4.3.0.Beta2 as fixVersion for now since I would think that this is most likely even more important than proper port forwarding? In my thinking we were framed by the approach in v2 where port forwarding and inspecting the log were both relying on ssh. This made us think that by having port forwarding we'd have the infrastructure to tail log files. Here in v3 we have a similar situation where both apparently rely on SPDY which we'll provide via wrapping the cli we'd have the basics to be able to inspect the logs. Thinking twice I would think that inspecting the logs is more important than port forwarding per se. [~maxandersen] [~jcantrill] WDYT? was (Author: adietish): setting 4.3.0.Beta2 as fixVersion for now since I would think that this is most likely even more important than proper port forwarding? [~maxandersen] WDYT? > enable a logstream for Openshift Pods > ------------------------------------- > > Key: JBIDE-20099 > URL: https://issues.jboss.org/browse/JBIDE-20099 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Diógenes Rettori > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta2 > > > enable the eclipse console to show > oc get logs <pod> > oc get build-logs <build> > You click on the pod, then right-click show logs, or double click go to logs... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 2015