[JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21233:
-------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-build-sites/pull/211, https://github.com/jbosstools/jbosstools-download.jboss.org/commit/be9ad3... (was: https://github.com/jbosstools/jbosstools-build-sites/pull/211)
> remove need for a targetplatforms/jbosstoolstarget/neon site
> ------------------------------------------------------------
>
> Key: JBIDE-21233
> URL: https://issues.jboss.org/browse/JBIDE-21233
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/
> But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain.
> Therefore I propose we stop linking to this site.
> We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21233:
------------------------------------
Related: https://github.com/jbosstools/jbosstools-download.jboss.org/commit/be9ad3...
> remove need for a targetplatforms/jbosstoolstarget/neon site
> ------------------------------------------------------------
>
> Key: JBIDE-21233
> URL: https://issues.jboss.org/browse/JBIDE-21233
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/
> But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain.
> Therefore I propose we stop linking to this site.
> We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ]
Nick Boldt reassigned JBIDE-21233:
----------------------------------
Assignee: Nick Boldt
> remove need for a targetplatforms/jbosstoolstarget/neon site
> ------------------------------------------------------------
>
> Key: JBIDE-21233
> URL: https://issues.jboss.org/browse/JBIDE-21233
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/
> But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain.
> Therefore I propose we stop linking to this site.
> We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21233?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21233:
-------------------------------
Fix Version/s: 4.4.0.Alpha1
> remove need for a targetplatforms/jbosstoolstarget/neon site
> ------------------------------------------------------------
>
> Key: JBIDE-21233
> URL: https://issues.jboss.org/browse/JBIDE-21233
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/
> But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain.
> Therefore I propose we stop linking to this site.
> We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21233) remove need for a targetplatforms/jbosstoolstarget/neon site
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21233:
----------------------------------
Summary: remove need for a targetplatforms/jbosstoolstarget/neon site
Key: JBIDE-21233
URL: https://issues.jboss.org/browse/JBIDE-21233
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build, target-platform
Affects Versions: 4.4.0.Alpha1
Reporter: Nick Boldt
For the last few years, we've had an associate site ref inside the JBT agg site, pointing at "the latest maximum TP", eg., http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/mars/
But since we now always co-release JBT with its TP in the same URL, this is only useful for someone who wants to do an OFFLINE install using the zip, which will then go ONLINE to resolve TP dependencies. It's at best a broken use case, and at worst it's unnecessary cruft to maintain.
Therefore I propose we stop linking to this site.
We can build the aggregates using a specific TP (the one in the parent pom, natch), and simply NOT use an associate site in the JBT aggregate site build.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3550?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3550:
-----------------------------------
[~rob.stryker] is CDK runtime detection plugged into the installer yet?
> Developer - autodetect the CDK in IDE
> -------------------------------------
>
> Key: JBDS-3550
> URL: https://issues.jboss.org/browse/JBDS-3550
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: runtime-detection
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 9.1.0.Beta1, 10.0.0.Alpha1
>
>
> User Story:
> As a Developer on first startup after the installer have run, the CDK should be configured in the IDE and be ready to use
> Acceptance Criteria:
> * If the CDK is running there should be an openshift connection that is configured with the right url and username and users should have been given a password that allows him to connect
> * if the CDK is running there should be a docker connection that is configured with the right connetion info, certifcates etc. to connect
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3550?page=com.atlassian.jira.plugin.... ]
Fred Bricon reassigned JBDS-3550:
---------------------------------
Assignee: Rob Stryker (was: Max Rydahl Andersen)
> Developer - autodetect the CDK in IDE
> -------------------------------------
>
> Key: JBDS-3550
> URL: https://issues.jboss.org/browse/JBDS-3550
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: runtime-detection
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 9.1.0.Beta1, 10.0.0.Alpha1
>
>
> User Story:
> As a Developer on first startup after the installer have run, the CDK should be configured in the IDE and be ready to use
> Acceptance Criteria:
> * If the CDK is running there should be an openshift connection that is configured with the right url and username and users should have been given a password that allows him to connect
> * if the CDK is running there should be a docker connection that is configured with the right connetion info, certifcates etc. to connect
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20916) importing jbosstools-website results in error
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20916?page=com.atlassian.jira.plugi... ]
Mickael Istria closed JBIDE-20916.
----------------------------------
Resolution: Cannot Reproduce Bug
> importing jbosstools-website results in error
> ---------------------------------------------
>
> Key: JBIDE-20916
> URL: https://issues.jboss.org/browse/JBIDE-20916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> use import nested of jbosstools-website result in progress dialog showing error saying:
> {quote}
> bin | Could not import project located at /Users/max/code/jbosstools/jbosstools-website/bin
> {quote}
> No additional info provided.
> (note: this happened on second import so it might be when .project already there)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-20916) importing jbosstools-website results in error
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20916?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-20916:
----------------------------------------
Without steps to reproduce, I cannot even see the error message to improve.
> importing jbosstools-website results in error
> ---------------------------------------------
>
> Key: JBIDE-20916
> URL: https://issues.jboss.org/browse/JBIDE-20916
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> use import nested of jbosstools-website result in progress dialog showing error saying:
> {quote}
> bin | Could not import project located at /Users/max/code/jbosstools/jbosstools-website/bin
> {quote}
> No additional info provided.
> (note: this happened on second import so it might be when .project already there)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months