July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17781) Arquillian New and Noteworthy for 4.2.0.Beta3

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17781?page=com.atlassian.jira.plugi... ] Snjezana Peco resolved JBIDE-17781. ----------------------------------- Resolution: Done > Arquillian New and Noteworthy for 4.2.0.Beta3 > --------------------------------------------- > > Key: JBIDE-17781 > URL: https://issues.jboss.org/browse/JBIDE-17781 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: testing-tools > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Priority: Critical > Fix For: 4.2.0.Beta3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Arquillian is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Arquillian by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/wha...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17089) New Arquillian test case - classes selection

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17089?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-17089: ---------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > New Arquillian test case - classes selection > -------------------------------------------- > > Key: JBIDE-17089 > URL: https://issues.jboss.org/browse/JBIDE-17089 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: testing-tools > Affects Versions: 4.2.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > > When I am creating a new Arquillian test case there is a tab named Create Arquillian Deploy Method. This tab contains functionality for adding additional classes to the deployment. > # could you include tested class by default to that list? > # when I hit the Add button, there is nothing listed by default. I need to start typing. This is different behaviour than e.g. on the first wizard page where is my tested class listed by default (when choosing Class under test) -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17767) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Central]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17767?page=com.atlassian.jira.plugi... ] Fred Bricon closed JBIDE-17767. ------------------------------- Resolution: Done Done > For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Central] > ----------------------------------------------------- > > Key: JBIDE-17767 > URL: https://issues.jboss.org/browse/JBIDE-17767 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central, maven, project-examples > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.2.0.Beta3 > > > For JBIDE 4.2.0.Beta3 [Central]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3 > [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Beta3x > git push origin jbosstools-4.2.0.Beta3x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and > * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17608) improve p2diff's URI handling to support relative path folder and zips

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17608?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17608: --------------------------------------------- not blocking b3. should we put this for 4.2.x or LATER ? > improve p2diff's URI handling to support relative path folder and zips > ---------------------------------------------------------------------- > > Key: JBIDE-17608 > URL: https://issues.jboss.org/browse/JBIDE-17608 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > Instead of having to type: > {code} > p2diff file:///home/nboldt/tru/disco/jbtearlyaccesstarget/multiple/target/jbtearlyaccess-multiple.target.repo/ file:///home/nboldt/tru/disco/jbtearlyaccesstarget/multiple/target_FULL/jbtearlyaccess-multiple.target.repo/ > {code} > I'd like to see it work for > {code} > p2diff target target2 > or > p2diff site.zip site2.zip > {code} > So we need a few things: > a) find the nested repo in the specified folder (if not in `pwd` look in child folders for a p2 repo or repo zip) > b) better error reporting if the specified folders aren't repos or don't contain repos (right now p2diff does NOTHING if it doesn't like the URIs stated > c) if a local path exists, prepend file:// onto the file path so it behaves like a p2 URI > d) if a local repo zip found then prepend jar:file:// and append !/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17465) Should org.jboss.tools.as.test.core test EAP 6.2 and 6.3?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17465?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17465: --------------------------------------------- For about the 100th time - jbosstools-integration-tests are *not* where unit tests for main functionality should go. Does adding a simple runtime identification test of a single server add any specific overhead still ? its not like we need to run *all* tests against all runtimes. > Should org.jboss.tools.as.test.core test EAP 6.2 and 6.3? > --------------------------------------------------------- > > Key: JBIDE-17465 > URL: https://issues.jboss.org/browse/JBIDE-17465 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Rob Stryker > Fix For: 4.2.0.Beta3 > > > Looking in org.jboss.tools.as.test.core/pom.xml I see you test for & with EAP 6.1 but not 6.2 or 6.3. > https://github.com/jbosstools/jbosstools-server/blob/master/as/tests/org.... > Should that be updated to include 6.2 (now available) and 6.3 (in a month or so when it's released) ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17608) improve p2diff's URI handling to support relative path folder and zips

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17608?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17608: ---------------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > improve p2diff's URI handling to support relative path folder and zips > ---------------------------------------------------------------------- > > Key: JBIDE-17608 > URL: https://issues.jboss.org/browse/JBIDE-17608 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, upstream > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > Instead of having to type: > {code} > p2diff file:///home/nboldt/tru/disco/jbtearlyaccesstarget/multiple/target/jbtearlyaccess-multiple.target.repo/ file:///home/nboldt/tru/disco/jbtearlyaccesstarget/multiple/target_FULL/jbtearlyaccess-multiple.target.repo/ > {code} > I'd like to see it work for > {code} > p2diff target target2 > or > p2diff site.zip site2.zip > {code} > So we need a few things: > a) find the nested repo in the specified folder (if not in `pwd` look in child folders for a p2 repo or repo zip) > b) better error reporting if the specified folders aren't repos or don't contain repos (right now p2diff does NOTHING if it doesn't like the URIs stated > c) if a local path exists, prepend file:// onto the file path so it behaves like a p2 URI > d) if a local repo zip found then prepend jar:file:// and append !/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12370) Add a video that shows how to handle missing requirements on New Project Example screen

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12370?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-12370: --------------------------------------------- sent email to ping @mmurray in addition to this ;) > Add a video that shows how to handle missing requirements on New Project Example screen > --------------------------------------------------------------------------------------- > > Key: JBIDE-12370 > URL: https://issues.jboss.org/browse/JBIDE-12370 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 3.3.0.Final > Reporter: Pete Muir > Assignee: Michelle Murray > Priority: Critical > Labels: doc'ed > Fix For: 4.2.0.CR1 > > > If the user clicks on _JBoss Central | Java EE Web Project_ they are presented with this screen http://www.jboss.org/jdf/stage/quickstarts/jboss-as-quickstart/guide//gfx... - it would be nice to have a short video showing how people can solve missing requirements, e.g. by clicking the Install button. This can then be linked to from tutorials that use these wizards. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12370) Add a video that shows how to handle missing requirements on New Project Example screen

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12370?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-12370: ---------------------------------------- Fix Version/s: 4.2.0.CR1 (was: 4.2.0.Beta3) > Add a video that shows how to handle missing requirements on New Project Example screen > --------------------------------------------------------------------------------------- > > Key: JBIDE-12370 > URL: https://issues.jboss.org/browse/JBIDE-12370 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: project-examples > Affects Versions: 3.3.0.Final > Reporter: Pete Muir > Assignee: Michelle Murray > Priority: Critical > Labels: doc'ed > Fix For: 4.2.0.CR1 > > > If the user clicks on _JBoss Central | Java EE Web Project_ they are presented with this screen http://www.jboss.org/jdf/stage/quickstarts/jboss-as-quickstart/guide//gfx... - it would be nice to have a short video showing how people can solve missing requirements, e.g. by clicking the Install button. This can then be linked to from tutorials that use these wizards. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17010) Hibernate schema update error while deploying Seam Portlet on JPP 6.1.1

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17010?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-17010: --------------------------------------- I can't reproduce the issue using the JBT master. Have you created a Seam project with the New Web Seam Project wizard? > Hibernate schema update error while deploying Seam Portlet on JPP 6.1.1 > ----------------------------------------------------------------------- > > Key: JBIDE-17010 > URL: https://issues.jboss.org/browse/JBIDE-17010 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.2.0.Beta1 > Environment: JPP 6.1.1, Seam 2.3.2, Portlet Bridge 3.2.1, Database: HSQL (DefaultDS) > Reporter: Radoslav Rábara > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > Attachments: jpp611.log > > > There is an error in console output when seam portlet is deployed to JPP 6.1.1. > {code} > ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 84) HHH000299: Could not complete schema update: java.lang.NullPointerException > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16993) quickfixes for the issues arquillian editor finds

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16993?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16993: --------------------------------------- I have moved the quickfix actions to the Problems section. !jbide-16993.png! > quickfixes for the issues arquillian editor finds > ------------------------------------------------- > > Key: JBIDE-16993 > URL: https://issues.jboss.org/browse/JBIDE-16993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: testing-tools > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Fix For: 4.2.0.Beta3 > > Attachments: jbide-16993.png > > > I get a warnings when using the arquillian editor about me missing certain artifacts, missing profiles etc. > Might be because I dont have a pom.xml but could there be some quickfixes are explanation of what the user is expected to do ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 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 July 2014