September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20830) "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType'

by The Alchemist (JIRA)

The Alchemist created JBIDE-20830: ------------------------------------- Summary: "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' Key: JBIDE-20830 URL: https://issues.jboss.org/browse/JBIDE-20830 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: ejb3 Reporter: The Alchemist Priority: Minor If you have the following {{ejb-jar.xml}}, which I got from the Jboss Wiki: {code:xml} <?xml version="1.0"?> <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:s="urn:security:1.1" xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" version="3.1" impl-version="2.0"> <enterprise-beans> <message-driven> <ejb-name>ReplyingMDB</ejb-name> <ejb-class>org.jboss.as.test.integration.ejb.mdb.messagedestination.ReplyingMDB</ejb-class> <activation-config> <activation-config-property> <activation-config-property-name>destination</activation-config-property-name> <activation-config-property-value>java:jboss/mdbtest/messageDestinationQueue </activation-config-property-value> </activation-config-property> </activation-config> </message-driven> </enterprise-beans> <assembly-descriptor> <s:security> <ejb-name>DDMyDomainSFSB</ejb-name> <s:security-domain>myDomain</s:security-domain> <s:run-as-principal>myPrincipal</s:run-as-principal> </s:security> </assembly-descriptor> </jboss:ejb-jar> {code} You'll get a few warnings: !screenshot.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20830) "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType'

by The Alchemist (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20830?page=com.atlassian.jira.plugi... ] The Alchemist updated JBIDE-20830: ---------------------------------- Attachment: screenshot.png > "src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' > ----------------------------------------------------------------- > > Key: JBIDE-20830 > URL: https://issues.jboss.org/browse/JBIDE-20830 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: ejb3 > Reporter: The Alchemist > Priority: Minor > Attachments: screenshot.png > > > If you have the following {{ejb-jar.xml}}, which I got from the Jboss Wiki: > {code:xml} > <?xml version="1.0"?> > <jboss:ejb-jar xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:s="urn:security:1.1" > xsi:schemaLocation="http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd" > version="3.1" > impl-version="2.0"> > <enterprise-beans> > <message-driven> > <ejb-name>ReplyingMDB</ejb-name> > <ejb-class>org.jboss.as.test.integration.ejb.mdb.messagedestination.ReplyingMDB</ejb-class> > <activation-config> > <activation-config-property> > <activation-config-property-name>destination</activation-config-property-name> > <activation-config-property-value>java:jboss/mdbtest/messageDestinationQueue > </activation-config-property-value> > </activation-config-property> > </activation-config> > </message-driven> > </enterprise-beans> > <assembly-descriptor> > <s:security> > <ejb-name>DDMyDomainSFSB</ejb-name> > <s:security-domain>myDomain</s:security-domain> > <s:run-as-principal>myPrincipal</s:run-as-principal> > </s:security> > </assembly-descriptor> > </jboss:ejb-jar> > {code} > You'll get a few warnings: > !screenshot.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-508: ---------------------------------- This seems more optimized to me (if it's ok w/ Max) - I'll take a pass through my release process doc. The good news is that the current JBTIS 4.2.4/ JBDSIS 8.0.4 release has no EA content anymore. What specifically should be done w/ devstudio IS discovery? > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20804) Flaky source lookup while debugging apps deployed on Wildfly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20804?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-20804. ------------------------------------ Resolution: Done The bug was fixed in both: 4.3.x (CR2) - https://github.com/jbosstools/jbosstools-central/commit/9cd4000bcbe27ea17... and master - https://github.com/jbosstools/jbosstools-central/commit/c096ec90491e7e5d0... But tests were pushed only to master - https://github.com/jbosstools/jbosstools-central/commit/d3ea9d3e98dba4a8f... > Flaky source lookup while debugging apps deployed on Wildfly > ------------------------------------------------------------ > > Key: JBIDE-20804 > URL: https://issues.jboss.org/browse/JBIDE-20804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven > Affects Versions: 4.3.0.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.CR2 > > > When debugging an application deployed on Wildfly, some sources can not be found even though a matching source jar exists in Maven Central. > - create an html5 app > - put a breakpoint on MemberService.listAllMembers() > - Debug As > Debug on Server (choose Wildfly 10) > - when the web page is displayed, the breakpoint is hit > - go down the stacktrace, source should be downloaded for each line > - reach io.undertow.server.handlers.PredicateHandler, no source can be found > The problem is caused by the class file being found in the wildfly-cli client jar. But it has no matching source jar containing the Predicate.java file. The same class exists in undertow-core.jar, which has a matching source jar. But the source lookup stopped once it found wildfly-cli.jar, regardless if an actual source could be found. It should keep looking until an actual source is found -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-508) integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-508?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-508: ---------------------------------- Found a couple other problems: JBTIS-509, JBTIS-510. > integration stack update sites mix discovery and earlyaccess causing inconsistent update mechanism > -------------------------------------------------------------------------------------------------- > > Key: JBTIS-508 > URL: https://issues.jboss.org/browse/JBTIS-508 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: releng > Reporter: Max Rydahl Andersen > Assignee: Paul Leacu > Priority: Blocker > > While reviewing JBIDE-20803 I noticed the following: > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2.4=http://downlo... > {code} > The stable release for 4.2.4 is stated to point to the stable integration stack url which on surface looks good: > But there are a few problems: > 1) why not just point to http://download.jboss.org/jbosstools/updates/stable/luna/ and have the above internal detail url composited in ? > 2) the actual composite behind it right now is http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... which links in http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... (our main sites should never composite earlyaccees since then when users install supported versions they suddenly will now also have access to earlyaccess. > #1 is mainly just to reduce the number of updatesites actually necessary for users to work with > #2 seems to be something inherent broken in the IS build since earlyaccess shold *never* be aggregated into the release site. > Any earlyaccess connectors should explicitly point to a *separate* earlyaccess site. > I would also have expected that the discovery site with the discovery plugins was kept *separate* from the actual update sites to avoid any coupling between these. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-510) did JBDS IS 8.0.3 never graduate from Early Access?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-510?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-510: ----------------------------- Attachment: jbdsis803-still-ea.png !jbdsis803-still-ea.png! > did JBDS IS 8.0.3 never graduate from Early Access? > --------------------------------------------------- > > Key: JBTIS-510 > URL: https://issues.jboss.org/browse/JBTIS-510 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: distribution > Affects Versions: 8.0.3.GA > Reporter: Nick Boldt > Attachments: jbdsis803-still-ea.png > > > On Aug 27, [~pleacu] sent a note to jbds-is-pm-list(a)redhat.com, > soa-tools-list(a)redhat.com, > jbosstools-dev(a)lists.jboss.org, > jboss-qe-leads(a)redhat.com announcing, "JBDSIS 8.0.3.GA/ JBTIS 4.2.3.Final now live". > But when I look at https://devstudio.redhat.com/updates/8.0/ I see no JBDS 8.0.3 content. Instead, this content remains on https://devstudio.redhat.com/earlyaccess/8.0/ > Is that what we intended to happen? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-510) did JBDS IS 8.0.3 never graduate from Early Access?

by Nick Boldt (JIRA)

Nick Boldt created JBTIS-510: -------------------------------- Summary: did JBDS IS 8.0.3 never graduate from Early Access? Key: JBTIS-510 URL: https://issues.jboss.org/browse/JBTIS-510 Project: JBoss Tools Integration Stack Issue Type: Sub-task Components: distribution Affects Versions: 8.0.3.GA Reporter: Nick Boldt On Aug 27, [~pleacu] sent a note to jbds-is-pm-list(a)redhat.com, soa-tools-list(a)redhat.com, jbosstools-dev(a)lists.jboss.org, jboss-qe-leads(a)redhat.com announcing, "JBDSIS 8.0.3.GA/ JBTIS 4.2.3.Final now live". But when I look at https://devstudio.redhat.com/updates/8.0/ I see no JBDS 8.0.3 content. Instead, this content remains on https://devstudio.redhat.com/earlyaccess/8.0/ Is that what we intended to happen? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20152) script the process of branching and tagging based on buildinfo.json

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20152?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-20152. ---------------------------------- > script the process of branching and tagging based on buildinfo.json > ------------------------------------------------------------------- > > Key: JBIDE-20152 > URL: https://issues.jboss.org/browse/JBIDE-20152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.3.0.CR1 > > > {quote} > Last time I suggested we created a file with a line for each repo, like: > {code}jbosstools/jbosstools-hibernate, 13asd123asd232, jbosstools-4.3.0.Beta1{code} > You had a txt file before that had this information but in a hard-to-parse format. > I can try parse the buildinfo.json too but thought if you had the simpler one I could use that instead. > /max {quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20826) Web module's URL is not detected correctly

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20826?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20826: ----------------------------------- Component/s: maven > Web module's URL is not detected correctly > ------------------------------------------ > > Key: JBIDE-20826 > URL: https://issues.jboss.org/browse/JBIDE-20826 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport, maven, server > Affects Versions: 4.3.0.CR1 > Reporter: Lucia Jelinkova > Assignee: Rob Stryker > Fix For: 4.3.x > > > The module's URL is not detected correctly in case project name is different to context-root mentioned in .settings/org.eclipse.wst.common.component. > This could happen for example when you import Maven project using Easymport. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-509) clean up duplicate IS content in JBT EA sites (Luna / 4.2)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-509?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-509: ----------------------------- Attachment: why-need-2-copies-of-jbtis-ea-tp.png !why-need-2-copies-of-jbtis-ea-tp.png! > clean up duplicate IS content in JBT EA sites (Luna / 4.2) > ---------------------------------------------------------- > > Key: JBTIS-509 > URL: https://issues.jboss.org/browse/JBTIS-509 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: distribution > Affects Versions: 4.2.3.Final > Reporter: Nick Boldt > Attachments: why-need-2-copies-of-jbtis-ea-tp.png > > > Using the p2 browser, I looked into the contents of these sites: > http://download.jboss.org/jbosstools/earlyaccess/stable/luna/ > http://download.jboss.org/jbosstools/earlyaccess/development/luna/ > And see that there are two copies of the earlyaccess jbtistarget: 4.2.6.Final and 4.2.7.Final. > Why do you need both? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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