April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19534) fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19534?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19534: ---------------------------------------- Assignee: Andre Dietisheim Resolution: Done merged and pushed to upstream/master > fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui > ------------------------------------------------------------------------- > > Key: JBIDE-19534 > URL: https://issues.jboss.org/browse/JBIDE-19534 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > When launching the OpenShift tooling there is currently the following log output which talks of missing messages in org.jboss.tools.openshift.internal.common.ui: > {code} > Warning: NLS missing message: EditorSectionDomainNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EditorSectionAppNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EditorSectionOutputDestLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EnterDomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainNameMayHaveLettersAndDigits in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainNameMaximumLength in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DeletingOpenShiftApplications in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DeletingApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: FailedToDeleteApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseCreateDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseSelectDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseSelectApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseCreateApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > {code} > These are most likely erroneous message keys that made it into common.ui when the CommonUIMessages class was copied from org.jboss.tools.openshift.express.ui > org.jboss.tools.openshift.express.ui also has 2 message classes: > * org.jboss.tools.openshift.express.internal.ui.ExpressUIMessages > * org.jboss.tools.openshift.express.internal.ui.messages.ExpressUIMessages -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19534) fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19534?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19534. ------------------------------------ nothing for QE to verify, closing. > fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui > ------------------------------------------------------------------------- > > Key: JBIDE-19534 > URL: https://issues.jboss.org/browse/JBIDE-19534 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > When launching the OpenShift tooling there is currently the following log output which talks of missing messages in org.jboss.tools.openshift.internal.common.ui: > {code} > Warning: NLS missing message: EditorSectionDomainNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EditorSectionAppNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EditorSectionOutputDestLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EnterDomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainNameMayHaveLettersAndDigits in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainNameMaximumLength in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DeletingOpenShiftApplications in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DeletingApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: FailedToDeleteApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseCreateDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseSelectDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseSelectApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseCreateApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > {code} > These are most likely erroneous message keys that made it into common.ui when the CommonUIMessages class was copied from org.jboss.tools.openshift.express.ui > org.jboss.tools.openshift.express.ui also has 2 message classes: > * org.jboss.tools.openshift.express.internal.ui.ExpressUIMessages > * org.jboss.tools.openshift.express.internal.ui.messages.ExpressUIMessages -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19534) fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19534?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19534: ------------------------------------------ The message class obviously was copied over from org.jboss.tools.openshift.express.ui while keeping the keys. I'll remove what's not being used. > fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui > ------------------------------------------------------------------------- > > Key: JBIDE-19534 > URL: https://issues.jboss.org/browse/JBIDE-19534 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > When launching the OpenShift tooling there is currently the following log output which talks of missing messages in org.jboss.tools.openshift.internal.common.ui: > {code} > Warning: NLS missing message: EditorSectionDomainNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EditorSectionAppNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EditorSectionOutputDestLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EnterDomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainNameMayHaveLettersAndDigits in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainNameMaximumLength in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DeletingOpenShiftApplications in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DeletingApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: FailedToDeleteApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseCreateDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseSelectDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseSelectApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseCreateApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > {code} > These are most likely erroneous message keys that made it into common.ui when the CommonUIMessages class was copied from org.jboss.tools.openshift.express.ui > org.jboss.tools.openshift.express.ui also has 2 message classes: > * org.jboss.tools.openshift.express.internal.ui.ExpressUIMessages > * org.jboss.tools.openshift.express.internal.ui.messages.ExpressUIMessages -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-15714: ------------------------------------------------ {quote}So just to play devils advocate here - if we force refresh on the preview browser, why do have a button to disable refresh on the visual/source part ? shouldn't that button affect both ? {quote} It shouldn't. There is nothing to disable for Preview tab. Preview tab's purpose is to show the editor content visual representation, provide ability to fill in the forms, click to links, etc. Preview tab content always been refreshed on its activation to show latest changes in the source. Visual/Source tab purpose is to provide communication between visual and source parts, see visual representation of changes user made without switching to another tab. If you don't want to see preview update on each change in editor - choose refresh-on-save or do refreshes manually. > Dynamic content assist for AngularJS expressions in html files > -------------------------------------------------------------- > > Key: JBIDE-15714 > URL: https://issues.jboss.org/browse/JBIDE-15714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: Diagram.gliffy, vpe.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3276) JBDS-IS Installer

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3276?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3276: ------------------------------------------- These are looking really good - do you have a screenshot of how the page will look like ? about where to put the installer i'm wonderig if we shouldn't just do it inside devstudio installer and have it as another variant of the installer ? anything for/against that ? > JBDS-IS Installer > ----------------- > > Key: JBDS-3276 > URL: https://issues.jboss.org/browse/JBDS-3276 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer, integration-platform, requirements > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Denis Golovin > > As a Fuse, integration-focused developer, I need a downloadable installer that will allow me to quickly and easily install JBDS with Fuse capabilities. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19534) fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19534?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19534: ------------------------------------- Description: When launching the OpenShift tooling there is currently the following log output which talks of missing messages in org.jboss.tools.openshift.internal.common.ui: {code} Warning: NLS missing message: EditorSectionDomainNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: EditorSectionAppNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: EditorSectionOutputDestLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: EnterDomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DomainNameMayHaveLettersAndDigits in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DomainNameMaximumLength in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DeletingOpenShiftApplications in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DeletingApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: FailedToDeleteApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseCreateDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseSelectDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseSelectApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseCreateApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages {code} These are most likely erroneous message keys that made it into common.ui when the CommonUIMessages class was copied from org.jboss.tools.openshift.express.ui org.jboss.tools.openshift.express.ui also has 2 message classes: * org.jboss.tools.openshift.express.internal.ui.ExpressUIMessages * org.jboss.tools.openshift.express.internal.ui.messages.ExpressUIMessages was: When launching the OpenShift tooling there is currently the following log output which talks of missing messages in org.jboss.tools.openshift.internal.common.ui: {code} Warning: NLS missing message: EditorSectionDomainNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: EditorSectionAppNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: EditorSectionOutputDestLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: EnterDomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DomainNameMayHaveLettersAndDigits in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DomainNameMaximumLength in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DeletingOpenShiftApplications in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: DeletingApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: FailedToDeleteApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseCreateDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseSelectDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseSelectApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages Warning: NLS missing message: OpenShiftServerWizardPleaseCreateApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages {code} These are most likely erroneous message keys that made it into common.ui when the CommonUIMessages class was copied from org.jboss.tools.openshift.express.ui > fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui > ------------------------------------------------------------------------- > > Key: JBIDE-19534 > URL: https://issues.jboss.org/browse/JBIDE-19534 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > When launching the OpenShift tooling there is currently the following log output which talks of missing messages in org.jboss.tools.openshift.internal.common.ui: > {code} > Warning: NLS missing message: EditorSectionDomainNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EditorSectionAppNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EditorSectionOutputDestLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EnterDomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainNameMayHaveLettersAndDigits in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainNameMaximumLength in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DeletingOpenShiftApplications in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DeletingApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: FailedToDeleteApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseCreateDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseSelectDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseSelectApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseCreateApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > {code} > These are most likely erroneous message keys that made it into common.ui when the CommonUIMessages class was copied from org.jboss.tools.openshift.express.ui > org.jboss.tools.openshift.express.ui also has 2 message classes: > * org.jboss.tools.openshift.express.internal.ui.ExpressUIMessages > * org.jboss.tools.openshift.express.internal.ui.messages.ExpressUIMessages -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19546) Unhandled event loop exception when downloading Android engine

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19546?page=com.atlassian.jira.plugi... ] Gorkem Ercan updated JBIDE-19546: --------------------------------- Fix Version/s: 4.3.0.Alpha2 > Unhandled event loop exception when downloading Android engine > -------------------------------------------------------------- > > Key: JBIDE-19546 > URL: https://issues.jboss.org/browse/JBIDE-19546 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.0.Alpha1 > Environment: Win 7, thym 0.2.0 > Reporter: Konstantin Marmalyukov > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > It smells like jface bug, but anyway it will be good to handle this exception -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts

by Arun Gupta (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ] Arun Gupta commented on JBIDE-19507: ------------------------------------ +1, very nicely described and this will make our tooling compelling. > Search and rename participants for Batch Artifacts > -------------------------------------------------- > > Key: JBIDE-19507 > URL: https://issues.jboss.org/browse/JBIDE-19507 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, PropertyRename.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png > > > *Search Participant* > 1. Should be able to find references in job.xml files for Batch Artifact Class IType > Example: > During the search for references for class "SearchableBatchlet" like: > {code} > package batch; > import javax.batch.api.BatchProperty; > import javax.batch.api.Batchlet; > import javax.inject.Inject; > import javax.inject.Named; > @Named > public class SearchableBatchlet implements Batchlet { > > @Inject @BatchProperty(name="secondName") String otherName; > @Override > public String process() throws Exception { > return null; > } > @Override > public void stop() throws Exception { > } > } > {code} > In the search result should be added references in jbob.xml files like this: > !SearchableBatchletReferences.png! > 2. Should be able to find references in job.xml files for Batch Artifact Property IField > Example: > During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this: > !FieldReference.png! > 3. Should be able to find references in job.xml files for Exception Class IType > Example: > During the search for references for class "SearchableException" like: > {code} > package batch; > public class SearchableException extends Exception{ > private static final long serialVersionUID = 1L; > } > {code} > In the search result should be added references in jbob.xml files like this: > !SearchableExceptionReferences.png! > *Rename Participant* > 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files. > Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named > Example: > During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring: > !BatchArtifactRename.png! > 2. Should be able to add changes in Batch Property Rename for references in job.xml files. > Note: Rename Participant does make sense only for Batch Properties which name comes from Java Field Name, not from annotation @BatchProperty > Example: > {code} > package batch; > import javax.batch.api.BatchProperty; > import javax.batch.api.Batchlet; > import javax.inject.Inject; > import javax.inject.Named; > @Named > public class RenamablePropertyBatchlet implements Batchlet { > > @Inject @BatchProperty String otherName; > @Override > public String process() throws Exception { > return null; > } > @Override > public void stop() throws Exception { > } > } > {code} > During rename of field "otherName" changes for job.xml references should be added in Refactoring: > !PropertyRename.png! > 3. Should be able to add changes in Exception Class Rename for references in job.xml files. > Example: > During rename of class "SearchableException" changes for job.xml references should be added in Refactoring: > !ExceptionRename.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3384: ------------------------------------------- [~rob.stryker] can you work with [~mickael_istria] and [~dgolovin] to make sure our Mars M6 and Devstudio installer actually have the right things needed for users to have the nice terminal (for alpha2) and preferably remove any non-used terminal UI (this could be done post-alpha2) > Investigate how the terminal changes in Mars will/should affect us > ------------------------------------------------------------------- > > Key: JBDS-3384 > URL: https://issues.jboss.org/browse/JBDS-3384 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, forge, openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 9.0.0.Alpha2 > > > Terminal (console) support in eclipse mars is changing and we should > make sure we adjust for it. > Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html > Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now. > This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new. > As we find what it entails we should link those issues to this jira. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3384) Investigate how the terminal changes in Mars will/should affect us

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3384?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3384: -------------------------------------- Fix Version/s: 9.0.0.Alpha2 > Investigate how the terminal changes in Mars will/should affect us > ------------------------------------------------------------------- > > Key: JBDS-3384 > URL: https://issues.jboss.org/browse/JBDS-3384 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: build, forge, openshift > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Blocker > Fix For: 9.0.0.Alpha2 > > > Terminal (console) support in eclipse mars is changing and we should > make sure we adjust for it. > Some changes this is doing at eclipse is documented at https://dev.eclipse.org/mhonarc/lists/epp-dev/msg03448.html > Hopefully this can be used to remove redundant/duplicate terminals and just have *one* instead of the 2.5 we got now. > This *probably* going to affect not only packaging of JBDS (remove old terminals, add the new one), but Forge ([~koen.aers]) probably could benefit from this and Fuse ([~lhein]) should stop extending the old terminals and use the new. > As we find what it entails we should link those issues to this jira. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-624) JBDS-IS 8.0.1: Update Install Document

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-624?page=com.atlassian.jira.plug... ] Supriya Bharadwaj commented on TOOLSDOC-624: -------------------------------------------- > Tested the steps > 5. Install JBoss Developer Studio Integration Stack in JBoss Developer Studio when Online: Added an admonition for the prerequisite > 6. Install JBoss Developer Studio Integration Stack in JBoss Developer Studio when Offline: Added an admonition for the prerequisite > 3. Install JBoss Developer Studio Integration Stack in Eclipse when Online: Added info for the categories that the user will select (I am not sure if this was required to be added; I did it anyway because I felt it was only apt to have it here) > 4. Install JBoss Developer Studio Integration Stack in Eclipse when Offline: Added info for the categories that the user will select > 5. Install JBoss Developer Studio Integration Stack in JBoss Developer Studio when Online (I am not sure if this was required to be added; I did it anyway because I felt it was only apt to have it here) > 6. Install JBoss Developer Studio Integration Stack in JBoss Developer Studio when Offline: Added info for the categories that the user will select > JBDS-IS 8.0.1: Update Install Document > --------------------------------------- > > Key: TOOLSDOC-624 > URL: https://issues.jboss.org/browse/TOOLSDOC-624 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Supriya Bharadwaj > > 1. Installation Guide - in Fuse, we have our own Fuse Tooling Installation Guide. After comparing the content of the two installation guides, I don't have objections to getting rid of ours and reusing the one from JBDS IS. But: > a) the guide should include (a link to) JBDS installation instructions; this information is currently missing and imo is very important in the isolated context of individual products' docs suites. Update: Four installation instructions are provided in the Install Guide at the moment. The first two are for installing JBDS, the latter two are for JBDS-IS. The latter two should have a prerequisite step that tells you to install JBDS and links to the relevant topics (the first two ways to install). > b) the "From the table of categories, select the JBoss Developer Studio Integration Stack functionality you want to install and click Next." step of each procedure should be expanded with specific instructions for individual products, i.e. what components of the IS to install for Fuse, DV and B*MS -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3188) Support of krb5-principal keys in openshift-java-client (eclipse)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3188?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3188: ------------------------------------------- [~adietish] this seem misassigned to me. Was there something I needed to do on it ? we should get the need for this figured our fo OSv3 at least. > Support of krb5-principal keys in openshift-java-client (eclipse) > ------------------------------------------------------------------ > > Key: JBDS-3188 > URL: https://issues.jboss.org/browse/JBDS-3188 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.x > Reporter: Christos Triantafyllidis > Assignee: Andre Dietisheim > > The openshift-java-client which is used by the eclipse plugin doesn't support this krb5-principal keys. > This request is to be able to clone/pull/push updates to openshift application repositories when krb5 credentials are already available and the openshift broker supports krb5 authentication. > https://github.com/openshift/openshift-java-client/blob/master/src/main/j... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3188) Support of krb5-principal keys in openshift-java-client (eclipse)

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3188?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen reassigned JBDS-3188: ----------------------------------------- Assignee: Andre Dietisheim (was: Max Rydahl Andersen) > Support of krb5-principal keys in openshift-java-client (eclipse) > ------------------------------------------------------------------ > > Key: JBDS-3188 > URL: https://issues.jboss.org/browse/JBDS-3188 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: openshift > Affects Versions: 8.x > Reporter: Christos Triantafyllidis > Assignee: Andre Dietisheim > > The openshift-java-client which is used by the eclipse plugin doesn't support this krb5-principal keys. > This request is to be able to clone/pull/push updates to openshift application repositories when krb5 credentials are already available and the openshift broker supports krb5 authentication. > https://github.com/openshift/openshift-java-client/blob/master/src/main/j... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19331) Links to JBDS release notes broken

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19331?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19331: ---------------------------------------- Fix Version/s: 4.2.1.Final > Links to JBDS release notes broken > ---------------------------------- > > Key: JBIDE-19331 > URL: https://issues.jboss.org/browse/JBIDE-19331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Affects Versions: 4.2.2.Final > Reporter: Martin Malina > Assignee: Max Rydahl Andersen > Fix For: 4.2.1.Final > > > This page has a link to release notes which is broken: > http://tools.jboss.org/downloads/devstudio/luna/8.0.2.GA.html > It points to https://access.redhat.com/site/documentation/en-US/Red_Hat_JBoss_Develope... > The same problem happens for JBDS 8.0.1 and 8.0.0. > The correct link is e.g.: > https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... > So it seems we just need to trim off the trailing index.html . -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19534) fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19534?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19534: ------------------------------------- Fix Version/s: 4.3.0.Alpha2 > fix missing messages/keys in org.jboss.tools.openshift.internal.common.ui > ------------------------------------------------------------------------- > > Key: JBIDE-19534 > URL: https://issues.jboss.org/browse/JBIDE-19534 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Alpha2 > > > When launching the OpenShift tooling there is currently the following log output which talks of missing messages in org.jboss.tools.openshift.internal.common.ui: > {code} > Warning: NLS missing message: EditorSectionDomainNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EditorSectionAppNameLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EditorSectionOutputDestLabel in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: EnterDomainName in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainNameMayHaveLettersAndDigits in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DomainNameMaximumLength in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DeletingOpenShiftApplications in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: DeletingApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: FailedToDeleteApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseCreateDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseSelectDomain in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseSelectApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > Warning: NLS missing message: OpenShiftServerWizardPleaseCreateApplication in: org.jboss.tools.openshift.internal.common.ui.CommonUIMessages > {code} > These are most likely erroneous message keys that made it into common.ui when the CommonUIMessages class was copied from org.jboss.tools.openshift.express.ui -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19575) Update openshift v3 tools to support deprecation of com.openshift.client

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19575?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19575. ------------------------------------ nothing for QE to verify, closing. > Update openshift v3 tools to support deprecation of com.openshift.client > ------------------------------------------------------------------------ > > Key: JBIDE-19575 > URL: https://issues.jboss.org/browse/JBIDE-19575 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19575) Update openshift v3 tools to support deprecation of com.openshift.client

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19575?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19575: ------------------------------------- Fix Version/s: 4.3.0.Alpha2 > Update openshift v3 tools to support deprecation of com.openshift.client > ------------------------------------------------------------------------ > > Key: JBIDE-19575 > URL: https://issues.jboss.org/browse/JBIDE-19575 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19575) Update openshift v3 tools to support deprecation of com.openshift.client

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19575?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19575: ------------------------------------- Affects Version/s: 4.3.0.Alpha2 (was: 4.3.x) > Update openshift v3 tools to support deprecation of com.openshift.client > ------------------------------------------------------------------------ > > Key: JBIDE-19575 > URL: https://issues.jboss.org/browse/JBIDE-19575 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19575) Update openshift v3 tools to support deprecation of com.openshift.client

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19575?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19575: ------------------------------------------ Thanks! also removed all access restrictions for the client plugin (internal markers with x-friends) so that 3rd party Eclipse plugins can use the client plugin. > Update openshift v3 tools to support deprecation of com.openshift.client > ------------------------------------------------------------------------ > > Key: JBIDE-19575 > URL: https://issues.jboss.org/browse/JBIDE-19575 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19410: ---------------------------------------- The check for early access makes that we use p2 immediately when showing Central, that's why it logs early. We do need to log it for our dev to understand something is wrong when they'll notice Central isn't behaving as expected and to be able to find the workaround (ticking "Support Software Installation" checkbox) by themselves). Otherwise, we'll just get dozens of IRC interruptions saying "Hey, my appl doesn't show Early-Access things are installed and there is nothing in log". > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19410: --------------------------------------------- "Profile id SELF is not registered" is not anything anyone outside p2 masterminds would grok what is missing. Why not just report as is "p2 installation and update not enabled for this product." and then leave the meaningless for most other as details in the error log ? Even better, dont log it. P2 does not log this either before its actually tried to be used. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3252) JBoss Modules support

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3252?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3252: -------------------------------------- Component/s: requirements > JBoss Modules support > --------------------- > > Key: JBDS-3252 > URL: https://issues.jboss.org/browse/JBDS-3252 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: requirements, server > Reporter: Max Rydahl Andersen > > JBoss Modules - Generic project creation, deployment/publish > JBoss Modules - JDBC Driver > JBoss Profile/Prov. of layered products > JBoss Profile/Provisioning Tool for EAP CRUD Modules of an EAP -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19507: --------------------------------------------- very nice description and looks like a great feature /cc [~ArunGupta] > Search and rename participants for Batch Artifacts > -------------------------------------------------- > > Key: JBIDE-19507 > URL: https://issues.jboss.org/browse/JBIDE-19507 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, PropertyRename.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png > > > *Search Participant* > 1. Should be able to find references in job.xml files for Batch Artifact Class IType > Example: > During the search for references for class "SearchableBatchlet" like: > {code} > package batch; > import javax.batch.api.BatchProperty; > import javax.batch.api.Batchlet; > import javax.inject.Inject; > import javax.inject.Named; > @Named > public class SearchableBatchlet implements Batchlet { > > @Inject @BatchProperty(name="secondName") String otherName; > @Override > public String process() throws Exception { > return null; > } > @Override > public void stop() throws Exception { > } > } > {code} > In the search result should be added references in jbob.xml files like this: > !SearchableBatchletReferences.png! > 2. Should be able to find references in job.xml files for Batch Artifact Property IField > Example: > During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this: > !FieldReference.png! > 3. Should be able to find references in job.xml files for Exception Class IType > Example: > During the search for references for class "SearchableException" like: > {code} > package batch; > public class SearchableException extends Exception{ > private static final long serialVersionUID = 1L; > } > {code} > In the search result should be added references in jbob.xml files like this: > !SearchableExceptionReferences.png! > *Rename Participant* > 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files. > Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named > Example: > During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring: > !BatchArtifactRename.png! > 2. Should be able to add changes in Batch Property Rename for references in job.xml files. > Note: Rename Participant does make sense only for Batch Properties which name comes from Java Field Name, not from annotation @BatchProperty > Example: > {code} > package batch; > import javax.batch.api.BatchProperty; > import javax.batch.api.Batchlet; > import javax.inject.Inject; > import javax.inject.Named; > @Named > public class RenamablePropertyBatchlet implements Batchlet { > > @Inject @BatchProperty String otherName; > @Override > public String process() throws Exception { > return null; > } > @Override > public void stop() throws Exception { > } > } > {code} > During rename of field "otherName" changes for job.xml references should be added in Refactoring: > !PropertyRename.png! > 3. Should be able to add changes in Exception Class Rename for references in job.xml files. > Example: > During rename of class "SearchableException" changes for job.xml references should be added in Refactoring: > !ExceptionRename.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3394: ------------------------------------------- for some reason this had empty release - now fixed so the CDW kicks in. > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3394: -------------------------------- > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3394: -------------------------------------- Target Release: 9.0.0.GA > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3394: ----------------------------- CDW pm_ack: ? CDW release: ? > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-627) QE Review: JBDS-IS Supported Config Updates

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-627?page=com.atlassian.jira.plug... ] Andrej Podhradsky resolved TOOLSDOC-627. ---------------------------------------- Resolution: Done Now, it looks good > QE Review: JBDS-IS Supported Config Updates > ------------------------------------------- > > Key: TOOLSDOC-627 > URL: https://issues.jboss.org/browse/TOOLSDOC-627 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: General documentation issues > Reporter: Misha Ali > Assignee: Andrej Podhradsky > > Andrej, please have a look at the updated components list in the supported config document here: > https://access.redhat.com/node/1351903/draft > The change is a new row added for 8.0.1 in the components list. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (LOCUS-39) Consider using Eclipse Bundle Recipes (EBR)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/LOCUS-39?page=com.atlassian.jira.plugin.s... ] Mickael Istria updated LOCUS-39: -------------------------------- Description: I've had the opportunity to attend a presentation about EBR, a technology to turn plain jars from Maven as OSGi bunle (generating MANIFEST, source bundle, p2 metadata...). I have the impression that it fits quite nicely most of our Locus bundles, we should consider adopting it. More background about EBR: * http://www.eclipse.org/ebr * http://de.slideshare.net/guw/tasty-recipes-for-osgi-bundles was:I've had the opportunity to attend a presentation about EBR, a technology to turn plain jars from Maven as OSGi bunle (generating MANIFEST, source bundle, p2 metadata...). I habe the impression that it fits quite nicely most of our Locus bundles, we should consider adopting it. > Consider using Eclipse Bundle Recipes (EBR) > ------------------------------------------- > > Key: LOCUS-39 > URL: https://issues.jboss.org/browse/LOCUS-39 > Project: JBoss Tools Locus > Issue Type: Enhancement > Reporter: Mickael Istria > > I've had the opportunity to attend a presentation about EBR, a technology to turn plain jars from Maven as OSGi bunle (generating MANIFEST, source bundle, p2 metadata...). I have the impression that it fits quite nicely most of our Locus bundles, we should consider adopting it. > More background about EBR: > * http://www.eclipse.org/ebr > * http://de.slideshare.net/guw/tasty-recipes-for-osgi-bundles -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19570) Arquillian icon is missing in JBDS 8.1.0 Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19570?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19570: ----------------------------------- Fix Version/s: 4.2.3.Final > Arquillian icon is missing in JBDS 8.1.0 Central > ------------------------------------------------ > > Key: JBIDE-19570 > URL: https://issues.jboss.org/browse/JBIDE-19570 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.2.3.Final > Reporter: Len DiMaggio > Assignee: Mickael Istria > Fix For: 4.2.3.Final > > Attachments: JBDS_810_GA.png > > > See attached screenshot -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15714: --------------------------------------------- So just to play devils advocate here - if we force refresh on the preview browser, why do have a button to disable refresh on the visual/source part ? shouldn't that button affect both ? > Dynamic content assist for AngularJS expressions in html files > -------------------------------------------------------------- > > Key: JBIDE-15714 > URL: https://issues.jboss.org/browse/JBIDE-15714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: Diagram.gliffy, vpe.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-627) QE Review: JBDS-IS Supported Config Updates

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-627?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-627: ------------------------------------ Fixed here, [~apodhrad]: https://access.redhat.com/node/1351903/draft Any other changes or are you happy to ACK this? > QE Review: JBDS-IS Supported Config Updates > ------------------------------------------- > > Key: TOOLSDOC-627 > URL: https://issues.jboss.org/browse/TOOLSDOC-627 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: General documentation issues > Reporter: Misha Ali > Assignee: Andrej Podhradsky > > Andrej, please have a look at the updated components list in the supported config document here: > https://access.redhat.com/node/1351903/draft > The change is a new row added for 8.0.1 in the components list. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-627) QE Review: JBDS-IS Supported Config Updates

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-627?page=com.atlassian.jira.plug... ] Andrej Podhradsky commented on TOOLSDOC-627: -------------------------------------------- Release components in 8.0.1: BPMN2 Modeler 1.1.2.Final (instead of 1.1.2.Final_1.1.0.Final_luna) And one small correction in the first section: "Suport Iiformation ..." I think it should be "Support information ..." > QE Review: JBDS-IS Supported Config Updates > ------------------------------------------- > > Key: TOOLSDOC-627 > URL: https://issues.jboss.org/browse/TOOLSDOC-627 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: General documentation issues > Reporter: Misha Ali > Assignee: Andrej Podhradsky > > Andrej, please have a look at the updated components list in the supported config document here: > https://access.redhat.com/node/1351903/draft > The change is a new row added for 8.0.1 in the components list. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-581) MobileDev How To: Import FH project

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-581?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-581: ------------------------------- Security: (was: Red Hat Internal) > MobileDev How To: Import FH project > ----------------------------------- > > Key: TOOLSDOC-581 > URL: https://issues.jboss.org/browse/TOOLSDOC-581 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: User Guide > Affects Versions: 4.2.3.Final > Reporter: Michelle Murray > Assignee: Supriya Bharadwaj > Fix For: 4.2.3.CR1 > > > See https://issues.jboss.org/browse/JBDS-3287 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19567) Thym doesn't support JGit 4.0

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19567?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19567: ---------------------------------------- Newer Thym is mirrored at http://download.jboss.org/jbosstools/updates/requirements/thym/0.2.0-SNAP... I'm not sure I fully understand how updating a Thym version should work now that it's moved out of .target file. Do you know what's to update? > Thym doesn't support JGit 4.0 > ----------------------------- > > Key: JBIDE-19567 > URL: https://issues.jboss.org/browse/JBIDE-19567 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Reporter: Mickael Istria > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Thym cannot be installed/resolved against a Mars M6 target-platform, because JGit moved to version 4.0, and Thym doesn't allow that yet. > {code}[INFO] [ERROR] Cannot resolve project dependencies: > [INFO] [ERROR] Software being installed: org.jboss.tools.aerogear.thym 1.3.0.qualifier > [INFO] [ERROR] Missing requirement: org.eclipse.thym.core 0.1.0.201503051642 requires 'bundle org.eclipse.jgit [3.0.0,4.0.0)' but it could not be found > [INFO] [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.thym 1.3.0.qualifier depends on: bundle org.eclipse.thym.core 0.1.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-423: ------------------------------------ Description: When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log {code} Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar {code} was: When we try to install to install JBDS-IS 8.0.1.GA from JBoss Central we cann see the following error in Error Log {code} Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' > --------------------------------------------------------------------------------- > > Key: JBTIS-423 > URL: https://issues.jboss.org/browse/JBTIS-423 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Environment: JBDS 8.1.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > > When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log > {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: > com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, > com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19410: ---------------------------------------- Since the use-case for it is only the dev-mode, I believe it's more efficient to show technical error messages at that time, so contributor writing code against JBT would more quickly understand what's missing. So I'm for keeping those messages as it. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-627) QE Review: JBDS-IS Supported Config Updates

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-627: ---------------------------------- Summary: QE Review: JBDS-IS Supported Config Updates Key: TOOLSDOC-627 URL: https://issues.jboss.org/browse/TOOLSDOC-627 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Sub-task Components: General documentation issues Reporter: Misha Ali Assignee: Andrej Podhradsky Andrej, please have a look at the updated components list in the supported config document here: https://access.redhat.com/node/1351903/draft The change is a new row added for 8.0.1 in the components list. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-626) JBDS-IS 8.0.1: Update supported configuration document

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-626?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-626: ------------------------------------ Updated doc draft by adding a row of components for 8.0.1: https://access.redhat.com/node/1351903/draft Flagging Andrej for review. > JBDS-IS 8.0.1: Update supported configuration document > ------------------------------------------------------ > > Key: TOOLSDOC-626 > URL: https://issues.jboss.org/browse/TOOLSDOC-626 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Update supported configuration page here: https://access.redhat.com/articles/1351903 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19389) Cannot set timeout configuration to connect JDV server on Teiid designer

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19389?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19389: ------------------------------------- [~blafond] Can you re-assign this issue unless ASTools is missing API or the current API is insufficient? > Cannot set timeout configuration to connect JDV server on Teiid designer > ------------------------------------------------------------------------ > > Key: JBIDE-19389 > URL: https://issues.jboss.org/browse/JBIDE-19389 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Reporter: Eiichi Nagai > Assignee: Rob Stryker > > Describe the issue: > The teiid-designer cannot connect to remote JDV server by timeout exceptions. However, the teiid-designer cannnot set timeout for it. > {noformat} > org.jboss.ide.eclipse.as.management.core.JBoss7ManangerException: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out > at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:336) > at org.jboss.ide.eclipse.as.internal.management.as71.JBoss71ManagerService.execute(JBoss71ManagerService.java:171) > at org.jboss.ide.eclipse.as.management.core.JBoss7ManagerServiceProxy.execute(JBoss7ManagerServiceProxy.java:87) > at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.executeRequest(JBoss7ServerUtil.java:66) > at org.teiid.designer.runtime.adapter.JBoss7ServerUtil.isTeiidServer(JBoss7ServerUtil.java:192) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptJBoss7Server(TeiidServerAdapterFactory.java:181) > at org.teiid.designer.runtime.adapter.TeiidServerAdapterFactory.adaptServer(TeiidServerAdapterFactory.java:82) > at org.teiid.designer.runtime.TeiidParentServerListener.serverChanged(TeiidParentServerListener.java:153) > at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125) > at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:742) > at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:650) > at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143) > at org.jboss.ide.eclipse.as.wtp.core.server.behavior.ControllableServerBehavior.setServerStarted(ControllableServerBehavior.java:201) > at org.jboss.tools.as.core.server.controllable.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:127) > at org.jboss.ide.eclipse.as.rse.core.StandardRSEStartLaunchDelegate.preLaunchCheck(StandardRSEStartLaunchDelegate.java:72) > at org.jboss.ide.eclipse.as.rse.core.subsystems.RSECommandLineLaunchController.preLaunchCheck(RSECommandLineLaunchController.java:103) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.preLaunchCheck(ControllableServerLaunchConfiguration.java:86) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:840) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3541) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3477) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) > Caused by: java.io.IOException: java.net.ConnectException: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:129) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:71) > at org.jboss.ide.eclipse.as.internal.management.as71.AS71Manager.execute(AS71Manager.java:325) > ... 23 more > Caused by: java.net.ConnectException: JBAS012144: JBAS012144: Could not connect to remote://XXXX:9999. The connection timed out > at org.jboss.as.protocol.ProtocolConnectionUtils.connectSync(ProtocolConnectionUtils.java:131) > at org.jboss.as.protocol.ProtocolConnectionManager$EstablishingConnection.connect(ProtocolConnectionManager.java:256) > at org.jboss.as.protocol.ProtocolConnectionManager.connect(ProtocolConnectionManager.java:70) > at org.jboss.as.protocol.mgmt.FutureManagementChannel$Establishing.getChannel(FutureManagementChannel.java:176) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient.getOrCreateChannel(RemotingModelControllerClient.java:144) > at org.jboss.as.controller.client.impl.RemotingModelControllerClient$1.getChannel(RemotingModelControllerClient.java:65) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:115) > at org.jboss.as.protocol.mgmt.ManagementChannelHandler.executeRequest(ManagementChannelHandler.java:98) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeRequest(AbstractModelControllerClient.java:236) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.execute(AbstractModelControllerClient.java:141) > at org.jboss.as.controller.client.impl.AbstractModelControllerClient.executeForResult(AbstractModelControllerClient.java:127) > ... 25 more > {noformat} > Additional information: > We want to set a property of "IAS7ManagementDetails.PROPERTY_TIMEOUT" via teiid-designer. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-626) JBDS-IS 8.0.1: Update supported configuration document

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-626?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-626: ------------------------------- Description: Update supported configuration page here: https://access.redhat.com/articles/1351903 > JBDS-IS 8.0.1: Update supported configuration document > ------------------------------------------------------ > > Key: TOOLSDOC-626 > URL: https://issues.jboss.org/browse/TOOLSDOC-626 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Update supported configuration page here: https://access.redhat.com/articles/1351903 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-626) JBDS-IS 8.0.1: Update supported configuration document

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-626?page=com.atlassian.jira.plug... ] Misha Ali updated TOOLSDOC-626: ------------------------------- Sprint: 2015/S7 (30-Mar > 12-Apr) (was: 2015/S8 (13-Apr > 26-Apr)) > JBDS-IS 8.0.1: Update supported configuration document > ------------------------------------------------------ > > Key: TOOLSDOC-626 > URL: https://issues.jboss.org/browse/TOOLSDOC-626 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-626) JBDS-IS 8.0.1: Update supported configuration document

by Misha Ali (JIRA)

Misha Ali created TOOLSDOC-626: ---------------------------------- Summary: JBDS-IS 8.0.1: Update supported configuration document Key: TOOLSDOC-626 URL: https://issues.jboss.org/browse/TOOLSDOC-626 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Bug Reporter: Misha Ali Assignee: Misha Ali -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19576) Execution environments with no matching JREs should not show up in runtime wizard

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19576?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19576. --------------------------------- Assignee: Rob Stryker Fix Version/s: 4.3.0.Alpha2 Resolution: Done Pushed to master. Ensures the set of compatible vm's for a given exec-env is non-zero before inclusion. Combo responds accurately to user adding or removing jre's to workspace. > Execution environments with no matching JREs should not show up in runtime wizard > --------------------------------------------------------------------------------- > > Key: JBIDE-19576 > URL: https://issues.jboss.org/browse/JBIDE-19576 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Alpha2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > > In a new server / runtime wizard, execution environments such as java8 may show up in the list despite hte workspace having no java8 or higher JREs available. When the user selects the Java8 exec-env, an error is shown and the user cannot continue. > This execution environment should not appear in the list unless the user has a compatible JRE in the workspace. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19576) Execution environments with no matching JREs should not show up in runtime wizard

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-19576: ----------------------------------- Summary: Execution environments with no matching JREs should not show up in runtime wizard Key: JBIDE-19576 URL: https://issues.jboss.org/browse/JBIDE-19576 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.3.0.Alpha2 Reporter: Rob Stryker In a new server / runtime wizard, execution environments such as java8 may show up in the list despite hte workspace having no java8 or higher JREs available. When the user selects the Java8 exec-env, an error is shown and the user cannot continue. This execution environment should not appear in the list unless the user has a compatible JRE in the workspace. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19567) Thym doesn't support JGit 4.0

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19567?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19567: -------------------------------------- Yes, it does. We need to merge https://github.com/jbosstools/jbosstools-aerogear/tree/independent_platforms when the new thym is pulled in. > Thym doesn't support JGit 4.0 > ----------------------------- > > Key: JBIDE-19567 > URL: https://issues.jboss.org/browse/JBIDE-19567 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Reporter: Mickael Istria > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Thym cannot be installed/resolved against a Mars M6 target-platform, because JGit moved to version 4.0, and Thym doesn't allow that yet. > {code}[INFO] [ERROR] Cannot resolve project dependencies: > [INFO] [ERROR] Software being installed: org.jboss.tools.aerogear.thym 1.3.0.qualifier > [INFO] [ERROR] Missing requirement: org.eclipse.thym.core 0.1.0.201503051642 requires 'bundle org.eclipse.jgit [3.0.0,4.0.0)' but it could not be found > [INFO] [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.thym 1.3.0.qualifier depends on: bundle org.eclipse.thym.core 0.1.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19575) Update openshift v3 tools to support deprecation of com.openshift.client

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19575?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19575: --------------------------------------- [~adietish] please merge. Updates to support changes in OSRCJ (???) > Update openshift v3 tools to support deprecation of com.openshift.client > ------------------------------------------------------------------------ > > Key: JBIDE-19575 > URL: https://issues.jboss.org/browse/JBIDE-19575 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19575) Update openshift v3 tools to support deprecation of com.openshift.client

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19575: ------------------------------------- Summary: Update openshift v3 tools to support deprecation of com.openshift.client Key: JBIDE-19575 URL: https://issues.jboss.org/browse/JBIDE-19575 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.x Reporter: Jeff Cantrill Assignee: Jeff Cantrill -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19475) Add New application wizard

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19475?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-19475: ------------------------------------- Assignee: Jeff Cantrill > Add New application wizard > -------------------------- > > Key: JBIDE-19475 > URL: https://issues.jboss.org/browse/JBIDE-19475 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.x > Reporter: Jeff Cantrill > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19571. --------------------------------- Assignee: Rob Stryker Fix Version/s: 4.3.0.Alpha2 Resolution: Done Pushed into stacks. Live now. > Add FSW to downloadable runtimes > -------------------------------- > > Key: JBIDE-19571 > URL: https://issues.jboss.org/browse/JBIDE-19571 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > > FSW 6.0 is not available in download runtimes -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19574) Add API so that downloaded runtimes can be installed via java -jar command

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19574?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-19574: ----------------------------------- Assignee: Rob Stryker Fix Version/s: 4.3.0.Alpha2 Resolution: Done This has been pushed into master. > Add API so that downloaded runtimes can be installed via java -jar command > -------------------------------------------------------------------------- > > Key: JBIDE-19574 > URL: https://issues.jboss.org/browse/JBIDE-19574 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > > Runtime detection currently supports only 'extraction' as a method of installation. It was recently expanded to include not just unzipping of jars, but also extracting .tar.gz files / .tar files / etc. But there's still no API for completely alternate methods of installation. > This JIRA should add an extension point for (basically the plumbing) to allow for alternate installation types in general, as well as add a default java -jar installation method as well. > It will be up to other runtimes (ie teiid etc) to USE this functionality in their own products, but it is up to jbt-base to make sure it is feasible at the API level. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19574) Add API so that downloaded runtimes can be installed via java -jar command

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-19574: ----------------------------------- Summary: Add API so that downloaded runtimes can be installed via java -jar command Key: JBIDE-19574 URL: https://issues.jboss.org/browse/JBIDE-19574 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: runtime-detection, server Affects Versions: 4.3.0.Alpha1 Reporter: Rob Stryker Runtime detection currently supports only 'extraction' as a method of installation. It was recently expanded to include not just unzipping of jars, but also extracting .tar.gz files / .tar files / etc. But there's still no API for completely alternate methods of installation. This JIRA should add an extension point for (basically the plumbing) to allow for alternate installation types in general, as well as add a default java -jar installation method as well. It will be up to other runtimes (ie teiid etc) to USE this functionality in their own products, but it is up to jbt-base to make sure it is feasible at the API level. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19539) Create and use Mars M6 target-platform

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19539?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19539: --------------------------------------- cordovasim.eclipse has compilation problems with thym/master updated to allow JGit 4.0. > Create and use Mars M6 target-platform > -------------------------------------- > > Key: JBIDE-19539 > URL: https://issues.jboss.org/browse/JBIDE-19539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > Mars M6 was released and contains interesting changes (in Platform UI), important version updates (EGit 4.0 and TM 4.0). > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19567) Thym doesn't support JGit 4.0

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19567?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19567: --------------------------------------- cordovasim.eclipse has compilation problems with thym master. {code}[INFO] [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.22.0:compile (default-compile) on project org.jboss.tools.cordovasim.eclipse: Compilation failure: Compilation failure: [INFO] [ERROR] /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/src/org/jboss/tools/cordovasim/eclipse/launch/CordovaSimLaunchParametersUtil.java:[39] [INFO] [ERROR] import org.eclipse.thym.core.engine.PlatformLibrary; [INFO] [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [INFO] [ERROR] The import org.eclipse.thym.core.engine.PlatformLibrary cannot be resolved [INFO] [ERROR] /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/src/org/jboss/tools/cordovasim/eclipse/launch/CordovaSimLaunchParametersUtil.java:[207] [INFO] [ERROR] HybridMobileEngine activeEngine = hybridProject.getActiveEngine(); [INFO] [ERROR] ^^^^^^^^^^^^^^^ [INFO] [ERROR] The method getActiveEngine() is undefined for the type HybridProject [INFO] [ERROR] /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/src/org/jboss/tools/cordovasim/eclipse/launch/CordovaSimLaunchParametersUtil.java:[209] [INFO] [ERROR] PlatformLibrary platformLibrary = getPlatformLibrary(activeEngine); [INFO] [ERROR] ^^^^^^^^^^^^^^^ [INFO] [ERROR] PlatformLibrary cannot be resolved to a type [INFO] [ERROR] /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/src/org/jboss/tools/cordovasim/eclipse/launch/CordovaSimLaunchParametersUtil.java:[209] [INFO] [ERROR] PlatformLibrary platformLibrary = getPlatformLibrary(activeEngine); [INFO] [ERROR] ^^^^^^^^^^^^^^^^^^ [INFO] [ERROR] The method getPlatformLibrary(HybridMobileEngine) from the type CordovaSimLaunchParametersUtil refers to the missing type PlatformLibrary [INFO] [ERROR] /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/src/org/jboss/tools/cordovasim/eclipse/launch/CordovaSimLaunchParametersUtil.java:[232] [INFO] [ERROR] HybridMobileEngine activeEngine = hybridProject.getActiveEngine(); [INFO] [ERROR] ^^^^^^^^^^^^^^^ [INFO] [ERROR] The method getActiveEngine() is undefined for the type HybridProject [INFO] [ERROR] /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/src/org/jboss/tools/cordovasim/eclipse/launch/CordovaSimLaunchParametersUtil.java:[240] [INFO] [ERROR] private static PlatformLibrary getPlatformLibrary(HybridMobileEngine engine) { [INFO] [ERROR] ^^^^^^^^^^^^^^^ [INFO] [ERROR] PlatformLibrary cannot be resolved to a type [INFO] [ERROR] /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/src/org/jboss/tools/cordovasim/eclipse/launch/CordovaSimLaunchParametersUtil.java:[241] [INFO] [ERROR] PlatformLibrary pl = null; [INFO] [ERROR] ^^^^^^^^^^^^^^^ [INFO] [ERROR] PlatformLibrary cannot be resolved to a type [INFO] [ERROR] /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/src/org/jboss/tools/cordovasim/eclipse/launch/CordovaSimLaunchParametersUtil.java:[243] [INFO] [ERROR] pl = engine.getPlatformLib(ANDROID_PLATFORM_ID); // Using android by default [INFO] [ERROR] ^^^^^^^^^^^^^^ [INFO] [ERROR] The method getPlatformLib(String) is undefined for the type HybridMobileEngine [INFO] [ERROR] /home/eskimo/data/Projects/jbdevstudio/4.3.x/fork/jbds-releng/jbosstools-aerogear/cordovasim/plugins/org.jboss.tools.cordovasim.eclipse/src/org/jboss/tools/cordovasim/eclipse/launch/CordovaSimLaunchParametersUtil.java:[245] [INFO] [ERROR] pl = engine.getPlatformLib(IOS_PLATFORM_ID); [INFO] [ERROR] ^^^^^^^^^^^^^^ {code} > Thym doesn't support JGit 4.0 > ----------------------------- > > Key: JBIDE-19567 > URL: https://issues.jboss.org/browse/JBIDE-19567 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Reporter: Mickael Istria > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Thym cannot be installed/resolved against a Mars M6 target-platform, because JGit moved to version 4.0, and Thym doesn't allow that yet. > {code}[INFO] [ERROR] Cannot resolve project dependencies: > [INFO] [ERROR] Software being installed: org.jboss.tools.aerogear.thym 1.3.0.qualifier > [INFO] [ERROR] Missing requirement: org.eclipse.thym.core 0.1.0.201503051642 requires 'bundle org.eclipse.jgit [3.0.0,4.0.0)' but it could not be found > [INFO] [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.thym 1.3.0.qualifier depends on: bundle org.eclipse.thym.core 0.1.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-15714: ---------------------------------------- {quote} Thus i'm still not really following what the problem is besides that on the very first content assist the browser might not be fully initialized ? {quote} #2 problem (refresh problem) means that we need to refresh the browser *before* we execute our JS to get proposals. But because this refresh is asynchronous and takes some time we can't invoke refresh when we asked to execute the JS. In this case the browser will be actually refreshed after the JS is executed and you will get proposals for the old html. We have to refresh the browser automatically when the code is changed. Not when we ask to execute the JS. It's too late. So, if we initialize the preview browser (when using the source tab) after first Ctrl+Space for {{}} and enable auto refreshing then we will have the only problem: no proposals for the very first Ctrl+Space. Which we agreed is not a big deal. We will have a message for that in the proposal list saying "content assist loading...try again". > Dynamic content assist for AngularJS expressions in html files > -------------------------------------------------------------- > > Key: JBIDE-15714 > URL: https://issues.jboss.org/browse/JBIDE-15714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: Diagram.gliffy, vpe.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19573) Improve test coverage for CDI 1.1/1.2 Annotated beans

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-19573: -------------------------------------- Summary: Improve test coverage for CDI 1.1/1.2 Annotated beans Key: JBIDE-19573 URL: https://issues.jboss.org/browse/JBIDE-19573 Project: Tools (JBoss Tools) Issue Type: Task Components: cdi Affects Versions: 4.3.0.Alpha1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 4.3.0.Beta1 Currently we test CDI 1.1/1.2 annotated beans only for CDI as-you-type model. (CDI model snapshots for files which are being edited). We should test it for regular CDI projects/models which are built by CDI builder. I see it in CDI11AnnotatedTest. Maybe more tests effected. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19567) Thym doesn't support JGit 4.0

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19567?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-19567: -------------------------------------- I now have a version of Thym with relaxed JGit requirements. I think we can pull that in for master builds but we need to make sure that it does not affect the 4.2.x as it will break on Luna. > Thym doesn't support JGit 4.0 > ----------------------------- > > Key: JBIDE-19567 > URL: https://issues.jboss.org/browse/JBIDE-19567 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Reporter: Mickael Istria > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Thym cannot be installed/resolved against a Mars M6 target-platform, because JGit moved to version 4.0, and Thym doesn't allow that yet. > {code}[INFO] [ERROR] Cannot resolve project dependencies: > [INFO] [ERROR] Software being installed: org.jboss.tools.aerogear.thym 1.3.0.qualifier > [INFO] [ERROR] Missing requirement: org.eclipse.thym.core 0.1.0.201503051642 requires 'bundle org.eclipse.jgit [3.0.0,4.0.0)' but it could not be found > [INFO] [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.thym 1.3.0.qualifier depends on: bundle org.eclipse.thym.core 0.1.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19567) Thym doesn't support JGit 4.0

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19567?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19567: ---------------------------------- Description: Thym cannot be installed/resolved against a Mars M6 target-platform, because JGit moved to version 4.0, and Thym doesn't allow that yet. {code}[INFO] [ERROR] Cannot resolve project dependencies: [INFO] [ERROR] Software being installed: org.jboss.tools.aerogear.thym 1.3.0.qualifier [INFO] [ERROR] Missing requirement: org.eclipse.thym.core 0.1.0.201503051642 requires 'bundle org.eclipse.jgit [3.0.0,4.0.0)' but it could not be found [INFO] [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.thym 1.3.0.qualifier depends on: bundle org.eclipse.thym.core 0.1.0 {code} was:Thym cannot be installed/resolved against a Mars M6 target-platform, because JGit moved to version 4.0, and Thym doesn't allow that yet. > Thym doesn't support JGit 4.0 > ----------------------------- > > Key: JBIDE-19567 > URL: https://issues.jboss.org/browse/JBIDE-19567 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Reporter: Mickael Istria > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Thym cannot be installed/resolved against a Mars M6 target-platform, because JGit moved to version 4.0, and Thym doesn't allow that yet. > {code}[INFO] [ERROR] Cannot resolve project dependencies: > [INFO] [ERROR] Software being installed: org.jboss.tools.aerogear.thym 1.3.0.qualifier > [INFO] [ERROR] Missing requirement: org.eclipse.thym.core 0.1.0.201503051642 requires 'bundle org.eclipse.jgit [3.0.0,4.0.0)' but it could not be found > [INFO] [ERROR] Cannot satisfy dependency: org.jboss.tools.aerogear.thym 1.3.0.qualifier depends on: bundle org.eclipse.thym.core 0.1.0 > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19551) Ionic Palette: Empty list item

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19551?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19551: -------------------------------------- Assignee: Daniel Azarov (was: Viacheslav Kabanovich) [~dazarov], we need to test it on all major platform we support: Mac, Windows 7/8 to make sure it's reproducible only for Linux GTK3. > Ionic Palette: Empty list item > ------------------------------ > > Key: JBIDE-19551 > URL: https://issues.jboss.org/browse/JBIDE-19551 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Environment: Linux Ubuntu. GTK 3. > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 4.3.0.Alpha2 > > Attachments: list.png > > > In New List wizard, if there is more than one item then all items but the first are empty: > !list.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19410: --------------------------------------- [~mickael_istria], it fixes the issue. Exception is reported in error log view only for in Central the same was as it was for NPE. In Installation details it shows error message below description text. Put still error messages are still confusing sometimes, like this one: "Problems occurred while performing installation: Profile id _SELF_ is not registered. Profile id _SELF_ is not registered.". Which tells nothing from user perspective :) But that is a different issue I guess. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-19410 at 4/9/15 6:29 PM: --------------------------------------------------------------- [~mickael_istria], it fixes the issue. Exception is reported in error log view only for in Central the same was as it was for NPE. In Installation details it shows error message below description text. But still error messages are still confusing sometimes, like this one: "Problems occurred while performing installation: Profile id _SELF_ is not registered. Profile id _SELF_ is not registered.". Which tells nothing from user perspective :) But that is a different issue I guess. was (Author: dgolovin): [~mickael_istria], it fixes the issue. Exception is reported in error log view only for in Central the same was as it was for NPE. In Installation details it shows error message below description text. Put still error messages are still confusing sometimes, like this one: "Problems occurred while performing installation: Profile id _SELF_ is not registered. Profile id _SELF_ is not registered.". Which tells nothing from user perspective :) But that is a different issue I guess. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19572) Replace ImageRepositories with ImageStream

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19572?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19572: ------------------------------------- Affects Version/s: 4.3.0.Alpha2 (was: 4.3.x) > Replace ImageRepositories with ImageStream > ------------------------------------------ > > Key: JBIDE-19572 > URL: https://issues.jboss.org/browse/JBIDE-19572 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Jeff Cantrill > > ImageRepository is to be deprecated in favor of ImageStream -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19572) Replace ImageRepositories with ImageStream

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19572: ------------------------------------- Summary: Replace ImageRepositories with ImageStream Key: JBIDE-19572 URL: https://issues.jboss.org/browse/JBIDE-19572 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 4.3.x Reporter: Jeff Cantrill ImageRepository is to be deprecated in favor of ImageStream -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-425) Establish a Mars/ JBDS 9.x based IS target platform

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-425: -------------------------------- Summary: Establish a Mars/ JBDS 9.x based IS target platform Key: JBTIS-425 URL: https://issues.jboss.org/browse/JBTIS-425 Project: JBoss Tools Integration Stack Issue Type: Feature Request Components: target-platform Reporter: Paul Leacu Assignee: Paul Leacu Create a Mars JBTIS and JBDSIS target platform. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-423: -------------------------------- Assignee: Paul Leacu > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' > --------------------------------------------------------------------------------- > > Key: JBTIS-423 > URL: https://issues.jboss.org/browse/JBTIS-423 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Environment: JBDS 8.1.0.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Minor > > When we try to install to install JBDS-IS 8.0.1.GA from JBoss Central we cann see the following error in Error Log > {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: > com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, > com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-424) Wrong title at JBDS-IS 8.0.1.GA update site

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-424?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-424: -------------------------------- Assignee: Paul Leacu > Wrong title at JBDS-IS 8.0.1.GA update site > ------------------------------------------- > > Key: JBTIS-424 > URL: https://issues.jboss.org/browse/JBTIS-424 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Optional > > There a wrong title at > http://download.englab.brq.redhat.com/pub/rhel/jbossqa/services/http/bina... > "JBoss Developer Studio Integration Stack - Early Access Release Update Site" > but it is not an earlyaccess. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19507: ---------------------------------- Description: *Search Participant* 1. Should be able to find references in job.xml files for Batch Artifact Class IType Example: During the search for references for class "SearchableBatchlet" like: {code} package batch; import javax.batch.api.BatchProperty; import javax.batch.api.Batchlet; import javax.inject.Inject; import javax.inject.Named; @Named public class SearchableBatchlet implements Batchlet { @Inject @BatchProperty(name="secondName") String otherName; @Override public String process() throws Exception { return null; } @Override public void stop() throws Exception { } } {code} In the search result should be added references in jbob.xml files like this: !SearchableBatchletReferences.png! 2. Should be able to find references in job.xml files for Batch Artifact Property IField Example: During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this: !FieldReference.png! 3. Should be able to find references in job.xml files for Exception Class IType Example: During the search for references for class "SearchableException" like: {code} package batch; public class SearchableException extends Exception{ private static final long serialVersionUID = 1L; } {code} In the search result should be added references in jbob.xml files like this: !SearchableExceptionReferences.png! *Rename Participant* 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files. Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named Example: During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring: !BatchArtifactRename.png! 2. Should be able to add changes in Batch Property Rename for references in job.xml files. Note: Rename Participant does make sense only for Batch Properties which name comes from Java Field Name, not from annotation @BatchProperty Example: {code} package batch; import javax.batch.api.BatchProperty; import javax.batch.api.Batchlet; import javax.inject.Inject; import javax.inject.Named; @Named public class RenamablePropertyBatchlet implements Batchlet { @Inject @BatchProperty String otherName; @Override public String process() throws Exception { return null; } @Override public void stop() throws Exception { } } {code} During rename of field "otherName" changes for job.xml references should be added in Refactoring: !PropertyRename.png! 3. Should be able to add changes in Exception Class Rename for references in job.xml files. Example: During rename of class "SearchableException" changes for job.xml references should be added in Refactoring: !ExceptionRename.png! was: *Search Participant* 1. Should be able to find references in job.xml files for Batch Artifact Class IType Example: During the search for references for class "SearchableBatchlet" like: {code} package batch; import javax.batch.api.BatchProperty; import javax.batch.api.Batchlet; import javax.inject.Inject; import javax.inject.Named; @Named public class SearchableBatchlet implements Batchlet { @Inject @BatchProperty(name="secondName") String otherName; @Override public String process() throws Exception { return null; } @Override public void stop() throws Exception { } } {code} In the search result should be added references in jbob.xml files like this: !SearchableBatchletReferences.png! 2. Should be able to find references in job.xml files for Batch Artifact Property IField Example: During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this: !FieldReference.png! 3. Should be able to find references in job.xml files for Exception Class IType Example: During the search for references for class "SearchableException" like: {code} package batch; public class SearchableException extends Exception{ private static final long serialVersionUID = 1L; } {code} In the search result should be added references in jbob.xml files like this: !SearchableExceptionReferences.png! *Rename Participant* 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files. Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named Example: During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring: !BatchArtifactRename.png! 2. Should be able to add changes in Exception Class Rename for references in job.xml files. Example: During rename of class "SearchableException" changes for job.xml references should be added in Refactoring: !ExceptionRename.png! > Search and rename participants for Batch Artifacts > -------------------------------------------------- > > Key: JBIDE-19507 > URL: https://issues.jboss.org/browse/JBIDE-19507 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, PropertyRename.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png > > > *Search Participant* > 1. Should be able to find references in job.xml files for Batch Artifact Class IType > Example: > During the search for references for class "SearchableBatchlet" like: > {code} > package batch; > import javax.batch.api.BatchProperty; > import javax.batch.api.Batchlet; > import javax.inject.Inject; > import javax.inject.Named; > @Named > public class SearchableBatchlet implements Batchlet { > > @Inject @BatchProperty(name="secondName") String otherName; > @Override > public String process() throws Exception { > return null; > } > @Override > public void stop() throws Exception { > } > } > {code} > In the search result should be added references in jbob.xml files like this: > !SearchableBatchletReferences.png! > 2. Should be able to find references in job.xml files for Batch Artifact Property IField > Example: > During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this: > !FieldReference.png! > 3. Should be able to find references in job.xml files for Exception Class IType > Example: > During the search for references for class "SearchableException" like: > {code} > package batch; > public class SearchableException extends Exception{ > private static final long serialVersionUID = 1L; > } > {code} > In the search result should be added references in jbob.xml files like this: > !SearchableExceptionReferences.png! > *Rename Participant* > 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files. > Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named > Example: > During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring: > !BatchArtifactRename.png! > 2. Should be able to add changes in Batch Property Rename for references in job.xml files. > Note: Rename Participant does make sense only for Batch Properties which name comes from Java Field Name, not from annotation @BatchProperty > Example: > {code} > package batch; > import javax.batch.api.BatchProperty; > import javax.batch.api.Batchlet; > import javax.inject.Inject; > import javax.inject.Named; > @Named > public class RenamablePropertyBatchlet implements Batchlet { > > @Inject @BatchProperty String otherName; > @Override > public String process() throws Exception { > return null; > } > @Override > public void stop() throws Exception { > } > } > {code} > During rename of field "otherName" changes for job.xml references should be added in Refactoring: > !PropertyRename.png! > 3. Should be able to add changes in Exception Class Rename for references in job.xml files. > Example: > During rename of class "SearchableException" changes for job.xml references should be added in Refactoring: > !ExceptionRename.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19507) Search and rename participants for Batch Artifacts

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19507?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-19507: ---------------------------------- Attachment: PropertyRename.png > Search and rename participants for Batch Artifacts > -------------------------------------------------- > > Key: JBIDE-19507 > URL: https://issues.jboss.org/browse/JBIDE-19507 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: batch > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: BatchArtifactRename.png, ExceptionRename.png, FieldReference.png, PropertyRename.png, SearchableBatchletReferences.png, SearchableExceptionReferences.png > > > *Search Participant* > 1. Should be able to find references in job.xml files for Batch Artifact Class IType > Example: > During the search for references for class "SearchableBatchlet" like: > {code} > package batch; > import javax.batch.api.BatchProperty; > import javax.batch.api.Batchlet; > import javax.inject.Inject; > import javax.inject.Named; > @Named > public class SearchableBatchlet implements Batchlet { > > @Inject @BatchProperty(name="secondName") String otherName; > @Override > public String process() throws Exception { > return null; > } > @Override > public void stop() throws Exception { > } > } > {code} > In the search result should be added references in jbob.xml files like this: > !SearchableBatchletReferences.png! > 2. Should be able to find references in job.xml files for Batch Artifact Property IField > Example: > During the search for references for field "otherName" of class "SearchableBatchlet" in the search result should be added references in jbob.xml files like this: > !FieldReference.png! > 3. Should be able to find references in job.xml files for Exception Class IType > Example: > During the search for references for class "SearchableException" like: > {code} > package batch; > public class SearchableException extends Exception{ > private static final long serialVersionUID = 1L; > } > {code} > In the search result should be added references in jbob.xml files like this: > !SearchableExceptionReferences.png! > *Rename Participant* > 1. Should be able to add changes in Batch Artifact Class Rename for references in job.xml files. > Note: Rename Participant does make sense only for Batch Artifacts which name comes from Java Class Name, not from annotation @Named > Example: > During rename of class "SearchableBatchlet" changes for job.xml references should be added in Refactoring: > !BatchArtifactRename.png! > 2. Should be able to add changes in Exception Class Rename for references in job.xml files. > Example: > During rename of class "SearchableException" changes for job.xml references should be added in Refactoring: > !ExceptionRename.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19402) should get other product/community runtimes made available from download runtimes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19402?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19402: ------------------------------------- I've made a subtask + PR to get FSW 6.0 added to stacks for download. DV, however, is another issue entirely. Our code currently 'installs' a runtime by unzipping it. We do not have API for alternate methods of install. DV is provided only via an installer jar, which, when unzipped, has a very incorrect structure. It must be installed via the installer, ie, via a java -jar command. This would require API changes to our wizard, and possibly to the DownloadRuntime objects themselves. Most likely I'd need to add another property for installation method (extract, jarInstall, etc). I could also conceivably provide an extension point for the extraction method, in case other runtimes have yet even more unique installation methods (or perhaps even a completely custom logic for remote installation or some such). I'll investigate it further. > should get other product/community runtimes made available from download runtimes > --------------------------------------------------------------------------------- > > Key: JBIDE-19402 > URL: https://issues.jboss.org/browse/JBIDE-19402 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: runtime-detection, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > Teiid, Fuse, SOA-P etc. runtimes would make sense to have available via download runtimes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19571?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19571: ------------------------------------- Linking dependent issue > Add FSW to downloadable runtimes > -------------------------------- > > Key: JBIDE-19571 > URL: https://issues.jboss.org/browse/JBIDE-19571 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Affects Versions: 4.3.0.Alpha1 > Reporter: Rob Stryker > > FSW 6.0 is not available in download runtimes -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19571) Add FSW to downloadable runtimes

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-19571: ----------------------------------- Summary: Add FSW to downloadable runtimes Key: JBIDE-19571 URL: https://issues.jboss.org/browse/JBIDE-19571 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: server Affects Versions: 4.3.0.Alpha1 Reporter: Rob Stryker FSW 6.0 is not available in download runtimes -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19368) File not deployed to server on Windows

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19368?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19368: ------------------------------------- [~ljelinko] - The only thing I can think is that the publish is occuring before the workspace had a chance to build the project. This would mean the bin / output folder for your jars is empty, and so the classes aren't present. I would suggest forcing a build on your project before publishing and see if that fixes the problem. If you want more checks, you should run a build, verify the .class file exists in build/classes, and then execute your publish. Let me know if this helps at all. > File not deployed to server on Windows > -------------------------------------- > > Key: JBIDE-19368 > URL: https://issues.jboss.org/browse/JBIDE-19368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.2.Final > Environment: Windows 7, JBDS 4.2.2, EAP 6.4 ER1 > Reporter: Lucia Jelinkova > Attachments: deployments.zip, jsp-project.zip, workspace.zip > > > Sometimes our automated EAP <-> JBDS compatibility UI tests fail on windows machine because one java file of the tested project is not deployed to the server (and is not in the deployment folder either). > The tests runs like this: > # Create server and start it > # Import project with JSP file from ZIP into the workspace > # Add server as targeted runtime via Properites > # Right-click server and via Add/Remove modules add the imported project to the server > # Open module's web page (right click + open in web browser) > RESULT: JSP file compilation fails because it is not able to resolve HelloWorld.java class > I have not seen any errors in server's console (except for the compilation error). > {code} > 05:25:04,990 INFO [org.jboss.modules] (main) JBoss Modules version 1.3.4.Final-redhat-1 > 05:25:05,678 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1 > 05:25:05,850 INFO [org.jboss.as] (MSC service thread 1-4) JBAS015899: JBoss EAP 6.4.0.Alpha1 (AS 7.5.0.Final-redhat-11) starting > 05:25:08,568 INFO [org.xnio] (MSC service thread 1-4) XNIO Version 3.0.11.GA-redhat-2 > 05:25:08,584 INFO [org.xnio.nio] (MSC service thread 1-4) XNIO NIO Implementation Version 3.0.11.GA-redhat-2 > 05:25:08,600 INFO [org.jboss.as.server] (Controller Boot Thread) JBAS015888: Creating http management service using socket-binding (management-http) > 05:25:08,787 WARN [org.jboss.as.txn] (ServerService Thread Pool -- 45) JBAS010153: Node identifier property is set to the default value. Please make sure it is unique. > 05:25:08,803 INFO [org.jboss.as.clustering.infinispan] (ServerService Thread Pool -- 30) JBAS010280: Activating Infinispan subsystem. > 05:25:08,850 INFO [org.jboss.as.naming] (ServerService Thread Pool -- 38) JBAS011800: Activating Naming Subsystem > 05:25:08,881 INFO [org.jboss.as.jsf] (ServerService Thread Pool -- 36) JBAS012605: Activated the following JSF Implementations: [main, 1.2] > 05:25:08,928 INFO [org.jboss.as.security] (ServerService Thread Pool -- 43) JBAS013171: Activating Security Subsystem > 05:25:08,975 INFO [org.jboss.as.webservices] (ServerService Thread Pool -- 47) JBAS015537: Activating WebServices Extension > 05:25:09,131 INFO [org.jboss.as.security] (MSC service thread 1-3) JBAS013170: Current PicketBox version=4.1.0.Beta1-redhat-1 > 05:25:09,381 INFO [org.jboss.remoting] (MSC service thread 1-4) JBoss Remoting version 3.3.4.Final-redhat-1 > 05:25:09,584 INFO [org.jboss.as.naming] (MSC service thread 1-4) JBAS011802: Starting Naming Service > 05:25:09,600 INFO [org.jboss.as.mail.extension] (MSC service thread 1-4) JBAS015400: Bound mail session [java:jboss/mail/Default] > 05:25:09,725 INFO [org.jboss.as.connector.logging] (MSC service thread 1-4) JBAS010408: Starting JCA Subsystem (IronJacamar 1.0.29.Final-redhat-1) > 05:25:10,334 INFO [org.jboss.as.connector.subsystems.datasources] (ServerService Thread Pool -- 15) JBAS010403: Deploying JDBC-compliant driver class org.h2.Driver (version 1.3) > 05:25:10,412 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) JBWEB003001: Coyote HTTP/1.1 initializing on : http-localhost/127.0.0.1:8080 > 05:25:10,553 INFO [org.apache.coyote.http11.Http11Protocol] (MSC service thread 1-2) JBWEB003000: Coyote HTTP/1.1 starting on: http-localhost/127.0.0.1:8080 > 05:25:10,881 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:9999 > 05:25:10,881 INFO [org.jboss.as.remoting] (MSC service thread 1-3) JBAS017100: Listening on 127.0.0.1:4447 > 05:25:10,928 INFO [org.jboss.as.server.deployment.scanner] (MSC service thread 1-4) JBAS015012: Started FileSystemDeploymentService for directory W:\workspace\eap-6x-jbds-compatibility-jbosstools-4.2.x-windows\8b0502d6\tests\org.jboss.ide.eclipse.as.ui.bot.test\target\requirements\jboss-eap-6.4\standalone\deployments > 05:25:11,287 INFO [org.jboss.as.connector.subsystems.datasources] (MSC service thread 1-3) JBAS010400: Bound data source [java:jboss/datasources/ExampleDS] > 05:25:12,100 INFO [org.jboss.ws.common.management] (MSC service thread 1-2) JBWS022052: Starting JBoss Web Services - Stack CXF Server 4.3.1.Final-redhat-1 > 05:25:12,272 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on http://127.0.0.1:9990/management > 05:25:12,272 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990 > 05:25:12,272 INFO [org.jboss.as] (Controller Boot Thread) JBAS015874: JBoss EAP 6.4.0.Alpha1 (AS 7.5.0.Final-redhat-11) started in 9016ms - Started 152 of 190 services (57 services are lazy, passive or on-demand) > 05:25:25,990 INFO [org.jboss.as.server.deployment.scanner] (DeploymentScanner-threads - 1) JBAS015003: Found jsp-project.war in deployment directory. To trigger deployment create a file called jsp-project.war.dodeploy > 05:25:26,084 INFO [org.jboss.as.server.deployment] (MSC service thread 1-3) JBAS015876: Starting deployment of "jsp-project.war" (runtime-name: "jsp-project.war") > 05:25:26,881 INFO [org.jboss.web] (ServerService Thread Pool -- 24) JBAS018210: Register web context: /jsp-project > 05:25:27,318 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "jsp-project.war" (runtime-name : "jsp-project.war") > 05:25:39,693 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jsp-project].[jsp]] (http-localhost/127.0.0.1:8080-1) JBWEB000236: Servlet.service() for servlet jsp threw exception: org.apache.jasper.JasperException: JBWEB004062: Unable to compile class for JSP: > JBWEB004060: An error occurred at line: 4 in the jsp file: /index.jsp > HelloWorld cannot be resolved > 1: <%@ page language="java" import="org.jboss.tools.tests.as.*" errorPage="" %> > 2: <html> > 3: <body> > 4: <%=HelloWorld.sayHello()%> > 5: </body> > 6: </html> > JBWEB004211: Stacktrace: > at org.apache.jasper.compiler.DefaultErrorHandler.javacError(DefaultErrorHandler.java:85) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.jasper.compiler.ErrorDispatcher.javacError(ErrorDispatcher.java:69) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.jasper.compiler.JDTCompiler.generateClass(JDTCompiler.java:461) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:361) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:339) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.jasper.compiler.Compiler.compile(Compiler.java:326) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.jasper.JspCompilationContext.compile(JspCompilationContext.java:606) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:308) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:309) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:242) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1] > at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:295) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:231) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.5.0.Final-redhat-11.jar:7.5.0.Final-redhat-11] > at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:344) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:854) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:926) [jbossweb-7.5.0.Beta4.jar:7.5.0.Beta4] > at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_20] > {code} > Do you have any idea why this could happen or how to continue with locating the problem? > I am attaching the imported project as ZIP file, the workspace after import and also the content of deployments folder. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19441) Application Client module 6.0 and JCA Module 1.6 cannot both be selected

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19441?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-19441. --------------------------------- Fix Version/s: 4.3.0.Alpha2 Resolution: Done Fixed. The default facet list for eap6.1+ has been changed to be specific per fixed-facet requirement. This means web 3.0 is only the default for web projects, not for all faceted projects. The same for other facet / project types as well. So for JPA, I've made it so the default facet list is java, jpa, and utility facet. This ensures the JPA project can be deployed. IF the user prefers it to be some other set of facets, he can customize the facets, uncheck the utility, and instead check ejb / web / connector / whatever he wants. > Application Client module 6.0 and JCA Module 1.6 cannot both be selected > ------------------------------------------------------------------------ > > Key: JBIDE-19441 > URL: https://issues.jboss.org/browse/JBIDE-19441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Sande Gilda > Assignee: Rob Stryker > Fix For: 4.3.0.Alpha2 > > > To recreate this issue: > 1. Choose File --> New --> Project --> JPA Project > 2. Enter a project name and choose a JBoss EAP 6.4 Runtime > An error appears at the top of the dialog saying: > Application Client module 6.0 and JCA Module 1.6 cannot both be selected. > It appears that when you select the runtime, it adds *all* Java EE facets: > web,ejb,jca,web fragment -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3394: ------------------------------------ I'm happy to ack this JIRA - where are the flags? ;-) > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19441) Application Client module 6.0 and JCA Module 1.6 cannot both be selected

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19441?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-19441: ------------------------------------- So it seems what is happening is as follows: The wizard (whether dynamic web or JPA project) gets a list of fixed facets. For Dynamic web, this is Java and jst.web. For JPA project, it's Java and jpt.jpa. It then gets a list of default facets for our runtime. For wildfly, as6, and all previous, we typically just list the default Java version. But for eap6.1, we specifically list a version of each facet. Why? because our EAP 6.1+ runtime expresses 'support' for higher facets even when we'd like the default to be a lower version. This is so users can upversion to higher spec without issue. Why does this work for dynamic web project on eap6.1+ but not for JPA? Because the framework will automatically remove any facets that 'conflict' with the primary / fixed facets. In the case of a dynamic web project, the fixed facet is jst.web, and so all the others (app-client, ejb, ear, etc) all conflict and are removed. In the case of JPA, none of our defaults conflict with the JPA facet individually; they only conflict with each other. So it adds all of our default facets to the default config, and removes none of them (since none conflict). I'll be looking into a solution. > Application Client module 6.0 and JCA Module 1.6 cannot both be selected > ------------------------------------------------------------------------ > > Key: JBIDE-19441 > URL: https://issues.jboss.org/browse/JBIDE-19441 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Reporter: Sande Gilda > Assignee: Rob Stryker > > To recreate this issue: > 1. Choose File --> New --> Project --> JPA Project > 2. Enter a project name and choose a JBoss EAP 6.4 Runtime > An error appears at the top of the dialog saying: > Application Client module 6.0 and JCA Module 1.6 cannot both be selected. > It appears that when you select the runtime, it adds *all* Java EE facets: > web,ejb,jca,web fragment -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19498) docker container view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19498?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-19498: --------------------------------------- solved in https://github.com/jbdevstudio/linuxtools-docker/commit/2e507da827095c241... > docker container view > --------------------- > > Key: JBIDE-19498 > URL: https://issues.jboss.org/browse/JBIDE-19498 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > Attachments: container_mockup.bmml, container_mockup.png > > > the docker view should give a nice overview of what docker containers are running and if possible how much strain they are putting on the system. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19563) Save docker connections in plugin preferences

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19563?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19563: ---------------------------------- Sprint: Sprint #1 April 2015 > Save docker connections in plugin preferences > --------------------------------------------- > > Key: JBIDE-19563 > URL: https://issues.jboss.org/browse/JBIDE-19563 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > In the current code, the Docker connections are not saved when exiting the workspace, so they need to be setup again after restart -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19564) Use background job to detect default connection settings

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19564?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-19564: ------------------------------------- Assignee: Xavier Coulon Sprint: Sprint #1 April 2015 > Use background job to detect default connection settings > -------------------------------------------------------- > > Key: JBIDE-19564 > URL: https://issues.jboss.org/browse/JBIDE-19564 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > In its current form, the New Connection wizard blocks the UI during opening and this can take a few seconds if the default docker deamon is not running (eg: using the REST API). There should be a background job or an immediate opening with a job (and a progress bar) while trying to detect the settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19559) Display Docker daemon info in properties view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19559?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19559: ---------------------------------- Sprint: Sprint #1 April 2015 > Display Docker daemon info in properties view > --------------------------------------------- > > Key: JBIDE-19559 > URL: https://issues.jboss.org/browse/JBIDE-19559 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > Show the equivalent of 'docker info' in the properties view when a Docker daemon (ie, a Docker connection) node is selected in the Docker Explorer view. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19498) docker container view

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19498?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-19498. ----------------------------------- Resolution: Done The view shows the creation date instead of the CPU/Mem consumption for now. > docker container view > --------------------- > > Key: JBIDE-19498 > URL: https://issues.jboss.org/browse/JBIDE-19498 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > Attachments: container_mockup.bmml, container_mockup.png > > > the docker view should give a nice overview of what docker containers are running and if possible how much strain they are putting on the system. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19564) Use background job to detect default connection settings

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19564?page=com.atlassian.jira.plugi... ] Xavier Coulon updated JBIDE-19564: ---------------------------------- Fix Version/s: 4.3.0.Alpha2 > Use background job to detect default connection settings > -------------------------------------------------------- > > Key: JBIDE-19564 > URL: https://issues.jboss.org/browse/JBIDE-19564 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: docker > Affects Versions: 4.3.0.Alpha1 > Reporter: Xavier Coulon > Fix For: 4.3.0.Alpha2 > > > In its current form, the New Connection wizard blocks the UI during opening and this can take a few seconds if the default docker deamon is not running (eg: using the REST API). There should be a background job or an immediate opening with a job (and a progress bar) while trying to detect the settings. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-421) Cannot install JBoss Integration and SOA Development from non-earlyaccess site

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-421?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-421. ----------------------------------- Verified with JBDS-IS 8.0.1.GA > Cannot install JBoss Integration and SOA Development from non-earlyaccess site > ------------------------------------------------------------------------------ > > Key: JBTIS-421 > URL: https://issues.jboss.org/browse/JBTIS-421 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.CR1 > Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.1.CR1 (without earlyaccess > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 8.0.1.GA > > Attachments: Screenshot_20150403103207.png, Screenshot_20150403103215.png > > > Cannot install JBoss Integration and SOA Development from non-earlyaccess site, namely if you try to install com.jboss.devstudio.integration-stack.soa.feature. > Note that this is not a common use case since you have to uncheck 'Group items by category' during installation. > The problem is that this feature includes fuse and switchyard features which are available only on early access. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-424) Wrong title at JBDS-IS 8.0.1.GA update site

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-424: --------------------------------------- Summary: Wrong title at JBDS-IS 8.0.1.GA update site Key: JBTIS-424 URL: https://issues.jboss.org/browse/JBTIS-424 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 8.0.1.GA Reporter: Andrej Podhradsky Priority: Optional There a wrong title at http://download.englab.brq.redhat.com/pub/rhel/jbossqa/services/http/bina... "JBoss Developer Studio Integration Stack - Early Access Release Update Site" but it is not an earlyaccess. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-423: ------------------------------------ Description: When we try to install to install JBDS-IS 8.0.1.GA from JBoss Central we cann see the following error in Error Log {code} Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar {code} was: When we try to install to install JBDS-IS 8.0.1.GA from JBoss Central we cann see the following error in Error Log {code} Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' > --------------------------------------------------------------------------------- > > Key: JBTIS-423 > URL: https://issues.jboss.org/browse/JBTIS-423 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Environment: JBDS 8.1.0.GA > Reporter: Andrej Podhradsky > Priority: Minor > > When we try to install to install JBDS-IS 8.0.1.GA from JBoss Central we cann see the following error in Error Log > {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: > com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, > com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-423: ------------------------------------ Description: When we try to install to install JBDS-IS 8.0.1.GA from JBoss Central we cann see the following error in Error Log {code} Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar {code} was: When we try to install to install JBDS-IS 8.0.1.GA from JBoss Central we cann see the following error in Error Log {code} Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' > --------------------------------------------------------------------------------- > > Key: JBTIS-423 > URL: https://issues.jboss.org/browse/JBTIS-423 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Environment: JBDS 8.1.0.GA > Reporter: Andrej Podhradsky > Priority: Minor > > When we try to install to install JBDS-IS 8.0.1.GA from JBoss Central we cann see the following error in Error Log > {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar, com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-423: --------------------------------------- Summary: Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' Key: JBTIS-423 URL: https://issues.jboss.org/browse/JBTIS-423 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 8.0.1.GA Environment: JBDS 8.1.0.GA Reporter: Andrej Podhradsky Priority: Minor When we try to install to install JBDS-IS 8.0.1.GA from JBoss Central we cann see the following error in Error Log {code} Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle' {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-422) Lots of errors when we try to install JBDS-IS 8.0.1.GA from central

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-422?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-422. ----------------------------------- Resolution: Won't Fix Verified > Lots of errors when we try to install JBDS-IS 8.0.1.GA from central > ------------------------------------------------------------------- > > Key: JBTIS-422 > URL: https://issues.jboss.org/browse/JBTIS-422 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Andrej Podhradsky > Attachments: error_log.txt > > > Specify the integration stack discovery artifact: > {code} > ./jbdevstudio -vmargs \ > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \ > -Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \ > -Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \ > -Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \ > -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA > {code} > then select Software/Update in JBoss Central and open Error Log. > Note that we are able to install all features without any other problem. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-422) Lots of errors when we try to install JBDS-IS 8.0.1.GA from central

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-422?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-422: ---------------------------------- [~apodhrad] - please try again - there was a bad link in one of the composites. > Lots of errors when we try to install JBDS-IS 8.0.1.GA from central > ------------------------------------------------------------------- > > Key: JBTIS-422 > URL: https://issues.jboss.org/browse/JBTIS-422 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Andrej Podhradsky > Attachments: error_log.txt > > > Specify the integration stack discovery artifact: > {code} > ./jbdevstudio -vmargs \ > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \ > -Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \ > -Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \ > -Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \ > -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA > {code} > then select Software/Update in JBoss Central and open Error Log. > Note that we are able to install all features without any other problem. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3394) Use cordova platform downloads from npm

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3394?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3394: ------------------------------------------- [~ldimaggio] I believe that is correct. The examples are what is in JBoss Central as quickstarts for hybrid mobile. > Use cordova platform downloads from npm > --------------------------------------- > > Key: JBDS-3394 > URL: https://issues.jboss.org/browse/JBDS-3394 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 9.0.0.Alpha2 > > > Switch to downloading the cordova platforms from npm and as a consequence limit the downloadable platform versions to what is available on npm. The plan is to continue to support building applications for Cordova version>3.0.0 but when a developer wants to download a cordova platform using JBDS/JBT, only versions 3.5.0 and later will be available. Configuring a manually downloaded cordova platforms on JBDS will still be available. > Around Cordova 3.5.0 time, Apache Cordova project switched to using npm for distributing cordova platforms. npm provides a much better infrastructure compared to the old way which is basically git archive mechanism. We already had cases where apache infrastructure was not available for maintenance. Also the lack of CDN does not help either. So I think JBDS should follow Apache Cordova and start using npm for downloading cordova platforms. Below are the list of relevant cordova platforms and version that are available today from npm. > cordova-ios > ['3.5.0', '3.6.0', '3.6.1', '3.6.3', '3.7.0', '3.8.0' ] > cordova-android > [ '3.5.0','3.5.1','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0','3.7.1' ] > cordova-wp8 > [ '3.5.0','3.6.0-dev','3.6.0','3.6.1','3.6.3','3.6.4','3.7.0-dev','3.7.0','3.7.1' ] -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3401) Missing target platform zip for JBDS 8.1.0.GA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBDS-3401?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBDS-3401: ----------------------------------------- Thank you! Now it is ok > Missing target platform zip for JBDS 8.1.0.GA > --------------------------------------------- > > Key: JBDS-3401 > URL: https://issues.jboss.org/browse/JBDS-3401 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: target-platform > Affects Versions: 8.1.0.GA > Reporter: Andrej Podhradsky > Assignee: Mickael Istria > Priority: Blocker > Fix For: 8.1.0.GA > > > There is a link (right column, offline install) for downloading target platform zip file at > https://devstudio.jboss.com/updates/8.0/ > but the linked file is missing > https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.1.0.GA-target... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19539) Create and use Mars M6 target-platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19539?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19539: ----------------------------------- Fix Version/s: 4.3.0.Alpha2 > Create and use Mars M6 target-platform > -------------------------------------- > > Key: JBIDE-19539 > URL: https://issues.jboss.org/browse/JBIDE-19539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > Mars M6 was released and contains interesting changes (in Platform UI), important version updates (EGit 4.0 and TM 4.0). > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19539) Create and use Mars M6 target-platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19539?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-19539: -------------------------------------- Assignee: Mickael Istria > Create and use Mars M6 target-platform > -------------------------------------- > > Key: JBIDE-19539 > URL: https://issues.jboss.org/browse/JBIDE-19539 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > Mars M6 was released and contains interesting changes (in Platform UI), important version updates (EGit 4.0 and TM 4.0). > We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3401) Missing target platform zip for JBDS 8.1.0.GA

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3401?page=com.atlassian.jira.plugin.... ] Mickael Istria closed JBDS-3401. -------------------------------- Resolution: Done Website updated: https://github.com/jbdevstudio/jbdevstudio-website/commit/66942904d1181a5... Documentation updated: https://github.com/jbdevstudio/jbdevstudio-devdoc/commit/81bcafb04463260c... I tried the links on the deployed index.html and they are now correct. > Missing target platform zip for JBDS 8.1.0.GA > --------------------------------------------- > > Key: JBDS-3401 > URL: https://issues.jboss.org/browse/JBDS-3401 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: target-platform > Affects Versions: 8.1.0.GA > Reporter: Andrej Podhradsky > Assignee: Mickael Istria > Priority: Blocker > Fix For: 8.1.0.GA > > > There is a link (right column, offline install) for downloading target platform zip file at > https://devstudio.jboss.com/updates/8.0/ > but the linked file is missing > https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.1.0.GA-target... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3263) Remove JSF Visual/Source and Preview Tabs

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3263?page=com.atlassian.jira.plugin.... ] Konstantin Marmalyukov commented on JBDS-3263: ---------------------------------------------- Info about JBDS jar size(Standalone without EAP): Alpha1 with included XulRunner: *509,370,869 bytes* Locally built Alpha2 without XulRunner: *456,620,525 bytes*. So what we can do according to [~dgisbert] feedback: # a. MacOS - remove Visual/Source and Preview tab for xhtml/jsp files like Burr suggested at first b. Windows - leave evarything as it is c. Linux - Make HTML5 mode default. Modify dialog to ask user only at first opening xhtml/jsp file if he wants to have good JSF support and don't ask user again. If user wants - do a restart and switch to XulRunner mode, if not - either show error message on preview tab with link to preferences(as it implemented now) or see pt. a. # Make Visual Editor for xhtml/jsp files available to download from central/update site, as [~dgolovin] suggested. This option will give us an actual amount of users which uses this feature, so we can decide is it ok to remove it or not. For me both options are fine, but I cannot guarantee that there is enough time to do everything for Alpha2. > Remove JSF Visual/Source and Preview Tabs > ----------------------------------------- > > Key: JBDS-3263 > URL: https://issues.jboss.org/browse/JBDS-3263 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Fix For: 9.0.0.Beta2 > > > Removal of the Visual/Source and Preview tabs, which normally provide an error message as it does not run on 64-bit JVMs. > http://www.screencast.com/t/wettTf6s6cU > http://www.screencast.com/t/zur1sCXmZ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15714) Dynamic content assist for AngularJS expressions in html files

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15714?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-15714: ------------------------------------------------ {quote}I would say if the user has disabled refresh then I would be fine saying he won't get uptodate content assist.{quote} This can be easily fixed with using preview web browser(what will be actually done), where refresh cannot be disabled. So that's not a problem. The biggest problem which we have is the first content assist. If it is not a problem - so we will have angular CA in Alpha2 > Dynamic content assist for AngularJS expressions in html files > -------------------------------------------------------------- > > Key: JBIDE-15714 > URL: https://issues.jboss.org/browse/JBIDE-15714 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha2 > > Attachments: Diagram.gliffy, vpe.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18722) Fixing Eclipse/Mars

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18722?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-18722: ---------------------------------------- https://bugs.eclipse.org/bugs/show_bug.cgi?id=464263 https://bugs.eclipse.org/bugs/show_bug.cgi?id=464265 > Fixing Eclipse/Mars > ------------------- > > Key: JBIDE-18722 > URL: https://issues.jboss.org/browse/JBIDE-18722 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: upstream > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > "container" issue for issues related to fixes important to get into Luna. > Please link your Eclipse/Mars issue to this one instead of using subtasks (edit this description). > Current open WTP bugs with patches waiting to be applied (copy from original issue without fixed): > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=398568 target: 3.6.3 > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=431910 show in console. target: none > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=441098 Unable to update from one version to the next on Windows - can not remove product.exe. target: none > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=309443 - [Forms] Section with zero size causes exception. target: none > * https://bugs.eclipse.org/bugs/show_bug.cgi?id=318670 - [Workbench] Not all settings copied when switching workspace and "Copy settings" marked -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19569) Unable to switch pages shown in visual preview when editing mobile html5

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19569?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-19569: ------------------------------------------------ [~mmalina] yes, but don't remember exactly is this a known issue and can we do anything with such links. Will investigate deeper/try to remember exactly a bit later. > Unable to switch pages shown in visual preview when editing mobile html5 > ------------------------------------------------------------------------ > > Key: JBIDE-19569 > URL: https://issues.jboss.org/browse/JBIDE-19569 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.2.3.Final > Reporter: Martin Malina > Assignee: Konstantin Marmalyukov > > I'm not sure if my use case is valid or not. > But today I tried something [1] and had a html5 using the jQuery Mobile 1.4 template, then I created a new page. The Visual part of the editor shows the first page (div with data-role="page") in the html, but it's impossible to show the second one. > So I thought: OK, I will add a button to the first page linking to the second page. But once I clicked the button, there was no way to get back and show the first page in the visual preview. > Shouldn't we offer some kind of navigation? Either the possibility to view different pages in the html, or at least a Back button? > But maybe I just just misunderstand how this works - maybe this is not a valid request - I'll be happy to be corrected :) > [1] I was reviewing a howto document that actually describes exactly this scenario - create html5 from the template and then add a new Page to it using the palette. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-422) Lots of errors when we try to install JBDS-IS 8.0.1.GA from central

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-422?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-422: ------------------------------------ Description: Specify the integration stack discovery artifact: {code} ./jbdevstudio -vmargs \ -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \ -Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \ -Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \ -Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \ -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA {code} then select Software/Update in JBoss Central and open Error Log. Note that we are able to install all features without any other problem. was: Specify the integration stack discovery artifact: {code} ./jbdevstudio -vmargs \ -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \ -Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \ -Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \ -Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \ -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA {code} then select Software/Update in JBoss Central and open Error Log > Lots of errors when we try to install JBDS-IS 8.0.1.GA from central > ------------------------------------------------------------------- > > Key: JBTIS-422 > URL: https://issues.jboss.org/browse/JBTIS-422 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.1.GA > Reporter: Andrej Podhradsky > Attachments: error_log.txt > > > Specify the integration stack discovery artifact: > {code} > ./jbdevstudio -vmargs \ > -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA/devstudio-integration-stack-directory.xml \ > -Djboss.discovery.site.url=https://devstudio.redhat.com/updates/8.0-development/ \ > -Djboss.discovery.earlyaccess.site.url=https://devstudio.redhat.com/earlyaccess/8.0-development/ \ > -Djboss.discovery.earlyaccess.list.url=https://devstudio.redhat.com/updates/8.0-development/devstudio-earlyaccess.properties \ > -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.1.GA > {code} > then select Software/Update in JBoss Central and open Error Log. > Note that we are able to install all features without any other problem. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19410: ---------------------------------------- [~maxandersen] Did you try the PR? Does it work as you'd like? > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-19410: --------------------------------------------- please stop saying it is a corner-case. it happens for *anyone* launching to test our plugins from PDE. This dialog will block everyone on the whole team. It will also show for users using JBDS to write eclipse plugins so it is even visible for users. There is zero reason to show the dialog, p2 itself don't complain on startup - neither should we. Sure, it is a special case, but it is definitely not just an edge case that is not worth fixing properly. > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years

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 April 2015