[JBoss JIRA] (JBIDE-19789) User Defined Modules are not loading in Eclipse
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19789?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-19789:
-----------------------------------
Component/s: server
> User Defined Modules are not loading in Eclipse
> ------------------------------------------------
>
> Key: JBIDE-19789
> URL: https://issues.jboss.org/browse/JBIDE-19789
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Environment: java 1.8, wildfly 8.1 , Mysql
> Reporter: Raj Kumar
>
> Hi , i want to load the Application server Libraries in Java Build Path in eclipse,
>
> i have 5 applications in eclipse which shares common libraries,
> i can't put all the libraries in each project lib folder,
> so i want to add the libraries in Wildfly Application server using modules.
>
> This is my module.xml file add added the lib at WILDFLY_HOME/modules/system/layers/base/com/mysql/main/mysql-connector-java-5.1.23-bin.jar
>
> <?xml version="1.0" encoding="UTF-8"?>
> <module xmlns="urn:jboss:module:1.1" name="com.mysql">
> <resources>
> <resource-root path="mysql-connector-java-5.1.23-bin.jar"/>
> </resources>
> <dependencies>
> <module name="javax.api"/>
> <module name="javax.transaction.api"/>
> </dependencies>
> </module>
>
> After Restarting the server,this module is not loading in Eclipse Build path.
> Can any one knows what wrong with this modules ?
> In Wildfly i have some predefined modules, those are loading in build path successfully, but user-defined modules are not loading ?
> why ?
> - See more at: https://developer.jboss.org/thread/257825?sr=inbox#sthash.MWLbzbco.dpuf
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19757) Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19757:
------------------------------------
There's no need to change the URL inside WTP.
If we can't use a simple symlink to the JBT site (due to performance concerns), then instead we continue to use a symlink to the webtools-site (../../static/mars/development/updates/webtools/4.3.0.Alpha2).
IMHO, there's no reason to switch to using a composite site when a symlink is just as good (better, in fact, because less metadata to read) and easier to change (one symlink to delete/create vs. 2 composite*.xml files to edit).
So... when Beta1 is released, we can switch the symlink to point to the webtools Beta1 site & get some performance numbers.
The, we can switch the symlink to point at the JBT Beta1 site & get some performance numbers.
If the result says we need to revert, we can do so. If not, we can move ahead w/ deleting the webtools-site config from Github and from the child-sites Jenkins jobs.
Sound good?
> Use jbosstools aggregate site instead of special webtools-site for WTP's AS server discovery
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-19757
> URL: https://issues.jboss.org/browse/JBIDE-19757
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, server
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19425) Error when loading projects in Central with Java 9
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19425?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-19425.
---------------------------------
Fix Version/s: 4.3.0.Beta2
(was: LATER)
Resolution: Done
Related to upstream bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=466683
I managed to create project examples without issues with latest SDK build ( http://download.eclipse.org/eclipse/downloads/drops4/I20150511-2130/) and Oracle JDK 1.9.0-ea-b63, on OSX 10.10.3
> Error when loading projects in Central with Java 9
> --------------------------------------------------
>
> Key: JBIDE-19425
> URL: https://issues.jboss.org/browse/JBIDE-19425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.3.0.Alpha1
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Labels: Java9
> Fix For: 4.3.0.Beta2
>
>
> Today I wanted to try out the latest build of Oracle JDK 1.9 beta and discovered a problem with central.
> When I started JBDS, I immediately got an error window pop up:
> {code}
> Refreshing JBoss Tutorials... has encountered a problem.
> An internal error occurred during: "Refreshing JBoss Tutorials...".
> javax/xml/bind/JAXBException
> {code}
> This is in the workspace log:
> {code}
> !ENTRY org.eclipse.core.jobs 4 2 2015-03-10 17:12:52.346
> !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...".
> !STACK 0
> java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.fetchCategories(ProjectExampleUtil.java:389)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:266)
> at org.jboss.tools.project.examples.model.ProjectExampleUtil.getProjects(ProjectExampleUtil.java:257)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:52)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: java.lang.ClassNotFoundException: javax.xml.bind.JAXBException cannot be found by org.jboss.tools.project.examples_3.0.0.Alpha1-v20150213-0945-B3
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:439)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:352)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:344)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:356)
> ... 5 more
> {code}
> I used JBDS 9.0.0.Alpha1 installed on OS X 10.10 Yosemite with Oracle JDK 1.9:
> {code}
> nattura:9.0.0 rasp$ java -version
> java version "1.9.0-ea"
> Java(TM) SE Runtime Environment (build 1.9.0-ea-b53)
> Java HotSpot(TM) 64-Bit Server VM (build 1.9.0-ea-b53, mixed mode)
> {code}
> The consequence of this is that the "Start from scratch" section in Central is not loaded and shows "No entries found".
> Note: When I installed the same JBDS with Java 8, there was no error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19776:
------------------------------------
Note that if we include *org.eclipse.tm.terminal.feature* in the target platform its validation fails like this:
{code}
[ERROR] Software being installed: org.eclipse.tm.terminal.feature.feature.group 4.0.0.201505051502
[ERROR] Missing requirement: org.eclipse.tm.terminal.feature.feature.group 4.0.0.201505051502 requires 'org.eclipse.tm.terminal.connector.local.feature.feature.group 4.0.0' but it could not be found
{code}
But I can easily include the *org.eclipse.tm.terminal plugin*, and much of the contents of the *org.eclipse.tm.terminal.feature*, too, without *tm.terminal.connector.local* being pulled in, which in turn depends on platform-specific bits of CDT.
> Create and use Mars M7 target-platform
> --------------------------------------
>
> Key: JBIDE-19776
> URL: https://issues.jboss.org/browse/JBIDE-19776
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v3.txt
>
>
> Mars M7 was released and contains interesting changes.
> We need to start using it ASAP to leverage new functionalities and adapt to the most important changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19776) Create and use Mars M7 target-platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19776?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-19776:
------------------------------------
Ah, so I added org.eclipse.tm.terminal plugin [4.0.0.201505051502], you told me to remove it, and cross-project-issues says to add its containing feature in instead. Fun times. We never included the tcf.te feature, only the new tm.terminal plugin.
So I guess my original PR was nearly valid and we DON'T need to remove server's dependency on tm.terminal or replace it with wacky CDT dependencies?
{quote}The PR just shows a basic removal that looks perfectly fine. Could we please get a p2diff ? {quote}
Did you mean my first PR, or this addendum [1] which adds a whole bunch of other stuff instead? Please provide references when you say "the PR" so it's clear what you mean -- I already provided p2diffs for the original PR, which shows no "basic removal". Nor does the second commit in that PR, which is why I'm confused by your statement.
[1] https://github.com/nickboldt/jbosstools-target-platforms/commit/5300fdbb6...
> Create and use Mars M7 target-platform
> --------------------------------------
>
> Key: JBIDE-19776
> URL: https://issues.jboss.org/browse/JBIDE-19776
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Fix For: 4.3.0.Beta1
>
> Attachments: jbdevstudio.p2diff.txt, jbdevstudio.p2diff.v3.txt, jbosstools.p2diff.txt, jbosstools.p2diff.v3.txt
>
>
> Mars M7 was released and contains interesting changes.
> We need to start using it ASAP to leverage new functionalities and adapt to the most important changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBDS-3434) Kubernetes editor & wizard
by Charles Moulliard (JIRA)
Charles Moulliard created JBDS-3434:
---------------------------------------
Summary: Kubernetes editor & wizard
Key: JBDS-3434
URL: https://issues.jboss.org/browse/JBDS-3434
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Reporter: Charles Moulliard
To deploy a project on Openshift3, it will be required to edit/generate a kubernetes.json file. The fabric8 project has created a maven plugin to generate the kubernetes.json file and next to deploy the project on OS" (= maven fabic8:install) but it could be interesteting also that we propose :
- a kubernetes editor within JBDS to update the YAML or JSON file and
- a wizard to create a kubernetes template file using some criteria like the API version, name, ports to be exposed, volumes to mount, ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19792) antlr packages and lib not exported in Hibernate Tools 4.0.1
by Bastian Ulke (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19792?page=com.atlassian.jira.plugi... ]
Bastian Ulke updated JBIDE-19792:
---------------------------------
Attachment: B82_MANIFEST.MF
B95_MANIFEST.MF
Reformatted (i.e. with 'readable line breaks') MANIFEST.MFs. Comparing shows the entries missing in B95.
> antlr packages and lib not exported in Hibernate Tools 4.0.1
> ------------------------------------------------------------
>
> Key: JBIDE-19792
> URL: https://issues.jboss.org/browse/JBIDE-19792
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.3.Final
> Environment: Eclipse Luna SR2
> Reporter: Bastian Ulke
> Attachments: B82_MANIFEST.MF, B95_MANIFEST.MF
>
>
> I am currently working on an Eclipse-Plugin that is built on top of the
> Hibernate Tools project. For example, I am using the following statements
> to get the AST of a named query:
> {code}
> try {
> HqlParser parser = HqlParser.getInstance(statementString);
> parser.statement();
> } catch (RecognitionException | TokenStreamException e) {
> e.printStackTrace();
> }
> AST statementAst = parser.getAST();
> {code}
> For this to work well with Hibernate Tools Version 4.0.0, I added bundle
> org.hibernate.eclipse.libs as required bundle to my plug-in configuration
> (which resolved to
> org.hibernate.eclipse.libs_4.0.0.Final-v20141016-1911-B82 so far).
> However, I now updated to Hiberate Tools 4.0.1
> (org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95). The problem I
> have now is that the following imports cannot be resolved:
> import antlr.RecognitionException;
> import antlr.TokenStreamException;
> import antlr.collections.AST;
> The problem seems to arise from the fact, that in the new version's
> MANIFEST.MF, the antlr... packages are not exported and
> lib/hibernate/antlr-2.7.6.jar is not listed in the Bundle-ClassPath any
> more (I reformatted both MANIFEST.MFs, that you can find attached, to allow
> a convenient comparison). After manually adding the antlr-related entries
> to the new version's MANIFEST.MF, my code works pretty well again.
> I agree, that internal libraries should generally not be exported. However,
> org.hibernate.hql.ast.HqlParser is exported -- so why not its prerequesites?
> (By the way, I'd be fine with integrating another library into my project.
> However, I tried to manally add antlr-2.7.6.jar as library to
> my project, which solved the compilation error, but yields a
> java.lang.ClassNotFoundException: antlr.LLkParser cannot be found by
> org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95.)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19792) antlr packages and lib not exported in Hibernate Tools 4.0.1
by Bastian Ulke (JIRA)
Bastian Ulke created JBIDE-19792:
------------------------------------
Summary: antlr packages and lib not exported in Hibernate Tools 4.0.1
Key: JBIDE-19792
URL: https://issues.jboss.org/browse/JBIDE-19792
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.2.3.Final
Environment: Eclipse Luna SR2
Reporter: Bastian Ulke
I am currently working on an Eclipse-Plugin that is built on top of the
Hibernate Tools project. For example, I am using the following statements
to get the AST of a named query:
{code}
try {
HqlParser parser = HqlParser.getInstance(statementString);
parser.statement();
} catch (RecognitionException | TokenStreamException e) {
e.printStackTrace();
}
AST statementAst = parser.getAST();
{code}
For this to work well with Hibernate Tools Version 4.0.0, I added bundle
org.hibernate.eclipse.libs as required bundle to my plug-in configuration
(which resolved to
org.hibernate.eclipse.libs_4.0.0.Final-v20141016-1911-B82 so far).
However, I now updated to Hiberate Tools 4.0.1
(org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95). The problem I
have now is that the following imports cannot be resolved:
import antlr.RecognitionException;
import antlr.TokenStreamException;
import antlr.collections.AST;
The problem seems to arise from the fact, that in the new version's
MANIFEST.MF, the antlr... packages are not exported and
lib/hibernate/antlr-2.7.6.jar is not listed in the Bundle-ClassPath any
more (I reformatted both MANIFEST.MFs, that you can find attached, to allow
a convenient comparison). After manually adding the antlr-related entries
to the new version's MANIFEST.MF, my code works pretty well again.
I agree, that internal libraries should generally not be exported. However,
org.hibernate.hql.ast.HqlParser is exported -- so why not its prerequesites?
(By the way, I'd be fine with integrating another library into my project.
However, I tried to manally add antlr-2.7.6.jar as library to
my project, which solved the compilation error, but yields a
java.lang.ClassNotFoundException: antlr.LLkParser cannot be found by
org.hibernate.eclipse.libs_4.0.1.Final-v20150324-2307-B95.)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months
[JBoss JIRA] (JBIDE-19791) Switch OpenShift plugins to require JDK7
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19791?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-19791:
------------------------------------------
merged and pushed to upstream/master
> Switch OpenShift plugins to require JDK7
> ----------------------------------------
>
> Key: JBIDE-19791
> URL: https://issues.jboss.org/browse/JBIDE-19791
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.3.0.Beta1
>
>
> With the switch to the new 4.50.0.Beta1-SNAPSHOT target platform (which is using Mars M7) OpenShift (especially the egit based parts) now require jdk7 to cleanly compilein Eclipse. Compilation error faced are references to java.land.AutoCloseable which was introduced in jdk7.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 11 months