August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18052) application wizard: use the project name as default application name (when launched via project->configure)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18052?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18052: ------------------------------------- Labels: application_wizard (was: ) > application wizard: use the project name as default application name (when launched via project->configure) > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18052 > URL: https://issues.jboss.org/browse/JBIDE-18052 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Burr Sutter > Priority: Minor > Labels: application_wizard > Fix For: 4.2.0.CR1 > > > The application name should default to the project name > http://screencast.com/t/xfyB3OZR -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18052) application wizard: use the project name as default application name (when launched via project->configure)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18052?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18052: ------------------------------------- Summary: application wizard: use the project name as default application name (when launched via project->configure) (was: Default application name to project name) > application wizard: use the project name as default application name (when launched via project->configure) > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18052 > URL: https://issues.jboss.org/browse/JBIDE-18052 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Burr Sutter > Priority: Minor > Fix For: 4.2.0.CR1 > > > The application name should default to the project name > http://screencast.com/t/xfyB3OZR -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18052) Default application name to project name

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18052?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18052: ------------------------------------- Fix Version/s: 4.2.0.CR1 > Default application name to project name > ---------------------------------------- > > Key: JBIDE-18052 > URL: https://issues.jboss.org/browse/JBIDE-18052 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Burr Sutter > Fix For: 4.2.0.CR1 > > > The application name should default to the project name > http://screencast.com/t/xfyB3OZR -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18052) Default application name to project name

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18052?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-18052: ------------------------------------- Priority: Minor (was: Major) > Default application name to project name > ---------------------------------------- > > Key: JBIDE-18052 > URL: https://issues.jboss.org/browse/JBIDE-18052 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Burr Sutter > Priority: Minor > Fix For: 4.2.0.CR1 > > > The application name should default to the project name > http://screencast.com/t/xfyB3OZR -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17948) Default Focus in 'Entity name' field in JPA: New Entity wizard

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17948?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-17948. ------------------------------------- Assignee: George Gastaldi Resolution: Done > Default Focus in 'Entity name' field in JPA: New Entity wizard > --------------------------------------------------------------- > > Key: JBIDE-17948 > URL: https://issues.jboss.org/browse/JBIDE-17948 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Minor > Fix For: 4.2.0.CR1 > > > It would be more handy to have focus in 'Entity name' field rather than in 'Target package' field by default. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18052) Default application name to project name

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18052?page=com.atlassian.jira.plugi... ] Burr Sutter commented on JBIDE-18052: ------------------------------------- Yes - but I notice the wizard has you pick the "eclipse project" in a later step - this whole app name vs eclipse project name has always throw me off, so I was hoping for more clever defaults. So, I, the end-user can more readily just hit Next-Next-Next-Finish and go get coffee :-) > Default application name to project name > ---------------------------------------- > > Key: JBIDE-18052 > URL: https://issues.jboss.org/browse/JBIDE-18052 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Burr Sutter > > The application name should default to the project name > http://screencast.com/t/xfyB3OZR -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17986) Bundled version of m2e-mavenarchiver is broken

by Rich DiCroce (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Rich DiCroce commented on JBIDE-17986: -------------------------------------- Sorry about the delay, the e-mail got lost in my in-box. Yes, I'm using the Java EE install. > Bundled version of m2e-mavenarchiver is broken > ---------------------------------------------- > > Key: JBIDE-17986 > URL: https://issues.jboss.org/browse/JBIDE-17986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, maven, target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Rich DiCroce > Assignee: Fred Bricon > Fix For: 4.2.0.CR1 > > > The version of m2e-mavenarchiver that is bundled in JBoss Tools seems to be broken. I was not getting any descriptors generated. Upgrading to the latest version fixes the problem. See http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2eclipse... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18053) Add Powermock to the target platform

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18053?page=com.atlassian.jira.plugi... ] Paul Richardson commented on JBIDE-18053: ----------------------------------------- [~nickboldt] Designer has little need for powermock at the moment since our tests have moved away from testing classes and towards testing interfaces. Consequently, mockito has served as the prime library for this. Looking at the specific use case of mocking a file, our tests have tended to create a temp file and blow it away afterwards. Not saying this would be appropriate for this use case but has allowed Designer to avoid needing to mock the File class. > Add Powermock to the target platform > ------------------------------------ > > Key: JBIDE-18053 > URL: https://issues.jboss.org/browse/JBIDE-18053 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.x > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > Reason: To improving testing by allowing the stubbing of scenerios like "new File(path).exists()" which require bytecode modifications in order to accomplish. Example of intended use: https://gist.github.com/jcantrill/fd83c27d3fc542742ec7 > License and owner: Apache 2.0 / https://github.com/jayway > Original repo: https://github.com/jayway/powermock > JBoss mirror: Unknown > Sources: Unknown > Affected projects: > Include in JBDS: *No* > Type of dependency: testing > List of bundles added/removed: > {code} > + <unit id="org.powermock.mockito-junit.feature.feature.group" version="1.5.4.1"/> > + <unit id="org.objenesis" version="2.1.0"/> > + <unit id="javassist" version="3.18.1.GA"/> > {code} > If applicable: > non-p2 repository: > non-p2 ids: -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17078) JAX-RS Problems doesn't appears after the JAX-RS Support is activated

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17078?page=com.atlassian.jira.plugi... ] Xavier Coulon reassigned JBIDE-17078: ------------------------------------- Assignee: Radoslav Rábara (was: Xavier Coulon) Can you try with the next nightly build ? It could not reproduce it (again). Using the sample class provided in the description of JBIDE-17988, I had a warning when activating the support for JAX-RS, with a message saying that there was not JAX-RS Activator defined in the project. Thanks > JAX-RS Problems doesn't appears after the JAX-RS Support is activated > --------------------------------------------------------------------- > > Key: JBIDE-17078 > URL: https://issues.jboss.org/browse/JBIDE-17078 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core, webservices > Affects Versions: 4.2.0.Beta1 > Reporter: Radoslav Rábara > Assignee: Radoslav Rábara > Fix For: 4.2.0.CR1 > > > JAX-RS validation runs when there is a change in the project with JAX-RS Support. However, it doesn't run right after the JAX-RS Support is enabled. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-221) Move files in developer workspaces in SVN to examples folder in trunk for automated publishing to download.jboss.org/jbosstools/examples/

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-221?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-221: ---------------------------------- I'm not suggesting we MOVE old stuff, but rather that we COPY the old stuff into a new place from which ongoing maintenance would occur (like when we migrated from SVN -> Github). So the old stuff, if referenced by JBDS 7 and earlier, would still exist in the old/ugly locations, but from JBDS 8 onward only the CORRECT URLs would be used in the examples *.xml files on download.jboss.org. I also like the idea of co-locating these examples in the projects for which they are relevant, as Brian did for ESB. [~bfitzpat] did you also get the examples from Rob C, and the BPEL examples? And what of the floor show that had been spoken of? In an empty house? In the middle of the night? What diabolical plan had seized Fitz' crazed imagination? [1] [1] http://lmgtfy.com/?q=and%20what%20of%20the%20floorshow? > Move files in developer workspaces in SVN to examples folder in trunk for automated publishing to download.jboss.org/jbosstools/examples/ > ----------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBTIS-221 > URL: https://issues.jboss.org/browse/JBTIS-221 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Security Level: Public(Everyone can see) > Reporter: Nick Boldt > Assignee: Fred Bricon > Labels: f2f2012 > Attachments: anonsvn.jboss.org_refs_in_examples_xml.txt > > > Instead of referencing files in dev workspaces, commit your files into this path in SVN [1] and they'll appear automatically [2] after the next rsync here [3]. Then you can point at a path that's served via a download server (file tracking, better throughput, backups) instead of our anonsvn web UI (slow, untracked). > [1] https://svn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosstool... > [2] http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j... > [3] http://download.jboss.org/jbosstools/examples/ > These files (line numbers shown) need fixing: > {code} > ./project-examples-jbds40.xml > 851: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design... > 877: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design... > 894: http://anonsvn.jboss.org/repos/jbosstools/workspace/jdoyle/teiid-designer... > ./project-examples-3.2.xml > 17: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design... > 43: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design... > 60: http://anonsvn.jboss.org/repos/jbosstools/workspace/jdoyle/teiid-designer... > {code} -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2014