May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19762) Remove JARs from cdi test projects

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19762?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19762: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-javaee/pull/330, https://github.com/jbosstools/jbosstools-javaee/pull/331 (was: https://github.com/jbosstools/jbosstools-javaee/pull/330) > Remove JARs from cdi test projects > ---------------------------------- > > Key: JBIDE-19762 > URL: https://issues.jboss.org/browse/JBIDE-19762 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdi, cdi-extensions > Affects Versions: 4.3.0.Beta1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.3.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18876: ------------------------------------ Problem was an unresolved variable (I was trying to resolve the version of the target platform dynamically from the value in the root pom, but assumed it could be parsed the same as the poms for central/EA) when publishing the updated target platform. So instead of pushing the update site ref'd by unified.target into http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... it went into http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/REPO/ I've added a more verbose check & failure to the job config. However, since unified.target depends on a successful publish, and it needs to be in github in order to be built, we retain this (somewhat) circular workflow. Here's what we do today: 1. push change to github for multiple.target and unified.target 2. deploy multiple.target to Nexus 3. rebuild target site 4. publish into http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/$\{... 5. deploy unified.target to Nexus (depends on the above URL being populated correctly & being up to date) Anyway, respinning: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... >=410 > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.3.x > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19772) Update fails with No repository found containing: osgi.bundle, org.apache.commons.io, 2.4.0

by Martin Schröder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19772?page=com.atlassian.jira.plugi... ] Martin Schröder updated JBIDE-19772: ------------------------------------ Attachment: bookmarks.xml Enabled repos > Update fails with No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19772 > URL: https://issues.jboss.org/browse/JBIDE-19772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.2.3.Final > Reporter: Martin Schröder > Assignee: Denis Golovin > Attachments: bookmarks.xml, jbosstools-diagnostics-20150506142332.zip > > > I'm trying to update my installed plugins in my Eclipse 4.4.2. This wants to update a lot of JBoss Tools components, but ultimately fails with > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19772) Update fails with No repository found containing: osgi.bundle, org.apache.commons.io, 2.4.0

by Martin Schröder (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19772?page=com.atlassian.jira.plugi... ] Martin Schröder commented on JBIDE-19772: ----------------------------------------- Yes. I've attached my installed repos. > Update fails with No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19772 > URL: https://issues.jboss.org/browse/JBIDE-19772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.2.3.Final > Reporter: Martin Schröder > Assignee: Denis Golovin > Attachments: jbosstools-diagnostics-20150506142332.zip > > > I'm trying to update my installed plugins in my Eclipse 4.4.2. This wants to update a lot of JBoss Tools components, but ultimately fails with > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-19711: -------------------------------- Attachment: JBIDE-19711.png In the above screenshot, if you click the "Run" button, it will start your server, and then open the proper html page (ind2.html). It functions exactly as a run-on-server action to the best of its ability. At this time, there's no ability to filter the target list if, for example, an ESB project is selected in the middle combo, such that a Tomcat server would not appear in the right. I believe this would require additional API extensions upstream as well. > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > Attachments: JBIDE-19711.png > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19711: ------------------------------------- It's mostly sensible to use, but it has problems, mostly with the upstream code. Features it has now: 1) Lists all servers in the right combo (target) 2) Will list any project that is a module in the center combo box as an object that can be launched 3) Will list any previously-executed artifact launch (ie index,html or MyServlet) as an object that can be launched 4) Will list (and set as active object) any artifact that can be discovered based on the current selection in the workspace. ie, if you select a server, and I can adapt that to an IModuleArtifact, I will set it as the active element. Things I don't like: 1) org.eclipse.remote has no UI extension points for providing images for your connection 2) Current master in launchbar therefore just has a green circle or red circle as icons for the remote connection. To fix 1) and 2) would require API additions to remote.ui as well as code changes to launchbar. 3) Launch configurations such as "Wildfly 8.0" appear in the middle combo list, because it is a launch configuration. The launchbar then appears to say "Debug" - "Wildfly 8.0" on "Wildfly 8.0", which makes no sense. API is probably needed to register specific launch configuration types as excluded from the middle bar. 4) Launch configurations such as "_index.html" also appear in the list. These launch configurations are actually used under-the-hood by wtp servertools, and the problem here is they hard-code the server used from the last launch. This can be fixed via the same mechanism as 3), an API / extension point to exclude some launch configuration types from the launchbar. > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19711) WTP servertools integration with CDT launchbar

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19711?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19711: --------------------------------------------- Also is your branch sensible to use? What features does it have? Can you screencast/shot them ? > WTP servertools integration with CDT launchbar > ---------------------------------------------- > > Key: JBIDE-19711 > URL: https://issues.jboss.org/browse/JBIDE-19711 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server, upstream > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > CDT has a new framework called Launchbar https://wiki.eclipse.org/CDT/LaunchBar > Integrating this with servertools, proof of concept, to see how feasible it is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18876 at 5/6/15 3:55 PM: ------------------------------------------------------------ Current Beta1-SNAPSHOT (as of build #407) is also failing in Jenkins with this error: {code}Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (34 KB at 81.0 KB/sec) [INFO] [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) @ jbosstools-unified --- [INFO] [INFO] --- target-platform-validation-plugin:0.22.0:validate-target-platform (default) @ jbosstools-unified --- [INFO] Validating /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/3cc13d4f/jbosstools/unified/target/jbosstools-unified.target... [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... (0B of 610.35kB at 0B/s) [INFO] Failed, see Error log below [ERROR] Validation found errors in 1 .target files: Could not resolve content of jbosstools-unified.target [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9.413 s [INFO] Finished at: 2015-05-06T13:36:15-04:00 [INFO] Final Memory: 23M/301M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.eclipse.tycho.extras:target-platform-validation-plugin:0.22.0:validate-target-platform (default) on project jbosstools-unified: Validation found errors in 1 .target files: [ERROR] Could not resolve content of jbosstools-unified.target{code} {code}Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (32 KB at 80.0 KB/sec) [INFO] [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) @ jbdevstudio-unified --- [INFO] [INFO] --- target-platform-validation-plugin:0.22.0:validate-target-platform (default) @ jbdevstudio-unified --- [INFO] Validating /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/a022b385/jbdevstudio/unified/target/jbdevstudio-unified.target... [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... [INFO] Failed, see Error log below [ERROR] Validation found errors in 1 .target files: Could not resolve content of jbdevstudio-unified.target [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.290 s [INFO] Finished at: 2015-05-06T13:31:21-04:00 [INFO] Final Memory: 23M/475M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.eclipse.tycho.extras:target-platform-validation-plugin:0.22.0:validate-target-platform (default) on project jbdevstudio-unified: Validation found errors in 1 .target files: [ERROR] Could not resolve content of jbdevstudio-unified.target{code} Everything was fine on Apr 22. Only one commit since then: https://github.com/jbosstools/jbosstools-target-platforms/commits/4.50.x And these build config changes: * use rsync.sh instead of publish.sh to push bits to download.jboss.org, www.qa, and devstudio.redhat.com * switch to use short workspaces (in support of generation of composite*.xml files that point into REPO/ folders (used to be done by publish.sh) was (Author: nickboldt): Current Beta1-SNAPSHOT is also failing in Jenkins with this error: {code}Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (34 KB at 81.0 KB/sec) [INFO] [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) @ jbosstools-unified --- [INFO] [INFO] --- target-platform-validation-plugin:0.22.0:validate-target-platform (default) @ jbosstools-unified --- [INFO] Validating /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/3cc13d4f/jbosstools/unified/target/jbosstools-unified.target... [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... (0B of 610.35kB at 0B/s) [INFO] Failed, see Error log below [ERROR] Validation found errors in 1 .target files: Could not resolve content of jbosstools-unified.target [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9.413 s [INFO] Finished at: 2015-05-06T13:36:15-04:00 [INFO] Final Memory: 23M/301M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.eclipse.tycho.extras:target-platform-validation-plugin:0.22.0:validate-target-platform (default) on project jbosstools-unified: Validation found errors in 1 .target files: [ERROR] Could not resolve content of jbosstools-unified.target{code} {code}Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (32 KB at 80.0 KB/sec) [INFO] [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) @ jbdevstudio-unified --- [INFO] [INFO] --- target-platform-validation-plugin:0.22.0:validate-target-platform (default) @ jbdevstudio-unified --- [INFO] Validating /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/a022b385/jbdevstudio/unified/target/jbdevstudio-unified.target... [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... [INFO] Failed, see Error log below [ERROR] Validation found errors in 1 .target files: Could not resolve content of jbdevstudio-unified.target [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.290 s [INFO] Finished at: 2015-05-06T13:31:21-04:00 [INFO] Final Memory: 23M/475M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.eclipse.tycho.extras:target-platform-validation-plugin:0.22.0:validate-target-platform (default) on project jbdevstudio-unified: Validation found errors in 1 .target files: [ERROR] Could not resolve content of jbdevstudio-unified.target{code} > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.3.x > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18876: ------------------------------------ Current Beta1-SNAPSHOT is also failing in Jenkins with this error: {code}Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (34 KB at 81.0 KB/sec) [INFO] [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) @ jbosstools-unified --- [INFO] [INFO] --- target-platform-validation-plugin:0.22.0:validate-target-platform (default) @ jbosstools-unified --- [INFO] Validating /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/3cc13d4f/jbosstools/unified/target/jbosstools-unified.target... [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... [INFO] Fetching content.jar from http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... (0B of 610.35kB at 0B/s) [INFO] Failed, see Error log below [ERROR] Validation found errors in 1 .target files: Could not resolve content of jbosstools-unified.target [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 9.413 s [INFO] Finished at: 2015-05-06T13:36:15-04:00 [INFO] Final Memory: 23M/301M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.eclipse.tycho.extras:target-platform-validation-plugin:0.22.0:validate-target-platform (default) on project jbosstools-unified: Validation found errors in 1 .target files: [ERROR] Could not resolve content of jbosstools-unified.target{code} {code}Downloaded: https://repository.jboss.org/nexus/content/groups/developer/org/jboss/too... (32 KB at 80.0 KB/sec) [INFO] [INFO] --- build-helper-maven-plugin:1.3:attach-artifact (attach-artifacts) @ jbdevstudio-unified --- [INFO] [INFO] --- target-platform-validation-plugin:0.22.0:validate-target-platform (default) @ jbdevstudio-unified --- [INFO] Validating /mnt/hudson_workspace/workspace/jbosstoolstargetplatforms-matrix/a022b385/jbdevstudio/unified/target/jbdevstudio-unified.target... [INFO] Adding repository http://download.jboss.org/jbosstools/targetplatforms/jbdevstudiotarget/4.... [INFO] Failed, see Error log below [ERROR] Validation found errors in 1 .target files: Could not resolve content of jbdevstudio-unified.target [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 6.290 s [INFO] Finished at: 2015-05-06T13:31:21-04:00 [INFO] Final Memory: 23M/475M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.eclipse.tycho.extras:target-platform-validation-plugin:0.22.0:validate-target-platform (default) on project jbdevstudio-unified: Validation found errors in 1 .target files: [ERROR] Could not resolve content of jbdevstudio-unified.target{code} > Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18876 > URL: https://issues.jboss.org/browse/JBIDE-18876 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.3.x > > > Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task. > So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. > Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19772) Update fails with No repository found containing: osgi.bundle, org.apache.commons.io, 2.4.0

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19772?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19772: --------------------------------------- Do you have [JBoss Tools Target Platform - Luna http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/luna/] enabled in Preferences [Install Update-> Available Software Sites]? > Update fails with No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19772 > URL: https://issues.jboss.org/browse/JBIDE-19772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.2.3.Final > Reporter: Martin Schröder > Assignee: Denis Golovin > Attachments: jbosstools-diagnostics-20150506142332.zip > > > I'm trying to update my installed plugins in my Eclipse 4.4.2. This wants to update a lot of JBoss Tools components, but ultimately fails with > No repository found containing: osgi.bundle,org.apache.commons.io,2.4.0 -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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