[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 commented on JBIDE-13431:
---------------------------------------
I hope so. Let me try.
> 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, 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
13 years, 1 month
[JBoss JIRA] (JBIDE-13452) investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION from parent pom
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-13452:
----------------------------------
Summary: investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION from parent pom
Key: JBIDE-13452
URL: https://issues.jboss.org/browse/JBIDE-13452
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, target-platform, updatesite
Affects Versions: 4.1.0.Alpha1
Reporter: Nick Boldt
Assignee: Nick Boldt
investigate removing JBT_VERSION, JBDS_VERSION, and TARGET_PLATFORM_VERSION (min and max) from parent pom
Can we switch to using dynamic maven variables like project.version instead?
Moving forward, jobs will override/set the version of target platform used to build (min) and test (max), and developers will be required to decide when/if to move to a newer parent pom or target platform version(s) if needed.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13443) Can't install on Kepler because of Birt
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13443?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-13443:
-----------------------------------
Assignee: Snjezana Peco (was: Mickael Istria)
A solution could simply be to:
* make birt component depend on birt 4.2.2
* Provide Birt 4.2.2 as part of the minimal Target Platform
[~snjeza]: Can you try to change dependency to Birt 4.2.2 and checkswhether this can install and run against Eclipse 4.2.1 and 4.3.0.M4 ?
What we don't know here is if we can use Birt 4.2.2 on Juno.
> Can't install on Kepler because of Birt
> ---------------------------------------
>
> Key: JBIDE-13443
> URL: https://issues.jboss.org/browse/JBIDE-13443
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: birt, target-platform
> Reporter: Mickael Istria
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha1
>
>
> The version of Birt we build against does not match with version for Kepler and conflicts on ICU4j
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> says:
> {quote}
> Could not install from: http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss BIRT Integration 1.4.0.Alpha1-v20130128-1419-B356 (org.jboss.tools.birt.feature.feature.group 1.4.0.Alpha1-v20130128-1419-B356)
> Software currently installed: Eclipse IDE for Java EE Developers 2.0.0.20121218-0936 (epp.package.jee 2.0.0.20121218-0936)
> Only one of the following can be installed at once:
> International Components for Unicode for Java (ICU4J) 4.4.2.v20110823 (com.ibm.icu 4.4.2.v20110823)
> International Components for Unicode for Java (ICU4J) 50.1.0.v20121116-2 (com.ibm.icu 50.1.0.v20121116-2)
> Cannot satisfy dependency:
> From: Eclipse IDE for Java EE Developers 2.0.0.20121218-0936 (epp.package.jee 2.0.0.20121218-0936)
> To: org.eclipse.epp.package.jee.feature.feature.group [2.0.0.20121218-0936]
> Cannot satisfy dependency:
> From: BIRT Chart Framework 4.2.1.v20120820-828i7EFQCnvK_6wFGvqLR (org.eclipse.birt.chart.feature.group 4.2.1.v20120820-828i7EFQCnvK_6wFGvqLR)
> To: org.eclipse.birt.core [4.2.1.v201209121203]
> Cannot satisfy dependency:
> From: BIRT Core Package 4.2.1.v201209121203 (org.eclipse.birt.core 4.2.1.v201209121203)
> To: package com.ibm.icu.lang [3.4.4,5.0.0)
> Cannot satisfy dependency:
> From: Eclipse e4 Rich Client Platform 1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4 (org.eclipse.e4.rcp.feature.group 1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4)
> To: com.ibm.icu [50.1.0.v20121116-2]
> Cannot satisfy dependency:
> From: Java EE IDE Feature 2.0.0.20121218-0936 (org.eclipse.epp.package.jee.feature.feature.group 2.0.0.20121218-0936)
> To: org.eclipse.platform.feature.group [4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP]
> Cannot satisfy dependency:
> From: Eclipse Platform 4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP (org.eclipse.platform.feature.group 4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP)
> To: org.eclipse.rcp.feature.group [4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP]
> Cannot satisfy dependency:
> From: Eclipse RCP 4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP (org.eclipse.rcp.feature.group 4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP)
> To: org.eclipse.e4.rcp.feature.group [1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4]
> Cannot satisfy dependency:
> From: JBoss BIRT Integration 1.4.0.Alpha1-v20130128-1419-B356 (org.jboss.tools.birt.feature.feature.group 1.4.0.Alpha1-v20130128-1419-B356)
> To: org.eclipse.birt.chart.feature.group 2.5.0
> {quote}
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13439) ESB Tests are failing locating project examples
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13439?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13439:
------------------------------------
This is a cart-before-horse problem.
You can't have examples for ESB until you have a connector in Central w/ ESB tooling feature in it.
Step 1:
Get ESB tooling for JBDS 6 built.
Step 2:
Update your tests.
Step 3:
When tests pass, update http://download.jboss.org/jbosstools/examples/project-examples-jbds60.xml (via PR to jbosstools-download.jboss.org repo in git) w/ new example definitions that reference the ESB connector in Central, install it, and proceed w/ the example stuff. See also http://download.jboss.org/jbosstools/examples/README.html
Step 4:
Profit!
> ESB Tests are failing locating project examples
> -----------------------------------------------
>
> Key: JBIDE-13439
> URL: https://issues.jboss.org/browse/JBIDE-13439
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Denis Golovin
>
> Problem:
> ESB tests stopped being able to find project examples when executing test. Why ?
> Nick's original theory, but that does not answer why the content that is still there is not showing up:
> Problem:
> a) you're missing stuff in http://download.jboss.org/jbosstools/examples/
> b) because people published their examples into their SVN workspaces instead of github, and expected it would magically appear in the /examples/ folder
> c) yet no one bothered to audit that their content was properly published, aaaand... it's gone.
> >> http://memegenerator.net/instance/33999035 <<
> Solution:
> a) submit PRs for their stuff to contribute it to the new github repo, https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j...
> b) kick this job to sync: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j...
> c) update this doc: https://community.jboss.org/wiki/ProjectExamplesSites
> d) update this README: http://download.jboss.org/jbosstools/examples/readme.process.txt with new instructions
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13449) JBT 4.1.0.Alpha1 nightly will not install on Juno
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13449?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-13449:
---------------------------------------
Thanks for the information, Nick! That explains it.
> JBT 4.1.0.Alpha1 nightly will not install on Juno
> -------------------------------------------------
>
> Key: JBIDE-13449
> URL: https://issues.jboss.org/browse/JBIDE-13449
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment: OS X 10.8 Mountain Lion
> Java 1.6 32bit
> eclipse-jee-indigo-SR2-macosx-cocoa.tar.gz
> JBT nightly 4.1.0.Alpha1-v20130129-1449-B6053
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha1
>
>
> Today I tried installing JBT nightly [1] on a clean installation of Juno SR2 and there are many conflicts in dependencies:
> {code}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Maven Portlet Configurator 1.5.0.Alpha1-v20130124-1009-B213 (org.jboss.tools.maven.portlet.feature.feature.group 1.5.0.Alpha1-v20130124-1009-B213)
> Software currently installed: Eclipse IDE for Java EE Developers 1.4.2.20120213-0813 (epp.package.jee 1.4.2.20120213-0813)
> Only one of the following can be installed at once:
> Debug Core 3.7.0.v20110518 (org.eclipse.debug.core 3.7.0.v20110518)
> Debug Core 3.7.100.v20120521-2012 (org.eclipse.debug.core 3.7.100.v20120521-2012)
> Debug Core 3.7.1.v20111129-2031 (org.eclipse.debug.core 3.7.1.v20111129-2031)
> Cannot satisfy dependency:
> From: Eclipse IDE for Java EE Developers 1.4.2.20120213-0813 (epp.package.jee 1.4.2.20120213-0813)
> To: org.eclipse.epp.package.jee.feature.feature.group [1.4.2.20120213-0813]
> Cannot satisfy dependency:
> From: Java EE IDE Feature 1.4.2.20120213-0813 (org.eclipse.epp.package.jee.feature.feature.group 1.4.2.20120213-0813)
> To: org.eclipse.platform.feature.group [3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q]
> Cannot satisfy dependency:
> From: Eclipse Platform 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q (org.eclipse.platform.feature.group 3.7.2.v20120207-1839-9gF7UHPDFxGjd-PqDr2jX_4yKaumkoHTz04_q-q)
> To: org.eclipse.debug.core [3.7.1.v20111129-2031]
> Cannot satisfy dependency:
> From: JBoss AS Core Plug-in 2.4.100.Alpha1-v20130129-1810-B163 (org.jboss.ide.eclipse.as.core 2.4.100.Alpha1-v20130129-1810-B163)
> To: bundle org.jboss.ide.eclipse.as.wtp.core 0.0.0
> Cannot satisfy dependency:
> From: WTP Overrides Core 2.4.100.Alpha1-v20130129-1810-B163 (org.jboss.ide.eclipse.as.wtp.core 2.4.100.Alpha1-v20130129-1810-B163)
> To: bundle org.eclipse.debug.core 3.7.100
> Cannot satisfy dependency:
> From: JBoss Maven Portlet Configurator 1.5.0.Alpha1-v20130124-1009-B213 (org.jboss.tools.maven.portlet 1.5.0.Alpha1-v20130124-1009-B213)
> To: bundle org.jboss.tools.portlet.core 0.0.0
> Cannot satisfy dependency:
> From: JBoss Maven Portlet Configurator 1.5.0.Alpha1-v20130124-1009-B213 (org.jboss.tools.maven.portlet.feature.feature.group 1.5.0.Alpha1-v20130124-1009-B213)
> To: org.jboss.tools.maven.portlet [1.5.0.Alpha1-v20130124-1009-B213]
> Cannot satisfy dependency:
> From: Portlet Core Plug-in 1.4.0.Alpha1-v20130128-2009-B183 (org.jboss.tools.portlet.core 1.4.0.Alpha1-v20130128-2009-B183)
> To: bundle org.jboss.ide.eclipse.as.core 0.0.0
> {code}
> It works on Kepler M4.
> AFAIK, 4.1.0 should work on both Juno and Kepler, correct?
> [1] http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
--
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
13 years, 1 month
[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:
----------------------------------------
{quote}
a) "Note that deprecated eclipse-update-site doesn't consider packed artifacts. "
So we'll have to migrate the remaining eclipse-update-site poms to eclipse-repository (and may lose some of the post-processing steps we do right now in https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...)
{quote}
eclipse-update-site hqs been deprecated for a long time now. We need to get away from it. That was part of the concerns for JBIDE-10596.
{quote}
b) "This does not apply on a full repository. eclipse-repository can only consume existing pack200'ed artifacts, not generate some. "
If I'm reading that correctly, I suspect that means that where today we can build an update site consisting of locally built AND upstream artifacts, in future this will have to be TWO builds: one to build stuff locally, then a second one to aggregate upstream and the local stuff into a single repo w/ pack.gz artifacts. I hope I'm wrong here, as that extra step would be a PITA.
{quote}
Nope, it means that the update-site does not create the pack200'd bundles. It consumes them from the artifacts build. Pack200 has to be enabled on eclipse-plugin and eclipse-test-plugin builds.
> 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
13 years, 1 month
[JBoss JIRA] (JBIDE-13443) Can't install on Kepler because of Birt
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13443?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13443:
----------------------------------------
Associate site for master is 4.2.1 http://download.jboss.org/jbosstools/updates/juno/SR1a/ which provides a version of Birt we can't install on Kepler
> Can't install on Kepler because of Birt
> ---------------------------------------
>
> Key: JBIDE-13443
> URL: https://issues.jboss.org/browse/JBIDE-13443
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: birt, target-platform
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> The version of Birt we build against does not match with version for Kepler and conflicts on ICU4j
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> says:
> {quote}
> Could not install from: http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss BIRT Integration 1.4.0.Alpha1-v20130128-1419-B356 (org.jboss.tools.birt.feature.feature.group 1.4.0.Alpha1-v20130128-1419-B356)
> Software currently installed: Eclipse IDE for Java EE Developers 2.0.0.20121218-0936 (epp.package.jee 2.0.0.20121218-0936)
> Only one of the following can be installed at once:
> International Components for Unicode for Java (ICU4J) 4.4.2.v20110823 (com.ibm.icu 4.4.2.v20110823)
> International Components for Unicode for Java (ICU4J) 50.1.0.v20121116-2 (com.ibm.icu 50.1.0.v20121116-2)
> Cannot satisfy dependency:
> From: Eclipse IDE for Java EE Developers 2.0.0.20121218-0936 (epp.package.jee 2.0.0.20121218-0936)
> To: org.eclipse.epp.package.jee.feature.feature.group [2.0.0.20121218-0936]
> Cannot satisfy dependency:
> From: BIRT Chart Framework 4.2.1.v20120820-828i7EFQCnvK_6wFGvqLR (org.eclipse.birt.chart.feature.group 4.2.1.v20120820-828i7EFQCnvK_6wFGvqLR)
> To: org.eclipse.birt.core [4.2.1.v201209121203]
> Cannot satisfy dependency:
> From: BIRT Core Package 4.2.1.v201209121203 (org.eclipse.birt.core 4.2.1.v201209121203)
> To: package com.ibm.icu.lang [3.4.4,5.0.0)
> Cannot satisfy dependency:
> From: Eclipse e4 Rich Client Platform 1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4 (org.eclipse.e4.rcp.feature.group 1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4)
> To: com.ibm.icu [50.1.0.v20121116-2]
> Cannot satisfy dependency:
> From: Java EE IDE Feature 2.0.0.20121218-0936 (org.eclipse.epp.package.jee.feature.feature.group 2.0.0.20121218-0936)
> To: org.eclipse.platform.feature.group [4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP]
> Cannot satisfy dependency:
> From: Eclipse Platform 4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP (org.eclipse.platform.feature.group 4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP)
> To: org.eclipse.rcp.feature.group [4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP]
> Cannot satisfy dependency:
> From: Eclipse RCP 4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP (org.eclipse.rcp.feature.group 4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP)
> To: org.eclipse.e4.rcp.feature.group [1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4]
> Cannot satisfy dependency:
> From: JBoss BIRT Integration 1.4.0.Alpha1-v20130128-1419-B356 (org.jboss.tools.birt.feature.feature.group 1.4.0.Alpha1-v20130128-1419-B356)
> To: org.eclipse.birt.chart.feature.group 2.5.0
> {quote}
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13443) Can't install on Kepler because of Birt
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13443?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-13443:
-----------------------------------
Summary: Can't install on Kepler because of Birt (was: Update version of Birt in Kepler target platform)
> Can't install on Kepler because of Birt
> ---------------------------------------
>
> Key: JBIDE-13443
> URL: https://issues.jboss.org/browse/JBIDE-13443
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: birt, target-platform
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> The version of Birt we build against does not match with version for Kepler and conflicts on ICU4j
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> says:
> {quote}
> Could not install from: http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss BIRT Integration 1.4.0.Alpha1-v20130128-1419-B356 (org.jboss.tools.birt.feature.feature.group 1.4.0.Alpha1-v20130128-1419-B356)
> Software currently installed: Eclipse IDE for Java EE Developers 2.0.0.20121218-0936 (epp.package.jee 2.0.0.20121218-0936)
> Only one of the following can be installed at once:
> International Components for Unicode for Java (ICU4J) 4.4.2.v20110823 (com.ibm.icu 4.4.2.v20110823)
> International Components for Unicode for Java (ICU4J) 50.1.0.v20121116-2 (com.ibm.icu 50.1.0.v20121116-2)
> Cannot satisfy dependency:
> From: Eclipse IDE for Java EE Developers 2.0.0.20121218-0936 (epp.package.jee 2.0.0.20121218-0936)
> To: org.eclipse.epp.package.jee.feature.feature.group [2.0.0.20121218-0936]
> Cannot satisfy dependency:
> From: BIRT Chart Framework 4.2.1.v20120820-828i7EFQCnvK_6wFGvqLR (org.eclipse.birt.chart.feature.group 4.2.1.v20120820-828i7EFQCnvK_6wFGvqLR)
> To: org.eclipse.birt.core [4.2.1.v201209121203]
> Cannot satisfy dependency:
> From: BIRT Core Package 4.2.1.v201209121203 (org.eclipse.birt.core 4.2.1.v201209121203)
> To: package com.ibm.icu.lang [3.4.4,5.0.0)
> Cannot satisfy dependency:
> From: Eclipse e4 Rich Client Platform 1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4 (org.eclipse.e4.rcp.feature.group 1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4)
> To: com.ibm.icu [50.1.0.v20121116-2]
> Cannot satisfy dependency:
> From: Java EE IDE Feature 2.0.0.20121218-0936 (org.eclipse.epp.package.jee.feature.feature.group 2.0.0.20121218-0936)
> To: org.eclipse.platform.feature.group [4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP]
> Cannot satisfy dependency:
> From: Eclipse Platform 4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP (org.eclipse.platform.feature.group 4.3.0.v20121210-194028-9PF7VHLnG0BBkXvb-5n61JdBeLn2Lmpr5BVxLP)
> To: org.eclipse.rcp.feature.group [4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP]
> Cannot satisfy dependency:
> From: Eclipse RCP 4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP (org.eclipse.rcp.feature.group 4.3.0.v20121212-184727-7IAUA7Bs-QiyWqWVNz0_nT4qjCeP)
> To: org.eclipse.e4.rcp.feature.group [1.1.0.v20121210-193513-9gFTdGWGGGduU3t_iBdO01nz--4]
> Cannot satisfy dependency:
> From: JBoss BIRT Integration 1.4.0.Alpha1-v20130128-1419-B356 (org.jboss.tools.birt.feature.feature.group 1.4.0.Alpha1-v20130128-1419-B356)
> To: org.eclipse.birt.chart.feature.group 2.5.0
> {quote}
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13451) Too many "xmlns:"-proposals when requesting content assist for tag attribute name
by Victor Rubezhny (JIRA)
Victor Rubezhny created JBIDE-13451:
---------------------------------------
Summary: Too many "xmlns:"-proposals when requesting content assist for tag attribute name
Key: JBIDE-13451
URL: https://issues.jboss.org/browse/JBIDE-13451
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.1.0.Alpha1
Reporter: Victor Rubezhny
Assignee: Victor Rubezhny
Fix For: 4.1.0.Alpha1
When requesting the Content Assist for a tag attribute name there are too many "xmlns:" proposals in the proposal list.
Need to hide these proposals for all the tags other that a page root element by showing those namespace proposals only if the entered text matches the "xmlns:" string.
--
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
13 years, 1 month
[JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13266:
------------------------------------
Two comments in http://wiki.eclipse.org/Tycho/Pack200 that worry me:
a) "Note that deprecated eclipse-update-site doesn't consider packed artifacts. "
So we'll have to migrate the remaining eclipse-update-site poms to eclipse-repository (and may lose some of the post-processing steps we do right now in https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...)
b) "This does not apply on a full repository. eclipse-repository can only consume existing pack200'ed artifacts, not generate some. "
If I'm reading that correctly, I suspect that means that where today we can build an update site consisting of locally built AND upstream artifacts, in future this will have to be TWO builds: one to build stuff locally, then a second one to aggregate upstream and the local stuff into a single repo w/ pack.gz artifacts. I hope I'm wrong here, as that extra step would be a PITA.
> 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
13 years, 1 month