[JBoss JIRA] (JBIDE-13443) Can't install on Kepler because of Birt
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13443?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-13443:
----------------------------------
Assignee: Nick Boldt (was: Snjezana Peco)
> 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: Nick Boldt
> Fix For: 4.1.0.Alpha1
>
> Attachments: keplerM4-JBT-BIRT-integration-installed.png
>
>
> 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, 2 months
[JBoss JIRA] (JBIDE-13443) Can't install on Kepler because of Birt
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13443?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13443:
------------------------------------
Found a workaround, which won't be needed once the nightly build has respun with this change [1].
[1] https://github.com/jbosstools/jbosstools-build-sites/commit/abce3f9bee5dd...
a) install Kepler M4 JEE
b) Help > Install > add http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ > search "birt" > select feature > *{color:red}FAIL*{color}
c) cancel install attempt. Help > Install > add http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3...
d) select previously added site http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ > search "birt" > select feature > *{color:green}SUCCESS{color}*
> 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, 2 months
[JBoss JIRA] (JBIDE-12850) Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12850?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-12850 at 1/30/13 12:30 PM:
--------------------------------------------------------------
Decision is that Pipeline view is pretty but not that helpful when there's only a single Flow job in it.
So... to merge the usefulness of both Pipeline and Flow, suggest we create 5 new Flow jobs:
{code}
Base
\-> Forge|Freemarker|GWT (parallel)
\-> Server>(WS|OS) (server first, WS/OS in parallel)
\-> (Hibernate>BIRT)|(Xulrunner>VPE>JST) (two parellel series of builds)
\-> JavaEE>Portlet>Central (series)
{code}
was (Author: nickboldt):
Decision is that Pipeline view is pretty but not that helpful when there's only a single Flow job in it.
So... to merge the usefulness of both Pipeline and Flow, suggest we create 5 new Flow jobs:
{code}
Base
\-> Forge|Freemarker|GWT (parallel)
\-> Server>(WS|OS) (server first, WS/OS in parallel)
\-> Hibernate>BIRT>Xulrunner>VPE>JST (series)
\-> JavaEE>Portlet>Central (series)
{code}
> Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-12850
> URL: https://issues.jboss.org/browse/JBIDE-12850
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Labels: f2f2012
> Fix For: 4.1.x
>
> Attachments: buildflow.png, pipeline_40.png, pipeline_buildflow.png
>
>
> In order to build the whole JBoss Tools in one click, we could try to use the https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin plugin to -orchestrate- display the whole build workflow, and the https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin plugin to orchestrate 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
13 years, 2 months
[JBoss JIRA] (JBIDE-12850) Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12850?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-12850 at 1/30/13 12:31 PM:
--------------------------------------------------------------
Decision is that Pipeline view is pretty but not that helpful when there's only a single Flow job in it.
So... to merge the usefulness of both Pipeline and Flow, suggest we create 5 new Flow jobs:
{code}
Base
\-> Forge|Freemarker|GWT (parallel)
\-> Server>(WS|OS) (server first, WS/OS in parallel)
\-> (Hibernate>BIRT)|(Xulrunner>VPE>JST) (two parallel series of builds)
\-> JavaEE>Portlet>Central (series)
{code}
was (Author: nickboldt):
Decision is that Pipeline view is pretty but not that helpful when there's only a single Flow job in it.
So... to merge the usefulness of both Pipeline and Flow, suggest we create 5 new Flow jobs:
{code}
Base
\-> Forge|Freemarker|GWT (parallel)
\-> Server>(WS|OS) (server first, WS/OS in parallel)
\-> (Hibernate>BIRT)|(Xulrunner>VPE>JST) (two parellel series of builds)
\-> JavaEE>Portlet>Central (series)
{code}
> Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-12850
> URL: https://issues.jboss.org/browse/JBIDE-12850
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Labels: f2f2012
> Fix For: 4.1.x
>
> Attachments: buildflow.png, pipeline_40.png, pipeline_buildflow.png
>
>
> In order to build the whole JBoss Tools in one click, we could try to use the https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin plugin to -orchestrate- display the whole build workflow, and the https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin plugin to orchestrate 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
13 years, 2 months
[JBoss JIRA] (JBIDE-12850) Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12850?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-12850 at 1/30/13 12:28 PM:
--------------------------------------------------------------
Decision is that Pipeline view is pretty but not that helpful when there's only a single Flow job in it.
So... to merge the usefulness of both Pipeline and Flow, suggest we create 5 new Flow jobs:
{code}
Base
\-> Forge|Freemarker|GWT (parallel)
\-> Server>(WS|OS) (server first, WS/OS in parallel)
\-> Hibernate>BIRT>Xulrunner>VPE>JST (series)
\-> JavaEE>Portlet>Central (series)
{code}
was (Author: nickboldt):
Decision is that Pipeline view is pretty but not that helpful when there's only a single Flow job in it.
So... to merge the usefulness of both Pipeline and Flow, suggest we create 5 new Flow jobs:
Base
\-> Forge|Freemarker|GWT (parallel)
\-> Server>(WS|OS) (server first, WS/OS in parallel)
\-> Hibernate>BIRT>Xulrunner>VPE>JST (series)
\-> JavaEE>Portlet>Central (series)
> Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-12850
> URL: https://issues.jboss.org/browse/JBIDE-12850
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Labels: f2f2012
> Fix For: 4.1.x
>
> Attachments: buildflow.png, pipeline_40.png, pipeline_buildflow.png
>
>
> In order to build the whole JBoss Tools in one click, we could try to use the https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin plugin to -orchestrate- display the whole build workflow, and the https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin plugin to orchestrate 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
13 years, 2 months
[JBoss JIRA] (JBIDE-12850) Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12850?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-12850 at 1/30/13 12:18 PM:
--------------------------------------------------------------
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
So, it looks like we can EITHER:
a) define a workflow that sets up the linkages between jobs in one place...
!buildflow.png!
... which makes the pipeline view rather useless, as it only contains a single entry:
See [^pipeline_buildflow.png]
or
b) continue to have jobs defined w/ upstream/downstream linkages, and then use the pipeline view:
See [^pipeline_40.png]
was (Author: nickboldt):
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
So, it looks like we can EITHER:
a) define a workflow that sets up the linkages between jobs in one place...
!buildflow.png!
... which makes the pipeline view rather useless, as it only contains a single entry:
!pipeline_buildflow.png!
or
b) continue to have jobs defined w/ upstream/downstream linkages, and then use the pipeline view:
!pipeline_40.png!
> Investigate usage of Jenkins Build Pipeline & Build Flow plugins for our build stream
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-12850
> URL: https://issues.jboss.org/browse/JBIDE-12850
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Labels: f2f2012
> Fix For: 4.1.x
>
> Attachments: buildflow.png, pipeline_40.png, pipeline_buildflow.png
>
>
> In order to build the whole JBoss Tools in one click, we could try to use the https://wiki.jenkins-ci.org/display/JENKINS/Build+Pipeline+Plugin plugin to -orchestrate- display the whole build workflow, and the https://wiki.jenkins-ci.org/display/JENKINS/Build+Flow+Plugin plugin to orchestrate 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
13 years, 2 months
[JBoss JIRA] (JBIDE-13439) ESB Tests are failing locating project examples
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13439?page=com.atlassian.jira.plugi... ]
Len DiMaggio commented on JBIDE-13439:
--------------------------------------
To summarize the issue and solution for https://issues.jboss.org/browse/JBIDE-13439:
* The ESB examples are included here: http://download.jboss.org/jbosstools/examples/project-examples-jbds40.xml
* The ESB examples are not yet included here: http://download.jboss.org/jbosstools/examples/project-examples-jbds60.xml
* The examples should not be added to project-examples-jbds60.xml until SOA/ESB plugins are created for JBDS6, as without these plugins, the examples cannot be installed
* Interim builds for SOA/ESB plugins are available here: http://download.jboss.org/jbosstools/updates/integration/juno/integration...
* Action items/questins: When does SOA PM want JBDS6 to support SOA 5.3.x? When will SOA create ESB plugins to provide this support?
Background:
* http://ether-man.rhcloud.com/p/build.next
* https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j...
* User requests for early access to SOA-P/BRMS-P stuff for JBDS 6 (specifically for ESB) - https://community.jboss.org/message/794130#794130
* Until this issue is resolved, these tests will fail:
- http://machydra.brq.redhat.com:8080/job/esb.bot.tests.ldimaggi.matrixtest...
- http://machydra.brq.redhat.com:8080/view/Code%20Coverage/job/jbosstools.e...
> 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, 2 months
[JBoss JIRA] (JBIDE-13453) Remove old Palette view
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-13453:
---------------------------------------------
Summary: Remove old Palette view
Key: JBIDE-13453
URL: https://issues.jboss.org/browse/JBIDE-13453
Project: Tools (JBoss Tools)
Issue Type: Task
Components: common/jst/core
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
13 years, 2 months