August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17808: ------------------------------------ In case EA is different for JBT and JBDS, the properties file [1] should instead be in two places: com.jboss.devstudio.core.central/earlyaccess.properties and org.jboss.tools.community.central/earlyaccess.properties [1] https://github.com/mickaelistria/jbosstools-central/blob/JBIDE-17808/cent... > Identify which installed IUs are from Early Access vs. supported/tested versions > -------------------------------------------------------------------------------- > > Key: JBIDE-17808 > URL: https://issues.jboss.org/browse/JBIDE-17808 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Nick Boldt > Assignee: Mickael Istria > Labels: documentation > Fix For: 4.2.0.CR1 > > Attachments: JBIDE17808.jpeg > > > [~maxandersen] brought up a good point on a call today: > we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location. > Thus we need some sort of UI to list installed IUs that are "Early Access". > This could be... (brainstorming now): > * a text file with the list of things installed from Early Access (features and plugins) > * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins > * a way to filter the plugin view (Help > About) to show only EA content (or exclude it) > * ... ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18105) generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18105?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18105: ------------------------------- Description: Since the JBT EA .target file already contains all the IUs which are considered early access (and their dependencies, which are sometimes also EA, like Tern) we can generate the list of EA features from that .target file, and maintain an ongoing [min,max] version range of what's considered early access. Currently the properties file looks like this: https://github.com/mickaelistria/jbosstools-central/blob/JBIDE-17808/cent... was:Since the JBT EA .target file already contains all the IUs which are considered early access (and their dependencies, which are sometimes also EA, like Tern) we can generate the list of EA features from that .target file, and maintain an ongoing [min,max] version range of what's considered early access. > generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target > ---------------------------------------------------------------------- > > Key: JBIDE-18105 > URL: https://issues.jboss.org/browse/JBIDE-18105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, discovery > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > Since the JBT EA .target file already contains all the IUs which are considered early access (and their dependencies, which are sometimes also EA, like Tern) we can generate the list of EA features from that .target file, and maintain an ongoing [min,max] version range of what's considered early access. > Currently the properties file looks like this: > https://github.com/mickaelistria/jbosstools-central/blob/JBIDE-17808/cent... -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3086) Change Central Discovery URLs?

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3086: -------------------------------------- Shouldn't Central be separated too? Can Central be updated with different heartbeats than JBDS? > Change Central Discovery URLs? > ------------------------------ > > Key: JBDS-3086 > URL: https://issues.jboss.org/browse/JBDS-3086 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, discovery, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.CR1 > > Attachments: jbds3086_no-change-to-categorized-view.png, jbds3086_uncategorized-view-sample1.png, jbds3086_uncategorized-view-sample2.png > > > Today, the Central discovery plugin for JBDS is points to this URL: > <site>/central/core/ > and for Early Access discovery: > <site>/central/earlyaccess/ > However, Max has suggested that we simplify the first, and change the second. > I believe he wants something like this: > https://devstudio.jboss.com/updates/8.0-staging/ > https://devstudio.jboss.com/updates/8.0-development > https://devstudio.jboss.com/updates/8.0/ > and > https://devstudio.jboss.com/earlyaccess/8.0-staging/ > https://devstudio.jboss.com/earlyaccess/8.0-development/ > https://devstudio.jboss.com/earlyaccess/8.0/ > What do people think about this proposed change? > [~mickael_istria] [~maxandersen] [~dgolovin] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-298) JBDS-IS zip file has 1.3GB

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-298?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-298: ---------------------------------- Went with a simpler approach. https://github.com/jbosstools/jbosstools-integration-stack/pull/215 https://github.com/jbosstools/jbosstools-integration-stack/pull/216 > JBDS-IS zip file has 1.3GB > -------------------------- > > Key: JBTIS-298 > URL: https://issues.jboss.org/browse/JBTIS-298 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: distribution > Affects Versions: 8.0.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > The zip file is available at > http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integratio... > The previos version of JBDS-IS (7.0.2.GA) has 247M -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3086) Change Central Discovery URLs?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3086: ------------------------------------------- earlyaccess cannot be merged into the root/final updatesite. that should continue to be separate. > Change Central Discovery URLs? > ------------------------------ > > Key: JBDS-3086 > URL: https://issues.jboss.org/browse/JBDS-3086 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, discovery, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.CR1 > > Attachments: jbds3086_no-change-to-categorized-view.png, jbds3086_uncategorized-view-sample1.png, jbds3086_uncategorized-view-sample2.png > > > Today, the Central discovery plugin for JBDS is points to this URL: > <site>/central/core/ > and for Early Access discovery: > <site>/central/earlyaccess/ > However, Max has suggested that we simplify the first, and change the second. > I believe he wants something like this: > https://devstudio.jboss.com/updates/8.0-staging/ > https://devstudio.jboss.com/updates/8.0-development > https://devstudio.jboss.com/updates/8.0/ > and > https://devstudio.jboss.com/earlyaccess/8.0-staging/ > https://devstudio.jboss.com/earlyaccess/8.0-development/ > https://devstudio.jboss.com/earlyaccess/8.0/ > What do people think about this proposed change? > [~mickael_istria] [~maxandersen] [~dgolovin] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3125) JBDS shouldn't link to download.jboss.org

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3125?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3125: -------------------------------------- CC [~nickboldt] & [~maxandersen] Isn't it only a matter of replacing a composite repo pointing to download.jboss.org by a copy of the jbdevstudiotarget repo? > JBDS shouldn't link to download.jboss.org > ----------------------------------------- > > Key: JBDS-3125 > URL: https://issues.jboss.org/browse/JBDS-3125 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Mickael Istria > Priority: Critical > Fix For: 8.0.0.GA > > > JBoss Developer Studio links to download.jboss.org to link to the target-platform. > Instead, the JBDS target-platform should be published on devstudio.jboss.com and JBDS should link to this repository. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3125) JBDS shouldn't link to download.jboss.org

by Mickael Istria (JIRA)

Mickael Istria created JBDS-3125: ------------------------------------ Summary: JBDS shouldn't link to download.jboss.org Key: JBDS-3125 URL: https://issues.jboss.org/browse/JBDS-3125 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: updatesite Reporter: Mickael Istria Priority: Critical JBoss Developer Studio links to download.jboss.org to link to the target-platform. Instead, the JBDS target-platform should be published on devstudio.jboss.com and JBDS should link to this repository. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3125) JBDS shouldn't link to download.jboss.org

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3125?page=com.atlassian.jira.plugin.... ] Mickael Istria updated JBDS-3125: --------------------------------- Fix Version/s: 8.0.0.GA > JBDS shouldn't link to download.jboss.org > ----------------------------------------- > > Key: JBDS-3125 > URL: https://issues.jboss.org/browse/JBDS-3125 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: updatesite > Reporter: Mickael Istria > Priority: Critical > Fix For: 8.0.0.GA > > > JBoss Developer Studio links to download.jboss.org to link to the target-platform. > Instead, the JBDS target-platform should be published on devstudio.jboss.com and JBDS should link to this repository. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18136) iBeacon plugin problem, can´t compile app

by eduardo de souza (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18136?page=com.atlassian.jira.plugi... ] eduardo de souza updated JBIDE-18136: ------------------------------------- Description: I have created a Hybrid Mobile App, then added an iBeacon plugin: https://github.com/petermetz/cordova-plugin-ibeacon.git Then I tried to compile to see if there was any problem. I got this message: An internal error occurred during: "Launching TesteApp4 (Android Device)". java.lang.NullPointerException was: I have created a Hybrid Mobile App, then added an iBeacon plugin: and tried to compile to see if there was any problem. I got this message: https://github.com/petermetz/cordova-plugin-ibeacon.git An internal error occurred during: "Launching TesteApp4 (Android Device)". java.lang.NullPointerException > iBeacon plugin problem, can´t compile app > ----------------------------------------- > > Key: JBIDE-18136 > URL: https://issues.jboss.org/browse/JBIDE-18136 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: eduardo de souza > Priority: Critical > > I have created a Hybrid Mobile App, then added an iBeacon plugin: > https://github.com/petermetz/cordova-plugin-ibeacon.git > Then I tried to compile to see if there was any problem. I got this message: > An internal error occurred during: "Launching TesteApp4 (Android Device)". > java.lang.NullPointerException -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18053) Add Powermock to the target platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18053?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18053: ----------------------------------- Comment: was deleted (was: We've been in touch with the author of Powermock-osgi and it's not clear whether a different JUnit and Hamcrest are required. There is no way we put in our TP a different version of JUnit and Hamcrest. So we're postponing this change.) > Add Powermock to the target platform > ------------------------------------ > > Key: JBIDE-18053 > URL: https://issues.jboss.org/browse/JBIDE-18053 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.x > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha1 > > > *Reason:* To improving testing by allowing the stubbing of scenerios like "new File(path).exists()" which require bytecode modifications in order to accomplish. Example of intended use: https://gist.github.com/jcantrill/fd83c27d3fc542742ec7 > *License and owner:* Apache 2.0 / https://github.com/jayway > *Original p2 repo:* http://powermock-osgi.googlecode.com/svn/updateSite/1.5.4.1/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/powermock/1.5.4.1/ > *Sources:* https://code.google.com/p/powermock-osgi/ , http://powermock-osgi.googlecode.com/svn/trunk/ > *Affected projects:* OpenShift tests > *Include in JBDS:* No > *Type of dependency:* testing > *List of bundles added/removed:* > {code} > + <unit id="org.powermock.mockito-junit.feature.feature.group" version="1.5.4.1"/> > + <unit id="org.objenesis" version="2.1.0"/> > + <unit id="javassist" version="3.18.1.GA"/> > {code} > *p2diff report:* > {code} > mistria@mistria--rh:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:$(pwd)/target/jbosstools-multiple.target.repo/ > > org.mockito.mockito-core [1.9.5] > > javassist [3.18.1.GA] > > org.powermock.powermock-api-support [1.5.4] > > org.powermock.powermock-reflect [1.5.4] > > org.powermock.powermock-api-mockito [1.5.4] > > org.powermock.powermock-module-junit4-common [1.5.4] > > org.powermock.powermock-module-junit4 [1.5.4] > > org.powermock.powermock-core [1.5.4] > > org.objenesis [2.1.0] > === Summary === > file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 9 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 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 2014