July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17754) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Aerogear]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17754?page=com.atlassian.jira.plugi... ] Gorkem Ercan closed JBIDE-17754. -------------------------------- Resolution: Done > For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Aerogear] > ------------------------------------------------------ > > Key: JBIDE-17754 > URL: https://issues.jboss.org/browse/JBIDE-17754 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid > Reporter: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.0.Beta3 > > > For JBIDE 4.2.0.Beta3 [Aerogear]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3 > [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Beta3x > git push origin jbosstools-4.2.0.Beta3x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and > * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-17728: ---------------------------------------- [~nickboldt], +1. I'm going to branch JST right now. > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3071) JBDS Installer shouldn't contain source features/plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3071?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3071: ----------------------------- Fix Version/s: 8.0.0.Beta3 > JBDS Installer shouldn't contain source features/plugins > -------------------------------------------------------- > > Key: JBDS-3071 > URL: https://issues.jboss.org/browse/JBDS-3071 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 8.0.0.Beta3 > > > {quote} > So the basic JBDS installer is 70MB fatter. From my understanding it's because we now ship a *huge* forge2 runtime (50MB), Tern, the JVM Monitor and probably some other minor stuff. > Fair enough. But do we *really* need to add all the source features/plugins to the installer? *If* we're legally bound to provide sources for JBoss plugins, couldn't we provide them via an other way? (p2 only). > I reckon we could save ~37 MB by not shipping sources in the installer. I know storage is cheap and d/l speeds are faster but that's not an excuse. > {quote} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17758) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Server]

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17758?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-17758. ------------------------------- Assignee: Rob Stryker Resolution: Done Branched > For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Server] > ---------------------------------------------------- > > Key: JBIDE-17758 > URL: https://issues.jboss.org/browse/JBIDE-17758 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: server > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Labels: task > Fix For: 4.2.0.Beta3 > > > For JBIDE 4.2.0.Beta3 [Server]: Please perform the following tasks: > 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. > Otherwise: > 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3 > [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. > {code} > mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT; > {code} > mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released) > or > mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged) > {code} > 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch; > {code} > git checkout master > git pull origin master > git checkout -b jbosstools-4.2.0.Beta3x > git push origin jbosstools-4.2.0.Beta3x > {code} > 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. > {code} > git checkout master > git pull origin master > {code} > 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*: > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.0.Beta3-SNAPSHOT</version> > </parent> > {code} > Now, your root pom will use parent pom version: > * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and > * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. > 7. Close (do not resolve) this JIRA when done. > 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17728: ------------------------------------ I would prefer that you branch JST today (or early tomorrow if necessary), and work on the new stuff in master. If it becomes ready fast enough that you can merge it over to Beta3x, we can evaluate doing so at that time. > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-17728: ---------------------------------------- [~maxandersen] do we still consider including a few ionic components to the palette for Beta3 or this is only for CR1? > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-17728: ---------------------------------------- {quote}PR looks good but devoid of any functionality.{quote} Yes, this PR is just for review to make sure we understand how we are going to organize ionic/angularJS plugins/features. {quote}Also noticed you depend on Angular in the feature, but not in the plugin.{quote} This was just a comment. I removed it so far. {quote}And you're calling the plugin "Tern Project Adapter" but the feature is "JBoss Tools Java Standard Tools AngularJS" ... seems inconsistent.{quote} Fixed and updated the PR. > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16614) skipRevisionCheckWhenPublishing is misleading in aggregators

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16614?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-16614. ------------------------------ Fix Version/s: 4.2.0.Beta3 (was: 4.2.x) Resolution: Won't Fix Yes, p2diff's power level is over 9000 - but we need to fix it so it works w/ http URLs again. Work to be done in JBIDE-16970. Closing. > skipRevisionCheckWhenPublishing is misleading in aggregators > ------------------------------------------------------------ > > Key: JBIDE-16614 > URL: https://issues.jboss.org/browse/JBIDE-16614 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.Beta3 > > > As the *aggregate* and devstudio-product_* are only run for good reasons (change in a component, or change in aggregation repository - category.xml and other, there is no reason why using the skipRevisionCheckWhenPublishing, which is furthermore a bit error prone and misleading (some manual builds are ignored whereas there has been changes). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17728) HTML5 Palette: Ionic components

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17728?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-17728: ---------------------------------- Attachment: ContentWizBan.png Content.png > HTML5 Palette: Ionic components > ------------------------------- > > Key: JBIDE-17728 > URL: https://issues.jboss.org/browse/JBIDE-17728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Labels: new_and_noteworthy > Fix For: 4.2.0.CR1 > > Attachments: Content.png, ContentWizBan.png > > > http://ionicframework.com/docs/ -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16614) skipRevisionCheckWhenPublishing is misleading in aggregators

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16614?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-16614: ---------------------------------------- I guess this flag will become useless once we are relying on p2 artifacts comparison to decide whether to publish or not. If we all agree p2diff is the better way, then we can reject this jira. > skipRevisionCheckWhenPublishing is misleading in aggregators > ------------------------------------------------------------ > > Key: JBIDE-16614 > URL: https://issues.jboss.org/browse/JBIDE-16614 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.x > > > As the *aggregate* and devstudio-product_* are only run for good reasons (change in a component, or change in aggregation repository - category.xml and other, there is no reason why using the skipRevisionCheckWhenPublishing, which is furthermore a bit error prone and misleading (some manual builds are ignored whereas there has been changes). -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 9 months

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 July 2014