[jboss-dev] mvn release failure

[John Bailey]

I started a script to do the version change in a platform independent way.  I am sure there is a much better way, but here is a sample that will at least find the files to update.  This could likely be piped into the substitution routine.  I haven't spent much time in Perl in the last several years, so I would guess there is a better way to do this.  

----
my $files = findFiles('.', '\.xml$|\.java$');

foreach $file (@$files) {
	print "$file\n";
}

sub findFiles {
	my @matches;
	_findFiles(shift, shift, \@matches); 
	return \@matches;
}

sub _findFiles {
	my $dir = shift;
	my $pattern = shift; 
	my $matches = shift;
	
	opendir ( DIR, $dir ) || die "Error in opening dir $dir\n";
	my @dirFiles=grep {!/^..?$/} readdir(DIR);
	closedir(DIR);
	
	foreach $file (@dirFiles){
		chomp($file);
		my $path = "$dir/$file";	
		if( -d $path) {
			_findFiles($path, $pattern, $matches); 
		} elsif($file =~ /$pattern/) {
			push(@$matches, $path);
		} 
	}
}
----

On Jan 7, 2010, at 2:41 PM, Paul Gier wrote:

> I don't know of anything that changed that would affect this.  It seems like 
> there are just a lot of little things that can go wrong in the communication 
> between the release plugin and svn.  Did you update your local svn client?  Or 
> maybe change the version of the release plugin that you are using?
> 
> The only non-windows compatible part of David's process is the perl script to 
> update the version.  For now you can either just do the version updates manually 
> (find and replace in eclipse?)
> 
> I'll work on a platform independent Perl script to do the updates.
> 
> Ales Justin wrote:
>> Easier said than done. ;-)
>> 
>> I never had good experiance of Cygwin, hence I doubt it will work.
>> 
>> And I'm changing OS as we speak,
>> but terrible UK weather prevents my new fancy hardware to be  
>> shipped. :-)
>> 
>> So, more suggestions welcome.
>> 
>> Btw, what changed that prevents my releases,
>> as I had no problems (or very little) before.
>> 
>> Sent from my iPod
>> 
>> On 7.1.2010, at 20:05, jason.greene at redhat.com wrote:
>> 
>>> Install Cygwin or switch to a better OS :)
>>> 
>>> Sent from my iPhone
>>> 
>>> On Jan 7, 2010, at 12:56, Dimitris Andreadis <dandread at redhat.com>
>>> wrote:
>>> 
>>>> I think Ales said something like how he can do this on Windoze :)
>>>> 
>>>> Paul Gier wrote:
>>>>> I agree, just use David's release process.  You can use a script or
>>>>> just
>>>>> manually update the POM versions.  It's not worth the effort to try
>>>>> to get the
>>>>> release plugin working, since base on past experience there is a
>>>>> good chance you
>>>>> will end up with another problem in the next release.
>>>>> 
>>>>> Jaikiran Pai wrote:
>>>>>> Yeah, i think David's release process is probably better. Because
>>>>>> with
>>>>>> the new release process explained in
>>>>>> http://community.jboss.org/wiki/MavenReleaseRepository, it looks
>>>>>> like
>>>>>> the release will be directly commited to SVN repo. The earlier
>>>>>> process
>>>>>> used to copy it to the local file system and then we used manually
>>>>>> commit it. That allowed us to decide whether or not to commit the
>>>>>> release, if something went wrong during the release. David's  
>>>>>> release
>>>>>> process provides me this flexibility.
>>>>>> 
>>>>>> -Jaikiran
>>>>>> 
>>>>>> Dimitris Andreadis wrote:
>>>>>>> Maybe you should consider also David's simplified release process:
>>>>>>> http://community.jboss.org/wiki/DavidsMavenReleaseProcess
>>>>>>> 
>>>>>>> Jaikiran Pai wrote:
>>>>>>>> Looks like the Maven release process for JBoss projects has now
>>>>>>>> changed http://community.jboss.org/wiki/MavenReleaseRepository  
>>>>>>>> and
>>>>>>>> now use Maven Wagon SCM
>>>>>>>> http://community.jboss.org/wiki/MavenReleaseRepository
>>>>>>>> 
>>>>>>>> -Jaikiran
>>>>>>>> Jaikiran Pai wrote:
>>>>>>>>> However, this doesn't explain why the tagging during release is
>>>>>>>>> failing. I do see another change in the "jboss-releases"
>>>>>>>>> distribution management repository config for jboss-parent-5-
>>>>>>>>> beta-5:
>>>>>>>>> 
>>>>>>>>> <distributionManagement>
>>>>>>>>> <repository>
>>>>>>>>> <id>jboss-releases</id>
>>>>>>>>> <name>JBoss Release Repository</name>
>>>>>>>>> <url>${jboss.releases.repo.url}</url>
>>>>>>>>> </repository>
>>>>>>>>> 
>>>>>>>>> and the ${jboss.releases.repo.url} points to:
>>>>>>>>> 
>>>>>>>>> <jboss.releases.repo.url>scm:svn:https://svn.jboss.org/repos/
>>>>>>>>> repository.jboss.org/maven2</jboss.releases.repo.url>
>>>>>>>>> 
>>>>>>>>> 
>>>>>>>>> In the earlier versions, this used to point to the local
>>>>>>>>> checkout of
>>>>>>>>> the maven repo:
>>>>>>>>> 
>>>>>>>>> <distributionManagement>
>>>>>>>>> <repository>
>>>>>>>>> <!-- Copy the distribution jar file to a local checkout of the
>>>>>>>>> maven
>>>>>>>>> repository
>>>>>>>>> - This variable can be set in $MAVEN_HOME/conf/settings.xml -->
>>>>>>>>> <id>repository.jboss.org</id>
>>>>>>>>> <url>file://${maven.repository.root}</url>
>>>>>>>>> </repository>
>>>>>>>>> 
>>>>>>>>> Not sure if this is causing the release issues. Maybe Paul  
>>>>>>>>> knows?
>>>>>>>>> 
>>>>>>>> _______________________________________________
>>>>>>>> jboss-development mailing list
>>>>>>>> jboss-development at lists.jboss.org
>>>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>>> _______________________________________________
>>>>>> jboss-development mailing list
>>>>>> jboss-development at lists.jboss.org
>>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>>> _______________________________________________
>>>>> jboss-development mailing list
>>>>> jboss-development at lists.jboss.org
>>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>>> _______________________________________________
>>>> jboss-development mailing list
>>>> jboss-development at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>>> _______________________________________________
>>> jboss-development mailing list
>>> jboss-development at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jboss-development
>> _______________________________________________
>> jboss-development mailing list
>> jboss-development at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-development
> 
> _______________________________________________
> jboss-development mailing list
> jboss-development at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-development

--
  John Bailey
  JBoss by Red Hat
--