January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-13266: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/43 (was: https://github.com/jbosstools/jbosstools-build/pull/29) New pull request https://github.com/jbosstools/jbosstools-build/pull/43 > Use pack200 to speed up download and install > -------------------------------------------- > > Key: JBIDE-13266 > URL: https://issues.jboss.org/browse/JBIDE-13266 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Affects Versions: 4.0.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > > p2 provides the pack200 stuff, which offers a better compressions for jars, and then that makes downloads faster when installing. > We should set up our repo to create the pack200'd artifacts. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13266: ---------------------------------------- Just ran some metrics on "jbosstools-central-maven-examples", both after a "mvn clean" $ mvn -o verify -Dmaven.test.skip=true => 2m59s $ mvn -o verify -Dmaven.test.skip=true -Ppack200 => 3m08s So it seems to be a matter of second to enable pack200. If all integration works well (from component to installer), I'll recommend to make it default, out of a profile. > Use pack200 to speed up download and install > -------------------------------------------- > > Key: JBIDE-13266 > URL: https://issues.jboss.org/browse/JBIDE-13266 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Affects Versions: 4.0.0.CR1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > > p2 provides the pack200 stuff, which offers a better compressions for jars, and then that makes downloads faster when installing. > We should set up our repo to create the pack200'd artifacts. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13175) Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13175?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13175: ------------------------------------------ I now implemented the additional check. It'll tell the user that there are local commits that were not pushed to OpenShift yet: !committed-not-published.png! > Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13175 > URL: https://issues.jboss.org/browse/JBIDE-13175 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha1 > > Attachments: 1-local-change.png, committed-not-published.png, no-local-changes.png, no_changes_yes.png > > > # EXEC: launch *OpenShift Application* wizard and create a new application / import existing one > # ASSERT: you get the OpenShift application imported to your workspace > # EXEC: in *Servers* view, select the adapter for your OpenShift application and pick *Publish* from its context menu > Result: > The adapter tells you that there are no local changes. If you look at your local project you'll see in the git-decoration that the local git repo is ahead of 1 commit of the remote, so there is a local commit that could be pushed/published. > !no-local-changes.png! > Expected result: > The adapter should tell you that there are local changes and ask you if you want to publish them. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13175) Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13175?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13175: ------------------------------------- Attachment: committed-not-published.png > Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13175 > URL: https://issues.jboss.org/browse/JBIDE-13175 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha1 > > Attachments: 1-local-change.png, committed-not-published.png, no-local-changes.png, no_changes_yes.png > > > # EXEC: launch *OpenShift Application* wizard and create a new application / import existing one > # ASSERT: you get the OpenShift application imported to your workspace > # EXEC: in *Servers* view, select the adapter for your OpenShift application and pick *Publish* from its context menu > Result: > The adapter tells you that there are no local changes. If you look at your local project you'll see in the git-decoration that the local git repo is ahead of 1 commit of the remote, so there is a local commit that could be pushed/published. > !no-local-changes.png! > Expected result: > The adapter should tell you that there are local changes and ask you if you want to publish them. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13329. ------------------------------ Resolution: Done Unified targets no longer include sources or sdk features, only the sdkbundle for GWT. http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... Closing. > should unified.target includes sources? > --------------------------------------- > > Key: JBIDE-13329 > URL: https://issues.jboss.org/browse/JBIDE-13329 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not. > However: > {code} > unified-4.2.1.a-20121220.173723-14-unified.target: > <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit"> > multiple-4.2.1.a-20121220.173233-14-multiple.target: > <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true"> > {code} > And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles: > http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/ > Is this intentional? Or is there a bug in your flatten mojo? > https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13349) JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13349?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13349: ------------------------------------ [~ray.ploski] there are still many links to http://www.redhat.com/promo/eap6beta/ but they redirect to the actual EAP 6 release page, so that's not really a blocker. Still, it's a little weird to cursor over links for EAP 6 and see "beta" when it's a full release -- in fact it's on 6.0.1 already. :) Otherwise the About and Features pages look good. Thanks! > JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6? > ----------------------------------------------------------------------------------- > > Key: JBIDE-13349 > URL: https://issues.jboss.org/browse/JBIDE-13349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Len DiMaggio > Assignee: Ray Ploski > Attachments: Screenshot-2.png > > > See attached screenshot -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2348) JBDS product page on redhat.com is out of date

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2348?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2348: ---------------------------------- https://www.redhat.com/apps/store/developers/jboss_developer_studio.html is now up to date (versions removed) but datasheet still mentions Eclipse 3.7 (JBDS 5) instead of Eclipse 4.2 (the latest release, JBDS 6). > JBDS product page on redhat.com is out of date > ---------------------------------------------- > > Key: JBDS-2348 > URL: https://issues.jboss.org/browse/JBDS-2348 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, documentation > Affects Versions: 5.0.1.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > > This page [1] mentions Eclipse 3.6 and JBoss Tools 3, but JBDS 6 uses Eclipse 4.2 and JBoss Tools 4. > [1] https://www.redhat.com/apps/store/developers/jboss_developer_studio.html > Can we get that page updated? -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12249) A lot of failures to install from marketplace.eclipse.org

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12249?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-12249. ------------------------------ JBoss Tools Indigo entry on Marketplace - http://marketplace.eclipse.org/content/jboss-tools-indigo#.UQns9rkzfVM - has had install errors (# in last 7 days) as follows: 1/16/2013 799 1/24/2013 835 (launch date for JBT 3.3.2) 1/30/2013 505 Remaining errors appear to all be solved by uninstalling m2e-wtp 0.15.2 or 0.15.3 in favour of 0.16. Not much we can do about this since there was a namespace change in between releases. > A lot of failures to install from marketplace.eclipse.org > --------------------------------------------------------- > > Key: JBIDE-12249 > URL: https://issues.jboss.org/browse/JBIDE-12249 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, QA > Affects Versions: 3.3.0.Final > Reporter: Mickael Istria > Assignee: Nick Boldt > Priority: Blocker > Fix For: 3.3.2 > > Attachments: JBIDE12249-Indigo-installs-dropping.png, JBIDE12249-jbds6-byoe-installs-rising.png, JBIDE12249-jbt4-installs-rising.png, JBIDE12249-m2e1.2-install-conflict.png, JBIDE12249-upversion-to-1.3.2.patch.txt, JBIDE12249.patch.txt > > > It appears that most installations of JBT from marketplace concludes in an error: > See: http://marketplace.eclipse.org/content/jboss-tools-indigo/error_reports > Some of the most frequent errors: > {quote} > Cannot satisfy dependency: From: JBoss JAX-RS Tooling (UI) 1.2.2.v20120605-1934-H134-CR1 (org.jboss.tools.ws.jaxrs.ui 1.2.2.v20120605-1934-H134-CR1) To: bundle org.eclipse.debug.ui 3.7.101 > {quote} > -> JaxRs depends on 3.7.1 ? Install from 3.7.0 or <. > {quote} > JBoss Maven Integration 1.3.0.v20120613-2141-H115-Final (org.jboss.tools.maven.ui 1.3.0.v20120613-2141-H115-Final) To: bundle org.eclipse.compare 3.5.202 > {quote} > -> Maven depends on 3.7.2 ? > {quote} > Cannot satisfy dependency: From: OpenShift UI 2.3.0.v20120613-1951-H135-Final (org.jboss.tools.openshift.express.ui 2.3.0.v20120613-1951-H135-Final) To: bundle org.eclipse.egit.ui [1.0.0,2.0.0) > {quote} > -> People who don't have EGit. EGit is not part of our site. -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13431) BrowserSim: remake galaxy S III skin

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13431?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-13431: ---------------------------------- Attachment: Buttons.png Clear skin.png > BrowserSim: remake galaxy S III skin > ------------------------------------ > > Key: JBIDE-13431 > URL: https://issues.jboss.org/browse/JBIDE-13431 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Visual Page Editor core > Reporter: Ilya Buziuk > Assignee: Daniel Azarov > Attachments: attributes.png, Buttons.png, buttons.png, Clear skin.png, forward-disabled.png, forward-selected.png, forward.png, refresh.png, refresh_replacement.png, screen_size.png, uneven_edge.png, uneven_edge_max.png > > > Need to remake galaxy S III skin, which is generated by Android Asset Studio: [http://android-ui-utils.googlecode.com/hg/asset-studio/dist/device-frames...] > * while compressing the mockup the edge of the device is becoming uneven: !uneven_edge.png|thumbnail! , !uneven_edge_max.png|thumbnail! - the edges should be even; > * the mockup should be vertically compressed until the screen size of the device will be no more than 800px - !screen_size.png|thumbnail!; > * mikrofon, 3 cameras, "sumsung" symbolism, *side buttons*: every item should be settled on the new layer: !attributes.png|thumbnail!; > * "menu" button should be replaced with the "refresh" !refresh.png|thumbnail! button: !refresh_replacement.png|thumbnail!; > * 3 buttons at the bottom of the device !refresh_replacement.png|thumbnail! should have 3 states: enable !forward.png|thumbnail!, disable !forward-disabled.png|thumbnail!, selected !forward-selected.png|thumbnail! - each item on the new layer; > Link to the source images: [http://code.google.com/p/android-ui-utils/source/browse/#hg%2Fasset-studi...] -- 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

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13456) Move palette implementation from vpe module to jst module

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-13456: --------------------------------------------- Summary: Move palette implementation from vpe module to jst module Key: JBIDE-13456 URL: https://issues.jboss.org/browse/JBIDE-13456 Project: Tools (JBoss Tools) Issue Type: Task Components: jsp/jsf/xml/html source editing Affects Versions: 4.0.0.Final Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 4.1.0.Alpha1 -- 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

11 years, 4 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2013