[JBoss JIRA] (JBDS-3861) Can't donwload some example projects from central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3861?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3861:
------------------------------
Status: New (was: New)
Target Release: 10.0.0.GA
> Can't donwload some example projects from central
> -------------------------------------------------
>
> Key: JBDS-3861
> URL: https://issues.jboss.org/browse/JBDS-3861
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 10.0.0.Alpha1
> Environment: Devstudio 10.0.0.Alpha1-v20160427-0539-B5240
> Reporter: Jan Richter
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 10.0.0.Alpha2
>
>
> Trying to download some example projects from central simply opens a progress dialog, which quickly disappears and nothing happens. So far I found it happening with HTML5 project, AngularJS forge and Java EE Web Project - but there might be more.
> Note that in JBT master they all work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Denis Golovin commented on JBIDE-13671:
---------------------------------------
Why do we need CI suffix then? It is obvious v -> built in CI, w - local build.
> Replace build timestamp in qualifier by last-mod-timestamp from git
> -------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.4.0.Alpha2
>
> Attachments: jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3861) Can't donwload some example projects from central
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3861?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3861:
------------------------------
Status: New (was: New)
> Can't donwload some example projects from central
> -------------------------------------------------
>
> Key: JBDS-3861
> URL: https://issues.jboss.org/browse/JBDS-3861
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: central, project-examples
> Affects Versions: 10.0.0.Alpha1
> Environment: Devstudio 10.0.0.Alpha1-v20160427-0539-B5240
> Reporter: Jan Richter
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 10.0.0.Alpha2
>
>
> Trying to download some example projects from central simply opens a progress dialog, which quickly disappears and nothing happens. So far I found it happening with HTML5 project, AngularJS forge and Java EE Web Project - but there might be more.
> Note that in JBT master they all work.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22273) Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22273?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-22273:
------------------------------------
Alpha1 is built with M5, not M6. Does this happen on M5 too? In a week we can update the TP to M7 and see if it's a problem there too.
> Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory
> -----------------------------------------------------------------
>
> Key: JBIDE-22273
> URL: https://issues.jboss.org/browse/JBIDE-22273
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.0.Alpha1
> Reporter: Martin Malina
>
> When I instal JBT 4.4.0.Alpha1 nightly into Eclipse Java EE Neon M6, I get this after starting Eclipse:
> {code}
> Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory: {org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand} vs {org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand@25fb43a9}
> {code}
> It's actually twice there and it then happens again at various times.
> I'm on Mac. And BTW I haven't seen this in JBDS, only in JBT.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22273) Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22273?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-22273:
-------------------------------
Component/s: target-platform
> Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory
> -----------------------------------------------------------------
>
> Key: JBIDE-22273
> URL: https://issues.jboss.org/browse/JBIDE-22273
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Martin Malina
>
> When I instal JBT 4.4.0.Alpha1 nightly into Eclipse Java EE Neon M6, I get this after starting Eclipse:
> {code}
> Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory: {org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand} vs {org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand@25fb43a9}
> {code}
> It's actually twice there and it then happens again at various times.
> I'm on Mac. And BTW I haven't seen this in JBDS, only in JBT.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22273) Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22273?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-22273:
----------------------------------
Assignee: Nick Boldt
> Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory
> -----------------------------------------------------------------
>
> Key: JBIDE-22273
> URL: https://issues.jboss.org/browse/JBIDE-22273
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Martin Malina
> Assignee: Nick Boldt
>
> When I instal JBT 4.4.0.Alpha1 nightly into Eclipse Java EE Neon M6, I get this after starting Eclipse:
> {code}
> Conflicting handlers for org.eclipse.e4.ui.importer.openDirectory: {org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand} vs {org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand@25fb43a9}
> {code}
> It's actually twice there and it then happens again at various times.
> I'm on Mac. And BTW I haven't seen this in JBDS, only in JBT.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-22275) oc version is not recognized
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22275?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22275:
-----------------------------------------------
For the message, I think it is not helping user to read 'Your OpenShift client version is 0.0.0' when actually parsing failed. Maybe if matcher.matches() returns false it is better to be logged.
> oc version is not recognized
> ----------------------------
>
> Key: JBIDE-22275
> URL: https://issues.jboss.org/browse/JBIDE-22275
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Marián Labuda
> Labels: openshift_v3
> Fix For: 4.4.0.Alpha2
>
> Attachments: oc_warning.png
>
>
> Using latest oc binary (1.2.0.RC2) there is an invalid warning message in OpenShift 3 preference page. It says my version is 0.0.0 and I need at least 1.1:1, although binary is 1.2.0.
> !oc_warning.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by SJ Cox (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
SJ Cox commented on JBDS-3605:
------------------------------
[~nickboldt] Sure thing! I will get those to you early next week! Im assuming the red circle would be replaced by the Red Hat Developer bracket logo circle that I sent you a while ago?
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: about-jbds10.png, gettingstarted.png, gs_nav.png, header-jbds10-installer.png, icns.zip, jbds_uninstall.ico, jbeap_edit_wiz.png, jbeap_new_wiz.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, splash-jbds10.png
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months
[JBoss JIRA] (JBIDE-13671) Replace build timestamp in qualifier by last-mod-timestamp from git
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13671 at 4/29/16 1:05 PM:
-------------------------------------------------------------
Any objections to applying my PR next week so we can get this in place for the next sprint and flesh out any problems with it?
[~dgolovin] [~maxandersen] [~akazakov] [~rob.stryker] [~mmalina] WDYT?
I'm thinking for Jenkins CI builds we should use
x.y.z.$\{BUILD_ALIAS}-vyyyyMMdd-HHmm-CI
where the timestamps come from github.
For local builds, so that OSGi sees them as newer and can therefore be installed with priority over anything else online:
x.y.z.$\{BUILD_ALIAS}-wyyyyMMdd-HHmm (note the 'w' instead of 'v')
Running this PR [1] locally I generated these plugins:
[1] https://github.com/jbosstools/jbosstools-build/pull/215
{code}
mvn clean install -DskipTests
...
# site/target/repository/plugins/org.jboss.tools.foundation.ui_1.3.0.Alpha1-w20160429-1628.jar
# site/target/repository/features/org.jboss.tools.openshift.express.feature_3.2.0.Alpha1-w20160429-1630.jar
{code}
{code}
mvn clean install -DskipTests -Phudson -DBUILD_NUMBER=1234
...
# site/target/repository/plugins/org.jboss.tools.foundation.ui_1.3.0.Alpha1-v20160420-1633-CI.jar
# site/target/repository/features/org.jboss.tools.openshift.express.feature_3.2.0.Alpha1-v20160428-2230-CI.jar
{code}
Note that I added jgit.dirtyWorkingTree=ignore. With that, we could ALSO version the locally built stuff using jgit timestamp, if we wanted [2]:
[2] https://github.com/jbosstools/jbosstools-build/pull/216
{code}
# site/target/repository/plugins/org.jboss.tools.foundation.ui_1.3.0.Alpha1-w20160420-1633.jar
{code}
So now we see the same timestamp as when built using the -Phudson profile, 20160420-1633, but with a 'w' prefix so your local bits will always win against the publishes ones.
And if I commit a change locally and rebuild, now I get the current timestamp of the change in from my local github:
{code}
# site/target/repository/plugins/org.jboss.tools.foundation.ui_1.3.0.Alpha1-w20160429-1700.jar{code}
was (Author: nickboldt):
Any objections to applying my PR next week so we can get this in place for the next sprint and flesh out any problems with it?
[~dgolovin] [~maxandersen] [~akazakov] [~rob.stryker] [~mmalina] WDYT?
I'm thinking for Jenkins CI builds we should use
x.y.z.$\{BUILD_ALIAS}-vyyyyMMdd-HHmm-CI
where the timestamps come from github.
For local builds, so that OSGi sees them as newer and can therefore be installed with priority over anything else online:
x.y.z.$\{BUILD_ALIAS}-wyyyyMMdd-HHmm (note the 'w' instead of 'v')
Running this PR [1] locally I generated these plugins:
[1] https://github.com/jbosstools/jbosstools-build/pull/215
{code}
mvn clean install -DskipTests
...
# site/target/repository/plugins/org.jboss.tools.foundation.ui_1.3.0.Alpha1-w20160429-1628.jar
# site/target/repository/features/org.jboss.tools.openshift.express.feature_3.2.0.Alpha1-w20160429-1630.jar
{code}
{code}
mvn clean install -DskipTests -Phudson -DBUILD_NUMBER=1234
...
# site/target/repository/plugins/org.jboss.tools.foundation.ui_1.3.0.Alpha1-v20160420-1633-CI.jar
# site/target/repository/features/org.jboss.tools.openshift.express.feature_3.2.0.Alpha1-v20160428-2230-CI.jar
{code}
Note that I added jgit.dirtyWorkingTree=ignore. With that, we could ALSO version the locally built stuff using jgit timestamp, if we wanted [2]:
[2] https://github.com/jbosstools/jbosstools-build/pull/216
{code}
# site/target/repository/plugins/org.jboss.tools.foundation.ui_1.3.0.Alpha1-w20160420-1633.jar
{code}
So now we see the same timestamp as when built using the -Phudson profile, 20160420-1633, but with a 'w' prefix so your local bits will always win against the publishes ones.
> Replace build timestamp in qualifier by last-mod-timestamp from git
> -------------------------------------------------------------------
>
> Key: JBIDE-13671
> URL: https://issues.jboss.org/browse/JBIDE-13671
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Optional
> Fix For: 4.4.0.Alpha2
>
> Attachments: jbide13671-before-and-after.png
>
>
> This needs to be added to master parent pom:
> {code}
> <plugin>
> <groupId>org.eclipse.tycho</groupId>
> <artifactId>tycho-packaging-plugin</artifactId>
> <version>${tycho.version}</version>
> <dependencies>
> <dependency>
> <groupId>org.eclipse.tycho.extras</groupId>
> <artifactId>tycho-buildtimestamp-jgit</artifactId>
> <version>${tycho-extras.version}</version>
> </dependency>
> </dependencies>
> <configuration>
> <strictBinIncludes>false</strictBinIncludes>
> <format>'v'yyyyMMdd-HHmm</format>
> <timestampProvider>jgit</timestampProvider>
> <jgit.ignore>
> </jgit.ignore>
> </configuration>
> </plugin>
> {code}
> Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 8 months