July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17986) Bundled version of m2e-mavenarchiver is broken

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17986: ------------------------------------ Current version in JBT (4.40.0.Beta4 target platform) is org.sonatype.m2e.mavenarchiver_0.16.0.201401211452-signed-20140310144306.jar Proposed version for 4.40.0.CR1-SNAPSHOT target platform) is org.sonatype.m2e.mavenarchiver_0.16.0.201405271551.jar Mirrored: http://download.jboss.org/jbosstools/updates/requirements/m2eclipse-maven... > Bundled version of m2e-mavenarchiver is broken > ---------------------------------------------- > > Key: JBIDE-17986 > URL: https://issues.jboss.org/browse/JBIDE-17986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Affects Versions: 4.2.0.Beta3 > Reporter: Rich DiCroce > > The version of m2e-mavenarchiver that is bundled in JBoss Tools seems to be broken. I was not getting any descriptors generated. Upgrading to the latest version fixes the problem. See http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2eclipse... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-292) Karaf cannot be started in debug

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-292?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBTIS-292: ----------------------------- Description: Cannot start a Fuse server in DEBUG mode, see: FUSETOOLS-1132 Please update JBoss Fuse Server Extension Feature to include version 7.3 which is now fixed. was: Cannot start a Fuse server in DEBUG mode, see: FUSETOOL-1132 Please update JBoss Fuse Server Extension Feature to include version 7.3 which is now fixed. > Karaf cannot be started in debug > -------------------------------- > > Key: JBTIS-292 > URL: https://issues.jboss.org/browse/JBTIS-292 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Fuse IDE > Affects Versions: 7.0.1.GA-JBDSIS > Environment: JBoss Fuse Server Extension Feature 7.2.1.v20140613-0455-H79-Final org.fusesource.ide.server.extensions.feature.feature.group JBoss by Red Hat > Reporter: Jason Shepherd > Priority: Minor > > Cannot start a Fuse server in DEBUG mode, see: > FUSETOOLS-1132 > Please update JBoss Fuse Server Extension Feature to include version 7.3 which is now fixed. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17998) Use better <name> in pom file

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17998?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17998: ------------------------------------ If it's just display info shown during the reactor summary, then +1. Safe for CR1. > Use better <name> in pom file > ----------------------------- > > Key: JBIDE-17998 > URL: https://issues.jboss.org/browse/JBIDE-17998 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > In order to improve identification of jbosstools related reports on SonarQube, the <name> in pom files should be: > * For the root pom, same name as the GitHub repo. Eg jbosstools-webservices, jbosstools-server... > * For the children, <name-of-repo>.<name-of-artifact>. Eg jbosstools-webservices.features, jbosstools-server.jmx.plugins... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17998) Use better <name> in pom file

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17998?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17998: ---------------------------------------- It's far from being a big refactoring. The <name> tag is not changing the structure of the project, it's just a display information. > Use better <name> in pom file > ----------------------------- > > Key: JBIDE-17998 > URL: https://issues.jboss.org/browse/JBIDE-17998 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > In order to improve identification of jbosstools related reports on SonarQube, the <name> in pom files should be: > * For the root pom, same name as the GitHub repo. Eg jbosstools-webservices, jbosstools-server... > * For the children, <name-of-repo>.<name-of-artifact>. Eg jbosstools-webservices.features, jbosstools-server.jmx.plugins... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17998) Use better <name> in pom file

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17998?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17998: ------------------------------------ Not something I'd recommend doing this close to GA. Big refactorings should be done for 8.1 or 9.0 Alpha, not 8.0 CR. So say we all? (cc: [~maxandersen] ) > Use better <name> in pom file > ----------------------------- > > Key: JBIDE-17998 > URL: https://issues.jboss.org/browse/JBIDE-17998 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.2.0.CR1 > > > In order to improve identification of jbosstools related reports on SonarQube, the <name> in pom files should be: > * For the root pom, same name as the GitHub repo. Eg jbosstools-webservices, jbosstools-server... > * For the children, <name-of-repo>.<name-of-artifact>. Eg jbosstools-webservices.features, jbosstools-server.jmx.plugins... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR

by Patrick Decat (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Patrick Decat commented on JBIDE-17724: --------------------------------------- [~rob.stryker] In debug mode, code changes are hot deployed instantly with kepler and JBoss Tools, even inside utility projects. Since luna and JBoss Tools 3, this is no longer the case because of the restart, it takes minutes instead with large apps. > Changes cause full redeployment of exploded WAR > ----------------------------------------------- > > Key: JBIDE-17724 > URL: https://issues.jboss.org/browse/JBIDE-17724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Windows 8.1 x64 > Java 7u51 x64 > Luna x64 > Reporter: Cody Lerum > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.Beta3, 4.2.0.CR1 > > Attachments: JBIDE-17724-JBossEAP5-testcase.tar.bz2, workspace.zip > > > After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final > This prevents any updating of JSF resources or debugging java code. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR

by Patrick Decat (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Patrick Decat commented on JBIDE-17724: --------------------------------------- [~maxandersen] would have been a pleasure but IRC and web relays are blocked at work... > Changes cause full redeployment of exploded WAR > ----------------------------------------------- > > Key: JBIDE-17724 > URL: https://issues.jboss.org/browse/JBIDE-17724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Windows 8.1 x64 > Java 7u51 x64 > Luna x64 > Reporter: Cody Lerum > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.Beta3, 4.2.0.CR1 > > Attachments: JBIDE-17724-JBossEAP5-testcase.tar.bz2, workspace.zip > > > After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final > This prevents any updating of JSF resources or debugging java code. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR

by Patrick Decat (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ] Patrick Decat commented on JBIDE-17724: --------------------------------------- Yep, running in debug mode. Sorry should have specified that. > Changes cause full redeployment of exploded WAR > ----------------------------------------------- > > Key: JBIDE-17724 > URL: https://issues.jboss.org/browse/JBIDE-17724 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Environment: Windows 8.1 x64 > Java 7u51 x64 > Luna x64 > Reporter: Cody Lerum > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.Beta3, 4.2.0.CR1 > > Attachments: JBIDE-17724-JBossEAP5-testcase.tar.bz2, workspace.zip > > > After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final > This prevents any updating of JSF resources or debugging java code. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17944) BrowserSim: Use http: protocol instead of file: for accessing local files

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17944?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-17944: ------------------------------------- [~akazakov], [~maxandersen] Frankly, I do not like the idea of running local files via http for BrowserSim. IMHO our tools (BrowserSim / HTML Preview) should *not* work interchangeably (different tools for different purposes): - BrowserSim is a browser and should work like a browser (local files should be accessed via file protol - just like other browser do it) - If user needs to get web root relative path support for BrowserSim then the project should be deployed on server. After that url should be opened in BrowserSim - HTML Preview is a WSIWYG editor (So it should cover all server specific stuff like webroot paths etc) <BrowserSim: Use http: protocol instead of file: for accessing local files AFAIK ^ this suggestion sounds like transforming BrowserSim to Preview, doesn't it? In terms of CordovaSim. If webroot relative path are supported by Phonegap it should be implemented for CordovaSim. > BrowserSim: Use http: protocol instead of file: for accessing local files > ------------------------------------------------------------------------- > > Key: JBIDE-17944 > URL: https://issues.jboss.org/browse/JBIDE-17944 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim > Reporter: Alexey Kazakov > Assignee: Konstantin Marmalyukov > > Currently, BrowserSim works through file: protocol but this protocol doesn't work well with paths relative to the webroot (which start with "/"). > So if a local file contains any links to local resources (css, js, ...) via relative paths then these resources are not available in BrowserSim. > For example all official ionic example projects use such paths. It makes "open with BrowserSim" feature useless for those projects. > It would be great if BrowserSim uses http: as our HTML5 preview does. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17909) Include Thym 0.1.0 snapshot into jbosstools TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17909?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-17909: ----------------------------------- Description: Include thym 0.1.0 snapshot release into JBossTools TP Reason: plugins moved to Eclipse License and owner: EPL, Eclipse.org Original repo: http://download.eclipse.org/thym/snapshots/ JBoss mirror: http://downloads.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNA... Sources: THyM does not include source bundles/features yet (cf https://bugs.eclipse.org/bugs/show_bug.cgi?id=440753 ) Affected projects: jbosstools-aerogear Include in JBDS: Yes Type of dependency: distribution List of bundles added/removed: /org.eclipse.thym /org.eclipse.thym.android.core /org.eclipse.thym.android.ui /org.eclipse.thym.core /org.eclipse.thym.ios.core /org.eclipse.thym.ios.ui /org.eclipse.thym.ui If applicable: non-p2 repository: non-p2 ids: was: Include thym 0.1.0 snapshot release into JBossTools TP Reason: plugins moved to Eclipse License and owner: EPL, Eclipse.org Original repo: http://download.eclipse.org/thym/snapshots/ JBoss mirror: ?? Sources: THyM does not include source bundles/features yet (cf https://bugs.eclipse.org/bugs/show_bug.cgi?id=440753 ) Affected projects: jbosstools-aerogear Include in JBDS: Yes Type of dependency: distribution List of bundles added/removed: /org.eclipse.thym /org.eclipse.thym.android.core /org.eclipse.thym.android.ui /org.eclipse.thym.core /org.eclipse.thym.ios.core /org.eclipse.thym.ios.ui /org.eclipse.thym.ui If applicable: non-p2 repository: non-p2 ids: > Include Thym 0.1.0 snapshot into jbosstools TP > ---------------------------------------------- > > Key: JBIDE-17909 > URL: https://issues.jboss.org/browse/JBIDE-17909 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.2.0.CR1 > > > Include thym 0.1.0 snapshot release into JBossTools TP > Reason: plugins moved to Eclipse > License and owner: EPL, Eclipse.org > Original repo: http://download.eclipse.org/thym/snapshots/ > JBoss mirror: http://downloads.jboss.org/jbosstools/updates/requirements/thym/0.1.0-SNA... > Sources: THyM does not include source bundles/features yet (cf https://bugs.eclipse.org/bugs/show_bug.cgi?id=440753 ) > Affected projects: jbosstools-aerogear > Include in JBDS: Yes > Type of dependency: distribution > List of bundles added/removed: > /org.eclipse.thym > /org.eclipse.thym.android.core > /org.eclipse.thym.android.ui > /org.eclipse.thym.core > /org.eclipse.thym.ios.core > /org.eclipse.thym.ios.ui > /org.eclipse.thym.ui > If applicable: > non-p2 repository: > non-p2 ids: -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014