I just saw you resolved MCHANGES-96 and MCHANGES-97 - great :)
I just had a quick look at MCHANGES-78 - the patch supplied is for a
whole new plugin (called svnchangelog-maven-plugin), rather than
modifications for maven-changes-plugin, it has no ASF source file
headers, "org.apache.codehaus" pack
On Feb 5, 2008 11:20 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> I have four issues left on my radar, that I'd like to solve or reject
> before doing the next release:
>
> MCHANGES-78 Build a changes report by parsing svn comments
> - Patch supplied, evaluate whether to include or not
>
> MCHA
Dumb question (possibly): what does the @aggregator annotation do,
exactly?
I read the doc here:
http://maven.apache.org/developers/mojo-api-specification.html
It says: "Flags this Mojo to run it in a multi module way, i.e. aggregate
the build with the set of projects listed as modules."
B
I have four issues left on my radar, that I'd like to solve or reject
before doing the next release:
MCHANGES-78 Build a changes report by parsing svn comments
- Patch supplied, evaluate whether to include or not
MCHANGES-88 NoSuchMethodError with maven 2.0.8 when generating
changes-report
-
This looks very exciting, and agree with most of the thread that
follows. I'm just going to reply in summary - most of my thoughts are
actually non-technical :)
Regarding databases: I don't think xml files are the solution (except
for the configuration where it makes a lot more sense :) - t
+1
On Feb 5, 2008 5:06 PM, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Below is the current proposal for the Continuum TLP.
> Please vote on whether to make this proposal a formal request to the Maven
> PMC to apply for graduation.
>
> [ ] +1
> [ ] 0
> [ ] -1
>
> Cheers,
> Emmanuel
>
>
Hi,
Below is the current proposal for the Continuum TLP.
Please vote on whether to make this proposal a formal request to the Maven
PMC to apply for graduation.
[ ] +1
[ ] 0
[ ] -1
Cheers,
Emmanuel
Establish the Apache Continuum Project
WHEREAS, the Board of Directors deems it to be in the be
Is there any chance of a Changes Plugin release? I'd like to use the
JIRA report improvements that have been fixed in the following:
https://jira.codehaus.org/browse/MCHANGES-92
https://jira.codehaus.org/browse/MCHANGES-94
There are currently 21 outstanding issues: http://tinyurl.com/yvkola
If s
On 06/02/2008, at 8:05 AM, Dan Fabulich wrote:
In Surefire 2.4, we stopped having surefire-booter depend directly
on plexus-archiver. We did that partly to workaround MSHADE-9 and
partly to simply reduce the number of dependencies in surefire-
booter (which unfortunately has to be in the
In Surefire 2.4, we stopped having surefire-booter depend directly on
plexus-archiver. We did that partly to workaround MSHADE-9 and partly to
simply reduce the number of dependencies in surefire-booter (which
unfortunately has to be in the classpath of the launched tests).
Our dependency o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
it seems I get ignored with this toppic on all channels.
I will try to create a JIRA issue, maybe that gets read one day...
Regards
Jörg
> Hello everybody,
>
> I posted to the users list but got no answer.
> Further I think of a deeper integr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi again,
I wrote:
> I would prefer that if maven builds a plugin that has no goal "help" already,
> then it auto-generates one in about the same way as it does
> when generating the goal-documentation for the site. Then each plugin
> would have (in f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
>>> Finding the definitive help information for a plugin should be
>>> absolutely trivial and built-in; having the CLI option which give the
>>> code-you-are-executing-right-now the ability to answer that question
>>> avoids the issues we have toda
Sorry for the delayed response -- have you resolved this yet? Whenever I
fixed this issue I was planning on using the generateReleasePoms feature but
never got around to it...
Looks like SCM-341 is the only pending issue for a 1.1 release of SCM... is
there a timeline on this?
Patrick
On Jan
Vote passed.
+1 binding: Dan Fabulich, Arnaud Heritier, Brian Fox, Lukas Theussl
+1 non-binding: Fabrizio Giustina, Nicolas de Loof, Mauro Talevi
-0 non-binding: Dan Tran
I'm going to try to stage this release today (though I'm predicting more
MSTAGE-4 and fix-permissions trouble).
-Dan
---
On 5-Feb-08, at 7:44 AM, Max Bowsher wrote:
Jason van Zyl wrote:
On 4-Feb-08, at 4:20 PM, Dan Fabulich wrote:
Jason van Zyl wrote:
I'm not saying the CLI is a good option. I think it's a bad
option. Keep this out of the core. It's perfectly fine as a plugin.
I'll throw in my two cents an
Jason van Zyl wrote:
On 4-Feb-08, at 4:20 PM, Dan Fabulich wrote:
Jason van Zyl wrote:
I'm not saying the CLI is a good option. I think it's a bad option.
Keep this out of the core. It's perfectly fine as a plugin.
I'll throw in my two cents and point out that while I basically agree
with
Vote passed: +3 (Vincent, Wendy, Lukas)
Cheers,
Vincent
2008/1/29, Vincent Siveton <[EMAIL PROTECTED]>:
> Hi,
>
> Lukas started to adapt the m1 linkcheck tool last year [1] and we
> created a plugin for it [2]. I'd like to move these out of the sandbox
> so we can start to prepare releases for t
Hi,
The original use of this parameter was for this "strange" effect. When i
introduced the new parameter i called it workspaceToConnect because the
parameter workspace was in use.
Arnaud fixed a jira (don't remember the number) that this effect has
nothing to do with the workspace and renamed it
On 05/02/2008, at 6:35 AM, Christian Edward Gruber wrote:
The point is that neither futzing with modues, or hacking
classifiers is sufficient. But associative metadata might just be
the trick.
This is the approach we took with Eclipse Kepler as we mapped out the
repository. We actually
Hello,
setting the workspace parameter to my workspace has a strange side-effect :
my eclipse .project files are not created in my project folder, but in my
eclipse workspace directory. I like the idea to automagically detect
available projects in my eclipse (MECLIPSE-344) but I prefer to have th
2008/2/5, Brett Porter <[EMAIL PROTECTED]>:
>
> On 05/02/2008, at 8:50 PM, Tomasz Pik wrote:
>
> > On Feb 5, 2008 9:03 AM, Raphaël Piéroni <[EMAIL PROTECTED]>
> > wrote:
> >> The main list is the internal catalog.
> >> It is also possible to define a specific catalog
> >> by -DarchetypeCatalog=http
I started to scratch a plexus component that do this kind of work.
Raphaël
2008/2/5, Tomasz Pik <[EMAIL PROTECTED]>:
> On Feb 5, 2008 9:03 AM, Raphaël Piéroni <[EMAIL PROTECTED]> wrote:
> > The main list is the internal catalog.
> > It is also possible to define a specific catalog
> > by -Darchet
On 05/02/2008, at 9:31 PM, Tomasz Pik wrote:
But where? :)
As an issue for archetypes: "Should archetype catalog reside at the
group
level, to be consistent with the plugin metadata?"
Or as an issue for archiva: "archiva should be able to merge
archetype catalogs
as they are defined curre
On Feb 5, 2008 11:14 AM, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> On 05/02/2008, at 8:50 PM, Tomasz Pik wrote:
>
> > On Feb 5, 2008 9:03 AM, Raphaël Piéroni <[EMAIL PROTECTED]>
> > wrote:
> >> The main list is the internal catalog.
> >> It is also possible to define a specific catalog
> >> by -D
On 05/02/2008, at 8:50 PM, Tomasz Pik wrote:
On Feb 5, 2008 9:03 AM, Raphaël Piéroni <[EMAIL PROTECTED]>
wrote:
The main list is the internal catalog.
It is also possible to define a specific catalog
by -DarchetypeCatalog=http://repo.company.com/maven2 the catalog
is an xml file located at th
On Feb 5, 2008 9:03 AM, Raphaël Piéroni <[EMAIL PROTECTED]> wrote:
> The main list is the internal catalog.
> It is also possible to define a specific catalog
> by -DarchetypeCatalog=http://repo.company.com/maven2 the catalog
> is an xml file located at the root and called archetype-catalog.xml.
P
Yes, that's the idea of a "vitrual" repository URL to acces a set ("group")
of managed repositories.
For my personnal use case I also have to look at the Dav server
implementation to add support for Windows UNC file path.
Nico.
2008/2/5, Maria Odea Ching <[EMAIL PROTECTED]>:
>
> Hi Nicolas,
>
>
The main list is the internal catalog.
It is also possible to define a specific catalog
by -DarchetypeCatalog=http://repo.company.com/maven2 the catalog
is an xml file located at the root and called archetype-catalog.xml.
The process that populates a catalog during deploy. is not currently working
29 matches
Mail list logo