We are pleased to announce the Maven Site Plugin 1.7.1 release!
http://maven.apache.org/maven-1.x/plugins/site/
Generate web site.
===
Changes in this version include:
Fixed bugs:
o Update files modes on the remot
We are pleased to announce the Maven Source Control Management Plugin 1.6.1
release!
http://maven.apache.org/maven-1.x/plugins/scm/
A plugin for SCM tasks.
===
Changes in this version include:
Fixed bugs:
o The p
We are pleased to announce the Maven PMD Plugin 1.10 release!
http://maven.apache.org/maven-1.x/plugins/pmd/
The Maven PMD plugin is a plugin that wraps the PMD framework
(http://pmd.sourceforge.net). PMD is a source checking framework that works by
scanning Java source code and looks for pote
We are pleased to announce the Maven PDF Plugin 2.5.1 release!
http://maven.apache.org/maven-1.x/plugins/pdf/
PDF Documentation generator
===
Changes in this version include:
Fixed bugs:
o Unable to remove cover t
We are pleased to announce the Maven JDiff Plugin 1.5.1 release!
http://maven.apache.org/maven-1.x/plugins/jdiff/
Plugin for JDiff - reports on the differences in the public API of two
releases by comparing the sources of two SCM checkouts.
We are pleased to announce the Maven Clover Plugin 1.11.2 release!
http://maven.apache.org/maven-1.x/plugins/clover/
The Clover plugin allows measuring test coverage using Clover
(http://www.cenqua.com/clover).
===
C
opensymphony Quartz scheduler exists on repo1.maven.org in both :
http://repo1.maven.org/maven2/quartz/quartz/
and
http://repo1.maven.org/maven2/opensymphony/quartz/
"opensymphony" groupId contains the latest 1.6.0, so it looks to be the
expected groupId, but this one has no POM ( migrate from
On 29/03/2007, at 4:13 PM, Stephane Nicoll wrote:
IMO, we really need the assembly release. It's been way too long and
it's beta. Can't we fix those things for beta-2?
If John's fixed the bug I filed, then I'm happy (was just waiting for
the new build to be announced so I could test it...)
On 3/29/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Agreed, in addition to making it easy to lock down your lifecycle
plugin versions. I wonder if I ever sent that proposal out for 2.1...
We just need to manage this as best we can (keep compat on x.y
versions, and separate unstable repo as I pos
Right! Sorry for the delay. It turns out I didnt have an account here
associated with my email address and thus I never got your response - no
matter.
1. Simply put, JAX-B is very limited in how much of the XML Schema it
actually understands (or is willing to bind). JAX-B also uses its own
annota
>Good point, but shouldn't that stable functionality be in the
>previous release, which folks should still be using in production
>until they need to upgrade?
In this case, yes because the stable goals have not changed at all (and
this is where pluginMgt comes in). However if the repos are sp
On 29/03/2007, at 1:03 PM, Brian E. Fox wrote:
Brett,
I can see some logic to this as it's just another shade of grey
between
the current snapshot repo and central. It does however feel a little
like a hack to work around some version ranging issues. I think
massembly is a good example of wh
Brett,
I can see some logic to this as it's just another shade of grey between
the current snapshot repo and central. It does however feel a little
like a hack to work around some version ranging issues. I think
massembly is a good example of where this is needed, but perhaps mdep is
a case where i
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (25 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-1449Unitils provides utilities to further simplify unit-testing
with JUnit, DBUnit, EasyMock, Hibernate and Spring.
http://jira.codehaus.org/br
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (39 issues)
Subscriber: mavendevlist
Key Summary
MEV-511 org.apache.struts:struts2-tiles-plugin:2.0.6 contains a SNAPSHOT
deps
http://jira.codehaus.org/browse/MEV-511
MEV-504 Jetty 5.1.10 and 5.
Agreed, in addition to making it easy to lock down your lifecycle
plugin versions. I wonder if I ever sent that proposal out for 2.1...
We just need to manage this as best we can (keep compat on x.y
versions, and separate unstable repo as I posted elsewhere).
- Brett
On 29/03/2007, at 11:5
This is a general problem with the magical RELEASE version that
plugins use... IMO this is an anti-feature and should be removed in
general and force people to configure the plugin's version to help
ensure that future releases of plugins don't break their builds.
--jason
On Mar 28, 2007,
The real problem here is that as long as there are tags out there that don't
specify plugin versions, we have no mechanism for deprecating or breaking
api compat, regardless of the version (2.0 -> 2.1 -> 2.2 -> 99.0).
-j
On 3/28/07, John Casey <[EMAIL PROTECTED]> wrote:
MASSEMBLY-192 is fixed
MASSEMBLY-192 is fixed in trunk, and I'm just about to apply it to the
tag...then we could roll another candidate, though I do want to resolve
Max's issue above as well.
Max: I'm tempted to say that we should look for decimal versions of common
octal expressions, then prefix the rest with '0' to
Flagged, since I have on my list to review how assembly ITs do their
thang.
Might take me up to a week :)
- Brett
On 29/03/2007, at 11:43 AM, John Casey (JIRA) wrote:
[ http://jira.codehaus.org/browse/MASSEMBLY-192?
page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hi,
I didn't want to pin the assembly plugin vote to this, but it seemed
like a good opportunity to bring this up.
I'd like to propose we split the stable repository from the unstable
repository (which would be where alphas, betas and rcs get deployed),
and make this a documented best pra
half here, half in felix-dev
I have made some improvements to Felix bundle plugin for manifest
generation that you can see here
https://issues.apache.org/jira/browse/FELIX-199
once that it's applied and hopefully released we'll give a try with
our own maven artifacts
On 3/28/07, Nathan Beyer <
-1
But it got really close :)
Unfortunately, I found a regression, though it looks a simple one to
fix: http://jira.codehaus.org/browse/MASSEMBLY-192
I'm continuing my testing past this to see if there are any other
issues, though it looks fine.
- Brett
On 29/03/2007, at 2:59 AM, John C
On 3/28/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
I'm working with the Felix guys to go through all these issues. As
usual Maven would provide a default manifest that you could override
with configuration in your pom.
Where is this conversation happening? I'd like to hear more about the det
John Casey wrote:
> Hi everyone,
>
> I wanted to call a vote to release a beta version of the new assembly
> plugin.
...
> Road Map:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126&styleName=Html&version=12617
>
> Tag:
> http://svn.apache.org/repos/asf/maven/plugins/tags/maven-
I'm working with the Felix guys to go through all these issues. As
usual Maven would provide a default manifest that you could override
with configuration in your pom.
On 3/28/07, Nathan Beyer <[EMAIL PROTECTED]> wrote:
On 3/28/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
> We're just trying t
On 3/28/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
We're just trying to help out the OSGi folks so that they aren't
repackaging everything which is what they are doing. It's basically
doing the minimum work so that JARs produced will function with OSGi
containers. If it has no impact on normal
I can't say that I care much one way or another, when it comes to moving all
doco from the codehaus wiki to cwiki or leaving it as-is...provided the
conversion is 100% successful, and cwiki is stable. The stability point is a
concern for me, since I've seen some pretty ugly messes with ASF infra i
(moving to main dev list as scope has increased)
On 29/03/2007, at 12:28 AM, Jason van Zyl wrote:
On 28 Mar 07, at 9:03 AM 28 Mar 07, Brett Porter wrote:
On 28/03/2007, at 10:35 PM, Jason van Zyl wrote:
No, please don't fragment even more our documentation situation.
We have the stuff
ok, I redid the release using the parent version of 7 so if its ok
with folks I would like to just keep this vote ongoing...the only
difference is the 8->7 in the parent version
I republished the artifacts to the same directory and smoked the old
ones, thanks for noticing that dennis
jesse
On 3
ping PMCs
Thx
Arnaud
On 26/03/07, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
Hi,
I think that it is the time to release the modello plugin for maven 1.xin
version
1.0.
This plugin allows to use modello (1.0-alpha-15) inside a maven 1.xbuild and
is used to create our maven-model classes
James,
This is definitely something that would be better put in the maven
repository as an eventual official Maven plugin. My suggestion would
be to create a new directory in the maven plugins sandbox: (all apache
committers have access)
https://svn.apache.org/repos/asf/maven/sandbox/trunk/p
+1
LOTS of us have been waiting for this one.
Thanks!
Dan
On Wednesday 28 March 2007 12:59, John Casey wrote:
> Hi everyone,
>
> I wanted to call a vote to release a beta version of the new assembly
> plugin. There are still some outstanding issues (though not as many as
> jira would have you
On 28 Mar 07, at 11:32 AM 28 Mar 07, Rollo, Dan wrote:
Any plans to also release an update to maven2 ant tasks and/or
embedder
in this go 'round?
Yes, I realized a snapshot and already posted about releasing them
after the 2.0.6 release.
They are sitting here:
http://idisk.maven.org/jv
On 3/28/07, John Casey <[EMAIL PROTECTED]> wrote:
Hi everyone,
I wanted to call a vote to release a beta version of the new assembly
plugin. There are still some outstanding issues (though not as many as jira
would have you believe; they just need tests), but I think we're at around
95-99% backw
oh oh, I see, that was the old artifact name...nevermind on the parent
part then, I'll fix that up and point it to 7 then
jesse
On 3/28/07, Jesse McConnell <[EMAIL PROTECTED]> wrote:
has that been pushed out anywhere?
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/maven/shared/shared
has that been pushed out anywhere?
http://mirrors.ibiblio.org/pub/mirrors/maven2/org/apache/maven/shared/shared-components-parent/
I only see up to 2 there...
On 3/28/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Jesse McConnell wrote:
> As part of the prepwork for getting an actual continuum
+1
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 28, 2007 12:59 PM
To: Maven Developers List
Subject: [vote] Release 2.2-beta-1 of maven-assembly-plugin
Hi everyone,
I wanted to call a vote to release a beta version of the new assembly
plugin. The
Jesse McConnell wrote:
As part of the prepwork for getting an actual continuum alpha release
out I need to get a few more dependencies released, one of them is the
maven-app-configuration. And since the currently released parent
version is out of date with regards to the new release setup I have
+1 (a little late)
- Joakim
Jason van Zyl wrote:
> Hi,
>
> The roadmap is here:
>
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10500&fixfor=13010
>
>
> The tag is here:
>
> http://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.6/
>
> Staging repository:
>
> http:
The fact that install / deploy process maintains the filename with a
version in it is simple.
The repository is to be thought of as a database.
The local repository is to be thought of as a remote repository cache.
The repository database *needs* versioning.
The plugins that bundle the artifacts
+1
- Joakim
Jesse McConnell wrote:
> As part of the prepwork for getting an actual continuum alpha release
> out I need to get a few more dependencies released, one of them is the
> maven-app-configuration. And since the currently released parent
> version is out of date with regards to the new
I've moved the closed issues out of the 2.2 version in JIRA, into a separate
2.2-beta-1 version:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126&styleName=Html&version=13338
On 3/28/07, Richard van der Hoff <[EMAIL PROTECTED]> wrote:
Yes! Please! Oh god, yes
John Casey wr
Yes! Please! Oh god, yes
John Casey wrote:
Hi everyone,
I wanted to call a vote to release a beta version of the new assembly
plugin. There are still some outstanding issues (though not as many as jira
would have you believe; they just need tests), but I think we're at around
95-99% backwar
+1
We're using the SNAPSHOT locally for many weeks now and all goes well.
Thanks,
Stéphane
On 3/28/07, John Casey <[EMAIL PROTECTED]> wrote:
Hi everyone,
I wanted to call a vote to release a beta version of the new assembly
plugin. There are still some outstanding issues (though not as many a
+1
On 3/28/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
+1
Emmanuel
Jesse McConnell a écrit :
> As part of the prepwork for getting an actual continuum alpha release
> out I need to get a few more dependencies released, one of them is the
> maven-app-configuration. And since the currently
Hi everyone,
I wanted to call a vote to release a beta version of the new assembly
plugin. There are still some outstanding issues (though not as many as jira
would have you believe; they just need tests), but I think we're at around
95-99% backward compatibility and the new features seem to be w
as soon as https://issues.apache.org/jira/browse/FELIX-199 gets
applied anybody can add the "manifest" goal and get the OSGi manifest
in the jar.
On 3/28/07, Damien Lecan <[EMAIL PROTECTED]> wrote:
2007/3/28, Carlos Sanchez <[EMAIL PROTECTED]>:
> > It would be great if that could be available in
2007/3/28, Carlos Sanchez <[EMAIL PROTECTED]>:
> It would be great if that could be available in 2.0.x version of
> Maven. We are too far from 2.1 version.
you will always have the option to add a plugin to your pom that will
generate the OSGi manifest (the maven-bundle-plugin from Apache
Felix).
On 3/28/07, Damien Lecan <[EMAIL PROTECTED]> wrote:
> > How this will be done ?
> At first by putting an innocuous plugin in the lifecycle, or in 2.1
> with extensions in Plexus it will be an extension to the JAR plugin
> that populates manifest information.
It would be great if that could be av
Any plans to also release an update to maven2 ant tasks and/or embedder
in this go 'round?
If not, any idea how/when these might be updated?
Last I saw, the embedder was basically dead until 2.1 is released, and
I'm wondering if the ant dep tasks are in the same boat.
Thanks,
Dan
-Original
i used the findbugs-maven-plugin in 1.0.0.
i have uploaded my findbugs xml result file.
http://www.nabble.com/file/7482/findbugs.xml findbugs.xml
but it will be great if findbugs (not the maven plugin ) can read his own
analysis result file and that we can
navigate in with the findbugs API
On 28 Mar 07, at 9:27 AM 28 Mar 07, Kaloyan Enimanev wrote:
On 3/28/07, Damien Lecan <[EMAIL PROTECTED]> wrote:
> > How this will be done ?
> At first by putting an innocuous plugin in the lifecycle, or in 2.1
> with extensions in Plexus it will be an extension to the JAR plugin
> that populat
On 28 Mar 07, at 9:11 AM 28 Mar 07, Brett Porter wrote:
Jason,
Can you set up the released versions for these before moving more
issues so that affects versions, etc are retained?
I think most of those are so unmaintained it doesn't matter. I'll be
going through them, as they are only 40
On 28 Mar 07, at 9:03 AM 28 Mar 07, Brett Porter wrote:
On 28/03/2007, at 10:35 PM, Jason van Zyl wrote:
No, please don't fragment even more our documentation situation.
We have the stuff in SVN, Confluence users spaces and developer
works spaces. The autoexport could easily be setup wi
On 28 Mar 07, at 9:15 AM 28 Mar 07, Damien Lecan wrote:
> How this will be done ?
At first by putting an innocuous plugin in the lifecycle, or in 2.1
with extensions in Plexus it will be an extension to the JAR plugin
that populates manifest information.
It would be great if that could be ava
Hi Milos
I was just expressing an opinion :)
I'm not part of the Maven team.
best regards,
Kaloyan
On 3/28/07, Milos Kleint <[EMAIL PROTECTED]> wrote:
if I understood correctly, OSGI bundles should have a special
packaging like ear/wars do and define it's lifecycle to include the
OSGI stuff i
if I understood correctly, OSGI bundles should have a special
packaging like ear/wars do and define it's lifecycle to include the
OSGI stuff in the resulting binary
Milos
On 3/28/07, Damien Lecan <[EMAIL PROTECTED]> wrote:
> > Ok I understand, but you didn't answer my (not clear) question : if
> Ok I understand, but you didn't answer my (not clear) question : if
> OSGi packaging is fast enough, will OSGi manifest entries be
> transparently added to every maven-build jars ?
>
> Or will it be an OSGi developer option, that will never be known and
> used by other common people ?
IMHO this
Which version of the Findbugs plugin are you using?
Are you able to send me the findbugs.xml file?
--
Regards,
Garvin LeClaire
[EMAIL PROTECTED]
On 3/28/07, dvicente <[EMAIL PROTECTED]> wrote:
Hi,
for my dashboard-maven-plugin, i want to parse the xml result file of
findbugs.
Does a
On 3/28/07, Damien Lecan <[EMAIL PROTECTED]> wrote:
> > How this will be done ?
> At first by putting an innocuous plugin in the lifecycle, or in 2.1
> with extensions in Plexus it will be an extension to the JAR plugin
> that populates manifest information.
It would be great if that could be av
> How this will be done ?
At first by putting an innocuous plugin in the lifecycle, or in 2.1
with extensions in Plexus it will be an extension to the JAR plugin
that populates manifest information.
It would be great if that could be available in 2.0.x version of
Maven. We are too far from 2.1 v
Brett Porter a écrit :
On 28/03/2007, at 10:35 PM, Jason van Zyl wrote:
No, please don't fragment even more our documentation situation. We
have the stuff in SVN, Confluence users spaces and developer works
spaces. The autoexport could easily be setup with the space we have if
it isn't a
Hi,
I'm planning on releasing the Ant Tasks after the release of 2.0.6 so
if you have any issues please look here:
http://jira.codehaus.org/browse/MANTTASKS
I've moved all the issues from MNG to MANTTASKS and if there's
anything folks really want I will schedule a couple things for
alpha
Jason,
Can you set up the released versions for these before moving more
issues so that affects versions, etc are retained? I only see 1.0-
alpha-1 in there at the moment, and it doesn't make much sense to go
backwards.
I've adjusted the project configuration to be standard maven style
(
On 28/03/2007, at 10:35 PM, Jason van Zyl wrote:
No, please don't fragment even more our documentation situation. We
have the stuff in SVN, Confluence users spaces and developer works
spaces. The autoexport could easily be setup with the space we have
if it isn't already.
This document
On 27 Mar 07, at 9:50 PM 27 Mar 07, Brett Porter wrote:
On 28/03/2007, at 2:37 AM, Emmanuel Venisse wrote:
- should we move the SCM space to cwiki since it can be
autoexported? Then we can put the provider matrix and the provider
details pages together and link them in to the site as stat
On 28 Mar 07, at 4:02 AM 28 Mar 07, Damien Lecan wrote:
Hello,
[...]
it is entirely non-invasive then I
think it would be fine to add to the default lifecycle.
How this will be done ?
At first by putting an innocuous plugin in the lifecycle, or in 2.1
with extensions in Plexus it will
Hi,
for my dashboard-maven-plugin, i want to parse the xml result file of
findbugs.
Does anyone know if exist a parser in the API to retreive all objects
structure without to parse the file as a simple xml file ?
the findbugs-maven-plugin generate xml file in wrong format .
it generates messag
Hi all,
I just searched the topic and found that if we put our plugin in
org.apache.maven.plugins, = groupdID, the plugin should run and as per the
previous discussion it worked for the topic starter BUT, i tried the same
and still getting the error!! :(
Any solution please..
C:\mp\test\sample
Brett Porter a écrit :
I think it's definitely time for another beta ASAP.
For 1.0, I'd still like to review (if not include) the following JIRAs.
High priority:
- SCM-17: I think the test structure needs some review, and we need to
ensure all unit tests run fast and without the software ins
Hello,
[...]
it is entirely non-invasive then I
think it would be fine to add to the default lifecycle.
How this will be done ?
Does "bundle" packaging will become official, or will it supercede
default jar packaging ?
Will it be active by default ?
Thank you for this great job !
Damien Lec
72 matches
Mail list logo
