On Fri, May 18, 2018 at 8:00 PM, Hervé BOUTEMY
wrote:
> Le vendredi 18 mai 2018, 22:36:20 CEST Rob Tompkins a écrit :
> > > On May 18, 2018, at 3:30 PM, Michael Osipov
> wrote:
> > >
> > > Am 2018-05-17 um 15:12 schrieb Rob Tompkins:
> > > > Hello maven guys,
> > > >
> > > > Over on commons we’v
Le vendredi 18 mai 2018, 22:36:20 CEST Rob Tompkins a écrit :
> > On May 18, 2018, at 3:30 PM, Michael Osipov wrote:
> >
> > Am 2018-05-17 um 15:12 schrieb Rob Tompkins:
> > > Hello maven guys,
> > >
> > > Over on commons we’ve been writing our own release-plugin
> >
> > What is wrong with the
For the maven-release-plugin (3.0.0) I've started to extract the API to
make it possible to define your own release strategy.
I'm quite interested in the steps you take and if this fits in the
improved design of the plugin.
If we take a look at the Maven Release process, there are still quite s
On Fri, May 18, 2018 at 2:36 PM, Rob Tompkins wrote:
>
>
> > On May 18, 2018, at 3:30 PM, Michael Osipov wrote:
> >
> > Am 2018-05-17 um 15:12 schrieb Rob Tompkins:
> > > Hello maven guys,
> > >
> > > Over on commons we’ve been writing our own release-plugin
> >
> > What is wrong with the curren
> On May 18, 2018, at 3:30 PM, Michael Osipov wrote:
>
> Am 2018-05-17 um 15:12 schrieb Rob Tompkins:
> > Hello maven guys,
> >
> > Over on commons we’ve been writing our own release-plugin
>
> What is wrong with the current Maven Release Plugin and why are you writing
> your own whereas we c
On Fri, May 18, 2018 at 1:30 PM, Michael Osipov wrote:
> Am 2018-05-17 um 15:12 schrieb Rob Tompkins:
> > Hello maven guys,
> >
> > Over on commons we’ve been writing our own release-plugin
>
> What is wrong with the current Maven Release Plugin and why are you
> writing your own whereas we could
Am 2018-05-17 um 15:12 schrieb Rob Tompkins:
> Hello maven guys,
>
> Over on commons we’ve been writing our own release-plugin
What is wrong with the current Maven Release Plugin and why are you
writing your own whereas we could improve the current one, can't we?
Michael
Hello maven guys,
Over on commons we’ve been writing our own release-plugin, and have the idea to
do the release promotion using a mojo. The goal here would be do do something
analogous to svn mv . Is that available in the [maven-scm-api]?
At first read it doesn’t look like it. Would you
Github user llebegue closed the pull request at:
https://github.com/apache/maven-release/pull/7
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Hi,
Jgit provider exposes password if it contains special characters :
SCM-817<https://issues.apache.org/jira/browse/SCM-817>
(https://issues.apache.org/jira/browse/SCM-817) was fixed in maven-scm-api
1.9.5 which was released in July 1st, 2016. maven-scm-api 1.9.6 has even been
released
GitHub user llebegue opened a pull request:
https://github.com/apache/maven-release/pull/7
Upgraded to maven-scm-api 1.9.5
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/llebegue/maven-release trunk
Alternatively you can
Hi,
I'm working on a merant Dimensions SCM SCM plugin. I kinda had it working
with the Dimensions CLI client.
Recently I tried upgrading the maven-scm-api dependency used by my plugin to
version 1.0. After some work this all compiles and installs fine.
But when I try running
I don't think this applies to Perforce but thanks for keeping me in the loop.
mike
On 3/21/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
Mike,
I don't know if Perforce checkout files in the current directory or in a subdirectory for
a "view", but if it's in a subdirectory like clearcase, it
http://svn.apache.org/viewvc?view=rev&rev=517605
Log:
Remove java5 code
Modified:
maven/scm/trunk/maven-scm-api/src/main/java/org/apache/maven/scm/command/update/AbstractUpdateCommand.java
Modified:
maven/scm/trunk/maven-scm-api/src/main/java/org/apache/maven/scm/comma
scm/trunk/maven-scm-api/src/main/java/org/apache/maven/
scm/command/update/AbstractUpdateCommand.java
Modified: maven/scm/trunk/maven-scm-api/src/main/java/org/apache/
maven/scm/command/update/AbstractUpdateCommand.java
URL: http://svn.apache.org/viewvc/maven/scm/trunk/maven-scm-api/src/
main
t; wrote:
>> Author: carlos
>> Date: Fri Dec 1 11:43:21 2006
>> New Revision: 481350
>>
>> URL: http://svn.apache.org/viewvc?view=rev&rev=481350
>> Log:
>> [maven-release-plugin] prepare release maven-scm-1.0-481343
>>
>> Modified:
>>
e.org/viewvc?view=rev&rev=481350
>> Log:
>> [maven-release-plugin] prepare release maven-scm-1.0-481343
>>
>> Modified:
>> maven/scm/trunk/maven-scm-api/pom.xml
>> maven/scm/trunk/maven-scm-client/pom.xml
>> maven/scm/trunk/maven-scm-managers
ROTECTED]> wrote:
Author: carlos
Date: Fri Dec 1 11:43:21 2006
New Revision: 481350
URL: http://svn.apache.org/viewvc?view=rev&rev=481350
Log:
[maven-release-plugin] prepare release maven-scm-1.0-481343
Modified:
maven/scm/trunk/maven-scm-api/pom.xml
maven/scm/trunk/maven-scm
&rev=481350
Log:
[maven-release-plugin] prepare release maven-scm-1.0-481343
Modified:
maven/scm/trunk/maven-scm-api/pom.xml
maven/scm/trunk/maven-scm-client/pom.xml
maven/scm/trunk/maven-scm-managers/maven-scm-manager-plexus/pom.xml
maven/scm/trunk/maven-scm-managers/pom.xm
In starteam, when I want work against all of files under a directory
(ie ScmFileSet without excludes and includes), I dont have to pass in
anything to command line
In order to detect this condition, I need a ability in ScmFileSet api to give me
an indication if the user uses either excludes or in
Folks,
Most of maven-scm-api commands like checkin, add, tag, changelog has a
ScmFileSet argument which ultimately expands into a list of individual
files on a command line. The finally command line becomes very long,
huge, so huge
for a larget project (like my legacy project).
I know for sure
API is mostly being used for read
> only operations (other than tagging and the occasional commit).
>
> If you'd like to subscribe here ([EMAIL PROTECTED]), it
> is very low traffic and we can work through it.
>
> Thanks again for contacting us.
>
> Cheers,
> Brett
like to subscribe here ([EMAIL PROTECTED]), it
is very low traffic and we can work through it.
Thanks again for contacting us.
Cheers,
Brett
Mike Esler wrote:
>Hi Brett. I've started working on an MKS provider for the maven scm api
>that I plan to contribute back.
>
>I have one
23 matches
Mail list logo
