[JBoss JIRA] (JBIDE-18541) Support generation of update sites both with and without references to upstream TP content
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18541?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18541:
------------------------------------
Conceptually, +1. Label-wise, +0.5. Not sure that "direct references" and "composite with references" is clear enough. Maybe...
* "embed-references-in-simple-site" vs.
* "generate-composite-wrapper-site"
I'm also not sure why we would ever want to support the OLD approach, when the new one is:
* better
* more complete
* backward compatible
You could also just add a <legacy>true</legacy> flag, if you really wanted to support the old approach. Or even simpler, just have people use the OLD version of the mojo, if they want the old approach. Then you need only support the NEW way.
> Support generation of update sites both with and without references to upstream TP content
> ------------------------------------------------------------------------------------------
>
> Key: JBIDE-18541
> URL: https://issues.jboss.org/browse/JBIDE-18541
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.2.0.CR2
> Reporter: Mickael Istria
> Assignee: Mickael Istria
>
> Instead of associating statically sites (target-platform) when creating a repository, the generate-repository-facade mojo could create some indirection files allowing to access the repository in 2 flavours:
> * One plain content only, without any reference: for downstream project aggregation
> * One that also references its dependencies for easy install and testers
> Example:
> {code}
> /integration-stack <-- composited without side effects into /earlyaccess/development/luna/
> content.jar
> artifacts.jar
> /withdeps <--- good for testing/single installs
> /compositeContent.xml -> ../ and ../targetplatform-link/
> /compositeArtifacts.xml
> /targetplatform-link <--- point to what is needed for install (not to be used by higher up composites/aggregates [JBT content, JBT IS content, JBT TP, JBT IS TP, etc.]
> content.xml -> associate pointer to TP using ONLY:
> <references size="4">
> <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/> (this currently includes *latest* JBT + JBT TP)
> <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/updates/development/luna/" url="http://download.jboss.org/jbosstools/updates/development/luna/"/>
> <repository options="1" type="0" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
> <repository options="1" type="1" uri="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..." url="http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/luna/is-..."/>
> </references>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18383) forge command rely on english description label to lookup commands - fragile!
by Lincoln Baxter III (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18383?page=com.atlassian.jira.plugi... ]
Lincoln Baxter III commented on JBIDE-18383:
--------------------------------------------
The new functionality accepts both forms, so the cheat sheet will still function, but yes, it should be updated.
> forge command rely on english description label to lookup commands - fragile!
> -----------------------------------------------------------------------------
>
> Key: JBIDE-18383
> URL: https://issues.jboss.org/browse/JBIDE-18383
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Reporter: Max Rydahl Andersen
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.0.CR2
>
>
> it seems this is the way forge commands are looked up:
> org.jboss.tools.forge.ui.runForgeCommand(org.jboss.tools.forge.ui.runForgeCommand.commandName=REST: Generate Endpoints From Entities)"
> meaning if description changes the cheatsheet breaks.
> should this not us a unique id or at least the cli command name so we have *one* API to obey to ?
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18544) Change JBoss Tools Central Discovery URLs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18544?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18544:
-------------------------------
Description:
Today, the Central discovery plugin for JBT is points to this URL:
http://download.jboss.org/jbosstools/updates/development/luna/central/core/
and for Early Access discovery:
http://download.jboss.org/jbosstools/updates/development/luna/central/ear...
However, Max has suggested that we simplify the first, and change the second.
I believe he wants something like this:
http://download.jboss.org/jbosstools/updates/development/luna/
http://download.jboss.org/jbosstools/updates/stable/luna/
and
http://download.jboss.org/jbosstools/earlyaccess/development/luna/
http://download.jboss.org/jbosstools/earlyaccess/stable/luna/
What do people think about this proposed change?
[~mickael_istria] [~maxandersen] [~dgolovin]
was:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site..., the Central discovery plugin for JBDS is points to this URL:
<site>/central/core/
and for Early Access discovery:
<site>/central/earlyaccess/
However, Max has suggested that we simplify the first, and change the second.
I believe he wants something like this:
https://devstudio.jboss.com/updates/8.0-staging/
https://devstudio.jboss.com/updates/8.0-development
https://devstudio.jboss.com/updates/8.0/
and
https://devstudio.jboss.com/earlyaccess/8.0-staging/
https://devstudio.jboss.com/earlyaccess/8.0-development/
https://devstudio.jboss.com/earlyaccess/8.0/
What do people think about this proposed change?
[~mickael_istria] [~maxandersen] [~dgolovin]
> Change JBoss Tools Central Discovery URLs
> ------------------------------------------
>
> Key: JBIDE-18544
> URL: https://issues.jboss.org/browse/JBIDE-18544
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, discovery, updatesite
> Affects Versions: 4.2.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.0.CR2
>
> Attachments: jbds3086_no-change-to-categorized-view.png, jbds3086_uncategorized-view-sample1.png, jbds3086_uncategorized-view-sample2.png
>
>
> Today, the Central discovery plugin for JBT is points to this URL:
> http://download.jboss.org/jbosstools/updates/development/luna/central/core/
> and for Early Access discovery:
> http://download.jboss.org/jbosstools/updates/development/luna/central/ear...
> However, Max has suggested that we simplify the first, and change the second.
> I believe he wants something like this:
> http://download.jboss.org/jbosstools/updates/development/luna/
> http://download.jboss.org/jbosstools/updates/stable/luna/
> and
> http://download.jboss.org/jbosstools/earlyaccess/development/luna/
> http://download.jboss.org/jbosstools/earlyaccess/stable/luna/
> What do people think about this proposed change?
> [~mickael_istria] [~maxandersen] [~dgolovin]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBIDE-18544) Change JBoss Tools Central Discovery URLs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18544?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18544:
-------------------------------
Git Pull Request: (was: https://github.com/jbdevstudio/jbdevstudio-website/pull/141, https://github.com/jbdevstudio/jbdevstudio-website/pull/146, https://github.com/jbosstools/jbosstools-discovery/pull/228, https://github.com/jbosstools/jbosstools-discovery/pull/229, https://github.com/jbdevstudio/jbdevstudio-website/pull/147, https://github.com/jbdevstudio/jbdevstudio-devdoc/pull/110)
> Change JBoss Tools Central Discovery URLs
> ------------------------------------------
>
> Key: JBIDE-18544
> URL: https://issues.jboss.org/browse/JBIDE-18544
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build, discovery, updatesite
> Affects Versions: 4.2.0.CR1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.2.0.CR2
>
> Attachments: jbds3086_no-change-to-categorized-view.png, jbds3086_uncategorized-view-sample1.png, jbds3086_uncategorized-view-sample2.png
>
>
> Today, the Central discovery plugin for JBT is points to this URL:
> http://download.jboss.org/jbosstools/updates/development/luna/central/core/
> and for Early Access discovery:
> http://download.jboss.org/jbosstools/updates/development/luna/central/ear...
> However, Max has suggested that we simplify the first, and change the second.
> I believe he wants something like this:
> http://download.jboss.org/jbosstools/updates/development/luna/
> http://download.jboss.org/jbosstools/updates/stable/luna/
> and
> http://download.jboss.org/jbosstools/earlyaccess/development/luna/
> http://download.jboss.org/jbosstools/earlyaccess/stable/luna/
> What do people think about this proposed change?
> [~mickael_istria] [~maxandersen] [~dgolovin]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months
[JBoss JIRA] (JBDS-3086) Change JBDS Central Discovery URLs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3086:
-----------------------------
Description:
Today, the Central discovery plugin for JBDS is points to this URL:
<site>/central/core/
and for Early Access discovery:
<site>/central/earlyaccess/
However, Max has suggested that we simplify the first, and change the second.
I believe he wants something like this:
https://devstudio.jboss.com/updates/8.0-staging/
https://devstudio.jboss.com/updates/8.0-development
https://devstudio.jboss.com/updates/8.0/
and
https://devstudio.jboss.com/earlyaccess/8.0-staging/
https://devstudio.jboss.com/earlyaccess/8.0-development/
https://devstudio.jboss.com/earlyaccess/8.0/
What do people think about this proposed change?
[~mickael_istria] [~maxandersen] [~dgolovin]
was:
http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site..., the Central discovery plugin for JBDS is points to this URL:
<site>/central/core/
and for Early Access discovery:
<site>/central/earlyaccess/
However, Max has suggested that we simplify the first, and change the second.
I believe he wants something like this:
https://devstudio.jboss.com/updates/8.0-staging/
https://devstudio.jboss.com/updates/8.0-development
https://devstudio.jboss.com/updates/8.0/
and
https://devstudio.jboss.com/earlyaccess/8.0-staging/
https://devstudio.jboss.com/earlyaccess/8.0-development/
https://devstudio.jboss.com/earlyaccess/8.0/
What do people think about this proposed change?
[~mickael_istria] [~maxandersen] [~dgolovin]
> Change JBDS Central Discovery URLs
> ----------------------------------
>
> Key: JBDS-3086
> URL: https://issues.jboss.org/browse/JBDS-3086
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Components: build, discovery, updatesite
> Affects Versions: 8.0.0.Beta3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 8.0.0.CR2
>
> Attachments: jbds3086_no-change-to-categorized-view.png, jbds3086_uncategorized-view-sample1.png, jbds3086_uncategorized-view-sample2.png
>
>
> Today, the Central discovery plugin for JBDS is points to this URL:
> <site>/central/core/
> and for Early Access discovery:
> <site>/central/earlyaccess/
> However, Max has suggested that we simplify the first, and change the second.
> I believe he wants something like this:
> https://devstudio.jboss.com/updates/8.0-staging/
> https://devstudio.jboss.com/updates/8.0-development
> https://devstudio.jboss.com/updates/8.0/
> and
> https://devstudio.jboss.com/earlyaccess/8.0-staging/
> https://devstudio.jboss.com/earlyaccess/8.0-development/
> https://devstudio.jboss.com/earlyaccess/8.0/
> What do people think about this proposed change?
> [~mickael_istria] [~maxandersen] [~dgolovin]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 8 months