[JBoss JIRA] (JBIDE-14610) Design http://download.jboss.org/jbosstools structure
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14610?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-14610 at 5/6/15 12:16 PM:
-------------------------------------------------------------
-Step 1: finish up reorg/refactoring - JBDS-3208-
-Step 2: merge existing pile of devdoc changes in sandbox branch to master-
Step 3: update devdoc w/ new URLs & processes - JBIDE-18846
Step 4: yes, we can add info to all the projects' README.md files, if required.
(Steps 1 & 2 are done.)
was (Author: nickboldt):
Step 1: finish up reorg/refactoring - JBDS-3208
Step 2: merge existing pile of devdoc changes in sandbox branch to master - https://github.com/jbosstools/jbosstools-devdoc/tree/sandbox
Step 3: update devdoc w/ new URLs & processes - JBIDE-18846
Step 4: yes, we can add info to all the projects' README.md files, if required.
> Design http://download.jboss.org/jbosstools structure
> -----------------------------------------------------
>
> Key: JBIDE-14610
> URL: https://issues.jboss.org/browse/JBIDE-14610
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: build, updatesite
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
>
> We have several types of objects which names should be presented in site stucture:
> # Project: jbosstools
> # Project Version: 4.1.0.Beta2,4.1.0.CR1, 4.1.0.Final
> # Subproject: core, soatools
> # Module: base, javaee, central, freemarker and etc.
> # Distribution Type: updates|builds
> # Bits Type: stable|development|nightly
> # Targeted Eclipse: indigo|juno|kepler
> # You name it ...
> Now we mostly use following patterns to publish nightly bits, but not always and not for every project:
> # aggregated update sites: $\{Project Name\}/updates/$\{Bits Type\}/$\{Subproject Name\}/$\{Targeted Eclipse\}
> # jbosstools modules composite nightly update sites are in $\{Project Name\}/builds/staging and it has no structure
> # jbosstools modules builds are published to $\{Project Name\}/builds/$\{Bits Type\} and it seems strategy of publishing is always being changed here, there is folder that match subcomponent name 'core' that was updated last time in February and 'trunk' folder that contains recent bits
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3208.
----------------------------
Resolution: Done
The JBDS build now pushes the standalone installer to devstudio.redhat.com. I believe that's the only remaining thing that was preventing this from being closed. Next up, documentation:
* JBIDE-14610 & JBIDE-18846 - new cascade page to show where to find builds, updates, discovery, etc
> reorg/refactor directories for consistency across JBT/JBDS
> ----------------------------------------------------------
>
> Key: JBDS-3208
> URL: https://issues.jboss.org/browse/JBDS-3208
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 9.0.0.Beta1
>
>
> Be it resolved - we should reorg directories for consistency across JBT/JBDS:
> Latest suggestion:
> * /\{mars,9.0}/
> ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/
> *** /*updates*/
> **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/
> ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/
> *** /*builds*/
> **** /<job-name>/
> ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/
> ---
> Older idea:
> {code}
> <download.jboss.org,devstudio.redhat.com>
> <earlyaccess,updates,discovery>/<mars,9.0>
> /snapshots [replace nightly]
> /staging [rename content for QE, moves to development when approved]
> /development
> /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler
> drop /integration (not used)
> builds/<jobname>/<buildid>
> builds/<jobname>/composite*.xml for last N builds
> targetplatforms/<type>/<version>
> {code}
> Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112
> This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970.
> [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2....
> [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
--
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 Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19756?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19756:
-------------------------------
Sprint: Sprint #3 May 2015
> 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
>
>
> 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] (JBDS-3367) Offline update from 8.0.x fails in installing FeedHenry
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3367?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3367:
----------------------------------
Which version did you last test on April 27? Was it 8.1 or 9.0.Alpha2?
I would like to know if this is fixed in Alpha2 or still a problem.
(Now that 8.1 is released, this probably won't be fixed in that stream.)
> Offline update from 8.0.x fails in installing FeedHenry
> -------------------------------------------------------
>
> Key: JBDS-3367
> URL: https://issues.jboss.org/browse/JBDS-3367
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build, installer
> Affects Versions: 8.1.0.Beta1
> Reporter: Jan Richter
> Assignee: Nick Boldt
> Fix For: 9.0.0.Beta1
>
>
> Updating from 8.0.0, 8.0.1 and 8.0.2 from the update zip causes the following error:
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Tools FeedHenry Integration 1.0.0.Beta1-v20150225-2159-B85 (org.jboss.tools.feedhenry.feature.group 1.0.0.Beta1-v20150225-2159-B85)
> Missing requirement: org.jboss.tools.feedhenry.ui 1.0.0.Beta1-v20150225-2159-B85 requires 'bundle org.jboss.tools.vpe.cordovasim.eclipse 3.6.2' but it could not be found
> Cannot satisfy dependency:
> From: JBoss Tools FeedHenry Integration 1.0.0.Beta1-v20150225-2159-B85 (org.jboss.tools.feedhenry.feature.group 1.0.0.Beta1-v20150225-2159-B85)
> To: org.jboss.tools.feedhenry.ui [1.0.0.Beta1-v20150225-2159-B85]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19717) Visual (diagram) editor for JSR-352 batch job files.
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19717?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19717:
-----------------------------------
Sprint: Sprint #3 May 2015
> Visual (diagram) editor for JSR-352 batch job files.
> ----------------------------------------------------
>
> Key: JBIDE-19717
> URL: https://issues.jboss.org/browse/JBIDE-19717
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: batch
> Affects Versions: 4.3.0.Alpha1
> Reporter: Tomáš Milata
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
>
> A *visual* editor which allows users to *graphically draw* structure of a JSR-352 batch job xml file.
> Existing Sapphire model makes it easy to create a new Sapphire diagram editor that works together with the existing tree editor.
> While the existing tree editor is efficient for editing properties of *single element*, the diagram editor should serve as a useful *visualization* tool that helps with orientation in complex flow *strucures*.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19431) Cannot generate ddl when hibernate console is used
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19431?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-19431:
--------------------------------------
Yes, without using Hibernate console for ddl generation it currently doesn't work when Hibernate 4.0 is used. It's ok for 3.5, 3.6, 3.7.
> Cannot generate ddl when hibernate console is used
> --------------------------------------------------
>
> Key: JBIDE-19431
> URL: https://issues.jboss.org/browse/JBIDE-19431
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.3.Beta1
> Environment: JBDS 8.1.0.Beta1
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> Cannot generate ddl when hibernate console is used. I will investigate further, it worked for 4.3 (and didn't work for lower hibernate versions)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19748) No error or message is displayed when a project namespace has no templates
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19748?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-19748:
---------------------------------------
[~adietish] I logged this while doing feature development and thought this was the issue. Verified feature works without uploaded templates and closed because it didnt generate this issue.
> No error or message is displayed when a project namespace has no templates
> --------------------------------------------------------------------------
>
> Key: JBIDE-19748
> URL: https://issues.jboss.org/browse/JBIDE-19748
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Fix For: 4.3.0.Beta1
>
>
> The following error when no templates are in a project namespace:
> org.eclipse.core.runtime.AssertionFailedException: null argument:
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:85)
> at org.eclipse.core.runtime.Assert.isNotNull(Assert.java:73)
> at org.eclipse.jface.viewers.StructuredViewer.assertElementsNotNull(StructuredViewer.java:583)
> at org.eclipse.jface.viewers.StructuredViewer.getRawChildren(StructuredViewer.java:1001)
> at org.eclipse.jface.viewers.ColumnViewer.getRawChildren(ColumnViewer.java:700)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1349)
> at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:353)
> at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:906)
> at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:617)
> at org.eclipse.jface.viewers.AbstractTreeViewer$1.run(AbstractTreeViewer.java:815)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:791)
> at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:611)
> at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:762)
> at org.eclipse.jface.viewers.AbstractTreeViewer.internalInitializeTree(AbstractTreeViewer.java:1541)
> at org.eclipse.jface.viewers.TreeViewer.internalInitializeTree(TreeViewer.java:790)
> at org.eclipse.jface.viewers.AbstractTreeViewer$5.run(AbstractTreeViewer.java:1525)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1462)
> at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:366)
> at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1423)
> at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged(AbstractTreeViewer.java:1517)
> at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:292)
> at org.eclipse.jface.viewers.StructuredViewer.setInput(StructuredViewer.java:1701)
> at org.jboss.tools.openshift.internal.ui.wizard.application.ResourcesDetailsPage.createTemplatesViewer(ResourcesDetailsPage.java:66)
> at org.jboss.tools.openshift.internal.ui.wizard.application.ResourcesDetailsPage.doCreateControls(ResourcesDetailsPage.java:48)
> at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage.createControl(AbstractOpenShiftWizardPage.java:70)
> at org.eclipse.jface.wizard.Wizard.createPageControls(Wizard.java:175)
> at org.eclipse.jface.wizard.WizardDialog.createPageControls(WizardDialog.java:705)
> at org.eclipse.jface.wizard.WizardDialog.createContents(WizardDialog.java:597)
> at org.eclipse.jface.window.Window.create(Window.java:430)
> at org.eclipse.jface.dialogs.Dialog.create(Dialog.java:1096)
> at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.createWizardDialog(WizardUtils.java:53)
> at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.openWizard(WizardUtils.java:74)
> at org.jboss.tools.openshift.internal.common.ui.utils.WizardUtils.openWizard(WizardUtils.java:67)
> at org.jboss.tools.openshift.internal.ui.command.NewApplicationHandler.execute(NewApplicationHandler.java:36)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> ... 38 more
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19431) Cannot generate ddl when hibernate console is used
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19431?page=com.atlassian.jira.plugi... ]
Jiri Peterka updated JBIDE-19431:
---------------------------------
Steps to Reproduce:
STEP: Create Maven Project with Hibernate Dependencies
STEP: Add JPA facets (Hibernate (JPA 2.0) and sakila h2 db connection profile
STEP: JPA Tools -> Generate Entities from Tables (disable Use Console Configuration)
STEP: JPA Tools -> Generate Tables to entities (use hibernate configuration),
STEP: Finish
ASSERT: DDL file should be generated
was:
STEP: Create Maven Project with Hibernate Dependencies
STEP: Add JPA facets (Hibernate (JPA 2.1) and sakila h2 db connection profile
STEP: JPA Tools -> Generate Entities from Tables (disable Use Console Configuration)
STEP: JPA Tools -> Generate Tables to entities (use hibernate configuration),
STEP: Finish
ASSERT: DDL file should be generated
> Cannot generate ddl when hibernate console is used
> --------------------------------------------------
>
> Key: JBIDE-19431
> URL: https://issues.jboss.org/browse/JBIDE-19431
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.3.Beta1
> Environment: JBDS 8.1.0.Beta1
> Reporter: Jiri Peterka
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
>
> Cannot generate ddl when hibernate console is used. I will investigate further, it worked for 4.3 (and didn't work for lower hibernate versions)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months