Hi,
IMHO, this can't be "automatic" because CONTINUUM-774 has been fixed.
If you use this option this means you don't want to checkout child modules as a
separate project even if it's a new module.
A parameter could be add (at the project level) to say something
"automaticAddChildModules" or an o
Hi,
Just try last continuum snapshot [1].
Now it's possible to define profile with particular jdk, mvn, maven1, ant
and/or env var.
--
Olivier
[1] http://maven.zones.apache.org/~continuum/builds/trunk/?M=D
-Message d'origine-
De : news [mailto:[EMAIL PROTECTED] De la part de Joerg He
Hi All,
I'm trying to fix up http://jira.codehaus.org/browse/CONTINUUM-798,
which is "Modules automatic discovery". I think the patch submitted is
already outdated and there was the issue about recursive modules.
Anyway, below is how I thought to implement the fix for this:
Create an "update
Dear God, I am so happy to hear that. I swear, I wish I had more
time to track this and contribute, but I'm really really impressed by
this whole team and the progression of this product over the last
year or so.
Christian.
On Jul 10, 2007, at 10:42 PM, Jesse McConnell wrote:
just fyi,
just fyi, we are working on getting that profile enabled version
released in the next couple of weeks
jesse
On 7/10/07, Brett Porter <[EMAIL PROTECTED]> wrote:
On 11/07/2007, at 10:32 AM, Joerg Heinicke wrote:
> Hello guys,
>
> we had an issue recently with Continuum on Cocoon and continuous
>
Results:
Binding +3 (Brian, Vincent S., Jason)
Non-Binding +1 Jason D.
I'll proceed with the release.
Thanks,
Brian
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 08, 2007 7:57 PM
To: Maven Developers List
Subject: [Vote] release maven-enforcer-plugin
Results:
Binding +4 (Brian, Arnaud,Vincent, S. Jason)
Non-Binding +1 Andy
I'll proceed with the release.
Thanks,
Brian
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Sunday, July 08, 2007 7:38 PM
To: Maven Developers List
Subject: [VOTE] release maven-plugin-testin
Results:
Binding: +5 (Brian, John, Carlos, Fabrizio, Arnaud)
Non-Binding: +0 Mark, +1 Denis C.
I will proceed with the release.
Thanks,
Brian
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Saturday, July 07, 2007 11:09 PM
To: Maven Developers List
Subject: [VOTE]
Results:
Binding: +5 (Brian, John, Carlos, Fabrizio, Arnaud)
Non-Binding: +1 Mark
I will proceed with the release.
Thanks,
Brian
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Friday, July 06, 2007 11:28 PM
To: Maven Developers List
Subject: [VOTE] release maven-p
On 11/07/2007, at 10:32 AM, Joerg Heinicke wrote:
Hello guys,
we had an issue recently with Continuum on Cocoon and continuous
integration
which fails to check JDK 1.4 compliance of Cocoon's code base since
Continuum
itself is running with a JDK 5 (in that particular case it was
usage of
Hello guys,
we had an issue recently with Continuum on Cocoon and continuous integration
which fails to check JDK 1.4 compliance of Cocoon's code base since Continuum
itself is running with a JDK 5 (in that particular case it was usage of
ThreadLocal.remove() [1]). I found the thread about raising
Yeah that would settle this once and for all ;)
Except you probably have to be able to specify the delimiters per
resource set sigh.
John Casey wrote:
I've seen several unix commands that allow configurable
delimiters...maybe that would be a better option?
-john
On Jul 10, 2007, at 12:5
Max Bowsher wrote:
Kenney Westerhof wrote:
Patrick Schneider wrote:
For now, I'm a fan of disallowing snapshots when they are not
explicitly in
the boundary, as per the patch.
In my mind, the problem with a profile flag is that it's an
all-or-nothing
proposition. Any released artifacts wit
I've seen several unix commands that allow configurable
delimiters...maybe that would be a better option?
-john
On Jul 10, 2007, at 12:55 PM, Kenney Westerhof wrote:
Daniel Kulp wrote:
Personally, I was thinking of just doing $$ -> $.
Yah, that's already in place for plugin parameters.
Kenney Westerhof wrote:
>
>
> Patrick Schneider wrote:
>> For now, I'm a fan of disallowing snapshots when they are not
>> explicitly in
>> the boundary, as per the patch.
>>
>> In my mind, the problem with a profile flag is that it's an
>> all-or-nothing
>> proposition. Any released artifacts w
Patrick Schneider wrote:
For now, I'm a fan of disallowing snapshots when they are not explicitly in
the boundary, as per the patch.
In my mind, the problem with a profile flag is that it's an all-or-nothing
proposition. Any released artifacts with version ranges will also start to
pull in sn
Daniel Kulp wrote:
Personally, I was thinking of just doing $$ -> $.
Yah, that's already in place for plugin parameters.
Thus, if you want ${pom.version} outputted, it would be $${pom.version}.
I think @@ also needs to be done.
Yup.
My original idea was to use both by default but allow
+1
-john
On Jul 7, 2007, at 11:09 PM, Brian E. Fox wrote:
It's been about 5 months since an eclipse plugin release and we have
lots of fixes and a handful of enhancements. The issues detected in
the
last vote (MECLIPSE-295) have been fixed in the currently staged
plugin-testing-tools 1.0-al
Brian E. Fox wrote:
So I propose:
- if -DdownloadSources is specified, download sources and fallback to javadoc,
just as it is now
- if -DdownloadJavaDoc is specified, download javadoc (possibly fallback to
sources)
- if both are specified, download both.
And:
- don't make this a def
Personally, I was thinking of just doing $$ -> $.
Thus, if you want ${pom.version} outputted, it would be $${pom.version}.
I think @@ also needs to be done.
Dan
On Tuesday 10 July 2007 12:05, John Casey wrote:
> Yeah, escaping makes more sense to me, too. IMO it's a bit of a duct-
> tape sol
Yeah, escaping makes more sense to me, too. IMO it's a bit of a duct-
tape solution to say this is only applicable in {archetype,
appserver, other-limited-effect-plugins...} when those are the
examples given... People can use filtering for just about anything,
and they may use the '${...}' f
Result
+1: 3
On 7/9/07, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
+1
Arnaud
On 09/07/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> fixed in the java classes, the pom missing license is due to the
> release plugin changes
>
> On 7/9/07, Vincent Siveton <[EMAIL PROTECTED]> wrote:
> > +1
> >
>
+1
On Jul 6, 2007, at 11:27 PM, Brian E. Fox wrote:
The plugin testing tools had a bug that caused the real build
artifacts
to become corrupted with the IT test version. This release is required
for the eclipse-plugin 2.4 release.
Issues fixed:
MNG-3095 : maven-plugin-testing-tools causes b
Hi all,
I have a unit test which has to behave differently based on if the
test is being run normally or if the test is running within mvn with
the -o (offline switch) option.
With mvn 2.0.4, I could look at the environment variables being set
(QUOTED_ARGS for linux and MVN_CMD_LINE_ARGS for win
Yeah, I had the same problem today trying to install it.
We need some integration tests on this functionality.
- Brett
On 10/07/2007, at 1:18 PM, Wendy Smoak wrote:
From http://maven.apache.org/archiva/guides/configuration.html :
"When Archiva saves it's configuration, all configuration is s
It's not just archetype - this has come up in appserver too, where
you need some properties in a file escaped and others left.
I suspect adding escape handling to the InterpolationFilterReader
might be a good way to go.
Andy
On 10 Jul 2007, at 11:35, Kenney Westerhof wrote:
Daniel Kulp w
Hi Fabrice,
This is definitely not the intended behaviour - sounds like a bug.
FWIW, I've successfully built sites in this fashion before - so
perhaps you could expand on how you do this (perhaps a sample project?).
Thanks,
Brett
On 07/07/2007, at 1:05 AM, Fabrice Bellingard wrote:
Hi g
>So I propose:
>- if -DdownloadSources is specified, download sources and fallback to javadoc,
>just as it is now
>- if -DdownloadJavaDoc is specified, download javadoc (possibly fallback to
>sources)
>- if both are specified, download both.
>And:
>- don't make this a default; the default beh
What about choosing the sources of property whose be filtering? So we
can have an way to escape properties
For example, in the pom.xml:
MavenProject
pom.version
Jochen Kuhnle wrote:
Hi,
currently, Maven does not require declaration of properties used in
the pom, you just use them anywhere you like. Usually, if a property
is missing, bad things tend to happen because it is replaced with the
string "null". On a good day, resources from "translations-
Ok, if you really need both sources and javadoc then that should
be possible. I never heard of the shift-f2 but indeed it doesn't work here.
I either use the tooltip when I hover over an element and possibly f2 for focus,
or open the javadoc view which displays the javadoc as soon as I select any
Daniel Kulp wrote:
On Monday 09 July 2007 19:08, Kenney Westerhof wrote:
Daniel Kulp wrote:
On Monday 09 July 2007 14:42, Kenney Westerhof wrote:
Daniel Kulp wrote:
Yep. That's the #1 issue.I've completely given up on trying to
get the string "${pom.version}" outputted into the file.
Ohh.. ok then, thanks for the clarification :-)
Arnaud HERITIER wrote:
Thats right but it's normal ;-)
Those classes are genarated and we generate them in 2 packages
(org.apache.maven.model and org.apache.maven.project) to keep a
backward compatibility with m1.0
Arnaud
On 10/07/07, Maria Odea
Hi,
I am new to maven and have been trying to create an example mojo.
Everything works fine. I can build the site and add documentation.
However, when I try automate the creation of xdoc html in my pom file, I
start to get errors. If I then remove the plugin details added for the
generation of t
+1
fabrizio
On 7/8/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
It's been about 5 months since an eclipse plugin release and we have
lots of fixes and a handful of enhancements. The issues detected in the
last vote (MECLIPSE-295) have been fixed in the currently staged
plugin-testing-tools 1.0-al
35 matches
Mail list logo
