May 2012 - jbosstools-issues - Jboss List Archives

[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-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

[JBoss JIRA] (JBIDE-11512) Create a script or sthg like that to create new "branch" jobs from trunk.

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11512: -------------------------------------- Summary: Create a script or sthg like that to create new "branch" jobs from trunk. Key: JBIDE-11512 URL: https://issues.jboss.org/browse/JBIDE-11512 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: Build/Releng Reporter: Mickael Istria Assignee: Nick Boldt Priority: Minor In Jenkins, Since betaX is a fork from trunk, it would be more convenient to find a way to create the betaX jobs and view as a fork of Trunk jobs. It would prevent from having to backport stuff all the time, and would make the jobs follow the same logic as code. Please list there the technical issues that this script will have to deal with. -- 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
13
0 / 0

[JBoss JIRA] (JBIDE-11645) Server JBoss AS 7.1.1 final start is not detected after installing JAX-RS and Web Services features

by Jaroslav Jankovič (JIRA)

Jaroslav Jankovič created JBIDE-11645: ----------------------------------------- Summary: Server JBoss AS 7.1.1 final start is not detected after installing JAX-RS and Web Services features Key: JBIDE-11645 URL: https://issues.jboss.org/browse/JBIDE-11645 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers, Webservices Affects Versions: 3.3.0.Beta3 Environment: Eclipse IDE for Java EE Developers 3.7.2 / Eclipse IDE for Java Developers 3.7.2, Linux x86-64b, JDK version: 1.6.0_29 Reporter: Jaroslav Jankovič Assignee: Rob Stryker Priority: Critical Fix For: 3.3.0.Beta3 In fresh Eclipse 3.7.2 (IDE for Java EE / IDE for Java Developers) after installing JBoss JAX-RS and JBoss Web Services features, the start of JBoss AS 7.1.1 final is not detected. -- 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

5
12
0 / 0

[JBoss JIRA] Created: (JBIDE-8667) improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs

by Nick Boldt (JIRA)

improve publishing of component sites using composite metadata so that content doesn't vanish and break downstream jobs ----------------------------------------------------------------------------------------------------------------------- Key: JBIDE-8667 URL: https://issues.jboss.org/browse/JBIDE-8667 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Nick Boldt (2011-04-01 10:11:04) nickboldt: and while I'd love to do: (2011-04-01 10:11:12) nickboldt: mkdir whatever-new (2011-04-01 10:11:22) nickboldt: rsync newstuff whatever-new (2011-04-01 10:11:25) nickboldt: rm -fr whatever (2011-04-01 10:11:29) nickboldt: mv whatever-new whatever (2011-04-01 10:11:43) nickboldt: so that the time between "it's there" and "it's there and updated" is less (2011-04-01 10:11:52) nickboldt: I CANNOT with the current infra we have (2011-04-01 10:12:03) nickboldt: instead I can do an rsync --delete and push into the same folder on top (2011-04-01 10:12:16) nickboldt: but that means that the metadata will oft be out of whack w.r.t the site content (2011-04-01 10:12:17) maxandersen: hmmm (2011-04-01 10:12:41) nickboldt: if you can think of a way to do a "push then rename" instead of "push into existing and clean out cruft" (2011-04-01 10:12:51) nickboldt: over sftp via a script (non-interactive) then I'm all ears (2011-04-01 10:13:26) nickboldt: I can't push a script there and run it, or simply connect over ssh and run a script directly (2011-04-01 10:13:35) maxandersen: well what I was thinking was to do a push of new site into new dir, push site.xml/compositewhatever pointing to new dir and then rsync delete the existing one.. (2011-04-01 10:14:10) maxandersen: sftp rm should work? (2011-04-01 10:14:13) nickboldt: MIGHT be able to do sftp delete (2011-04-01 10:14:39) maxandersen: if you control it with a composite artifact you dont need to rename anything (2011-04-01 10:14:51) maxandersen: except the content pointer in there which you know "locally" (2011-04-01 10:15:01) nickboldt: true... so I'd need a tool to do a one line swap in the composite*.xml files (2011-04-01 10:15:13) nickboldt: remove ref to old site, replace w/ ref to new site (2011-04-01 10:15:17) nickboldt: and then delete the old one 1. generate composite metadata files on the fly 2. publish that into root dir, all/repo/ 3. purge previous build's folder over scripted sftp? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

7
44
0 / 0

[JBoss JIRA] Created: (JBIDE-4810) Create JUnit Test Suite for every component in repository

by Denis Golovin (JIRA)

Create JUnit Test Suite for every component in repository --------------------------------------------------------- Key: JBIDE-4810 URL: https://jira.jboss.org/jira/browse/JBIDE-4810 Project: Tools (JBoss Tools) Issue Type: Sub-task Reporter: Denis Golovin Assignee: Denis Golovin -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 6 months

3
16
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 May 2012