You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jcs-dev@jakarta.apache.org by Scott Eade <se...@backstagetech.com.au> on 2007/05/08 01:14:45 UTC
Re: Progress towards a release
Thomas: Can I be so bold as to ask you to apply your new found
CodeWrestler expertise to the JCS trunk? Doing this would bring us a
step closer to a release.
TIA,
Scott
Scott Eade wrote:
> So going over the messages triggered by my email of 10 days ago I have
> the following list:
>
> * There are a small number of apparent test failures - Scott noted a
> few, Thomas noted just one.
> I have spent some time today looking at these and Aaron is quite right
> - they do all run successfully. The apparent failures crop up when
> the tests are run via maven on a fast machine - if the test classes
> are executed individually they run just fine. Is there a way we can
> alter these so that they can execute correctly in all cases?
>
> * A review of project.xml revealed a number of dependencies using
> fairly old versions.
> I have just now committed an update that brings most of these up to
> date. I also added the jar and java plugin properties suggested by
> Thomas to explicitly state the compiler version desired by Aaron and
> to include this information in the jar manifest.
>
> * The source headers are still to be updated. I was thinking that
> this should wait until the all the tests pass, but since they actually
> do there is no longer any need to hold off doing this. Henning, can
> you please proceed with running your script against
> https://svn.apache.org/repos/asf/jakarta/jcs/trunk
>
> * Michael Stevens has offered to produce a Maven 2 POM (for users of
> Maven 2, not for building purposes). Michael, there is no time like
> the present...
>
> * There are seven open issues in Jira. I am of the opinion that
> JCS-13 should be skipped for now. Are there any strong opinions on
> the others?
>
> * What version number will we call the release? "1.2.7.9.3" may raise
> a few eyebrows.
>
> Let's get the above sorted, then we can build a site and release
> package on which to vote. Thomas's release experience will come in
> handy at this point.
>
> Let me know if I have missed anything.
>
> Scott
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Progress towards a release
Posted by Michael Stevens <ms...@etla.org>.
On Thu, May 10, 2007 at 07:10:13PM +0200, Thomas Vandahl wrote:
> http://maven.apache.org/maven-1.x/news.html
>
> I'd suggest to add the line
>
> maven.repo.remote=http://repo1.maven.org/maven
>
> to a build.properties in your home directory as this is not exactly a
> project issue but an issue of your environment. (No, Maven 1.1 won't
> help, it will fix this but break other things...)
Yep, it's that one :) I've easily fixed it locally, but I think JCS
has maven.repo.remote in its tree (and it does), it should be
something that actually lets you retrieve the dependencies that JCS
needs.
Why make everyone who build JCS set the same property when it could be
defined once?
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Progress towards a release
Posted by Thomas Vandahl <tv...@apache.org>.
Michael Stevens wrote:
> Did you fix the bug where it can't be build with an empty maven1
> repository as the repo url has changed?
I didn't fix any bugs. The whole process was about fulfilling legal
requirements and a few formatting issues. I suspect, however that you
are facing something like this:
http://maven.apache.org/maven-1.x/news.html
I'd suggest to add the line
maven.repo.remote=http://repo1.maven.org/maven
to a build.properties in your home directory as this is not exactly a
project issue but an issue of your environment. (No, Maven 1.1 won't
help, it will fix this but break other things...)
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Progress towards a release
Posted by Michael Stevens <ms...@etla.org>.
On Fri, May 11, 2007 at 08:17:53AM +1000, Scott Eade wrote:
> Thomas was just fixing the licenses in the source headers as per the
> previous discussions where we are working towards a JCS release. Thanks
> Thomas!
I only mentioned it to Thomas because he also said it was building
fine.
Fixing the licenses is good.
> I think the only reason the maven repository isn't being generally
> applied and committed is that there is an expectation that the central
> ibiblio repository will be repaired at some stage. I can't see too much
> harm in updating JCS, et al to use the interim location - just as long
> as we remove it once ibiblio's repository is back in action.
I didn't realise the ibiblio repository was planned to move back.
I'm just keen that it be as easy as possible to build things.
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Progress towards a release
Posted by Scott Eade <se...@backstagetech.com.au>.
Michael Stevens wrote:
> On Thu, May 10, 2007 at 06:23:31PM +0200, Thomas Vandahl wrote:
>
>> The whole thing builds with maven1 and all tests run fine. However when
>> building the site I still get some NPEs during the JCoverage run.
>>
>
> Did you fix the bug where it can't be build with an empty maven1
> repository as the repo url has changed
Thomas was just fixing the licenses in the source headers as per the
previous discussions where we are working towards a JCS release. Thanks
Thomas!
I think the only reason the maven repository isn't being generally
applied and committed is that there is an expectation that the central
ibiblio repository will be repaired at some stage. I can't see too much
harm in updating JCS, et al to use the interim location - just as long
as we remove it once ibiblio's repository is back in action.
Scott
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Progress towards a release
Posted by Michael Stevens <ms...@etla.org>.
On Thu, May 10, 2007 at 06:23:31PM +0200, Thomas Vandahl wrote:
> The whole thing builds with maven1 and all tests run fine. However when
> building the site I still get some NPEs during the JCoverage run.
Did you fix the bug where it can't be build with an empty maven1
repository as the repo url has changed?
Michael
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Progress towards a release
Posted by Thomas Vandahl <tv...@apache.org>.
Thomas Vandahl wrote:
> Scott Eade wrote:
>> Thomas: Can I be so bold as to ask you to apply your new found
>> CodeWrestler expertise to the JCS trunk? Doing this would bring us a
>> step closer to a release.
> I'll give it a try, but won't make it before weekend.
I managed to squeeze it in. The license has been added to 251 files and
replaced in 326 files. The headers have been reformatted and all
trailing blanks removed.
The whole thing builds with maven1 and all tests run fine. However when
building the site I still get some NPEs during the JCoverage run.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org
Re: Progress towards a release
Posted by Thomas Vandahl <tv...@apache.org>.
Scott Eade wrote:
> Thomas: Can I be so bold as to ask you to apply your new found
> CodeWrestler expertise to the JCS trunk? Doing this would bring us a
> step closer to a release.
I'll give it a try, but won't make it before weekend.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: jcs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jcs-dev-help@jakarta.apache.org