January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-16376) Disabled "fetch-zips" on aggregate

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16376?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16376: ------------------------------------ A consequence of disabling the collection of zips is that we are also no longer collecting all the github revisions used in the build. Compare: http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... (no ALL_REVISIONS.txt file) vs. http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... We will therefore need to script a new approach to collecting this metadata in https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub... > Disabled "fetch-zips" on aggregate > ---------------------------------- > > Key: JBIDE-16376 > URL: https://issues.jboss.org/browse/JBIDE-16376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha2 > > > As a consequence of changes for JBIDE-16309, the Maven mojo which fetches zip from aggregate files doesn't work any more. > So I disabled it (added fetch-zips-for-aggregate.skip=true ). We should decide whether to keep this or not. It seems to me that so far, the individual zips have not been used often, so we may be able to get rid of it. -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2669 at 1/24/14 10:24 AM: ------------------------------------------------------------ [~maxandersen] I've updated the PR and branch w/ an extra commit: https://github.com/nickboldt/jbdevstudio-product/commit/00d21efcfa5ee377d... This is a consequence of JBIDE-16309 which changed the default resolution of $\{jbosstools-nightly} via this commit: https://github.com/jbosstools/jbosstools-build/commit/df0e20e754566ad1703... was (Author: nickboldt): [~maxandersen] I've updated the PR and branch w/ an extra commit: https://github.com/nickboldt/jbdevstudio-product/commit/00d21efcfa5ee377d... This is a consequence of JBIDE-16309 which changed the default resolution of \${jbosstools-nightly} via this commit: https://github.com/jbosstools/jbosstools-build/commit/df0e20e754566ad1703... > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2669: ---------------------------------- PR and TB updated w/ an extra commit: https://github.com/nickboldt/jbdevstudio-product/commit/00d21efcfa5ee377d... This is a consequence of JBIDE-16309 in commit https://github.com/jbosstools/jbosstools-build/commit/df0e20e754566ad1703... which changed the default resolution of \${jbosstools-nightly} > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-2669 at 1/24/14 10:24 AM: ------------------------------------------------------------ [~maxandersen] I've updated the PR and branch w/ an extra commit: https://github.com/nickboldt/jbdevstudio-product/commit/00d21efcfa5ee377d... This is a consequence of JBIDE-16309 which changed the default resolution of \${jbosstools-nightly} via this commit: https://github.com/jbosstools/jbosstools-build/commit/df0e20e754566ad1703... was (Author: nickboldt): PR and TB updated w/ an extra commit: https://github.com/nickboldt/jbdevstudio-product/commit/00d21efcfa5ee377d... This is a consequence of JBIDE-16309 in commit https://github.com/jbosstools/jbosstools-build/commit/df0e20e754566ad1703... which changed the default resolution of \${jbosstools-nightly} > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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, 5 months

1
0
0 / 0

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

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15332?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-15332: ------------------------------------- It also affects maven-dependency-plugin copy goal used for copying jars to be added to plugin classpath. It forces to add <skip>false</skip> to pom.xml containing dependency plugin configuration. This issue was very hard to find (thanks to [~mickael_istria]) > 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 > 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2669) rename/refactor JBDS product .feature / plugin / .product to have less confusing names

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2669?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-2669: ------------------------------------------- I'm trying to review this PR but it seems to not build. I think it is missing declaration of where to get it plugins from since i'm getting: [INFO] Cannot complete the request. Generating details. [INFO] Cannot complete the request. Generating details. [INFO] {osgi.ws=cocoa, osgi.os=macosx, osgi.arch=x86, org.eclipse.update.install.features=true} [ERROR] Cannot resolve project dependencies: [ERROR] Software being installed: com.jboss.devstudio.core.usage.branding 8.0.0.qualifier [ERROR] Missing requirement: com.jboss.devstudio.core.usage.branding 8.0.0.qualifier requires 'bundle org.jboss.tools.usage [1.0.0,2.0.0)' but it could not be found [ERROR] [ERROR] Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from com.jboss.devstudio.core.usage.branding 8.0.0.qualifier to bundle org.jboss.tools.usage [1.0.0,2.0.0).; No solution found because the problem is unsatisfiable.] -> [Help 1] org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from com.jboss.devstudio.core.usage.branding 8.0.0.qualifier to bundle org.jboss.tools.usage [1.0.0,2.0.0).; No solution found because the problem is unsatisfiable.] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:168) at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) Caused by: java.lang.RuntimeException: No solution found because the problem is unsatisfiable.: [Unable to satisfy dependency from com.jboss.devstudio.core.usage.branding 8.0.0.qualifier to bundle org.jboss.tools.usage [1.0.0,2.0.0).; No solution found because the problem is unsatisfiable.] at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.newResolutionException(AbstractResolutionStrategy.java:98) at org.eclipse.tycho.p2.resolver.ProjectorResolutionStrategy.resolve(ProjectorResolutionStrategy.java:88) at org.eclipse.tycho.p2.resolver.AbstractResolutionStrategy.resolve(AbstractResolutionStrategy.java:63) at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:134) at org.eclipse.tycho.p2.impl.resolver.P2ResolverImpl.resolveDependencies(P2ResolverImpl.java:87) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.doResolvePlatform(P2TargetPlatformResolver.java:369) at org.eclipse.tycho.p2.resolver.P2TargetPlatformResolver.resolveDependencies(P2TargetPlatformResolver.java:345) at org.eclipse.tycho.core.resolver.DefaultTychoDependencyResolver.resolveProject(DefaultTychoDependencyResolver.java:109) at org.eclipse.tycho.core.maven.TychoMavenLifecycleParticipant.afterProjectsRead(TychoMavenLifecycleParticipant.java:75) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:274) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) ... 11 more > rename/refactor JBDS product .feature / plugin / .product to have less confusing names > -------------------------------------------------------------------------------------- > > Key: JBDS-2669 > URL: https://issues.jboss.org/browse/JBDS-2669 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, installer, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 8.0.0.Alpha2 > > Attachments: update-product-manually-with-refactoring-full-featureset-review.png, update-product-manually-with-refactoring-full-featureset.png, update-product-manually-with-refactoring.png > > > We should consider some better names for these artifacts so they collide less and are more obvious which is which. > 1. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/features/c... > ** featureName=JBoss Developer Studio (Core Features) / BYOE category in update site > 2. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... and https://github.com/jbdevstudio/jbdevstudio-product/blob/master/plugins/co... > ** Bundle-SymbolicName: com.jboss.jbds.product;singleton:=true > 3. https://github.com/jbdevstudio/jbdevstudio-product/blob/master/site/com.j... > ** name="JBoss Developer Studio (Branded Product)" uid="com.jboss.jbds.all" id="com.jboss.jbds.product.product" -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16357) ApplicationWizard: RemoteSystemsTempFiles is possible to choose in OpenShift select project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16357?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16357: ------------------------------------- Attachment: filter-acceptable-projects.png > ApplicationWizard: RemoteSystemsTempFiles is possible to choose in OpenShift select project > ------------------------------------------------------------------------------------------- > > Key: JBIDE-16357 > URL: https://issues.jboss.org/browse/JBIDE-16357 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Burr Sutter > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha2 > > Attachments: filter-acceptable-projects.png > > > The Select Existing Project dialog should not display > RemoteSystemTempFiles as an option > http://screencast.com/t/CKEnB16Rbad -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16357) ApplicationWizard: RemoteSystemsTempFiles is possible to choose in OpenShift select project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16357?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-16357: ------------------------------------------ added a checkbox to toggle the filter: !filter-acceptable-projects.png! The filtering is *on* by default and stored to the preferences. > ApplicationWizard: RemoteSystemsTempFiles is possible to choose in OpenShift select project > ------------------------------------------------------------------------------------------- > > Key: JBIDE-16357 > URL: https://issues.jboss.org/browse/JBIDE-16357 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Burr Sutter > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha2 > > Attachments: filter-acceptable-projects.png > > > The Select Existing Project dialog should not display > RemoteSystemTempFiles as an option > http://screencast.com/t/CKEnB16Rbad -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16398) Aerogear Push Plugin

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-16398: ----------------------------------- Summary: Aerogear Push Plugin Key: JBIDE-16398 URL: https://issues.jboss.org/browse/JBIDE-16398 Project: Tools (JBoss Tools) Issue Type: Bug Components: browsersim Reporter: Burr Sutter Adding the Aerogear Push Cordova Plugin causes an error in CordovaSim/Ripple. Yes, APNS/GCM can not be simulated, however, we should attempt to augment the message to say "Push can not be simulated, use real hardware". http://screencast.com/t/Ud7ZlQQvJ -- 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, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2857) Add OS X Mavericks to the support matrix

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2857?page=com.atlassian.jira.plugin.... ] Burr Sutter updated JBDS-2857: ------------------------------ CDW pm_ack: + (was: ?) Status: New (was: New) > Add OS X Mavericks to the support matrix > ---------------------------------------- > > Key: JBDS-2857 > URL: https://issues.jboss.org/browse/JBDS-2857 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 7.1.0.CR1 > Reporter: Martin Malina > Assignee: Len DiMaggio > Fix For: 7.1.1.GA, 8.0.0.Alpha2 > > > I know this comes very late, so you may want to just push this to 8.0.0 immediately. > However, we've already been testing on Mavericks (I use it every day myself) since it was introduced on October 22, 2013 and have never seen any problem specific to it. > I only realized we still don't have Mavericks in the matrix today when I checked Michelle's Supported Configurations document. -- 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, 5 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 2014