[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2709:
-----------------------------
CDW release: ?
Status: New (was: New)
Target Release: 7.1.0.GA
Based on QE approval, need to decide if this update should replace the older subclipse/svnkit now in Central
> Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
> ----------------------------------------------------------
>
> Key: JBDS-2709
> URL: https://issues.jboss.org/browse/JBDS-2709
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 7.1.0.Beta1
>
>
> As reported here:
> https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=...
> {quote}
> Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN.
> http://subclipse.tigris.org/update_1.10.x
> Local repository compatibility between these tools and JBDS is very nice to have.
> Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question.
> {quote}
> http://www.svnkit.com/download.php
> Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer version.
--
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
12 years, 8 months
[JBoss JIRA] (JBDS-2709) Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2709?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-2709 at 10/16/13 9:41 AM:
------------------------------------------------------------
Based on QE approval, need to decide if this update should replace the older subclipse/svnkit now in Central.
Also need to decide when to include it -- Beta2 version of SVNKit, or wait for its Final release?
was (Author: nickboldt):
Based on QE approval, need to decide if this update should replace the older subclipse/svnkit now in Central
> Investigate use of Subclipse 1.10 / SVNKit 1.8 in Central
> ----------------------------------------------------------
>
> Key: JBDS-2709
> URL: https://issues.jboss.org/browse/JBDS-2709
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, updatesite
> Affects Versions: 7.0.0.GA
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 7.1.0.Beta1
>
>
> As reported here:
> https://issues.jboss.org/browse/JBDS-2485?focusedCommentId=12791354&page=...
> {quote}
> Subclipse 1.10 has support for the new 1.8 working copy format, which is the format used by the current stable versions of Windows tools like TortoiseSVN and SlikSVN.
> http://subclipse.tigris.org/update_1.10.x
> Local repository compatibility between these tools and JBDS is very nice to have.
> Unfortunately, this version of SubClipse supports only JavaHL, not SVNKit, because version 1.8.0 of the latter is still in alpha. And since we can't reliably use JavaHL (see JBIDE-14795), using 1.8.0 is out of the question.
> {quote}
> http://www.svnkit.com/download.php
> Once there's a more stable version of SVNKit 1.8 that works with Subclipse 1.10, we can explore updating Central to include the newer version.
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-15593) WS Tester should put a warning when parameter is not valid
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15593?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-15593:
-------------------------------------------
Honestly I don't see this is as a blocking change. How much time do we have left?
> WS Tester should put a warning when parameter is not valid
> ----------------------------------------------------------
>
> Key: JBIDE-15593
> URL: https://issues.jboss.org/browse/JBIDE-15593
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: webservices
> Affects Versions: 4.1.0.Final
> Reporter: Xavier Coulon
> Assignee: Brian Fitzpatrick
> Fix For: 4.1.1.Beta1
>
>
> WS Tester input parameter dialog should display a warning and not prevent dialog close instead of displaying an error if the value of a parameter is not compatible with its type.
> User should be allowed to submit the request with bad parameters if she really wants to.
--
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
12 years, 8 months
[JBoss JIRA] (JBDS-2774) Investigate use of Atlassian 3.2.x in JBT 4.1.1, JBDS 7.1, and JBoss Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2774?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2774:
----------------------------------
>From [~ldimaggio], we have something that vaguely resembles a +1, albeit an informal one:
{quote}
from: Len DiMaggio <ldimaggi(a)redhat.com>
to: "Nboldt(a)redhat.com " <nboldt(a)redhat.com>
subject: Seems OK!
date: Tue, 15 Oct 2013 22:09:59 -0400 (EDT)
<nboldt> ldimaggi_: any chance you can review this before noon tomorrow so we can include it in an updated TP release tomorrow, in advance of code freeze Thursday?
<nboldt> ldimaggi_: https://issues.jboss.org/browse/JBDS-2774
{quote}
> Investigate use of Atlassian 3.2.x in JBT 4.1.1, JBDS 7.1, and JBoss Central
> ----------------------------------------------------------------------------
>
> Key: JBDS-2774
> URL: https://issues.jboss.org/browse/JBDS-2774
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central
> Affects Versions: 7.1.0.Alpha2
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Fix For: 7.1.0.Beta1
>
>
> JBT 4.1.0 / JBDS 7.0.0 contains Atlassian 3.2.1 (JBIDE-13682) but a newer 3.2.2.v20130909 is available from:
> http://update.atlassian.com/atlassian-eclipse-plugin/rest/e3.6/
> (as per https://confluence.atlassian.com/display/IDEPLUGIN/Installing+the+Eclipse... )
> Mirrored here:
> http://download.jboss.org/jbosstools/updates/requirements/atlassian/3.2.2...
> Please review to decide if we should include this for Beta1.
--
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
12 years, 8 months
[JBoss JIRA] (JBIDE-14936) Add jackson-databinding to Locus repo
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14936?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14936:
----------------------------------------
Fix Version/s: (was: 1.1.0-LOCUS)
> Add jackson-databinding to Locus repo
> -------------------------------------
>
> Key: JBIDE-14936
> URL: https://issues.jboss.org/browse/JBIDE-14936
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: locus
> Reporter: Xavier Coulon
> Assignee: Nick Boldt
>
> Please, add the following artifacts to the JBoss Tools Locus repo:
> {code}
> <artifactItems>
> <artifactItem>
> <groupId>com.fasterxml.jackson.core</groupId>
> <artifactId>jackson-databind</artifactId>
> <version>2.2.2</version>
> </artifactItem>
> <artifactItem>
> <groupId>com.fasterxml.jackson.core</groupId>
> <artifactId>jackson-annotations</artifactId>
> <version>2.2.2</version>
> </artifactItem>
> <artifactItem>
> <groupId>com.fasterxml.jackson.core</groupId>
> <artifactId>jackson-core</artifactId>
> <version>2.2.2</version>
> </artifactItem>
> </artifactItems>
> {code}
--
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
12 years, 8 months
[JBoss JIRA] (JBDS-2744) Certification for Google plugins 3.3.0
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2744?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-2744.
----------------------------
Assignee: Nick Boldt
Fix Version/s: 7.1.0.Beta1
Resolution: Rejected
Rejected - superseded by JBDS-2801 - GPE 3.4 is out now.
> Certification for Google plugins 3.3.0
> --------------------------------------
>
> Key: JBDS-2744
> URL: https://issues.jboss.org/browse/JBDS-2744
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
>
> Google GDT plugins have been updated to version 3.3.0. Current version we use in 3.2.3.
> Can we include 3.3.0 in our Target Platform for JBT 4.2.0.Alpha1 ?
--
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
12 years, 8 months