Hi Benjamin and Paul,
According your comments, I created a new module doxia-test-docs which
includes svn copy on several documents. I also updated tests to fetch
these changes.
Any comments are welcome!
Cheers,
Vincent
2008/12/8 Benjamin Bentmann [EMAIL PROTECTED]:
Vincent Siveton wrote:
Vincent,
The project doxia-test-docs should contain the documents and the
document should be maintained in the projects source repository so
they can be release by the project, i.e. mvn release... The version
of this project should change whenever the source documents change,
i.e when
Hi Oleg,
In fact, I have only one question: why create a completely new codebase?
Of course, the new code with less features is simpler *for the moment*: less
features is less code.
Features are exactly same as current ant-tasks: see the documentation [1]
How can you -1 something you don't even work on? A suggestion to
improve it, fine. I think you're way out of line given you're not even
remotely involved.
He is adding tests which is the number one priority. How big the test
base is a secondary concern. Don't you think actually having the
Hello,
[Repost from users list, hoping to get more in-depth answer here]
I am busy creating an easy Maven2 setup for a 200+ module system, both targeted
to an easier release and an easier development setup. It is a multi-level
system, with common modules, service modules and presentation
Have a look at versions:update-properties... (you'd need version 1.0-alpha-2
or newer)
I'd structure things a little differently... but it might help you achieve
your end-goal.
2008/12/10 De Smet Ringo [EMAIL PROTECTED]
Hello,
[Repost from users list, hoping to get more in-depth answer here]
Stephen,
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: woensdag 10 december 2008 13:12
To: Maven Developers List
Subject: Re: Version property in root POM multi-level
dependency resolution
Have a look at versions:update-properties... (you'd need
On 10/12/2008, at 4:33 PM, Brett Porter wrote:
Sorry Oleg, I have to -1 this commit. There's no way 70mb of test
resources (147mb if you use checkout instead of export!) should be
necessary here.
Didn't have time to check this earlier, but an interim suggestion
would be to do this:
find
2008/12/10 De Smet Ringo [EMAIL PROTECTED]
Stephen,
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: woensdag 10 december 2008 13:12
To: Maven Developers List
Subject: Re: Version property in root POM multi-level
dependency resolution
Have a
On 10/12/2008, at 7:52 PM, Hervé BOUTEMY wrote:
Hi Oleg,
In fact, I have only one question: why create a completely new
codebase?
Of course, the new code with less features is simpler *for the
moment*: less
features is less code.
This was my first reaction as well. I think you might
+1, not using it yet, but sources build, and spot checked that sigs
and licenses are in place.
We need to start using this somewhere so more people beat it around.
BTW, The staging repo has apache-maven 2.1.0-M2-SNAPSHOT in there -
need to make sure it is not synced in the release (so the
Stephen,
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: woensdag 10 december 2008 14:01
To: Maven Developers List
Subject: Re: Version property in root POM multi-level
dependency resolution
I'm not sure where you see the run-time error? In Maven in
Jason,
I see you are in your usual fine form :)
On 10/12/2008, at 8:34 PM, Jason van Zyl wrote:
How can you -1 something you don't even work on? A suggestion to
improve it, fine.
Don't be such a drama queen. A -1 is not an attack on anyone, so I
don't know why you're on the defensive,
Brett,
Brett Porter a écrit :
- the SAT POMs don't have license/org information so the notices are
incomplete.
That information is available in org.sat4j.pom:
http://repository.sonatype.org/content/repositories/third-party/org/sat4j/org.sat4j.pom/2.0.4/org.sat4j.pom-2.0.4.pom
licenses
Regrettably, that's not what is on central, but some auto-generated
Nexus stuff:
http://repo2.maven.org/maven2/org/sat4j/org.sat4j.core/2.0.4/org.sat4j.core-2.0.4.pom
- Brett
On 11/12/2008, at 12:38 AM, Daniel Le Berre wrote:
Brett,
Brett Porter a écrit :
- the SAT POMs don't have
On 10-Dec-08, at 1:13 PM, Brett Porter wrote:
Jason,
I see you are in your usual fine form :)
On 10/12/2008, at 8:34 PM, Jason van Zyl wrote:
How can you -1 something you don't even work on? A suggestion to
improve it, fine.
Don't be such a drama queen. A -1 is not an attack on anyone,
Nexus doesn't auto-generate anything. Certainly not POMs.
On 10-Dec-08, at 3:07 PM, Brett Porter wrote:
Regrettably, that's not what is on central, but some auto-generated
Nexus stuff:
http://repo2.maven.org/maven2/org/sat4j/org.sat4j.core/2.0.4/org.sat4j.core-2.0.4.pom
- Brett
On
I am only responding because the disagreement is public and everyone is
blessed to witness it :)
Forgive the way other Apache projects might use vetoing power, but I can't
see anything inappropriate about casting a -1 vote on a commit. The vote
isn't about intentions to solve or fix the
On Wednesday 10 December 2008 10:34:22 am [EMAIL PROTECTED] wrote:
I am only responding because the disagreement is public and everyone is
blessed to witness it :)
Forgive the way other Apache projects might use vetoing power, but I can't
see anything inappropriate about casting a -1 vote on
On 10-Dec-08, at 4:34 PM, [EMAIL PROTECTED] wrote:
I am only responding because the disagreement is public and everyone
is blessed to witness it :)
Forgive the way other Apache projects might use vetoing power, but I
can't see anything inappropriate about casting a -1 vote on a commit.
On 11/12/2008, at 2:24 AM, Jason van Zyl wrote:
The -1 is a last action that should be taken. You tossed it out in a
very cavalier fashion. What you're saying above describes discussing
with Oleg to fix the problem. But that's not what you did. You're
right, Oleg checking in a bunch of
On 11/12/2008, at 2:26 AM, Jason van Zyl wrote:
Nexus doesn't auto-generate anything. Certainly not POMs.
From the POM:
descriptionPOM was created by Sonatype Nexus/description
I presume that was someone doing an upload somewhere or something -
perhaps I should have said generated, not
Hi,
We're thinking about upgrading our SVN server to 1.5.4 ... does anyone
have a working solution/patch for the scm-/release-plugin issues ? Or
has this been fixed already and the JIRA is just outdated ?
Regards,
Tobias
-
To
Workaround: just do svn up and rerun mvn release:prepare
No, this issue is not fixed.
2008/12/10, Tobias Gierke [EMAIL PROTECTED]:
Hi,
We're thinking about upgrading our SVN server to 1.5.4 ... does anyone
have a working solution/patch for the scm-/release-plugin issues ? Or
has this
If I may cast my opinion here as a direct recipient.
When I saw Oleg, I have to -1 this to me it sounded like a death
sentence, an honorable PMC member vetoed my changes! And for what - test
repo is too big ??
Right after this - I see that I can no longer connect to
people.apache.org nor
Herve,
Hervé BOUTEMY wrote:
Hi Oleg,
In fact, I have only one question: why create a completely new codebase?
Of course, the new code with less features is simpler *for the moment*: less
features is less code.
At first I honestly tried to plug in Mercury into existing code, but:
* as the
Hi Maven team!
JWebUnit project is bitten by http://jira.codehaus.org/browse/MJAVADOC-181
I would like to know if someone could apply the provided patch and push a new
SNAPSHOT (and even better release a new version to avoid a SNAPSHOT dependency).
Thank you very much
Julien
ok, I understand: for you, the tasks code is big then it is difficult to
integrate Mercury, and for me, Mercury is big then it is difficult to
integrate it into the tasks. :)
For the doc and the overall logic, now that the doc has been rewritten, split
into parts (big thank you Dennis),
Took me a while to figure that one out as well. This comes from uploading a
third party jar via the ui...it gens an empty pom the same as
deploy:deploy-file would.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2008 11:02 AM
To: Maven
Thanks. Benjamin says it's good on the grid now too. I'll double check
locally and then restage tonight.
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, December 10, 2008 12:36 AM
To: Maven Developers List
Subject: testing 2.0.10-RC5-SNAPSHOT
Hi Brian,
Herve,
It also works now - I can compile java with mercury supplied jars. You
can checkout the Mercury trunk. Unfortunately - thank to unknown
samaritan - I cannot logon to people.apache.org and cannot deploy
snapshots, so you'll have to install Mercury snapshots and package
mecrcury-ant: it
Oleg, I can appreciate how you felt. I guess my take on a -1 is
somewhere in between. Justification for a -1 is always required. You
can respond with a) why what you did is absolutely necessary and begin
a dialogue, b) fix the problem that was specified or c) remove the
code. While you
On 11/12/2008, at 5:02 AM, Oleg Gusakov wrote:
Right after this - I see that I can no longer connect to
people.apache.org nor can I deploy any snapshots. I still cannot.
Brett, if you did this - please restore my access to the site. I
don't think I deserved that.
No, of course not (I
Benjamin, Jason,
I'm having the same problem. See inline
On 26/11/2008, at 12:48 AM, Benjamin Bentmann wrote:
jvanzyl wrote:
Author: jvanzyl
Date: Mon Nov 24 23:11:35 2008
New Revision: 720432
URL: http://svn.apache.org/viewvc?rev=720432view=rev
Log:
o primarily refactoring in part for the
On 10/12/2008, at 11:17 PM, Brett Porter wrote:
On 10/12/2008, at 4:33 PM, Brett Porter wrote:
Sorry Oleg, I have to -1 this commit. There's no way 70mb of test
resources (147mb if you use checkout instead of export!) should be
necessary here.
Didn't have time to check this earlier,
Hello,
This RC fixes the SCP wagon problem identified in RC2 (MNG-3717). We
have reverted the 2.0.x branch back to use wagon beta-2 where it was
historically for stability. Users that require fixes for wagon beta-3+
should use 2.1.0-M1 instead.
Here's the list of issues fixed in 2.0.10:
Deploying a new snapshot of plexus-plugin-manager would fix this since
it works after building locally but not if the latest snapshot is
retrieved (I don't have permission to do this).
The test continues to fail if wagon-webdav is not in the local
repository already, so it's probably going
Hello,
(I already tried on users- list)
I'm trying to make a jar containing x dependencies to be used as a
single dependency, using Shade with the following options:
createSourcesJartrue/createSourcesJar
keepDependenciesWithProvidedScopetrue/keepDependenciesWithProvidedScope
38 matches
Mail list logo
