The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.0.
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/
The new plugin is
Hi,
Maven 2.x supports a CLI like
mvn -r -D maven.reactor.includes=... -D maven.reactor.excludes=...
to select sub directories of the current directory by glob patterns for
the reactor.
Now that the Make-like reactor mode is in-place [0], I wonder whether
this old-school mode still
Lukas Theussl wrote:
Right now there are also a number of other issues scheduled that are not
related (eg MSITE-79, MSITE-206, MSITE-326) which I would like to leave
out and schedule for a later release.
Is this ok with everyone?
+1, I don't see the point in blocking a release or even just
Paul Gier wrote:
I didn't even know this feature existed!
Excellent, just remember to forget that we talked about ;-)
To make sure I understand the new make-like reactor mode, will it allow
me to only select certain modules in a multi-module build? Something
like this?
mvn -pl
Jason van Zyl wrote:
It's there if you go to the UI, something appears to be wrong with the
redirects.
The repo isn't closed, that could explain why it doesn't show up in
public via the URL.
Benjamin
-
To unsubscribe,
Jason van Zyl wrote:
Not sure if it's in flux
but the format of what came out in the Jar Signer Plugin and what
Vincent just released for the Javadoc Plugin seems to be different
though the same version of the parent appears to have been used.
The parent is not responsible for the
Hi Olivier,
Author: olamy
Date: Sun Jul 26 23:22:56 2009
New Revision: 798002
URL: http://svn.apache.org/viewvc?rev=798002view=rev
Log:
[MCHANGES-161] Add properties interpolation for changes.xml
null
Modified:
Hi Olivier,
Author: olamy
Date: Mon Jul 27 23:28:58 2009
New Revision: 798330
URL: http://svn.apache.org/viewvc?rev=798330view=rev
Log:
declare Apache Snapshot Repository until maven-filtering release is here
Modified:
maven/plugins/trunk/maven-changes-plugin/pom.xml
Modified:
Hi Arnaud,
Author: aheritier
Date: Mon Jul 27 23:54:06 2009
New Revision: 798336
URL: http://svn.apache.org/viewvc?rev=798336view=rev
Log:
issue MECLIPSE-178: symbolic links need to able to be specified in the pom
http://jira.codehaus.org/browse/MECLIPSE-178
Applied the patch from ashok to
Vincent Siveton wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-027
Staging site:
http://maven.apache.org/plugins/maven-javadoc-plugin-2.6/
+1
Benjamin
-
To unsubscribe, e-mail:
Jason van Zyl wrote:
I think he would be a great addition to the team.
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Geoffrey De Smet wrote:
IMHO the FAQ should follow the recommended guidelines
Well, the recommendation is to not skip tests ;-)
so shouldn't it use skipTests instead of maven.test.skip?
I updated the FAQ to mention both properties, it's up to the user to
choose what fits his/her
Brett Porter wrote:
I think he'd be a great addition to the team.
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Hi,
I would like to propose an extension of the mojo annotation
@requiresDependencyResolution requiredScope
This currently allows to resolve only a single scope from the set
compile, runtime and test. A problem I have seen in some plugins
is about using runtime scope. This scope is not a
Hi Vincent,
Author: vsiveton
Date: Sat Aug 1 11:31:06 2009
New Revision: 799840
URL: http://svn.apache.org/viewvc?rev=799840view=rev
Log:
o using doxia and doxia sitetools 1.0
o using snapshot linkcheck
o added the invoker as a workaround for the linkcheck goal
Modified:
Hi,
as per MNG-4024, the CLIManager was exposed to the public API. Its
parse() method returns a CommandLine object from commons-cli. Per
MNG-4166, commons-cli is no longer filtered from the plugin realm.
This constellation prohibits the usage CLIManager.parse() from Maven
2.2.x in plugins
Hi Vincent,
Author: vsiveton
Date: Sun Aug 2 11:24:25 2009
New Revision: 800032
URL: http://svn.apache.org/viewvc?rev=800032view=rev
Log:
o using maven 2.0.9
This also requires to bump the prerequsites on Maven, e.g. older Maven
versions don't support MavenProject.clone() and will die with
Hi Vincent,
Think about plugins which use ${project.reporting.outputDirectory} in
there conf.
A properly [0] implemented reporting plugin must not use this value
during the site lifecycle. But you're right, updating the model is more
robust as it captures the buggy plugins as well.
Brian Fox wrote:
I think those bugs may be due to the plugin using the runtime scope
not the runtime classpath? The runtime classpath should include the
compile scope artifacts.
Let my try to describe the problem in more detail. Assume the following
POM snippet for the project that wants to
Brian Fox wrote:
In the dependency and enforcer plugins where I potentially need
everything, I just ask for test to be resolved and then i pick the
elements i need.
Yeah, I know, the problem I described is not impossible to solve. All I
wondered is whether this pattern does not give evidence
Barrie Treloar wrote:
I cant remember if this is already raised somewhere else, but there is
similar problem with the scope test.
test means both testCompile and testRuntime (which themselves dont
exist) so things like dependency:analyze reports errors because that
level of granularity does not
Hi Vincent,
Author: vsiveton
Date: Mon Aug 3 12:58:03 2009
New Revision: 800341
URL: http://svn.apache.org/viewvc?rev=800341view=rev
Log:
MJAVADOC-248: Site 'Usage' page references 2.5 version of m-javadoc-p
o fix it
Modified: maven/plugins/trunk/maven-javadoc-plugin/src/site/apt/usage.apt
Vincent Siveton wrote:
IMHO it will be an overhead for nothing...
Well, enabling the doc filtering is a one-time task and I wouldn't say
it's for nothing. The problem I see with those version-less POM snippets
is that users just use them as is, without further thought. Nobody is
going to
Brian Fox wrote:
Perhaps what is needed is the addition of a
few more resolution scope tags that a plugin could ask for. I mean,
how many combinations aren't already covered by the existing scopes?
If it's small and adding one or two more might be easier to support
and maintain than allowing a
Hi,
in the interface ToolchainManagerPrivate, i.e. the one used by the
maven-toolchain-plugin to setup the toolchains for a build, we currently
have the method
ToolchainPrivate[] getToolchainsForType( String type )
The impl of this method processes the toolchains.xml. Given the above
Stephen Connolly wrote:
Add an interface
public interface MavenSessionAware {
public void setMavenSession(MavenSession session);
public MavenSession getMavenSession();
}
and make the impl additionally implement the MavenSessionAware interface?
If you refer to the impl of
John Casey wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-staging-013
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
John Casey wrote:
The artifacts we're voting on for the 2.2.1 release are here:
https://repository.apache.org/content/repositories/maven-staging-018/
+1
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=15512styleName=HtmlprojectId=11990
There are no issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11990status=1
Staging repo:
Benjamin Bentmann wrote:
The maven-toolchain-plugin is the only client of the
ToolchainManagerPrivate interface and was not released yet. However,
changing the interface means the next plugin version can only be used
with a new Maven version, say 2.3+.
I updated the plugin to reflectively
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
Hi,
for Maven 3.x, I would like to discuss the introduction of a new mojo
annotation
@requiresDependencyCollection required-scope
As the name probably suggests, the intended effect is to resemble an
invocation of the artifact collector, i.e. calculate the dependency tree
but don't try
Hi,
with a new major release of Maven hopefully not far away, we might also
want to review aggregator plugins. I tried to get some inspirations from
existing proposals and put some further thoughts about this in the wiki
[0] and would like to know what you think. Are the presented use cases
Stephen Connolly wrote:
Do you want comments on this thread or on the wiki?
Good question. Personally, I could imagine keeping the discussion on the
mailing list is easier to follow, this linear comment listing in
Confluence doesn't look like being up to a threaded discussion. So I
suggest
[0] http://docs.codehaus.org/display/MAVEN/Aggregator+Plugins
1. Background
In Maven 2.x we have a boolean mojo annotation @aggregator with the
following effects on the mojo execution:
Execution
For mojos executed directly from the CLI, the mojo will only be
executed once and not per
Wendy Smoak wrote:
It would also be good to post the original document on the mailing
list, so it will be in the archives as a basis for the discussion.
Right, quoting would be easier if the content is handy, silly me.
Benjamin
Stephen Connolly wrote:
To address this distinction in aggregation scope, we might start off with
new mojo annotations like @aggregator top-level|project that plugin
authors can use to indicate the desired operational mode. But it seems this
ultimatively demands a new POM element to enable the
Brian Fox wrote:
Project Ordering
A project with packaging pom can serve both as a parent POM and as an
aggregator POM. [...] For this reason, the project sorter needs to
be changed to mark an aggregator POM as a dependant of all its
modules.
What happens in the normal case where the pom is
Vote open for 72 hours.
Ping
Ping
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
Brian Fox wrote:
Such a project would be built after its child modules.
So in essence we are relying on the resolution of this artifact (the
parent) from the reactor and not from the local repo?
Just to make sure we have the same understanding of artifact here. For
some project, we have
Hi,
The vote has passed with the following result:
+1 (binding): Vincent Siveton, Olivier Lamy, Arnaud Héritier
I will promote the artifacts to the central repository and continue with
the release. Thanks to the voters to help get this out!
Benjamin
Arnaud HERITIER wrote:
Staging
repo:https://repository.apache.org/content/repositories/maven-staging-025/
This is missing the ASF-compliant source distribution.
Benjamin
-
To unsubscribe, e-mail:
Arnaud HERITIER wrote:
I have to take the example on another recent release ?
Likely, either grab the assembly descriptor and the corresponding POM
bits from some plugin or try John's recent work on [0].
Benjamin
[0]
Arnaud HERITIER wrote:
Must I add this :profile
idrelease/id
[...]
Or this :
profile
idapache-release/id
[...]
??
Given the effective POM for the artifact filters says
plugin
artifactIdmaven-release-plugin/artifactId
version2.0-beta-8/version
configuration
Hi Arnaud,
Author: aheritier
Date: Sun Aug 16 12:54:37 2009
New Revision: 804685
URL: http://svn.apache.org/viewvc?rev=804685view=rev
Log:
Add source distrib for apache
Modified:
maven/shared/trunk/maven-common-artifact-filters/pom.xml
Modified:
The Maven team is pleased to announce the release of the Maven Jarsigner
Plugin, version 1.1.
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
Arnaud HERITIER wrote:
Staging
repo:https://repository.apache.org/content/repositories/maven-staging-027/
Staging site:http://maven.apache.org/shared/maven-common-artifact-filters-1.2/
+1
Benjamin
-
To unsubscribe,
Hi,
Vincent notified me that many of the site files I recently deployed via
mvn site-deploy (using Maven 2.2.1) ended up with the wrong security
settings: While the files are group-writable, the group is bentmann
and not maven.
I had a quick chat with someone over at #asfinfra and they
Wendy Smoak wrote:
Nothing changed that I know of... it's always been like this, and you
have to go change the permissions on new files that you deploy.
I probably couldn't explain the issue properly. I know that we have to
update the permissions in terms of chmod, in particular make files
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:
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:
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:
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
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:
systemPath${java.home}/../lib/tools.jar/systemPath
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.
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,
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:
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
Tony Chemit wrote:
Le Thu, 10 Sep 2009 19:41:00 -0700,
Jason Chaffee jason.chaf...@zilliontv.tv 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
Hi Nicolas,
Author: nicolas
Date: Thu Sep 10 10:06:11 2009
New Revision: 813343
URL: http://svn.apache.org/viewvc?rev=813343view=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:
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 in
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
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,
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,
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
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
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 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=14534styleName=HtmlprojectId=11761
There are still a couple of issues left in JIRA:
Hi,
We solved 21 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=14609styleName=HtmlprojectId=11441
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11441status=1
Staging repo:
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.
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
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
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:
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:
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=15698styleName=HtmlprojectId=11990
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11990status=1
Staging repo:
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
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
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=15018styleName=HtmlprojectId=11139
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11139status=1
Staging repo:
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
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:
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,
501 - 600 of 1109 matches
Mail list logo
