September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15428) No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15428?page=com.atlassian.jira.plugi... ] Radoslav Rábara edited comment on JBIDE-15428 at 9/5/13 5:20 AM: ----------------------------------------------------------------- There is no error after the project is imported in a fresh workspace. was (Author: rrabara): There is no error after the project in imported in a fresh workspace. > No JAX-RS problems when importing a project that contains HTTPMethod annotation without @Target and @Retention > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15428 > URL: https://issues.jboss.org/browse/JBIDE-15428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.1.0.Final > Reporter: Radoslav Rábara > Fix For: 4.1.1.Alpha1 > > Attachments: After import.png, After workaround.png, Before import.png > > > After importing Dynamic Web Project with JAX-RS support with HTTPMethod annotation without @Target and @Retention annotations, there is no error. > This looks like a regression of JBIDE-12690. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15433) mvn/tycho does not bump version in site/category.xml

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15433?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15433: --------------------------------------------- so in short - all nightly builds haven't actually published 1.1.0 but only 1.0.0 ? > mvn/tycho does not bump version in site/category.xml > ---------------------------------------------------- > > Key: JBIDE-15433 > URL: https://issues.jboss.org/browse/JBIDE-15433 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Xavier Coulon > > After running the following command on the livereload component: > {code} > mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=1.2.0-SNAPSHOT > {code} > I could see that all pom.xml, feature.xml and MANIFEST.xml were updated, but not the site/category.xml which I had to edit myself (mvn clean verify failed) > {code} > <site> > <feature url="features/org.jboss.tools.livereload.feature_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature" version="1.2.0.qualifier"/> > <feature url="features/org.jboss.tools.livereload.feature.source_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature.source" version="1.2.0.qualifier"/> > </site> > {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15434) Bump LiveReload to version 1.2.0

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15434: ------------------------------------- Summary: Bump LiveReload to version 1.2.0 Key: JBIDE-15434 URL: https://issues.jboss.org/browse/JBIDE-15434 Project: Tools (JBoss Tools) Issue Type: Task Components: livereload Affects Versions: 4.2.0.Alpha1 Reporter: Xavier Coulon Assignee: Xavier Coulon Fix For: 4.2.0.Alpha1 Because the version on branch 4.1.x was also bumped to 1.1.0 (by mistake), we decided to bump the 'master' branch to 1.2.0 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15433) mvn/tycho does not bump version in site/category.xml

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15433?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15433: ---------------------------------------- [~maxandersen]: It was using previous builds from the composite (on CI) or aggregated site (locally) which are input repository to resolve internal dependencies. > mvn/tycho does not bump version in site/category.xml > ---------------------------------------------------- > > Key: JBIDE-15433 > URL: https://issues.jboss.org/browse/JBIDE-15433 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Xavier Coulon > > After running the following command on the livereload component: > {code} > mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=1.2.0-SNAPSHOT > {code} > I could see that all pom.xml, feature.xml and MANIFEST.xml were updated, but not the site/category.xml which I had to edit myself (mvn clean verify failed) > {code} > <site> > <feature url="features/org.jboss.tools.livereload.feature_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature" version="1.2.0.qualifier"/> > <feature url="features/org.jboss.tools.livereload.feature.source_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature.source" version="1.2.0.qualifier"/> > </site> > {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15433) mvn/tycho does not bump version in site/category.xml

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15433?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15433: --------------------------------------- Thanks, [~mickael_istria] ! > mvn/tycho does not bump version in site/category.xml > ---------------------------------------------------- > > Key: JBIDE-15433 > URL: https://issues.jboss.org/browse/JBIDE-15433 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Xavier Coulon > > After running the following command on the livereload component: > {code} > mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=1.2.0-SNAPSHOT > {code} > I could see that all pom.xml, feature.xml and MANIFEST.xml were updated, but not the site/category.xml which I had to edit myself (mvn clean verify failed) > {code} > <site> > <feature url="features/org.jboss.tools.livereload.feature_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature" version="1.2.0.qualifier"/> > <feature url="features/org.jboss.tools.livereload.feature.source_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature.source" version="1.2.0.qualifier"/> > </site> > {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15392) Add api in server needed for source lookup

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15392?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15392: --------------------------------------------- [~snjeza] I get that you support just using a home directory and opposite to what [~rob.stryker] claims it is relevant to be able to do that. *but* that does not mean we cannot also have support for referencing servers directly and from there add better handling. In case you only have a dir you already identify the server versions you should be able to use as api to build a "virtual" server for this directory which you can use to explore it with ? [~rob.stryker] I believe this is not limited to servers < 7. Don't you need to know the list of module path that are to be loaded too for AS >= 7 > Add api in server needed for source lookup > ------------------------------------------ > > Key: JBIDE-15392 > URL: https://issues.jboss.org/browse/JBIDE-15392 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > As uncovered in https://github.com/jbosstools/jbosstools-central/pull/128/files#L5L120 we got a problem with source lookup code always having to play catchup with server changes. > We need to define a stable api that can be used here. > lets outline what api is actually needed and then subjiras for the specifics. > For me it looks like server lookup needs a few things: > 0. know exact version of server > 1. know the file structure of a certain server > 2. get dir or directories that contain jar that is the "runtime" > My guess is that #2 might just be sufficient for source code lookup. > Any comments ? -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15433) mvn/tycho does not bump version in site/category.xml

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15433?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-15433. ---------------------------------- Resolution: Won't Fix This is out of the scope of the tycho bump-version plugin. It's generally easier to change versions manually. Some tips: * Remove the "url" attribute from category.xml, it's useless (Tycho does not parse it) * Use 0.0.0 as version (except if you really want to use 1.2.0.qualifier). 0.0.0 will use the latest available version. It should generally be the one from the reactor. > mvn/tycho does not bump version in site/category.xml > ---------------------------------------------------- > > Key: JBIDE-15433 > URL: https://issues.jboss.org/browse/JBIDE-15433 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Xavier Coulon > > After running the following command on the livereload component: > {code} > mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=1.2.0-SNAPSHOT > {code} > I could see that all pom.xml, feature.xml and MANIFEST.xml were updated, but not the site/category.xml which I had to edit myself (mvn clean verify failed) > {code} > <site> > <feature url="features/org.jboss.tools.livereload.feature_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature" version="1.2.0.qualifier"/> > <feature url="features/org.jboss.tools.livereload.feature.source_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature.source" version="1.2.0.qualifier"/> > </site> > {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15433) mvn/tycho does not bump version in site/category.xml

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15433: ------------------------------------- Summary: mvn/tycho does not bump version in site/category.xml Key: JBIDE-15433 URL: https://issues.jboss.org/browse/JBIDE-15433 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: build Reporter: Xavier Coulon After running the following command on the livereload component: {code} mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=1.2.0-SNAPSHOT {code} I could see that all pom.xml, feature.xml and MANIFEST.xml were updated, but not the site/category.xml which I had to edit myself (mvn clean verify failed) {code} <site> <feature url="features/org.jboss.tools.livereload.feature_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature" version="1.2.0.qualifier"/> <feature url="features/org.jboss.tools.livereload.feature.source_1.2.0.qualifier.jar" id="org.jboss.tools.livereload.feature.source" version="1.2.0.qualifier"/> </site> {code} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2722) Include Kepler SR1 by default

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2722?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-2722: -------------------------------------- Component/s: build (was: openshift) > Include Kepler SR1 by default > ------------------------------ > > Key: JBDS-2722 > URL: https://issues.jboss.org/browse/JBDS-2722 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > > Kepler SR1 has bugfixes - we should include it in upcoming release. > * Affects JBT TP, JBDS TP, and JBDS installer. > * Verification by comparing old TPs and installer contents to newer one, eg., using vwatch tool [1] or by scheduled job [2]. > [1] https://github.com/jbdevstudio/jbdevstudio-qa/tree/master/vwatch > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14530) Support 'Arquillian Cruiser' in standard 'Outline' view

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14530?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14530: --------------------------------------------- there is no reason/logic in wanting to extend the outline view. I suggest to look at alternatives to solve the actual usecase or reject this. > Support 'Arquillian Cruiser' in standard 'Outline' view > ------------------------------------------------------- > > Key: JBIDE-14530 > URL: https://issues.jboss.org/browse/JBIDE-14530 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Aslak Knutsen > Assignee: Max Rydahl Andersen > Fix For: 4.1.x > > > Would it be possible to extend the normal 'Outline' view to specially handle 'Deployment methods' and add the option to continue drilling down into the content of the defined archive? -- 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, 7 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 September 2013