Even after removing the repos from that profile, I still got codehaus
downloads on my last attempt. I'm trying again from an empty local
repository and rechecking that the tag got deleted from
release:rollback.
-
To unsubscribe, e
To my knowledge the only thing that's missing from Robert's list is
some code that was added to maven-artifact-transfer quite a bit after
I did the 3.x porting work to assembly. So it's really quite
unimportant as far as I'm concerned.
I might of course be mistaken, 3.0.0 of assembly should be the
I can find few others references to codehaus repositories to remove in
./maven-archetype/maven-archetype-plugin/src/test/projects/simple-inheritence/pom.xml:
http://snapshots.repository.codehaus.org
./trunks/plugins/maven-eclipse-plugin/src/test/resources/projects/MECLIPSE-295/pom.xml:
Hi,
Because of the run-its profile which adds
codehaus.org
http://snapshots.repository.codehaus.org
false
codehaus.snapshots
http://snapshots.repository.codehaus
In the 2.6 branch I've removed the extra repositories from the run-its
profile of this plugin.
On Tue, Oct 6, 2015 at 7:37 AM, Benson Margulies wrote:
> [INFO] [INFO] Building Apache Maven Assembly Plugin 2.6
> [INFO] [INFO]
>
[INFO] [INFO] Building Apache Maven Assembly Plugin 2.6
[INFO] [INFO]
[INFO] Downloading:
http://snapshots.repository.codehaus.org/org/apache/maven/plugins/maven-source-plugin/2.3/maven-source-plugin-2.3.pom
[INFO] 384 B
[INF
I don't know what's on trunk so really can't say. But I see no issue in
truynk being work towards 3.0 and your branch is a small addition ot the
2.x stream which will be in 2.6.0. If it's a bug fix it should be 2.5.x.
>From my pow it's totally fine going Java 6 in v2.6. You don't have to go
v3.0 fo
So, I have this 2.6 branch, but it's tightly my Snappy obsession. So
is that what you all mean, or do you want a large subset of the trunk
in there, possibly up to and including the current end of the trunk?
On Mon, Oct 5, 2015 at 3:03 PM, Anders Hammar wrote:
> I agree with Robert; it would be g
I agree with Robert; it would be great to do lots of cleanup (remove
deprecated goals for starters) in a 3.0 version. So doing a v2.6 now would
keep that option open.
/Anders
On Mon, Oct 5, 2015 at 8:23 PM, Robert Scholte wrote:
> IIRC for maven-assembly-plugin most of the actions have been don
IIRC for maven-assembly-plugin most of the actions have been done as
stated in the migration strategy[1]
Due to not knowing about maven-artifact-transfer the plugin contains some
equivalent code, but the custom code doesn't work for all M3.0+ versions
(I think only 3.0.4 and above).
AFAIK i
On Mon, Oct 5, 2015 at 4:27 AM, Kristian Rosenvold
wrote:
> Personally I'd release 3.0.0 and stuff whatever nit-picky requirements
> are not met. Revert any changes that depends on code that is not yet
> ready for release. I think ultimately the large list of requirements
> is a nice way to just h
Personally I'd release 3.0.0 and stuff whatever nit-picky requirements
are not met. Revert any changes that depends on code that is not yet
ready for release. I think ultimately the large list of requirements
is a nice way to just halt all progress.
It'll be at least a jdk 1.6 release no matter wh
I have my itch scratched on the 2.6 branch. If anyone else wants to
pull something else onto the branch before I release 2.6.0, please
speak up.
On Sun, Oct 4, 2015 at 6:03 PM, Benson Margulies wrote:
> OK, will do.
>
>
> On Sun, Oct 4, 2015 at 5:54 PM, Karl Heinz Marbaise wrote:
>> Hi Benson,
>
OK, will do.
On Sun, Oct 4, 2015 at 5:54 PM, Karl Heinz Marbaise wrote:
> Hi Benson,
>
> just update the branch. I have checked in a fix for that...
>
> You need simply to define Java 6 as target/source otherwise the parent will
> control that which is there by default 1.5...
>
> I would suggest
Hi Benson,
just update the branch. I have checked in a fix for that...
You need simply to define Java 6 as target/source otherwise the parent
will control that which is there by default 1.5...
I would suggest to make 2.6.0 which identifies as JDK
6...requirement3.0.0 should be reserved f
What can I do to help move the 3.0 effort along?
Or, alternatively, what would it take to get a consensus to move to
Java 1.6 for m-a-p 2.6?
I'm stuck on...
The version of plexus I need to get the feature I want requires 1.6,
and the existing code is insisting on 1.5.
[INFO] --- maven-enforcer-
On Oct 4, 2015 4:08 PM, "Dennis Lundberg" wrote:
> From what I have read we need to move all of maven-plugins to git in one
> go.
> See the thread "Full migration to Git" for more info
>
I guess I'll have to go tune into that thread.
>
> 2015-10-04 14:07 GMT+02:00 Benson Margulies :
> > OK, th
>From what I have read we need to move all of maven-plugins to git in one go.
See the thread "Full migration to Git" for more info
2015-10-04 14:07 GMT+02:00 Benson Margulies :
> OK, then, I want to move it to git first. Any objections?
>
>
> On Sun, Oct 4, 2015 at 7:27 AM, Karl Heinz Marbaise wr
Yes, we have a wiki page with an official procedure.
On Oct 4, 2015 9:11 AM, "Tibor Digana" wrote:
> @Benson
> Maybe no objections if you mention details of moving repo from svn / to
> github, etc.
> Do you mean that assembly will be fully git based in [1] which means I will
> be able to directly
@Benson
Maybe no objections if you mention details of moving repo from svn / to
github, etc.
Do you mean that assembly will be fully git based in [1] which means I will
be able to directly push to GitHub and the pull-requests as well?
[1] https://github.com/apache/maven-plugins/tree/trunk/maven-ass
OK, then, I want to move it to git first. Any objections?
On Sun, Oct 4, 2015 at 7:27 AM, Karl Heinz Marbaise wrote:
> Hi,
>
>
> On 10/4/15 10:58 AM, Robert Scholte wrote:
>>
>> Hmm, I see we tried to start with a 3.0.0 version, so not on the trunk.
>>
>> Assembly is far from ready as M3-only, s
Hi,
On 10/4/15 10:58 AM, Robert Scholte wrote:
Hmm, I see we tried to start with a 3.0.0 version, so not on the trunk.
Assembly is far from ready as M3-only, so I suggest branching the latest
tag.
Yes that's the way to make a fix release...
Kind regards
Karl Heinz Marbaise
thanks,
Robert
Hmm, I see we tried to start with a 3.0.0 version, so not on the trunk.
Assembly is far from ready as M3-only, so I suggest branching the latest
tag.
thanks,
Robert
Op Fri, 02 Oct 2015 13:26:18 +0200 schreef Benson Margulies
:
Could we do this? I'm waiting on the 'snappy' support.
---
Could we do this? I'm waiting on the 'snappy' support.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
24 matches
Mail list logo
