[JBoss JIRA] (JBIDE-13698) Build As submenu
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13698?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13698:
----------------------------------------
Fix Version/s: 4.1.0.Beta1
> Build As submenu
> ----------------
>
> Key: JBIDE-13698
> URL: https://issues.jboss.org/browse/JBIDE-13698
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Reporter: Burr Sutter
> Fix For: 4.1.0.Beta1
>
> Attachments: Screen Shot 2013-03-01 at 8.03.01 AM.png
>
>
> This is a usability issue - new users to Eclipse struggle with finding the "mvn package" or "mvn install" options hidden in the JBDS menu. Having those under Run As is simply not intuitive. Not too mention that there is a Maven menu, that does not have the build options - which would have been slightly more intuitive.
> One proposal is a Build As menu - where I can issue my various mvn commands.
> Screenshot of current JBDS 7 context menu (right-click) on a project attached.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14323) Maven Update Project should be hotkey bindable
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14323?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14323:
---------------------------------------------
For those who don't know or remember the big performance boost from old m2e to new m2e is that it does *not* automatically run the "update project configuration" since it has sideeffects which in common cases can cause recursive triggering of "update project configuration".
Thus it is not automatically done since it had bad sideeffects.
That said I think there are two things that could be done here:
A) open a RFE against m2e to atleast make "Update project configuration" a command so it can be hotkey bindable AND at least possible to show up in Cmd+3 (quick access)
B) Look into if one could not detect via the pom hiearchy to run an "update project configuration" when something that is a parent pom gets updated - run that update project configuration and have a "lock" to prevent it from triggering again automatically. It would be a "poor man" version of what was there in the past but if a user can invoke this across multiple projects then the IDE should be able to do it too without causing havoc.
> Maven Update Project should be hotkey bindable
> ----------------------------------------------
>
> Key: JBIDE-14323
> URL: https://issues.jboss.org/browse/JBIDE-14323
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven, upstream
> Affects Versions: 4.1.0.Alpha1
> Reporter: Lincoln Baxter III
> Fix For: 4.1.0.Beta2
>
>
> Currently it is not possible to bind a hotkey shortcut to "maven-->update project", forcing the user to go to the mouse and do a lot of clicking. This is a pretty big problem when projects go out of sync so frequently in larger projects ;)
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-13788) mvn package
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13788?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13788:
----------------------------------------
Fix Version/s: 4.1.0.Beta1
> mvn package
> -----------
>
> Key: JBIDE-13788
> URL: https://issues.jboss.org/browse/JBIDE-13788
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Reporter: Burr Sutter
> Fix For: 4.1.0.Beta1
>
> Attachments: 2013-03-13_1738.png, Screen Shot 2013-03-13 at 5.39.10 PM.png
>
>
> In Java EE land you tend to use "mvn package", but that is not listed in the menu, nor is it visible in the dialog. Not too mention, having the Maven commands under the Run menu option, instead of the Maven menu is counter-intuitive.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-13626) 3 test failures in jsp/jsf/xml/html source editing
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13626?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13626:
----------------------------------------
Fix Version/s: 4.1.0.Beta1
> 3 test failures in jsp/jsf/xml/html source editing
> --------------------------------------------------
>
> Key: JBIDE-13626
> URL: https://issues.jboss.org/browse/JBIDE-13626
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.1.0.Beta1
>
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_4.1.kepler/job/jbosstools-jst_41/4/testReport/}
> Test Result
> 3 failures
> 101 tests
> Took 3 min 34 sec.
> add description
> All Failed Tests
> Test Name Duration Age
> >>> org.jboss.tools.jst.web.ui.test.NewCheckboxWizardTest.testNewCheckboxWizard 8.8 sec 3
> >>> org.jboss.tools.test.util.ProjectImportTestSetup.org.jboss.tools.jst.web.ui.test.NewCheckboxWizardTest 9.3 sec 3
> >>> org.jboss.tools.jst.css.test.jbide.InputFractionalValueTest_JBIDE4790.testInputFractionalValue 2.4 sec 4
> {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
12 years, 11 months
[JBoss JIRA] (JBIDE-14340) "Searching for runtimes" dialog is opened whenever starting JBDS
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14340?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-14340:
---------------------------------------
{quote}
What is the failing usecase?
{quote}
Not sure if I understand, but the issue can be reproduced as follows:
- start JBDS that includes EAP
EAP server will be created automatically.
- restart JBDS
The "Searching for runtimes" dialog will show up.
The issue can also be reproduced in JBT.
> "Searching for runtimes" dialog is opened whenever starting JBDS
> ----------------------------------------------------------------
>
> Key: JBIDE-14340
> URL: https://issues.jboss.org/browse/JBIDE-14340
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.1.0.Alpha2
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
> Priority: Blocker
>
> The dialog shouldn't be opened if the corresponding server is created.
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14305) Error popup when runing schema ddl with Hibernate Configurations
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-14305:
----------------------------------------
Fix Version/s: 4.1.0.Beta1
> Error popup when runing schema ddl with Hibernate Configurations
> -----------------------------------------------------------------
>
> Key: JBIDE-14305
> URL: https://issues.jboss.org/browse/JBIDE-14305
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 4.1.0.Final
> Reporter: labdoui labdoui
> Fix For: 4.1.0.Beta1
>
>
> Using Hibernate 4, and slf4j 1.7.2, I can't runing my ddl schema
> to reproduce the problem just explore the database from hibernate console
> java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V
> at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133)
> at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26)
> at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476)
> at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
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
12 years, 11 months
[JBoss JIRA] (JBIDE-14305) Error popup when runing schema ddl with Hibernate Configurations
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14305?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14305:
---------------------------------------------
It does not happen for me.
Can you please give exact steps and versions of Hibernate that you are using ?
It is probably a version mismatch of sl4j.
> Error popup when runing schema ddl with Hibernate Configurations
> -----------------------------------------------------------------
>
> Key: JBIDE-14305
> URL: https://issues.jboss.org/browse/JBIDE-14305
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: hibernate
> Affects Versions: 4.1.0.Final
> Reporter: labdoui labdoui
> Fix For: 4.1.0.Beta1
>
>
> Using Hibernate 4, and slf4j 1.7.2, I can't runing my ddl schema
> to reproduce the problem just explore the database from hibernate console
> java.lang.NoSuchMethodError: org.slf4j.spi.LocationAwareLogger.log(Lorg/slf4j/Marker;Ljava/lang/String;ILjava/lang/String;[Ljava/lang/Object;Ljava/lang/Throwable;)V
> at org.apache.commons.logging.impl.SLF4JLocationAwareLog.debug(SLF4JLocationAwareLog.java:133)
> at org.hibernate.cfg.reveng.dialect.JDBCMetaDataDialect.getTables(JDBCMetaDataDialect.java:26)
> at org.hibernate.cfg.reveng.JDBCReader.processTables(JDBCReader.java:476)
> at org.hibernate.cfg.reveng.JDBCReader.readDatabaseSchema(JDBCReader.java:74)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter$2.execute(LazyDatabaseSchemaWorkbenchAdapter.java:116)
> at org.hibernate.console.execution.DefaultExecutionContext.execute(DefaultExecutionContext.java:63)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.readDatabaseSchema(LazyDatabaseSchemaWorkbenchAdapter.java:107)
> at org.hibernate.eclipse.console.workbench.LazyDatabaseSchemaWorkbenchAdapter.getChildren(LazyDatabaseSchemaWorkbenchAdapter.java:63)
> at org.hibernate.eclipse.console.workbench.BasicWorkbenchAdapter.fetchDeferredChildren(BasicWorkbenchAdapter.java:106)
> at org.eclipse.ui.progress.DeferredTreeContentManager$1.run(DeferredTreeContentManager.java:235)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
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
12 years, 11 months
[JBoss JIRA] (JBTIS-67) JBDSIS - Add support in Jenkins to promote the update site zip file
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-67?page=com.atlassian.jira.plugin.s... ]
Nick Boldt updated JBTIS-67:
----------------------------
Description:
Enhance the publish Jenkins job
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-aggregate-publ...
to publish the update site zip file as well as the update site itself.
(10:01:01 AM) nboldt: pleacu: would expect to see a zip somewhere like in here, next to the unpacked site: http://download.jboss.org/jbosstools/updates/integration/juno/integration...
...
(10:08:25 AM) nboldt: pleacu: re: https://issues.jboss.org/browse/JBDS-2556?page=com.atlassian.jira.plugin....
(10:08:27 AM) jbott_rhat: Feature Request: [JBDS-2556] JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip [Open, Major, (central), nickboldt] https://issues.jboss.org/browse/JBDS-2556
ref JBDS-2556:
For production of an update site zip for JBDS, we already do that (and put it on the Early Access site). Only thing to do is ensure it's pushed to CSP this time around.
For production of a update site zip for JBDS-IS (Integration Stack / SOA-P/BRMS-P Tooling), I believe that's already being done. Paul Leacu can comment if that's not the case.
was:
Enhance the publich Jenkins job
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-aggregate-publ...
to publish the update site zip file as well as the update site itself.
(10:01:01 AM) nboldt: pleacu: would expect to see a zip somewhere like in here, next to the unpacked site: http://download.jboss.org/jbosstools/updates/integration/juno/integration...
...
(10:08:25 AM) nboldt: pleacu: re: https://issues.jboss.org/browse/JBDS-2556?page=com.atlassian.jira.plugin....
(10:08:27 AM) jbott_rhat: Feature Request: [JBDS-2556] JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip [Open, Major, (central), nickboldt] https://issues.jboss.org/browse/JBDS-2556
ref JBDS-2556:
For production of an update site zip for JBDS, we already do that (and put it on the Early Access site). Only thing to do is ensure it's pushed to CSP this time around.
For production of a update site zip for JBDS-IS (Integration Stack / SOA-P/BRMS-P Tooling), I believe that's already being done. Paul Leacu can comment if that's not the case.
> JBDSIS - Add support in Jenkins to promote the update site zip file
> -------------------------------------------------------------------
>
> Key: JBTIS-67
> URL: https://issues.jboss.org/browse/JBTIS-67
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Affects Versions: 4.1.0
> Reporter: Paul Leacu
> Assignee: Paul Leacu
>
> Enhance the publish Jenkins job
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBTIS-aggregate-publ...
> to publish the update site zip file as well as the update site itself.
> (10:01:01 AM) nboldt: pleacu: would expect to see a zip somewhere like in here, next to the unpacked site: http://download.jboss.org/jbosstools/updates/integration/juno/integration...
> ...
> (10:08:25 AM) nboldt: pleacu: re: https://issues.jboss.org/browse/JBDS-2556?page=com.atlassian.jira.plugin....
> (10:08:27 AM) jbott_rhat: Feature Request: [JBDS-2556] JBDS70_0315, JBDS70_0413: [Commit] (Dev) (P2) Offline - JBDS Update Site Zip [Open, Major, (central), nickboldt] https://issues.jboss.org/browse/JBDS-2556
> ref JBDS-2556:
> For production of an update site zip for JBDS, we already do that (and put it on the Early Access site). Only thing to do is ensure it's pushed to CSP this time around.
> For production of a update site zip for JBDS-IS (Integration Stack / SOA-P/BRMS-P Tooling), I believe that's already being done. Paul Leacu can comment if that's not the case.
--
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
12 years, 11 months