May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22248) Some CI jobs fail at deploying to Nexus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22248?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22248: ------------------------------------ [~mickael_istria] Do you mean eng-ops has fixed the load balancer, or my workaround [1],[2] worked? [1] https://github.com/jbosstools/jbosstools-build/commit/9855f568a24386f47b9... [2] https://github.com/jbosstools/jbosstools-target-platforms/commit/4b3a9580... > Some CI jobs fail at deploying to Nexus > --------------------------------------- > > Key: JBIDE-22248 > URL: https://issues.jboss.org/browse/JBIDE-22248 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Nick, can you take a look why mvn deploy fails here? > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > It worked for us in the past. > It says: > {code} > [WARNING] Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 04:49 min > [INFO] Finished at: 2016-04-26T09:42:02-04:00 > [INFO] Final Memory: 19M/612M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project jboss-reddeer-archetype: Failed to retrieve remote metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml: Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > {code} > I'm not exactly sure how this works. Or is this something that is managed in jenkins config, so should I raise this with the jenkins team? > Cc: [~rawagner] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22248) Some CI jobs fail at deploying to Nexus

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22248?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22248: ---------------------------------------- Seems like things are now fixed automagically, aren't they? > Some CI jobs fail at deploying to Nexus > --------------------------------------- > > Key: JBIDE-22248 > URL: https://issues.jboss.org/browse/JBIDE-22248 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.0.Alpha1 > Reporter: Martin Malina > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Alpha1 > > > Nick, can you take a look why mvn deploy fails here? > https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > It worked for us in the past. > It says: > {code} > [WARNING] Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. > [INFO] ------------------------------------------------------------------------ > [INFO] BUILD FAILURE > [INFO] ------------------------------------------------------------------------ > [INFO] Total time: 04:49 min > [INFO] Finished at: 2016-04-26T09:42:02-04:00 > [INFO] Final Memory: 19M/612M > [INFO] ------------------------------------------------------------------------ > [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project jboss-reddeer-archetype: Failed to retrieve remote metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml: Could not transfer metadata org.jboss.reddeer:jboss-reddeer-archetype/maven-metadata.xml from/to jboss-snapshots-repository (https://repository.jboss.org/nexus/content/repositories/snapshots/): Not authorized , ReasonPhrase:Unauthorized. -> [Help 1] > [ERROR] > [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. > [ERROR] Re-run Maven using the -X switch to enable full debug logging. > [ERROR] > [ERROR] For more information about the errors and possible solutions, please read the following articles: > [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException > {code} > I'm not exactly sure how this works. Or is this something that is managed in jenkins config, so should I raise this with the jenkins team? > Cc: [~rawagner] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21597) New Application Wizard: OpenShift project is resetted to 1st entry when I get back

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21597?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21597. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > New Application Wizard: OpenShift project is resetted to 1st entry when I get back > ----------------------------------------------------------------------------------- > > Key: JBIDE-21597 > URL: https://issues.jboss.org/browse/JBIDE-21597 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: default-selected.png, testforuser-selected.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22157) On deployment, utility JAR projects are being exploded on WEB-INF/LIB

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22157: -------------------------------- Summary: On deployment, utility JAR projects are being exploded on WEB-INF/LIB (was: On deployoment, utility JAR projects are being exploded on WEB-INF/LIB) > On deployment, utility JAR projects are being exploded on WEB-INF/LIB > --------------------------------------------------------------------- > > Key: JBIDE-22157 > URL: https://issues.jboss.org/browse/JBIDE-22157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: Eclipse: Mars, latest version. > Webserver: Wilfly 10.0.0 > Maven: 3.3.3 > JBoss Tools: Latest version. > Reporter: Tiago Matias > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha2 > > Attachments: JBIDE22157.zip > > > Consider two eclipse maven projects: A Web project (WAR) and a Utility project JAR with a JSP TLD file inside. > After building the project and deploying to Wildfly the utiltiy JAR will be exploded under WEB-INF/LIB of the WAR project. > An exploded jar is incompatible with TLD files since the JSP engine search for the TLD file and then try to open/unzip the JAR. Since the JAR is just a folder, it causes an "Access Denied" exception, as shown below: > org.apache.jasper.JasperException: java.io.FileNotFoundException: C:\Program Files\Java\wildfly-10.0.0.Final\standalone\deployments\portal.web.war\WEB-INF\lib\portal.framework-0.0.1-SNAPSHOT.jar (Acesso negado) > org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:151) > org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:412) > org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475) > org.apache.jasper.compiler.Parser.parseElements(Parser.java:1456) > org.apache.jasper.compiler.Parser.parse(Parser.java:143) > A possible alternative would be to turnoff the option "Resolve dependencies from workspace projects" in Eclipse. In this scenario the JAR won't get exploded on WAR's WEB-INF/lib and everything works. However, any change to the JAR project won't get picked up and deployed to the target unless it's POM version is incremented which is incompatible with a development scenario where the projects are constantly updated and built. > I request that the eclipse wildfly connector provides an option to control weather the dependency JAR's are exploded or not into the final deployment. > Please note, this only applies to dependencies that are workspace projects. All the other dependencies (spring, hibernate, etc...) are simply copied as a JAR archive, as expected. > Thank you. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21063) Applcation wizard: error message tells me to select server template while I'm about to pick a local template

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21063?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21063. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Applcation wizard: error message tells me to select server template while I'm about to pick a local template > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-21063 > URL: https://issues.jboss.org/browse/JBIDE-21063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > Attachments: choosing-local-template-wrong-error.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21010) Add validation for a project name in case of duplicates

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21010?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21010. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Add validation for a project name in case of duplicates > ------------------------------------------------------- > > Key: JBIDE-21010 > URL: https://issues.jboss.org/browse/JBIDE-21010 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Optional > Fix For: 4.4.0.Alpha1 > > > There could be a simple validation of a project name for duplicates. It should not be necessary to hit Finish button in Create OpenShift Project dialog to find out that project already exists based on response from server. Simple validation based on existence of a tree item of project or some similar mechanism would be helpful. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-570) JBTIS Target Platform - add Birt reporting engine

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-570?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-570: ---------------------------------- Paul said: {quote} The JBTIS TP is now in place. It picks up Birt reporting plugins itself http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.4.0.Al... {quote} > JBTIS Target Platform - add Birt reporting engine > ------------------------------------------------- > > Key: JBTIS-570 > URL: https://issues.jboss.org/browse/JBTIS-570 > Project: JBoss Tools Integration Stack > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.4.0.Alpha1-TP > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 4.4.0.Alpha1-TP > > > Birt is needed by Teiid Designer. It is no longer needed by JBDS hance its movement out of JBDS core TP and into JBTIS TP. > ref: > https://issues.jboss.org/browse/JBIDE-21105 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21961) Styled texts are markable and it is possible to put caret into them

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21961?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21961. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > Styled texts are markable and it is possible to put caret into them > ------------------------------------------------------------------- > > Key: JBIDE-21961 > URL: https://issues.jboss.org/browse/JBIDE-21961 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Optional > Labels: openshift_v2, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Currently styled texts for "get started" and "retrieve token" parts (maybe there are other places) are almost perfect. What I found a place for an enhancement is making it similar to labels. I mean don't allow user to put caret into it (after mouse left click) and marking text would not be possible too. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20946) New Application wizard: Add multi-tag filtering to templates

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20946?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-20946. --------------------------------- Verified in Red Hat Developer Studio 10.0.0.Alpha1 B5264. > New Application wizard: Add multi-tag filtering to templates > ------------------------------------------------------------ > > Key: JBIDE-20946 > URL: https://issues.jboss.org/browse/JBIDE-20946 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Final > Reporter: Jeff Cantrill > Assignee: Fred Bricon > Priority: Optional > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Filtering in 'new app from template' is limited to a single value for name and tag. It would be useful to allow further filter by choosing all things that fit a comma or space delimited pattern of values. I don't know if this is an 'and' filtering or an 'or' filtering -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21750) OpenShift Explorer : running Builds should use the standard build execution icon

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21750?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21750. --------------------------------- Out of date. Icons were replaced by the one used in OpenShift in general. > OpenShift Explorer : running Builds should use the standard build execution icon > -------------------------------------------------------------------------------- > > Key: JBIDE-21750 > URL: https://issues.jboss.org/browse/JBIDE-21750 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > When a build is started, it shows up in the OpenShift explorer with the File icon. It should use a more standard eclipse build icon -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016