[JBoss JIRA] (JBIDE-13342) kitchensink-html5-mobile - Readme isn't shown when importing for first time with empty local repository
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-13342:
----------------------------------
Summary: kitchensink-html5-mobile - Readme isn't shown when importing for first time with empty local repository
Key: JBIDE-13342
URL: https://issues.jboss.org/browse/JBIDE-13342
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central, project-examples
Affects Versions: 4.0.0.Final
Reporter: Radim Hopp
Assignee: Snjezana Peco
When importing kitchensink-html5-mobile for the first time (with clean maven repo & freshly started JBT), readme isn't shown and project has one error marker:
{noformat}
Project configuration is not up-to-date with pom.xml. Run Maven->Update Project or use Quick Fix
{noformat}
When trying to import for the second time, everything behaves as it should (readme is shown and no errors are present)
--
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
13 years, 3 months
[JBoss JIRA] (JBDS-2440) JBDS 6.0.1 - Archetypes available in JBoss Central are using versions of the BOM which aren't in the EAP 6.0.1 Maven repo
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-2440:
----------------------------------
Summary: JBDS 6.0.1 - Archetypes available in JBoss Central are using versions of the BOM which aren't in the EAP 6.0.1 Maven repo
Key: JBDS-2440
URL: https://issues.jboss.org/browse/JBDS-2440
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: central
Affects Versions: 6.0.1.GA
Reporter: Len DiMaggio
Assignee: Len DiMaggio
Priority: Blocker
Fix For: 6.0.1.GA
This problem will not be solved in a JBDS build, but it must be resolved in time for the JBDS 6.0.1 release.
The issue is that the archetypes didn't get properly checked for EAP 6.0.1. As a result they are still using versions of the BOM which aren't in the EAP 6.0.1 Maven repo.
--
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
13 years, 3 months
[JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-13266 at 1/4/13 5:04 AM:
----------------------------------------------------------------
Pack200 has been used for awhile in many Eclipse projects. Also the tycho pack200 plugins are working well and maintained as part of the CBI. Most issue linked are refering to older JVM version or older p2.
The big gain is:
* 50% less bytes to download at installation (the download speed is currently the bottleneck when installing JBT)
We can also expect:
* Saved some time at build time to get other JBT artifacts
The cost is:
* +30 to 40% size of our repository (consumed on download.jboss.org)
pack200 seems worth giving it a try.
was (Author: mickael_istria):
Pack200 has been used for awhile in many Eclipse projects. Also the tycho pack200 plugins are working well and maintained as part of the CBI. Most issue linked are refering to older JVM version or older p2.
The big gain is:
* more 50% less bytes to download at installation (the download speed is currently the bottleneck when installing JBT)
We can also expect:
* Saved some time at build time to get other JBT artifacts
The cost is:
* +30 to 40% size of our repository (consumed on download.jboss.org)
pack200 seems worth giving it a try.
> Use pack200 to speed up download and install
> --------------------------------------------
>
> Key: JBIDE-13266
> URL: https://issues.jboss.org/browse/JBIDE-13266
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Affects Versions: 4.0.0.CR1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
>
> p2 provides the pack200 stuff, which offers a better compressions for jars, and then that makes downloads faster when installing.
> We should set up our repo to create the pack200'd artifacts.
--
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
13 years, 3 months
[JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13266:
----------------------------------------
Pack200 has been used for awhile in many Eclipse projects. Also the tycho pack200 plugins are working well and maintained as part of the CBI. Most issue linked are refering to older JVM version or older p2.
The big gain is:
* more 50% less bytes to download at installation (the download speed is currently the bottleneck when installing JBT)
We can also expect:
* Saved some time at build time to get other JBT artifacts
The cost is:
* +30 to 40% size of our repository (consumed on download.jboss.org)
pack200 seems worth giving it a try.
> Use pack200 to speed up download and install
> --------------------------------------------
>
> Key: JBIDE-13266
> URL: https://issues.jboss.org/browse/JBIDE-13266
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Affects Versions: 4.0.0.CR1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.0.1.Final, 4.1.0.Alpha1
>
>
> p2 provides the pack200 stuff, which offers a better compressions for jars, and then that makes downloads faster when installing.
> We should set up our repo to create the pack200'd artifacts.
--
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
13 years, 3 months
[JBoss JIRA] (JBIDE-13341) Test the RichFaces Kitchensink archetype upgrade
by Brian Leathem (JIRA)
Brian Leathem created JBIDE-13341:
-------------------------------------
Summary: Test the RichFaces Kitchensink archetype upgrade
Key: JBIDE-13341
URL: https://issues.jboss.org/browse/JBIDE-13341
Project: Tools (JBoss Tools)
Issue Type: Component Upgrade
Components: central
Reporter: Brian Leathem
Assignee: Fred Bricon
Priority: Critical
Fix For: 4.0.0.Final
RichFaces kitchensink archetype 4.2.3.Final-1 is currently in a JBoss staging repository.
The archetype will be promoted out of staging when JBoss tools QA is complete.
--
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
13 years, 3 months
[JBoss JIRA] (JBIDE-13341) Test the RichFaces Kitchensink archetype upgrade
by Brian Leathem (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13341?page=com.atlassian.jira.plugi... ]
Brian Leathem updated JBIDE-13341:
----------------------------------
Description:
RichFaces kitchensink archetype 4.2.3.Final-2 is currently in a JBoss staging repository.
The archetype will be promoted out of staging when JBoss tools QA is complete.
was:
RichFaces kitchensink archetype 4.2.3.Final-1 is currently in a JBoss staging repository.
The archetype will be promoted out of staging when JBoss tools QA is complete.
> Test the RichFaces Kitchensink archetype upgrade
> ------------------------------------------------
>
> Key: JBIDE-13341
> URL: https://issues.jboss.org/browse/JBIDE-13341
> Project: Tools (JBoss Tools)
> Issue Type: Component Upgrade
> Components: central
> Reporter: Brian Leathem
> Assignee: Fred Bricon
> Priority: Critical
> Labels: exampleswarnings
> Fix For: 4.0.0.Final
>
>
> RichFaces kitchensink archetype 4.2.3.Final-2 is currently in a JBoss staging repository.
> The archetype will be promoted out of staging when JBoss tools QA is complete.
--
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
13 years, 3 months
[JBoss JIRA] (JBIDE-12592) El is not revalidated in java comments
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12592?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-12592:
--------------------------------------
Assignee: Victor Rubezhny (was: Alexey Kazakov)
> El is not revalidated in java comments
> --------------------------------------
>
> Key: JBIDE-12592
> URL: https://issues.jboss.org/browse/JBIDE-12592
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.0.0.Alpha1
> Environment: Juno
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha1
>
>
> 1. Create the following class:
> {code}
> package test;
> import javax.enterprise.inject.Produces;
> import javax.inject.Named;
> public class Bean_Broken {
> public void foo() {
> String s = "#{string.ss}";
> }
> @Named
> @Produces
> public String string() {
> return "";
> }
> }
> {code}
> 2. The EL is marked as a problem
> 3. Ctrl + / on {code}String s = "#{string.ss}";{code} Don't save the file.
> 4. FAILURE: There is still a validation problem on the EL.
> 5. Save the file. The problem in the comment is gone.
--
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
13 years, 3 months