[JBoss JIRA] Created: (JBIDE-9639) using Tycho 0.13.0-SNAPSHOT, cannot resolve hibernate when building birt
by Nick Boldt (JIRA)
using Tycho 0.13.0-SNAPSHOT, cannot resolve hibernate when building birt
------------------------------------------------------------------------
Key: JBIDE-9639
URL: https://issues.jboss.org/browse/JBIDE-9639
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: birt
Affects Versions: 3.3.0.M4
Reporter: Nick Boldt
Assignee: Snjezana Peco
Fix For: 3.3.0.M4
$ mvn3 clean install -DtychoVersion=0.13.0-SNAPSHOT -U
ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/Parameter.java (at line 32):[-1,-1]
[ERROR] hibernateTypes.put(TimestampType, Hibernate.TIMESTAMP);
[ERROR] ^^^^^^^^^
[ERROR] Hibernate cannot be resolved to a variable
[ERROR]
[ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/Parameter.java (at line 33):[-1,-1]
[ERROR] hibernateTypes.put(BooleanType, Hibernate.BOOLEAN);
[ERROR] ^^^^^^^^^^^^^^
[ERROR] Type cannot be resolved to a type
[ERROR]
[ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/Parameter.java (at line 33):[-1,-1]
[ERROR] hibernateTypes.put(BooleanType, Hibernate.BOOLEAN);
[ERROR] ^^^^^^^^^
[ERROR] Hibernate cannot be resolved to a variable
[ERROR]
[ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/Parameter.java (at line 90):[-1,-1]
[ERROR] public Type getHibernateType() {
[ERROR] ^^^^
[ERROR] Type cannot be resolved to a type
[ERROR]
[ERROR] /home/nboldt/eclipse/workspace-jboss/jbosstools_trunk/birt/plugins/org.jboss.tools.birt.oda/src/org/jboss/tools/birt/oda/impl/Parameter.java (at line 91):[-1,-1]
[ERROR] return hibernateTypes.get(type);
[ERROR] ^^^^^^^^^^^^^^
[ERROR] Type cannot be resolved to a type
etc.
This could be a problem w/ feature-feature or plugin-plugin dependencies not being clearly stated in the feature.xml or MANIFEST.MF files.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] Created: (JBDS-1799) Hide 3rd party features from JBDS 5 Extras site - only com.jboss.jbds.* features should be exposed
by Nick Boldt (JIRA)
Hide 3rd party features from JBDS 5 Extras site - only com.jboss.jbds.* features should be exposed
--------------------------------------------------------------------------------------------------
Key: JBDS-1799
URL: https://issues.jboss.org/browse/JBDS-1799
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Enhancement
Components: 3rdPartyDependencies, Build, updatesite
Affects Versions: 4.1.0.CR4, 5.0.0.M2
Reporter: Nick Boldt
Assignee: Nick Boldt
Priority: Blocker
Fix For: 4.1.0.GA, 5.0.0.M3
1. instead of including 3rd party features in com.jboss.jbds.* features, include contained plugins.
2. rewrite com.jboss.jbds.* features to list out contents so it's clear what versions of 3rd party stuff are included.
Benefits:
* anything installable from JBDS Extras site is a feature we build and maintain (and test and support).
* to install any non-com.jboss 3rd party feature, must go to 3rd party site (or jboss.org community mirror). Because this is "off the reservation", it's not supported, and users' mileage may vary.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] Created: (JBIDE-6178) releng update site, feature naming conventions
by Darryl Miles (JIRA)
releng update site, feature naming conventions
----------------------------------------------
Key: JBIDE-6178
URL: https://jira.jboss.org/jira/browse/JBIDE-6178
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: updatesite
Affects Versions: 3.1.0.GA
Reporter: Darryl Miles
Priority: Minor
Please consider the impact of users using the "All Update Site" view when installing JBoss plugins.
Some rules to consider:
1) If JBoss creates a new top-level group (which consists entirely of JBoss features) then that top-level name should begin with the word "JBoss".
2) If JBoss reuses a top-level group which belongs to another vendor (for which JBT is built on top of, for example BIRT/Maven/DTP) then you can reuse the top-level group name of the outside vendor, but ensure your features underneath are prefixed with the word "JBoss"."
In enclose a screen grab from 3.1.0.GA which indicates the discrepancy; BIRT is following the above rules, but "Maven Support" is not (and also "Data Services" top level group is not).
The "All in one JBoss" top-level group doesn't really need to follow this convention, since the top level group clearly indicates it is from JBoss and entirely contains JBoss features and those features are a duplicated entrypoint for installation (i.e. each feature also exist somewhere else in the "features to install" tree view). The ambigiouty is over such names as "Maven Support" and "Data Services" in the context of the "all update site view" from the drop-down filter at the top of the page.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months
[JBoss JIRA] (JBIDE-9851) Get JBossTools added to wtp 3.3's list of server adapters :: Indigo
by Nick Boldt (Created) (JIRA)
Get JBossTools added to wtp 3.3's list of server adapters :: Indigo
-------------------------------------------------------------------
Key: JBIDE-9851
URL: https://issues.jboss.org/browse/JBIDE-9851
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: UpStream
Affects Versions: 3.2.0.Final
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 3.2.2.Final, 3.3.0.M4
It seems what happens is you must make use of the org.eclipse.wst.server.discovery plugin. This plugin has a file (discovery.xml) which has "sites", and those sites (such as http://public.dhe.ibm.com/software/websphere/wasce/updates/) seem to be an eclipse update site.
The entry point for this wizard is in the New Runtime wizard. At the top is a hyperlink that reads "Download other adapters" (or something similar). It then queries these sites, and allows you to select one of those available.
It seems the objects are then downloaded as IInstallableUnit's, which is in the org.eclipse.equinox.p2.metadata package.
I kinda lose track of it here, but, I suspect that after this it is downloaded as an actual eclipse bundle and added into the eclipse installation. But I guess I could trace through further
Changes to our site would require adding the category and adding it to certain features in our site.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 4 months