[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)
1 week, 5 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
[JBoss JIRA] (JBIDE-17730) JAX-RS @PathParam Field is not validated against @Path annotation value
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17730?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-17730:
----------------------------------
Description:
Take the following code:
{code}
@Path("/")
public class CarResource {
@PathParam("id")
private Integer id;
@GET
@Path("{id}")
public Object getCar() {
return null;
}
}
{code}
replace {{@PathParam("id")}} with {{@PathParam("i")}}, there is no problem reported in 'as-you-type', while there should be (user has to save the file to see the problem markers).
Same goes when changing the value of the {{@Path}} annotation on the method: no 'as-you-type' problem report.
was:
Take the following code:
{code}
@Path("/")
public class CarResource {
@PathParam("id")
private Integer id;
@GET
@Path("{id}")
public Object getCar() {
return null;
}
}
{code}
replace {{@PathParam("id")}} with {{@PathParam("i")}}, there is no problem reported, while there should be.
> JAX-RS @PathParam Field is not validated against @Path annotation value
> -----------------------------------------------------------------------
>
> Key: JBIDE-17730
> URL: https://issues.jboss.org/browse/JBIDE-17730
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> Take the following code:
> {code}
> @Path("/")
> public class CarResource {
>
> @PathParam("id")
> private Integer id;
>
> @GET
> @Path("{id}")
> public Object getCar() {
> return null;
> }
> }
> {code}
> replace {{@PathParam("id")}} with {{@PathParam("i")}}, there is no problem reported in 'as-you-type', while there should be (user has to save the file to see the problem markers).
> Same goes when changing the value of the {{@Path}} annotation on the method: no 'as-you-type' problem report.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (JBIDE-17730) JAX-RS @PathParam Field is not validated against @Path annotation value
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17730?page=com.atlassian.jira.plugi... ]
Xavier Coulon updated JBIDE-17730:
----------------------------------
Description:
Take the following code:
{code}
@Path("/")
public class CarResource {
@PathParam("id")
private Integer id;
@GET
@Path("{id}")
public Object getCar() {
return null;
}
}
{code}
replace {{@PathParam("id")}} with {{@PathParam("i")}}, there is no problem reported, while there should be.
was:
Take the following code:
{code}
@Path("/")
public class CarResource {
@PathParam("id")
private Integer id;
@GET
@Path("{id}")
public Object getCar() {
return null;
}
}
{code}
replace {{@PathParam("id")}} with {{@PathParam("i")}}, there is no problem reported, while there should be.
Note: replacing {{@Path("{id}")}} with {{@Path("{i}")}} instead results in a proble reported by the JAX-RS validator.
> JAX-RS @PathParam Field is not validated against @Path annotation value
> -----------------------------------------------------------------------
>
> Key: JBIDE-17730
> URL: https://issues.jboss.org/browse/JBIDE-17730
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
>
> Take the following code:
> {code}
> @Path("/")
> public class CarResource {
>
> @PathParam("id")
> private Integer id;
>
> @GET
> @Path("{id}")
> public Object getCar() {
> return null;
> }
> }
> {code}
> replace {{@PathParam("id")}} with {{@PathParam("i")}}, there is no problem reported, while there should be.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (JBIDE-17730) JAX-RS @PathParam Field is not validated against @Path annotation value
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-17730:
-------------------------------------
Summary: JAX-RS @PathParam Field is not validated against @Path annotation value
Key: JBIDE-17730
URL: https://issues.jboss.org/browse/JBIDE-17730
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: webservices
Affects Versions: 4.2.0.Beta2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.2.0.Beta3
Take the following code:
{code}
@Path("/")
public class CarResource {
@PathParam("id")
private Integer id;
@GET
@Path("{id}")
public Object getCar() {
return null;
}
}
{code}
replace {{@PathParam("id")}} with {{@PathParam("i")}}, there is no problem reported, while there should be.
Note: replacing {{@Path("{id}")}} with {{@Path("{i}")}} instead results in a proble reported by the JAX-RS validator.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (JBIDE-17729) compile failure in Seam (JavaEE)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17729?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17729:
-----------------------------------
Fix Version/s: 4.2.0.Beta3
> compile failure in Seam (JavaEE)
> --------------------------------
>
> Key: JBIDE-17729
> URL: https://issues.jboss.org/browse/JBIDE-17729
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, seam2
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Priority: Blocker
> Fix For: 4.2.0.Beta3
>
>
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.jboss.tools.seam.ui: Compilation failure: Compilation failure:
> [ERROR] /home/daniel/git/jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/DBTablesViewer.java:[247]
> [ERROR] Settings newSettings = cfg.buildSettings();
> [ERROR] ^^^^^^^^^^^^^^^^^^^
> [ERROR] Type mismatch: cannot convert from ISettings to Settings
> [ERROR] 1 problem (1 error)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (JBIDE-17729) compile failure in Seam (JavaEE)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17729?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17729:
-----------------------------------
Component/s: hibernate
> compile failure in Seam (JavaEE)
> --------------------------------
>
> Key: JBIDE-17729
> URL: https://issues.jboss.org/browse/JBIDE-17729
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, seam2
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
>
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.jboss.tools.seam.ui: Compilation failure: Compilation failure:
> [ERROR] /home/daniel/git/jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/DBTablesViewer.java:[247]
> [ERROR] Settings newSettings = cfg.buildSettings();
> [ERROR] ^^^^^^^^^^^^^^^^^^^
> [ERROR] Type mismatch: cannot convert from ISettings to Settings
> [ERROR] 1 problem (1 error)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months
[JBoss JIRA] (JBIDE-17729) compile failure in Seam (JavaEE)
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17729?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-17729:
-----------------------------------
Priority: Blocker (was: Major)
> compile failure in Seam (JavaEE)
> --------------------------------
>
> Key: JBIDE-17729
> URL: https://issues.jboss.org/browse/JBIDE-17729
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate, seam2
> Affects Versions: 4.2.0.Beta3
> Reporter: Daniel Azarov
> Priority: Blocker
>
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.20.0:compile (default-compile) on project org.jboss.tools.seam.ui: Compilation failure: Compilation failure:
> [ERROR] /home/daniel/git/jbosstools-javaee/seam/plugins/org.jboss.tools.seam.ui/src/org/jboss/tools/seam/ui/views/DBTablesViewer.java:[247]
> [ERROR] Settings newSettings = cfg.buildSettings();
> [ERROR] ^^^^^^^^^^^^^^^^^^^
> [ERROR] Type mismatch: cannot convert from ISettings to Settings
> [ERROR] 1 problem (1 error)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 3 months