Alan D. Cabrera wrote:
> On Nov 9, 2008, at 6:43 AM, Max Bowsher wrote:
>> Alan D. Cabrera wrote:
>>> On Nov 8, 2008, at 2:55 PM, Max Bowsher wrote:
>> (There's also the question of what architecture/processor naming scheme
>> to use - amd64 vs. x86_64, i
Alan D. Cabrera wrote:
> On Nov 8, 2008, at 2:55 PM, Max Bowsher wrote:
>> The difficulty is that there is no standard on how to manage the
>> multitude of flavours of native binaries that are possible.
>>
>> For example, there's architecture and OS that need to b
Alan D. Cabrera wrote:
> I would like to publish the APR artifacts into the Maven repository,
> [1]. I think that the group id should be org.apache.apr and the
> artifact id should be apr.
>
> Does anyone have a problem with these group and artifact ids? Does
> anyone have a problem with me publ
David Jencks wrote:
Would it be possible for the release plugin to do the following?
1. modify working copy poms to release version
2. do a working copy to repo copy for the new tag
3. adjust the working copy poms to the new version, or revert if the new
version is the same as the old version
Vincent Siveton wrote:
Hi,
Background:
Trying to mavenize an Eclipse Plugin project, I got error messages
like the following:
Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
I put in jira a test project to reproduce this error [1].
Discussions:
After some investigation
Daniel Kulp wrote:
Dan,
I'm cannot really answer the question about what @aggregator does, but I
can say the javadoc example is not a good one. There are many of us
that think the javadoc mojo should NOT have it and have our javadoc
plugins locked down to a previous version for the same rea
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
Gilles Scokart wrote:
> Yes, I understand that someone decided to rename the version number.
>
> My problem is that I don't know how to consider the version number in the
> conflict resolution. If I consider the
> version number of the relocated module or the version number of the 'target
> of
Carlos Sanchez wrote:
> On Nov 28, 2007 8:07 PM, Max Bowsher <[EMAIL PROTECTED]> wrote:
>> Carlos Sanchez wrote:
>>> As I said before it's easier to add the new bundles using
>>> id=groupId+artifactId than to change the whole repo so artifactId can
>>
Carlos Sanchez wrote:
> As I said before it's easier to add the new bundles using
> id=groupId+artifactId than to change the whole repo so artifactId can
> be used as id
>
> You have to consider that the repository is not only for Maven users
My point is that the repository is currently in a stat
Carlos Sanchez wrote:
> On Nov 28, 2007 6:40 PM, Richard van Nieuwenhoven <[EMAIL PROTECTED]> wrote:
>> The reason for me is that eclipse is the source of the jars and eclipse
>> does repeat the group name in the jar name.
>>
>> It looks very strange to have 10 different jars in the classpath all
>
Carlos Sanchez wrote:
> I'm uploading right now a good number of jars to
> http://repo1.maven.org/eclipse-staging/
> If it looks good I will sync to central
>
> Note that the location for the one you want should be
> http://repo1.maven.org/eclipse-staging/org/eclipse/core/resources/3.2.1/
I wonde
Brian E. Fox wrote:
> I think classes should be first. (before test-classes)
Wasn't that the old way, and it's recently been switched?
Presumably the rationale is to allow test-classes to contain resources
which override same-named resources in the main classes dir, or something?
Max.
signat
olivier lamy wrote:
> Hi,
> Is there any objections to have a fisheye support here :
> http://fisheye6.cenqua.com/
Better check with the Infrastructure team ([EMAIL PROTECTED]), as IIRC
the fisheye initial indexing process puts a *LOT* of load on svn.
Max.
signature.asc
Description: OpenPGP di
Mark Hobson wrote:
> On 17/09/2007, Brian E. Fox <[EMAIL PROTECTED]> wrote:
>> Actually I missed that. Mark, what's the problem with analyze forking
>> the build if there is already a justAnalyze that doesn't?
>
> Okay, I like Max's suggestion of following the assembly plugin's
> convention. I'll
Mark Hobson wrote:
> On 17/09/2007, Mark Hobson <[EMAIL PROTECTED]> wrote:
>> On 17/09/2007, Mark Hobson <[EMAIL PROTECTED]> wrote:
>>> Brian and anyone else interested,
>>>
>>> I'd like to make a couple of small changes to the analyze goal:
>>>
>>> 1) Remove @execute phase="test-compile" and repla
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
Dan Tran wrote:
> cool, at least someone sees what i see. So this 2.4 release is a nogo. -1
> from me.
>
> we should reopen MECLIPSE-248 as well right?
No, this is not the issue for which I reported MECLIPSE-248, which has
been fixed.
This is a vaguely similar issue which has been conflated wi
Richard van Nieuwenhoven wrote:
> Another question did anyone test the plugin with eclipse 3.3 (with and
> without WTP) ?
Works fine on ordinary projects. I don't use WTP so I can't test that.
Max.
signature.asc
Description: OpenPGP digital signature
Barrie Treloar wrote:
> Apologies for the noob question, but how do I test the stage release?
> (I had a quick look at
> http://docs.codehaus.org/display/MAVEN/Development+Process and
> http://docs.codehaus.org/display/MAVEN/Development+Procedures but
> couldn't find it).
>
> Is it just a matter o
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 site has been updated:
> http://maven.apache.org/plugins/maven-eclipse-plugin
>
> Plugin is staged here:
> http://people.apache.org/~brianf/stag
Vincent Siveton wrote:
> Same thing here:
> Tests work on windows, failed on solaris so -1 too
Could you confirm what it was that you were building? Was it the tag,
http://svn.apache.org/repos/asf/maven/plugins/tags/maven-eclipse-plugin-2.4/
?
If not, could you re-test, using that.
If you're sti
Max Bowsher wrote:
> I've also found some sort of regression, I believe related to
> dependencies with classifiers.
Filed MECLIPSE-287.
Max.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-m
Brian E. Fox wrote:
> Sorry, I didn't mean to start the conversation, then bail. I was hoping
> I could stage and call a vote before I went travelling and working off a
> slow cell connection.
>
> I'm still having failures on XP. Is this just a windows problem, or is
> stuff really broken, or is
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() atte
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
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
>>
ted by configuration method.
Max.
> On 6/21/07, Max Bowsher <[EMAIL PROTECTED]> wrote:
>> Arnaud HERITIER wrote:
>> > are you sure that ${artifactId} is supported ? It's not
>> ${pom.artifactId} ?
>>
>>
>> The javadoc in the plugin says:
>>
[snip]
&g
Arnaud HERITIER wrote:
> are you sure that ${artifactId} is supported ? It's not ${pom.artifactId} ?
The javadoc in the plugin says:
/**
* Allows configuring the name of the eclipse projects. This
property wins over
* addVersionToProjectName and addGroupIdToProjectName
*
Max Bowsher wrote:
> Brian E. Fox wrote:
>> It's been about 5 months since we last released eclipse. There are
>> plenty of issues already fixed:
>>
>> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13001&styleName
>> =Html&projectId=11
Brian E. Fox wrote:
> It's been about 5 months since we last released eclipse. There are
> plenty of issues already fixed:
>
> http://jira.codehaus.org/secure/ReleaseNote.jspa?version=13001&styleName
> =Html&projectId=11133&Create=Create
>
> There are currently 24 remaining open. Any objections t
Joakim Erdfelt wrote:
> -1 (conditional)
>
> evoking the spirit of dkulp ...
>
> 1) The embedded maven-core-2.0.7-uber.jar has bad LICENSE.txt and
> NOTICE.txt files.
> 1a) The LICENSE.txt at the root of the maven-core-2.0.7-uber.jar is for
> JSch's LGPL license. not ASL.
> 1b) There is no NOTICE
Jason Dillon wrote:
> I'm looking to create a custom converted that saves a plexus
> configuration instance for delayed object configuration. I'm wondering
> what the class is that provides the default mojo instance parameter
> expression handling and injection?
org.apache.maven.plugin.PluginPara
Mark Donszelmann wrote:
> Hi
>
> I am using an aggregate project such as:
>
> T
> -A
> -B
> -C
>
> where C and B have a dependency on A
> and A, B, C all use T as their parent pom.
>
> When I run "mvn install" the projects are run in the correct order: "T,
> A, B, C"
> and all works fine for le
This is an email about a class of bugs, discovered working with the
following general scenario:
I am building a standalone Java application.
maven-jar-plugin is configured with mainClass and addClasspath=true.
maven-assembly-plugin is configured with a to gather up
all the dependencies into a sin
Timothy Reilly wrote:
> Just an observation but when I attempt to add the maven 2 XSD's to
> the XML Catalog within Eclipse I have issues with the key to use.
>
> This is due to the fact that both settings xsd and project xsd's
> share the same target namespace.
> The key may be Namespace Name or
Philippe, Colbert wrote:
> I searched everywhere in the documentation without success. Where
> (what directory) is the Super POM supposed to be and can we change
> that directory?
It is not in a directory. It is packed inside the jar files of the core
Maven distribution. No, you cannot change it
I've just found an utterly bizarre deployment bug. On one particular
developer's workstation, deployment, using scpexe, was failing - and it
turned out to be that somehow the environment variables are getting
corrupted, such that the SSH_AUTH_SOCK variable actually contained its
own previous value,
Jochen Wiedmann wrote:
> I can change that to
>
>mywar
>
> but that means changing the extension.
Not necessarily. Maven plugins are maven-plugin,
but have extension .jar - the two do not have to be the same.
Max.
signature.asc
Description: OpenPGP digital signature
Pankaj Tandon wrote:
> Hi,
> I would like to enhance the release plugin's prepare goal to do the
> following:
> 1. Create a file in the project folder that holds the release tag that the
> user has entered as a part of the release:prepare dialog.
> 2. Check in this file, along with the others in th
Stephane Nicoll wrote:
> On 4/14/07, Max Bowsher <[EMAIL PROTECTED]> wrote:
>>
>> Too late for this release, but could someone take a look at MRELEASE-137
>> so it gets into the next one? It's a trivial one-liner fix. The attached
>> patch is for maven-rele
Jesse McConnell wrote:
> With maven-scm having its latest release underway, the final linchpin
> in getting alpha releases of continuum up and running is the
> maven-release and maven-release-manager.
>
> So I am calling a vote to get the maven-release parent pom released
> and the maven-release-m
The:
maven-enforcer-plugin
maven-gpg-plugin
maven-invoker-plugin
maven-remote-resources-plugin
maven-stage-plugin
do not have tags in the maven-plugins parent pom.
Patch attached - also removes trailing whitespace from one line, and
flips maven-war-plugin and maven-verifier-plugin arou
Brian E. Fox wrote:
> As Jerome pointed out earlier today on the enforcer thread, it would be
> nice to be able to bind some plugins like the enforcer to a phase that
> affects both default and site. After all, if you don't want to support
> some Maven/Jdk/Os/other version, chances are that applies
Jörg Schaible wrote:
> Another regression problem: XDoclet plugin is completly broken. The
> plugin itself was problematic anyway, since it depends on the
> o.a.m.p:maven-anrun-plugin:1.0 (as jar dependency!!!) that prevented the
> version 1.1 from antrun-plugin to work properly already with earlie
Jörg Schaible wrote:
> Max Bowsher wrote on Thursday, March 29, 2007 1:46 PM:
>> private static HashMap commonDecimalModes = new HashMap() {{
>> add("420"); add("436");
>> add("493");
>> add("509");
>> }}
Max Bowsher wrote:
> John Casey wrote:
>> Max: I'm tempted to say that we should look for decimal versions of common
>> octal expressions, then prefix the rest with '0' to ensure they're
>> interpreted as octal (unless they have 0x in front, that is).
>
John Casey wrote:
> Max: I'm tempted to say that we should look for decimal versions of common
> octal expressions, then prefix the rest with '0' to ensure they're
> interpreted as octal (unless they have 0x in front, that is).
>
> Is that a decent solution?
I think that it is the best compromise
John Casey wrote:
> Hi everyone,
>
> I wanted to call a vote to release a beta version of the new assembly
> plugin.
...
> Road Map:
> http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11126&styleName=Html&version=12617
>
> Tag:
> http://svn.apache.org/repos/asf/maven/plugins/tags/maven-
David J. M. Karlsen wrote:
> I'm getting another issue on another project.
> It builds fine on maven 2.0.5, with the snapshot I get a problem with
> xdoclet - see the attached log.
>
>
> this realm = app0.child-container[org.codehaus.mojo:xdoclet-maven-plugin]
...
> urls[10] = file:/heim/ab62939/
Jörg Schaible wrote:
> It is very unfortunate, that you took the same goal that was introduces
> by the maven-dependency-analyzer-plugion, that is currently merged in
> the sandbox in a branch.
TTBOMK, it is not possible for one plugin to implement foobar:alpha and
another to implement foobar:beta
Kenney Westerhof wrote:
> tags cannot change, ever.
The maven-2.0.5 tag already has been changed a bit since creation.
The perpetual tension between burning publicly visible version numbers,
and retaining unique identity of versions strikes again. Unfortunately,
it's a problem without any obvious
Emmanuel Venisse wrote:
> Vincent Siveton a écrit :
>> 2007/1/12, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>>> Author: evenisse
>>> Date: Fri Jan 12 01:05:58 2007
>>> New Revision: 495520
>>>
>>> URL: http://svn.apache.org/viewvc?view=rev&rev=495520
>>> Log:
>>> Fix maven-* version
>>
>> [SNIP]
>>
>>
If you visit http://repo1.maven.org/maven/ you will see that there's a
bogus header that tells you to use the apache.org mirrors.
Someone should modify or remove the HEADER.html in that directory to
remove the out-dated information.
Max.
--
Carlos Sanchez wrote:
> I'd just prefer have xml syntax over string parsing and encourage
> people to use whatever the standard we choose.
Whilst in general, XML can be useful, this might be overusing it.
Versions *must* have some sort of string representation, to be embedded
in file names. That
Brett Porter wrote:
> Hi,
>
> I am going to start looking into the issue with Archiva hanging on
> repository.maven.org, then look at getting a release together, since
> there has been a spike in interest and we can't really just recommend
> people grab it from SVN.
>
> Other than that issue, doe
Barrie Treloar wrote:
>> I've had to comment out one assert: 2.0.1-xyz < 2.0.1. I think
>> generally this is not the case. For example,
>> the wiki guide to patching plugins states that you could patch a
>> plugin and change it's version to 2.0-INTERNAL.
>> In this case, 2.0 would be newer than 2.0
[EMAIL PROTECTED] wrote:
> After that, you can add something with "-" which maven will just
> string-compare (so alpha10 comes between alpha1 and alpha2).
Not true, actually. Maven actually has some weird extra logic that kicks
in when one string component is a prefix of the other, such that actu
Carlos Sanchez wrote:
> actually the ideal id for the repos should be "apache.org"
But, wouldn't that only make sense if it was the only repository at
apache.org?
Is there a recommendation somewhere suggesting how repository IDs should
be chosen?
Max.
e that there's reasonable cause for artifacts
to provide two different File getters, one to get the filename based on
the "version", and one to get the filename based on the "baseVersion".
What do people think about this?
Thanks for reading.
--
Max Bowsher <[EMAIL PROTECTED]>
http://www.mxtelecom.com
signature.asc
Description: OpenPGP digital signature
making the copy - couldn't everything use the
name of the file already existing?
Is it deliberate that at the end of this block, the artifact's
baseVersion has been set to its version?
Thanks in advance to anyone who has the patience to answer - I realize
that's a rat
61 matches
Mail list logo
