September 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18428) Login dialog: get "Unknown error" instead of "Authentication error" when using bad credentials

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-18428: ---------------------------------------- Summary: Login dialog: get "Unknown error" instead of "Authentication error" when using bad credentials Key: JBIDE-18428 URL: https://issues.jboss.org/browse/JBIDE-18428 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Minor -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18427) Markers wizard: ReadMe is listed as marker file

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18427?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18427: ------------------------------------- Attachment: readme-is-a-maker.png > Markers wizard: ReadMe is listed as marker file > ----------------------------------------------- > > Key: JBIDE-18427 > URL: https://issues.jboss.org/browse/JBIDE-18427 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.CR2 > > Attachments: readme-is-a-maker.png > > -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18427) Markers wizard: ReadMe is listed as marker file

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-18427: ---------------------------------------- Summary: Markers wizard: ReadMe is listed as marker file Key: JBIDE-18427 URL: https://issues.jboss.org/browse/JBIDE-18427 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.2.0.CR2 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3129) Verify Eclipse Luna SR1 for JBDS 8.0.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3129?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3129: -------------------------------------- Thanks > Verify Eclipse Luna SR1 for JBDS 8.0.0 > -------------------------------------- > > Key: JBDS-3129 > URL: https://issues.jboss.org/browse/JBDS-3129 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: upstream > Reporter: Mickael Istria > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.0.0.CR2 > > Attachments: install_1.png, install_2.png, install_3.png, install_4.png > > > Luna SR1 is to be available on Sept 26th (and ready on Sept 21st): https://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#SR1 > We need to use if for JBDS 8.0 (cf JBIDE-18182). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3129) Verify Eclipse Luna SR1 for JBDS 8.0.0

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3129?page=com.atlassian.jira.plugin.... ] Len DiMaggio resolved JBDS-3129. -------------------------------- Resolution: Done > Verify Eclipse Luna SR1 for JBDS 8.0.0 > -------------------------------------- > > Key: JBDS-3129 > URL: https://issues.jboss.org/browse/JBDS-3129 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: upstream > Reporter: Mickael Istria > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.0.0.CR2 > > Attachments: install_1.png, install_2.png, install_3.png, install_4.png > > > Luna SR1 is to be available on Sept 26th (and ready on Sept 21st): https://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#SR1 > We need to use if for JBDS 8.0 (cf JBIDE-18182). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3129) Verify Eclipse Luna SR1 for JBDS 8.0.0

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3129?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3129: ------------------------------------ Also tried: https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/205/artifac... Looks good to go. > Verify Eclipse Luna SR1 for JBDS 8.0.0 > -------------------------------------- > > Key: JBDS-3129 > URL: https://issues.jboss.org/browse/JBDS-3129 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: upstream > Reporter: Mickael Istria > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.0.0.CR2 > > Attachments: install_1.png, install_2.png, install_3.png, install_4.png > > > Luna SR1 is to be available on Sept 26th (and ready on Sept 21st): https://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#SR1 > We need to use if for JBDS 8.0 (cf JBIDE-18182). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3129) Verify Eclipse Luna SR1 for JBDS 8.0.0

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBDS-3129?page=com.atlassian.jira.plugin.... ] Martin Malina commented on JBDS-3129: ------------------------------------- I downloaded Eclipse for Java EE Luna SR1 RC4 from https://hudson.eclipse.org/packaging/job/luna.epp-tycho-build/205/artifac... Then installed JBDS 8.0.0.CR1 BYOE from Eclipse Marketplace. It installed fine, I didn't spot any errors and I was able to deploy the html5 project from central to eap 6.3. So it looks ok. > Verify Eclipse Luna SR1 for JBDS 8.0.0 > -------------------------------------- > > Key: JBDS-3129 > URL: https://issues.jboss.org/browse/JBDS-3129 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Sub-task > Components: upstream > Reporter: Mickael Istria > Assignee: Len DiMaggio > Priority: Blocker > Fix For: 8.0.0.CR2 > > Attachments: install_1.png, install_2.png, install_3.png, install_4.png > > > Luna SR1 is to be available on Sept 26th (and ready on Sept 21st): https://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#SR1 > We need to use if for JBDS 8.0 (cf JBIDE-18182). -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18239) Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18239?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18239: ---------------------------------------- [~nickboldt]: * I tried them, Tycho validation and mirror mojo support 0.0.0 fine. If for some reason there is a bug I didn't see, then we can fix those mojos * I believe [~maxandersen] is even in favour of totally removing any org.jboss.tools content from target definition. [~maxandersen] * I agree with [~nickboldt] main concern: what about content that is available in JBT aggregate and JBDS central, but not in JBDS main site? Do we want to allow that? If we simply say that such content should always go in JBDS main site, then things are easier. We just need to be sure we're ok with that. > Create new update site zip(s) (rather than target platform zip) for JBT content needed for Central/EA site > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18239 > URL: https://issues.jboss.org/browse/JBIDE-18239 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central, discovery, updatesite > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Labels: f2f2014 > Fix For: 4.3.0.Alpha1 > > Attachments: JBIDE18239-proposed.png > > > In order to simplify the process for getting JBT features into Central (for JBDS) and EA (for both JBT/JBDS), it's been suggested (by [~maxandersen], who doesn't like opening JIRAs :D) that instead of a target platform which needs to be updated every time we spin or respin a build, we could instead just produce an update site containing the handful of IUs (cordovasim, arquillian, etc.). > We could further extend this idea to include all the things that currently are in BOTH JBT or JBDS and in Central, such as TestNG. > These would be produced as new zips using the JBT aggregate builder: > https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/ > Need to decide what to call this... "Extras" "JBT-not-in-JBDS" "Shared" ...? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18422) Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18422?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-18422: -------------------------------------- Just to confirm - are there zero user doc changes needed for this? Thx! > Include latest Tern & AngularJS 0.6.0.20140923161* into jbosstools/jbds TPs AND Early Access too > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-18422 > URL: https://issues.jboss.org/browse/JBIDE-18422 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Affects Versions: 4.2.0.CR1 > Reporter: Victor Rubezhny > Assignee: Denis Golovin > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.2.0.CR2 > > > In JBIDE-18273, the JBT/JBDS target platforms were updated to include the latest Tern 0.6.0.201409041810-SNAPSHOT, but the version of AngularJS included in the Early Access site remained at 0.5.0.201408281218. Since these traditionally have been updated IN PARALLEL at the same time, it seems we need a new version of AngularJS in the EA site. > However, since the latest AngularJS is now 0.6.0.201409231617, maybe we want to pull the latest Tern 0.6.0.201409231610 too, instead of the 2014/09/04 version? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17940) JPA Details view doesn't work for entities in autodiscovery mode when they are not explicitely listed

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17940?page=com.atlassian.jira.plugi... ] Koen Aers commented on JBIDE-17940: ----------------------------------- The behavior of the JPA details view is the same for the Generic platform as for the Hibernate platform: the details only show up after clicking in the editor. I would expect that the details view is populated as soon as the editor opens. I have a feeling this is an upstream problem but it needs more investigation. Also, afaics there is no difference between the auto discovery mode and when the entities are listed in the persistence.xml: in both cases the details view is only populated after clicking in the open editor. The behavior of the JPA structure view is different. With the generic platform the entities are recognized as JPA entities and the JPA structure view populates (even without clicking in the editor). With the Hibernate platform this doesn't happen (not even when clicking in the editor). So in this last case, I have the impression that it is a problem of the Hibernate platform implementation. > JPA Details view doesn't work for entities in autodiscovery mode when they are not explicitely listed > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-17940 > URL: https://issues.jboss.org/browse/JBIDE-17940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate, upstream > Affects Versions: 4.2.0.Beta3 > Environment: JBDS 8.0.0.Beta3, GNU/Linux 64 > Reporter: Jiri Peterka > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.CR2 > > > JPA Details view is not working for entities in autodiscovery mode. It only works when entities are added into Managed Classes entities list. It's expected when JPA project is configured with "Discover annotated classes automatically" it should without manual listing entities in persistence.xml. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 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 2014