Hi,
any chance to do a maven release plugin release soon? 2.4 has the annoying
regression of not being able to deploy from a local repo (fixed in
MRELEASE-818) so either getting 2.4.1 or 2.5 would be really helpful.
Thanks,
Henning
And something like a CI server can make use of this capability as well.
On 3/15/2013 2:20 AM, Robert Scholte wrote:
At least the maven-help-plugin and probably the maven-site-plugin too.
There's a small difference between the resolved pom for Maven(core)
and the way paths are transformed for
FYI, I've deployed the latest snapshots to
https://oss.sonatype.org/content/repositories/snapshots
On 15 Mar 2013, at 00:40, Stuart McCulloch wrote:
> On 15 Mar 2013, at 00:24, Jason van Zyl wrote:
>
>> Agreed, I don't see any harm on this being on master.
>>
>> Do those two issues below corre
On 15 Mar 2013, at 00:24, Jason van Zyl wrote:
> Agreed, I don't see any harm on this being on master.
>
> Do those two issues below correspond to the two failed ITs here:
^ I think you meant to post a different link... if you're talking about the
core ITs then remember that the issue to bring
Agreed, I don't see any harm on this being on master.
Do those two issues below correspond to the two failed ITs here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=403286
If so, if you can publish a snapshot I'll update master and then we can let it
bake more.
On Mar 14, 2013, at 4:15 PM, Stu
On 14 Mar 2013, at 14:23, Jason van Zyl wrote:
> Why is it an issue?
>
> Unless you have a non painful way to setup jobs to test it against the IT
> matrix how else are we going to vet the changes?
From my perspective it's better in master so people can kick the tyres rather
than have it squir
This is an interesting discussion as well as a very relevant direction of
thoughts.
I feel that the maven distribution strategies (mainly within site/release
plugins) are full of
[fairly undocumented] assumptions - the net result of which is a confusing
experience
for the users.
It would seem that
At least the maven-help-plugin and probably the maven-site-plugin too.
There's a small difference between the resolved pom for Maven(core) and
the way paths are transformed for the maven-release-plugin and
maven-site-plugin.
here are some examples:
https://jira.codehaus.org/browse/MSITE-669
On Thursday, 14 March 2013, Robert Scholte wrote:
> Let's create a new shared component[1] for it: there are more plugins
> depending on this intelligence.
What other plugins could be concerned with knowing which projects are roots
for the release plugin?
Or maybe you gave something else in min
Let's create a new shared component[1] for it: there are more plugins
depending on this intelligence.
Looks to me there's no component for this kind of stuff yet.
Robert
[1] http://maven.apache.org/shared/index.html
Op Thu, 14 Mar 2013 10:32:26 +0100 schreef Stephen Connolly
:
No it mak
Why is it an issue?
Unless you have a non painful way to setup jobs to test it against the IT
matrix how else are we going to vet the changes?
On Mar 13, 2013, at 5:32 PM, Olivier Lamy wrote:
> master branch really ?
>
> 2013/3/13 :
>> Updated Branches:
>> refs/heads/master 41a292d9a -> 2c2
No it makes more sense in the release plugin
On 14 March 2013 09:16, Rahul Thakur wrote:
>
> And perhaps this capability can reside in Maven core? Just a thought
>
>
>
>
> On 3/12/2013 2:56 AM, Robert Scholte wrote:
>
>> Hi,
>>
>> There are several MSITE/DOXIA and MRELEASE issues related to
And perhaps this capability can reside in Maven core? Just a thought
On 3/12/2013 2:56 AM, Robert Scholte wrote:
Hi,
There are several MSITE/DOXIA and MRELEASE issues related to this
subject.
For the SCM-section and the site-section of the distributionManagement
we need a more intell
13 matches
Mail list logo
