April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19558) Central search for customer portal doesnt work - again

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19558?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19558: ------------------------------------- I'm saying current design only searches for quickstarts. JBDS-3248 doesn't express the need to search for Red Hat CSP Not sure if dcp.jboss.org indexes *all* Red Hat CSP anyway. If we're to look for more than quickstarts info, well I need to know, so I can change the way I perform searches now > Central search for customer portal doesnt work - again > ------------------------------------------------------ > > Key: JBIDE-19558 > URL: https://issues.jboss.org/browse/JBIDE-19558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.3.Final, 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Same as JBIDE-18666 > Search URL changed again -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19558) Central search for customer portal doesnt work - again

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19558?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19558: --------------------------------------------- wait, are you saying Red Hat CSP broke it so we can't or just saying we start by having quickstarts in here and will add customer portal later ? > Central search for customer portal doesnt work - again > ------------------------------------------------------ > > Key: JBIDE-19558 > URL: https://issues.jboss.org/browse/JBIDE-19558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.3.Final, 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Same as JBIDE-18666 > Search URL changed again -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19558) Central search for customer portal doesnt work - again

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19558?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-19558: ------------------------------------- [~burrsutter], [~maxandersen] : AFAIU this feature won't be available in the next JBoss Central iteration. Search will only search for quickstarts. Do we agree or? > Central search for customer portal doesnt work - again > ------------------------------------------------------ > > Key: JBIDE-19558 > URL: https://issues.jboss.org/browse/JBIDE-19558 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.3.Final, 4.3.0.Alpha1 > Reporter: Rastislav Wagner > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > Same as JBIDE-18666 > Search URL changed again -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19565) New Stereotype annotation wizard requires definition of @Target

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19565?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-19565: ------------------------------------- Issue Type: Bug (was: Feature Request) > New Stereotype annotation wizard requires definition of @Target > --------------------------------------------------------------- > > Key: JBIDE-19565 > URL: https://issues.jboss.org/browse/JBIDE-19565 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > > New Stereotype annotation wizard requires to choose one of: > TYPE, METHOD, FIELD > TYPE > METHOD > FIELD > METHOD, FIELD > which is ok for CDI 1.0 but > CDI 1.1+ isnt restricted to these target combinations and also it does not require to define target at all (see https://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#defining_new_stereotype ) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19565) New Stereotype annotation wizard requires definition of @Target

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19565?page=com.atlassian.jira.plugi... ] Rastislav Wagner updated JBIDE-19565: ------------------------------------- Description: New Stereotype annotation wizard requires to choose one of: TYPE, METHOD, FIELD TYPE METHOD FIELD METHOD, FIELD which is ok for CDI 1.0 but CDI 1.1+ isnt restricted to these target combinations and also it does not require to define target at all (see https://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#defining_new_stereotype ) was: New Stereotype annotation wizard requires to choose one of: TYPE, METHOD, FIELD TYPE METHOD FIELD METHOD, FIELD CDI 1.1+ isnt restricted to these target combinations and also it does not require to define target at all (see https://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#defining_new_stereotype ) > New Stereotype annotation wizard requires definition of @Target > --------------------------------------------------------------- > > Key: JBIDE-19565 > URL: https://issues.jboss.org/browse/JBIDE-19565 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdi > Affects Versions: 4.3.0.Alpha1 > Reporter: Rastislav Wagner > > New Stereotype annotation wizard requires to choose one of: > TYPE, METHOD, FIELD > TYPE > METHOD > FIELD > METHOD, FIELD > which is ok for CDI 1.0 but > CDI 1.1+ isnt restricted to these target combinations and also it does not require to define target at all (see https://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#defining_new_stereotype ) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19565) New Stereotype annotation wizard requires definition of @Target

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-19565: ---------------------------------------- Summary: New Stereotype annotation wizard requires definition of @Target Key: JBIDE-19565 URL: https://issues.jboss.org/browse/JBIDE-19565 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdi Affects Versions: 4.3.0.Alpha1 Reporter: Rastislav Wagner New Stereotype annotation wizard requires to choose one of: TYPE, METHOD, FIELD TYPE METHOD FIELD METHOD, FIELD CDI 1.1+ isnt restricted to these target combinations and also it does not require to define target at all (see https://docs.jboss.org/cdi/spec/1.1/cdi-spec.html#defining_new_stereotype ) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19336) To avoid disparity of versions, Central should not include the same IUs as JBT/JBDS update sites

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19336?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19336: ---------------------------------------- The issue is that those TP/sites are shared between JBT and JBDS, so it needs to contain everything that is not in JBDS, with the risk of repeating some IUs that are already in JBT. So it has a strong dependency on JBIDE-19025 . I don't think there is nothing sustainable we can do on this topic until JBIDE-19025 is resolved. > To avoid disparity of versions, Central should not include the same IUs as JBT/JBDS update sites > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-19336 > URL: https://issues.jboss.org/browse/JBIDE-19336 > 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.Alpha2 > > Attachments: two-versions-of-a-feature-not-good.png > > > For master branch I'm getting conflicts between what's in JBT and what's in Central: > {code} > 17:01:57 [p2.dir] Only one of the following can be installed at once: > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150212-1941-B633 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150212-1941-B633) > 17:01:57 [p2.dir] JBoss Tools Maven Packaging Configurator 1.7.0.Alpha1-v20150213-0945-B3 (org.jboss.tools.maven.jbosspackaging.feature.feature.jar 1.7.0.Alpha1-v20150213-0945-B3) > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish.sh in parent pom as versioned maven dependency

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria edited comment on JBIDE-18772 at 4/7/15 10:38 AM: ----------------------------------------------------------------- {quote}If we push a call to rsync.sh into the parent pom for all projects that use the parent pom, we might want to wrap that with a profile so that local builds don't attempt to deploy. Or so that other projects that use the parent pom (like jbosstools-discovery) don't try to deploy accidentally. Does that make sense? {quote} Yes, I think it does make sense. I'll make a PR for parent pom. was (Author: mickael_istria): {quote{If we push a call to rsync.sh into the parent pom for all projects that use the parent pom, we might want to wrap that with a profile so that local builds don't attempt to deploy. Or so that other projects that use the parent pom (like jbosstools-discovery) don't try to deploy accidentally. Does that make sense? {quote} Yes, I think it does make sense. I'll make a PR for parent pom. > Include publish.sh in parent pom as versioned maven dependency > -------------------------------------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha2 > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-16220) create an all-in-one build for JBT projects, using submodules

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16220?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16220: ----------------------------------- Issue Type: Enhancement (was: Bug) > create an all-in-one build for JBT projects, using submodules > ------------------------------------------------------------- > > Key: JBIDE-16220 > URL: https://issues.jboss.org/browse/JBIDE-16220 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 4.3.x > > Attachments: buildlog_maven311.txt > > > Git 1.8.2 includes an option to have submodules track a branch tip, rather than specific commit IDs. > {code:title=https://github.com/git/git/blob/master/Documentation/RelNotes/1.8.2.txt#L186-L188} > "git submodule" started learning a new mode to integrate with the > tip of the remote branch (as opposed to integrating with the commit > recorded in the superproject's gitlink). > {code} > Therefore, while the solution [~dgolovin] has for his https://github.com/dgolovin/jbosstools-submodules project is a decent option, it requires updating to stay current with branch tips. It's therefore only really as useful as it stays current. > If we can get Git 1.8.2 or newer installed on the Jenkins slaves, we could do a submodule build against whatever branch we wanted - master, 4.2.0.Alpha1x, etc. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18927) Multiple target platform has validation problems related to jetty sources

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18927?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-18927. ------------------------------------ Resolution: Done > Multiple target platform has validation problems related to jetty sources > ------------------------------------------------------------------------- > > Key: JBIDE-18927 > URL: https://issues.jboss.org/browse/JBIDE-18927 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > Attachments: jetty-sources.png, validation-button.png > > > multiple target platform reports validation problems: > !jetty-sources.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

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