[JBoss JIRA] (JBDS-4209) Request for Administrator credentials should be shown once
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4209:
-----------------------------------
Summary: Request for Administrator credentials should be shown once
Key: JBDS-4209
URL: https://issues.jboss.org/browse/JBDS-4209
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 10.2.0.GA
Environment: macOS
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 10.3.0.AM1
Current implementation asks for administrator credentials for both vagrant and virtualbox installation. The request should be shown only once per installation.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23481) build target platform sources site (for use with TP and PDE Source Lookup)
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23481?page=com.atlassian.jira.plugi... ]
Lukáš Valach closed JBIDE-23481.
--------------------------------
Verified in 4.4.2.Final. I performed a p2diff and it seems that a lot of sources has been added.
> build target platform sources site (for use with TP and PDE Source Lookup)
> --------------------------------------------------------------------------
>
> Key: JBIDE-23481
> URL: https://issues.jboss.org/browse/JBIDE-23481
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.2.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.2.Final
>
>
> So that dev and qe can use Fred's PDE source lookup tool [1] to grab source bundles on demand (instead of having to build a target platform locally w/ all the sources [2]), we need to:
> [1] https://github.com/fbricon/pde.source.lookup/
> [2] https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ...
> * build a targetplatform with all the sources
> * split that repo into two pieces: all the .source files, and everything else
> * regen the metadata (featureandbundlepublisher) in each new repo so that all the features/plugins are uncategorized
> OR...
> * build a targetplatform without the sources
> * transform the .target file so that each IU ends with .source
> * build the target platform repo from the new .target file
> * verify that sources repo includes the sources of nested features, and those features' plugins' sources too
> ----
> Then once we have the targetplatform.source repo, publish that and verify it works with the PDE Source Lookup plugin:
> 1. install the PDE source lookup plugin
> 2. Window > Prefs > Update > Avail Software Sites > Add the new tp.source site
> 3. for something you want sources, use the plugin and see if it can resolve soources
> ----
> Then, if that works, we can consider adding the new tp.source site into the JBT/devstudio composite sites, along with jbt + tp + central + central tp (or ds + ds tp + central + central tp) as a 5th child site.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23479) Seam doesn't compile because of changes in Hibernate
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23479?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-23479.
------------------------------------
verified on jenkins
> Seam doesn't compile because of changes in Hibernate
> ----------------------------------------------------
>
> Key: JBIDE-23479
> URL: https://issues.jboss.org/browse/JBIDE-23479
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, seam2
> Affects Versions: 4.4.2.AM3
> Reporter: Alexey Kazakov
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.4.2.Final
>
>
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.26.0:compile (default-compile) on project org.jboss.tools.seam.ui: Compilation failure: Compilation failure:
> [ERROR] /home/igels/Projects/jbt-4.0/contribution-neon/jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/DBTablesViewer.java:[158]
> [ERROR] List schemaNames = tablesCollector.getMatchingSchemaNames(catalog.getName(), buildSettings.getDefaultSchemaName());
> [ERROR] ^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method getDefaultSchemaName() is undefined for the type ISettings
> [ERROR] /home/igels/Projects/jbt-4.0/contribution-neon/jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/DBTablesViewer.java:[221]
> [ERROR] reader.readDatabaseTables(tablesCollector, buildSettings.getDefaultCatalogName(), buildSettings.getDefaultSchemaName());
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method getDefaultCatalogName() is undefined for the type ISettings
> [ERROR] /home/igels/Projects/jbt-4.0/contribution-neon/jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/DBTablesViewer.java:[221]
> [ERROR] reader.readDatabaseTables(tablesCollector, buildSettings.getDefaultCatalogName(), buildSettings.getDefaultSchemaName());
> [ERROR] ^^^^^^^^^^^^^^^^^^^^
> [ERROR] The method getDefaultSchemaName() is undefined for the type ISettings
> [ERROR] 3 problems (3 errors)
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please read the following articles:
> [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
> [ERROR]
> [ERROR] After correcting the problems, you can resume the build with the command
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-4208) Detection for installed components always counts cygwin as detected on macOS
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4208:
-----------------------------------
Summary: Detection for installed components always counts cygwin as detected on macOS
Key: JBDS-4208
URL: https://issues.jboss.org/browse/JBDS-4208
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: platform-installer
Affects Versions: 10.2.0.GA
Environment: macOS
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 10.3.0.AM1
It means confirmation page message about detected components always increase number of detected components by one. If only Java is detected it would say "We found 2 installed components" one is Java and another one is Cygwin which is not visible under macOS.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months