[JBoss JIRA] (JBIDE-19034) Bump org.jboss.tools.forge.m2e version
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19034?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19034:
------------------------------
Description: org.jboss.tools.forge.m2e version needs to become 1.1.2 (was: Currently org.jboss.tools.forge.m2e defines it's own version instead of using the one from the parent pom. This causes problems when using the plugin in multiple branches.)
> Bump org.jboss.tools.forge.m2e version
> ---------------------------------------
>
> Key: JBIDE-19034
> URL: https://issues.jboss.org/browse/JBIDE-19034
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.1.Final
> Reporter: Koen Aers
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.3.0.Alpha1
>
>
> org.jboss.tools.forge.m2e version needs to become 1.1.2
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19034) Make org.jboss.tools.forge.m2e use parent pom version
by Koen Aers (JIRA)
Koen Aers created JBIDE-19034:
---------------------------------
Summary: Make org.jboss.tools.forge.m2e use parent pom version
Key: JBIDE-19034
URL: https://issues.jboss.org/browse/JBIDE-19034
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: forge
Affects Versions: 4.2.1.Final
Reporter: Koen Aers
Assignee: Koen Aers
Priority: Blocker
Fix For: 4.2.2.Final
Currently org.jboss.tools.forge.m2e defines it's own version instead of using the one from the parent pom. This causes problems when using the plugin in multiple branches.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-18274) AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18274?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-18274:
---------------------------------------
I wanted to try again now. So I installed JBT 4.3.0.Alpha1-SNAPSHOT (master nightly) on Eclipse Mars M4 and again, I can reproduce this on my machine (OS X 10.10 Yosemite, oracle java 1.7, wildfly 8.2).
Then I tried exactly the same on a mac mini running the same config and this time it worked ok :(
So right now it seems it's only me (as it was from the beginning), but perhaps Rob could help me debug this so we can see what's going on on my machine.
> AS7/WildFly8/EAP6 with oracle java 7 fails to start when bound to your hostname
> -------------------------------------------------------------------------------
>
> Key: JBIDE-18274
> URL: https://issues.jboss.org/browse/JBIDE-18274
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.3.Final, 4.3.0.Alpha1
>
> Attachments: server-adapter.png, server-editor.png, server-logs.png, server-runtime.png
>
>
> This is a follow up of JBIDE-17935 .
> Previously, Rob fixed this:
> {quote}
> I've surprisingly been able to replicate this and it's a race-condition. I'll need to synchronize some variables in this class here.
> {quote}
> But in this rare case it still fails for me.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months
[JBoss JIRA] (JBIDE-19030) Creation of new RichFaces project results in outdated archetype
by Matej Novotny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19030?page=com.atlassian.jira.plugi... ]
Matej Novotny commented on JBIDE-19030:
---------------------------------------
Works like a charm, thanks for quick fix!
> Creation of new RichFaces project results in outdated archetype
> ---------------------------------------------------------------
>
> Key: JBIDE-19030
> URL: https://issues.jboss.org/browse/JBIDE-19030
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: project-examples
> Affects Versions: 4.2.1.Final
> Reporter: Matej Novotny
> Assignee: Fred Bricon
> Priority: Minor
> Fix For: 4.2.2.Final
>
>
> In JBDS one can create RichFaces project via:
> * File -> New -> Other -> RichFaces Project
> This results in choosing kitchensink archetype for version 4.2.3 which is outdated.
> There were some major changes to RichFaces beggining with version 4.5 so it would be nice if JBDS could make use of any 4.5.x.Final version artifact instead.
> Note: Latest archetype version is 4.5.1.Final and 4.5.2.Final is being staged at the moment, so one of these two should be used I guess.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 3 months