[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)
3 weeks, 3 days
[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
3 months, 4 weeks
[JBoss JIRA] (JBIDE-15250) Explode utility jars in EAR/WAR deployments
by Christian Beikov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi... ]
Christian Beikov edited comment on JBIDE-15250 at 12/31/14 11:46 AM:
---------------------------------------------------------------------
Here I provide 3 example projects
* test-ear-with-lib - contains the problematic case which shows that a library jar is deployed in zipped format
* test-ear-with-module - contains the described case which deploys the library jar as utility module(DOES NOT WORK)
* test-ear-with-ejb - contains the only working solution which deploys the jar as ejb module in the exploded form
It's always the same code. You can test it by starting the application from within eclipse on a wildfly that runs in debug mode. Changes made to test-file.properties located in jar/src/main/resources are only immediately visible, if deployed in the exploded form(ejb module). The contents of the file can be viewed by browsing to localhost:8080/test-war/index.xhtml
was (Author: christian.beikov):
Here I provide 3 example projects
* test-ear-with-lib - contains the problematic case which shows that a library jar is deployed in zipped format
* test-ear-with-module - contains the described case which deploys the library jar as utility module(DOES NOT WORK)
* test-ear-with-ejb - contains the only working solution which deploys the jar as ejb module in the exploded form
It's always the same code. You can test it by starting the application from within eclipse on a wildfly that runs in debug mode. Changes made to test-file.properties located in jar/src/main/resources are only immediately visible, if deployed in the exploded form(ejb module).
> Explode utility jars in EAR/WAR deployments
> -------------------------------------------
>
> Key: JBIDE-15250
> URL: https://issues.jboss.org/browse/JBIDE-15250
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.0.1.Final
> Reporter: Kevin Formsma
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
> Attachments: test-ear.zip
>
>
> For larger projects that utilize utility jars within the EAR, it would be nice to have these deployed exploded as well. This would allow hot code replacement for those utility projects.
> A current work around is to make the utility projects modules so that the tooling treats them as a EJB module and deploys them exploded.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (JBIDE-15250) Explode utility jars in EAR/WAR deployments
by Christian Beikov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15250?page=com.atlassian.jira.plugi... ]
Christian Beikov updated JBIDE-15250:
-------------------------------------
Attachment: test-ear.zip
Here I provide 3 example projects
* test-ear-with-lib - contains the problematic case which shows that a library jar is deployed in zipped format
* test-ear-with-module - contains the described case which deploys the library jar as utility module(DOES NOT WORK)
* test-ear-with-ejb - contains the only working solution which deploys the jar as ejb module in the exploded form
It's always the same code. You can test it by starting the application from within eclipse on a wildfly that runs in debug mode. Changes made to test-file.properties located in jar/src/main/resources are only immediately visible, if deployed in the exploded form(ejb module).
> Explode utility jars in EAR/WAR deployments
> -------------------------------------------
>
> Key: JBIDE-15250
> URL: https://issues.jboss.org/browse/JBIDE-15250
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.0.1.Final
> Reporter: Kevin Formsma
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
> Attachments: test-ear.zip
>
>
> For larger projects that utilize utility jars within the EAR, it would be nice to have these deployed exploded as well. This would allow hot code replacement for those utility projects.
> A current work around is to make the utility projects modules so that the tooling treats them as a EJB module and deploys them exploded.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 9 months
[JBoss JIRA] (JBIDE-18993) New Meter wizard for HTML5 palette
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-18993:
---------------------------------------------
Summary: New Meter wizard for HTML5 palette
Key: JBIDE-18993
URL: https://issues.jboss.org/browse/JBIDE-18993
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.3.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (JBIDE-18992) New Menu wizard for HTML5 palette
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-18992:
---------------------------------------------
Summary: New Menu wizard for HTML5 palette
Key: JBIDE-18992
URL: https://issues.jboss.org/browse/JBIDE-18992
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.3.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (JBIDE-18991) New Menuitem wizard for HTML5 palette
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-18991:
---------------------------------------------
Summary: New Menuitem wizard for HTML5 palette
Key: JBIDE-18991
URL: https://issues.jboss.org/browse/JBIDE-18991
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.3.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months
[JBoss JIRA] (JBIDE-18990) New Datalist wizard for HTML5 palette
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-18990:
---------------------------------------------
Summary: New Datalist wizard for HTML5 palette
Key: JBIDE-18990
URL: https://issues.jboss.org/browse/JBIDE-18990
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsp/jsf/xml/html source editing
Affects Versions: 4.3.0.Alpha1
Reporter: Viacheslav Kabanovich
Assignee: Viacheslav Kabanovich
Fix For: 4.3.0.Alpha1
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
10 years, 10 months