[JBoss JIRA] (JBTIS-1) 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/JBTIS-1?page=com.atlassian.jira.plugin.sy... ]
Mickael Istria updated JBTIS-1:
-------------------------------
Assignee: Paul Leacu
Priority: Major (was: Blocker)
> Generate target platforms for JBT/JBDS SOA Tooling which include: JBT/JBDS Core TP + last stable Core milestone
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-1
> URL: https://issues.jboss.org/browse/JBTIS-1
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Reporter: Nick Boldt
> Assignee: Paul Leacu
> Labels: f2f2012
> Attachments: JBIDE-11121.tweak.txt, 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, 5 months
[JBoss JIRA] (JBIDE-13329) should unified.target includes sources?
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13329:
----------------------------------------
So which branch should be updated. It's quite difficult to apply suggested PR on master because it's conflicting with the Kepler commit.
About crossing the streams, it makes me more and more in favor of:
* Removing the minimal and maximal profiles in TP parent pom, and choose the child pom directly in builds
* keep all TPs in branch instead of removing the "older" one.
I'm starting to be convinced that the way we deal with TPs in the jbosstools-build repository is very hacky and difficult to maintain. I'll probably soon set up a jbosstools-target-platforms reposioty where 1 branch = 1 version of TP...
> should unified.target includes sources?
> ---------------------------------------
>
> Key: JBIDE-13329
> URL: https://issues.jboss.org/browse/JBIDE-13329
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not.
> However:
> {code}
> unified-4.2.1.a-20121220.173723-14-unified.target:
> <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit">
> multiple-4.2.1.a-20121220.173233-14-multiple.target:
> <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true">
> {code}
> And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles:
> http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/
> Is this intentional? Or is there a bug in your flatten mojo?
> https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-...
--
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, 5 months
[JBoss JIRA] (JBIDE-12474) Allow JBT 3.3.x maven plugins to use m2e 1.2
by Rastislav Wagner (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12474?page=com.atlassian.jira.plugi... ]
Rastislav Wagner closed JBIDE-12474.
------------------------------------
Verified with indigo + m2e 1.2 + m2e-wtp 0.15.3
> Allow JBT 3.3.x maven plugins to use m2e 1.2
> --------------------------------------------
>
> Key: JBIDE-12474
> URL: https://issues.jboss.org/browse/JBIDE-12474
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 3.3.1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Fix For: 3.3.2
>
>
> m2e 1.2 and m2e-wtp 0.16.0 (from eclipse) will be released on sept 28th 2012.
> Current JBT 3.3.x depends on m2eclipse-wtp 0.15.2 (from github) which has a strict version range restriction on m2e : [1.0, 1.2). Most jboss maven plugins also have the same restriction.
> we should remove that defensive restriction on our maven plugins in the 3.3.2 release, regardless if a m2eclipse 0.15.3 can be released too (other people could fork it)
--
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, 5 months
[JBoss JIRA] (JBIDE-13364) Consider changing the way in which BrowserSim uses WebKit engine
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13364?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich updated JBIDE-13364:
-------------------------------------
Description:
A perfect solution for BrowserSim must match the following criteria:
* Be Java-based
* Allow to fully customize the application window [skinning]
* Work on every supported platform (Windows, Mac and Linux)
* Use browser already installed in the system [to avoid library conflicts and reduce the size of our plugins]
* Allow to execute JavaScript and/or modify DOM [to simulate some mobile * JavaScript events and Cordova API]
* Allow to change User-Agent header
* Allow to disable web security or support extensions [for Cordova cross-domain requests]
* Support debugging protocol or support extensions [for better LiveEdit/LiveReload]
* Support debugging protocol or ability to launch Web Inspector/Chrome Developer Tools [for JavaScript debugging capabilities]
Unfortunately, there is no perfect solution, at least I do not know any.
This is the list of the libraries I consider for BrowserSim (+=Pros, -=Cons, ?=questionable):
* Java wrapper for [Chromium Embedded Framework|http://code.google.com/p/javachromiumembedded/]
** + I was able to run it on Windows
** - It failed in a half of a minute :)
** - Not supported since 2010
** ? probably will work better with the most recent version of CEF
** ? looks like there is no Linux support
* [Qt WebKit bindings for SWT|http://code.google.com/p/qtwidgetsinswt/]
** + I was able successfully run on Windows (32-bit) with Qt 4.8 and MinGW
** + At least during my smoketesting it did not fail
** - The plugin page claims that only win32 and cocoa32 are supported
** - requires Qt (and MSVC or MinGW for Windows) libraries to be bundled with it
** - Does not have existing API for invoking JavaScript.
** - Not supported since 2010
** ? I do not know how easy it would be to run it on Linux
** ? I do not know if it will work with Qt 5
* [AppJS|http://appjs.org/] - a JavaScript SDK for creating Chromium based desktop applications
** + Supports Windows, Mac and Linux!
** + Allows to disable web security
** + Has active community
** + Did not fail at my smoketest
** ? need to ensure that applications may be run without borders
* [node-webkit|https://github.com/rogerwang/node-webkit#readme] - the idea is the same as with AppJS - allows to create desktop apps with JavaScript
** + supported by Intel in some way
** ? I did not try it yet
* [Google Chrome Frame|http://www.google.com/chromeframe]
** + the only way to embed _already installed_ Chrome into our application (all other require libraries to be bundled)
** - Windows only
** - [no success to use it as Ole object|http://code.google.com/p/chromium/issues/attachmentText?id=25448&a...]
** ? Probably will work if use it with Browser(SWT.NONE)
* Stay with existing SWT bindings for WebKit
** + We already use it
** + Support all platforms
** + Allow JavaScript to be executed
** + Do not require to be bundled with our plugins
** + Allow skinning
** - Require Safari on Windows [no updates since May 9, 2012]
** - Web security cannot be disabled
** - Do not support extensions
** - Do not support remote debugging protocol
** - Do not support Web Inspector/Chrome Developer Tools
*To conclude:*
* Firstly, moving to a JavaScript SDK potentially could resolve all our problems, but now I do not think it is worth it.
* Secondly, it would be great if we had good SWT bindings for Chromium, but they do not exist. The only way to get them is to implement them by ourself.
* Thirdly, the last option does not look too bad. And probably it does not worth it to create Chromium bindings or to move to another non-Java language. Especially, if we would be able to create a good workaround for cross-domain requests for Cordova, then almost everything else is ok.
* Fourthly, the biggest issue with existing SWT bindings is that Safari is not supported anymore on Windows. It is an OS specific issue and we could consider a replacement of SWT bindings on Windows only (e.g. use Chrome Frame or Qt on Windows).
was:
A perfect solution for BrowserSim must match the following criteria:
* Be Java-based
* Allow to fully customize the application window [skinning]
* Work on every supported platform (Windows, Mac and Linux)
* Use browser already installed in the system [to avoid library conflicts and reduce the size of our plugins]
* Allow to execute JavaScript and/or modify DOM [to simulate some mobile * JavaScript events and Cordova API]
* Allow to change User-Agent header
* Allow to disable web security or support extensions [for Cordova cross-domain requests]
* Support debugging protocol or support extensions [for better LiveEdit/LiveReload and JavaScript debugging capabilities]
Unfortunately, there is no perfect solution, at least I do not know any.
This is the list of the libraries I consider for BrowserSim (+=Pros, -=Cons, ?=questionable):
* Java wrapper for [Chromium Embedded Framework|http://code.google.com/p/javachromiumembedded/]
** + I was able to run it on Windows
** - It failed in a half of a minute :)
** - Not supported since 2010
** ? probably will work better with the most recent version of CEF
** ? looks like there is no Linux support
* [Qt WebKit bindings for SWT|http://code.google.com/p/qtwidgetsinswt/]
** + I was able successfully run on Windows (32-bit) with Qt 4.8 and MinGW
** + At least during my smoketesting it did not fail
** - The plugin page claims that only win32 and cocoa32 are supported
** - requires Qt (and MSVC or MinGW for Windows) libraries to be bundled with it
** - Does not have existing API for invoking JavaScript.
** - Not supported since 2010
** ? I do not know how easy it would be to run it on Linux
** ? I do not know if it will work with Qt 5
* [AppJS|http://appjs.org/] - a JavaScript SDK for creating Chromium based desktop applications
** + Supports Windows, Mac and Linux!
** + Allows to disable web security
** + Has active community
** + Did not fail at my smoketest
** ? need to ensure that applications may be run without borders
* [node-webkit|https://github.com/rogerwang/node-webkit#readme] - the idea is the same as with AppJS - allows to create desktop apps with JavaScript
** + supported by Intel in some way
** ? I did not try it yet
* [Google Chrome Frame|http://www.google.com/chromeframe]
** + the only way to embed _already installed_ Chrome into our application (all other require libraries to be bundled)
** - Windows only
** - [no success to use it as Ole object|http://code.google.com/p/chromium/issues/attachmentText?id=25448&a...]
** ? Probably will work if use it with Browser(SWT.NONE)
* Stay with existing SWT bindings for WebKit
** + We already use it
** + Support all platforms
** + Allow JavaScript to be executed
** + Do not require to be bundled with our plugins
** + Allow skinning
** - Require Safari on Windows [no updates since May 9, 2012]
** - Web security cannot be disabled
** - Do not support extensions
** - Do not support remote debugging protocol
*To conclude:*
* Firstly, moving to a JavaScript SDK potentially could resolve all our problems, but now I do not think it is worth it.
* Secondly, it would be great if we had good SWT bindings for Chromium, but they do not exist. The only way to get them is to implement them by ourself.
* Thirdly, the last option does not look too bad. And probably it does not worth it to create Chromium bindings or to move to another non-Java language. Especially, if we would be able to create a good workaround for cross-domain requests for Cordova, then almost everything else is ok.
* Fourthly, the biggest issue with existing SWT bindings is that Safari is not supported anymore on Windows. It is an OS specific issue and we could consider a replacement of SWT bindings on Windows only (e.g. use Chrome Frame or Qt on Windows).
Agree about Web Inspector/Chrome Developer Tools. Added it to the list.
Note that in the case of Chromium/Chrome based engine the support of debugging protocol implies that Chrome Developer Tools will work automatically (by pointing a WebKit browser to localhost:DEBUGGING_PORT) [1].
[1] https://developers.google.com/chrome-developer-tools/docs/remote-debugging
> Consider changing the way in which BrowserSim uses WebKit engine
> ----------------------------------------------------------------
>
> Key: JBIDE-13364
> URL: https://issues.jboss.org/browse/JBIDE-13364
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Visual Page Editor core
> Reporter: Yahor Radtsevich
> Assignee: Yahor Radtsevich
> Fix For: 4.1.x
>
>
> A perfect solution for BrowserSim must match the following criteria:
> * Be Java-based
> * Allow to fully customize the application window [skinning]
> * Work on every supported platform (Windows, Mac and Linux)
> * Use browser already installed in the system [to avoid library conflicts and reduce the size of our plugins]
> * Allow to execute JavaScript and/or modify DOM [to simulate some mobile * JavaScript events and Cordova API]
> * Allow to change User-Agent header
> * Allow to disable web security or support extensions [for Cordova cross-domain requests]
> * Support debugging protocol or support extensions [for better LiveEdit/LiveReload]
> * Support debugging protocol or ability to launch Web Inspector/Chrome Developer Tools [for JavaScript debugging capabilities]
> Unfortunately, there is no perfect solution, at least I do not know any.
> This is the list of the libraries I consider for BrowserSim (+=Pros, -=Cons, ?=questionable):
> * Java wrapper for [Chromium Embedded Framework|http://code.google.com/p/javachromiumembedded/]
> ** + I was able to run it on Windows
> ** - It failed in a half of a minute :)
> ** - Not supported since 2010
> ** ? probably will work better with the most recent version of CEF
> ** ? looks like there is no Linux support
> * [Qt WebKit bindings for SWT|http://code.google.com/p/qtwidgetsinswt/]
> ** + I was able successfully run on Windows (32-bit) with Qt 4.8 and MinGW
> ** + At least during my smoketesting it did not fail
> ** - The plugin page claims that only win32 and cocoa32 are supported
> ** - requires Qt (and MSVC or MinGW for Windows) libraries to be bundled with it
> ** - Does not have existing API for invoking JavaScript.
> ** - Not supported since 2010
> ** ? I do not know how easy it would be to run it on Linux
> ** ? I do not know if it will work with Qt 5
> * [AppJS|http://appjs.org/] - a JavaScript SDK for creating Chromium based desktop applications
> ** + Supports Windows, Mac and Linux!
> ** + Allows to disable web security
> ** + Has active community
> ** + Did not fail at my smoketest
> ** ? need to ensure that applications may be run without borders
> * [node-webkit|https://github.com/rogerwang/node-webkit#readme] - the idea is the same as with AppJS - allows to create desktop apps with JavaScript
> ** + supported by Intel in some way
> ** ? I did not try it yet
> * [Google Chrome Frame|http://www.google.com/chromeframe]
> ** + the only way to embed _already installed_ Chrome into our application (all other require libraries to be bundled)
> ** - Windows only
> ** - [no success to use it as Ole object|http://code.google.com/p/chromium/issues/attachmentText?id=25448&a...]
> ** ? Probably will work if use it with Browser(SWT.NONE)
> * Stay with existing SWT bindings for WebKit
> ** + We already use it
> ** + Support all platforms
> ** + Allow JavaScript to be executed
> ** + Do not require to be bundled with our plugins
> ** + Allow skinning
> ** - Require Safari on Windows [no updates since May 9, 2012]
> ** - Web security cannot be disabled
> ** - Do not support extensions
> ** - Do not support remote debugging protocol
> ** - Do not support Web Inspector/Chrome Developer Tools
> *To conclude:*
> * Firstly, moving to a JavaScript SDK potentially could resolve all our problems, but now I do not think it is worth it.
> * Secondly, it would be great if we had good SWT bindings for Chromium, but they do not exist. The only way to get them is to implement them by ourself.
> * Thirdly, the last option does not look too bad. And probably it does not worth it to create Chromium bindings or to move to another non-Java language. Especially, if we would be able to create a good workaround for cross-domain requests for Cordova, then almost everything else is ok.
> * Fourthly, the biggest issue with existing SWT bindings is that Safari is not supported anymore on Windows. It is an OS specific issue and we could consider a replacement of SWT bindings on Windows only (e.g. use Chrome Frame or Qt on Windows).
--
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, 5 months
[JBoss JIRA] (JBIDE-4264) String field type should be considered as primary id candidate (now id candidate should be subclass of Number).
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4264?page=com.atlassian.jira.plugin... ]
Max Rydahl Andersen commented on JBIDE-4264:
--------------------------------------------
This is for Generate Hibernate/JPA annotations.
if you have a class:
class MyEntity {
String id;
int number;
String name;
}
then before String id; would not be suggested as primarykey - it would only allow types of subclass number.
But now String id; should be marked with @Id too.
> String field type should be considered as primary id candidate (now id candidate should be subclass of Number).
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-4264
> URL: https://issues.jboss.org/browse/JBIDE-4264
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 3.1.0.M1
> Reporter: Dmitry Geraskov
> Assignee: Koen Aers
> Priority: Minor
> Fix For: 4.0.0.Alpha1
>
>
> CollectEntityInfo class collects information about selected java class. It considers field of java class as primiry id candidate if it has type of Number subclass. Also it should consider fields with type String.
--
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, 5 months
[JBoss JIRA] (JBIDE-13365) Maven Hibernate plugin fails to build against Kepler
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13365?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-13365:
-------------------------------------
Yeah the hibernate plugin is different from the JPA plugin. It provides 2 things :
* enables the hibernate console for projects having hibernate dependencies
* provides Maven-backed Hibernate libraries in the JPA Facet configuration page
> Maven Hibernate plugin fails to build against Kepler
> ----------------------------------------------------
>
> Key: JBIDE-13365
> URL: https://issues.jboss.org/browse/JBIDE-13365
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Reporter: Mickael Istria
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
>
> Using TP from JBIDE-13336 which contain:
> {code}
> <unit id="org.eclipse.jpt.common.feature.feature.group" version="1.3.0.v201210121950-67A-AkF7BFAM7P7EQM"/>
> <unit id="org.eclipse.jpt.common.eclipselink.feature.feature.group" version="1.3.0.v201210121950-35-8s73574E3D38C8"/>
> <unit id="org.eclipse.jpt.jpa.eclipselink.feature.feature.group" version="3.3.0.v201210121950-7K7P0EVVFNVKhJeGepg6NHG"/>
> <unit id="org.eclipse.jpt.jpa.feature.feature.group" version="3.3.0.v201210121950-7W7W4FBBoParY-XLUG4H6NHG"/>
> <unit id="org.eclipse.jpt.jaxb.feature.feature.group" version="1.3.0.v201210121950-57A-AkF7BFAM7P7EQM"/>
> {code},
> I couldn't build the maven/central component because of an issue in org.jboss.tools.maven.hibernate bundle
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project org.jboss.tools.maven.hibernate: Compilation failure: Compilation failure:
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[15,0]
> [ERROR] import org.eclipse.jpt.common.core.JptCommonCorePlugin;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.eclipse.jpt.common.core.JptCommonCorePlugin cannot be resolved
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[18,0]
> [ERROR] import org.eclipse.jpt.jpa.core.platform.JpaPlatformDescription;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.eclipse.jpt.jpa.core.platform.JpaPlatformDescription cannot be resolved
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[25,0]
> [ERROR] public class MavenHibernateLibraryProviderInstallOperationConfig extends MavenLibraryProviderInstallOperationConfig implements JpaLibraryProviderInstallOperationConfig {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type MavenHibernateLibraryProviderInstallOperationConfig must implement the inherited abstract method JpaLibraryProviderInstallOperationConfig.setJpaPlatformConfig(JpaPlatformConfig)
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[25,0]
> [ERROR] public class MavenHibernateLibraryProviderInstallOperationConfig extends MavenLibraryProviderInstallOperationConfig implements JpaLibraryProviderInstallOperationConfig {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type MavenHibernateLibraryProviderInstallOperationConfig must implement the inherited abstract method JpaLibraryProviderInstallOperationConfig.getJpaPlatformConfig()
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[27,0]
> [ERROR] private JpaPlatformDescription jpaPlatformDescription;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[29,0]
> [ERROR] public JpaPlatformDescription getJpaPlatform() {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[30,0]
> [ERROR] return jpaPlatformDescription;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[33,0]
> [ERROR] public void setJpaPlatform(JpaPlatformDescription jpaPlatform) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[34,0]
> [ERROR] this.jpaPlatformDescription = jpaPlatform;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[43,0]
> [ERROR] if (getJpaPlatform() != null) {
> [ERROR] ^^^^^^^^^^^^^^
> [ERROR] The method getJpaPlatform() from the type MavenHibernateLibraryProviderInstallOperationConfig refers to the missing type JpaPlatformDescription
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[44,0]
> [ERROR] for (LibraryValidator libraryValidator : JptCommonCorePlugin.getLibraryValidators(this)) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^
> [ERROR] JptCommonCorePlugin cannot be resolved
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/HibernateLibValidator.java:[26,0]
> [ERROR] if (jpaConfig.getJpaPlatform().getId().contains("hibernate")) {
> [ERROR] ^^^^^^^^^^^^^^
> [ERROR] The method getJpaPlatform() is undefined for the type JpaLibraryProviderInstallOperationConfig
> [ERROR] 12 problems (12 errors)
> {code}
> Please re-assign this issue to me if you think we should use and ship another version of JBT.
--
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, 5 months
[JBoss JIRA] (JBIDE-11907) import.sql should warn me if I have multiple lines as it seems hibernate does not like that, or is this is hibernate issue?
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11907?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen closed JBIDE-11907.
---------------------------------------
Resolution: Rejected
Closing as rejected this issue that is marked as fix in an archived version and is 100% an issue in hibernate core afaics.
> import.sql should warn me if I have multiple lines as it seems hibernate does not like that, or is this is hibernate issue?
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-11907
> URL: https://issues.jboss.org/browse/JBIDE-11907
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Reporter: Jim Tyrrell
> Assignee: Dmitry Geraskov
>
> For example this line does not work:
> insert into Event (id, name, description, major, picture, version) values (2,
> 'Rock concert of the decade',
> 'Get ready to rock...',
> true,
> 'http://dl.dropbox.com/u/65660684/640px-Weir%2C_Bob_(2007)_2.jpg',
> It also has bad quotes in it, the tool should give you a better error message on that also.
--
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, 5 months
[JBoss JIRA] (JBIDE-13365) Maven Hibernate plugin fails to build against Kepler
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13365?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-13365:
---------------------------------------------
Fred - is this functionality even relevant now when m2e-wtp in Kepler will have this ?
> Maven Hibernate plugin fails to build against Kepler
> ----------------------------------------------------
>
> Key: JBIDE-13365
> URL: https://issues.jboss.org/browse/JBIDE-13365
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Reporter: Mickael Istria
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
>
> Using TP from JBIDE-13336 which contain:
> {code}
> <unit id="org.eclipse.jpt.common.feature.feature.group" version="1.3.0.v201210121950-67A-AkF7BFAM7P7EQM"/>
> <unit id="org.eclipse.jpt.common.eclipselink.feature.feature.group" version="1.3.0.v201210121950-35-8s73574E3D38C8"/>
> <unit id="org.eclipse.jpt.jpa.eclipselink.feature.feature.group" version="3.3.0.v201210121950-7K7P0EVVFNVKhJeGepg6NHG"/>
> <unit id="org.eclipse.jpt.jpa.feature.feature.group" version="3.3.0.v201210121950-7W7W4FBBoParY-XLUG4H6NHG"/>
> <unit id="org.eclipse.jpt.jaxb.feature.feature.group" version="1.3.0.v201210121950-57A-AkF7BFAM7P7EQM"/>
> {code},
> I couldn't build the maven/central component because of an issue in org.jboss.tools.maven.hibernate bundle
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project org.jboss.tools.maven.hibernate: Compilation failure: Compilation failure:
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[15,0]
> [ERROR] import org.eclipse.jpt.common.core.JptCommonCorePlugin;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.eclipse.jpt.common.core.JptCommonCorePlugin cannot be resolved
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[18,0]
> [ERROR] import org.eclipse.jpt.jpa.core.platform.JpaPlatformDescription;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.eclipse.jpt.jpa.core.platform.JpaPlatformDescription cannot be resolved
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[25,0]
> [ERROR] public class MavenHibernateLibraryProviderInstallOperationConfig extends MavenLibraryProviderInstallOperationConfig implements JpaLibraryProviderInstallOperationConfig {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type MavenHibernateLibraryProviderInstallOperationConfig must implement the inherited abstract method JpaLibraryProviderInstallOperationConfig.setJpaPlatformConfig(JpaPlatformConfig)
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[25,0]
> [ERROR] public class MavenHibernateLibraryProviderInstallOperationConfig extends MavenLibraryProviderInstallOperationConfig implements JpaLibraryProviderInstallOperationConfig {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type MavenHibernateLibraryProviderInstallOperationConfig must implement the inherited abstract method JpaLibraryProviderInstallOperationConfig.getJpaPlatformConfig()
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[27,0]
> [ERROR] private JpaPlatformDescription jpaPlatformDescription;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[29,0]
> [ERROR] public JpaPlatformDescription getJpaPlatform() {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[30,0]
> [ERROR] return jpaPlatformDescription;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[33,0]
> [ERROR] public void setJpaPlatform(JpaPlatformDescription jpaPlatform) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[34,0]
> [ERROR] this.jpaPlatformDescription = jpaPlatform;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[43,0]
> [ERROR] if (getJpaPlatform() != null) {
> [ERROR] ^^^^^^^^^^^^^^
> [ERROR] The method getJpaPlatform() from the type MavenHibernateLibraryProviderInstallOperationConfig refers to the missing type JpaPlatformDescription
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[44,0]
> [ERROR] for (LibraryValidator libraryValidator : JptCommonCorePlugin.getLibraryValidators(this)) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^
> [ERROR] JptCommonCorePlugin cannot be resolved
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/HibernateLibValidator.java:[26,0]
> [ERROR] if (jpaConfig.getJpaPlatform().getId().contains("hibernate")) {
> [ERROR] ^^^^^^^^^^^^^^
> [ERROR] The method getJpaPlatform() is undefined for the type JpaLibraryProviderInstallOperationConfig
> [ERROR] 12 problems (12 errors)
> {code}
> Please re-assign this issue to me if you think we should use and ship another version of JBT.
--
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, 5 months
_2.jpg){kind=link}