Jason,
I don't entirely agree with all your points below, but agree with the
move out of the super POM by a final 2.1 release so don't feel the
need to go into it any further.
Just two questions remain unanswered:
- are the changes written down anywhere? As I said, I can't find the
page i
On 29 Oct 07, at 10:30 PM 29 Oct 07, Kevin Jackson wrote:
I'm also interested in organising a Maven project BOF at each. Any
thoughts?
Could we discuss a way to allow the parser to include xml fragments to
prevent duplicate xml? AFAIK the problem is with the plexus XML
parser that doesn't su
On 29 Oct 07, at 10:42 PM 29 Oct 07, Wendy Smoak wrote:
On 10/29/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I doubt that given my visitation of production environments. But that
said the portion from our own POM provides the same functionality, or
it would even be preferable in subsequent v
I'll be at ApacheCon.
Ralph
Brett Porter wrote:
I know several folks are presenting and will definitely be there, but
I thought it might be good to send a shout out and see who is coming
along? Hopefully we'll get some opportunities for getting together
around the hackathon/code-a-ramas.
I'
I think you're looking for the surefire skip parameter - but this
question belongs on the [EMAIL PROTECTED] list. Please reply
there if necessary.
Thanks,
Brett
On 30/10/2007, at 2:48 PM, Kalyan Akella wrote:
Hi,
Recently, I developed a Java-based maven plugin intended to run in
the tes
Hello,
I have an issue, in that you can specify an id of 'default' for a
profile and that profile is automatically and always activated. No
mention of this little feature is made on the documentation page.
Here is the documentation: http://maven.apache.org/guides/
introduction/introduction
Hi,
Recently, I developed a Java-based maven plugin intended to run in the test
phase of the maven build instead of the standard surefire-plugin. It has
just one goal, 'test'. When I configured my project's POM to include my
plugin for the testing phase and made sure the POM doesn't refernce suref
On 10/29/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> I doubt that given my visitation of production environments. But that
> said the portion from our own POM provides the same functionality, or
> it would even be preferable in subsequent versions of the release
> plugin to make these goals def
> I'm also interested in organising a Maven project BOF at each. Any
> thoughts?
Could we discuss a way to allow the parser to include xml fragments to
prevent duplicate xml? AFAIK the problem is with the plexus XML
parser that doesn't support entities
> [ ] I'll be at ApacheCon US in Atlanta
>
I know several folks are presenting and will definitely be there, but
I thought it might be good to send a shout out and see who is coming
along? Hopefully we'll get some opportunities for getting together
around the hackathon/code-a-ramas.
I'm also interested in organising a Maven project
I can do another release at the end of this week :) Everybody okay with
that?
-Deng
Brett Porter wrote:
I've merged 1.0-beta-4 back into 1.0-beta-3 in JIRA too.
When would you like to cut the release again Deng?
The only pre-condition I see is that we do need another plexus-webdav
release f
On 29 Oct 07, at 9:35 PM 29 Oct 07, William Ferguson wrote:
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Yes, I know we discussed it briefly at the time, but I
wanted to look at the actual implications for 2.0.x users now.
There are none, they aren't using it. And it's only
implication
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> > Yes, I know we discussed it briefly at the time, but I
> > wanted to look at the actual implications for 2.0.x users now.
> There are none, they aren't using it. And it's only
> implication is in conjunction with the release plugin and the
On 29 Oct 07, at 8:31 PM 29 Oct 07, Brett Porter wrote:
Ok, I can file that for starters.
I think we'll need to make clear instructions about setting up a
repository manager to handle this scenario since I bet there are a
lot of people using simple m1 repos internally for their m1
proje
On 29 Oct 07, at 8:24 PM 29 Oct 07, Brett Porter wrote:
On 30/10/2007, at 7:48 AM, Jason van Zyl wrote:
On 29 Oct 07, at 10:47 AM 29 Oct 07, Brett Porter wrote:
Hi,
I noticed that the super POM has changed on trunk (the removal of
the release profile)
Long long time ago.
Yes, I kno
On 10/25/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> Continuum 1.1-beta-4 is ready for release
+1 - looks good here, license and notice are in place, I added some m2
projects and tried a few things.
I don't care for the column title of "Nb Projects" on the summary
page. How about "Total"?
On 30/10/2007, at 7:51 AM, Jason van Zyl wrote:
Just warn and continue on its business.
Currently, it appears as if the path gets translated correctly,
but it chokes on the lack of a POM file in the repository (this
may also be an issue with builds that don't have POM files in the
m2 rep
On 30/10/2007, at 7:48 AM, Jason van Zyl wrote:
On 29 Oct 07, at 10:47 AM 29 Oct 07, Brett Porter wrote:
Hi,
I noticed that the super POM has changed on trunk (the removal of
the release profile)
Long long time ago.
Yes, I know we discussed it briefly at the time, but I wanted to look
Hi,
Due to a couple of issues we need to release doxia-1.0-alpha-10, before
we can start using it in the plugins. This time I will release doxia and
doxia-sitetools separately, so that we don't confuse Continuum this
time. A vote for doxia-sitetools-1.0-alpha-10 will follow.
Release Notes:
h
On 29 Oct 07, at 11:04 AM 29 Oct 07, Brett Porter wrote:
What is the expected behaviour of legacy repository definitions in
2.1?
Not supported. By the time 2.1 is actually released it will have been
well over two years since 2.0. The support can exist in 2.0.x but
anyone starting with 2.
On 29 Oct 07, at 10:47 AM 29 Oct 07, Brett Porter wrote:
Hi,
I noticed that the super POM has changed on trunk (the removal of
the release profile)
Long long time ago.
, but the version hasn't yet - it's still 4.0.0. Also, IT 51 is
excluded which checks the release profile.
For reason
done
On Oct 25, 2007, at 7:30 PM, Jason van Zyl wrote:
On 25 Oct 07, at 3:36 PM 25 Oct 07, Carlos Sanchez wrote:
could you please keep the old methods and deprecate them with a
comment, if not keeping up with the changes becomes a nightmare
John, put the any additional things you need in t
No worries Brett, thanks for getting back to me. :)
-m
- Original Message
From: Brett Porter <[EMAIL PROTECTED]>
To: Maven Developers List
Sent: Sunday, October 28, 2007 11:56:56 PM
Subject: Re: When I submit a patch for a bug, how do I get someone's attention
to merge it
Generally,
With the exception of the integration tests on trunk (which I just
sent a separate mail about), all the builds in Continuum are passing.
I had to fix a few problems, though all were problems in the relevant
tests under certain circumstances (and most were occurring locally
for me as well),
agreed - this was already on the list. You can see the list of things
that are intended for the system here:
http://issues.apache.org/jira/browse/INFRA/component/12311662
On 30/10/2007, at 3:30 AM, Daniel Kulp wrote:
The only thing to be careful of is the size of the snapshots
directory.
What is the expected behaviour of legacy repository definitions in
2.1? I realise much of the handling was removed - is it expected it
will just error out gracefully if one is encountered? Or the repo
ignored?
Currently, it appears as if the path gets translated correctly, but
it chokes o
John,
You might like to look at IT 0100 and IT 0102 here: http://
maven.zones.apache.org/continuum/surefireReport.action?
buildId=32116&projectId=514&projectGroupId=40#org.apache.maven.its.Suite
It seems there's a problem with some recent changes?
If these aren't showing as issues in your en
Hi,
I noticed that the super POM has changed on trunk (the removal of the
release profile), but the version hasn't yet - it's still 4.0.0.
Also, IT 51 is excluded which checks the release profile.
For reasons of reproducibility, shouldn't POMs with the current
modelVersion retain the same
The only thing to be careful of is the size of the snapshots directory.
Infrastructure has been complaining off and on that various groups
aren't cleaning it up and it "grows and grows and grows".
I think if we had some way to cleanup older snapshots to keep the growth
in check, I'd be
Yeah, that's what I thought.
What we've got is a number of projects that are being built with m2, and
dependencies between them. If the dependency is to 'in-development' code,
then it is usually pulled into an overall 'workspace' project with SVN
externals, and a property in the project is set to
sorry, my fault. killed the wrong build :D
On 30/10/2007, at 3:19 AM, [EMAIL PROTECTED] wrote:
Online report : http://maven.zones.apache.org/continuum/
buildResult.action?buildId=32081&projectId=113
Build statistics:
State: Failed
Previous State: Ok
Started at: Mon 29 Oct 2007 16:18:49 +00
+1
I checked the new license and notice, and checked that it started up
ok from scratch - happy to go ahead with the beta release.
- Brett
On 25/10/2007, at 5:10 PM, Emmanuel Venisse wrote:
Hi,
Continuum 1.1-beta-4 is ready for release
The highlights are
- lot of bug fixes
- A new page
FYI: I have fixed a few issues that were within my reach :), for the
rest I have opened a jira: http://jira.codehaus.org/browse/DOXIA-184
-Lukas
Lukas Theussl wrote:
I've just checked the output of the identity test for the docbook
module, below is a list of discrepancies (note: the identity t
Hello,
(I apologize in advance if this issue was addressed already. Jira ticket
at: http://jira.codehaus.org/browse/MNG-3262 which contains the source
and pom of the plugin and project that uses the plugin)
Wondering if anyone can spot anything stupid I'm doing here...
I've written a Maven 2
I think LATEST and RELEASE apply to plugins only. SNAPSHOT is used in
conjunction with a version. If you really don't care what version you
get (curious) then use a range.
-Original Message-
From: Nigel Magnay [mailto:[EMAIL PROTECTED]
Sent: Monday, October 29, 2007 7:33 AM
To: Maven Deve
I could have sworn I'd read somewhere that it was possible to use dependency
versions of LATEST, RELEASE and SNAPSHOT in a pom dependency to not have to
specify which particular version I needed.
Did I just dream that? Or does it not apply to dependencies?
yep - thanks for taking care of that!
On 29/10/2007, at 8:34 PM, Stephane Nicoll wrote:
It's fixed. Can you test on your end and uncomment the test back if
it's ok?
Thanks,
Stéphane
On 10/29/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
What's the probem?
Thanks,
Stéphane
-- For
It's fixed. Can you test on your end and uncomment the test back if it's ok?
Thanks,
Stéphane
On 10/29/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote:
> What's the probem?
>
> Thanks,
> Stéphane
>
> -- Forwarded message --
> From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
> Date: Oct 2
What's the probem?
Thanks,
Stéphane
-- Forwarded message --
From: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Oct 29, 2007 7:38 AM
Subject: svn commit: r589518 -
/maven/plugins/trunk/maven-ear-plugin/src/test/java/org/apache/maven/plugin/ear/EarMojoTest.java
To: [EMAIL PROTECTED]
39 matches
Mail list logo
