[JBoss JIRA] (JBIDE-19801) Why is skipTestOrITest only defined for jbosstools-server/as/itests, but not wtp/itests/ ?
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19801:
----------------------------------
Summary: Why is skipTestOrITest only defined for jbosstools-server/as/itests, but not wtp/itests/ ?
Key: JBIDE-19801
URL: https://issues.jboss.org/browse/JBIDE-19801
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.3.0.Beta1
Reporter: Nick Boldt
2 questions:
a) why is the variable skipTestOrITest, and not skipTestsOrITests ?
b) why isn't it defined in your root pom such that it can be reused in other itests/ folders? I see skipITests being used in as/itests/ and wtp/itests/ but only as/itests is resolving the skipTestOrITest flag.
Was there a JIRA to push this into the parent pom, too?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3436) Central in 9.0.beta1 nightly only displays ticketmonster
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3436?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3436:
-----------------------------------
This looks like it's caused by XulRunner on GTK2 not being able to properly display the HTML5 content.
> Central in 9.0.beta1 nightly only displays ticketmonster
> --------------------------------------------------------
>
> Key: JBDS-3436
> URL: https://issues.jboss.org/browse/JBDS-3436
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 9.0.0.Beta1
> Environment: Version: 9.0.0.Beta1
> Build id: Beta1-v20150512-1045-B3188
> Build date: 20150512-1045
> RHEL 6.6
> java -version
> java version "1.7.0_55"
> Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode)
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Attachments: Screenshot-5.3.png, Screenshot-6.2.png, Screenshot-7.2.png, Screenshot-8.png
>
>
> In the Beta1-v20150512-1045-B3188 build - I am seeing multiple issues.
> See the attached screenshots - The user is presented with:
> * A text box that accepts text and discrards it
> * A "gear" icon that is not functional
> * No option that functions other than ticketmonster
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3436) Central in 9.0.beta1 nightly only displays ticketmonster
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3436?page=com.atlassian.jira.plugin.... ]
Fred Bricon closed JBDS-3436.
-----------------------------
Resolution: Duplicate Issue
Closing as duplicate of JBIDE-19773
> Central in 9.0.beta1 nightly only displays ticketmonster
> --------------------------------------------------------
>
> Key: JBDS-3436
> URL: https://issues.jboss.org/browse/JBDS-3436
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 9.0.0.Beta1
> Environment: Version: 9.0.0.Beta1
> Build id: Beta1-v20150512-1045-B3188
> Build date: 20150512-1045
> RHEL 6.6
> java -version
> java version "1.7.0_55"
> Java(TM) SE Runtime Environment (build 1.7.0_55-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 24.55-b03, mixed mode)
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Attachments: Screenshot-5.3.png, Screenshot-6.2.png, Screenshot-7.2.png, Screenshot-8.png
>
>
> In the Beta1-v20150512-1045-B3188 build - I am seeing multiple issues.
> See the attached screenshots - The user is presented with:
> * A text box that accepts text and discrards it
> * A "gear" icon that is not functional
> * No option that functions other than ticketmonster
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19756) jbosstools-src.zip has incomplete/misleading version info in folder names/structure
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19756:
---------------------------------------------
Why do you want to have jbds use local sources and not same as jbosstools ?
And why is it a problem to have you as user access jbdevstudio ? you can't run these builds if you dont have the access.
> jbosstools-src.zip has incomplete/misleading version info in folder names/structure
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19756
> URL: https://issues.jboss.org/browse/JBIDE-19756
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build
> Affects Versions: 4.3.0.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
> Attachments: jbide19756.png, jbide19756_jbds-sources-zip.png, jbide19756_new_subfolders_and_zipfile_name.png
>
>
> Downloading latest jbosstools-src.zip from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... I see multiple files in root named:
> <componentname>_<buildqualifier>_<sha1>
> example:
> jbosstools-javaee_Beta1-v20150501-0413-B767_149f9a46d5c676fd7119515e8b6aa796859955ad
> A few issues with this:
> a) it would have been nice unzipping would not create multiple root level folders. Maybe have a jbosstools-source folder as root ?
> b) the buildqualifier is there but the version string for the component is not. Either put the full version string for that component (not overall jbosstools version) or just leave it as <component>-<sha> and have the root folder state the full version of jbosstools. since non-indulged user would not know this one had to do with 4.3.0.Beta1 or 4.2.3.Beta1 (for example).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19798) include buildinfo.json files inside source zips
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19798?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19798:
---------------------------------------------
I do not follow how output of one mojo is input to another mojo is a problem.
That is how almost all mojo's work. The compiler mojo produces .class files that the assembly mojo packages up.
And these are called even in completely different projects and at different times so not following at all what the problem is.
if we can not safely ensure the consistency of buildinfo.json matches what we build/gather for source zips then we got a bigger and very different problem.
> include buildinfo.json files inside source zips
> -----------------------------------------------
>
> Key: JBIDE-19798
> URL: https://issues.jboss.org/browse/JBIDE-19798
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Nick Boldt
>
> Max asked: {quote}
> [W]here are the build-info.json files to provide the info you were initially partially encoding into the file names ?
> {quote}
> I replied: {quote}
> Adding json files will take more work as they're produced in a different mojo (GenerateRepositoryFacadeMojo.java, not FetchSourcesFromManifests.java), and I'm a bit hesitant to have one mojo depend on another.
> Do you want that the FetchSourcesFromManifests will also FetchJSONFromUpstreamLatestBuildsFolders (hoping that no respins have happened between the start of the aggregate job and the time when the fetch starts) ? Or should I just include target/fullSite/all/repo/buildinfo.json into target/fullSite/all/jbosstools-src.zip ?
> It's already included in the generated update site + update site zip, so I don't have a problem adding it to the src.zip too... except for the fact that we'll have cross-mojo dependencies. This will mean that the aggregate builds (JBT & JBDS) will depend on BOTH mojos, and that they can only be configured to run in a SPECIFIC order. Is that acceptable?
> {quote}
> (From JBIDE-19756)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-19590 at 5/13/15 3:40 PM:
-------------------------------------------------------------
[~dgolovin], Max claims he's told you about Oomph for doing psf importing and a whole lot more. I don't see it in this JIRA or on linked messages, so I'll copy his claim here:
{quote}
[3:30:26 PM] Nick Boldt: have you ever used a project set file (.psf) in eclipse? Denis has this vision for how we can make importing all the crap a CAT user needs to build something like Hibernate (including Base & TP) in one import step into Eclipse
[3:30:44 PM] Max Andersen: yes i've used them.
[3:30:58 PM] Max Andersen: I said oomph is supposed to do it better
[3:31:26 PM] Nick Boldt: I don't know what oomph is relative to psfs
[3:31:41 PM] Max Andersen: psfs just do git clones.
[3:32:20 PM] Max Andersen: oomph psfs, clones targets, configure workingsets, sets target platfrorms, reuses bundle pools so updating takes seconds instead of hours and more.
[3:32:47 PM] Nick Boldt: please tell Denis' jira about oomph so we can move in that direction instead
[3:33:11 PM] Max Andersen: i already told denis about oomph. its in jira.
{quote}
was (Author: nickboldt):
[~dgolovin], Max claims he's told you about Oomph for doing psf importing and a whole lot more. I don't see it in this JIRA or on linked messages, so I'll copy his claim here:
{quote}
[3:30:26 PM] Nick Boldt: have you ever used a project set file (.psf) in eclipse? Denis has this vision for how we can make importing all the crap a CAT user needs to build something like Hibernate (including Base & TP) in one import step into Eclipse
[3:30:44 PM] Max Andersen / conf# 592-775-2520: yes i've used them.
[3:30:58 PM] Max Andersen / conf# 592-775-2520: I said oomph is supposed to do it better
[3:31:26 PM] Nick Boldt: I don't know what oomph is relative to psfs
[3:31:41 PM] Max Andersen / conf# 592-775-2520: psfs just do git clones.
[3:32:20 PM] Max Andersen / conf# 592-775-2520: oomph psfs, clones targets, configure workingsets, sets target platfrorms, reuses bundle pools so updating takes seconds instead of hours and more.
[3:32:47 PM] Nick Boldt: please tell Denis' jira about oomph so we can move in that direction instead
[3:33:11 PM] Max Andersen / conf# 592-775-2520: i already told denis about oomph. its in jira.
{quote}
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.Beta1
>
> Attachments: hibernate-psf-import.mp4
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19590:
------------------------------------
[~dgolovin], Max claims he's told you about Oomph for doing psf importing and a whole lot more. I don't see it in this JIRA or on linked messages, so I'll copy his claim here:
{quote}
[3:30:26 PM] Nick Boldt: have you ever used a project set file (.psf) in eclipse? Denis has this vision for how we can make importing all the crap a CAT user needs to build something like Hibernate (including Base & TP) in one import step into Eclipse
[3:30:44 PM] Max Andersen / conf# 592-775-2520: yes i've used them.
[3:30:58 PM] Max Andersen / conf# 592-775-2520: I said oomph is supposed to do it better
[3:31:26 PM] Nick Boldt: I don't know what oomph is relative to psfs
[3:31:41 PM] Max Andersen / conf# 592-775-2520: psfs just do git clones.
[3:32:20 PM] Max Andersen / conf# 592-775-2520: oomph psfs, clones targets, configure workingsets, sets target platfrorms, reuses bundle pools so updating takes seconds instead of hours and more.
[3:32:47 PM] Nick Boldt: please tell Denis' jira about oomph so we can move in that direction instead
[3:33:11 PM] Max Andersen / conf# 592-775-2520: i already told denis about oomph. its in jira.
{quote}
> Update module's README.md files with information about dependencies to other modules
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-19590
> URL: https://issues.jboss.org/browse/JBIDE-19590
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Affects Versions: 4.3.0.Alpha2
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 4.3.0.Beta1
>
> Attachments: hibernate-psf-import.mp4
>
>
> For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development:
> 1. Set up target platform in preferences
> 2. Import JBT module sources into workspace
> 3. Import required JBT module sources into worksapce
> (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example).
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBTIS-438) Add JAXB XJC to TP
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-438?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-438:
--------------------------------
Assignee: Paul Leacu
> Add JAXB XJC to TP
> ------------------
>
> Key: JBTIS-438
> URL: https://issues.jboss.org/browse/JBTIS-438
> 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.Alpha1
>
>
> Fuse Data Transformation tooling relies on JAXB XJC to generate model classes from XML schema. Looks like jaxb-impl is already in the TP, but jaxb-xjc is not. After some experimentation, it looks like jaxb-xjc is sensitive to the version of jaxb-impl (as in, there are problems when they are not the same version).
> We currently bundle both jaxb-xjc and jaxb-impl inside the data transformation plugin within Fuse IDE. If jaxb-xjc is added to the TP, then we will remove both jars from our plugin.
> *Project page/sources:* https://jaxb.java.net/
> *Version:* 2.2.7 (no hard requirement on this specific version that I know of)
> *License and owner:* CDDL v1.1 and GPL v2
> *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/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months