[JBoss JIRA] (JBIDE-18846) create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18846?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-18846:
------------------------------------
For now, there's this:
https://github.com/jbosstools/jbosstools-devdoc/blob/master/list_of_proje...
But yes, migrating this to yaml would be nice. Especially if we could generate this page from out of jjb/buildchow. :D
> create replacement page for cascade/swimlanes pages, to facilitate access to build, discovery, TP, and update site URLs
> -----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18846
> URL: https://issues.jboss.org/browse/JBIDE-18846
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, website
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.3.0.CR1
>
>
> Borrowing heavily from https://projects.eclipse.org/list-of-projects we need a new landing page for the aggregates, which list where to find such things as:
> builds (nightly, staging, dev, stable)
> updates (nightly, staging, dev, stable)
> Jenkins jobs
> discovery sites (nightly, staging, dev, stable)
> target platforms
> etc.
> And for each component, we can list:
> build
> update
> Jenkins job
> etc.
> The old cascade pages are here: http://download.jboss.org/jbosstools/builds/cascade/swimlanes_42.html
> Unsure whether generated HTML (via script) or simple .adoc is better for this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBIDE-20125) v3 Import-, application wizard: use easy import, not our custom facility
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20125?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-20125:
--------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.CR1)
> v3 Import-, application wizard: use easy import, not our custom facility
> ------------------------------------------------------------------------
>
> Key: JBIDE-20125
> URL: https://issues.jboss.org/browse/JBIDE-20125
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Labels: openshift_v3
> Fix For: 4.3.x
>
>
> The current impl of the import wizard in v2 and v3 is using a custom import logic where it launches m2e for repositories that have a pom.xml and "General project" for all the others. In JBDS-3285 [~mickael_istria] contributed a new Easy import facility for Eclipse that we should use instead of our own minimalistic, custom made approach
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBDS-3279) Screencasts: Maven
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3279?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3279:
-----------------------------------
I'll try to get my hands on some screencasting software after the code freeze
> Screencasts: Maven
> ------------------
>
> Key: JBDS-3279
> URL: https://issues.jboss.org/browse/JBDS-3279
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, maven, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 9.0.0.GA
>
>
> As a Java EE developer, new to using Eclipse + Maven, I need short, sub-6 minute screencasts of individual key Maven focused use cases, so that I can better understand how Maven is integrated into the Eclipse + Java EE development workflow.
> Use cases include:
> - creation of a new project and its pom.xml, with the pom.xml editor
> - dependencies adds/removes
> - Import maven projects - from a SVN or Git repo
> - multi-module maven projects
> - run on server
> - package vs install
> - update - the magic "update project" that helps get Eclipse and Maven back into agreement
> - adjust profiles - address the Arquillian profile
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months
[JBoss JIRA] (JBDS-3279) Screencasts: Maven
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3279?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3279:
------------------------------
Fix Version/s: 9.0.0.GA
(was: 9.0.0.CR1)
> Screencasts: Maven
> ------------------
>
> Key: JBDS-3279
> URL: https://issues.jboss.org/browse/JBDS-3279
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, maven, requirements
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 9.0.0.GA
>
>
> As a Java EE developer, new to using Eclipse + Maven, I need short, sub-6 minute screencasts of individual key Maven focused use cases, so that I can better understand how Maven is integrated into the Eclipse + Java EE development workflow.
> Use cases include:
> - creation of a new project and its pom.xml, with the pom.xml editor
> - dependencies adds/removes
> - Import maven projects - from a SVN or Git repo
> - multi-module maven projects
> - run on server
> - package vs install
> - update - the magic "update project" that helps get Eclipse and Maven back into agreement
> - adjust profiles - address the Arquillian profile
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 7 months