[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, 5 months
[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, 5 months
[JBoss JIRA] (JBIDE-12545) JSF Validation error in Java EE Project
by Rastislav Wagner (JIRA)
Rastislav Wagner created JBIDE-12545:
----------------------------------------
Summary: JSF Validation error in Java EE Project
Key: JBIDE-12545
URL: https://issues.jboss.org/browse/JBIDE-12545
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: project-examples
Affects Versions: 3.3.1, 4.0.0.Alpha1
Reporter: Rastislav Wagner
Assignee: Snjezana Peco
Fix For: 4.0.0.Alpha2
index.xhtml in project Java EE Project (from Central) contains JSF validation error at this line:
<h:commandButton id="register" action="#{memberController.register}" value="Register" styleClass="register"/>
Method must have signature "String method()" but has signature "void method()"
--
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
13 years, 5 months