December 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3240) Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3240?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3240: ----------------------------- Fix Version/s: 8.0.1.GA > Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central > -------------------------------------------------------------------- > > Key: JBDS-3240 > URL: https://issues.jboss.org/browse/JBDS-3240 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Reporter: Marek Novotny > Assignee: Fred Bricon > Fix For: 8.0.1.GA > > > JBDS 8 aka JBoss Central provide by default old EAP/WFK archetype and not the latest 6.3.0.GA/2.6.0.Final by default. > For instance I click on HTML5 project in Start from Scratch in JBoss Central: > it launches wizard dialog where the archetype is org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:1.0.4.Final-redhat-wfk-2 version -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3240) Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3240?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3240: ----------------------------- Summary: Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central (was: JBDS 8 aka JBoss Central provide by default old EAP/WFK archetypes) > Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central > -------------------------------------------------------------------- > > Key: JBDS-3240 > URL: https://issues.jboss.org/browse/JBDS-3240 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Reporter: Marek Novotny > Assignee: Fred Bricon > > JBDS 8 aka JBoss Central provide by default old EAP/WFK archetype and not the latest 6.3.0.GA/2.6.0.Final by default. > For instance I click on HTML5 project in Start from Scratch in JBoss Central: > it launches wizard dialog where the archetype is org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:1.0.4.Final-redhat-wfk-2 version -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18772: ------------------------------------ PR 116 is already merged. -1 for PR 117. > 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.x > > > 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.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18848) setup tests for ide-config.properties

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18848?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18848: ---------------------------------------- Component/s: build common/jst/core > setup tests for ide-config.properties > ------------------------------------- > > Key: JBIDE-18848 > URL: https://issues.jboss.org/browse/JBIDE-18848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common/jst/core > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > > JBIDE-18837 and other jiras showed that ide-config.properties risk having errors introduced into it. > we should have a test that runs every day to check if it is still consistent. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18852) No warning about missing invocation handler for interface

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-18852: ---------------------------------------- Summary: No warning about missing invocation handler for interface Key: JBIDE-18852 URL: https://issues.jboss.org/browse/JBIDE-18852 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi-extensions Affects Versions: 4.2.1.CR1 Reporter: Rastislav Wagner Fix For: 4.3.0.Alpha1 1. Create CDI 1.1 project and add deltaspike libs 2. create partial bean binding {code} @PartialBeanBinding @Target(ElementType.TYPE) @Retention(RetentionPolicy.RUNTIME) public @interface ExamplePartialBeanBinding { } {code} 3.create interface {code} import javax.enterprise.context.ApplicationScoped; @ApplicationScoped @ExamplePartialBeanBinding public interface Interf { String sayHello(String hello); } {code} FAIL: There's no warning saying that class should have an invocation handler 4. create abstract class {code} import javax.enterprise.context.ApplicationScoped; @ApplicationScoped @ExamplePartialBeanBinding public abstract class Abs { public abstract String sayHello(String hello); public String otherHey (String hello) { return "Other: " + hello; } } {code} ASSERT: warning about missing invocation handler is displayed for abstract class 5. Check interface class again -> no warning, edit file & save -> warning is displayed -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18497) Importing PicketLink quickstart raises error

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18497?page=com.atlassian.jira.plugi... ] Radim Hopp edited comment on JBIDE-18497 at 12/1/14 7:48 AM: ------------------------------------------------------------- I stumbled onto this today... but I noticed one more thing regarding jboss-picketlink-sts quickstart: After importing as maven project, not only jboss-picketlink-sts appears in Project Explorer, but also project named "JSR-109 Web Services", which cannot be deleted (by delete key) but even right-click does not invoke context menu. Error log is silent. [~ldimaggio] did you notice something like this? was (Author: rhopp): I stumbled onto this today... but I noticed one more thing regarding jboss-picketlink-sts quickstart: After importing as maven project, not only jboss-picketlink-sts appears in Project Explorer, but also project named "JSR-109 Web Services", which cannot be deleted (by delete key) but even right-click does not invoke context menu. Error log is silent. > Importing PicketLink quickstart raises error > -------------------------------------------- > > Key: JBIDE-18497 > URL: https://issues.jboss.org/browse/JBIDE-18497 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1 > Java 1.7 - OpenJDK > RHEL6 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > Steps to recreate issue: > * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap > * Install JBDS8.0.CR1 > * Import-> Existing Maven Projects - select the quickstart > The error is: > jboss-picketlink-sts > Referenced file contains errors (http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-wsse-server.xml /jboss-picketlink-sts/src/main/webapp/WEB-INF line 1 XML Problem -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18497) Importing PicketLink quickstart raises error

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18497?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-18497: ------------------------------------ I stumbled onto this today... but I noticed one more thing regarding jboss-picketlink-sts quickstart: After importing as maven project, not only jboss-picketlink-sts appears in Project Explorer, but also project named "JSR-109 Web Services", which cannot be deleted (by delete key) but even right-click does not invoke context menu. Error log is silent. > Importing PicketLink quickstart raises error > -------------------------------------------- > > Key: JBIDE-18497 > URL: https://issues.jboss.org/browse/JBIDE-18497 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1 > Java 1.7 - OpenJDK > RHEL6 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > Steps to recreate issue: > * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap > * Install JBDS8.0.CR1 > * Import-> Existing Maven Projects - select the quickstart > The error is: > jboss-picketlink-sts > Referenced file contains errors (http://www.jboss.com/ws-security/schema/jboss-ws-security_1_0.xsd). For more information, right click on the message in the Problems View and select "Show Details..." jboss-wsse-server.xml /jboss-picketlink-sts/src/main/webapp/WEB-INF line 1 XML Problem -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18692) Jenkins build for jbosstools-incubator-ripple

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18692?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18692: ------------------------------------- [~mickael_istria], content of the *pkg/hosted* folder > Jenkins build for jbosstools-incubator-ripple > --------------------------------------------- > > Key: JBIDE-18692 > URL: https://issues.jboss.org/browse/JBIDE-18692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > We need a jenkins job to build for jbosstools-incubator-ripple, and have it > invoking "./configure && jake" and distribute the builds to Nexus so that cordovasim can start using ripple from this repo. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18692) Jenkins build for jbosstools-incubator-ripple

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18692?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18692: ---------------------------------------- [~ibuziuk] Once the build of Ripple is done, which folder/files do you need for your integration? > Jenkins build for jbosstools-incubator-ripple > --------------------------------------------- > > Key: JBIDE-18692 > URL: https://issues.jboss.org/browse/JBIDE-18692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > We need a jenkins job to build for jbosstools-incubator-ripple, and have it > invoking "./configure && jake" and distribute the builds to Nexus so that cordovasim can start using ripple from this repo. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18837) because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18837?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-18837 at 12/1/14 6:00 AM: ---------------------------------------------------------------------- [~nickboldt] we have been linking our test builds to different version of central/examples/EA through most if not all of our majority test phase thus that comment is just factually false. The only time this could actually happen is if a user/QE/dev *Explicitly* goes and install a *subpart* of jbosstools and go out of his ways to make sure he does not have the latest update to foundation. JBT already looks for specific versions. There is no need to introduce -D flags. It should be sufficient to just have: jboss.discovery.site.url|jbosstools|4.2=http://download.jboss.org/jbossto... jboss.discovery.site.url|jbosstools|4.2.1.CR1=http://download.jboss.org/j... or if you want nightlies to pick up latest development no matter what: jboss.discovery.site.url|jbosstools|4.2=http://download.jboss.org/jbossto... jboss.discovery.site.url|jbosstools|4.2.0=http://download.jboss.org/jboss... This is what we did until now - why is that not considered possible anymore ? The above stuff of course assumes we actually bump the version correctly but that is what we found we missed - that is now fixed. None of that requires *forceful* linking from parent pom to foundation down to the micro level. was (Author: maxandersen): [~nickboldt] we have been linking our test builds to different version of central/examples/EA through most if not all of our majority test phase thus that comment is just factually false. The only time this could actually happen is if a user/QE/dev *Explicitly* goes and install a *subpart* of jbosstools and go out of his ways to make sure he does not have the latest update to foundation. JBT already looks for specific versions. There is no need to introduce -D flags. It should be sufficient to just have: jboss.discovery.site.url|jbosstools|4.2=http://download.jboss.org/jbossto... jboss.discovery.site.url|jbosstools|4.2.1.CR1=http://download.jboss.org/j... or if you want nightlies to pick up latest development no matter what: jboss.discovery.site.url|jbosstools|4.2=http://download.jboss.org/jbossto... jboss.discovery.site.url|jbosstools|4.2.0=http://download.jboss.org/jboss... This is what we did until now - why is that now considered possible anymore ? The above stuff of course assumes we actually bump the version correctly but that is what we found we missed - that is now fixed. None of that requires *forceful* linking from parent pom to foundation down to the micro level. > because Foundation defines the version of JBoss Tools used to do ide-config.properties lookup, must enforce it's always updated > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18837 > URL: https://issues.jboss.org/browse/JBIDE-18837 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, common/jst/core, project-examples > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > When updating from 4.2.0 to 4.2.1, a user might decide to only update Central or Project Examples, and NOT update Foundation.core, which means his Eclipse will still think it's 4.2.0, not 4.2.1, and he might get the wrong version of central/examples. > Therefore we need manifest-level [4.2.1,) requirements on upstream foundation.core in examples and central, to force this lock-step updating. > And we need to use the maven enforcer plugin to fail the build if these versions get out of sync. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

10 years, 11 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2014