Brett Porter wrote:
Maybe it used to have the setgid bit set on the directory?
From some docs I found on this bit that looks pretty much like the
thing we want so I asked infra to put in on/back:
https://issues.apache.org/jira/browse/INFRA-2189
Benjamin
Stephen Connolly wrote:
Item not found on path /repositories/apache-staging-029
This appears to be a typo, the proper URL is
https://repository.apache.org/content/repositories/maven-staging-029/
i.e. "maven-staging-029", not "apache-staging-029".
Benjamin
---
John Casey wrote:
The staging repository for the apache-resources and
source-release-descriptor artifacts is here:
https://repository.apache.org/content/repositories/apache-staging-028
The staging repository for maven-parent-13 is here:
https://repository.apache.org/content/repositories/apac
John Casey wrote:
Since maven-filtering is recently released (or in the process of
releasing) is this snapshot dependency really necessary
IIRC, the reason for the snapshot dependency was to get MSHARED-93 out
into IDEs.
Benjamin
--
John Casey wrote:
The staging repository is here:
https://repository.apache.org/content/repositories/maven-staging-032
+1, the IT custom-delimiter of the maven-resources-plugin is buggy but
otherwise the releases look good.
Benjamin
---
Issue Type: Bug
Affects Versions: 1.5.15
Reporter: Benjamin Bentmann
Attachments: pu-vs-pi.zip
[r8255|http://fisheye.codehaus.org/changelog/plexus/?cs=8255] caused exclusion of the
plexus-interpolation classes from the plexus-utils JAR. This in turn makes usage
Arnaud HERITIER wrote:
In theory, we remove things only in a major version (2.0).
That's fine, so we'll call it 2.0.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h
John Casey wrote:
I have a working implementation [...] but it
currently depends on Java 1.5. [...] I'd really prefer to leave this requirement
on 1.5 in place, to help us gradually pull ourselves out of the JDK 1.4
tarpit.
+1
Benjamin
-
Sohn, Matthias wrote:
- where can I find the sources ?
See http://maven.apache.org/source-repository.html
- which is the right developer mailing list ?
This one.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.
Hi,
there's still some work left to do but after a rather long journey we're
finally approaching a point where Maven 3.x stabilizes and can be used
as a drop-in replacement for Maven 2.x. In an attempt to hunt down
regressions/incompatibilities and to provide users an overview of known
issues
Arnaud HERITIER wrote:
I'd like to propose giving commit access to Stephen Connolly.
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Ioannis Deligiannis wrote:
Is states the following:
${java.home}/../lib/tools.jar
If not obvious, let say that java.home=c:\java\jdk1
But this should resolve to:
C:\java\lib\tools.jar which is wrong.
Usually, ${java.home} points to the private JRE of the JDK, e.g.
JAVA_HOME=D:\Programme\Jav
Stefan Sperling wrote:
The message should either be removed entirely (which is what the
patch below does) or changed to 'debug'.
Patches usually go into the issue tracker:
http://jira.codehaus.org/browse/ARCHETYPE
Benjamin
-
Jason van Zyl wrote:
And b configures a plugin with dependency foo, and c configures the same
plugin, but with dependency bar, if I run mvn in "c", it works fine (gets
bar), but if I run from a, it doesn't work right in c. It just gets
foo.
Thus, it works differently depending on where I type
Vincent Siveton schrieb:
In a 2.0 case, we need to sync some classes (PLXUTILS-21)
I removed the interpolation stuff and followed Arnaud's advice to bump
the version to 2.0.
Let me repeat that the removal of the interpolation classes was to get
plexus-utils back into an easy shape, without
Hi,
I was hoping to get some plugin release done but figured there is still
some tiny bit missing so first I would like to get maven-plugins:14
released which inherits from maven-parent:13 and as such provides the
configuration for the ASF-compliant source distros.
Staging repo:
https://repo
Hi,
sorry to bug you guys again, but there is another POM that would be
handy once released :-)
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-009/
Guide to testing staged releases:
http://maven.apache.org/guides/development/guide-testing-releases.html
Vote op
Tony Chemit wrote:
Le Thu, 10 Sep 2009 19:41:00 -0700,
Jason Chaffee a écrit :
Is there a way to turn off javadoc execution during release:perform? I
using -Dgoals=deploy, but javadoc execution is still happening.
from the version 2.5, you can skip the javadoc plugin via the
configuratin
Hi Nicolas,
Author: nicolas
Date: Thu Sep 10 10:06:11 2009
New Revision: 813343
URL: http://svn.apache.org/viewvc?rev=813343&view=rev
Log:
[MRELEASE-383] svn inconsistent line ending style
CDATA sections after transformation use "\n" as line ending style and break the
xml file consistency
fix
Martin Gainty wrote:
java.lang.ClassCastException: org.apache.maven.model.Repository cannot be cast
to org.apache.maven.artifact.repository.ArtifactRepository
Among the top-10 Google results for "ClassCastException:
org.apache.maven.model.Repository" I get:
http://jira.codehaus.org/brows
Martin Gainty wrote:
i downloaded maven-3.0 full
at command line ran
mvn -e -X install
I don't want to sound rude but those few lines aren't really helpful either.
You "downloaded maven-3.0 full", is that "downloaded" as in you
downloaded some source/binary archive from some URL, or more as
Martin Gainty wrote:
[INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu
gins:maven-remote-resources-plugin:1.0:process': Unable to load the mojo 'org.ap
ache.maven.plugins:maven-remote-resources-plugin:1.0:process' in the plugin 'org
.apache.maven.plugins:maven-remo
John Casey wrote:
The staging repository is here:
https://repository.apache.org/content/repositories/maven-staging-016/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail
John Casey wrote:
The staging repository is here:
https://repository.apache.org/content/repositories/maven-staging-017/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, John Casey, Hervé Boutemy, Arnaud Héritier,
Lukas Theussl, Vincent Siveton
+1 (non-binding): Stephen Connolly
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, John Casey, Hervé Boutemy, Arnaud Héritier,
Lukas Theussl, Vincent Siveton
+1 (non-binding): Stephen Connolly
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
John Casey wrote:
Staging Repository:
https://repository.apache.org/content/repositories/maven-staging-018/
+1
Staging Site:
http://maven.apache.org/plugins/maven-remote-resources-plugin-1.1/
The site has weird links in the nav bar so just be sure to not cp this
to the non-versioned URL
Tristan JC Rouse wrote:
1) The DefaultArtifactResolver class's resolve(Artifact, List,
ArtifactRepository) method takes an ArtifactRepository parameter which
specifies the local repository. I can't figure out where to find this
Have a glance at the sections "For accessing artifacts and reposit
Hi,
the ITs of the versions-maven-plugin employ version ranges like
"[,3.0-!)". The interesting question is how something like "3.0-!"
should compare to usual version numbers. For instance, we currently have
Maven 2.x:
3.0-! < 3.0-SNAPSHOT < 3.0
Maven 3.x, cf. [0]:
3.0-SNAPSHOT < 3.0 <
Hervé BOUTEMY wrote:
FYI, I just took another pass on OSGi spec and added a link to it in [0] with
pointer to the corresponding paragraphs I know of. It is really very very
light and doesn't tell anything on comparison for version with qualifiers: I
hope I missed something...
Thanks for the
Hervé BOUTEMY wrote:
any objection if I move maven-artifact to retired in svn [2]?
Nope
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
This is a prerequisite for the upcoming release of
maven-invoker-plugin:1.4 which I will stage next.
We solved 1 issue:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14534&styleName=Html&projectId=11761
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/s
Hi,
We solved 21 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14609&styleName=Html&projectId=11441
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11441&status=1
Staging repo:
https://repository.apache.org/c
Hi,
The current fix for this issue makes me feel a little uneasy. As is, the
code in the 2.2.x branch applies profiles from the settings in full
extent to POMs of dependencies. In particular, properties defined by
profiles from the user's settings override properties in dependency POMs.
For
Brett Porter wrote:
Any objections to disabling write to the Codehaus MAVEN space and
pointing people to cwiki as described below?
Nope.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional com
Benjamin Bentmann wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-038/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h
Benjamin Bentmann wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-039/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, Arnaud Héritier, Benjamin Bentmann
+1 (non-binding): Stephen Connolly
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
Hi,
The vote has passed with the following result:
+1 (binding): Olivier Lamy, Arnaud Héritier, Benjamin Bentmann
+1 (non-binding): Stephen Connolly
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
The Maven team is pleased to announce the release of the Maven Invoker,
version 2.0.11.
This component allows to programmatically invoke Maven. See the
component's site for more details:
http://maven.apache.org/shared/maven-invoker/
To use this component in your projects, add the following
The Maven team is pleased to announce the release of the Maven Invoker
Plugin, version 1.4.
This plugin allows to run Maven on a collection of projects and is
especially useful for integration testing of other Maven plugins. See
the plugin's site for more details:
http://maven.apache.org/p
The Maven team is pleased to announce the release of the Maven Invoker
Plugin, version 1.4.
This plugin allows to run Maven on a collection of projects and is
especially useful for integration testing of other Maven plugins. See
the plugin's site for more details:
http://maven.apache.org/p
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=15698&styleName=Html&projectId=11990
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11990&status=1
Staging repo:
https://repository.apache.org/co
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Brian Fox, Olivier Lamy
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
-
To unsubscribe
The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.2.
This plugin signs and verifies the project artifacts using the jarsigner
tool. See the plugin's site for more details:
http://maven.apache.org/plugins/maven-jarsigner-plugin/
This plugin is meant to
John Casey wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-013/
Staging site (should be showing up in a couple hours or so):
http://maven.apache.org/plugins/maven-resources-plugin-2.4.1/
+1
The source distro contains target/test-classes so maybe you want
John Casey wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-014/
Staging site (should be showing up in a couple hours or so):
http://maven.apache.org/plugins/maven-repository-plugin-2.3/
+1
Benjamin
--
Hi,
We solved 10 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=15018&styleName=Html&projectId=11139
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11139&status=1
Staging repo:
https://repository.apache.org/c
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Dennis Lundberg, Arnaud Héritier,
Vincent Siveton, Lukas Theussl, Olivier Lamy, John Casey
+1 (non binding): Nicolas de Loof, Stephen Connolly
I will promote the artifacts to the central repository and
The Maven team is pleased to announce the release of the Maven Plugin
Tools, version 2.5.1.
This plugin assists authors of Maven plugins in the creation of a plugin
descriptor and documentation by scanning the plugin sources for mojo
annotations. See the plugin's site for more details:
htt
Arnaud HERITIER wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-017/
Staging site:
http://maven.apache.org/plugins/maven-source-plugin-2.1.1/
+1
The source distro again contains target/** so we probably should look
into another assembly descriptor, some
Arnaud HERITIER wrote:
Benjamin, should I fix something ? :-(
For this release? No, not because of me. The stuff from target is
superfluos but should not hurt, unless you discover files that reveal
sensitive information.
If you wanted to look into working on the underlying assembly
descri
gerhard presser wrote:
because of that i want to fetch the last release of my artifact.
how can i do that. i'm playing around with ArtifactResolver,
ArtifactMetadataSource etc.
is this the right way?
Yes, [0] and [1] could provide further hints on using those components.
IIRC, the artifact re
Hi Nicolas,
Author: nicolas
Date: Thu Oct 15 08:25:55 2009
New Revision: 825432
URL: http://svn.apache.org/viewvc?rev=825432&view=rev
Log:
[MECLIPSE-156] Plugin should support setting file encoding
o read maven-compiler-plugin configuration for encoding and generate related
.settings configur
Stephane Nicoll wrote:
I am trying to stage the ear plugin v 2.4. So far so good but I have
the following error when I try to generate the site (with -Preporting)
[INFO]
[ERROR] BUILD ERROR
[INFO] -
Hi Dennis,
Author: dennisl
Date: Wed Oct 14 19:52:51 2009
New Revision: 825243
URL: http://svn.apache.org/viewvc?rev=825243&view=rev
Log:
[MCHECKSTYLE-105] Update to Checkstyle 5.0
Submitted by: Felix Röthenbacher, Ben Speakmon and Max Berger
Reviewed by: Dennis Lundberg
Modified:
maven/pl
Niall Pemberton wrote:
The building m2 guide is out of date for maven-3[1] since it moved[2]
location in the repository
Patch applies, thanks, but for the future, please fill an issue at
http://jira.codehaus.org/browse/MNGSITE and attach the patch there.
Benjamin
-
Stephen Connolly wrote:
maven-deploy-plugin updates the metadata whenever there is a deploy...
e.g.
it sets the /metadata/versioning/latest to the version that is has just
deployed. and if the version is not a SNAPSHOT, it sets the
/metadata/versioning/release as well.
Actually, it's a littl
Stephane Nicoll wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-004/
Staging site:
http://maven.apache.org/plugins/maven-ear-plugin-2.4/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsub
Dennis Lundberg wrote:
https://grid.sonatype.org/ci/job/maven-plugins-ITs/jdk=1.5,label=ubuntu/296/consoleFull
Wait a second, where did you find that URL?
When you are at
https://grid.sonatype.org/ci/job/maven-plugins-ITs/jdk=1.5,label=ubuntu/296/console,
the page starts with a sentence ab
Hi Stephen,
Author: stephenc
Date: Tue Oct 20 19:18:02 2009
New Revision: 827765
URL: http://svn.apache.org/viewvc?rev=827765&view=rev
Log:
Implements MINVOKER-95
See [0] for the recommended template.
Also, please remember to set a "Fix Version" for the issue.
Added:
maven/plugins/trunk/m
Hervé BOUTEMY schrieb:
what about MavenProject.class.getPackage().getImplementationVersion()?
That could be a good additional check because of its simplicity and
different data source. I wouldn't suggest to make it the only check
because of [0]:
"Null is returned if no package object was c
Brian Fox wrote:
What was wrong with the RuntimeInformation that was present in M2?
It was put in maven-compat and deprecated in M3 so we were looking for
alternatives.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@m
Andrew Harmel-Law wrote:
I am having the exact same problem, having just upgraded my plugin to 1.327.
However, because the file with the illegal escape characters is being auto
generated, I cannot escape them.
As far as I understand, the file is generated by the maven-hpi-plugin,
so the issue
Stephen Connolly wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-013/
Staging site:
http://maven.apache.org/plugins/maven-invoker-plugin-1.5/
+1
Benjamin
-
To unsubscribe, e-mail: dev-
Vincent Siveton wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-011
Staging site:
http://maven.apache.org/plugins/maven-javadoc-plugin-2.6.1
+1
Benjamin
-
To unsubscribe, e-mail: dev-u
Hi,
This is a maintenance release for the assembly descriptor that we use to
create ASF-compliant source distros. This release fixes a bug in version
1.0 that erroneously includes paths like "target/**/src/**" in the distro.
Note: If you want to test this descriptor with the Maven Assembly
P
Hi,
these releases are primarily meant to incorporate the fixed source
release assembly descriptor into our projects, thereby addressing the
issue outlined in http://jira.codehaus.org/browse/MASSEMBLY-446.
Furthermore, maven-parent:14 also contains an update to the
configuration of the maven
Paul Benedict wrote:
I realize there is no alpha-3, but I was hoping there were snapshot
distros somewhere.
CI is spitting those out here:
https://grid.sonatype.org/ci/job/maven-3.0.x-bootstrap/jdk=1.5,label=ubuntu/ws/trunk/apache-maven/target/
Benjamin
Hi,
following a comment by Wendy on JIRA, I wanted to re-check what our
plans are for repositories in dependency POMs. In more detail, how is
dependency resolution in Maven 3.x expected to work here:
project ---depends-on---> A ---depends-on---> B
where the POM of A declares the repositor
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Vincent Siveton, Arnaud Héritier, John
Casey, Hervé Boutemy
+1 (non binding): Stephen Connolly
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Vincent Siveton, Arnaud Héritier, John
Casey, Hervé Boutemy
+1 (non binding): Stephen Connolly
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
The Maven team is pleased to announce the release of Apache
Source-Release Assembly Descriptor, version 1.0.1.
This is a standardized assembly descriptor for use in the
maven-assembly-plugin. Source-release artifacts are archives which
contain the full project structure (sources only, no build ou
To be precise, the site descriptors are completely missing from central
for the three parents I released, i.e.:
- maven-parent:14
- maven-plugins:15
- maven-shared-components:13
effectively making those parents useless.
I was thinking about just adding those files (which are both tagged and
i
Hi,
if some of you have a déjà vu while regarding the mail title, that's
fine... my previous attempt at making our release processes smoother
failed due to missing site descriptors in the deployment. So if you
liked the predecessor versions of the parents being voted on, I hope you
also like
Mark Struberg wrote:
But in my local repo, all the artifacts from those repositories gets merged to
a single big landfill.
That seems to be a completely independent issue, isn't it? The question
I originally raised was about what repositories ought to be considered
during dependency resolut
Brian Fox wrote:
I think we have to also consider that 2) is what Maven does now.
(Benjamin thinks it might be 3 but I seem to recall repos added along
the way stick around forever)
I was trying to check what Maven 2.x actually does and came up with this
POM snippet:
org.sonat
Stephen Connolly wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-004
Staging site:
http://maven.apache.org/plugins/maven-toolchains-plugin-1.0
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubsc
Dennis Lundberg wrote:
-1
I tried these POMs with Java 1.4. Unfortunately the changes made in
r830510 by Vincent has created a Java 1.5 dependency on Maven Parent.
That's because Cobertura Maven Plugin 2.3 (specified in reporting
section of Maven Parent)
Is something preventing us from build
Stephen Connolly wrote:
The Maven Toolchains Plugin has been released.
Can this get added to the next board report please.
Done.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Olivier Lamy, Arnaud Héritier
+0 (binding): Dennis Lundberg
+1 (non binding): Stephen Connolly
I will promote the artifacts to the central repository and continue with
the release.
Benjamin
Hi,
Unless somebody objects, I'm going to drop the staging repository
"maven-staging-003" [0] which is a left over of a failed release [1] by
the end of the week.
Benjamin
[0] https://repository.apache.org/content/repositories/maven-staging-003/
[1] http://www.mail-archive.com/dev@maven.ap
Mark Hobson wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-009/
+1
Staging site:
http://maven.apache.org/shared/maven-runtime-1.0-alpha-2/
The site apparently suffers from the missing site descriptor for
maven-shared-components:13, i.e. it's missing stuff li
Henri Gomez wrote:
Caused by: org.apache.maven.shared.filtering.MavenFilteringException
at
org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:130)
at
org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filterResources(Defa
Henri Gomez wrote:
What's the JIRA for this problem (and fix in r832389) ?
I'd like to verify if this bug could affect some of ours projects
There is no JIRA because it's not a bug in Maven itself. As visible from
the mentioned SVN revision, the failure to build Maven was due to a
corrupt re
Mark Hobson wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-012/
Staging site:
http://maven.apache.org/shared/maven-runtime-1.0-alpha-2/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@m
Vincent Siveton wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-013/
Staging site:
http://maven.apache.org/shared/maven-reporting-impl-2.0.4.3
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubsc
Stephen Connolly wrote:
https://svn.apache.org/repos/asf/maven/sandbox/trunk/maven/maven-plugin-enforcer
For M3, drop it in the lib folder and just add
-Dforce.plugins=gId:aId:ver,gId:aId,ver,etc
OK, with some guidance from John I got Maven 3.0-SNAPSHOT (r832795)
including the maven-plugin-e
John Casey wrote:
https://repository.apache.org/content/repositories/orgapacheapache-001/org/apache/apache/7/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@
Mark Hobson wrote:
Maven Runtime has been released.
Can this get added to the next board report please.
Done.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@mav
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11124&version=14345
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11124&status=1
Staging repo:
https://repository.apache.org/content/repositor
Hi Dan,
Author: dfabulich
Date: Fri Nov 6 21:46:48 2009
New Revision: 833566
URL: http://svn.apache.org/viewvc?rev=833566&view=rev
Log:
Adding experimental multithreading support. Naive implementation. Not
guaranteed to work. Builder beware. You'd be crazy to use this...
-Dmaven.threads
Raphaël Piéroni wrote:
Is there anything done about the automatic release of sources along side the
binary in the default release process in the parent of plugins' pom ?
I just found out that the existing source-release assembly descriptors
used by our parents will not work for the Archetype
Hi,
This is a maintenance release for the assembly descriptor that we use to
create ASF-compliant source distros. This release fixes a bug in version
1.0.1 that erroneously excludes paths like "src/**/.classpath" from the
distro.
Note: If you want to test this descriptor with the Maven Assem
Hi,
OK, here we go, another alpha release of Maven, for all those brave guys
that want to take it for a test drive ;-)
We solved many issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500&version=14719
There are still a couple of issues left in JIRA:
http://jira.codehaus.or
Benjamin Bentmann schrieb:
So I wouldn't like to see such experiments on trunk, given we are trying
to stabilize it. Hence I created a branch with your changes and reverted
them on trunk.
In talking with Dan and Wendy on IRC I realized that my immediate
reaction of reverting Dan
Vote open for 72 hours.
Ping.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Julien HENRY schrieb:
I don't know if it is related to Maven 3, but I'm not able to update to a newer
SNAPSHOT that is available in my corporate repository, even by using the -U
command line option. It seems Maven is not even asking the repository manager
for a new version.
If you have -U s
Tony Chemit wrote:
Any idea about it ?
Sorry, not from those few bits of info. Please fill an issue at
http://jira.codehaus.org/browse/MNG with as much information attached as
available. I ideally need something to reproduce, so a minimal test
project or the SVN URL to your project with ste
Benjamin Bentmann wrote:
If you have -U specified and the maven-metadata-nexus.xml for this
parent POM in your local repo is not updated to match the one in your
Nexus, that's indeed a bug. I'll look into it for alpha-4.
Confirmed and tracked in [0]. If you like, CI already produc
401 - 500 of 1131 matches
Mail list logo
