[JBoss JIRA] (JBIDE-17848) Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17848?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17848:
-------------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/440 (was: https://github.com/jbosstools/jbosstools-openshift/pull/439)
> Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17848
> URL: https://issues.jboss.org/browse/JBIDE-17848
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Optional
> Labels: application_wizard
> Fix For: 4.2.0.CR1
>
> Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png
>
>
> EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git)
> EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application).
> EXEC: Choose basic cartridge and click Next button (ex. EAP 6).
> EXEC: Fill in name on the next wizard page and click Next.
> EXEC: Choose Use existing project and select the existing git based project.
> EXEC: Finish the wizard.
> *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge).
> !import-failed-uncommitted-changes.png!
> This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17848) Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17848?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17848:
-------------------------------------
Labels: application_wizard (was: application_wizard respin-a)
> Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17848
> URL: https://issues.jboss.org/browse/JBIDE-17848
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Optional
> Labels: application_wizard
> Fix For: 4.2.0.CR1
>
> Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png
>
>
> EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git)
> EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application).
> EXEC: Choose basic cartridge and click Next button (ex. EAP 6).
> EXEC: Fill in name on the next wizard page and click Next.
> EXEC: Choose Use existing project and select the existing git based project.
> EXEC: Finish the wizard.
> *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge).
> !import-failed-uncommitted-changes.png!
> This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17848) Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17848?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-17848:
------------------------------------------
we now validate the selected existing project and error if it has uncommitted changes (we dont error if there are untracked files since one can merge into a repo with untracked files)
!uncommitted-changes.png!
> Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17848
> URL: https://issues.jboss.org/browse/JBIDE-17848
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Optional
> Labels: application_wizard
> Fix For: 4.2.0.CR1
>
> Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png
>
>
> EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git)
> EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application).
> EXEC: Choose basic cartridge and click Next button (ex. EAP 6).
> EXEC: Fill in name on the next wizard page and click Next.
> EXEC: Choose Use existing project and select the existing git based project.
> EXEC: Finish the wizard.
> *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge).
> !import-failed-uncommitted-changes.png!
> This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17831) Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17831?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17831:
-------------------------------------
Affects: Documentation (Ref Guide, User Guide, etc.),Interactive Demo/Tutorial,Release Notes,User Experience
> Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17831
> URL: https://issues.jboss.org/browse/JBIDE-17831
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Optional
> Labels: application_wizard, respin-a
> Fix For: 4.2.0.Beta3
>
> Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png
>
>
> EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git)
> EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application).
> EXEC: Choose basic cartridge and click Next button (ex. EAP 6).
> EXEC: Fill in name on the next wizard page and click Next.
> EXEC: Choose Use existing project and select the existing git based project.
> EXEC: Finish the wizard.
> *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge).
> !import-failed-uncommitted-changes.png!
> This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17848) Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17848?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17848:
-------------------------------------
Fix Version/s: 4.2.0.CR1
(was: 4.2.0.Beta3)
> Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17848
> URL: https://issues.jboss.org/browse/JBIDE-17848
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Optional
> Labels: application_wizard
> Fix For: 4.2.0.CR1
>
> Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png
>
>
> EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git)
> EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application).
> EXEC: Choose basic cartridge and click Next button (ex. EAP 6).
> EXEC: Fill in name on the next wizard page and click Next.
> EXEC: Choose Use existing project and select the existing git based project.
> EXEC: Finish the wizard.
> *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge).
> !import-failed-uncommitted-changes.png!
> This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17848) Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-17848:
----------------------------------------
Summary: Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
Key: JBIDE-17848
URL: https://issues.jboss.org/browse/JBIDE-17848
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.2.0.Beta3
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Priority: Optional
Fix For: 4.2.0.Beta3
Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png
EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git)
EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application).
EXEC: Choose basic cartridge and click Next button (ex. EAP 6).
EXEC: Fill in name on the next wizard page and click Next.
EXEC: Choose Use existing project and select the existing git based project.
EXEC: Finish the wizard.
*RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge).
!import-failed-uncommitted-changes.png!
This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17831) Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17831?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-17831:
------------------------------------------
merged and pushed to jbosstools-4.2.0.Beta3
> Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17831
> URL: https://issues.jboss.org/browse/JBIDE-17831
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Optional
> Labels: application_wizard, respin-a
> Fix For: 4.2.0.Beta3
>
> Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png
>
>
> EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git)
> EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application).
> EXEC: Choose basic cartridge and click Next button (ex. EAP 6).
> EXEC: Fill in name on the next wizard page and click Next.
> EXEC: Choose Use existing project and select the existing git based project.
> EXEC: Finish the wizard.
> *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge).
> !import-failed-uncommitted-changes.png!
> This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17831) Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17831?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-17831:
-------------------------------------
Attachment: uncommitted-changes.png
we now validate the selected existing project and error if it has uncommitted changes (we dont error if there are untracked files since one can merge into a repo with untracked files)
!uncommitted-changes.png!
> Application wizard: dirty project should not be selectable as existing projectstuck with application but existing project cannot be merged: uncommitted changes
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17831
> URL: https://issues.jboss.org/browse/JBIDE-17831
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Optional
> Labels: application_wizard, respin-a
> Fix For: 4.2.0.Beta3
>
> Attachments: import-failed-uncommitted-changes.png, uncommitted-changes.png
>
>
> EXEC: Import a git based project into the workspace in JBT (ex. git@github.com:adietish/kitchensink.git)
> EXEC: Launch New application wizard from OpenShift explorer (or launch via project context menu Configure->New/Import OpenShift Application).
> EXEC: Choose basic cartridge and click Next button (ex. EAP 6).
> EXEC: Fill in name on the next wizard page and click Next.
> EXEC: Choose Use existing project and select the existing git based project.
> EXEC: Finish the wizard.
> *RESULT:* There is the error that there are uncommitted changes and it is required to commit them first. Application on OpenShift is default (from basic cartridge).
> !import-failed-uncommitted-changes.png!
> This is expected as you cannot merge into a project with uncommitted changes. But the missing requirement (clean project without uncommitted changes) can be spotted far earlier when the existing project is selected.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-17726) Wierd proposals in css content assist for ionic projects
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17726?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-17726:
-----------------------------------------
PR is linked, but there is another problem for me regarding the hyperlinks: Since the project is not a WTP project (it has no Module Core Nature ("org.eclipse.wst.common.modulecore.ModuleCoreNature")) we still cannot find according CSS file. This is a limitation in o.j.t.jst.web.kb.PageContextFactory.getFileFromProject(String, IFile).
> Wierd proposals in css content assist for ionic projects
> --------------------------------------------------------
>
> Key: JBIDE-17726
> URL: https://issues.jboss.org/browse/JBIDE-17726
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta3
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
>
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBDS-2869) 3rd party certification for JBDS 8.0.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2869?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2869:
----------------------------------
More changes for Beta3 (and CR1, too):
* JBDS-3053 - Update to Findbugs 3.0.0 in JBoss Central
* JBDS-2933 - Update to Eclipse Checkstyle 5.7.0.201402131929 in JBoss Central
* JBIDE-17749:- Update fix discovery plugins to include correct (new) Tern features in EA discovery site
> 3rd party certification for JBDS 8.0.0.GA
> -----------------------------------------
>
> Key: JBDS-2869
> URL: https://issues.jboss.org/browse/JBDS-2869
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements, target-platform
> Affects Versions: 8.0.0.Alpha1
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.GA
>
>
> For JBDS 8.0.0.GA, we need to ensure this list is as current and up to date as possible.
> Upstream question about JDK 7 support:
> * https://bugs.eclipse.org/bugs/show_bug.cgi?id=423834
> Proposed *new* connectors for JBDS 8.0:
> * SpringSource's Quick Search - JBDS-2686 (affects JBDS installer/Central TP) :: *DROPPED FOR 7.1, TBD for 8.0*
> Connectors we could update:
> * Mylyn Builds Connector: Hudson/Jenkins org.eclipse.mylyn.hudson.feature 1.1.1.v20130917-0100
> * m2e-wro4j 1.0.2 connector
> * atlassian/3.2.2.v20130909 (affects JBT/JBDS/Central TP)
> * pmd/4.0.1
> * testng/6.8.6.20130914_0724 (affects JBDS installer/Central TP)
> * VJET/0.10.0.201309201624
> * eclipsecs/5.6.1.201306282206
> * springide/3.4.0.201310051539-RELEASE
> * gwt/3.4.2.v201310081834-rel-*r43 ONLY* (affects JBT/JBDS/Central TP)
> * subclipse/1.10.3_1.8.0.r10086_v20131126_1344/
> * findbugs/2.0.2.20121210 - nothing new as of 2013.10.15
> Additionally (Target Platform):
> * swtbot 2.1.1.201305311053 (included in JBT TP; needed for running UI tests; move to 2.1.2?)
> JBoss Tools Locus (for use with Teiid in JBT-IS/JBDS-IS only):
> * mockito/1.9.5 - JBIDE-12971¥ (to be included in JBT Locus 1.0.0 [1,2,3])
> * fest-assert/1.4 & fest-util/1.1.6 - JBIDE-12972¥ (to be included in JBT Locus 1.0.1 [1,2,3])
> See comments below for latest site URLs.
> [1] https://github.com/jbosstools/jbosstools-locus/
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-locus.sit...
> [3] http://download.jboss.org/jbosstools/updates/nightly/locus/trunk/
> ¥ - These issues did not block the release of JBDS 7.1.0.GA, and therefore would not block 8.0.0 either
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months