[JBoss JIRA] (JBIDE-16011) create install/download section
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16011?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16011:
------------------------------------
[~mmusaji] If we make it easy for users to find JBDS 7.1.Alpha1, they'll use it. And then expect support. Hence my desire to make 'em vanish once .GA comes out. So, yes, making pre-GA stuff available WILL affect GSS.
> create install/download section
> -------------------------------
>
> Key: JBIDE-16011
> URL: https://issues.jboss.org/browse/JBIDE-16011
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: website
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.0.x
>
>
> should have download section that explains how and where to get jbosstools installed.
> Should have a page pr. specific version download and a "archive" view to get directly to the past versions.
> Should not require more than a few lines with urls to add a new download/install.
> archived links for anything not on actual released update site urls (i.e. previous GA's in same release train) could start by just having download zip url (no updatesite)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16011) create install/download section
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16011?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-16011:
------------------------------------
[~xcoulon] We need a way to make the Update Site Zip tab vanish if there are no defined zips.
> create install/download section
> -------------------------------
>
> Key: JBIDE-16011
> URL: https://issues.jboss.org/browse/JBIDE-16011
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: website
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.0.x
>
>
> should have download section that explains how and where to get jbosstools installed.
> Should have a page pr. specific version download and a "archive" view to get directly to the past versions.
> Should not require more than a few lines with urls to add a new download/install.
> archived links for anything not on actual released update site urls (i.e. previous GA's in same release train) could start by just having download zip url (no updatesite)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16351) FixClasspathConfigurator isn't obliged in a newer m2e
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16351?page=com.atlassian.jira.plugi... ]
Snjezana Peco reassigned JBIDE-16351:
-------------------------------------
Assignee: Fred Bricon (was: Snjezana Peco)
> FixClasspathConfigurator isn't obliged in a newer m2e
> -----------------------------------------------------
>
> Key: JBIDE-16351
> URL: https://issues.jboss.org/browse/JBIDE-16351
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: maven
> Affects Versions: 4.2.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Fred Bricon
> Fix For: 4.2.0.Alpha2
>
>
> The FixClasspathConfigurator configurator has been introduced to solve https://issues.sonatype.org/browse/MNGECLIPSE-2433.
> The issue happens with a mavenized seam 2 project that has a flat layout structure.
> This configurator refreshes the old maven facade causing m2e to solve dependencies twice when ever building a project.
> It is the configurator for maven-compiler-plugin so it is called for every Java project.
> Since solving dependencies can take a long, it can slow down building projects up to 15% (depends on the project's dependencies)
> The solution:
> - removing the configurator. The issue is only related to the mavenized Seam projects that aren't included into project examples anymore and a required classpath entry can be manually added(newer m2 versions won't remove the existing classpath entry).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16351) FixClasspathConfigurator isn't obliged in a newer m2e
by Snjezana Peco (JIRA)
Snjezana Peco created JBIDE-16351:
-------------------------------------
Summary: FixClasspathConfigurator isn't obliged in a newer m2e
Key: JBIDE-16351
URL: https://issues.jboss.org/browse/JBIDE-16351
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: maven
Affects Versions: 4.2.0.Alpha1
Reporter: Snjezana Peco
Assignee: Snjezana Peco
Fix For: 4.2.0.Alpha2
The FixClasspathConfigurator configurator has been introduced to solve https://issues.sonatype.org/browse/MNGECLIPSE-2433.
The issue happens with a mavenized seam 2 project that has a flat layout structure.
This configurator refreshes the old maven facade causing m2e to solve dependencies twice when ever building a project.
It is the configurator for maven-compiler-plugin so it is called for every Java project.
Since solving dependencies can take a long, it can slow down building projects up to 15% (depends on the project's dependencies)
The solution:
- removing the configurator. The issue is only related to the mavenized Seam projects that aren't included into project examples anymore and a required classpath entry can be manually added(newer m2 versions won't remove the existing classpath entry).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-12355) JBoss tools website redesign
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-12355:
------------------------------------
More tweaks to readme.adoc:
https://github.com/jbosstools/jbosstools-website/pull/13
> JBoss tools website redesign
> ----------------------------
>
> Key: JBIDE-12355
> URL: https://issues.jboss.org/browse/JBIDE-12355
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 4.0.x
>
> Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png
>
>
> jboss.org/tools have started to have issues scaling on several fronts.
> 1) no clear path to what we want users to download (too many upfront choices)
> 2) we are missing info about what jbosstools actually does
> 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live)
> 4) the content is generally getting very stale
> 5) it is not easy to blog via community.jboss.org - resulting in less content (#4)
> etc. etc.
> 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor.
> We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content.
> https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress.
> http://xcoulon.github.io/jbosstools-website/ <-- current version
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-12355) JBoss tools website redesign
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12355?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-12355:
------------------------------------
Nodejs dependency (or at least dependency on javascript) seen here, when loading the site via `rake preview` on localhost:
thunk - - [13/Jan/2014:10:31:08 EST] "GET / HTTP/1.1" 200 13167
thunk - - [13/Jan/2014:10:31:09 EST] "GET /cache/static.jboss.org/theme/js/libs/jquery/jquery-1.9.1.js HTTP/1.1" 200 268381
thunk - - [13/Jan/2014:10:31:09 EST] "GET /javascripts/bootstrap-community.js HTTP/1.1" 200 127661
> JBoss tools website redesign
> ----------------------------
>
> Key: JBIDE-12355
> URL: https://issues.jboss.org/browse/JBIDE-12355
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: website
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 4.0.x
>
> Attachments: downloads.bmml, downloads.bmml, downloads.bmml, downloads.png, download_archives.bmml, download_archives.bmml, download_archives.png, download_jbosstools_latest.bmml, download_jbosstools_latest.bmml, download_jbosstools_latest.png, features-page-mockup.bmml, features-page-mockup.png, mockupfromjbw.bmml, mockupfromjbw.png, specific-component-features.bmml, specific-component-features.png
>
>
> jboss.org/tools have started to have issues scaling on several fronts.
> 1) no clear path to what we want users to download (too many upfront choices)
> 2) we are missing info about what jbosstools actually does
> 3) updating it requires using magnolia (limited access, no option for easy review or experimenting without pushing fully live)
> 4) the content is generally getting very stale
> 5) it is not easy to blog via community.jboss.org - resulting in less content (#4)
> etc. etc.
> 6) update for releases are a lot of copy/paste and manual updating. if we want to reorg that content it is alot of manual labor.
> We are looking into using awestruct as a way to solve a lot of the technical/practical issues. Other projects like wildfly.org, arquillian.org, aerogear.org, infinispan.org have used that and its improved their publishing process and the content.
> https://github.com/xcoulon/jbosstools-website has a current experimental push of the progress.
> http://xcoulon.github.io/jbosstools-website/ <-- current version
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months