[JBoss JIRA] (JBIDE-13292) No version in BrowseSim about dialog
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-13292:
------------------------------------
Summary: No version in BrowseSim about dialog
Key: JBIDE-13292
URL: https://issues.jboss.org/browse/JBIDE-13292
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Visual Page Editor core
Affects Versions: 4.0.0.Final
Environment: JBDS 6.0.0.GA, L64
Reporter: Jiri Peterka
Assignee: Yahor Radtsevich
Priority: Minor
Fix For: 4.0.x
No version in BrowseSim About dialog, see screenshot
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13291) AlwaysOnTop ability for BrowserSim
by Jiri Peterka (JIRA)
Jiri Peterka created JBIDE-13291:
------------------------------------
Summary: AlwaysOnTop ability for BrowserSim
Key: JBIDE-13291
URL: https://issues.jboss.org/browse/JBIDE-13291
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: Visual Page Editor core
Affects Versions: 4.0.0.Final
Reporter: Jiri Peterka
Assignee: Yahor Radtsevich
Fix For: 4.0.x
Always on Top or some pin functionality would useful in BrowserSim menu.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-13290) Incorrect module status shown while server is stopped
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-13290:
-----------------------------------
Summary: Incorrect module status shown while server is stopped
Key: JBIDE-13290
URL: https://issues.jboss.org/browse/JBIDE-13290
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 4.0.0.Final
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Minor
Fix For: 4.1.0.Alpha1
Small cosmetic bug when adding a webapp/ear to a stopped server, the new module appears as started, when it's obviously not.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-11121:
----------------------------------------
Hey Bob.
The target-platform (defined by a .target file) is the way how Tycho will resolve dependencies. We are trying to use a target-platforms that is based on JBoss Tools target-platform, to ensure the SOA/Integration components are compatible with JBoss Tools and then that all JBoss Eclipse stuff can be installed together.
So I've made a target-platform that I hope should work for your SOA projects.
If you feel a bit lost with that, can you please tell me where I can get your code, so I'll give it a try.
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11121
> URL: https://issues.jboss.org/browse/JBIDE-11121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: SOA Tooling
> Affects Versions: 3.3.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Labels: f2f2012
> Fix For: 4.0.x
>
> Attachments: ModeShapeToolsBuildLog.txt
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone.
> 2. JBDS Core TP + last stable JBDS Core milestone.
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months
[JBoss JIRA] (JBIDE-11121) Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
by Robert (Bob) Brodt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11121?page=com.atlassian.jira.plugi... ]
Robert (Bob) Brodt commented on JBIDE-11121:
--------------------------------------------
Hey y'all...I know you THINK I'm supposed to know what all of this means, but really I don't have much of a clue. I know there's this thing called a ".target" file which I can create using an eclipse wizard, but beyond that...all of the words here parse like english (well, most of them) but they don't really make much sense to me. What exactly am I supposed to do here? I tried following the steps 1-5 described by Mickael above, but haven't gotten very far. What I see is
[ERROR] Plugin org.jboss.tools.tycho-plugins:target-platform-utils:0.0.1-SNAPSHOT or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.jboss.tools.tycho-plugins:target-platform-utils:jar:0.0.1-SNAPSHOT: Could not find artifact org.jboss.tools.tycho-plugins:tar
get-platform-utils:pom:0.0.1-SNAPSHOT in tycho-snapshots (https://oss.sonatype.org/content/groups/public/) -> [Help 1]
which makes not much sense to me
HELP 1!
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11121
> URL: https://issues.jboss.org/browse/JBIDE-11121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: SOA Tooling
> Affects Versions: 3.3.0.Beta1-SOA
> Reporter: Nick Boldt
> Assignee: Douglas Palmer
> Priority: Blocker
> Labels: f2f2012
> Fix For: 4.0.x
>
> Attachments: ModeShapeToolsBuildLog.txt
>
>
> Generate target platforms for JBT/JBDS SOA Tooling which include:
> 1. JBT Core TP + last stable JBT Core milestone.
> 2. JBDS Core TP + last stable JBDS Core milestone.
> Then, all SOA Component jobs should be rekeyed to use these new TPs when building instead of the JBT/JBDS Core ones.
> This includes Drools, which currently builds against Helios instead of Indigo, and Savara, which has requirements which are not as yet in the JBT/JBDS Core TPs (eg., GMF and Graphiti).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 4 months