January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13817) aggregate site build should produce junit test output to confirm if the contents of the zips fetched from the upstream composite site match 100% the contents of the produced aggregate site

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13817?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-13817. ---------------------------------- Resolution: Rejected > aggregate site build should produce junit test output to confirm if the contents of the zips fetched from the upstream composite site match 100% the contents of the produced aggregate site > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13817 > URL: https://issues.jboss.org/browse/JBIDE-13817 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.2.0.Alpha2 > > > The old way to pull zips is with https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... but it is an incomplete solution as it has never verified that the zips were the same content as the aggregate site (they could have changed AFTER the aggregate was built). It also tried to pull the list of zips from a local zip.list.txt file [0] rather than just going right to the composite site. > [0] http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... > The new way should be an *optional* mojo (runs only for aggregate builds, not individual project builds) which: > * reads the upstream composite site [1], and > ** for each child site listed, > *** downloads a zip matching the last CI build for that project > **** IF the contents of that downloaded zip match the IU versions of the aggregate site we just built, then produce a passing JUnit xml report. > **** If the contents differ, return an error report. > Aggregate jobs will therefore need to be updated to look for these JUnit reports, and mark the build UNSTABLE (yellow) if any non-passing results are found. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trunk/, > There is also this file [2] produced by this job [3], which might make things easier: > [2] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/trun... > [3] http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/job... -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16411) Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16411?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-16411: ----------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.CR1) > Add m2eclipse-mavenarchiver 0.16.0 to our TP + requirements > ----------------------------------------------------------- > > Key: JBIDE-16411 > URL: https://issues.jboss.org/browse/JBIDE-16411 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, target-platform > Affects Versions: 4.1.1.Beta1 > Reporter: Fred Bricon > Assignee: Mickael Istria > Priority: Blocker > Labels: jbds711 > Fix For: 4.1.2.CR1, 4.2.0.Alpha2 > > > An unsigned build of m2eclipse-mavenarchiver 0.16.0 is available from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-mavenarchiver/0.1... > An eclipse signed version should be available in the upcoming weeks, as part of the Luna release > Please add it to our TP / Requirements / whatever for JBT 4.1.2. > This builds prevents aggressive pom.xml/pom.properties generation on each incremental build. > This is required to help fix JBIDE-16286 -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2857) Add OS X 10.9 Mavericks to the support matrix

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2857?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2857: --------------------------------------- Burr's comment above and the jbds-pm minutes from 30 jan say 7.1.1 forwards only. Max's comment says 7.x and that's what Nick's added to the JBT configs page. Some one (probably Burr) needs to make a definitive decision about whether we are stating Mavericks support for 7.0.x, 7.1.x or 7.1.1 onwards. I will then update the JBDS configs page as appropriate. > Add OS X 10.9 Mavericks to the support matrix > --------------------------------------------- > > Key: JBDS-2857 > URL: https://issues.jboss.org/browse/JBDS-2857 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 7.1.0.CR1 > Reporter: Martin Malina > Assignee: Len DiMaggio > Fix For: 7.1.1.CR1, 8.0.0.Alpha2 > > > I know this comes very late, so you may want to just push this to 8.0.0 immediately. > However, we've already been testing on Mavericks (I use it every day myself) since it was introduced on October 22, 2013 and have never seen any problem specific to it. > I only realized we still don't have Mavericks in the matrix today when I checked Michelle's Supported Configurations document. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16318) Application wizard: rework page/model setup in ApplicationConfigurationWizardPage

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16318?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-16318. -------------------------------------- Assignee: Andre Dietisheim Resolution: Out of Date this was fixed when doing JBIDE-14002 > Application wizard: rework page/model setup in ApplicationConfigurationWizardPage > --------------------------------------------------------------------------------- > > Key: JBIDE-16318 > URL: https://issues.jboss.org/browse/JBIDE-16318 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: application_wizard > Fix For: 4.2.0.Alpha2 > > > The page/model setup in ApplicationConfigurationWizardPage is messy. > #onPageActivated is called when the page is activated as 1st page of the wizard, but also when we switch from page2 back to this page. This causes resources to get loaded even if we switch from page2 to page1. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2777) Support Team Management operations in openshift UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2777?page=com.atlassian.jira.plugin.... ] Andre Dietisheim edited comment on JBDS-2777 at 1/31/14 7:43 AM: ----------------------------------------------------------------- we agreed in OpenShift sync call that we wont support administering groups, users, ownerships in JBDS/JBT. The administrative options - once configured - should work fully transparently in JBDS/JBT. The only thing we'll possibly provide is decorating the explorer to show if you're the owner of a domain. was (Author: adietish): we agreed in OpenShift sync call that there we wont support administering groups, users, ownerships in JBDS/JBT. The administrative options - once configured - should work fully transparently in JBDS/JBT. The only thing we'll possibly provide is decorating the explorer to show if you're the owner of a domain. > Support Team Management operations in openshift UI > -------------------------------------------------- > > Key: JBDS-2777 > URL: https://issues.jboss.org/browse/JBDS-2777 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Optional > Fix For: 8.0.0.GA > > > OpenShift is providing a team API where teams may be created. Users or groups may get assigned to a team. There's always only 1 group per team and there is no finer-grained role based acl. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2777) Support Team Management operations in openshift UI

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2777?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-2777: ---------------------------------------- we agreed in OpenShift sync call that there we wont support administering groups, users, ownerships in JBDS/JBT. The administrative options - once configured - should work fully transparently in JBDS/JBT. The only thing we'll possibly provide is decorating the explorer to show if you're the owner of a domain. > Support Team Management operations in openshift UI > -------------------------------------------------- > > Key: JBDS-2777 > URL: https://issues.jboss.org/browse/JBDS-2777 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Optional > Fix For: 8.0.0.GA > > > OpenShift is providing a team API where teams may be created. Users or groups may get assigned to a team. There's always only 1 group per team and there is no finer-grained role based acl. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2769) Shortcut for Redo action is missing

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-2769?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-2769: ----------------------------------------- There is nothing wrong with shortcut Shift+Ctrl+Z in Eclipse. The problem is that the shortcut is missing in JBDS. > Shortcut for Redo action is missing > ----------------------------------- > > Key: JBDS-2769 > URL: https://issues.jboss.org/browse/JBDS-2769 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: upstream > Affects Versions: 7.0.0.GA, 7.1.0.Alpha1 > Reporter: Andrej Podhradsky > > By default, there is no shortcut for Redo action like in Eclipse (ShiftCtrl+Z). > I think it would be cool if there is a shortcut for redo by default ;-) -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15107) JBoss EAP 6.1 Server cannot be started with 32-bit JVM on Windows 7

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15107?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-15107: ------------------------------------- We'll need to document the workaround regardless actually. But I think we can change default args based on windows, but Idon't think there's a way to do it based on vm details (ie oracle, 32bit, etc). I don't think there's any easy way to get that information. > JBoss EAP 6.1 Server cannot be started with 32-bit JVM on Windows 7 > ------------------------------------------------------------------- > > Key: JBIDE-15107 > URL: https://issues.jboss.org/browse/JBIDE-15107 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Beta2 > Environment: 64-bit Windows 7 > 32-bit JDK 7u25 > Reporter: Yahor Radtsevich > Assignee: Rob Stryker > Priority: Critical > Labels: jbds711 > Fix For: 4.1.2.CR1, 4.2.0.Alpha2 > > Attachments: screenshot.png > > > I cannot run JBoss EAP 6.1 with its default launch configuration. > The default launch configuration has {{-Xms1303m}} and {{-Xmx1303m}} in its parameters, which is obviously the reason of this bug. > *Steps to reproduce:* > # Install JBDS 7.0.0.Beta2 bundled with JBoss EAP 6.1 Server > # Open JBoss Central and create new HTML5 Project > # Try to run this project on the server > *Actual result:* > Server cannot be started. The following message is shown in the console: > {code:title=console output} > Error occurred during initialization of VM > Could not reserve enough space for object heap > {code} > And this pop-up appears: > !screenshot.png! -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15471) Cannot cancel creating Java EE project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15471?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-15471: ------------------------------------- It seems it will require significant refactoring to be able to implement that feature. Punting to following release for now. > Cannot cancel creating Java EE project > -------------------------------------- > > Key: JBIDE-15471 > URL: https://issues.jboss.org/browse/JBIDE-15471 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Final > Environment: Fedora Gnome 3.4.2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.2.0.Beta1 > > > During creation of new Java EE Web project or Java EE EAR project is impossible to cancel task - cancellation icon is grey and unclickable. If user doesn't have EE runtime it takes significant time to download it etc. -- 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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15471) Cannot cancel creating Java EE project

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15471?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15471: -------------------------------- Fix Version/s: 4.2.0.Beta1 (was: 4.2.0.Alpha2) > Cannot cancel creating Java EE project > -------------------------------------- > > Key: JBIDE-15471 > URL: https://issues.jboss.org/browse/JBIDE-15471 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Final > Environment: Fedora Gnome 3.4.2 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.2.0.Beta1 > > > During creation of new Java EE Web project or Java EE EAR project is impossible to cancel task - cancellation icon is grey and unclickable. If user doesn't have EE runtime it takes significant time to download it etc. -- 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, 2 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 January 2014