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
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
Hi Nicolas,
Author: nicolas
Date: Thu Oct 15 08:25:55 2009
New Revision: 825432
URL: http://svn.apache.org/viewvc?rev=825432view=rev
Log:
[MECLIPSE-156] Plugin should support setting file encoding
o read maven-compiler-plugin configuration for encoding and generate related
.settings
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=825243view=rev
Log:
[MCHECKSTYLE-105] Update to Checkstyle 5.0
Submitted by: Felix Röthenbacher, Ben Speakmon and Max Berger
Reviewed by: Dennis Lundberg
Modified:
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
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:
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
Hi Stephen,
Author: stephenc
Date: Tue Oct 20 19:18:02 2009
New Revision: 827765
URL: http://svn.apache.org/viewvc?rev=827765view=rev
Log:
Implements MINVOKER-95
See [0] for the recommended template.
Also, please remember to set a Fix Version for the issue.
Added:
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
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:
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
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:
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:
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
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
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 repository
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
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
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
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:
dependencies
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:
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
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,
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]
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
Henri Gomez wrote:
Caused by: org.apache.maven.shared.filtering.MavenFilteringException
at
org.apache.maven.shared.filtering.DefaultMavenFileFilter.copyFile(DefaultMavenFileFilter.java:130)
at
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
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:
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:
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
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:
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:
Hi,
We solved 3 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11124version=14345
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11124status=1
Staging repo:
Hi Dan,
Author: dfabulich
Date: Fri Nov 6 21:46:48 2009
New Revision: 833566
URL: http://svn.apache.org/viewvc?rev=833566view=rev
Log:
Adding experimental multithreading support. Naive implementation. Not
guaranteed to work. Builder beware. You'd be crazy to use this...
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
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=10500version=14719
There are still a couple of issues left in JIRA:
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's commit
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
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
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 produced a fixed
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Olivier Lamy, Arnaud
Héritier
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 Ant
Plugin, version 2.3.
This plugin generates build files for Ant from a POM. See the plugin's
site for more details:
http://maven.apache.org/plugins/maven-ant-plugin/
To use the updated plugin in your projects, you need to add
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,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Olivier Lamy, Brian Fox
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 Apache
Source-Release Assembly Descriptor, version 1.0.2.
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
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Arnaud Héritier, Olivier Lamy, Jason
van Zyl, Stéphane Nicoll, Dan Fabulich, Brian Fox, Brett Porter, Vincent
Siveton, John Casey, Hervé Boutemy
+1 (non-binding): Stephen Connolly, Stuart McCulloch, Paul
Hi,
I noticed that we didn't mention previous alphas of 3.0 on the Maven
site. How do we want to go about that with alpha-3?
To attract more testers, I think we should have this alpha listed in the
download section. E.g. some structure like
* Stable Releases
2.2.1
2.1.0
2.0.10
*
The Maven team is pleased to announce the release of Apache Maven
3.0-alpha-3.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of
Brett Porter wrote:
I've staged a sample site here:
http://people.apache.org/~brett/staged-maven-site/
+1, I like the proposed structure.
Just one minor thing: I believe the JAR/PDF of the site should be listed
separately as currently and not be part of the table listing the 2.2.1
Hi,
Ready for the next round ;-) ?
We solved 6 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14951
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1
Staging repo:
Mark Hobson wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-001/
Staging site:
http://maven.apache.org/plugins/maven-checkstyle-plugin-2.4/
+1
Benjamin
-
To unsubscribe, e-mail:
Benjamin Bentmann wrote:
John Casey wrote:
https://repository.apache.org/content/repositories/orgapacheapache-001/org/apache/apache/7/
+1
I change my vote -1 after discovering that the version of the
maven-javadoc-plugin being used by this POM, namely 2.6.1, is prone to
fail during
Jason van Zyl wrote:
We can give you access.
Well,
http://svn.sonatype.org/m2eclipse/sandbox/trunk/maven-performance-tests/
is already public.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Olivier Lamy, Arnaud
Héritier
+1 (non-binding): Paul Benedict, Stephen Connolly
I will promote the artifacts to the central repository and continue with
the release. Thanks for all
Hi,
this is the first release of the plugin testing harness branch for usage
with Maven 3.0.
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11740version=15444
There are still a couple of issues left in JIRA:
Sebastian Annies wrote:
Has anyone of you experienced similar behavior or is intended to work
that way?
Maybe there's some bad interaction with the default versions in the
super POM, I'll have a closer look.
Benjamin
-
The Maven team is pleased to announce the release of Apache Maven
3.0-alpha-4.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of
Sebastian Annies wrote:
we are using a custom lifecycle and bind the maven-source-plugin in
version 2.1 to the verify phase. In the 2.X branch it always worked
perfectly. But now I tried alpha-3 and 4 and it seems that Maven uses
the maven-source-plugin in version 2.0.4
Confirmed and filled
Brian Fox wrote:
Second, I always subscribe to the theory that closest wins.
[...] I think in this case, the pom is
closer than the lifecycle and therefore it should win as is
happening in the 3.x case.
I agree, it's simply a matter of giving the build engineer control over
his build.
Gilles Scokart wrote:
Are you publishing this to an apache maven repository or did you publish it
directly into central?
I see it at
https://repository.apache.org/content/repositories/releases/org/apache/maven/apache-maven/3.0-alpha-4/
as found by
Mark Hobson done:
The Maven Checkstyle Plugin has been released.
Can this get added to the next board report please.
Done.
For the future, please remember to cc the result to the PMC as well (cf.
step 9 of the [0]).
Benjamin
[0]
Brian Fox wrote:
1) we included some plugins that are commonly used but aren't in a
lifecycle such as the dependency and enforcer plugins.
I know, if those are declared in the POM they have to have/inherit a
version or Maven 3.0 will output a warning.
In other words, what we consider
Brian Fox wrote:
I guess what I had in mind was given a single reactor build:
A : Jar
B: War but binds jar to a phase.
Will B always get the same version of the jar plugin as A?
No, the projects are handled independently regarding their build plugins.
For instance, if B doesn't lock down
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Olivier Lamy, Arnaud
Héritier
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 Plugin
Testing, version 2.0-alpha-1.
This harness assists in creating unit or integration tests for Maven
plugins. See the component's site for more details:
http://maven.apache.org/plugin-testing/
This new version of the
Brian Fox wrote:
What is the behavior in an embedded env like M2e? Since it's not going
to execute the full lifecycle, it probably needs to have the same
logic regardless to look at the lifecycle and pick the right version
of a plugin it does run.
Not sure I understand that question.
Dennis Lundberg wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-012/
Staging site:
http://maven.apache.org/plugins/maven-changes-plugin-2.2/
+1
Benjamin
-
To unsubscribe, e-mail:
Dennis Lundberg wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-013/
Staging site:
http://maven.apache.org/plugins/maven-jar-plugin-2.3/
+1
Benjamin
-
To unsubscribe, e-mail:
Dennis Lundberg wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-014/
Staging site:
http://maven.apache.org/shared/maven-doxia-tools-1.1/
+1
Benjamin
-
To unsubscribe, e-mail:
Hi,
We solved 7 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11540version=15525
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=11540status=1
Staging repo:
Larry Shatzer, Jr. wrote:
I attached a patch (with a test too!) for MSHADE-52, and would love
that to get included
Sorry, not in this release.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
Hi,
We solved some more issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500version=14952
There are still a couple of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truepid=10500status=1
Staging repo:
Jorg Heymans wrote:
[ERROR] The project build-tools:1-SNAPSHOT
(D:\src\myproject\pom.xml) has 1 error
[ERROR]
'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: junit:junit:jar - duplicate declaration of version
3.8.2
Shall i log an issue
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,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Vincent Siveton, Jason van Zyl, Olivier
Lamy
+1 (non-binding): Mark Struberg, 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 Shade
Plugin, version 1.2.2.
This plugin provides the capability to package the artifact in an
uber-jar, including its dependencies and to shade - i.e. rename - the
packages of some of the dependencies. See the plugin's site for
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Arnaud Héritier, Olivier
Lamy
+1 (non-binding): Nicolas De Loof, Stephen Connolly, Igor Fedorenko
I will promote the artifacts to the central repository and continue with
the release
The Maven team is pleased to announce the release of Apache Maven
3.0-alpha-5.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of
Paul Gier wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-033/
+1
Staging site (need to sync):
http://maven.apache.org/ant-tasks-2.1.0/
Some minor things. The installation [0] page still refers to version
2.0.10 and the mailing list overview [1] is
nicolas de loof wrote:
I'm using maven3-alpha-5 and get a deploy:deploy error on
people.apache.org (maybe related to MNG-4241 ?)
[INFO] [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-deploy-plugin:2.4:deploy (default-deploy) on
project fonzie: Error deploying artifact:
nicolas de loof wrote:
Maven 2.2.1 deploys fine with same POM
Then please fill an issue with a demo project.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
Dennis Lundberg wrote:
This vote comes soon after the 2.2 release
No need to apologize ;-)
Staging repo:
https://repository.apache.org/content/repositories/maven-036/
The .pom.asc seems not to match the plugin POM [0]. Looking at the POM,
it seems as if it was deployed using Maven 2.1.0
Paul Gier wrote:
The Maven Ant Tasks 2.1.0 have been released.
Can this be added to the next board report please?
Done.
Benjamin
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail:
Stevo Slavić wrote:
It seems 3.0-alpha-5 is not compatible with current 2.0-alpha-4 version of
maven-archetype-plugin - archetype:create-from-project mojo creates
archetype project with packaging maven-archetype, but that packaging seems
not to be supported by / valid for 3.0-alpha-5
Try
Dennis Lundberg wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-042/
Staging site:
http://maven.apache.org/plugins/maven-changes-plugin-2.3/
+1
Benjamin
-
To unsubscribe, e-mail:
Donszelmann Mark wrote:
Is it correct that it compiles and tests fine without ever running into the install phase... That is, maven
probably sorts out that B is dependent on A, and thus in this multi-module project:
1. B does not download A,
2. B just refers to module A.
In principle yes,
Dennis Lundberg wrote:
The plugin-plugin should be updated to version 2.5.1, to fix the
problems with deprecated annotations.
Good catch, the reporting was declared to use an older version. I will
deploy the final site using 2.5.1.
Benjamin
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
Vincent Siveton wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-044
Staging site (need to sync)
http://maven.apache.org/plugins/maven-pdf-plugin-1.1/
+1
Benjamin
-
To unsubscribe, e-mail:
Dennis Lundberg wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-045/
Staging site:
http://maven.apache.org/shared/maven-doxia-tools-1.2/
+1
Benjamin
-
To unsubscribe, e-mail:
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
601 - 700 of 1109 matches
Mail list logo
