January 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3269) FeedHenry Build Farm Integration Level 1

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3269?page=com.atlassian.jira.plugin.... ] Gorkem Ercan commented on JBDS-3269: ------------------------------------ [~maxandersen] thanks. > FeedHenry Build Farm Integration Level 1 > ---------------------------------------- > > Key: JBDS-3269 > URL: https://issues.jboss.org/browse/JBDS-3269 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 8.1.0.GA > > > Level 1: > 1) git push of Hybrid Mobile Cordova Projects to FH provided URL > 2) Using the Web UI to start the build process > 3) Using the Web UI to review the QR Code -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19058) refactor output.html and product.html into report_detailed.html and report_summary.html

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19058?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-19058: ------------------------------- Description: Today, vwatch produces two files: * a detailed, tabular report called "output.hml" * a summary report called "product.html" In Jenkins, I then rename these to results*.html and report*.html, which is a bit confusing because the files are not listed next to each other in the http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... folder. So, I propose we generate the files with these names: * report_detailed.html * report_summary.html Then in Jenkins we can simply rename them to include a timestamp/buildID prefix, and continue to differentiate the "all" report from the org.jboss-only "filtered" report: * 2015-01-07_17-28-06_B1766_report_detailed_all.html * 2015-01-07_17-28-06_B1766_report_detailed_filtered.html * 2015-01-07_17-28-06_B1766_report_summary_all.html * 2015-01-07_17-28-06_B1766_report_summary_filtered.html was: Today, vwatch produces two files: * a detailed, tabular report called "output.hml" * a summary report called "report.html" In Jenkins, I then rename these to results*.html and report*.html, which is a bit confusing because the files are not listed next to each other in the http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... folder. So, I propose we generate the files with these names: * report_detailed.html * report_summary.html Then in Jenkins we can simply rename them to include a timestamp/buildID prefix, and continue to differentiate the "all" report from the org.jboss-only "filtered" report: * B1766_2015-01-07_17-28-06_report_detailed_all.html * B1766_2015-01-07_17-28-06_report_detailed_filtered.html * B1766_2015-01-07_17-28-06_report_summary_all.html * B1766_2015-01-07_17-28-06_report_summary_filtered.html > refactor output.html and product.html into report_detailed.html and report_summary.html > --------------------------------------------------------------------------------------- > > Key: JBIDE-19058 > URL: https://issues.jboss.org/browse/JBIDE-19058 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa > Reporter: Nick Boldt > > Today, vwatch produces two files: > * a detailed, tabular report called "output.hml" > * a summary report called "product.html" > In Jenkins, I then rename these to results*.html and report*.html, which is a bit confusing because the files are not listed next to each other in the http://download.jboss.org/jbosstools/builds/staging/devstudio.versionwatc... folder. > So, I propose we generate the files with these names: > * report_detailed.html > * report_summary.html > Then in Jenkins we can simply rename them to include a timestamp/buildID prefix, and continue to differentiate the "all" report from the org.jboss-only "filtered" report: > * 2015-01-07_17-28-06_B1766_report_detailed_all.html > * 2015-01-07_17-28-06_B1766_report_detailed_filtered.html > * 2015-01-07_17-28-06_B1766_report_summary_all.html > * 2015-01-07_17-28-06_B1766_report_summary_filtered.html -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15332: ---------------------------------------- Comment: was deleted (was: also why do we have both maven-download-plugin and download-maven-plugin configured. should it not only be download-maven-plugin ? ) > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15332) why are skipRequirements controlling download of normal maven dependencies ?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15332: --------------------------------------------- also why do we have both maven-download-plugin and download-maven-plugin configured. should it not only be download-maven-plugin ? > why are skipRequirements controlling download of normal maven dependencies ? > ---------------------------------------------------------------------------- > > Key: JBIDE-15332 > URL: https://issues.jboss.org/browse/JBIDE-15332 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Beta1 > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > > I stumbled on [~dgolovin]'s patch for livreload at https://github.com/jbosstools/jbosstools-livereload/pull/54/files > This is not the first time i've seen skip having to be enabled for plain normal mvn dependencies. > skipRequirements are supposed to only cover big downloads (like EAP, jboss etc.) - things done via non-maven download mechanism. > Why is this applied to mvn dependency downloads ? > The culprit for needing this line is at: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > and a bugzilla (*not* jira?!) is referenced as the reason for this back in 2012: https://github.com/jbosstools/jbosstools-build/commit/2e18baaf88e0cd73b3b... > I understand why the explicit google download plugin (why is there two versions used btw?) but why is skipTests controlling normal mvn dependency download ? Which requirements are using this for download ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19063) Ensure that new "bumped.png" image is published when vwatch reports are archived in Jenkins / published to dl.jb.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19063?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19063: ---------------------------------- Assignee: Jiri Peterka (was: Nick Boldt) > Ensure that new "bumped.png" image is published when vwatch reports are archived in Jenkins / published to dl.jb.org > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19063 > URL: https://issues.jboss.org/browse/JBIDE-19063 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, qa > Affects Versions: 4.2.2.Final > Reporter: Nick Boldt > Assignee: Jiri Peterka > > A new bumped icon has been added to the vwatch reports [ in jbdevstudio-qa/vwatch/target/bumped.png ], but it's not included in what is archived in Jenkins and published to dl.jb.org. > So, we need to ensure that any images are published when vwatch reports are archived in Jenkins / published to dl.jb.org -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3269) FeedHenry Build Farm Integration Level 1

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3269?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3269: ------------------------------------------- I do not follow why both need to there since its stated that JBDS-3269 cannot be done before JBDS-3287 is done ...so why is JBDS-3287 then not just marked as resolved when that time comes and note to QE that before they close JBDS-3287 they should test what is described in this jira ? That would reduce the number of jiras we would have to juggle around. Anyways, since you prefer it like that i've reopend JBDS-3287 again (p.s. you can just do that in future - dont need to wait for me) > FeedHenry Build Farm Integration Level 1 > ---------------------------------------- > > Key: JBDS-3269 > URL: https://issues.jboss.org/browse/JBDS-3269 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid, requirements > Reporter: Burr Sutter > Assignee: Gorkem Ercan > Fix For: 8.1.0.GA > > > Level 1: > 1) git push of Hybrid Mobile Cordova Projects to FH provided URL > 2) Using the Web UI to start the build process > 3) Using the Web UI to review the QR Code -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3319) JBDS 9.0 installer underreports space requirement by 225 - 250MB

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3319?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3319: ------------------------------------------- so roll back to tycho 0.21 until issue fixed ? > JBDS 9.0 installer underreports space requirement by 225 - 250MB > ---------------------------------------------------------------- > > Key: JBDS-3319 > URL: https://issues.jboss.org/browse/JBDS-3319 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.2.GA > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > The (eap embedded) installer for JBDS 8.0.2 informs the user that this much disk space is required: > Disk Space: > Available Disk Space: 31.64 GB Required Disk Space: 585.78 MB > The actual install uses this much: > du -sh installdir/ > 822M installdir/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3319) JBDS 9.0 installer underreports space requirement by 225 - 250MB

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3319?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3319: ---------------------------------- Unfortunately I can't test this because with the migration to Tycho 0.22 (and repository-utils 0.22.1-SNAPSHOT) I can't get jbdevstudio-product to build locally or in Jenkins. :( cc: [~dgolovin] [~mickael_istria] [~maxandersen] ). > JBDS 9.0 installer underreports space requirement by 225 - 250MB > ---------------------------------------------------------------- > > Key: JBDS-3319 > URL: https://issues.jboss.org/browse/JBDS-3319 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 8.0.2.GA > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > The (eap embedded) installer for JBDS 8.0.2 informs the user that this much disk space is required: > Disk Space: > Available Disk Space: 31.64 GB Required Disk Space: 585.78 MB > The actual install uses this much: > du -sh installdir/ > 822M installdir/ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19047) Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19047?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-19047 at 1/26/15 4:55 PM: -------------------------------------------------------------- you should have seen some markers on the projects or errors in the logs. like : !http://content.screencast.com/users/fbricon/folders/Jing/media/025a9592-9d11-41f2-91ca-01b394b1fff0/00000053.png! Could you whip up a sample project to see if I need to get m2e-wtp to behave more appropriately? was (Author: fbricon): you should have seen some markers on the projects or errors in the logs. Could you whip up a sample project to see if I need to get m2e-wtp to behave more appropriately? > Issue deploying EAR project from eclipse to Wildfly using JBoss Tools Plugin > ---------------------------------------------------------------------------- > > Key: JBIDE-19047 > URL: https://issues.jboss.org/browse/JBIDE-19047 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server, upstream > Environment: Ubuntu 14.04, Wildfly 8.2.0 FInal, Eclipse Luna > Reporter: Nick . > Assignee: Fred Bricon > Fix For: 4.3.x > > Attachments: sample.zip, settings.zip > > > Hi, > I have a maven EAR project, which contains a couple of WAR and JAR files. I'm using Eclipse Luna (tried STS and IntelliJ ) IDE with JBoss Tools 1.6.0 (latest). > When I try to deploy my EAR to Wildfly (as well as in EAP 6.2.0) with JBoss Tools from eclipse i'm facing the following issues. > My Jars (external jars and project jar) are getting copied into WEB-INF/lib and EAR/lib, where i expected it to be only in EAR/lib. > EAR application.xml is not getting copied into EAR/META-INF/ folder > But when i use command line to build my project , i'm not experiencing the above issue. > FYI : We are using <skinnyWars>true</skinnyWars>. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19090) jbosstools-maven-plugins requires Java 7 but compiles to Java 8 requirement?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19090?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19090: --------------------------------------------- yes, we should not use this library - why are we using it ? can't we just use dmr as we use everywhere else for json ? > jbosstools-maven-plugins requires Java 7 but compiles to Java 8 requirement? > ---------------------------------------------------------------------------- > > Key: JBIDE-19090 > URL: https://issues.jboss.org/browse/JBIDE-19090 > 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.Alpha1 > > > Parent pom compilation is now failing if run with JDK 7 (but works w/ JDK 8): > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build.parent_master/419/} > [8mha:AAAAYB+LCAAAAAAAAP9b85aBtbiIQSmjNKU4P0+vJLE4u1gvPjexLDVPzxdEuhYV5Rf55ZekOlc7RKnPKH7IxMBQUcQgBdWQnJ9XnJ+TqucMoUEKGSCAEaSwAACsNFCqYAAAAA== > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site (generate-full-site) on project > parent: Execution generate-full-site of goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site failed: An API > incompatibility was encountered while executing org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site: > java.lang.UnsupportedClassVersionError: org/json/JSONObject : Unsupported major.minor version 52.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 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 January 2015