[JBoss JIRA] (JBDS-3078) 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3078?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3078:
-------------------------------------------
I've pinged [~james.cobb] (can't rely on @mentions only for priority stuff :)
He is contacting Red Hat brand to see if we can get the larger versions from the old artwork. He will update this jira.
> 7 icon(s) not replaced in laucher.exe @ com.jboss.devstudio.core.site
> ---------------------------------------------------------------------
>
> Key: JBDS-3078
> URL: https://issues.jboss.org/browse/JBDS-3078
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, updatesite
> Affects Versions: 8.0.0.Beta3
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Fix For: 8.0.0.CR1
>
> Attachments: 128_jbds_icon.png
>
>
> Building locally:
> {code}
> [INFO] --- tycho-p2-publisher-plugin:0.20.0:publish-products (default-publish-products) @ com.jboss.devstudio.core.site ---
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron9054877340821028927/launcher.exe using /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/products/com.jboss.devstudio.core.package/jbds.ico
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron489909634983575622/launcher.exe using /home/nboldt/eclipse/workspace-jboss/jbdevstudio-github-master/jbdevstudio-product/site/target/products/com.jboss.devstudio.core.package/jbds.ico
> {code}
> Building in Jenkins:
> {code}
> [INFO] --- tycho-p2-publisher-plugin:0.20.0:publish-products (default-publish-products) @ com.jboss.devstudio.core.site ---
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron5040285231221120320/launcher.exe using /qa/hudson_workspace/workspace/devstudio.product_master/sources/product/site/target/products/com.jboss.devstudio.core.package/jbds.ico
> Error - 7 icon(s) not replaced in /tmp/p2.brandingIron8242740933405392439/launcher.exe using /qa/hudson_workspace/workspace/devstudio.product_master/sources/product/site/target/products/com.jboss.devstudio.core.package/jbds.ico{code}
> Is this a problem?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[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 edited comment on JBIDE-17724 at 7/30/14 4:48 AM:
----------------------------------------------------------------
Well, it works fine with eclipse kepler and JBoss Tools. We are not using m2e because large Maven projects (> 500 POMs :() take hours to import and update with a decent computer (Core2Quad 3GHz, 16GB RAM and an SSD) . I'll give it a try with luna.
Anyway, importing the sample project with m2e results the same.
was (Author: pdecat):
Well, it works fine with eclipse kepler and JBoss Tools. We are not using m2e because large Maven projects (> 500 POMs :() take hours to import and update. I'll give it a try with luna.
Anyway, importing the sample project with m2e results the same.
> 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)
11 years, 8 months
[JBoss JIRA] (JBIDE-17998) Use better <name> in pom file
by Mickael Istria (JIRA)
Mickael Istria created JBIDE-17998:
--------------------------------------
Summary: 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
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)
11 years, 8 months
[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 reassigned JBIDE-17998:
--------------------------------------
Assignee: Mickael Istria
> 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)
11 years, 8 months
[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 edited comment on JBIDE-17724 at 7/30/14 4:41 AM:
----------------------------------------------------------------
Well, it works fine with eclipse kepler and JBoss Tools. We are not using m2e because large Maven projects (> 500 POMs :() take hours to import and update. I'll give it try with luna.
Anyway, importing the sample project with m2e results the same.
was (Author: pdecat):
Well, it works fine with eclipse kepler and JBoss Tools. We are not using m2e because large Maven projects (> 500 POMs :() take hours to import and update.
Anyway, importing the sample project with m2e results the same.
> 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)
11 years, 8 months
[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 edited comment on JBIDE-17724 at 7/30/14 4:41 AM:
----------------------------------------------------------------
Well, it works fine with eclipse kepler and JBoss Tools. We are not using m2e because large Maven projects (> 500 POMs :() take hours to import and update. I'll give it a try with luna.
Anyway, importing the sample project with m2e results the same.
was (Author: pdecat):
Well, it works fine with eclipse kepler and JBoss Tools. We are not using m2e because large Maven projects (> 500 POMs :() take hours to import and update. I'll give it try with luna.
Anyway, importing the sample project with m2e results the same.
> 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)
11 years, 8 months
[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:
---------------------------------------
Well, it works fine with eclipse kepler and JBoss Tools. We are not using m2e because large Maven projects (> 500 POMs :() take hours to import and update.
Anyway, importing the sample project with m2e results the same.
> 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)
11 years, 8 months
[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17724:
---------------------------------------------
The example does not build cleanly, i've cloned it and pushed at https://github.com/maxandersen/JBIDE-17724 for now so can be used for testing.
> 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)
11 years, 8 months
[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17724:
---------------------------------------------
Please do not do step #2 - that is not supported by eclipse for *years* now. the output of this will *not* work.
Please use m2e-wtp to import it.
That said - I would like to see if we can detect it and warn.
> 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)
11 years, 8 months
[JBoss JIRA] (JBTIS-292) Karaf cannot be started in debug
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-292?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-292:
-------------------------------------------
moved to JBTIS which is where Fuse is bundled.
> 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:
> FUSETOOL-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)
11 years, 8 months