July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-17728: ---------------------------------- Attachment: IonicRadioWizBan.png IonicRadio.png > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png, IonicRadio.png, IonicRadioWizBan.png, List.png, ListWizBan.png, Scroll.png, ScrollWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17811) Incorrect bean injection eligibility assumption for beans excluded using DeltaSpike @Exclude

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17811?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-17811: -------------------------------------- Assignee: Viacheslav Kabanovich > Incorrect bean injection eligibility assumption for beans excluded using DeltaSpike @Exclude > -------------------------------------------------------------------------------------------- > > Key: JBIDE-17811 > URL: https://issues.jboss.org/browse/JBIDE-17811 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi-extensions > Environment: JBDS 8.0.0.Beta2d > Reporter: Ron Šmeral > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.CR1 > > > With the following classes on the classpath: > {code:java|title=DeactivatableTest.java} > @Inject > private MyBean myBean; > {code} > {code:java|title=MyBean.java} > @Exclude > public class MyBean {} > {code} > {code:java|title=ExcludeExtensionDeactivator.java} > public class ExcludeExtensionDeactivator implements ClassDeactivator { > public Boolean isActivated(Class<? extends Deactivatable> targetClass { > if (ExcludeExtension.class.equals(targetClass)) { > return false; > } > return null; > } > } > {code} > ..the injection point in DeactivatableTest is marked with a warning: > {noformat} > No bean is eligible for injection to the injection point [JSR-299 §5.2.1] {noformat} > ..which is incorrect. MyBean *is* eligible despite being annotated @Exclude, since ExcludeExtension is deactivated using the core DeltaSpike mechanism of deactivation (ClassDeactivator). > There does not seem to be a (simple) solution to this other than executing the code in all available ClassDeactivators. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17812) "No bean is eligible for injection" warning for beans added in AfterBeanDiscovery

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17812?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-17812: ----------------------------------- Fix Version/s: 4.2.0.CR1 > "No bean is eligible for injection" warning for beans added in AfterBeanDiscovery > --------------------------------------------------------------------------------- > > Key: JBIDE-17812 > URL: https://issues.jboss.org/browse/JBIDE-17812 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi-extensions > Reporter: Ron Šmeral > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.CR1 > > > JBDS shows _No bean is eligible for injection to the injection point_ warning for injection points where the beans are provided by an extension in the ABD event: > {code:java|title=ByIdExtensionTest.java} > @Inject @ById("rbenevides") > private Person rafael; > {code} > * shows _No bean is eligible for injection to the injection point \[JSR-299 §5.2.1\]_ > {code:java|title=ByIdExtension.java} > public void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) { > for (final String idValue : ids) { > BeanBuilder<Person> beanBuilder = new BeanBuilder<Person>(bm) > .beanClass(Person.class) > .types(Person.class, Object. > .qualifiers(new ByIdLiteral(idValue)) > .beanLifecycle(new PersonContextualLifecycle(idValue)); > abd.addBean(beanBuilder.create()); > } > } > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17812) "No bean is eligible for injection" warning for beans added in AfterBeanDiscovery

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17812?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-17812: -------------------------------------- Assignee: Viacheslav Kabanovich > "No bean is eligible for injection" warning for beans added in AfterBeanDiscovery > --------------------------------------------------------------------------------- > > Key: JBIDE-17812 > URL: https://issues.jboss.org/browse/JBIDE-17812 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi-extensions > Reporter: Ron Šmeral > Assignee: Viacheslav Kabanovich > Fix For: 4.2.0.CR1 > > > JBDS shows _No bean is eligible for injection to the injection point_ warning for injection points where the beans are provided by an extension in the ABD event: > {code:java|title=ByIdExtensionTest.java} > @Inject @ById("rbenevides") > private Person rafael; > {code} > * shows _No bean is eligible for injection to the injection point \[JSR-299 §5.2.1\]_ > {code:java|title=ByIdExtension.java} > public void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) { > for (final String idValue : ids) { > BeanBuilder<Person> beanBuilder = new BeanBuilder<Person>(bm) > .beanClass(Person.class) > .types(Person.class, Object. > .qualifiers(new ByIdLiteral(idValue)) > .beanLifecycle(new PersonContextualLifecycle(idValue)); > abd.addBean(beanBuilder.create()); > } > } > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17448) repository-utils should allow skipping generation of web content

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17448?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17448: ---------------------------------------- [~a_silgidjian] We are currently vaidating/rebuilding/releasing a milestone of JBDS. This process takes a few weeks during which ones we prefer avoiding taking any risk of breaking a build. So let's say that we'll try to release 0.19.0 version of those plugins after our Beta3 is release. This should be by the end of July/beginning of October (or earlier if we're lucky). > repository-utils should allow skipping generation of web content > ---------------------------------------------------------------- > > Key: JBIDE-17448 > URL: https://issues.jboss.org/browse/JBIDE-17448 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Robert Munteanu > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Beta3 > > > I'm using the repository-utils:generate-repository-facade goal to associate additional p2 update sites to my own update site. I'm not interested in generating an index.html file for it, but the default is to generate an update site with a JBoss layout. > Rather than providing my own index.html template, I'd prefer to skip the generation of web content altogether. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3085) Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3085?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3085: ---------------------------------- Right, and because uninstalling a product is problematic at best, my gut feeling here is we should NOT support the notion of upgrading from GA to non-GA. > Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access? > --------------------------------------------------------------------------- > > Key: JBDS-3085 > URL: https://issues.jboss.org/browse/JBDS-3085 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > > Max brought up a question on a call today: > *Should we be able to update JBDS 8.0.0.GA -> 8.1.0.Alpha1 via Early Access?* > This was supposedly in the original scope for the creation of a Early Access site, but I never saw that. So, in order to get some eyeballs on this idea, and to get buy-in from QE/doc/dev/PM/PgM/PL, I'm cc:'ing some people here so we can discuss the cons and cons of this idea. > cc: [~mmusaji] [~mmurray] [~mmalina] [~maxandersen] [~mickael_istria][~ldimaggio] [~burrsutter] [~jpallich] [~rruss] [~fbricon] > (Aside: has anyone noticed that there's an plethora of people with "M" names on this team?) > Things to consider: > a) what happens if an 8.0.0.GA user suddenly finds they've updated to an Alpha or Beta release? Can they uninstall? (Probably not, if they started with the installer; probably yes if they started from BYOE / Marketplace.) > b) how will GSS support these "I was on GA but not I'm on Beta" users? > c) What about project examples that might / might not be compatible between 8.0 and 8.x, eg., because of changes in Eclipse Luna or a new default runtime (EAP 6.3, 6.4) ? > d) what could possibly go wrong? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17448) repository-utils should allow skipping generation of web content

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17448?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17448: ------------------------------------ Other than having to update all the various refs in pom.xml files to 0.19.0 or 0.20.0-SNAPSHOT, no, I see no problem here. > repository-utils should allow skipping generation of web content > ---------------------------------------------------------------- > > Key: JBIDE-17448 > URL: https://issues.jboss.org/browse/JBIDE-17448 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Robert Munteanu > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Beta3 > > > I'm using the repository-utils:generate-repository-facade goal to associate additional p2 update sites to my own update site. I'm not interested in generating an index.html file for it, but the default is to generate an update site with a JBoss layout. > Rather than providing my own index.html template, I'd prefer to skip the generation of web content altogether. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17808: ---------------------------------------- Once installed, there is no way to know where an IU is coming from, so it means we'd need to keep that separated. Also, it's not because an IU comes from Early Access that it's not supported, What is the use-case for this feature? We could just compare the content of an installation to what's available on a reference p2 repo and say that everything that isn't on the reference p2 repo is not supported. > Identify which installed IUs are from Early Access vs. supported/tested versions > -------------------------------------------------------------------------------- > > Key: JBIDE-17808 > URL: https://issues.jboss.org/browse/JBIDE-17808 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Nick Boldt > Fix For: 4.2.0.Beta3 > > > [~maxandersen] brought up a good point on a call today: > we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location. > Thus we need some sort of UI to list installed IUs that are "Early Access". > This could be... (brainstorming now): > * a text file with the list of things installed from Early Access (features and plugins) > * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins > * a way to filter the plugin view (Help > About) to show only EA content (or exclude it) > * ... ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17812) "No bean is eligible for injection" warning for beans added in AfterBeanDiscovery

by Ron Šmeral (JIRA)

Ron Šmeral created JBIDE-17812: ---------------------------------- Summary: "No bean is eligible for injection" warning for beans added in AfterBeanDiscovery Key: JBIDE-17812 URL: https://issues.jboss.org/browse/JBIDE-17812 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi-extensions Reporter: Ron Šmeral JBDS shows _No bean is eligible for injection to the injection point_ warning for injection points where the beans are provided by an extension in the ABD event: {code:java|title=ByIdExtensionTest.java} @Inject @ById("rbenevides") private Person rafael; {code} * shows _No bean is eligible for injection to the injection point \[JSR-299 §5.2.1\]_ {code:java|title=ByIdExtension.java} public void afterBeanDiscovery(@Observes AfterBeanDiscovery abd, BeanManager bm) { for (final String idValue : ids) { BeanBuilder<Person> beanBuilder = new BeanBuilder<Person>(bm) .beanClass(Person.class) .types(Person.class, Object. .qualifiers(new ByIdLiteral(idValue)) .beanLifecycle(new PersonContextualLifecycle(idValue)); abd.addBean(beanBuilder.create()); } } {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17448) repository-utils should allow skipping generation of web content

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17448?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17448: ---------------------------------------- [~nickboldt] Do you see any issue in release our Maven plugins right now and starting a 0.20.0-SNAPSHOT stream? > repository-utils should allow skipping generation of web content > ---------------------------------------------------------------- > > Key: JBIDE-17448 > URL: https://issues.jboss.org/browse/JBIDE-17448 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Robert Munteanu > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Beta3 > > > I'm using the repository-utils:generate-repository-facade goal to associate additional p2 update sites to my own update site. I'm not interested in generating an index.html file for it, but the default is to generate an update site with a JBoss layout. > Rather than providing my own index.html template, I'd prefer to skip the generation of web content altogether. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 July 2014