Hi,
This is a new shared component consisting of code from Maven WAR
Plugin, that has been repackaged for reuse by other plugins.
We solved 1 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&styleName=Html&version=19526
There no issues left in JIRA:
http://jira.codehaus.o
Are you sure it's not using the src package uploaded in parallel with the
binary jar? This was my understanding. Doing it from SCM would be a mine
field at best. I know it gets javadocs this way, assumed source was the
same.
On Sat, Aug 10, 2013 at 9:20 PM, Arnaud Héritier wrote:
> AFAIR in eclip
AFAIR in eclipse m2e ( I don't use it anymore ) you can checkout the
code of any maven dependency/project (materialize feature). I'm almost
sure that it is using informations from SCM part in the POM to do it.
I think it isn't the only usage of it. I'm not 100% satisfied of this
usage because such
I found that most people use
false and
true
Which renders most of the stuff useless in GIT.
LieGrue,
strub
- Original Message -
> From: Fred Cooke
> To: Maven Developers List
> Cc:
> Sent: Saturday, 10 August 2013, 15:19
> Subject: Re: What is the correct Git SCM URL for a branc
Hi,
So, we should not have in there at all?
Say I wanted to release Maven 2.2.2 from the branch, would this be the
correct recipe?
1. Clone the Git repo for Maven
2. "Select" the branch/head called "maven-2.2.x" using Git
3. mvn release:prepare, mvn release:perform
If that is correct how will
Convention over configuration is fine. Dictatorships end badly. Make it the
convention, and allow it to be configured off. This is where Maven has
always failed from time to time, especially in the old days. The less it's
true, the better.
On Sat, Aug 10, 2013 at 3:13 PM, Olivier Lamy wrote:
> O
On 10 August 2013 23:06, Fred Cooke wrote:
> Please keep such information leakage optional. The editing of, and indeed
> adding of, the "tag" element by the release plugin should already be
> optional IMO.
Why?
With such information I know which tag has been used to build
artifacts. (
http://rep
Please keep such information leakage optional. The editing of, and indeed
adding of, the "tag" element by the release plugin should already be
optional IMO. Especially if it breaks formatting of the POM, which it does
in some cases, at least. And yeah, I know why, and I know it's not a
trivial fix.
On 10 August 2013 21:12, Dennis Lundberg wrote:
> Hi,
>
> I'm looking at the sources for Maven core in Git, which I'm learning
> as I go along.
>
> "master" is at version 3.1.1-SNAPSHOT and has this in its pom.xml
>
>
> scm:git:https://git-wip-us.apache.org/repos/asf/maven.git
>
> scm
Just did the quick POC (without red wine!!) at
https://github.com/krosenvold/plexus-classworlds/commit/f1059c904788eb96e22a9a6a1ead6b3febe57948
By recording the classloading and re-running in reverse order in a
(single) separate thread on
subsequent reloads, it would appear I almost cut the class
Hi,
I'm looking at the sources for Maven core in Git, which I'm learning
as I go along.
"master" is at version 3.1.1-SNAPSHOT and has this in its pom.xml
scm:git:https://git-wip-us.apache.org/repos/asf/maven.git
scm:git:https://git-wip-us.apache.org/repos/asf/maven.git
https://gi
11 matches
Mail list logo
