March 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15394) Add arquillian.xml GUI editor to jbosstools-arquillian

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15394?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15394: --------------------------------------- The http://screencast.com/t/s16HzZEzmx screencast is showing the way to add the required artifacts to pom.xml while editing the arquillian.xml file. Notice: the Servlet 2.5/Servlet 3.0 protocol requires the org.jboss.arquillian.protocol:arquillian-protocol-servlet artifact. You will see a warning icon if the required artifact doesn't exist. When you click the icon, you will get the description of the issue and an action (Add required dependencies...) that can fix the issue. If you call the action, you will get the standard refactoring dialog so that you can review the change, add dependencies or cancel. A similar action has been added when editing a container. I have also added an action for opening a pom.xml file from the Arquillian XML editor. TODO - add a list of possible values for different properties (protocol properties, container properties ...) - add a list of possible values for extensions - add a validation and an action for the extension's dependencies Re the extensions, we could use Masao's extension.json, but it would be better if we have a file similar to containers.json on the internet. [~aslak], is there a file similar to https://github.com/masao-kunii/jbosstools-arquillian/blob/jbide-15394/plu... that describes Arquillian extensions? > Add arquillian.xml GUI editor to jbosstools-arquillian > ------------------------------------------------------ > > Key: JBIDE-15394 > URL: https://issues.jboss.org/browse/JBIDE-15394 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: testing-tools > Reporter: Masao Kunii > Assignee: Snjezana Peco > Priority: Optional > Fix For: 4.2.0.Beta1 > > > The arquillian.xml editor is an editor to edit arquillian.xml easily and visually. This is a feature for jbosstools-arquillian(https://github.com/jbosstools/jbosstools-arquillian) and enables to: > - Edit containers, container groups, extensions, protocols and engines > - Modify pom.xml automatically corresponding settings in arquillian.xml > - Register favorite container/container groups from Eclipse preferences -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16736) Project examples XML points to old examples

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16736?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-16736: ------------------------------------- I kept http://download.jboss.org/jbosstools/examples/project-examples-maven-4.1.... because there was no change between 4.1.1 and 4.1.2 As for some examples pointing at 4.0.0 instead of 4.1.1 : well the 4.1.1 ones were obviously new and required, compared to the older 4.0.0s, so are referenced as such. As for the old ones (4.0.0) I would have to test them all before switching them to 4.1.1. But I can do the change and let you do that :-) > Project examples XML points to old examples > ------------------------------------------- > > Key: JBIDE-16736 > URL: https://issues.jboss.org/browse/JBIDE-16736 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.2.CR1 > Environment: JBT 4.1.2.CR1 > Reporter: Radim Hopp > Fix For: 4.1.2.Final > > > As far as I understand, project examples plugin (at least in JBT) points to some xmls where are project examples defined (name, description, location). > Project examples plugin from JBT 4.1.2.CR1 (org.jboss.tools.community.project.examples_1.5.4.Final-v20140303-0549-B152.jar) points to http://download.jboss.org/jbosstools/examples/project-examples-maven-4.1.... and this file points all its examples to directory 4.0.0.GA (http://download.jboss.org/jbosstools/examples/4.0.0.GA/) even though there are newer versions in directory 4.1.1.GA (http://download.jboss.org/jbosstools/examples/4.1.1.GA/). > I think this issue also affects 4.1.1 (and maybe 4.1.0), but I anly tested it now on 4.1.2.CR1. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15355) The JBoss Central quickstarts should include the .html version of the readme files.

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15355?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-15355: ------------------------------------ Waiting for JBIDE-16736 to verify this. > The JBoss Central quickstarts should include the .html version of the readme files. > ----------------------------------------------------------------------------------- > > Key: JBIDE-15355 > URL: https://issues.jboss.org/browse/JBIDE-15355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Reporter: Burr Sutter > Assignee: Snjezana Peco > Fix For: 4.1.1.Final, 4.2.0.Alpha1 > > > The helloworld quickstart on JBoss Central offers the end-user a readme.md - which is not easily readable by the average human. It includes a phrase that looks like > If you have not yet done so, you must [Configure Maven](../README.md#mavenconfiguration) before testing the quickstarts. > The JBoss Central quickstarts should include the .html version of the readme files. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16736) Project examples XML points to old examples

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-16736: ---------------------------------- Summary: Project examples XML points to old examples Key: JBIDE-16736 URL: https://issues.jboss.org/browse/JBIDE-16736 Project: Tools (JBoss Tools) Issue Type: Bug Components: project-examples Affects Versions: 4.1.2.CR1 Environment: JBT 4.1.2.CR1 Reporter: Radim Hopp Fix For: 4.1.2.Final As far as I understand, project examples plugin (at least in JBT) points to some xmls where are project examples defined (name, description, location). Project examples plugin from JBT 4.1.2.CR1 (org.jboss.tools.community.project.examples_1.5.4.Final-v20140303-0549-B152.jar) points to http://download.jboss.org/jbosstools/examples/project-examples-maven-4.1.... and this file points all its examples to directory 4.0.0.GA (http://download.jboss.org/jbosstools/examples/4.0.0.GA/) even though there are newer versions in directory 4.1.1.GA (http://download.jboss.org/jbosstools/examples/4.1.1.GA/). I think this issue also affects 4.1.1 (and maybe 4.1.0), but I anly tested it now on 4.1.2.CR1. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15482: ------------------------------------ [~maxandersen] He's saying that because the defaults set in the parent pom [1] point to URLs like http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_4.2.l... [2] by default you get only the latest staged nightly build. [1] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... [2] https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... [~dgolovin] We could change the default *jbosstools-site-suffix* to be *all* instead of all/repo, thus pointing builds at http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_4.2.l... which is a composite of {code} <child location='../../../staging/jbosstools-base_4.2.luna/all/repo/'/> <child location='../../../staging.previous/jbosstools-base_4.2.luna/all/repo/'/> {code} Or we can continue down the path of timestamped folders proposed in this JIRA and generate composite*.xml files FOR EACH PROJECT, similar to the above but with the added complexity that it's for 17 projects instead of 1 composite site. > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 4.2.x > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {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

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16735) Fix broken mylyn tests

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16735?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-16735: -------------------------------------- https://github.com/jbosstools/jbosstools-integration-tests/pull/525 > Fix broken mylyn tests > ---------------------- > > Key: JBIDE-16735 > URL: https://issues.jboss.org/browse/JBIDE-16735 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.Beta1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.0.Beta2 > > > http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/400/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16735) Fix broken mylyn tests

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16735?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-16735: -------------------------------------- Need to change call to DefaultCombo to LabeledCombo tests/org.jboss.tools.mylyn.ui.bot.test/src/org/jboss/tools/mylyn/ui/bot/test/MylynTestBzQuery.java > Fix broken mylyn tests > ---------------------- > > Key: JBIDE-16735 > URL: https://issues.jboss.org/browse/JBIDE-16735 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.2.0.Beta1 > Reporter: Len DiMaggio > Assignee: Len DiMaggio > Fix For: 4.2.0.Beta2 > > > http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/400/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16735) Fix broken mylyn tests

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-16735: ------------------------------------ Summary: Fix broken mylyn tests Key: JBIDE-16735 URL: https://issues.jboss.org/browse/JBIDE-16735 Project: Tools (JBoss Tools) Issue Type: Task Components: qa Affects Versions: 4.2.0.Beta1 Reporter: Len DiMaggio Assignee: Len DiMaggio Fix For: 4.2.0.Beta2 http://machydra.brq.redhat.com:8080/job/jbosstools.mylyn.bot.tests.poc/400/ -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2956) Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBDS-2956?page=com.atlassian.jira.plugin.... ] Snjezana Peco commented on JBDS-2956: ------------------------------------- JBDS 7 includes those plugins so the issue is caused by OSGi changes. > Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting" > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-2956 > URL: https://issues.jboss.org/browse/JBDS-2956 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Alpha2 > Environment: 64-bit Fedora 17 > Reporter: Marián Labuda > Assignee: Snjezana Peco > Attachments: jbds800Alpha2report.zip, jbds_part1.png, jbds_part2.png, JBT4.2.0.Alpha2breport.zip, jbt_part1.png, jbt_part2.png, jbt_part3.png, spring_projects.png > > > After installing Spring IDE into JBDS 8.0.0.Alpha2 there should be option to create associated projects / examples / files... from menu File - Other - Spring, but there is only item for creation Spring bean configuration file. Others are missing. Tests also JBT 4.2.0.Alpha2 and there was not this issue. > See attached file. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2956) Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting"

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-2956?page=com.atlassian.jira.plugin.... ] Marián Labuda commented on JBDS-2956: ------------------------------------- [~maxandersen] yeah, I wanted to be sure so I have installed 7.1.1 again and with the same Spring IDE version the problem does not occur in JBDS (I tried in on latest build GA-v20140303-1841-B672). > Spring IDE's associated projects and files cannot be created and many plugins never goes past "Starting" > -------------------------------------------------------------------------------------------------------- > > Key: JBDS-2956 > URL: https://issues.jboss.org/browse/JBDS-2956 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification > Affects Versions: 8.0.0.Alpha2 > Environment: 64-bit Fedora 17 > Reporter: Marián Labuda > Assignee: Snjezana Peco > Attachments: jbds800Alpha2report.zip, jbds_part1.png, jbds_part2.png, JBT4.2.0.Alpha2breport.zip, jbt_part1.png, jbt_part2.png, jbt_part3.png, spring_projects.png > > > After installing Spring IDE into JBDS 8.0.0.Alpha2 there should be option to create associated projects / examples / files... from menu File - Other - Spring, but there is only item for creation Spring bean configuration file. Others are missing. Tests also JBT 4.2.0.Alpha2 and there was not this issue. > See attached file. -- 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, 3 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 March 2014