October 2015 - jbosstools-dev - Jboss List Archives

ACTION REQUIRED: 4 issues with no component

by manderse＠redhat.com

This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3549 https://issues.jboss.org/browse/JBDS-3549 Summary: Developer - start and stop the CDK easily from within the IDE Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 18:21:40.475489 ---------------------------- * No component for JBDS-3552 https://issues.jboss.org/browse/JBDS-3552 Summary: Developer - be able to incrementally deploy changes to docker containers Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 19:01:31.471336 ---------------------------- * No component for JBDS-3550 https://issues.jboss.org/browse/JBDS-3550 Summary: Developer - autodetect the CDK in IDE Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 19:01:37.475317 ---------------------------- * No component for JBDS-3551 https://issues.jboss.org/browse/JBDS-3551 Summary: JavaEE Developer - be able to start/stop applications on docker with debug on/off Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 1 day, 19:01:35.475136 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

9 years, 4 months

1
0
0 / 0

Fwd: [cross-project-issues-dev] DTP major version bump for Neon

by Max Rydahl Andersen

fyi. this major version bump is probably going to affect some our plugins and most definitely the TP when we update to this. thus a heads up. /max http://about.me/maxandersen Forwarded message: > From: Konstantin Komissarchik <konstantin.komissarchik(a)oracle.com> > To: Cross project issues <cross-project-issues-dev(a)eclipse.org> > Subject: [cross-project-issues-dev] DTP major version bump for Neon > Date: Fri, 23 Oct 2015 12:37:59 -0700 > > DTP will soon contribute v2 to Neon aggregation stream. The current > version is 1.12.1. The reason for the major version bump is the move > to requiring Java 8. All DTP plugins and features will get a major > version bump. > > I recommend all consuming projects to prepare for this ahead of time > by relaxing the version ranges. > > Thanks, > > - Konstantin > > _______________________________________________ > cross-project-issues-dev mailing list > cross-project-issues-dev(a)eclipse.org > To change your delivery options, retrieve your password, or > unsubscribe from this list, visit > https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

9 years, 4 months

1
0
0 / 0

JBDSIS 9.0.0.GA -> JBDSIS 9.0.0.Alpha2

by Paul Leacu

Hey - In an ill-advised effort to create stable release URLs for the Integration Stack for use in JBDS I created a GA/Final release for the SOA 5.x compatibility plugins (with the rest of the stack as early access) without the appropriate oversight and authorization. This has now been reverted - JBT IS 4.3.0.Alpha2 and JBDS IS 9.0.0.Alpha2 are now available from within Central; .Final and .GA are no longer available; all content in Central is now labelled Early Access. I won't try that again... --paull

9 years, 4 months

2
1
0 / 0

ACTION REQUIRED: 4 issues with no component

by manderse＠redhat.com

This email is the result of a query to locate stalled/invalid jiras. Please fix them. Thanks! * No component for JBDS-3549 https://issues.jboss.org/browse/JBDS-3549 Summary: Developer - start and stop the CDK easily from within the IDE Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 18:21:53.878312 ---------------------------- * No component for JBDS-3552 https://issues.jboss.org/browse/JBDS-3552 Summary: Developer - be able to incrementally deploy changes to docker containers Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 19:01:44.874168 ---------------------------- * No component for JBDS-3550 https://issues.jboss.org/browse/JBDS-3550 Summary: Developer - autodetect the CDK in IDE Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 19:01:50.878140 ---------------------------- * No component for JBDS-3551 https://issues.jboss.org/browse/JBDS-3551 Summary: JavaEE Developer - be able to start/stop applications on docker with debug on/off Assignee: None set - please fix. Component: None set - please fix. Problem: No component - please assign this issue to one or more components. Last Update: 19:01:48.877960 ---------------------------- Query used: https://issues.jboss.org/issues/?jql=filter%3D%27ds_lint_nocomponent%27

9 years, 4 months

1
0
0 / 0

by Nick Boldt

Here is a suggested change for target-platform 4.60.0.Alpha1-SNAPSHOT, currently used when building from master branch: https://github.com/jbosstools/jbosstools-target-platforms/pull/169 Changes: * add a couple Jetty plugins from 9.3 (not 9.2) * WTP 3.8 instead of 3.7 (uses an integration build because no M2 available yet) * Neon M2 instead of M1, in order to get bits that are newer/upversioned compared to Neon.1 * egit 4.1.0.201509280440-r instead of 4.0.0 (to get newer org.eclipse.egit.ui.importer) * add org.eclipse.core.runtime.compatibility since org.eclipse.datatools now requires it * remove org.eclipse.core.runtime.compatibility.registry since Neon M2 no longer includes it Please review the suggested patch and the p2diff, and comment on the bug if you see anything worrying. https://issues.jboss.org/browse/JBIDE-20976?focusedCommentId=13119674&pag... Goal is to merge this change within a couple of days (as soon as possible). Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

9 years, 4 months

1
1
0 / 0

by Nick Boldt

Here is a suggested change for the Early Access targetplatforms for 4.51 (Mars, 4.3.x), including upversioning the TP to 4.51 (was 4.50): https://github.com/jbosstools/jbosstools-discovery/pull/316/files#diff-90..., https://github.com/jbosstools/jbosstools-discovery/pull/315 Changes: * update to AngularJS 1.0.0.201508312121 p2diffs show no changes other than simple upversioning of existing IUs. Please review the suggested patch and the p2diff, and comment on the bug if you see anything worrying. https://issues.jboss.org/browse/JBIDE-20976?focusedCommentId=13120054&pag... Goal is to merge this change within a couple of days (as soon as possible). --- Additionally, I noticed that the build of jbosstools-jst relies on a different version of AngularJS than does the Early Access target platform. For details, see: https://issues.jboss.org/browse/JBIDE-21001 https://github.com/jbosstools/jbosstools-jst/pull/542 Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

9 years, 4 months

1
1
0 / 0

by Nick Boldt

Here is a suggested change for the Early Access targetplatforms for 4.60 (Neon, master): https://github.com/jbosstools/jbosstools-discovery/pull/315 Changes: * update to Mars M2 * update to AngularJS 1.0.0.201508312121 p2diffs show no changes other than simple upversioning of existing IUs. Please review the suggested patch and the p2diff, and comment on the bug if you see anything worrying. https://issues.jboss.org/browse/JBIDE-20976?focusedCommentId=13120054&pag... Goal is to merge this change within a couple of days (as soon as possible). --- Additionally, I noticed that the build of jbosstools-jst relies on a different version of AngularJS than does the Early Access target platform. For details, see: https://issues.jboss.org/browse/JBIDE-21001 https://github.com/jbosstools/jbosstools-jst/pull/543 Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

9 years, 4 months

1
1
0 / 0

QE Handoff - JBDSIS 8.0.4.CR2, JBTIS 4.2.4.CR2

by Paul Leacu

Greetings, The latest Eclipse-Luna capable, JBDS 8.1.0 compatible Integration Stack candidate release tooling is available for QE testing. This release contains the following: * Released .Final components BPEL 1.3.100.Final BPMN2 1.1.3.Final_1.1.0.Final_luna DROOLS/JBPM6 6.3.0.Final ESB 1.5.530.Final > FUSE TOOLING 7.3.2.CR2 (w/ Fuse Transformation Tooling) JBPM3 4.5.200.Final MODESHAPE 3.7.0.Final SWITCHYARD 2.0.1.CR1 > TEIID DESIGNER 9.0.4.Final * Early Access components None The latest SAP tooling (7.3.2.CR2) is also available through the Fuse import update wizard and a separate update site. This release is for *internal consumption only* until after QE has sanctioned it. JBDSIS 8.0.4.CR2, JBTIS 4.2.4.CR2 1. If installing from Eclipse Luna: Help > Eclipse Marketplace... - in the 'Search' tab enter 'jbds' in the 'Find' input widget - select the 'Go' button - install 'Red Hat JBoss Developer Studio 8.1.0.GA' 2. Start jbdevstudio or eclipse-with-jbds from step 1, then: Help > Install New Software... Add... - use this for 'Location:' for the integration stack: http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integratio... Done! JBoss Central is supported for JBDSIS: * Specify the integration stack discovery artifact: ./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/integration-stack/8.0.4.CR2/devstudio-directory.xml \ -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/integration-stack/8.0.4.CR2 The standard Eclipse installer is available for JBTIS: * Start eclipse-with-jboss-tools, then: Help > Install New Software... Add... - use this for 'Location:' for the integration stack: http://download.jboss.org/jbosstools/builds/staging/development/luna/inte... JBoss Central is supported for JBTIS: * Install JBoss Tools 4.2.3.Final: Help > Eclipse Marketplace... - in the 'Search' tab enter 'jboss tools' in the 'Find' input widget - select the 'Go' button - install 'JBoss Tools 4.2.3.Final' * Specify the integration stack discovery artifacts: ./eclipse -vmargs \ -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/builds/staging/discovery/development/integration-stack/4.2.4.CR2/jbosstools-directory.xml \ -Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/builds/staging/discovery/development/integration-stack/4.2.4.CR2/ Offline zip files are supported for both production and community installs: 1. http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integratio... (MD5) 2. http://download.jboss.org/jbosstools/updates/development/luna/integration... (MD5) For component and QE test developers - the JBTIS target platforms are: - Full and candidate release target platforms including early access dependencies: https://repository.jboss.org/nexus/content/repositories/releases/org/jbos... http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.2.8.Fi... Note that the integration stack update site is in a QE development area until after it's validated. If you have trouble accessing the server add these lines to your /etc/hosts or C:\windows\system32\drivers\etc\hosts file: 10.16.89.17 dev39.mw.lab.eng.bos.redhat.com www.qa.jboss.com 10.16.90.43 hudson.qa.jboss.com --paull

9 years, 4 months

1
0
0 / 0

Openshif build fails

by Denis Golovin

Fred, openshift build from master is failing after changing openshift-restclient-java changed to 3.1.0-SNAPSHOT, should we kick openshift-restclient-java project on jenkins with master branch? -- Denis

9 years, 4 months

4
4
0 / 0

please keep order in jira versions

by Max Rydahl Andersen

Hey jira-admins that isn't me, jira don't let me know who changed jira versions but jiralint got all confused by whatever latest changes that are there - so I have to send out this broader message. a) if you create a new jira version - please place it in the right order i.e.: 9.0.1.Beta is *before* 9.1.0.Final, not the other way around. If this is not upheld version range comparison in jira and jiralint falls apart. b) have *one* version with a start date in both master and branch version stream. The start date are used to indicate if this is where work is going on. If not set, jiralint thinks no work is happening and implodes on itself. c) please don't have one version in JBIDE and no match in JBDS This does not break anything, except it makes it freaking hard for humans to actually see what lines up. I've fixed what I could find now so the order is right and for each version in JBDS there is one in JBIDE and vice versa. btw. no idea what 9.0.x is about vs 9.x ... do we really need 9.0.x too ? /max http://about.me/maxandersen

9 years, 4 months

3
5
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev October 2015