January 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-8) JBossTools Integration Stack :: drools: Verify the component configuration of the initial IS tooling release.

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/JBTIS-8?page=com.atlassian.jira.plugin.sy... ] Kris Verlaenen resolved JBTIS-8. -------------------------------- Resolution: Done > JBossTools Integration Stack :: drools: Verify the component configuration of the initial IS tooling release. > ------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-8 > URL: https://issues.jboss.org/browse/JBTIS-8 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Components: drools > Environment: JBT 4.0 > Reporter: Paul Leacu > Assignee: Kris Verlaenen > > Please verify your component configuration of the JBoss Integration Stack for a JBoss Tools 4.0 target. > Also check that all components are compatible with the upstream components defined in the target platform. > ref: > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... - compositeContent.xml > https://github.com/pleacu/jbosstools-integration-stack-proto/blob/master/... > I'm working on getting this project promoted to jbosstools in github. Unitl then please refer to/fork the urls above. There is a best-guess already specified for each component. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13457) Wrong link in MemberController in default Java EE Web Project

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-13457: ------------------------------------ Summary: Wrong link in MemberController in default Java EE Web Project Key: JBIDE-13457 URL: https://issues.jboss.org/browse/JBIDE-13457 Project: Tools (JBoss Tools) Issue Type: Bug Components: central Affects Versions: 4.0.0.Final Reporter: Jiri Peterka Assignee: Snjezana Peco Fix For: 4.1.0.Alpha1 There is invalid link in MemberControler package org.jboss.tools.examples.controller; ... // EL name // Read more about the @Model stereotype in this FAQ: // http://sfwk.org/Documentation/WhatIsThePurposeOfTheModelAnnotation This link is not valid anymore -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13283) Use Akamai for Target-Platform, Mirror, releases stuff

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13283?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13283: ---------------------------------------- Here is a list of things to mirror: To mirror {code} examples/ Exceptions: nightly/ publishExample.sh requirements/ targetplatform/jbosstoolstarget/ Including: *.Final-SNAPSHOT/ (?<!SNAPSHOT)/ everything that is not SNAPSHOT, anticipating JBIDE-13316 test-runtimes/ updates/ Exceptions: development/ nightly/ m2e-*/ staging/ README.html stable/ (contains only links and discovery definition, volatile content) requirements/ .directory README.building.txt README.html mirror.sh.txt remove.references.xml **/build*.xml {code} > Use Akamai for Target-Platform, Mirror, releases stuff > ------------------------------------------------------ > > Key: JBIDE-13283 > URL: https://issues.jboss.org/browse/JBIDE-13283 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > All our repositories that are either mirrors or target-platform are not updated often. Then we could use Akamai to improve performances. At least these folders would be good: > * http://download.jboss.org/jbosstools/updates/requirements/ > * http://download.jboss.org/jbosstools/updates/stable/ -- 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, 1 month

1
0
0 / 0

[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 updated JBIDE-13266: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-build/pull/43 (was: https://github.com/jbosstools/jbosstools-build/pull/29) New pull request https://github.com/jbosstools/jbosstools-build/pull/43 > 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, 1 month

1
0
0 / 0

[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: ---------------------------------------- Just ran some metrics on "jbosstools-central-maven-examples", both after a "mvn clean" $ mvn -o verify -Dmaven.test.skip=true => 2m59s $ mvn -o verify -Dmaven.test.skip=true -Ppack200 => 3m08s So it seems to be a matter of second to enable pack200. If all integration works well (from component to installer), I'll recommend to make it default, out of a profile. > 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13175) Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13175?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13175: ------------------------------------------ I now implemented the additional check. It'll tell the user that there are local commits that were not pushed to OpenShift yet: !committed-not-published.png! > Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13175 > URL: https://issues.jboss.org/browse/JBIDE-13175 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha1 > > Attachments: 1-local-change.png, committed-not-published.png, no-local-changes.png, no_changes_yes.png > > > # EXEC: launch *OpenShift Application* wizard and create a new application / import existing one > # ASSERT: you get the OpenShift application imported to your workspace > # EXEC: in *Servers* view, select the adapter for your OpenShift application and pick *Publish* from its context menu > Result: > The adapter tells you that there are no local changes. If you look at your local project you'll see in the git-decoration that the local git repo is ahead of 1 commit of the remote, so there is a local commit that could be pushed/published. > !no-local-changes.png! > Expected result: > The adapter should tell you that there are local changes and ask you if you want to publish them. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13175) Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13175?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-13175: ------------------------------------- Attachment: committed-not-published.png > Openshift server adapter: on first push it says that it has no local changes. Even though local clone has 1 commit more than remote > ----------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13175 > URL: https://issues.jboss.org/browse/JBIDE-13175 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.0.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha1 > > Attachments: 1-local-change.png, committed-not-published.png, no-local-changes.png, no_changes_yes.png > > > # EXEC: launch *OpenShift Application* wizard and create a new application / import existing one > # ASSERT: you get the OpenShift application imported to your workspace > # EXEC: in *Servers* view, select the adapter for your OpenShift application and pick *Publish* from its context menu > Result: > The adapter tells you that there are no local changes. If you look at your local project you'll see in the git-decoration that the local git repo is ahead of 1 commit of the remote, so there is a local commit that could be pushed/published. > !no-local-changes.png! > Expected result: > The adapter should tell you that there are local changes and ask you if you want to publish them. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-13329. ------------------------------ Resolution: Done Unified targets no longer include sources or sdk features, only the sdkbundle for GWT. http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.2... http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.3... Closing. > should unified.target includes sources? > --------------------------------------- > > Key: JBIDE-13329 > URL: https://issues.jboss.org/browse/JBIDE-13329 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.0.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not. > However: > {code} > unified-4.2.1.a-20121220.173723-14-unified.target: > <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit"> > multiple-4.2.1.a-20121220.173233-14-multiple.target: > <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true"> > {code} > And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles: > http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/ > Is this intentional? Or is there a bug in your flatten mojo? > https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-... -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13349) JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13349?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13349: ------------------------------------ [~ray.ploski] there are still many links to http://www.redhat.com/promo/eap6beta/ but they redirect to the actual EAP 6 release page, so that's not really a blocker. Still, it's a little weird to cursor over links for EAP 6 and see "beta" when it's a full release -- in fact it's on 6.0.1 already. :) Otherwise the About and Features pages look good. Thanks! > JBoss Way 'about' page refers to JBDS5|OBJ| - can we update this to refer to JBDS6? > ----------------------------------------------------------------------------------- > > Key: JBIDE-13349 > URL: https://issues.jboss.org/browse/JBIDE-13349 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: website > Reporter: Len DiMaggio > Assignee: Ray Ploski > Attachments: Screenshot-2.png > > > See attached screenshot -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-2348) JBDS product page on redhat.com is out of date

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2348?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-2348: ---------------------------------- https://www.redhat.com/apps/store/developers/jboss_developer_studio.html is now up to date (versions removed) but datasheet still mentions Eclipse 3.7 (JBDS 5) instead of Eclipse 4.2 (the latest release, JBDS 6). > JBDS product page on redhat.com is out of date > ---------------------------------------------- > > Key: JBDS-2348 > URL: https://issues.jboss.org/browse/JBDS-2348 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Build, documentation > Affects Versions: 5.0.1.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 6.0.1.GA > > > This page [1] mentions Eclipse 3.6 and JBoss Tools 3, but JBDS 6 uses Eclipse 4.2 and JBoss Tools 4. > [1] https://www.redhat.com/apps/store/developers/jboss_developer_studio.html > Can we get that page updated? -- 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, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2013