Exclusions ?
org.codehaus.plexus
plexus-archiver
1.0-alpha-9-SNAPSHOT
org.codehaus.plexus
plexus-container-default
org.codehaus.plexus
plexus-component-api
-Message d'origine-
De : Brian E. Fox [mailto:
On 23/06/2007, at 10:25 AM, [EMAIL PROTECTED] wrote:
How do I get the source distro to unpack to a directory ending in -
src?
Simply add it to the finalName (you get a weird -src-src artifact in
target, but it's correct in the repository and when unpacked - see
the maven root pom).
-
Coudln't this be done with the model version?
On 23/06/2007, at 11:42 AM, [EMAIL PROTECTED] wrote:
Author: jdcasey
Date: Fri Jun 22 18:42:13 2007
New Revision: 549997
URL: http://svn.apache.org/viewvc?view=rev&rev=549997
Log:
Adding since-2.2 annotations to the two new flags.
Modified:
ma
We shouldn't permit relative entities in the POM - it would cause
grief when deployed to the repository.
- Brett
On 23/06/2007, at 5:29 AM, Hervé BOUTEMY wrote:
Le vendredi 22 juin 2007, Arnaud HERITIER a écrit :
Be careful, because when you read an xml file with a reader (or an
inputstream
Ugh. Several highly desired fixes for mdep require the new archiver. Is
there anyway to get it fixed or are we stuck?
(for the record, it still works for me but it appears unstable if mark
can't build it)
-Original Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Friday, June
Le vendredi 22 juin 2007, Arnaud HERITIER a écrit :
> Be careful, because when you read an xml file with a reader (or an
> inputstream) instead of a path (or an url) you can't use relative entities
> in xml (because the parser can't know where the main doc is).
yes, read(InputStream) is better than
fixed (again) hopefully
On 6/22/07, Max Bowsher <[EMAIL PROTECTED]> wrote:
Max Bowsher wrote:
> Oh. I was caught out by the interpolation syntax change ${foo} to [foo].
> Adapting to that, it now seems to be working - thanks!
Seems I spoke too soon :-(
-Declipse.addVersionToProjectName doesn't
On 21 Jun 07, at 10:26 PM 21 Jun 07, Hervé BOUTEMY wrote:
Le jeudi 21 juin 2007, Jason van Zyl a écrit :
It seems like there are many problems with encoding that could be
easily solved with a couple tweaks to modello, specifically the
reader and writing so I've scheduled these for 2.0.8. There
On 22 Jun 07, at 9:44 AM 22 Jun 07, Mark Hobson wrote:
On 22/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
On 22/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
> On 21/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
> > On 21/06/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> > > That's odd, I am a
Be careful, because when you read an xml file with a reader (or an
inputstream) instead of a path (or an url) you can't use relative entities
in xml (because the parser can't know where the main doc is).
This is not a problem because we discourage the usage of xml entities in our
xml documents, bu
You can find here the different protocols allowed http://maven.apache.org/wagon/
http:// doesn't allow deploying
file:// will put it in your local file system, if you want it in the
subversion repo later you'd have to commit
scm:svn: is probably what you want, although is not well tested yet,
see
On 22/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
On 22/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
> On 21/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
> > On 21/06/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> > > That's odd, I am able to build mdep with no problems.
> >
> > I'm building u
Le vendredi 22 juin 2007, Kenney Westerhof a écrit :
> * There are multiple methods for version modification/retrieval:
>
> * resolved version (setter only - sets version)
> * version (sets version, baseversion, and versionrange; gets version)
> * base version (sets base version, gets basever
Le vendredi 22 juin 2007, Kenney Westerhof a écrit :
> Hi,
Hi,
>
> indeed, it's a case of doing new XXXInputstream( something, "encoding" ),
> or a reader. Some work has been done on this, IIRC.
>
> The problem is that you need to prescan the xml declaration, so you start
> parsing until you get t
On 22/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
On 21/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
> On 21/06/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> > That's odd, I am able to build mdep with no problems.
>
> I'm building using the current 2.0.x branch, if that makes any difference?
On 21/06/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
On 21/06/07, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> That's odd, I am able to build mdep with no problems.
I'm building using the current 2.0.x branch, if that makes any difference?
Same problem with 2.0.5, 2.0.6 and 2.0.7..
Mark
On 22/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 22 Jun 07, at 3:15 AM 22 Jun 07, Mark Hobson wrote:
> As mentioned above, this requires a change in the Maven installation
> rather than the POM. Obviously far from ideal, but I'm happy to live
> with this for the huge gain in productivity
On 22 Jun 07, at 6:38 AM 22 Jun 07, Mark Hobson wrote:
"The method I've been using to switch conflict resolvers in 2.0.x
is by
supplying an auxiliary components.xml in $M2_HOME/extensions and
updating m2.conf, as described in MNG-2771. I'm aware that this is
per-installation and not define
Hi, i'm writting you because i don't undestand very well yet Maven. I
want do a simply task: deploy a maven project on SVN repository via
http .
If I put an http:// URL into tags I have an 409 error
deploiyng. If i use file:// ,the project will be copy to the
repositori...but, is not visib
On 22/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
On 22 Jun 07, at 2:56 AM 22 Jun 07, Mark Hobson wrote:
> MNG-1577 is a small step in the right direction, but nearest conflict
> resolution is the root cause of most of our dependency woes which sap
> large amounts of developer time. As I men
On 22 Jun 07, at 6:26 AM 22 Jun 07, Jason van Zyl wrote:
MNG-1577 is not simply the employing the nearest strategy of
selection: it is putting the user in control of what gets selected.
"To give an example of the number of components within our top-level
projects: a typical project has 15
On 22 Jun 07, at 3:15 AM 22 Jun 07, Mark Hobson wrote:
On 22/06/07, Brett Porter <[EMAIL PROTECTED]> wrote:
It's never been an alternative, but it was implemented as "newest
wins" in an early alpha.
Curse the person who switched to nearest! ;)
> How would anyone select a different strategy
On 22 Jun 07, at 2:56 AM 22 Jun 07, Mark Hobson wrote:
On 21/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I don't think this makes sense to add to 2.0.x as we have to 1)
provide a way to load these strategies which is taken care of in 2.1,
The method I've been using to switch conflict res
On 22 Jun 07, at 3:51 AM 22 Jun 07, Kenney Westerhof wrote:
Jason van Zyl wrote:
[snip]
I will coalesce these three pages to mesh:
http://docs.codehaus.org/display/MAVEN/Taxonomy
http://docs.codehaus.org/display/MAVEN/Maven+Taxonomy
http://docs.codehaus.org/display/MAVEN/Architectural+Goal
On 22/06/07, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
Well, just looked at the code and it's a mess. Here are the problems:
* The isSnapshot method does a regexp on the version for the timestamp, and if
it matches,
replaces the baseversion with -SNAPSHOT. If it doesn't match, checks for
'
It seems to run the 2.0 version of the report plugin, which is quite old.
Try setting the version for surefire and the report plugin to 2.3 or later
snapshots.
The surefire artifacts on central haven't been updated since feb 28 2007,
so there haven't been any deployments lately.
Did you mean the
Hervé BOUTEMY wrote:
Le mercredi 20 juin 2007, Kenney Westerhof a écrit :
Also see
https://svn.apache.org/repos/asf/maven/surefire/trunk/maven-surefire-plugin
/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java
line 494.
I tried to fix this a while back but it's a big mess a
I am having the same problem. Just appeared today out of blue..
What has happened with the surefire plugins lately? It seems like people are
deploying a lot of broken surefire artifacts to the central repository..
-olemartin
2007/6/15, Jon Strayer <[EMAIL PROTECTED]>:
I have a main project wi
Max Bowsher wrote:
> Oh. I was caught out by the interpolation syntax change ${foo} to [foo].
> Adapting to that, it now seems to be working - thanks!
Seems I spoke too soon :-(
-Declipse.addVersionToProjectName doesn't work. The problem is that
calculateProjectNameTemplate() attempts to use:
An emphatic +1 :-)
-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
Sent: Wednesday, June 20, 2007 12:46 PM
To: Maven Developers List
Subject: [vote] Release Maven 1.1 Final
Hi team,
It's with pleasure that I want to launch the vote to release the final
version of m
Max Bowsher wrote:
> Carlos Sanchez wrote:
>> On 6/21/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
>>> On 6/21/07, Max Bowsher <[EMAIL PROTECTED]> wrote:
Carlos Sanchez wrote:
> yes, it should work, if I configure it in the pom it does, can you
>>> try
> that?
The interpolation d
Carlos Sanchez wrote:
> On 6/21/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
>> On 6/21/07, Max Bowsher <[EMAIL PROTECTED]> wrote:
>> > Carlos Sanchez wrote:
>> > > yes, it should work, if I configure it in the pom it does, can you
>> try
>> > > that?
>> >
>> > The interpolation does work then, ye
Jason van Zyl wrote:
[snip]
I will coalesce these three pages to mesh:
http://docs.codehaus.org/display/MAVEN/Taxonomy
http://docs.codehaus.org/display/MAVEN/Maven+Taxonomy
http://docs.codehaus.org/display/MAVEN/Architectural+Goals+for+Maven+2.1
I you mean 'merging' by 'coalesce', please
Hi,
indeed, it's a case of doing new XXXInputstream( something, "encoding" ),
or a reader. Some work has been done on this, IIRC.
The problem is that you need to prescan the xml declaration, so you start
parsing until you get the first xml language element that is not a comment,
(an xml element
Mark Hobson wrote:
On 22/06/07, Brett Porter <[EMAIL PROTECTED]> wrote:
It's never been an alternative, but it was implemented as "newest
wins" in an early alpha.
Curse the person who switched to nearest! ;)
:)
It should be nearest though, with a fallback to newest if there are 2
nodes a
On 22/06/07, Brett Porter <[EMAIL PROTECTED]> wrote:
It's never been an alternative, but it was implemented as "newest
wins" in an early alpha.
Curse the person who switched to nearest! ;)
> How would anyone select a different strategy? This would require a
> change to the POM to even turn on
On 22/06/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Maybe I misunderstood, but I don't think the intention of this patch
is to allow other people to plug in their own, but simply allowing
them to use alternatives we've provided. The pluggable part certainly
needs to come later.
Yep, and in 2.0
On 21/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote:
I don't think this makes sense to add to 2.0.x as we have to 1)
provide a way to load these strategies which is taken care of in 2.1,
The method I've been using to switch conflict resolvers in 2.0.x is by
supplying an auxiliary components.xm
For the POM we are using the maven-model generated by modello and its
stax-plugin
Arnaud
On 22/06/07, Brett Porter <[EMAIL PROTECTED]> wrote:
Yep, it's just "use Xerces, not xpp3". IIRC, you changed it back to
xerces at some point?
- Brett
On 21/06/2007, at 6:27 PM, Arnaud HERITIER wrote:
>
Yo,
Thanks Lukas, it's been a pleasure to work with you. Hope you'll still
get involved somehow.
Cheers,
Stéphane
On 6/22/07, Lukas Theussl <[EMAIL PROTECTED]> wrote:
+1
Mission accomplished! :) I also consider that we finally finished a job
that should have been done a long time ago, but it'
In maven 1.1 we are already using the stax reader/writer to support XML
entities, and it's working fine...
Arnaud
On 22/06/07, Brett Porter <[EMAIL PROTECTED]> wrote:
On 22/06/2007, at 11:38 AM, Jason van Zyl wrote:
> Does it buy us anything? You've tried it so I don't know but the
> source
+1
Mission accomplished! :) I also consider that we finally finished a job
that should have been done a long time ago, but it's out now at last and
I'm pretty impressed and proud of what we have achieved. (Merci Arnaud,
c'etait tout a cause de toi!) Being somewhat unsure about my future in
th
42 matches
Mail list logo
