[JBoss JIRA] (JBDS-3682) Online installer reports missing package.js file
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3682?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3682:
--------------------------------
Labels: havoc (was: )
> Online installer reports missing package.js file
> ------------------------------------------------
>
> Key: JBDS-3682
> URL: https://issues.jboss.org/browse/JBDS-3682
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: havoc
>
> Installer now files to load path.resolve('./package.json') file and fails, because file not found. In this case it tries to resolve from folder where installer started, which is a temp folder where electron installer unpacked all the files after start. package.json real location is in app subfolder which can be referenced by __pathname variable plus one level up.
> Right way to reference package json would be:
> {code}var pjson = require(path.join(__dirname,'../package.json'));{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21897) JNP when creating an hbm.xml file
by Mohammed El Kihal (JIRA)
Mohammed El Kihal created JBIDE-21897:
-----------------------------------------
Summary: JNP when creating an hbm.xml file
Key: JBIDE-21897
URL: https://issues.jboss.org/browse/JBIDE-21897
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate
Affects Versions: 4.3.0.Final
Environment: eclipse.buildId=4.5.2.M20160212-1500
java.version=1.8.0_73
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product org.eclipse.epp.package.jee.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product org.eclipse.epp.package.jee.product
Reporter: Mohammed El Kihal
Priority: Blocker
Attachments: HibernateError.txt, pom.xml
Generating new Hibernate mapping files becomes impossible when converting a dynamic web project to maven and modifying the pom.xml.
After switching the default pom.xml with the one i have pre-configured,it lead to the JNP,even after switching to the default one again,the error persisted.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3647) Investigate why we are including both cygwin and mingw
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3647?page=com.atlassian.jira.plugin.... ]
Denis Golovin resolved JBDS-3647.
---------------------------------
Resolution: Done
returning cygwin back for these reasons:
- it is the only ssh/rsync implementation that can be used to configure sshd service and then use version 1.0.0 of vagrant-sshfs to mount the users home directory into the VM (see JBDS-3671 for details);
- it works with latest vagrant release 1.8.1, mingw based ssh/rsync does not. This is the going tombe a problem in case someone has it already installed and decided to skip vagrant installation and use pre-installed one.
> Investigate why we are including both cygwin and mingw
> ------------------------------------------------------
>
> Key: JBDS-3647
> URL: https://issues.jboss.org/browse/JBDS-3647
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Pete Muir
> Assignee: Denis Golovin
> Priority: Critical
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> We shouldn't need to include cygwin to make vagrant work. Let's check why we include this.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years