[ https://issues.jboss.org/browse/JBIDE-13292?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-13292:
------------------------------------------------
this is obviously build problem. I know how to fix it, but I need to clarify some questions before creating PR.
> BrowserSim: No version in about dialog
> --------------------------------------
>
> Key: JBIDE-13292
> URL: https://issues.jboss.org/browse/JBIDE-13292
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.0.0.Final
> Environment: JBDS 6.0.0.GA, L64
> Reporter: Jiri Peterka
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.1.0.Alpha2
>
> Attachments: no-version-in-browsersim.png
>
>
> No version in BrowseSim About dialog, see screenshot
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-13682:
----------------------------------------
RH BZ is bugzilla. Not JIRA. So it has nothing to do with Atlassian connectors. Bugzilla connector is bundled with Mylyn.
> Investigate use of Atlassian 3.2 in JBoss Central
> -------------------------------------------------
>
> Key: JBIDE-13682
> URL: https://issues.jboss.org/browse/JBIDE-13682
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha2
>
>
> Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno.
> There is also a 3.2 available:
> https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo...
> available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-13682:
-----------------------------------------
Also I can see RH BugZilla issues (Made Query from Red Hat Bugzilla Task Repository as Annonymous user) (didn't try to create/edit some issue because I have no credentials for RH BZ and as such I have no issues assigned to me there).
I suppose it should be able to build with 4 mentioned plug-ins... But when you're installing the "Mylyn Issue Tracker Connectors", will the list of dependencies be changed to include those two Atlassian plug-ins of version 3.2.0 (instead of 3.0.7 that are shown in the installation wizard) or we should file a new issue due for the Central (to change those dependencies)?
> Investigate use of Atlassian 3.2 in JBoss Central
> -------------------------------------------------
>
> Key: JBIDE-13682
> URL: https://issues.jboss.org/browse/JBIDE-13682
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha2
>
>
> Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno.
> There is also a 3.2 available:
> https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo...
> available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13682:
------------------------------------
The point of this JIRA is to verify that Atlassian 3.2 works with the mylyn issue connector (RH BZ, JB JIRA), and that the Atlassian 3.2 stuff also works as intended in Kepler.
You don't need to test 3.0.7, if 3.2 works, since we would include 3.2 instead of 3.0.7 in Central.
Sounds like it works as intended.
Therefore we can add these features (version 3.2) to the TP in order to be able to build org.jboss.tools.common.mylyn:
{code}
com.atlassian.connector.eclipse.commons.core
com.atlassian.connector.eclipse.commons.ui
com.atlassian.connector.eclipse.jira.core
com.atlassian.connector.eclipse.jira.ui
{code}
The rest of the features can simply be found from the Central site (eg., http://download.jboss.org/jbosstools/updates/requirements/atlassian/3.2.0... )
> Investigate use of Atlassian 3.2 in JBoss Central
> -------------------------------------------------
>
> Key: JBIDE-13682
> URL: https://issues.jboss.org/browse/JBIDE-13682
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha2
>
>
> Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno.
> There is also a 3.2 available:
> https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo...
> available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ]
Victor Rubezhny edited comment on JBIDE-13682 at 3/14/13 11:59 AM:
-------------------------------------------------------------------
Nick, should I leave 3.0.7 versions of Atlassian Connector for Eclipse Usage Monitoring and Atlassian JIRA Connector checked for install and repeat the try?
What do you mean by "but does it WORK as expected?"? - I made this and [that|https://issues.jboss.org/browse/JBIDE-13682?focusedCommentId=1276118...] comment from the Task Editor in JBDS. Isn't enough?
PS: Can't find how to edit my existing comment from JBDS Task Editor.
was (Author: vrubezhny):
Nick, should I leave 3.0.7 versions of Atlassian Connector for Eclipse Usage Monitoring and Atlassian JIRA Connector checked for install and repeat the try?
What do you mean by "but does it WORK as expected?"? - I made this and [that|Nick, should I leave 3.0.7 versions of Atlassian Connector for Eclipse Usage Monitoring and Atlassian JIRA Connector checked for install and repeat the try?
What do you mean by "but does it WORK as expected?"? - I made that comment from JBDS ] comment from the Task Editor in JBDS. Isn't enough?
> Investigate use of Atlassian 3.2 in JBoss Central
> -------------------------------------------------
>
> Key: JBIDE-13682
> URL: https://issues.jboss.org/browse/JBIDE-13682
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha2
>
>
> Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno.
> There is also a 3.2 available:
> https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo...
> available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-13682:
-----------------------------------------
Nick, should I leave 3.0.7 versions of Atlassian Connector for Eclipse Usage Monitoring and Atlassian JIRA Connector checked for install and repeat the try?
What do you mean by "but does it WORK as expected?"? - I made this and [that|Nick, should I leave 3.0.7 versions of Atlassian Connector for Eclipse Usage Monitoring and Atlassian JIRA Connector checked for install and repeat the try?
What do you mean by "but does it WORK as expected?"? - I made that comment from JBDS ] comment from the Task Editor in JBDS. Isn't enough?
> Investigate use of Atlassian 3.2 in JBoss Central
> -------------------------------------------------
>
> Key: JBIDE-13682
> URL: https://issues.jboss.org/browse/JBIDE-13682
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha2
>
>
> Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno.
> There is also a 3.2 available:
> https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo...
> available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13682:
------------------------------------
[~vrubezhny] OK, so it installs... but does it WORK as expected? Also, seeing 3.0.7 excluded as you attempt to install 3.2.0 makes sense. Newer trumps older.
> Investigate use of Atlassian 3.2 in JBoss Central
> -------------------------------------------------
>
> Key: JBIDE-13682
> URL: https://issues.jboss.org/browse/JBIDE-13682
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha2
>
>
> Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno.
> There is also a 3.2 available:
> https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo...
> available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[ https://issues.jboss.org/browse/JBIDE-13682?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-13682:
-----------------------------------------
This comment is made by using:
- JBoss Developer Studio, Version: 7.0.0.Alpha1, Build id: Alpha1-v20130306-0101-B124, Build date: 20130306-0101 started with the following option: -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml due to specify Boss Central Discovery Directory URL
- Atlassian Connector for Eclipse, Version 3.2.0 installed from http://download.jboss.org/jbosstools/updates/requirements/atlassian/3.2.0...
- Mylyn Issue Tracker Connectors installed from JBoss Central (The following two software options were excluded: Atlassian Connector for Eclipse Usage Monitoring, Version: 3.0.7.v20121218 and Atlassian JIRA Connector (Recommended), Version: 3.0.7.v20121218)
> Investigate use of Atlassian 3.2 in JBoss Central
> -------------------------------------------------
>
> Key: JBIDE-13682
> URL: https://issues.jboss.org/browse/JBIDE-13682
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha2
>
>
> Need to evaluate if Atlassian Connector for Eclipse 3.0.7 is compatible w/ Kepler and works the same way as the previous 3.0.6 version, which requires Juno.
> There is also a 3.2 available:
> https://confluence.atlassian.com/display/IDEPLUGIN/Atlassian+Connector+fo...
> available from http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
Martin Malina created JBIDE-13790:
-------------------------------------
Summary: Prepare fast-filter script for integration-stack-tests split
Key: JBIDE-13790
URL: https://issues.jboss.org/browse/JBIDE-13790
Project: Tools (JBoss Tools)
Issue Type: Task
Affects Versions: 4.0.1.Final, 4.1.0.Alpha1
Reporter: Martin Malina
Assignee: Martin Malina
Fix For: 4.0.2.Final, 4.1.0.Alpha2
As discussed in JBIDE-12974 and elsewhere, we need to split https://github.com/jbosstools/jbosstools-integration-tests in two:
- the current repo will contain tests for all features of JBT core
- the new repo - integration-stack-tests - will contain all soa/drools/teiid related tests
We need a fast-filter script to do the split while preserving history
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira