August 2013 - jbosstools-issues - Jboss List Archives

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

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15332: ---------------------------------------- Some big downloads (such as AS and seam IIRC) are actually fetched using the maven-dependency-plugin, which was formerly used only for big test dependencies. The solution would be to remove that flag from the parent pom, and instead move it to all executions of maven-download-plugin that are "big test dependencies", A workaround for Denis' patch is to explicitly put <skip>false</skip> in the okugin execution. > 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: Bug > Components: Build/Releng > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15317) LiveReload script injection corrupted html encoding

by Pei-Tang Huang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15317?page=com.atlassian.jira.plugi... ] Pei-Tang Huang commented on JBIDE-15317: ---------------------------------------- More information about Chrome Content-Length handling here: http://stackoverflow.com/questions/10125784/what-kind-of-network-error-is... > LiveReload script injection corrupted html encoding > --------------------------------------------------- > > Key: JBIDE-15317 > URL: https://issues.jboss.org/browse/JBIDE-15317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Pei-Tang Huang > Assignee: Max Rydahl Andersen > Priority: Critical > Labels: encoding, livereload > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > Attachments: chinese.html > > Original Estimate: 1 day > Remaining Estimate: 1 day > > LiveReload script injection dissmisses the encoding of the original HTML content, my page contains CJK character in UTF-8 all became "?" character. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15353) PMD 4.0.1

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-15353: -------------------------------------- Summary: PMD 4.0.1 Key: JBIDE-15353 URL: https://issues.jboss.org/browse/JBIDE-15353 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: target-platform, upstream Reporter: Mickael Istria Priority: Minor PMD 4.0.1 was released a few days ago and is not available in the new official site: https://sourceforge.net/projects/pmd/files/pmd-eclipse/update-site/ It appears that this site also fixes the issue we got with Partial IU ( https://sourceforge.net/p/pmd/bugs/1098/ ) and should simply get mirrored (no need for regenerating p2 metadata) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15317) LiveReload script injection corrupted html encoding

by Pei-Tang Huang (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15317?page=com.atlassian.jira.plugi... ] Pei-Tang Huang commented on JBIDE-15317: ---------------------------------------- Current patch broken on Chrome, I submitted a pull request correcting this problem here: https://github.com/xcoulon/jbosstools-livereload/pull/2 > LiveReload script injection corrupted html encoding > --------------------------------------------------- > > Key: JBIDE-15317 > URL: https://issues.jboss.org/browse/JBIDE-15317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Pei-Tang Huang > Assignee: Max Rydahl Andersen > Priority: Critical > Labels: encoding, livereload > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > Attachments: chinese.html > > Original Estimate: 1 day > Remaining Estimate: 1 day > > LiveReload script injection dissmisses the encoding of the original HTML content, my page contains CJK character in UTF-8 all became "?" character. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-141?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-141: ----------------------------- Fix Version/s: 4.0.2 4.1.2 (was: 4.0.1) (was: 4.1.1) > fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb > ----------------------------------------------------------------------------- > > Key: JBTIS-141 > URL: https://issues.jboss.org/browse/JBTIS-141 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, ESB, jBPM3 > Affects Versions: 4.0.0, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.2, 4.1.2 > > > Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. > Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-141?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-141: ---------------------------------- Similarly, the following sites contain only .Final versions of BPEL 1.2.100, ESB 1.5.300, and jBPM3 4.5.200: http://download.jboss.org/jbosstools/builds/staging/JBTIS-aggregate-disc/... http://download.jboss.org/jbosstools/updates/integration/kepler/integrati... > fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb > ----------------------------------------------------------------------------- > > Key: JBTIS-141 > URL: https://issues.jboss.org/browse/JBTIS-141 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, ESB, jBPM3 > Affects Versions: 4.0.0, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1, 4.1.1 > > > Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. > Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-141?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-141 at 8/19/13 10:20 AM: ------------------------------------------------------------ Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=8 *DONE* Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=2 *DONE* http://download.jboss.org/jbosstools/builds/staging/JBTIS-aggregate-disc-... now contains only .Final versions of BPEL 1.2.1, ESB 1.5.200, and jBPM3 4.5.100. was (Author: nickboldt): Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=8 *DONE* Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=2 > fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb > ----------------------------------------------------------------------------- > > Key: JBTIS-141 > URL: https://issues.jboss.org/browse/JBTIS-141 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, ESB, jBPM3 > Affects Versions: 4.0.0, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1, 4.1.1 > > > Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. > Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-141) fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-141?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBTIS-141 at 8/19/13 10:21 AM: ------------------------------------------------------------ Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=8 *DONE* Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=2 *DONE* The following sites now contain only .Final versions of BPEL 1.2.1, ESB 1.5.200, and jBPM3 4.5.100. * http://download.jboss.org/jbosstools/builds/staging/JBTIS-aggregate-disc-... * http://download.jboss.org/jbosstools/updates/integration/juno/integration... was (Author: nickboldt): Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=8 *DONE* Respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/JBTI... >=2 *DONE* http://download.jboss.org/jbosstools/builds/staging/JBTIS-aggregate-disc-... now contains only .Final versions of BPEL 1.2.1, ESB 1.5.200, and jBPM3 4.5.100. > fix JBTIS composite sites to include correct versions of jbpm3, bpel, and esb > ----------------------------------------------------------------------------- > > Key: JBTIS-141 > URL: https://issues.jboss.org/browse/JBTIS-141 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: BPEL, distribution, ESB, jBPM3 > Affects Versions: 4.0.0, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.0.1, 4.1.1 > > > Need to update the URLs in the composite*.xml files to point at the newly minted esb, jbpm3 and bpel update sites for 4.0.x and 4.1.x streams. > Also found some other problems in the compositeContent.xml files in that they contain a compositeArtifactRepository instead of compositeMetadataRepository so I'll attach a PR for that fix too. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2425) JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2425?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-2425. ---------------------------- Fixed in post-7.0.0.GA update to Central Discovery plugin (B276). Verified now works from within default OOTB JBDS 7.0.0.GA install to launch this page [1] when certification links on Central's Software/Update tab are clicked. [1] https://devstudio.jboss.com/updates/7.0/central/ Closing. > JBoss Central lists features as tested or supported - but the tooltip link provided does not include a definition of these terms > -------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2425 > URL: https://issues.jboss.org/browse/JBDS-2425 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Central > Affects Versions: 6.0.0.CR1 > Environment: Version: 6.0.0.CR1 > Build id: CR1-v20121204-0201-B166 > Build date: 20121204-0201 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 7.0.0.GA > > Attachments: 2425.png, 2425_2.png, 2425_3.png > > > In JBoss Central (see attached screenshot), features are listed as "tested" or "supported" - but the active links provided take the user to: https://devstudio.jboss.com/download/ > Where these terms are not defined. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-139) ensure that shared categories in JBTIS/JBDSIS update sites / Central discovery plugin use same categories as in JBT/JBDS

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-139?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-139. ------------------------------ Fix Version/s: 4.1.2 Resolution: Done Corrected labels in categories and connectors where appropriate. https://github.com/jbosstools/jbosstools-integration-stack/pull/77 > ensure that shared categories in JBTIS/JBDSIS update sites / Central discovery plugin use same categories as in JBT/JBDS > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBTIS-139 > URL: https://issues.jboss.org/browse/JBTIS-139 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 4.1.1 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.1.2 > > > Per discussion today, we need to ensure that any features in JBTIS or JBDSIS which need to be categorized into existing JBT or JBDS categories (update site + Central) will appear correctly, and in the existing JBT / JBDS categories. > To make sure this is the case, you'll want to diff your aggregate update site's category.xml (look for matching <category-def>) and discovery plugin's plugin.xml (look for <connectorCategory>) files with these equivalent files from JBT/JBDS: > Master branch: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/categ... > https://github.com/jbosstools/jbosstools-discovery/blob/master/jbosstools... > https://github.com/jbosstools/jbosstools-discovery/blob/master/jbdevstudi... > 4.1.x branch: > https://github.com/jbosstools/jbosstools-build-sites/blob/jbosstools-4.1.... > https://github.com/jbdevstudio/jbdevstudio-product/blob/jbosstools-4.1.x/... > https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.1.x/... > https://github.com/jbosstools/jbosstools-discovery/blob/jbosstools-4.1.x/... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 7 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 August 2013