January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12973) publish reddeer update site to download.jboss.org

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-12973: --------------------------------------- Thanks Nick, this seems to work. So the next step for me is to remove repo definitions from all the tests and have just one repo defined in our root pom. For now it is the master nightly build, but of course the idea was that we always point to some specific build so that will be the next step. I tried using your promote job to create this: http://download.jboss.org/jbosstools/updates/integration/kepler/core/redd... This was just a first attempt. At first I thought that the job will also ask for a version and then change the feature version but I guess I was wrong - so we need to have all the correct versions already in the builds before we promote that build, right? What path would you suggest I use in the future? Except for the version (the last part), is the above ok? Next time maybe I should use something like 0.2.0.201301271221 to reflect the exact snapshot? > publish reddeer update site to download.jboss.org > ------------------------------------------------- > > Key: JBIDE-12973 > URL: https://issues.jboss.org/browse/JBIDE-12973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.1.x > > > Red deer should publish nightly/development/stable update sites like other components of JBT onto download.jboss.org. > Simplest way to get a nightly build into download.jboss.org/jbosstools/builds/staging/ is to use my publish.sh [1] script as a step during your build job. > Then, if you want to copy that to a more stable URL (for a dev milestone or stable release) use this job [2]: > [1] https://svn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12973) publish reddeer update site to download.jboss.org

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12973?page=com.atlassian.jira.plugi... ] Martin Malina reassigned JBIDE-12973: ------------------------------------- Assignee: Nick Boldt (was: Martin Malina) Nick, can you please answer my questions and then assign back to me? Thanks. > publish reddeer update site to download.jboss.org > ------------------------------------------------- > > Key: JBIDE-12973 > URL: https://issues.jboss.org/browse/JBIDE-12973 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, testing, updatesite > Affects Versions: 4.0.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > > Red deer should publish nightly/development/stable update sites like other components of JBT onto download.jboss.org. > Simplest way to get a nightly build into download.jboss.org/jbosstools/builds/staging/ is to use my publish.sh [1] script as a step during your build job. > Then, if you want to copy that to a more stable URL (for a dev milestone or stable release) use this job [2]: > [1] https://svn.jboss.org/repos/jbosstools/trunk/build/publish/publish.sh > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-promote/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13413) jQuery Mobile Widget Palette

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13413?page=com.atlassian.jira.plugi... ] Yahor Radtsevich updated JBIDE-13413: ------------------------------------- Attachment: CSS-Preview.png Yes, this is possible. There is CSS Preview View in {{org.jboss.tools.jst.css}}. !CSS-Preview.png|thumbnail! See the code of the [CSSBrowser|https://github.com/jbosstools/jbosstools-jst/blob/master/plugi...] class. > jQuery Mobile Widget Palette > ---------------------------- > > Key: JBIDE-13413 > URL: https://issues.jboss.org/browse/JBIDE-13413 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 4.1.x > > Attachments: CSS-Preview.png, NewBlock.bmml, NewBlock.bmml, NewBlock.png, NewButton.bmml, NewButton.png, NewCheckBox.bmml, NewCheckBox.png, NewDialog.bmml, NewDialog.bmml, NewDialog.png, NewFlip.bmml, NewFlip.png, NewGrid.bmml, NewGrid.png, NewGroupedCheckBoxes.bmml, NewGroupedCheckBoxes.png, NewHeaderBar.bmml, NewHeaderBar.png, NewListview.bmml, NewListview.png, NewNavbar.bmml, NewNavbar.png, NewPage.bmml, NewPage.png, NewPopup.bmml, NewPopup.png, NewRadioButton.bmml, NewRadioButton.png, withwithoutpreview.bmml, withwithoutpreview.png > > > http://jquerymobile.com/test/ > See my proposal regarding the content of jQuery Mobile palette below. > Also I have an idea to add a live preview into each wizard. > We could try to add a browser to the wizard which will show how the widget is going to look. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13458) Make apitools good to be contributed to Eclipse

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-13458: -------------------------------------- Summary: Make apitools good to be contributed to Eclipse Key: JBIDE-13458 URL: https://issues.jboss.org/browse/JBIDE-13458 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Mickael Istria Assignee: Rob Stryker Based on Ant tasks from https://github.com/mickaelistria/apitooling and https://github.com/robstryker/apitooling , it would be good to contribute our API Tooling efforts to Eclipse: https://bugs.eclipse.org/bugs/show_bug.cgi?id=399276 In order to contribute this work to Eclipse, I think we need to make the following changes for Eclipse/OxBEEF code: * Rename net.oxbeef bundle to org.eclipse.pde.apitools.ant . It should then contain the Ant tasks that are currently in org.eclipse.pde.apitools.ui/src-ant * Deprecate the old ant tasks from org.eclipse.pde.apitools.ui/src-ant * Include a flag to existing tasks to ignore missing .apidescription file * Optionally add some more convenient tasks. These changes will then be proposed to PDE, so we'll be able to go ahead a contribute a Mojo consuming only this bundle and the tweaks in it rather than org.eclipse.pde.apitools.ui. -- 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, 3 months

1
0
0 / 0

[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 closed JBIDE-13443. ------------------------------ Resolution: Done As of build 6057, https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-4.1_trunk... , contents from http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ can be installed into Kepler M4 JEE bundle without workaround. Closing. > 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

11 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-298) 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created TOOLSDOC-298: -------------------------------------------- Summary: 6.0 release notes says it *requires* JDK 6 which is not true since it also works with JDK 7 Key: TOOLSDOC-298 URL: https://issues.jboss.org/browse/TOOLSDOC-298 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Enhancement Components: Release Notes Reporter: Max Rydahl Andersen Assignee: Michelle Murray Was pointed out by [~aileenc] that our release notes say: "JBoss Developer Studio 6 requires Java Development Kit (JDK) 1.6." at https://access.redhat.com/knowledge/docs/en-US/JBoss_Developer_Studio/6.0... That is not exactly correct since it also runs and have been tested on Java 7. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-8) JBossTools Integration Stack :: drools: Verify the component configuration of the initial IS tooling release.

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-8?page=com.atlassian.jira.plugin.sy... ] Kris Verlaenen commented on JBTIS-8: ------------------------------------ Looks good now, Thx! Kris > JBossTools Integration Stack :: drools: Verify the component configuration of the initial IS tooling release. > ------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-8 > URL: https://issues.jboss.org/browse/JBTIS-8 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: drools > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Kris Verlaenen > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-8) JBossTools Integration Stack :: drools: Verify the component configuration of the initial IS tooling release.

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-8?page=com.atlassian.jira.plugin.sy... ] Kris Verlaenen resolved JBTIS-8. -------------------------------- Resolution: Done > JBossTools Integration Stack :: drools: Verify the component configuration of the initial IS tooling release. > ------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-8 > URL: https://issues.jboss.org/browse/JBTIS-8 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: drools > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Kris Verlaenen > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13457) Wrong link in MemberController in default Java EE Web Project

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13457: ------------------------------------ Summary: Wrong link in MemberController in default Java EE Web Project Key: JBIDE-13457 URL: https://issues.jboss.org/browse/JBIDE-13457 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.0.0.Final Reporter: Jiri Peterka Assignee: Snjezana Peco Fix For: 4.1.0.Alpha1 There is invalid link in MemberControler package org.jboss.tools.examples.controller; ... // EL name // Read more about the @Model stereotype in this FAQ: // http://sfwk.org/Documentation/WhatIsThePurposeOfTheModelAnnotation This link is not valid anymore -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13283) Use Akamai for Target-Platform, Mirror, releases stuff

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13283?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13283: ---------------------------------------- Here is a list of things to mirror: To mirror {code} examples/ Exceptions: nightly/ publishExample.sh requirements/ targetplatform/jbosstoolstarget/ Including: *.Final-SNAPSHOT/ (?<!SNAPSHOT)/ everything that is not SNAPSHOT, anticipating JBIDE-13316 test-runtimes/ updates/ Exceptions: development/ nightly/ m2e-*/ staging/ README.html stable/ (contains only links and discovery definition, volatile content) requirements/ .directory README.building.txt README.html mirror.sh.txt remove.references.xml **/build*.xml {code} > Use Akamai for Target-Platform, Mirror, releases stuff > ------------------------------------------------------ > > Key: JBIDE-13283 > URL: https://issues.jboss.org/browse/JBIDE-13283 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > All our repositories that are either mirrors or target-platform are not updated often. Then we could use Akamai to improve performances. At least these folders would be good: > * http://download.jboss.org/jbosstools/updates/requirements/ > * http://download.jboss.org/jbosstools/updates/stable/ -- 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, 3 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