[JBoss JIRA] (JBIDE-15531) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [XULRunner]
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15531?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich resolved JBIDE-15531.
--------------------------------------
Assignee: Yahor Radtsevich
Resolution: Rejected
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [XULRunner]
> --------------------------------------------------------
>
> Key: JBIDE-15531
> URL: https://issues.jboss.org/browse/JBIDE-15531
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: xulrunner
> Reporter: Nick Boldt
> Assignee: Yahor Radtsevich
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2 [XULRunner]: Please perform the following tasks:
> 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.31.0.Alpha2
> {code}
> 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
> {code}
> git checkout jbosstools-4.1.x
> git pull origin jbosstools-4.1.x
> git checkout -b jbosstools-4.1.1.Alpha2x
> git push origin jbosstools-4.1.1.Alpha2x
> {code}
> 5. Close (not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for XULRunner task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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, 6 months
[JBoss JIRA] (JBIDE-15530) For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [VPE]
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15530?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich resolved JBIDE-15530.
--------------------------------------
Assignee: Yahor Radtsevich
Resolution: Rejected
> For JBIDE 4.1.1.Alpha2: Code Freeze + Branch [VPE]
> --------------------------------------------------
>
> Key: JBIDE-15530
> URL: https://issues.jboss.org/browse/JBIDE-15530
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Reporter: Nick Boldt
> Assignee: Yahor Radtsevich
> Priority: Blocker
> Labels: task
> Fix For: 4.1.1.Alpha2
>
>
> For JBIDE 4.1.1.Alpha2 [VPE]: Please perform the following tasks:
> 0. If nothing has changed in your component since the last milestone or GA release on this branch, *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.Alpha2
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.1.1.Alpha2-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.1.1.Alpha2-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.31.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.31.0.Alpha2
> {code}
> 4. Branch from your existing jbosstools-4.1.x branch into a new jbosstools-4.1.1.Alpha2x branch;
> {code}
> git checkout jbosstools-4.1.x
> git pull origin jbosstools-4.1.x
> git checkout -b jbosstools-4.1.1.Alpha2x
> git push origin jbosstools-4.1.1.Alpha2x
> {code}
> 5. Close (not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
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, 6 months
[JBoss JIRA] (JBIDE-15382) Create target platform from Kepler SR1 (RC) dependencies
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15382?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-15382:
-----------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/20 (was: https://github.com/jbosstoolshttps://github.com/jbosstools/jbosstools-tar...)
> Create target platform from Kepler SR1 (RC) dependencies
> --------------------------------------------------------
>
> Key: JBIDE-15382
> URL: https://issues.jboss.org/browse/JBIDE-15382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
> Assignee: Mickael Istria
>
> Based on the posted schedule [1] the first RC1 of Kepler SR1 will be available tomorrow. So, we should start mirroring those updated bits and produce a new target platform with which to build JBT 4.1.1 / JBDS 7.1.0.
> [1] http://wiki.eclipse.org/Kepler/Simultaneous_Release_Plan#SR1
> There may be other 3rd party features we can also update as part of this release. See JBDS-2710 to track those items.
> For example, we might want to consider including Spring's QuickSearch ( JBDS-2686 ) in JBT/JBDS.
> === FORMAL REQUEST ===
> Reason: Leverage bugfixs of Kepler SR1 RC1 (or RC2 for components which already submitted RC2)
> License and owner: EPL, Eclispe community
> Original repository: download.eclipse.org webtools,kepler,mylyn,tm,m2e,orbit
> JBoss Mirrored repository:
> Source: git.eclipse.org
> Affected projects: All
> Required in devstudio: Yes
> Type of dependency: distributions
> List of bundles: only some version changed + new dependency for EGit (org.tukaani.xy)
--
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, 6 months
[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2767:
-----------------------------
Fix Version/s: 7.1.0.Beta1
> Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection
> ---------------------------------------------------------------------
>
> Key: JBDS-2767
> URL: https://issues.jboss.org/browse/JBDS-2767
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: servers, updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
> Attachments: 15498.png
>
>
> Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0.
> Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances.
> Original from Nick:
> Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7.
> Comparing the update sites for JBT 4.1.x and JBDS 7.1.x:
> !15498.png!
> Was it intentionally excluded from the update site, or forgotten?
--
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, 6 months
[JBoss JIRA] (JBDS-2767) Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2767?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2767:
-----------------------------
CDW devel_ack: + (was: ?)
Status: New (was: New)
> Include org.jboss.tools.wtp.runtimes.tomcat.feature for EWP detection
> ---------------------------------------------------------------------
>
> Key: JBDS-2767
> URL: https://issues.jboss.org/browse/JBDS-2767
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: servers, updatesite
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Attachments: 15498.png
>
>
> Tomcat autodetection is available in JBoss Tools 4.1 but not in JBDS 7.0.
> Suggestion is to include this feature so JBDS can automatically configure and setup JBoss EWP instances in addition to "plain" JBoss AS/EAP instances.
> Original from Nick:
> Noticed today that while org.jboss.tools.wtp.runtimes.tomcat.feature and org.jboss.tools.wtp.runtimes.tomcat.feature.source were added to JBoss Tools 4.1, it was omitted from JBDS 7.
> Comparing the update sites for JBT 4.1.x and JBDS 7.1.x:
> !15498.png!
> Was it intentionally excluded from the update site, or forgotten?
--
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, 6 months
[JBoss JIRA] (JBIDE-15550) Endpoint from Resource Locator and Subresources don't appear in the Project Explorer
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-15550:
-------------------------------------
Summary: Endpoint from Resource Locator and Subresources don't appear in the Project Explorer
Key: JBIDE-15550
URL: https://issues.jboss.org/browse/JBIDE-15550
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.1.0.Final
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.1.1.Beta1, 4.2.0.Alpha1
Take the 2 following classes:
{code}
@Path("/products")
public class ProductResourceLocator {
@PathParam("productType")
private String productType = null;
@Path("/{productType}")
public Object getProductResourceLocator() {
if ("books".equals(productType)) {
return new BookResource();
}
if ("games".equals(productType)) {
return new GameResource();
}
throw new WebApplicationException(Status.NOT_FOUND);
}
}
{code}
and
{code}
public class BookResource {
@GET
@Path("/{id}")
@Produces({ "application/xml", "application/json" })
public Book getProduct(@PathParam("id") Integer id) {
return null;
}
}
{code}
The combination of those 2 classes should produce the following endpoint:
/<rest_app>/products/{productType:String};bar={String}/{id:int}
but *sometimes*, this endpoint is missing and running a 'Project>Clean' does not solve the problem.
--
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, 6 months
[JBoss JIRA] (JBDS-2710) 3rd party certification for JBDS 7.1.0.GA
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2710?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2710:
-----------------------------
Description:
For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774
* gwt/3.2.3.v201304260926-rel-r42/ - JBDS-2486
* pmd/4.0.0.v20130510-1000 - JBIDE-14902
* SpringSource's Quick Search - JBDS-2686 *TBD*
* springide/3.3.0.201307091516-RELEASE - JBDS-2690¥, JBDS-2691¥
* subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
* testng/6.8.1.20130330_0839/ - JBDS-2415
* VJET 0.10 - JBIDE-14764
These are currently unchanged since December when we released JBDS 6.0.0:
* *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799).
* findbugs/2.0.2.20121210 - nothing new as of 2013.06.21
Additionally (Target Platform):
* swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
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 do not block the release of JBDS 7.0.1.GA.
was:
For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
The current list of Extras/Central connectors that we mirror are:
* atlassian/3.2.1.v20130402 - JBIDE-13682
* gwt/3.2.3.v201304260926-rel-r42/ - JBDS-2486
* pmd/4.0.0.v20130510-1000 - JBIDE-14902
* SpringSource's Quick Search - JBDS-2686 *TBD*
* springide/3.3.0.201307091516-RELEASE - JBDS-2690¥, JBDS-2691¥
* subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
* testng/6.8.1.20130330_0839/ - JBDS-2415
* VJET 0.10 - JBIDE-14764
These are currently unchanged since December when we released JBDS 6.0.0:
* *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799).
* findbugs/2.0.2.20121210 - nothing new as of 2013.06.21
Additionally (Target Platform):
* swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
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 do not block the release of JBDS 7.0.1.GA.
> 3rd party certification for JBDS 7.1.0.GA
> -----------------------------------------
>
> Key: JBDS-2710
> URL: https://issues.jboss.org/browse/JBDS-2710
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, requirements
> Affects Versions: 7.0.0.GA
> Reporter: Max Rydahl Andersen
> Assignee: Len DiMaggio
> Priority: Blocker
>
> For JBDS 7.1.0.GA, we need to ensure this list is as current and up to date as possible.
> The current list of Extras/Central connectors that we mirror are:
> * atlassian/3.2.1.v20130402 --> 3.2.2.v20130909 - JBIDE-13682, JBDS-2774
> * gwt/3.2.3.v201304260926-rel-r42/ - JBDS-2486
> * pmd/4.0.0.v20130510-1000 - JBIDE-14902
> * SpringSource's Quick Search - JBDS-2686 *TBD*
> * springide/3.3.0.201307091516-RELEASE - JBDS-2690¥, JBDS-2691¥
> * subclipse/1.8.20_1.7.9.1 --> 1.10_1.8 - JBDS-2485, JBDS-2709
> * testng/6.8.1.20130330_0839/ - JBDS-2415
> * VJET 0.10 - JBIDE-14764
> These are currently unchanged since December when we released JBDS 6.0.0:
> * *[REMOVED]* eclipsecs/5.6.0.201209221626 - no new releases as of 2013.06.27, only some 5.6.1 milestones, so [~maxandersen] has requested we remove this from Central (JBIDE-14799).
> * findbugs/2.0.2.20121210 - nothing new as of 2013.06.21
> Additionally (Target Platform):
> * swtbot 2.1 / junit4 - JBIDE-13843 (included in JBT TP; needed for running UI tests)
> 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 do not block the release of JBDS 7.0.1.GA.
--
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, 6 months