[JBoss JIRA] (JBIDE-18148) problem with Hibernate package-info.java TypeDefs
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18148?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18148:
---------------------------------------------
thanks for the bug report - can you tell if this worked for you in previous versions ?
And where do you get the error/warning about type could not be found ? Any error logs, screenshots ?
> problem with Hibernate package-info.java TypeDefs
> -------------------------------------------------
>
> Key: JBIDE-18148
> URL: https://issues.jboss.org/browse/JBIDE-18148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Environment: OSX 10.9.4
> Reporter: Jeffrey Simpson
>
> I just tried out JBoss Developer Studio 8.0.0.Beta3 and it reports all of my Hibernate types that are defined in a package-info as not being found. I get "Type "common-big-decimal" could not be found" where I use it to define an attribute on an entity.
> Here is my Package-info.java
>
> @org.hibernate.annotations.TypeDefs (
>
> {
> @org.hibernate.annotations.TypeDef(name="yfu_boolean", typeClass=org.yfu.util.hibernate.TrueFalseBooleanUserType.class),
> @org.hibernate.annotations.TypeDef(name="integer_date", typeClass=org.yfu.util.hibernate.IntegerDateUserType.class),
> @org.hibernate.annotations.TypeDef(name="integer_local_date", typeClass=org.yfu.util.hibernate.IntegerLocalDateUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_big_decimal", typeClass=org.yfu.util.hibernate.NullableBigDecimalUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_long", typeClass=org.yfu.util.hibernate.NullableLongUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_integer", typeClass=org.yfu.util.hibernate.NullableIntegerUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_string", typeClass=org.yfu.util.hibernate.NullableStringUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_tf_boolean", typeClass=org.yfu.util.hibernate.NullableTFBooleanUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_yn_boolean", typeClass=org.yfu.util.hibernate.NullableYNBoolenaUserType.class),
> @org.hibernate.annotations.TypeDef(name="yfu_boolean_integer", typeClass=org.yfu.util.hibernate.YFUBooleanIntegerUserType.class),
>
> }
> )
> package org.yfu.util.hibernate;
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18148) problem with Hibernate package-info.java TypeDefs
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18148?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18148:
----------------------------------------
Component/s: hibernate
> problem with Hibernate package-info.java TypeDefs
> -------------------------------------------------
>
> Key: JBIDE-18148
> URL: https://issues.jboss.org/browse/JBIDE-18148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Environment: OSX 10.9.4
> Reporter: Jeffrey Simpson
>
> I just tried out JBoss Developer Studio 8.0.0.Beta3 and it reports all of my Hibernate types that are defined in a package-info as not being found. I get "Type "common-big-decimal" could not be found" where I use it to define an attribute on an entity.
> Here is my Package-info.java
>
> @org.hibernate.annotations.TypeDefs (
>
> {
> @org.hibernate.annotations.TypeDef(name="yfu_boolean", typeClass=org.yfu.util.hibernate.TrueFalseBooleanUserType.class),
> @org.hibernate.annotations.TypeDef(name="integer_date", typeClass=org.yfu.util.hibernate.IntegerDateUserType.class),
> @org.hibernate.annotations.TypeDef(name="integer_local_date", typeClass=org.yfu.util.hibernate.IntegerLocalDateUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_big_decimal", typeClass=org.yfu.util.hibernate.NullableBigDecimalUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_long", typeClass=org.yfu.util.hibernate.NullableLongUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_integer", typeClass=org.yfu.util.hibernate.NullableIntegerUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_string", typeClass=org.yfu.util.hibernate.NullableStringUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_tf_boolean", typeClass=org.yfu.util.hibernate.NullableTFBooleanUserType.class),
> @org.hibernate.annotations.TypeDef(name="common_yn_boolean", typeClass=org.yfu.util.hibernate.NullableYNBoolenaUserType.class),
> @org.hibernate.annotations.TypeDef(name="yfu_boolean_integer", typeClass=org.yfu.util.hibernate.YFUBooleanIntegerUserType.class),
>
> }
> )
> package org.yfu.util.hibernate;
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18135) License header plugin
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18135?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-18135:
----------------------------------------
Component/s: common/jst/core
> License header plugin
> ---------------------
>
> Key: JBIDE-18135
> URL: https://issues.jboss.org/browse/JBIDE-18135
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: common/jst/core
> Reporter: Kabir Khan
>
> In WIldFly we have split out the core from the EE part of the project, and there is a plan to relicense the core. I and others who work on WildFly using Eclipse seem to like having both the 'core' and 'EE' projects open in the same workspace. once the relicensing has happened, it will become problematic to maintain the licenses in the mixed workspace.
> We would like to be able to configure some code templates adding the 'core' licenses when a new file is added to the 'core' projects, and to add the lgpl header when a new file is added to the the 'ee' projects.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18176) Ionic palette: New Navigation wizard
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-18176:
---------------------------------------------
Summary: Ionic palette: New Navigation wizard
Key: JBIDE-18176
URL: https://issues.jboss.org/browse/JBIDE-18176
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.2.0.CR1
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18147) Port forwarding cause tearing down the session
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18147?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18147:
------------------------------------------
[~mlabuda] is there a workaround?
> Port forwarding cause tearing down the session
> ----------------------------------------------
>
> Key: JBIDE-18147
> URL: https://issues.jboss.org/browse/JBIDE-18147
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Fix For: 4.2.0.CR2
>
>
> After starting and stopping port forwarding there happens something wrong with session / ssh calling. I found it in Environment variables shell after creating env. variable and clicking on Refresh button. Following error has shown in log and environment variable from table was not removed, although it should be (Refresh button update local environment variables to environment variable of an existing OpenShift application).
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eap"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:871)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:840)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:614)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:843)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:865)
> ... 6 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18147) Port forwarding cause tearing down the session
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18147?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-18147:
-------------------------------------
Fix Version/s: 4.2.0.CR2
> Port forwarding cause tearing down the session
> ----------------------------------------------
>
> Key: JBIDE-18147
> URL: https://issues.jboss.org/browse/JBIDE-18147
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.CR1
> Reporter: Marián Labuda
> Fix For: 4.2.0.CR2
>
>
> After starting and stopping port forwarding there happens something wrong with session / ssh calling. I found it in Environment variables shell after creating env. variable and clicking on Refresh button. Following error has shown in log and environment variable from table was not removed, although it should be (Refresh button update local environment variables to environment variable of an existing OpenShift application).
> {code}
> com.openshift.client.OpenShiftSSHOperationException: Failed to execute remote ssh command "eap"
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:871)
> at com.openshift.internal.client.ApplicationResource.loadPorts(ApplicationResource.java:840)
> at com.openshift.internal.client.ApplicationResource.refresh(ApplicationResource.java:614)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EditEnvironmentVariablesWizardModel.refreshEnvironmentVariables(EditEnvironmentVariablesWizardModel.java:35)
> at org.jboss.tools.openshift.express.internal.ui.wizard.environment.EnvironmentVariablesWizardPage$RefreshEnvironmentVariablesJob.doRun(EnvironmentVariablesWizardPage.java:292)
> at org.jboss.tools.openshift.express.internal.ui.job.AbstractDelegatingMonitorJob.run(AbstractDelegatingMonitorJob.java:36)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: com.jcraft.jsch.JSchException: session is down
> at com.jcraft.jsch.Session.openChannel(Session.java:843)
> at com.openshift.internal.client.ApplicationResource.sshExecCmd(ApplicationResource.java:865)
> ... 6 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBTIS-312) Generate source bundles for IS component features.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-312?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen edited comment on JBTIS-312 at 8/28/14 5:01 PM:
--------------------------------------------------------------------
Just to give context - its always been a requirement for all jboss tools plugins, been done in different ways over the years. SOA-P/JBTIS just haven't enforced it yet.
It is now being requested because we are getting customer cases asking for it.
For existing bundles/releases we can (if expliciltly requested) go back and point to related git/svn commits.
But looking forward this should be incorporated when possible (its worth noting it should be trivial exercise for anything built with tycho - the tricky/heavy part is in making the aggregation consistent at JBTIS level ;)
was (Author: maxandersen):
Just to give context - its always been a requirement for all jboss tools plugins. SOA-P/JBTIS just haven't enforced it yet.
It is now being requested because we are getting customer cases asking for it.
For existing bundles/releases we can (if expliciltly requested) go back and point to related git/svn commits.
But looking forward this should be incorporated when possible (its worth noting it should be trivial exercise for anything built with tycho - the tricky/heavy part is in making the aggregation consistent at JBTIS level ;)
> Generate source bundles for IS component features.
> --------------------------------------------------
>
> Key: JBTIS-312
> URL: https://issues.jboss.org/browse/JBTIS-312
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Fuse IDE, switchyard, teiid
> Affects Versions: 8.0.0.Alpha1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> IS components must generate source bundles for features that will be aggregated (uncategorized) by JBDSIS.
> Courtesy [~nickboldt]:
> How to make maven/tycho build source bundles and features:
> In the upstream projects:
> http://wiki.eclipse.org/Minerva#Source
> Then in the aggregator for JBTIS/JBSIS update site:
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
> As a result, users can install sources from within JBDS rather than
> needing a separate source zip with .java files. Way more useful, if
> you're a java developer using JBDS/Eclipse.
> If you also want to produce a zip of *actual source files* as pulled
> from github, I have a script for that, too.
> See:
> 1. https://github.com/jbdevstudio/jbdevstudio-product/tree/master/sources
> Produces a zip of the contents of the JBDS product build, so people can
> build it offline. Does NOT include upstream sources.
> Result:
> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma...
> (2.4M)
> 2.
> https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub...
> Produces a zip of upstream sources based on upstream project zips. This
> is the old approach, since pulling a previously-built zip doesn't 100%
> guarantee you're getting the correct version AND it requires that the
> upstream project produce a source zip.
> -OR-
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
> Fetches sources directly from github based on the source-reference in
> the specified plugins' manifest.mf files, then collates those sources
> into a single zip.
> Results:
> http://download.jboss.org/jbosstools/builds/nightly/core/master/latest/al...
> (35M)
> Ref:
> (10:02:47 AM) maxandersen: pleacu: for core we've just been providing source bundles for the plugins we provide.
> (10:03:55 AM) pleacu: maxandersen, nboldt: sure - and they use tycho to generate them, correct?
> (10:04:21 AM) maxandersen: pleacu: yes - jboss tools parent pom somewhat "enforces" it.
> (10:05:04 AM) pleacu: maxandersen: ok - I'll look at fuse tooling first since I'm most familiar with that
> (10:05:12 AM) maxandersen: pleacu: and nboldt / mistria explicltily aggregates it in uncategorized so it wont show up in default experience.
> (10:06:43 AM) nboldt: pleacu: fuse tooling doesn't do source bundles
> (10:07:07 AM) nboldt: pleacu: see my email in re: "Where can our customer download source code for jbdevstudio-integration-stack-updatesite-7.0.2.GA.zip?" with details about who does and does not yet produce sources
> (10:08:20 AM) nboldt: maxandersen: actually, we don't "aggregate it in uncategorized" because that implies we're specifically putting into a category called "uncategorized"
> (10:08:43 AM) nboldt: maxandersen: rather, it's just added to the category.xml w/o setting <category>: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... (cc: pleacu )
> Components that generate source bundles:
> http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
> Some that don't:
> http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...
> http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBTIS-312) Generate source bundles for IS component features.
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-312?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-312:
-------------------------------------------
Just to give context - its always been a requirement for all jboss tools plugins. SOA-P/JBTIS just haven't enforced it yet.
It is now being requested because we are getting customer cases asking for it.
For existing bundles/releases we can (if expliciltly requested) go back and point to related git/svn commits.
But looking forward this should be incorporated when possible (its worth noting it should be trivial exercise for anything built with tycho - the tricky/heavy part is in making the aggregation consistent at JBTIS level ;)
> Generate source bundles for IS component features.
> --------------------------------------------------
>
> Key: JBTIS-312
> URL: https://issues.jboss.org/browse/JBTIS-312
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: Fuse IDE, switchyard, teiid
> Affects Versions: 8.0.0.Alpha1
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> IS components must generate source bundles for features that will be aggregated (uncategorized) by JBDSIS.
> Courtesy [~nickboldt]:
> How to make maven/tycho build source bundles and features:
> In the upstream projects:
> http://wiki.eclipse.org/Minerva#Source
> Then in the aggregator for JBTIS/JBSIS update site:
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
> As a result, users can install sources from within JBDS rather than
> needing a separate source zip with .java files. Way more useful, if
> you're a java developer using JBDS/Eclipse.
> If you also want to produce a zip of *actual source files* as pulled
> from github, I have a script for that, too.
> See:
> 1. https://github.com/jbdevstudio/jbdevstudio-product/tree/master/sources
> Produces a zip of the contents of the JBDS product build, so people can
> build it offline. Does NOT include upstream sources.
> Result:
> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio.product_ma...
> (2.4M)
> 2.
> https://github.com/jbosstools/jbosstools-build-ci/blob/master/publish/pub...
> Produces a zip of upstream sources based on upstream project zips. This
> is the old approach, since pulling a previously-built zip doesn't 100%
> guarantee you're getting the correct version AND it requires that the
> upstream project produce a source zip.
> -OR-
> https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat...
> Fetches sources directly from github based on the source-reference in
> the specified plugins' manifest.mf files, then collates those sources
> into a single zip.
> Results:
> http://download.jboss.org/jbosstools/builds/nightly/core/master/latest/al...
> (35M)
> Ref:
> (10:02:47 AM) maxandersen: pleacu: for core we've just been providing source bundles for the plugins we provide.
> (10:03:55 AM) pleacu: maxandersen, nboldt: sure - and they use tycho to generate them, correct?
> (10:04:21 AM) maxandersen: pleacu: yes - jboss tools parent pom somewhat "enforces" it.
> (10:05:04 AM) pleacu: maxandersen: ok - I'll look at fuse tooling first since I'm most familiar with that
> (10:05:12 AM) maxandersen: pleacu: and nboldt / mistria explicltily aggregates it in uncategorized so it wont show up in default experience.
> (10:06:43 AM) nboldt: pleacu: fuse tooling doesn't do source bundles
> (10:07:07 AM) nboldt: pleacu: see my email in re: "Where can our customer download source code for jbdevstudio-integration-stack-updatesite-7.0.2.GA.zip?" with details about who does and does not yet produce sources
> (10:08:20 AM) nboldt: maxandersen: actually, we don't "aggregate it in uncategorized" because that implies we're specifically putting into a category called "uncategorized"
> (10:08:43 AM) nboldt: maxandersen: rather, it's just added to the category.xml w/o setting <category>: https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... (cc: pleacu )
> Components that generate source bundles:
> http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
> Some that don't:
> http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...
> http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months