Hi Chris,

You scared me a bit, as if something went wrong during the release.
I've never released 2.4 [1], but I did deploy a 2.4-SNAPSHOT.
Since this is a bugfix-release, I've changed the version to 2.3.2 during release. I'll keep developing for 2.4-SNAPSHOT, because that's still my target for the next release.

-Robert

[1] http://svn.apache.org/viewvc/maven/release/tags/


Op Wed, 13 Jun 2012 01:56:13 +0200 schreef Chris Graham <chrisgw...@gmail.com>:

Hi Robert.

  Thanks for that.

  Now, you've called for a vote on 2.3.2, but when I checked out the
release dir, it was 2.4! That was before the voet was called for, and I
mentioned it above, but you might have missed it.

  Has the version been incorrctly bumped up?

  In short, what are we voting on? 2.3.2 or 2.4 of the MRP?

-Chris

On Tue, Jun 12, 2012 at 3:30 AM, Robert Scholte <rfscho...@apache.org>wrote:

Up until SCM-1.7 the ScmFile had no specification about its arguments.
It just depended on the provider.
But for good usability the ScmFile should be transparent for the *users*,
not the provider.
Fixing this with the ScmFile can be dangerous and would take a lot of time.
So the fastest way to fix this is by solving this in the ScmTranslators.

The toRelativePath makes it much easer to use org.codehaus.plexus.util.**SelectorUtils(),
which requires:
* path should NOT start with a file-separator
* use the OS-specific File.separator to as the file-separator
IMO this is the best way to describe an OS-independent relative path.
By moving this logic to the ScmTranslator I know how to handle ScmFiles
and their paths.

-Robert

Op Mon, 11 Jun 2012 05:58:53 +0200 schreef Chris Graham <
chrisgw...@gmail.com>:


 Oops. Bad bad me.

[INFO]
------------------------------**------------------------------**
------------
[INFO] Building GPDB - J2EE Multi Module Project
[INFO]    task-segment: [release:prepare, release:perform]
(aggregator-style)
[INFO]
------------------------------**------------------------------**
------------
[INFO] [release:prepare {execution: default-cli}]
[INFO] Verifying that there are no local modifications...
[INFO]   ignoring changes on: **\pom.xml.branch, **\pom.xml.backup,
**\pom.xml.releaseBackup, **\release.properties, **\pom.xml.next,
**\pom.xml.tag
[INFO] Executing: cmd.exe /X /C "scm status --username Deb --password
*****
--wide"
[INFO] Working directory: C:\CALMData\Workspaces\RTC\**Deb\GPDB
[2.4] JazzScmTranslator.**toRelativePath():
[2.4] JazzScmTranslator.**toRelativePath() path =
/GPDB/release.properties
[2.4] JazzScmTranslator.**toRelativePath() rc = GPDB\release.properties
[INFO] Ignoring SNAPSHOT depenedencies and plugins ...
[INFO] Transforming 'GPDB - J2EE Multi Module Project'...

It *is* being called, and is returning what you want.

I do have one question though.
The underling CLI tool (scm.exe) returns unix path formats on all envs,
including windows (I just checked with the authors of it).

So why are we converting the returned path to a windows format?

(or is that the way that the rest of the system expects it to behave?)

-Chris


On Mon, Jun 11, 2012 at 1:35 PM, Chris Graham <chrisgw...@gmail.com>
wrote:

 Hi Robert,

We're up to 2.4-SNAPSHOT now?

Nope. Still not being called.

Let me look into it for ya. :-)

-Chris


On Sun, Jun 10, 2012 at 10:26 PM, Chris Graham <chrisgw...@gmail.com
>wrote:

 Ok. I'll check it tomorrow.

I'm in Sydney in a hotel room with a WiFi that doesn't.

-Chris

Sent from my iPhone

On 10/06/2012, at 7:34 PM, "Robert Scholte" <apa...@sourcegrounds.com>
wrote:

> Hi Chris,
>
> By coincident Sonar pointed me to this issue.
> I've created MRELEASE-770 and fixed it.
> A SNAPSHOT has been deployed, ready for testing.
>
> -Robert
>
> Op Sun, 10 Jun 2012 06:29:15 +0200 schreef Chris Graham <
chrisgw...@gmail.com>:
>
>> Hi Robert.
>>
>> I was just running it from two different locations (workspaces),
otherwise
>> no real differences. Both are valid workspaces.
>>
>> -Chris
>>
>> On Sat, Jun 9, 2012 at 11:20 PM, Robert Scholte <
apa...@sourcegrounds.com>**wrote:
>>
>>> Hi Chris,
>>>
>>> yes, I would expect it between "Verifying that there are no local
>>> modifications..." and "Checking dependencies and plugins for
snapshots
>>> ...", unless there's no reason to call it.
>>> This latest log doesn't match your first log, which failed right
after the
>>> "Working directory..." - info line.
>>>
>>> I don't know if it matters, but I see a difference between the
working
>>> directories:
>>>
>>> [INFO] Working directory: C:\tmp\release-workspace\GPDB
>>> versus
>>>
>>> [INFO] Working directory: C:\CALMData\Workspaces\RTC\****Deb\GPDB
>>>
>>> -Robert
>>>
>>> Op Sat, 09 Jun 2012 14:54:10 +0200 schreef Chris Graham <
>>> chrisgw...@gmail.com>:
>>>
>>> Hi Robert.
>>>>
>>>> Found a few minutes...
>>>>
>>>> As far as I can see, the method toRelativePath is not being called.
>>>>
>>>> When are you expecting it to be called? I would have thought at the
check
>>>> for local modifications.
>>>>
>>>> But, this is what I'm seeing:
>>>>
>>>> [INFO]
>>>> ------------------------------****----------------------------**
--**
>>>> ------------
>>>> [INFO] Building GPDB - J2EE Multi Module Project
>>>> [INFO]    task-segment: [release:prepare, release:perform]
>>>> (aggregator-style)
>>>> [INFO]
>>>> ------------------------------****----------------------------**
--**
>>>> ------------
>>>> [INFO] [release:prepare {execution: default-cli}]
>>>> [INFO] Verifying that there are no local modifications...
>>>> [INFO] ignoring changes on: **\pom.xml.branch, **\pom.xml.backup, >>>> **\pom.xml.releaseBackup, **\release.properties, **\pom.xml.next,
>>>> **\pom.xml.tag
>>>> [INFO] Executing: cmd.exe /X /C "scm status --username Deb
--password
>>>> *****
>>>> --wide"
>>>> [INFO] Working directory: C:\CALMData\Workspaces\RTC\****Deb\GPDB
>>>> [INFO] Checking dependencies and plugins for snapshots ...
>>>> [INFO] Transforming 'GPDB - J2EE Multi Module Project'...
>>>> JazzScmTranslator.****translateTagUrl():
>>>> JazzScmTranslator.****translateTagUrl():
>>>> JazzScmTranslator.****translateTagUrl():
>>>> JazzScmTranslator.resolveTag()****:
>>>> [INFO] Transforming 'GPDB - Resources Project'...
>>>> [INFO] Transforming 'GPDB - WAR Project'...
>>>> [INFO]   Updating GPDBResources to 1.0.42
>>>> [INFO] Transforming 'GPDB - EAR Project'...
>>>> [INFO]   Updating GPDBWeb to 1.0.42
>>>> [INFO] Not generating release POMs
>>>> [INFO] Executing goals 'clean verify'...
>>>>
>>>> -Chris
>>>>
>>>> On Sat, Jun 9, 2012 at 6:21 AM, Robert Scholte <
apa...@sourcegrounds.com>
>>>> **wrote:
>>>>
>>>> Hi Chris,
>>>>>
>>>>> I'd like to do a 2.3.2 release somewhere next week.
>>>>> Could you investigate this issue?
>>>>>
>>>>> -Robert
>>>>>
>>>>> Op Sat, 02 Jun 2012 12:24:01 +0200 schreef Chris Graham <
>>>>> chrisgw...@gmail.com>:
>>>>>
>>>>>
>>>>> Now that I have my VM (where I've done all of my jazz development)
back
>>>>>
>>>>>> able to talk to the Internet, I'll give it a go.
>>>>>>
>>>>>> -Chris
>>>>>>
>>>>>> Sent from my iPhone
>>>>>>
>>>>>> On 02/06/2012, at 6:17 PM, "Robert Scholte" <
apa...@sourcegrounds.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hi Chris,
>>>>>>
>>>>>>>
>>>>>>> can you confirm that the org.apache.maven.shared.**
>>>>>>> release.scm.JazzScmTranslator.******toRelativePath(String) is
executed?
>>>>>>>
>>>>>>> I've written unittests for this method, which reflect your
usecase.
>>>>>>> Have
>>>>>>> a look at them too.
>>>>>>>
>>>>>>> -Robert
>>>>>>>
>>>>>>> Op Sat, 02 Jun 2012 05:46:14 +0200 schreef Chris Graham <
>>>>>>> chrisgw...@gmail.com>:
>>>>>>>
>>>>>>> Hi All.
>>>>>>>
>>>>>>>>
>>>>>>>> Sorry for that the fact that it's taken me so long to get
around
to
>>>>>>>> testing
>>>>>>>> the 2.3.1 release plugin, but my laptop had some 'firewall
issues'
>>>>>>>> that
>>>>>>>> needed to be resolved by IBM.
>>>>>>>>
>>>>>>>> So, I checked out a new jazz workspace, and attempted my first
release
>>>>>>>> in
>>>>>>>> it, and this is what I got:
>>>>>>>>
>>>>>>>> C:\tmp\release-workspace\GPDB>******mvn -B -Dresume=false
>>>>>>>> -DworkingDirectory=C:\tmp\******maven release:prepare
release:perform
>>>>>>>> [INFO] Scanning for projects...
>>>>>>>> [INFO] snapshot au.com.warpspeed:warpspeed-******
>>>>>>>> dynamic-parent:1-SNAPSHOT:
>>>>>>>>
>>>>>>>> checking for updates from warpspeed.repos
>>>>>>>> [WARNING] repository metadata for: 'snapshot
>>>>>>>> au.com.warpspeed:warpspeed-******dynamic-parent:1-SNAPSHOT'
could
not
>>>>>>>> be
>>>>>>>>
>>>>>>>> retrieved from repository: warpspeed.repos due to an
>>>>>>>> error: Authorization failed: Access denied to:
>>>>>>>> http://archiva.warpspeed.com.******au/archiva/repository/**
>>>>>>>> warpspeed.repos/au/com/******warpspeed/warpspeed-dynamic-****
**
>>>>>>>> parent/1-SNAPSHO<http://**arch**iva.warpspeed.com.au/**<http://archiva.warpspeed.com.au/**>
>>>>>>>> archiva/repository/warpspeed.****repos/au/com/warpspeed/**
>>>>>>>> warpspeed-dynamic-parent/1-****SNAPSHO<
http://archiva.warpspeed.com.**au/archiva/repository/**
warpspeed.repos/au/com/**warpspeed/warpspeed-dynamic-**parent/1-SNAPSHO<http://archiva.warpspeed.com.au/archiva/repository/warpspeed.repos/au/com/warpspeed/warpspeed-dynamic-parent/1-SNAPSHO>
>
>>>>>>>> >
>>>>>>>>
>>>>>>>> T/maven-metadata.xml
>>>>>>>> [INFO] Repository 'warpspeed.repos' will be blacklisted
>>>>>>>> [INFO] Reactor build order:
>>>>>>>> [INFO]   GPDB - J2EE Multi Module Project
>>>>>>>> [INFO]   GPDB - Resources Project
>>>>>>>> [INFO]   GPDB - WAR Project
>>>>>>>> [INFO]   GPDB - EAR Project
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>>
>>>>>>>> ------------
>>>>>>>> [INFO] Building GPDB - J2EE Multi Module Project
>>>>>>>> [INFO]    task-segment: [release:prepare, release:perform]
>>>>>>>> (aggregator-style)
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>>
>>>>>>>> ------------
>>>>>>>> [INFO] [release:prepare {execution: default-cli}]
>>>>>>>> [INFO] Verifying that there are no local modifications...
>>>>>>>> [INFO]   ignoring changes on: **\pom.xml.branch,
**\pom.xml.backup,
>>>>>>>> **\pom.xml.releaseBackup, **\release.properties,
**\pom.xml.next,
>>>>>>>> **\pom.xml.tag
>>>>>>>> [INFO] Executing: cmd.exe /X /C "scm status --username Deb
--password
>>>>>>>> *****
>>>>>>>> --wide"
>>>>>>>> [INFO] Working directory: C:\tmp\release-workspace\GPDB
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>> ------------
>>>>>>>> [ERROR] BUILD FAILURE
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>>
>>>>>>>> ------------
>>>>>>>> [INFO] Cannot prepare the release because you have local
>>>>>>>> modifications :
>>>>>>>> [/GPDB/release.properties:******added]
>>>>>>>>
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>>
>>>>>>>> ------------
>>>>>>>> [INFO] For more information, run Maven with the -e switch
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>>
>>>>>>>> ------------
>>>>>>>> [INFO] Total time: 1 minute 11 seconds
>>>>>>>> [INFO] Finished at: Sat Jun 02 13:24:59 EST 2012
>>>>>>>> [INFO] Final Memory: 24M/71M
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>>
>>>>>>>> ------------
>>>>>>>> C:\tmp\release-workspace\GPDB>
>>>>>>>>
>>>>>>>>
>>>>>>>> So, it appears that it is still not ignoring some of the
temporary
>>>>>>>> files in
>>>>>>>> the release process. What that what some of the new methods
were
meant
>>>>>>>> to
>>>>>>>> address? Or have I missed something?
>>>>>>>>
>>>>>>>> Here is the output of the "scm status" command that is used to
>>>>>>>> determine
>>>>>>>> the status of files.
>>>>>>>>
>>>>>>>> C:\tmp\release-workspace\GPDB>******scm status
>>>>>>>>
>>>>>>>> Workspace: (1156) "GPDBWorkspace" <-> (1157) "GPDBStream"
>>>>>>>> Component: (1158) "GPDB" <-> (1157) "GPDBStream"
>>>>>>>> Baseline: (2222) 36 "GPDB-1.0.36"
>>>>>>>> Unresolved:
>>>>>>>>   a-- /GPDB/release.properties
>>>>>>>>
>>>>>>>> C:\tmp\release-workspace\GPDB>
>>>>>>>>
>>>>>>>> This is what is being processed, and you can see the output of
the mvn
>>>>>>>> scm:status command:
>>>>>>>>
>>>>>>>> C:\tmp\release-workspace\GPDB>******mvn scm:status
>>>>>>>> [INFO] Scanning for projects...
>>>>>>>> [INFO] snapshot au.com.warpspeed:warpspeed-******
>>>>>>>> dynamic-parent:1-SNAPSHOT:
>>>>>>>>
>>>>>>>> checking for updates from warpspeed.repos
>>>>>>>> [WARNING] repository metadata for: 'snapshot
>>>>>>>> au.com.warpspeed:warpspeed-******dynamic-parent:1-SNAPSHOT'
could
not
>>>>>>>> be
>>>>>>>>
>>>>>>>> retrieved from repository: warpspeed.repos due to an
>>>>>>>> error: Authorization failed: Access denied to:
>>>>>>>> http://archiva.warpspeed.com.******au/archiva/repository/**
>>>>>>>> warpspeed.repos/au/com/******warpspeed/warpspeed-dynamic-****
**
>>>>>>>> parent/1-SNAPSHO<http://**arch**iva.warpspeed.com.au/**<http://archiva.warpspeed.com.au/**>
>>>>>>>> archiva/repository/warpspeed.****repos/au/com/warpspeed/**
>>>>>>>> warpspeed-dynamic-parent/1-****SNAPSHO<
http://archiva.warpspeed.com.**au/archiva/repository/**
warpspeed.repos/au/com/**warpspeed/warpspeed-dynamic-**parent/1-SNAPSHO<http://archiva.warpspeed.com.au/archiva/repository/warpspeed.repos/au/com/warpspeed/warpspeed-dynamic-parent/1-SNAPSHO>
>
>>>>>>>> >
>>>>>>>>
>>>>>>>> T/maven-metadata.xml
>>>>>>>> [INFO] Repository 'warpspeed.repos' will be blacklisted
>>>>>>>> [INFO] Reactor build order:
>>>>>>>> [INFO]   GPDB - J2EE Multi Module Project
>>>>>>>> [INFO]   GPDB - Resources Project
>>>>>>>> [INFO]   GPDB - WAR Project
>>>>>>>> [INFO]   GPDB - EAR Project
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>>
>>>>>>>> ------------
>>>>>>>> [INFO] Building GPDB - J2EE Multi Module Project
>>>>>>>> [INFO]    task-segment: [scm:status] (aggregator-style)
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>>
>>>>>>>> ------------
>>>>>>>> [INFO] [scm:status {execution: default-cli}]
>>>>>>>> [INFO] Executing: cmd.exe /X /C "scm status --username Deb
--password
>>>>>>>> *****
>>>>>>>> --wide"
>>>>>>>> [INFO] Working directory: C:\tmp\release-workspace\GPDB
>>>>>>>> [INFO] added status for /GPDB/release.properties
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>> ------------
>>>>>>>> [INFO] BUILD SUCCESSFUL
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>>
>>>>>>>> ------------
>>>>>>>> [INFO] Total time: 28 seconds
>>>>>>>> [INFO] Finished at: Sat Jun 02 13:34:00 EST 2012
>>>>>>>> [INFO] Final Memory: 17M/48M
>>>>>>>> [INFO]
>>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>>>
>>>>>>>> ------------
>>>>>>>> C:\tmp\release-workspace\GPDB>
>>>>>>>>
>>>>>>>> The only workaround so far that I've been able to do is to add
>>>>>>>> 'release.properties' to the .jazzignore file, so that jazz
itself
>>>>>>>> ignores
>>>>>>>> the file (much like the svn.ignore property). The file
'.jazzignore'
>>>>>>>> now
>>>>>>>> looks something like this:
>>>>>>>>
>>>>>>>> ### Jazz Ignore 0
>>>>>>>> # Default value for core.ignore.recursive is *.class
>>>>>>>> #  Changing this value changes check-in behaviour for the
entire
>>>>>>>> project.
>>>>>>>> #
>>>>>>>> # Default value for core.ignore is bin
>>>>>>>> # Changing this value changes check-in behaviour for the local
>>>>>>>> directory.
>>>>>>>> #
>>>>>>>> # Ignore properties should contain a space separated list of
filename
>>>>>>>> patterns.
>>>>>>>> # Each pattern is case sensitive and surrounded by braces ('{'
and
>>>>>>>> '}').
>>>>>>>> # "*" matches zero or more characters, and "?" matches single
>>>>>>>> characters.
>>>>>>>> #
>>>>>>>> # e.g: {*.sh} {\.*} ignores shell scripts and hidden files
>>>>>>>>
>>>>>>>> # NOTE: modifying ignore files will not change the ignore
status
of
>>>>>>>> derived
>>>>>>>> # resources.
>>>>>>>>
>>>>>>>> core.ignore.recursive= \
>>>>>>>> {*.class} \
>>>>>>>> {*.log}
>>>>>>>>
>>>>>>>> core.ignore= \
>>>>>>>> {release.properties} \
>>>>>>>> {target}
>>>>>>>>
>>>>>>>> -Chris
>>>>>>>>
>>>>>>>>
>>>>>>>
------------------------------******--------------------------**
--**--**
>>>>>>> ---------
>>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.******org<
>>>>>>> dev-unsubscribe@maven.**apache**.org <http://apache.org> <
dev-unsubscribe@maven.apache.**org <dev-unsubscr...@maven.apache.org>>>
>>>>>>>
>>>>>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------******--------------------------*
*--**
>>>>>> --**---------
>>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.******org<
>>>>>> dev-unsubscribe@maven.**apache**.org <http://apache.org> <
dev-unsubscribe@maven.apache.**org <dev-unsubscr...@maven.apache.org>>>
>>>>>>
>>>>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>>>>
>>>>>>
>>>>> ------------------------------******--------------------------**
--**
>>>>> --**---------
>>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.******org<
>>>>> dev-unsubscribe@maven.**apache**.org <http://apache.org> <
dev-unsubscribe@maven.apache.**org <dev-unsubscr...@maven.apache.org>>>
>>>>>
>>>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>>>
>>>>>
>>>
------------------------------****----------------------------**
--**---------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.****org<
dev-unsubscribe@maven.apache.**org <dev-unsubscr...@maven.apache.org>>
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>
> ------------------------------**------------------------------**
---------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org>
> For additional commands, e-mail: dev-h...@maven.apache.org
>



------------------------------**------------------------------**---------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.**org<dev-unsubscr...@maven.apache.org>
For additional commands, e-mail: dev-h...@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Reply via email to