jboss-development May 2007

jboss-development@lists.jboss.org

24 participants
1005 discussions

Start a nNew thread

jboss-4.2-testsuite-sun-1.5 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

19 years, 2 months

1
0
0 / 0

jboss-head-jdk-matrix Build Failed

by jboss-qa-internal＠redhat.com

19 years, 2 months

1
0
0 / 0

jboss-head-jdk-matrix Build Failed

by jboss-qa-internal＠redhat.com

19 years, 2 months

1
0
0 / 0

jboss-remoting-testsuite-1.6 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

19 years, 2 months

1
0
0 / 0

jboss-remoting-testsuite-1.5 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

19 years, 2 months

1
0
0 / 0

jboss-4.0-testsuite-sun-1.4 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

19 years, 2 months

1
0
0 / 0

jboss-4.2-testsuite-sun-1.5 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

19 years, 2 months

1
0
0 / 0

Re: [jboss-dev] SVN properties in trunk

by David M. Lloyd

On Thu, 24 May 2007 18:48:24 +0200 Mladen Turk <mturk(a)redhat.com> wrote: You are mixing development with release. > If someone is releasing on windows, then he must use > svn export --native-eol LF and then make a release. Assuming they remember to do that. > I presume no one is doing a release from his development > repository. However if that is the fact, then there is > something wrong with our release procedure. This is not true if you fix eol-style to LF. One could simply "svn switch" to the release tag. Assuming the project has a sane build system, you could then do a clean build with identical results as "svn export", without having to remember to force it to use LF every time you do a release. - DML

19 years, 2 months

1
0
0 / 0

jboss-seam-testsuite Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

19 years, 2 months

1
0
0 / 0

Fw: [jboss-dev] SVN properties in trunk

by David M. Lloyd

On Thu, 24 May 2007 18:10:58 +0200 Mladen Turk <mturk(a)redhat.com> wrote: > That's why you have --native-eol LF > > And what would happen if you have build stamp in manifest, > different JDK, etc... Not an valid argument. This may be true in this case, but my other argument still stands - LFs are usable on Windows, but CR/LF is not usable on Linux/Solaris/OS X/etc. - DML

19 years, 2 months

1
0
0 / 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-development May 2007