[JBoss JIRA] (JBIDE-17627) Special characters like > are not processed correctly in the Forge console
by Vineet Reynolds (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17627?page=com.atlassian.jira.plugi... ]
Vineet Reynolds commented on JBIDE-17627:
-----------------------------------------
[~jpeterka], yes it can be set as resolved. I could not reproduce it any longer.
> Special characters like > are not processed correctly in the Forge console
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17627
> URL: https://issues.jboss.org/browse/JBIDE-17627
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta2
> Environment: Mac OS X Mavericks, Oracle JDK 7 u60, Oracle JDK 8u5
> Reporter: Vineet Reynolds
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.2.0.Beta3
>
>
> When I run a Forge command in console where some special characters are present in the input, the input following the special characters are omitted during processing.
> For example:
> {noformat}
> [Event.java]$ constraint-add --onProperty name --constraint Size --min 5 --max 50 --message "Must be > 5 and < 50"
> aesh: can't redirect to more than one file.
> {noformat}
> which results in the following bit of code being generated:
> {noformat}
> @Column
> @Size(min = 5, max = 50, message = "Must be ")
> private String name;
> {noformat}
> Note the characters following {{'>'}} have been omitted in the generated annotation attribute value.
> This is not a problem with the Eclipse GUI, so I guess this is an Aesh+Forge issue involving escaping of such characters.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17311) jvmmonitor agent project moved + renamed into jbt-server repo
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17311?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-17311.
---------------------------------
Assignee: Rob Stryker
Fix Version/s: 4.2.0.Beta3
Resolution: Done
The code has been moved and a new agent jar has been built. The agent code, howerver, is NOT an osgi bundle, and must still be built manually.
If we figure out how to do this cleaner it can be changed in a future release.
> jvmmonitor agent project moved + renamed into jbt-server repo
> -------------------------------------------------------------
>
> Key: JBIDE-17311
> URL: https://issues.jboss.org/browse/JBIDE-17311
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jmx
> Affects Versions: 4.2.0.Beta2
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.2.0.Beta3
>
>
> The file "jvmmonitor-agent.jar" is currently a built component separate from its project. This must be somehow unified with the other jvm-monitor code in terms of where it lives and how it gets built.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17627) Special characters like > are not processed correctly in the Forge console
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17627?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-17627:
--------------------------------------
This can be set as resolved now, right? If it's not ok, it well be reopened by QE.
> Special characters like > are not processed correctly in the Forge console
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17627
> URL: https://issues.jboss.org/browse/JBIDE-17627
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta2
> Environment: Mac OS X Mavericks, Oracle JDK 7 u60, Oracle JDK 8u5
> Reporter: Vineet Reynolds
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.2.0.Beta3
>
>
> When I run a Forge command in console where some special characters are present in the input, the input following the special characters are omitted during processing.
> For example:
> {noformat}
> [Event.java]$ constraint-add --onProperty name --constraint Size --min 5 --max 50 --message "Must be > 5 and < 50"
> aesh: can't redirect to more than one file.
> {noformat}
> which results in the following bit of code being generated:
> {noformat}
> @Column
> @Size(min = 5, max = 50, message = "Must be ")
> private String name;
> {noformat}
> Note the characters following {{'>'}} have been omitted in the generated annotation attribute value.
> This is not a problem with the Eclipse GUI, so I guess this is an Aesh+Forge issue involving escaping of such characters.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-3073) use installMode="root" for top-level JBDS "Core Features" feature
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3073?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3073.
----------------------------
Resolution: Won't Fix
If you want to run from the installer, you must continue to run from the installer and upgrade the full Branded Product feature (eg., via Help > Check for updates).
Or, if you install from Marketplace (BYOE) then you can update pieces or the Core Features.
What's not supported is a hybrid scenario where you start w/ JBDS Branded Product but then upgrade the Core Features feature (or any smaller pieces).
> use installMode="root" for top-level JBDS "Core Features" feature
> -----------------------------------------------------------------
>
> Key: JBDS-3073
> URL: https://issues.jboss.org/browse/JBDS-3073
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 8.0.0.Beta3
>
>
> To better support the BYOE scenario and be more easily able to update pieces of JBDS w/o having to update the product, we could consider adding `installMode="root"` to the JBDS "Core Features" feature so it can be installed in parallel to the JBDS "Branded Product" feature, rather than as its child [1].
> [1] http://codeandme.blogspot.fr/2014/06/tycho-11-install-root-level-features...
> We could further do this with other JBDS/JBT child features, but I suspect we *don't want to do that* as it would allow users to update *individual parts piecemeal*, rather than as one big update.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-15609) versionwatch should ignore when there's a folder & jar which are identical
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15609?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15609:
------------------------------------
[~jpeterka] How do you disable the md5 checks in jobs? Is this slipping to CR1, or will it be fixed during the next 3 weeks (QE cycle for Beta3) ?
> versionwatch should ignore when there's a folder & jar which are identical
> --------------------------------------------------------------------------
>
> Key: JBIDE-15609
> URL: https://issues.jboss.org/browse/JBIDE-15609
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa
> Affects Versions: 4.1.1.Alpha2
> Reporter: Nick Boldt
> Assignee: Jiri Peterka
> Fix For: 4.2.0.Beta3
>
>
> A while ago I added a facility to jar up feature and plugin folders so they could have their md5 sums compared.
> Now, the vwatch tool complains when there's a folder and a jar present.
> Two possible solutions to this come to mind:
> a) ignore this - do not report as *{color:red}a problem{color}*
> b) whenever a folder is jarred up, delete the source folder, so the above condition cannot occur
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17627) Special characters like > are not processed correctly in the Forge console
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17627?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-17627:
--------------------------------
Assignee: Koen Aers (was: George Gastaldi)
> Special characters like > are not processed correctly in the Forge console
> ---------------------------------------------------------------------------
>
> Key: JBIDE-17627
> URL: https://issues.jboss.org/browse/JBIDE-17627
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Beta2
> Environment: Mac OS X Mavericks, Oracle JDK 7 u60, Oracle JDK 8u5
> Reporter: Vineet Reynolds
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.2.0.Beta3
>
>
> When I run a Forge command in console where some special characters are present in the input, the input following the special characters are omitted during processing.
> For example:
> {noformat}
> [Event.java]$ constraint-add --onProperty name --constraint Size --min 5 --max 50 --message "Must be > 5 and < 50"
> aesh: can't redirect to more than one file.
> {noformat}
> which results in the following bit of code being generated:
> {noformat}
> @Column
> @Size(min = 5, max = 50, message = "Must be ")
> private String name;
> {noformat}
> Note the characters following {{'>'}} have been omitted in the generated annotation attribute value.
> This is not a problem with the Eclipse GUI, so I guess this is an Aesh+Forge issue involving escaping of such characters.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months