[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-3044 at 5/28/14 10:36 AM:
------------------------------------------------------------
Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2:
{quote}
{code}
find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+"
{code}
shows 251 as the longest path on Mac so not really safe
longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor
but that is spring and it's data
{quote}
So we're already pushing the limit here for long paths on Windows / NTFS...
Related (with some LOLs): http://blog.codinghorror.com/filesystem-paths-how-long-is-too-long/
There are ways to achieve more-than-260-char paths, but do we want to?
was (Author: nickboldt):
Martin did a quick test on OSX to see what the longest file paths are inside JBDS 8 Beta2:
{quote}
{code}
find jbdevstudio-* |awk '{ print length($0) ; }'|sort|uniq|egrep "2.+"
{code}
shows 251 as the longest path on Mac so not really safe
longest is ./studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor
but that is spring and it's data
{quote}
So we're already pushing the limit here for long paths on Windows / NTFS...
> Align installation default path with installer filename
> -------------------------------------------------------
>
> Key: JBDS-3044
> URL: https://issues.jboss.org/browse/JBDS-3044
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: discuss
> Fix For: 8.0.0.Beta3
>
>
> Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync.
> This question is open for discussion. Nick pointed out some reasons against this suggestion:
> {quote}
> Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons:
> a) Max is AFK, and will want to vet/veto this idea
> b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces
> c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience
> So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters.
> Max Rydahl Andersen WDYT?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
4 weeks, 1 day
[JBoss JIRA] (JBDS-2719) Multiple Spring AOP problems when travel example is imported
by Joshua Wilson (JIRA)
[ https://issues.jboss.org/browse/JBDS-2719?page=com.atlassian.jira.plugin.... ]
Joshua Wilson commented on JBDS-2719:
-------------------------------------
[~nickboldt] I will need to test several different configurations to confirm my earlier guess. This is what I know so far.
First I would ask that you test with the [Kitchensink-Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts] as I am working to keep them up to date and error free as much as possible. This specific error can be seen in the [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] quickstart. The Travel and PetClinic will be kept as close to the original as possible (and I haven't had a chance to update them yet).
With that in mind if I Build (with Eclipse/JBDS) [kitchensink-spring-matrixvariable|https://github.com/jboss-developer/jbos...] in JBDS 7.0.1 with Spring IDE 3.3 installed from JBoss Central, I get the aspectj error. However if I Build while in a standard Eclipse JEE install with JBDS and the stock Spring IDE/STS 3.4 installed, I do NOT get the aspectj error.
In order to truly confirm that adding both "AspectJ Compiler" and "AspectJ Development Tools" will fix the error, I would need to test that on my JBDS 7.0.1/SpringIDE 3.3 set up.
> Multiple Spring AOP problems when travel example is imported
> ------------------------------------------------------------
>
> Key: JBDS-2719
> URL: https://issues.jboss.org/browse/JBDS-2719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, upstream
> Affects Versions: 7.0.0.GA
> Environment: JBDS 7.0.0.GA, L64, Spring IDE 3.3 installed from JBoss Central
> Reporter: Jiri Peterka
> Assignee: Nick Boldt
> Fix For: 7.1.0.Beta1
>
>
> There are Multiple Spring AOP Errors after travel example is imported:
> {code}
> Build path is incomplete. Cannot find class file for org/aspectj/weaver/reflect/ReflectionWorld$ReflectionWorldException
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
4 months
[JBoss JIRA] (JBIDE-20571) OpenShift Explorer: Build/Pod activity should be refreshed automatically
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20571?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20571:
-------------------------------------
assigning to [~jcantrill] since he's implementing watch support in the rest client
> OpenShift Explorer: Build/Pod activity should be refreshed automatically
> ------------------------------------------------------------------------
>
> Key: JBIDE-20571
> URL: https://issues.jboss.org/browse/JBIDE-20571
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.Beta1
>
>
> Currently, when a build is running on openshift, users need to manually refresh the OpenShift Explorer view, to see when a build or a deployment finishes.
> We need to be able to let the explorer "watch" some specific project events (via websockets or some other method).
> As a workaround we might be able to trigger automatic refreshes of the viewer, every 5secs, when we detect a pod is in pending, building, deploying or some other status.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-20571) OpenShift Explorer: Build/Pod activity should be refreshed automatically
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20571?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-20571:
-----------------------------------
Assignee: Jeff Cantrill
> OpenShift Explorer: Build/Pod activity should be refreshed automatically
> ------------------------------------------------------------------------
>
> Key: JBIDE-20571
> URL: https://issues.jboss.org/browse/JBIDE-20571
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Fix For: 4.3.1.Beta1
>
>
> Currently, when a build is running on openshift, users need to manually refresh the OpenShift Explorer view, to see when a build or a deployment finishes.
> We need to be able to let the explorer "watch" some specific project events (via websockets or some other method).
> As a workaround we might be able to trigger automatic refreshes of the viewer, every 5secs, when we detect a pod is in pending, building, deploying or some other status.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBDS-3553) Integrate/Enable CodeRecommenders substring completion in JBDS 9
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3553?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-3553.
------------------------------
Resolution: Done
PRs merged. Building:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... >= 465
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... >= 131
> Integrate/Enable CodeRecommenders substring completion in JBDS 9
> ----------------------------------------------------------------
>
> Key: JBDS-3553
> URL: https://issues.jboss.org/browse/JBDS-3553
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: p2-product, target-platform
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Labels: new_and_noteworthy
> Fix For: 9.1.0.Beta1
>
>
> Eclipse Mars release are shipped with CodeRecommenders enabled so that Java developers can benefit from substring completion and many others: https://www.eclipse.org/recommenders/manual/
> JBDS doesn't have it enabled by default when installing from installer. Since it provides a lot of value for Java developers, it should be on by default.
> *Project page/sources:* https://www.eclipse.org/recommenders/manual/
> *Version:* 2.2.4 (part of Mars)
> *License and owner:* EPL, Eclipse Community/CodeTrails
> *Original p2 repo:* included in Mars repository
> *JBoss mirror:* will use our Mars mirror
> *Include Sources:* No
> *Affected JBoss Tools components:* JBDS feature and product
> *Include in JBDS:* Yes (only, not in JBT as it's supposed to be available in upstream Eclipse)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> mistria@mistria-laptop:~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64$ ./p2diff http://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.51.0.Fina... file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/
> > org.eclipse.recommenders.jdt [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.overrides [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.injection [2.2.4.v20150914-0857]
> > org.eclipse.aether.maven.feature.feature.group [3.1.0.20140706-2237]
> > org.eclipse.aether.transport.http [1.0.1.v20141111]
> > org.eclipse.aether.api [1.0.1.v20141111]
> > org.eclipse.aether.transport.http.feature.feature.jar [1.0.1.v20141111]
> > org.eclipse.aether.transport.file.feature.feature.jar [1.0.1.v20141111]
> > org.eclipse.recommenders.overrides.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.utils [2.2.4.v20150914-0857]
> > org.eclipse.aether.connector.basic.feature.feature.jar [1.0.1.v20141111]
> > org.eclipse.aether.spi [1.0.1.v20141111]
> > com.google.inject.multibindings [3.0.0.v201402270930]
> > org.eclipse.recommenders.completion.rcp [2.2.4.v20150914-0857]
> > org.eclipse.aether.maven.feature.feature.jar [3.1.0.20140706-2237]
> > org.apache.commons.lang3 [3.1.0.v201403281430]
> > org.eclipse.aether.feature.feature.group [1.0.1.v20141111]
> > org.eclipse.recommenders.types.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.calls.rcp [2.2.4.v20150914-0857]
> > org.eclipse.aether.connector.basic.feature.feature.group [1.0.1.v20141111]
> > org.apache.commons.pool [1.6.0.v201204271246]
> > org.eclipse.aether.maven [3.1.0.v20140706-2237]
> > org.eclipse.recommenders.models [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.jayes [2.2.4.v20150914-0857]
> > org.eclipse.aether.transport.file [1.0.1.v20141111]
> > org.apache.commons.math [2.1.0.v201105210652]
> > org.eclipse.recommenders.coordinates [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.subwords.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.models.rcp [2.2.4.v20150914-0857]
> > org.eclipse.aether.transport.http.feature.feature.group [1.0.1.v20141111]
> > org.eclipse.recommenders.chain.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.apidocs [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.rcp.feature.feature.jar [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.constructors [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.calls [2.2.4.v20150914-0857]
> > org.apache.solr.client.solrj [3.5.0.v20150506-0844]
> > org.eclipse.aether.impl [1.0.1.v20141111]
> > org.eclipse.recommenders.jayes.io [2.2.4.v20150914-0857]
> > com.google.inject [3.0.0.v201312141243]
> > org.eclipse.aether.connector.basic [1.0.1.v20141111]
> > ch.qos.logback.slf4j [1.0.7.v201505121915]
> > org.eclipse.aether.util [1.0.1.v20141111]
> > org.eclipse.recommenders.utils.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.net [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.constructors.rcp [2.2.4.v20150914-0857]
> > org.eclipse.aether.feature.feature.jar [1.0.1.v20141111]
> > org.eclipse.recommenders.rcp [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.apidocs.rcp [2.2.4.v20150914-0857]
> > org.eclipse.aether.transport.file.feature.feature.group [1.0.1.v20141111]
> > org.eclipse.recommenders.rcp.feature.feature.group [2.2.4.v20150914-0857]
> > org.eclipse.recommenders.coordinates.rcp [2.2.4.v20150914-0857]
> === Summary ===
> file:/home/mistria/git/jbosstools-target-platforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo/ contains 51 unique IUs
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years