July 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2235) Investigate use of GWT 2.6.1 in JBoss Central & JBDS Extras sites

by Nick Boldt (JIRA)

13 years, 6 months

2
17
0 / 0

[JBoss JIRA] (JBIDE-11687) Add Mac x86_64 and Win x86_64 to target platform in parent pom

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-11687: --------------------------------------- Summary: Add Mac x86_64 and Win x86_64 to target platform in parent pom Key: JBIDE-11687 URL: https://issues.jboss.org/browse/JBIDE-11687 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Affects Versions: 3.3.0.Beta3 Reporter: Lucia Jelinkova Assignee: Nick Boldt Plugin configuration for org.eclipse.tycho:target-platform-configuration does not intentionally specify the Mac x86_64 and Win x86_64 environments since these entries break XulRunner build. However, QE would like to run SWTBot tests also on these environments and overriding the configuration in every bot test plugin is probably not a good idea. One solution could be to specify those environments in parent pom and override it only in XullRunner's pom file (the requirement not to specify the environments would be clearly defined and documented for XullRunner). Other solution might be to specify a profile that we could activate on the command line that would add those two environments to the plugin's configuration. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
8
0 / 0

[JBoss JIRA] (JBIDE-12236) Download runtime dialog - the URL field should be greyed out

by Lucia Jelinkova (JIRA)

13 years, 6 months

4
10
0 / 0

[JBoss JIRA] (JBIDE-11621) SVN based jobs fail to send email notifications due to "No author in changeset" at hudson.plugins.git.GitChangeSet.getAuthor, and job fails

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11621: ---------------------------------- Summary: SVN based jobs fail to send email notifications due to "No author in changeset" at hudson.plugins.git.GitChangeSet.getAuthor, and job fails Key: JBIDE-11621 URL: https://issues.jboss.org/browse/JBIDE-11621 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta3 Reporter: Nick Boldt Assignee: Nick Boldt Priority: Blocker {code} ERROR: Publisher hudson.tasks.Mailer aborted due to exception java.lang.RuntimeException: No author in changeset ee602dc8116843c09f46beb374071a1547c1120b at hudson.plugins.git.GitChangeSet.getAuthor(GitChangeSet.java:240) at hudson.model.AbstractBuild.hasParticipant(AbstractBuild.java:357) {code} This error has been happening a lot lately. Most of our jobs source from SVN, yet we're seeing GitChangeSet.getAuthor() being called to send email notifications of build failures. WTH? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
9
0 / 0

[JBoss JIRA] (JBIDE-11155) consider caching svn sources outside Jenkins workspaces

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-11155: ---------------------------------- Summary: consider caching svn sources outside Jenkins workspaces Key: JBIDE-11155 URL: https://issues.jboss.org/browse/JBIDE-11155 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.Beta2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.Beta2 >From JBIDE-10974: > 9. Every change in build component triggers full rebuild for all components 9. This could be fixed by instead of watching the /build folder in SVN for changes, we simply fetch it using `svn co` or `svn up` as a prelim step in the job. Perhaps taking this a step further, we could fetch the whole SVN tree and store it outside the workspaces so that jobs would simply re-use local shared space instead of clean-fetching everything every time they run on a new slave. This would of course make jobs "more tied to infrastructure" and "harder to build the same way offline" but that's the price you pay for optimizing for speed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
12
0 / 0

[JBoss JIRA] (JBIDE-10197) Deployment assembly missbehaves - workaround with fileset

by Dirk Dollar (Created) (JIRA)

Deployment assembly missbehaves - workaround with fileset --------------------------------------------------------- Key: JBIDE-10197 URL: https://issues.jboss.org/browse/JBIDE-10197 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.2.0.Final Environment: Eclipse helios 3.6.2 Reporter: Dirk Dollar Assignee: Rob Stryker Priority: Minor This is my first bugreport... if I'm doing something wrong or chose the wrong component (something) - please be forgiving :-) so I had a couple days to figure this one out - the deployment assembly is misbehaving similarly (but differnt) to older versions when it was used under a different name (J2EE module dependencies i think). So when I add a folder e.g. WebContent and want it to deploy to / it will not work or more accurately - under certain circumstances it will stop working. E.g. I think after adding some additional libraries to deploy to webcontent/lib. I suspect the problem is that it gets deleted before deploying. The workaround for me was to use a fileset of the <projectname>/WebContent folder and to point it to an empty deploy path - and to scream in rage at everyone who dared to touch any settings in there. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

10
23
0 / 0

[JBoss JIRA] (JBIDE-11398) Make H2 a first class citizen for JBDC Connection Setup

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-11398: ----------------------------------- Summary: Make H2 a first class citizen for JBDC Connection Setup Key: JBIDE-11398 URL: https://issues.jboss.org/browse/JBIDE-11398 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Burr Sutter Attachments: Screen Shot 2012-03-25 at 1.15.57 PM.png H2 is not in the list of possible databases. Attached is a series of screenshots that illustrate what it takes to configure H2 against the sakila database - to then allow for JPA generate entities from tables. https://github.com/maxandersen/sakila-h2 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
17
0 / 0

[JBoss JIRA] (JBIDE-12222) turning project into maven project causes compilation error

by Andre Dietisheim (JIRA)

13 years, 6 months

4
16
0 / 0

[JBoss JIRA] (JBIDE-11436) we should use license features

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11436: ------------------------------------------- Summary: we should use license features Key: JBIDE-11436 URL: https://issues.jboss.org/browse/JBIDE-11436 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Reporter: Max Rydahl Andersen Assignee: Mickael Istria Priority: Blocker Fix For: 3.3.0.Beta3 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-11319) Use Eclipse-SourceReferences

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11319: -------------------------------------- Summary: Use Eclipse-SourceReferences Key: JBIDE-11319 URL: https://issues.jboss.org/browse/JBIDE-11319 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Nick Boldt Priority: Optional In order to provide nice entry points to turn users into contributors, it could be efficient to set Eclipse-SourceReferences in Manifest: http://wiki.eclipse.org/PDE/UI/SourceReferences -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
8
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 July 2012