to me, it's clear we need some formal attribution to ASF from each major
contributor, since the code was committed to Codehaus, not ASF, and Codehaus
is not an antity that can transfer the result to ASF
for the formal part, without being a lawyer, I suppose each constributor has
to confirm he
When/if we move these components I assume they will get a new groupId? Will
that not cause issues with duplicated plexus libraries (due to two
different sets of GA) until everything has moved over to the new
dependencies?
/Anders
On Thu, Sep 11, 2014 at 8:10 AM, Hervé BOUTEMY
I agree that it is about projects migrating dependencies - which can take
awhile, to put it mildly.
However, migrating package names at the same time as migrating groupIDs can
go a long way towards avoiding ClassCastExceptions.
That would - in turn - imply that a new major version number is
Excellent proposal Hervé, but how do we deal with jira-based
submissions ? I am probably @author of half my committs and @committer
of the rest ?
Kristian
2014-09-11 8:10 GMT+02:00 Hervé BOUTEMY herve.bout...@free.fr:
to me, it's clear we need some formal attribution to ASF from each major
A mixture. The release plugin had not moved.
On Sep 10, 2014 11:46 PM, Chris Graham chrisgw...@gmail.com wrote:
Sorry, I thought that the plugins, the scm ones in this case, had moved to
git? Still in SVN? If so, then no issues.
-Chris
On Thu, Sep 11, 2014 at 11:43 AM, Benson Margulies
Hi Manfred,
so you mentioned a shared component is this the component you mean:
http://maven.apache.org/shared/maven-dependency-tree/
currently in JIRA are two issues solved so i don't see a reason not to
release a new version of this component...
If you like i can start it...
Kind
Hi,
The vote has passed with the following result:
+1 (binding):
Jason van Zyl,
Karl-Heinz Marbaise,
Hervé Boutemy,
Oliver Lamy
+1 (non binding): none.
I will promote the artifacts to the central repo.
Kind regards
Karl-Heinz Marbaise
tested by replace wagon*2.6 for wagon*2.6 under my maven-3.2.3/lib.
It turns out maven 3.2.x now include jsoup, commons-io, and commons-lang
under lib dir, so http://jira.codehaus.org/browse/WAGON-407 no longer
needed unless maven dev remove thosed shaded file when ever wagon 2.7 got
pushed into
Hi all!
As mentioned in the hangout earlier today it would be great if we could get a
release of the Maven Dependency Tree component done.
Specifically the Android Maven Plugin relies on these changes
https://github.com/apache/maven-shared/commit/20380b7f6e61e09edd63695da7661b82f7e3b1b7
That would be great!
Karl Heinz Marbaise wrote on 11.09.2014 13:19:
Hi Manfred,
so you mentioned a shared component is this the component you mean:
http://maven.apache.org/shared/maven-dependency-tree/
currently in JIRA are two issues solved so i don't see a reason not to
release a
Hi Manfred,
Hi all!
As mentioned in the hangout earlier today it would be great
if we could get a release of the
Maven Dependency Tree component done.
Specifically the Android Maven Plugin relies on these changes
The Apache Maven team is pleased to announce the release of the
Apache Maven RAR Plugin, Version 2.4
A resource adapter is a system-level software driver that a Java application
uses to connect to an enterprise information system (EIS). The RAR plugin has
the capability to store these resource
Further test shows that http://jira.codehaus.org/browse/WAGON-407 is NOT
fixed so it is best to revert it, and mark as wont fix
How it is tested
under apache-maven-3.2.3/lib
1. Replace wagon*2.6* with wagon 2.7, I can use wagon-maven-plugin to
download. This worls
2. Remove
From today's maven hangout discussion
Just want to let you know Kristian Rosenvold
https://plus.google.com/u/0/112402174582006942652?prsrc=4 mentioned [1]
he did some work on this area
-D
[1]
http://maven.40175.n5.nabble.com/Use-native-tar-to-unpack-good-bad-idea-td5794712.html
How did you test that?
--
Olivier
On Sep 12, 2014 7:13 AM, Dan Tran dant...@gmail.com wrote:
Further test shows that http://jira.codehaus.org/browse/WAGON-407 is NOT
fixed so it is best to revert it, and mark as wont fix
How it is tested
under apache-maven-3.2.3/lib
1. Replace
check out
https://svn.codehaus.org/mojo/trunk/mojo/wagon-maven-plugin/src/it/http-download/
run
mvn clean install -Dversion=1.0-beta-5
-D
On Thu, Sep 11, 2014 at 2:24 PM, Olivier Lamy ol...@apache.org wrote:
How did you test that?
--
Olivier
On Sep 12, 2014 7:13 AM, Dan Tran
Robert has looked into this in more detail, and think the trail points back
into SCM. As per info I've added to the JIRA, it is not caused by git
barking at the release.properties and pom.xml.xxx file; if you add those to
.gitignore, they disappear from the scene, but it still does not work. I'm
So there is something here I don't understand or you have give me more
details on how to test your problem.
mb-olamy:http-download olamy$ mvn clean install -Dversion=1.0-beta-5
[INFO] Scanning for projects...
[INFO]
[INFO]
that works because M2_HOME/lib has jsoup.jar, common-io.jar,
commons-lang.jar ( those are NOT in 3.1.x)
Try to remove commons-io.jar, it will fail since maven could not find a
commons-io class. The question here why maven could not find the same
class under wagon-http-2.7-shaded.jar
-Dan
On
19 matches
Mail list logo
