December 2014 - jbosstools-issues

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3208: ---------------------------------- Rationale for having updates/9.0/ be a composite site pointer to updates/9.0/stable/ (and similar for updates/mars/ == updates/mars/stable/ ) is because some people complain that when URLs get too long they stop being "easy" or "consistent". Since the old tradition is to just have updates/<version>, my thought was to avoid these freakouts by having /updates/<version> and /updates/<version>/stable/ result in the same content. Also, <updates,discovery>/*/snapshots can be symlinks (easier to maintain than composite sites) to builds/*/<jobname>/composite*.xml > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > {code} > download.jboss.org > <earlyaccess,updates,discovery>/mars > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/mars/stable is a pointer back into updates/mars) > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > and > {code} > devstudio.redhat.com > <earlyaccess,updates,discovery>/9.0 > /snapshots > /staging > /development > /stable (updates/9.0/stable is a pointer back into updates/9.0) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18864) Upgrade Forge Runtime to 2.12.3.Final

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18864?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18864: ----------------------------------- Labels: respin-a (was: ) > Upgrade Forge Runtime to 2.12.3.Final > ------------------------------------- > > Key: JBIDE-18864 > URL: https://issues.jboss.org/browse/JBIDE-18864 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: respin-a > Fix For: 4.2.1.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18860) Publish to Wildfly AS does not update files

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18860?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-18860: -------------------------------- Attachment: org.example.jbide18860_v3.zip Your sample project has a number of issues, which makes it not deployed properly : * it doesn't build in mvn CLI, because you use a flat layout but didn't set the relativePath to the parent pom in each project * there's a cyclic dependency in build : the parent project is referenced both as a parent and a module This causes the jar project to be missing in the ear and most projects appear as out-of-sync after importing as maven project. Less important, but that will likely cause issues in a real project : the jar project is set to be deployed in both the war/WEB-INF/lib and ear/lib folders. I attached [^org.example.jbide18860_v3.zip], which fixes the deployment issue for me (I left the jar scope in war, though). Please import it as a maven project (you shouldn't need to perform 'maven > update project') and check if you can reproduce the issue with that. > Publish to Wildfly AS does not update files > ------------------------------------------- > > Key: JBIDE-18860 > URL: https://issues.jboss.org/browse/JBIDE-18860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Environment: Windows7 64bit, JDK8u25 > Reporter: Darryl Miles > Priority: Critical > Fix For: 4.2.1.Final, 4.2.2.Final, 4.3.0.Alpha1 > > Attachments: org.example.jbide18860.tar.gz, org.example.jbide18860_v2.tar.gz, org.example.jbide18860_v3.zip > > > I think I am on JBIDE product 4.2.0.Final (but features show as 3.6.0.Final and Plugins as 3.0.0.Final-v20141016) > I have an EAR Maven project published to Wildfly 8.x. > there is a file in the project TOPLEVEL/src/main/application/META-INF/jboss-deployment-structure.xml > If this file is edited and saved, and I perform publish operation on server. The change is never made to the deployments directory. > If I manually delete the file from the deployments direcory, then perform clean operation and publish operation and full publish operation, the file is never re-crearted. > The only way is to REMOVE EAR module from server, clean server, stop server, ADD EAR module to server, publish server, start server. > Now the file is updated. > I also note that I have a number of workspace JPA/JAR projects that should be included in the EAR in the lib/* folder but they are never copied there. > I have found a copy in a folder like workspace\.metadata\.plugins\org.jboss.ide.eclipse.as.core\WildFly_8.1.0.Final\tempRemoteDeploy\ in here are the JARs I expected to find in the server runtime folder wildfly-8.1.0.Final\standalone\deployments\com.company.ear\lib\** > The timestamps on the files in this directory appear to be up-to-date at each publish event. > As a workaround I use "Make As Deployable" on the file workspace\com.company.ear\target\com.company.ear-1.2.3-SNAPSHOW.ear and I use a manual Maven build profile to create this file. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18355) Unexpected chars in freemarker editor

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18355?page=com.atlassian.jira.plugi... ] Jiri Peterka updated JBIDE-18355: --------------------------------- Fix Version/s: (was: 4.2.1.Final) Priority: Minor (was: Major) > Unexpected chars in freemarker editor > ------------------------------------- > > Key: JBIDE-18355 > URL: https://issues.jboss.org/browse/JBIDE-18355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1b, L64 > Reporter: Jiri Peterka > Assignee: Peter Palaga > Priority: Minor > Fix For: 4.3.0.Alpha1 > > Attachments: freemarker-strange-char.ogv, html-template.ftl > > > Strange characters occurs when editing ftl file (check the screencast) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18355) Unexpected chars in freemarker editor

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18355?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-18355: -------------------------------------- [~maxandersen] Yes, I mean a quick diff char or mark. If you compare status from 0:21 with the state of the beginning there there is no diff but quick diff mark is still present. It shouldn't be there IMO. When playing with that more quick diff has some other bugs for example it reports removed line when it is not (not part of the video). I've tried with with plain txt editor with the same file and it worked good there. > Unexpected chars in freemarker editor > ------------------------------------- > > Key: JBIDE-18355 > URL: https://issues.jboss.org/browse/JBIDE-18355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1b, L64 > Reporter: Jiri Peterka > Assignee: Peter Palaga > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > Attachments: freemarker-strange-char.ogv, html-template.ftl > > > Strange characters occurs when editing ftl file (check the screencast) -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18712) Add wildfly archetypes to JBoss Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18712?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18712. ------------------------------ Verified in JBDS 8.0.1.CR1. > Add wildfly archetypes to JBoss Central > --------------------------------------- > > Key: JBIDE-18712 > URL: https://issues.jboss.org/browse/JBIDE-18712 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Fred Bricon > Assignee: Fred Bricon > Fix For: 4.2.1.CR1 > > > JBoss Central doesn't propose the Wildfly archetypes when a Wildfly runtime is selected, even though they have been released in Maven Central : http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.wildfly.archetype%22 > They should be added to stacks.yaml, with environment: web-ee7 for the pure webapp and environment: full-ee7 for the EAR -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18864) Upgrade Forge Runtime to 2.12.3.Final

by George Gastaldi (JIRA)

George Gastaldi created JBIDE-18864: --------------------------------------- Summary: Upgrade Forge Runtime to 2.12.3.Final Key: JBIDE-18864 URL: https://issues.jboss.org/browse/JBIDE-18864 Project: Tools (JBoss Tools) Issue Type: Component Upgrade Components: forge Reporter: George Gastaldi Assignee: George Gastaldi Fix For: 4.2.1.CR1 -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18777) Ensure features and plugins have upversioned since 4.2.0.Final release [Central]

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18777?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-18777. ------------------------------ Verified in JBDS 8.0.1.CR1 > Ensure features and plugins have upversioned since 4.2.0.Final release [Central] > -------------------------------------------------------------------------------- > > Key: JBIDE-18777 > URL: https://issues.jboss.org/browse/JBIDE-18777 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Affects Versions: 4.2.1.CR1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.2.1.CR1 > > > You have commits in your 4.2.x branch which happened AFTER 4.2.0.Final. Yet your root pom is still at version 4.2.0, and your affected plugins' versions are not incremented. > https://github.com/jbosstools/jbosstools-central/commits/jbosstools-4.2.x > Please bump your stuff to a .1 version to reflect the fact you're doing maintenance in the 4.2.x branch. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18858) Update Thym release on TP [4.2.1 CR1a]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18858?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18858: ------------------------------------ +1 for PRs. [~mickael_istria] should we also rename this target platform from CR2-SNAPSHOT to Final-SNAPSHOT so it's ready for the release of 4.2.1/8.0.1 in 2 weeks? > Update Thym release on TP [4.2.1 CR1a] > -------------------------------------- > > Key: JBIDE-18858 > URL: https://issues.jboss.org/browse/JBIDE-18858 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.2.1.CR1 > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.1.CR1, 4.3.0.Alpha1 > > > *Reason:* Update Eclipse Thym to pickup fixes to JBDS issues > *License and owner:* Eclipse > *Original p2 repo:* http://download.eclipse.org/thym/snapshots (buildId=201412020246) > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNAP... > *Sources:* https://github.com/eclipse/thym > *Affected projects:* jbosstools-aerogear > *Include in JBDS:* YES > *Type of dependency:* build > *List of bundles added/removed:* > {code} > TODO > {code} -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3240) Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3240?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3240: ----------------------------------- archetype versions depend on selected runtimes. By default, we fallback on the lowest common denominator (EE6 app that deploys on AS7) > Provide latest EAP 6.3 / WFK 2.6 archetypes in latest JBDS 8 Central > -------------------------------------------------------------------- > > Key: JBDS-3240 > URL: https://issues.jboss.org/browse/JBDS-3240 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: central > Affects Versions: 8.0.0.GA > Reporter: Marek Novotny > Assignee: Fred Bricon > Fix For: 8.0.1.GA > > > JBDS 8 aka JBoss Central provide by default old EAP/WFK archetype and not the latest 6.3.0.GA/2.6.0.Final by default. > For instance I click on HTML5 project in Start from Scratch in JBoss Central: > it launches wizard dialog where the archetype is org.jboss.tools.example.html5:jboss-as-kitchensink-html5-mobile:1.0.4.Final-redhat-wfk-2 version -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 8 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 December 2014