[JBoss JIRA] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19756:
-------------------------------
Attachment: jbide19756_final_JBDS-sourcesZip.png
> jbosstools-src.zip has incomplete/misleading version info in folder names/structure
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19756
> URL: https://issues.jboss.org/browse/JBIDE-19756
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
> Attachments: jbide19756.png, jbide19756_final_JBDS-sourcesZip.png, jbide19756_jbds-sources-zip.png, jbide19756_new_subfolders_and_zipfile_name.png
>
>
> Downloading latest jbosstools-src.zip from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I see multiple files in root named:
> <componentname>_<buildqualifier>_<sha1>
> example:
> jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad
> A few issues with this:
> a) it would have been nice unzipping would not create multiple root level folders. Maybe have a jbosstools-source folder as root ?
> b) the buildqualifier is there but the version string for the component is not. Either put the full version string for that component (not overall jbosstools version) or just leave it as <component>-<sha> and have the root folder state the full version of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1 or 4.2.3.Beta1 (for example).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19812) Refactor IConnection to be agnostic of authorization specifics
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-19812:
-------------------------------------
Summary: Refactor IConnection to be agnostic of authorization specifics
Key: JBIDE-19812
URL: https://issues.jboss.org/browse/JBIDE-19812
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.x
Reporter: Jeff Cantrill
The auth scheme can change in v3. A plain IConnection should be able to be refactored to support the auth details as an interface and details like get/set password, username, etc should be moved to those interface implementations.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19811) Refactor IConnection interface to support connection specific display formating
by Jeff Cantrill (JIRA)
Jeff Cantrill created JBIDE-19811:
-------------------------------------
Summary: Refactor IConnection interface to support connection specific display formating
Key: JBIDE-19811
URL: https://issues.jboss.org/browse/JBIDE-19811
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.x
Reporter: Jeff Cantrill
Ultimately, IConnection should be oblivious to username and password since those are authentication specific. There are a few places where we should introduce a 'display' interface which each type can implement in order to remove the dependency of the common label provider on username and password
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19776:
-------------------------------
Attachment: jbdevstudio.p2diff.v20150514.txt
> Create and use Mars M7 target-platform
> --------------------------------------
>
> Key: JBIDE-19776
> URL: https://issues.jboss.org/browse/JBIDE-19776
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt
>
>
> Mars M7 was released and contains interesting changes.
> 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.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19776 at 5/14/15 5:13 PM:
-------------------------------------------------------------
To recap changes since I first put this PR together:
* remove fest (it was commented out already)
* add org.eclipse.tm.terminal.control.feature.feature.group (rse.terminals requires it); remove old org.junit 3.8.2.v3_8_2_v20130308-0410
* add org.eclipse.egit.ui.importer 0.0.1.201505070847 (needed for easymport)
* jbosstools-server requests that the new tm.terminal views/connectors be installed along with it, so add org.eclipse.tm.terminal.*, connector.local.feature and org.eclipse.cdt.core.native.feature (JBIDE-17686, JBIDE-19776)
* Switch to Mockito 1.9.5.v20131024-0922 (from Locus 1.2.0.Final site)
If you haven't tried the latest M7 TP, please do so from this PR:
https://github.com/jbosstools/jbosstools-target-platforms/pull/142/
Updated p2diffs:
[^jbosstools.p2diff.v20150514.txt]
[^jbdevstudio.p2diff.v20150514.txt]
was (Author: nickboldt):
To recap changes since I first put this PR together:
* remove fest (it was commented out already)
* add org.eclipse.tm.terminal.control.feature.feature.group (rse.terminals requires it); remove old org.junit 3.8.2.v3_8_2_v20130308-0410
* add org.eclipse.egit.ui.importer 0.0.1.201505070847 (needed for easymport)
* jbosstools-server requests that the new tm.terminal views/connectors be installed along with it, so add org.eclipse.tm.terminal.*, connector.local.feature and org.eclipse.cdt.core.native.feature (JBIDE-17686, JBIDE-19776)
* Switch to Mockito 1.9.5.v20131024-0922 (from Locus 1.2.0.Final site)
If you haven't tried the latest M7 TP, please do so from this PR:
https://github.com/jbosstools/jbosstools-target-platforms/pull/142/
> Create and use Mars M7 target-platform
> --------------------------------------
>
> Key: JBIDE-19776
> URL: https://issues.jboss.org/browse/JBIDE-19776
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v20150514.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt
>
>
> Mars M7 was released and contains interesting changes.
> 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.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19776:
-------------------------------
Attachment: jbosstools.p2diff.v20150514.txt
> Create and use Mars M7 target-platform
> --------------------------------------
>
> Key: JBIDE-19776
> URL: https://issues.jboss.org/browse/JBIDE-19776
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v20150514.txt, jbosstools.p2diff.v3.txt
>
>
> Mars M7 was released and contains interesting changes.
> 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.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19776:
------------------------------------
To recap changes since I first put this PR together:
* remove fest (it was commented out already)
* add org.eclipse.tm.terminal.control.feature.feature.group (rse.terminals requires it); remove old org.junit 3.8.2.v3_8_2_v20130308-0410
* add org.eclipse.egit.ui.importer 0.0.1.201505070847 (needed for easymport)
* jbosstools-server requests that the new tm.terminal views/connectors be installed along with it, so add org.eclipse.tm.terminal.*, connector.local.feature and org.eclipse.cdt.core.native.feature (JBIDE-17686, JBIDE-19776)
* Switch to Mockito 1.9.5.v20131024-0922 (from Locus 1.2.0.Final site)
If you haven't tried the latest M7 TP, please do so from this PR:
https://github.com/jbosstools/jbosstools-target-platforms/pull/142/
> Create and use Mars M7 target-platform
> --------------------------------------
>
> Key: JBIDE-19776
> URL: https://issues.jboss.org/browse/JBIDE-19776
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v3.txt
>
>
> Mars M7 was released and contains interesting changes.
> 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.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19810) easymport is slow and wrong compared to basic import since it lets mvn overrule .project
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19810?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-19810:
----------------------------------------
Summary: easymport is slow and wrong compared to basic import since it lets mvn overrule .project (was: easymport is slow compared to basic import since it lets mvn overrule .project)
Description:
when using git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.git it already has tons of projects with .project in it but also pom.xml. Resulting in slow and eventually wrong imported projects.
This import is *really* slow with easyimport vs just using plain file import.
Shouldn't easyimport honor existing .project files over presence of a pom.xml (or anything else) ?
If not could we allow users to disable certain configurators for an import or even reorder priority so mvn wont win ?
was:
when using git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.git it already has tons of projects with .project in it but also pom.xml.
This import is *really* slow with easyimport vs just using plain file import.
Shouldn't easyimport honor existing .project files over presence of a pom.xml (or anything else) ?
If not could we allow users to disable certain configurators for an import or even reorder priority so mvn wont win ?
> easymport is slow and wrong compared to basic import since it lets mvn overrule .project
> ----------------------------------------------------------------------------------------
>
> Key: JBIDE-19810
> URL: https://issues.jboss.org/browse/JBIDE-19810
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Reporter: Max Rydahl Andersen
>
> when using git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.git it already has tons of projects with .project in it but also pom.xml. Resulting in slow and eventually wrong imported projects.
> This import is *really* slow with easyimport vs just using plain file import.
> Shouldn't easyimport honor existing .project files over presence of a pom.xml (or anything else) ?
> If not could we allow users to disable certain configurators for an import or even reorder priority so mvn wont win ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19542) Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19542?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19542 at 5/14/15 3:56 PM:
-------------------------------------------------------------
PR to review: https://github.com/jbosstools/jbosstools-base/pull/402
When I built this and installed the o.j.t.common.mylyn feature, I no longer got the "connectorKind 'jira'" message.
was (Author: nickboldt):
PR to review: https://github.com/jbosstools/jbosstools-base/pull/402
> Installing "JBoss Tools Common - Mylyn" from JBoss Tools result in errors being logged until "Mylyn Issue Tracker Connectors" is installed from Central
> --------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19542
> URL: https://issues.jboss.org/browse/JBIDE-19542
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.2.3.Final
> Reporter: Len DiMaggio
> Assignee: Nick Boldt
> Priority: Minor
>
> Steps to recreate the error:
> * Install Eclipse (eclipse-jee-luna-SR2-linux-gtk-x86_64.tar.gz)
> * Configure JBoss Tools as an update site (http://download.jboss.org/jbosstools/updates/staging/luna/)
> * Install JBoss Tools Common - Mylyn (3.6.2.Final-v20150325-0456-B99, org.jboss.tools.common.mylyn.feature.feature.group)
> * Whenever eclipse is started, this error is written to the .log
> ============================================================================
> cat .log
> !SESSION 2015-03-31 14:33:50.481 -----------------------------------------------
> eclipse.buildId=4.4.2.M20150204-1700
> java.version=1.7.0_55
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.epp.package.jee.product
> Command-line arguments: -os linux -ws gtk -arch x86_64 -product org.eclipse.epp.package.jee.product
> !ENTRY org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
> !MESSAGE Unexpected error while loading repository template extensions
> !SUBENTRY 1 org.eclipse.mylyn.tasks.core 4 0 2015-03-31 14:34:00.231
> !MESSAGE Could not load repository template extension contributed by 'org.jboss.tools.common.mylyn' with connectorKind 'jira'
> ============================================================================
> Workaround:
> * From JBoss Central, install: "Mylyn Issue Tracker Connectors"
> * This results in the following packages being installed
> * Mylyn Commons 3.14.2.v20150217-2244 org.eclipse.mylyn.commons.feature.group
> * Mylyn Context Connector: Eclipse IDE 3.14.2.v20150218-0125 org.eclipse.mylyn.ide_feature.feature.group
> * Mylyn Context Connector: Java Development 3.14.2.v20150218-0125 org.eclipse.mylyn.java_feature.feature.group
> * Mylyn Context Connector: Plug-in Development 3.14.2.v20150218-0125 org.eclipse.mylyn.pde_feature.feature.group
> * Mylyn Context Connector: Team Support 3.14.2.v20150218-0125 org.eclipse.mylyn.team_feature.feature.group
> * Mylyn Task List 3.14.2.v20150217-2341 org.eclipse.mylyn_feature.feature.group
> * Mylyn Task-Focused Interface 3.14.2.v20150218-0125 org.eclipse.mylyn.context_feature.feature.group
> * Mylyn Tasks Connector: Bugzilla 3.14.2.v20150217-2341 org.eclipse.mylyn.bugzilla_feature.feature.group
> * Mylyn Versions 1.6.2.v20150217-2249 org.eclipse.mylyn.versions.feature.group
> After installing this^, the error is not generated
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months