[jboss-cvs] Repository SVN: r28275 - maven2/org/jboss/webbeans/webbeans-version-matrix.

[David M. Lloyd]

On 07/29/2009 12:02 PM, Paul Gier wrote:
> Pete Muir wrote:
>>
>> On 29 Jul 2009, at 17:30, David M. Lloyd wrote:
>>
>>> On 07/29/2009 11:25 AM, Pete Muir wrote:
>>>> This was due to Roger using webdav to commit to the repo (see 
>>>> http://www.jboss.org/community/wiki/MavenReleaseRepository/version/18)
>>>>>> I've also noticed that it diffs JARs inline.  This
>>>>>> might be an indication that it is using the wrong mime-type,
>>>>>> which might mean that it's using the wrong EOL style, which
>>>>>> might mean that the JARs will get hosed if they were, say,
>>>>>> created on windows and checked out on linux.
>>>> Thats not good :-) Any ideas how we fix?
>>>
>>> No idea.  I don't use webdav, I bundle all my repo changes into 
>>> single commits. :-)
>>
>> We used to do that, but recently updated to this new style when Paul 
>> changed the wiki page recommendations.
> 
> I changed the wiki recommendations because of complaints about having to 
> check out the repository before committing.  I wasn't aware of the 
> issues that David brough up.  David, how can we check if these problems 
> (mime-type, etc) are happening?

$ svn propget svn:mime-type 
https://svn.jboss.org/repos/repository.jboss.org/maven2/org/jboss/webbeans/webbeans-core/1.0.0.PREVIEW2.SP2/webbeans-core-1.0.0.PREVIEW2.SP2.jar
(no result - uh oh!  The default is treated as text/plain!  Who knows what 
it's going to use for eol-style...)

Fix with:
$ svn propset svn:mime-type application/octet-stream <URL>

Not sure how you can fix it via DAV while it uploads though.  Personally I 
don't think that checking out the repos is a huge deal; it lets me do a lot 
of "did I screw up yet?" checks along the way; my process is something like 
this:

Start
     For each project that is part of this release:
         Change POM to release version
         MVN Install
         MVN Deploy (into my checked out repos)
     Test each dependent project, make sure everything builds right & tests
     If problems, fix and go to Start (repos is not committed yet, so I can 
still change stuff!)
     If everything is OK, commit all my changes in one go (since I used SVN 
to add the files, JARs won't be diffed in the commit msg so it will be small)
     Wait for it to show up on repos.j.o
     Commit dependent projects to depend on the new stuff
End

It's a bit more work then, say, using the release plugin, but I screw up a 
lot less, so it's a tradeoff I guess.

- DML