[JBoss JIRA] (JBIDE-13035) Mave Repositories : TextMerge Preview always shows whitespace changes on Windows
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13035?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-13035:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.0.x)
> Mave Repositories : TextMerge Preview always shows whitespace changes on Windows
> --------------------------------------------------------------------------------
>
> Key: JBIDE-13035
> URL: https://issues.jboss.org/browse/JBIDE-13035
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, upstream
> Affects Versions: 4.0.0.Beta2
> Environment: Windows 7 pro 64
> Reporter: Fred Bricon
> Assignee: Alexey Kazakov
> Fix For: 4.5.0.AM1
>
> Attachments: Text_Merge_preview_show_whitespace_changes.png
>
>
> On Windows, the Maven Repositories wizard's preview pane always shows whitespace changes, diminishing the preview usefulness.
> !Text_Merge_preview_show_whitespace_changes.png!
> I tried to mess with the code a bit but to no avail. I suspected some line endings weirdness, but it seems to be really a problem with white spaces. I tried to compare the contents of my original settings.xml, to the contents in both panels, using an hex editor, they really are identical.
> I don't have any issue on linux.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-2356) JEE project example generates warnings
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-2356?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-2356:
-----------------------------
Fix Version/s: 10.3.0.AM1
(was: 6.0.2.GA)
> JEE project example generates warnings
> --------------------------------------
>
> Key: JBDS-2356
> URL: https://issues.jboss.org/browse/JBDS-2356
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 6.0.0.Alpha2
> Environment: Version: 6.0.0.Alpha2
> Build id: Alpha2-v20121004-2330-B40
> Build date: 20121004-2330
> Reporter: Len DiMaggio
> Assignee: Marius Bogoevici
> Labels: examplewarnings
> Fix For: 10.3.0.AM1
>
>
> The JEE project example generates these warnings:
> jboss-javaee6-multi-ejb
> No connection specified for project. No database-specific validation will be performed.
> The import javax.persistence.PersistenceContext is never used
> WebResources.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util
> line 10
> The import javax.enterprise.event.Event is never used
> MemberController.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/controller
> line 6
> The import javax.persistence.EntityManager is never used
> WebResources.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util
> line 9
> The import java.util.logging.Logger is never used
> MemberController.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/controller
> line 3
> The import javax.enterprise.inject.spi.InjectionPoint is never used
> WebResources.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util
> line 7
> The import java.util.logging.Logger is never used
> WebResources.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util
> line 3
> Unnecessary @SuppressWarnings("unused") Resources.java
> /jboss-javaee6-multi-ejb/src/main/java/org/jboss/tools/example/util
> line 24
> No connection specified for project. No database-specific validation will be performed.
> jboss-javaee6-multi-ejb
> The import javax.persistence.EntityManager is never used
> MemberController.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/controller
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-2356) JEE project example generates warnings
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-2356?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-2356:
--------------------------------
Assignee: Fred Bricon (was: Marius Bogoevici)
> JEE project example generates warnings
> --------------------------------------
>
> Key: JBDS-2356
> URL: https://issues.jboss.org/browse/JBDS-2356
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 6.0.0.Alpha2
> Environment: Version: 6.0.0.Alpha2
> Build id: Alpha2-v20121004-2330-B40
> Build date: 20121004-2330
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Labels: examplewarnings
> Fix For: 10.3.0.AM1
>
>
> The JEE project example generates these warnings:
> jboss-javaee6-multi-ejb
> No connection specified for project. No database-specific validation will be performed.
> The import javax.persistence.PersistenceContext is never used
> WebResources.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util
> line 10
> The import javax.enterprise.event.Event is never used
> MemberController.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/controller
> line 6
> The import javax.persistence.EntityManager is never used
> WebResources.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util
> line 9
> The import java.util.logging.Logger is never used
> MemberController.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/controller
> line 3
> The import javax.enterprise.inject.spi.InjectionPoint is never used
> WebResources.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util
> line 7
> The import java.util.logging.Logger is never used
> WebResources.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/util
> line 3
> Unnecessary @SuppressWarnings("unused") Resources.java
> /jboss-javaee6-multi-ejb/src/main/java/org/jboss/tools/example/util
> line 24
> No connection specified for project. No database-specific validation will be performed.
> jboss-javaee6-multi-ejb
> The import javax.persistence.EntityManager is never used
> MemberController.java
> /jboss-javaee6-multi-web/src/main/java/org/jboss/tools/example/controller
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-2355) JEE web project example generates warnings
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-2355?page=com.atlassian.jira.plugin.... ]
Jeff MAURY updated JBDS-2355:
-----------------------------
Fix Version/s: 10.3.0.AM1
(was: 6.0.2.GA)
> JEE web project example generates warnings
> ------------------------------------------
>
> Key: JBDS-2355
> URL: https://issues.jboss.org/browse/JBDS-2355
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 6.0.0.Alpha2
> Environment: Version: 6.0.0.Alpha2
> Build id: Alpha2-v20121004-2330-B40
> Build date: 20121004-2330
> Reporter: Len DiMaggio
> Assignee: Marius Bogoevici
> Labels: examplewarnings
> Fix For: 10.3.0.AM1
>
>
> The JEE web project example generates these warnings:
> The import java.util.logging.Logger is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 3
> No connection specified for project. No database-specific validation will be performed.
> jboss-javaee6-webapp
> Unnecessary @SuppressWarnings("unused") Resources.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/util
> line 26
> The import javax.persistence.EntityManager is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 14
> The import javax.enterprise.event.Event is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 7
> The import javax.ejb.Stateful is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 6
> The import org.jboss.tools.examples.controller.MemberController is never used
> MemberRegistrationTest.java
> /jboss-javaee6-webapp/src/test/java/org/jboss/tools/examples/test
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-2355) JEE web project example generates warnings
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBDS-2355?page=com.atlassian.jira.plugin.... ]
Jeff MAURY reassigned JBDS-2355:
--------------------------------
Assignee: Fred Bricon (was: Marius Bogoevici)
> JEE web project example generates warnings
> ------------------------------------------
>
> Key: JBDS-2355
> URL: https://issues.jboss.org/browse/JBDS-2355
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: central
> Affects Versions: 6.0.0.Alpha2
> Environment: Version: 6.0.0.Alpha2
> Build id: Alpha2-v20121004-2330-B40
> Build date: 20121004-2330
> Reporter: Len DiMaggio
> Assignee: Fred Bricon
> Labels: examplewarnings
> Fix For: 10.3.0.AM1
>
>
> The JEE web project example generates these warnings:
> The import java.util.logging.Logger is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 3
> No connection specified for project. No database-specific validation will be performed.
> jboss-javaee6-webapp
> Unnecessary @SuppressWarnings("unused") Resources.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/util
> line 26
> The import javax.persistence.EntityManager is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 14
> The import javax.enterprise.event.Event is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 7
> The import javax.ejb.Stateful is never used
> MemberController.java
> /jboss-javaee6-webapp/src/main/java/org/jboss/tools/examples/controller
> line 6
> The import org.jboss.tools.examples.controller.MemberController is never used
> MemberRegistrationTest.java
> /jboss-javaee6-webapp/src/test/java/org/jboss/tools/examples/test
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-12452) Add support for creating and auto-discovering JBoss AS "user instances"
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12452?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-12452:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.2.x)
> Add support for creating and auto-discovering JBoss AS "user instances"
> -----------------------------------------------------------------------
>
> Key: JBIDE-12452
> URL: https://issues.jboss.org/browse/JBIDE-12452
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 3.3.1.Final
> Environment: Fedora 17 and above
> Fedora JBoss AS package (jboss-as)
> Reporter: Dan Allen
> Fix For: 4.5.0.AM1
>
>
> The Fedora JBoss AS package supports creating user instances of JBoss AS. A user instance allows an unprivileged user to run JBoss AS out of that user's home directory. An instance is created using the jboss-as-cp script. For example:
> {code}
> jboss-as-cp -l $HOME/applications/jboss-as-user-instance
> {code}
> The user instance is skinny, meaning it only contains the configuration files for the instance. The libraries are kept in the system instance and referenced by the custom startup script:
> {code}
> JBOSS_BASE_DIR=$HOME/applications/jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml
> {code}
> JBoss Tools does not currently auto-detect these instances. However, it could offer to create and/or auto-discover them.
> It's possible to get JBoss Tools to control the user instance, but it requires tweaking the startup flags in the server configuration. Here's how:
> 1. Have JBoss AS auto-discover the system instance at /usr/share/java
> 2. Open the server launch configuration
> 3. Uncheck the box "Always update arguments related to the runtime" so our changes don't get overwritten
> 4. Replace the VM arguments that contain "jboss" with:
> -Dorg.jboss.boot.log.file=${env_var:HOME}/applications/jboss-as-user-instance/log/boot.log -Dlogging.configuration=file:${env_var:HOME}/applications/jboss-as-user-instance/configuration/logging.properties -Djboss.home.dir=/usr/share/jboss-as -Djboss.server.base.dir=${env_var:HOME}/applications/jboss-as-user-instance
> Having native support for JBoss AS to auto-detect and configure user instances would be ideal.
> If changes are required in the jboss-as-cp script, please use this issue tracker: https://bugzilla.redhat.com/buglist.cgi?component=jboss-as&product=Fedora...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-12452) Add support for creating and auto-discovering JBoss AS "user instances"
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12452?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-12452:
----------------------------------
Assignee: Rob Stryker
> Add support for creating and auto-discovering JBoss AS "user instances"
> -----------------------------------------------------------------------
>
> Key: JBIDE-12452
> URL: https://issues.jboss.org/browse/JBIDE-12452
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 3.3.1.Final
> Environment: Fedora 17 and above
> Fedora JBoss AS package (jboss-as)
> Reporter: Dan Allen
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM1
>
>
> The Fedora JBoss AS package supports creating user instances of JBoss AS. A user instance allows an unprivileged user to run JBoss AS out of that user's home directory. An instance is created using the jboss-as-cp script. For example:
> {code}
> jboss-as-cp -l $HOME/applications/jboss-as-user-instance
> {code}
> The user instance is skinny, meaning it only contains the configuration files for the instance. The libraries are kept in the system instance and referenced by the custom startup script:
> {code}
> JBOSS_BASE_DIR=$HOME/applications/jboss-as-user-instance /usr/share/jboss-as/bin/standalone.sh -c standalone-web.xml
> {code}
> JBoss Tools does not currently auto-detect these instances. However, it could offer to create and/or auto-discover them.
> It's possible to get JBoss Tools to control the user instance, but it requires tweaking the startup flags in the server configuration. Here's how:
> 1. Have JBoss AS auto-discover the system instance at /usr/share/java
> 2. Open the server launch configuration
> 3. Uncheck the box "Always update arguments related to the runtime" so our changes don't get overwritten
> 4. Replace the VM arguments that contain "jboss" with:
> -Dorg.jboss.boot.log.file=${env_var:HOME}/applications/jboss-as-user-instance/log/boot.log -Dlogging.configuration=file:${env_var:HOME}/applications/jboss-as-user-instance/configuration/logging.properties -Djboss.home.dir=/usr/share/jboss-as -Djboss.server.base.dir=${env_var:HOME}/applications/jboss-as-user-instance
> Having native support for JBoss AS to auto-detect and configure user instances would be ideal.
> If changes are required in the jboss-as-cp script, please use this issue tracker: https://bugzilla.redhat.com/buglist.cgi?component=jboss-as&product=Fedora...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-12161) Deploy application to JBoss AS 7 in domain mode
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12161?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-12161:
------------------------------------
[~rob.stryker]can you check if this is still relevant
> Deploy application to JBoss AS 7 in domain mode
> -----------------------------------------------
>
> Key: JBIDE-12161
> URL: https://issues.jboss.org/browse/JBIDE-12161
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 3.3.0.CR1
> Environment: Any.
> Reporter: Humberto Ferreira da Luz Jr.
> Assignee: Rob Stryker
> Labels: f2f2012
> Fix For: 4.5.0.AM1
>
>
> I think JBoss Tools should be able to deploy an application to JBoss AS 7 in domain mode.
> We would choose an specific server group (or any) and the application would be automatically deployed (I guess JBoss AS CLI could be directly used by JBoss Tools instead of ftp, ssh...).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-12161) Deploy application to JBoss AS 7 in domain mode
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12161?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-12161:
-------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.2.x)
> Deploy application to JBoss AS 7 in domain mode
> -----------------------------------------------
>
> Key: JBIDE-12161
> URL: https://issues.jboss.org/browse/JBIDE-12161
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 3.3.0.CR1
> Environment: Any.
> Reporter: Humberto Ferreira da Luz Jr.
> Assignee: Rob Stryker
> Labels: f2f2012
> Fix For: 4.5.0.AM1
>
>
> I think JBoss Tools should be able to deploy an application to JBoss AS 7 in domain mode.
> We would choose an specific server group (or any) and the application would be automatically deployed (I guess JBoss AS CLI could be directly used by JBoss Tools instead of ftp, ssh...).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBDS-3866) vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3866?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3866:
----------------------------------
Slip to 10.3.0.AM1. [~rob.stryker] please have a look. if this is done, set the fixversion back to 10.2.0.GA and mark it resolved.
> vagrant up failed due to rsync error, eclipse tooling confused about state of cdk server
> ----------------------------------------------------------------------------------------
>
> Key: JBDS-3866
> URL: https://issues.jboss.org/browse/JBDS-3866
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit.
> (previous installs of CDK and dependencies)
> Reporter: Robert Terzi
> Assignee: Rob Stryker
> Fix For: 10.3.0.AM1
>
>
> vagrant up through the CDK server tooling failed because of an rsync problem. The tooling lost track of the state of the vagrant box. The vagrant box couldn't be stopped from inside of Eclipse.
> The vagrant up failed because of an error with rsync. Something was confused about the user's home directory. It was trying to write to /home/username/.ssh, however, $HOME isn't /home/username, it's /cygdrive/c/Users/username, so /home/username/ doesn't exist.
> The CDK server was shown as 'Started, Sychronized'.
> The error message appeared in the server console tab. However the stop button wouldn't work. Provisioning had never finished so the OpenShift connection wasn't working either.
> Synchronized seems misleading here, since no files had been sync'd yet.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months