[JBoss JIRA] (JBIDE-20185) create just one marketplace entry for jboss tools
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20185?page=com.atlassian.jira.plugi... ]
Andrej Podhradsky commented on JBIDE-20185:
-------------------------------------------
Hi [~mickael_istria], I tried only Luna since there is no Integration Stack for Mars so I tried the following use case
- Install JBDS from marketplace into Luna, then install JBDS-IS from JBoss Central (this is OK)
Note that once we install JBDS into Eclipse from marketplace then we are not able to install JBDS-IS from marketplace (because JBDS-IS entry contains JBDS features).
> create just one marketplace entry for jboss tools
> -------------------------------------------------
>
> Key: JBIDE-20185
> URL: https://issues.jboss.org/browse/JBIDE-20185
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: marketplace
> Affects Versions: 4.3.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Fix For: 4.3.0.Beta1
>
>
> As discussed on JBIDE-20024 it now makes sense to have just one jboss tools entry on markteplace.
> To avoid full loss of stats the entry to rename is JBoss Tools (Luna): http://marketplace.eclipse.org/content/jboss-tools-luna/metrics since it has the highest count by far currently.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-16071) Duplicate cheat sheet options in Project Examples Preferences
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16071?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16071:
----------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.Beta2)
> Duplicate cheat sheet options in Project Examples Preferences
> -------------------------------------------------------------
>
> Key: JBIDE-16071
> URL: https://issues.jboss.org/browse/JBIDE-16071
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 4.1.1.CR1
> Reporter: Michelle Murray
> Assignee: Snjezana Peco
> Fix For: 4.3.0.CR1
>
> Attachments: Central_cheatsheet.png
>
>
> Click Window > Preferences > JBoss Tools > Project Examples.
> The check box options include 'show readme/cheatsheet file' and then further down specifically for cheat sheets radio buttons for cheat sheet behavior.
> !Central_cheatsheet.png!
> I think the labelling of 'show readme/cheatsheet file' is left over from earlier. With the new cheat sheet functionality, I think that option should just read 'show readme file'. And then the radio button 'Always show' etc. deal with cheat sheets.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20045) Software/Update page looks bad in Dark mode
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20045?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-20045:
----------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.Beta2)
> Software/Update page looks bad in Dark mode
> -------------------------------------------
>
> Key: JBIDE-20045
> URL: https://issues.jboss.org/browse/JBIDE-20045
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Beta1
> Reporter: Fred Bricon
> Assignee: Snjezana Peco
> Fix For: 4.3.0.CR1
>
> Attachments: central.png
>
>
> - Enable Eclipse Dark Theme in Preferences > Appearance,
> - Open Central, click on the Software Update page
> - Make sure Early Access is enabled
> - Check this :
> !http://content.screencast.com/users/fbricon/folders/Jing/media/679d7466-cba0-42b8-aaf0-8d6b2f35691a/00000113.png!
> - grey areas around the checkboxes and the titles
> - blue links don't look good
> - Early-Access items are not highlighted (even after fixing JBIDE-20007)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-16225) Let the user select the version of the arquillian container adapter
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16225?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-16225:
----------------------------------
Fix Version/s: 4.3.0.CR1
(was: 4.3.0.Beta2)
> Let the user select the version of the arquillian container adapter
> ---------------------------------------------------------------------
>
> Key: JBIDE-16225
> URL: https://issues.jboss.org/browse/JBIDE-16225
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: arquillian
> Affects Versions: 4.1.1.CR1
> Reporter: Xavier Coulon
> Assignee: Snjezana Peco
> Fix For: 4.3.0.CR1
>
>
> The Arquillian wizard provides users with a list of containers (eg: JBOSS_AS_REMOTE_7.X) that can be used but it misses the version selection (eg: 7.1.1.Final, 7.2.0.Final, etc.).
> I think it's important to let the user choose the version of the 'driver' she needs to use, because it needs to match against the actual version of the container.
> for example, using org.jboss.as:jboss-as-arquillian-container-remote:7.2.0.Final against JBoss AS 7.1.1 will not work.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBTIS-437) Add jsonschema2pojo to TP
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-437?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-437:
----------------------------------
Hey [~nickboldt] - could you please :) take a look at this PR:
https://github.com/jbosstools/jbosstools-locus/pull/43
I think it's close - need to figure out the dependencies. I've modified the locus TP but can't get an Import-Package to find the two packages I've added:
Import-Package: com.fasterxml.jackson.core.jackson-databind,
javax.validation.validation-api
So - the pom from the import of the package lists a set of dependencies here:
https://repo1.maven.org/maven2/org/jsonschema2pojo/jsonschema2pojo-core/0...
Most of these dependencies Fuse Data Trans didn't need to specify in their local libs dependencies capture. Should all of these be part of the Import-Package of the jsonschema2pojo manifest?
Thkx (in advance...)
> Add jsonschema2pojo to TP
> -------------------------
>
> Key: JBTIS-437
> URL: https://issues.jboss.org/browse/JBTIS-437
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: Fuse IDE, target-platform
> Reporter: Keith Babo
> Assignee: Paul Leacu
> Fix For: 4.3.0.Final-TP
>
>
> Fuse Data Transformation tooling relies on jsonschema2pojo to generate model classes from JSON schema and JSON instance documents. At present, this dependency is bundled directly inside the data transformation plugin for Fuse IDE.
> *Project page/sources:* http://www.jsonschema2pojo.org/
> *Version:* 0.4.5 (this is a bit old - current is 0.4.11 and happy to try that if we want to be on the latest/greatest)
> *License and owner:* ALv2
> *Original p2 repo:* unknown
> *JBoss mirror:* unknown
> *Include Sources:* Yes
> *Affected projects:* Fuse IDE
> *Include in JBDS:* unknown
> *Type of dependency:* unknown
> *non-p2 repository:* https://repo1.maven.org/maven2/org/jsonschema2pojo/jsonschema2pojo-core/0...
> There are additional dependencies (see the POM) beyond jsonschema2pojo that will need to be included depending on which parts of jsonschema2pojo are used. For us, that includes:
> - commons-lang3 (although we should be able to use the v2 version which is already present in the TP - need to confirm)
> - jackson-annotations.jar (2.2.0)
> - jackson-core.jar (2.2.0)
> - jackson-databind.jar (2.2.0)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months