April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19592) Update to latest tern.java 0.9.0.201504141710

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19592?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-19592: ------------------------------------- Assignee: Denis Golovin > Update to latest tern.java 0.9.0.201504141710 > --------------------------------------------- > > Key: JBIDE-19592 > URL: https://issues.jboss.org/browse/JBIDE-19592 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Alpha2 > > > Mirror llatest tern.java snapshot from http://oss.opensagres.fr/tern.repository/0.9.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19592) Update to latest tern.java 0.9.0.201504141710

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19592?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19592: ---------------------------------- Fix Version/s: 4.3.0.Alpha2 > Update to latest tern.java 0.9.0.201504141710 > --------------------------------------------- > > Key: JBIDE-19592 > URL: https://issues.jboss.org/browse/JBIDE-19592 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Fix For: 4.3.0.Alpha2 > > > Mirror llatest tern.java snapshot from http://oss.opensagres.fr/tern.repository/0.9.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19592) Update to latest tern.java 0.9.0.201504141710

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-19592: ------------------------------------- Summary: Update to latest tern.java 0.9.0.201504141710 Key: JBIDE-19592 URL: https://issues.jboss.org/browse/JBIDE-19592 Project: Tools (JBoss Tools) Issue Type: Task Components: jsp/jsf/xml/html source editing Affects Versions: 4.3.0.Alpha2 Reporter: Denis Golovin Mirror llatest tern.java snapshot from http://oss.opensagres.fr/tern.repository/0.9.0-SNAPSHOT -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3285: -------------------------------------- About import-me, I believe it works much better if you have the Maven configurator available (see latest version of PR ). > Easy Import of non-eclipse projects > ----------------------------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > Attachments: import-me.zip > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3406) JBDS doesn't prompt for workspace when you run it from installer's last step

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-3406?page=com.atlassian.jira.plugin.... ] Pavol Srna updated JBDS-3406: ----------------------------- Fix Version/s: 9.0.0.Alpha2 > JBDS doesn't prompt for workspace when you run it from installer's last step > ---------------------------------------------------------------------------- > > Key: JBDS-3406 > URL: https://issues.jboss.org/browse/JBDS-3406 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Alpha2 > Reporter: Pavol Srna > Fix For: 9.0.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ] Pavol Srna updated JBDS-3404: ----------------------------- Fix Version/s: 9.0.0.Alpha2 > Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly) > -------------------------------------------------------- > > Key: JBDS-3404 > URL: https://issues.jboss.org/browse/JBDS-3404 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Pavol Srna > Priority: Blocker > Fix For: 9.0.0.Alpha2 > > Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png > > > When you do Check for update, only thym update is offered: > !Screenshot 2015-04-13 14.03.50.png! > Output when you do Install/Check All > {code} > Your original request has been modified. > "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead. > "JBoss JAX-RS Tools" is already installed, so an update will be performed instead. > "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead. > "Apache Deltaspike Tools" is already installed, so an update will be performed instead. > "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead. > "JBoss Tools Foundation" is already installed, so an update will be performed instead. > "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead. > "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead. > "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead. > "JBoss Tools RichFaces" is already installed, so an update will be performed instead. > "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead. > "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead. > "JBoss Maven Project Examples" is already installed, so an update will be performed instead. > "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead. > "JMX Console" is already installed, so an update will be performed instead. > "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead. > "JBoss Tools JSF" is already installed, so an update will be performed instead. > "Seam Tools" is already installed, so an update will be performed instead. > "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead. > "JBoss Archives Tools" is already installed, so an update will be performed instead. > "JBoss Stacks Tools" is already installed, so an update will be performed instead. > "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead. > "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead. > "Project Examples" is already installed, so an update will be performed instead. > "JBoss Maven Integration" is already installed, so an update will be performed instead. > "JBoss Runtime Detection Core" is already installed, so an update will be performed instead. > "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead. > "JBoss WebServices Tools" is already installed, so an update will be performed instead. > "Hibernate Tools" is already installed, so an update will be performed instead. > "JBoss Tools LiveReload" is already installed, so an update will be performed instead. > "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead. > "JBoss Tools EGit Integration" is already installed, so an update will be performed instead. > "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead. > "Forge Tools" is already installed, so an update will be performed instead. > "Context and Dependency Injection Tools" is already installed, so an update will be performed instead. > "JBossAS Tools" is already installed, so an update will be performed instead. > Cannot complete the install because of a conflicting dependency. > Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822) > Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3) > Only one of the following can be installed at once: > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822) > JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3) > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3) > To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3] > Cannot satisfy dependency: > From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822) > To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822] > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3285: -------------------------------------- There is no clear priorities between frameworks/technologies/languages/buildtools.... Examples: Why would Gradle have priority over Maven, or vice-versa? And if a Maven project doesn't define a JavaScript plugin, does that make that we shouldn't enable JSDT on a given webapp which includes many JavaScript files? If we have Bower and Maven, which one should have priority? Should we also define some "work together" rules? Where would they be defined? Dealing with priorities require every configurator to be aware of all other configurators in order to define priorities/compatibilities... I've thought about it while designing the API, and I came to the conclusion that priorities are a quite complex and weak workaround for things don't work together. It's IMO more scalable to just assume that things have to work together. About giving choice to the user about which configurator to use, this is already what the "legacy" import wizard has done for so many years. The less choice we give to user, the more useful is this tool. > Easy Import of non-eclipse projects > ----------------------------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > Attachments: import-me.zip > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3285: ----------------------------------- I think there's a fundamental flaw in the easymport API : there's no configurator sort per priority. Each configurator should declare a weight/priority, so all of them could be sorted, then the first configurator (highest priority) that applies do its thing. So then you can have : Maven > PDE > generic project (.project) > projectless folder If we had, say Gradle and Maven having the same priority, and both pom.xml and build.gradle are found, the UI should show the conflicting configurators and let the user decide how to import the project. > Easy Import of non-eclipse projects > ----------------------------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > Attachments: import-me.zip > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3285: ------------------------------ Attachment: import-me.zip Unzip import-me.zip and import project folder. 2 projects will be created import-me and classes > Easy Import of non-eclipse projects > ----------------------------------- > > Key: JBDS-3285 > URL: https://issues.jboss.org/browse/JBDS-3285 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, upstream > Affects Versions: 8.0.0.GA > Reporter: Burr Sutter > Assignee: Mickael Istria > Labels: usability > Fix For: 9.0.0.Alpha2 > > Attachments: import-me.zip > > > As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance. > The mission here is to make the Git experience much more user friendly. > Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19473) Central can't load Discovery catalog

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19473?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-19473. ------------------------------------ Resolution: Done I updated the jbosstools-discovery_master job to update traditional nightly location for discovery catalog: {code} . ${WORKSPACE}/sources/publish/rsync.sh -s ${WORKSPACE}/sources/jbosstools/org.jboss.tools.central.discovery/target/discovery-site \ -t discovery/nightly/core/master {code} I'm still not sure whether it's a good idea or not... But at least, I could test the latest catalog, and verify that it's now loading again. The actual issue was indeed the typos in the plugin.xml > Central can't load Discovery catalog > ------------------------------------ > > Key: JBIDE-19473 > URL: https://issues.jboss.org/browse/JBIDE-19473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found. > The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... ), referenced plugins are existing and seem to have right content. > Log says > {quote} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223 > !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar > {quote} > I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 2 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2015