I agree that it's not a problem to have different urls to get
artifacts and to upload them. Settings for those two operations are
differents in maven (12) thus it doesn't save some lines of settings
if we have the same.
The more important is to provide a mechanism to separate physical
(managed)
On 11/07/07, Brett Porter [EMAIL PROTECTED] wrote:
Do you see the virtual repository as a replacement for all such get
requests, or an additional feature?
I agree with the need for it, I just think we should have both GET (r/
o) per repo, WebDAV (r/w) per repo, and virtual repos (r/o), so it's
More chat logs.. :-)
joakim http://jira.codehaus.org/browse/MRM-426
brett I believe we should include all snapshots in the list, and point
1.3-SNAPSHOT to the latest
brett we can get fancy later (maybe fold the list up under the
1.3-SNAPSHOT heading)
joakim so .. (a) index all versions. (b)
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
This sounds fine to me.
Questions I think weren't answered here:
- how do you track when the modules change - by comparing modules
to the list of projects in a group? If so, how to handle the edge
cases where extra projects are added to or removed from a group aside
from the modules?
- how
Hi Olivier,
I think CONTINUUM-798 is for automatic discovery of new modules of a
project that is already in Continuum. The current setup is that when
Continuum updates from svn, the module is not added as a separate
project. Considering CONTINUUM-774, this should only be done if the
Brett Porter a écrit :
This sounds fine to me.
Questions I think weren't answered here:
- how do you track when the modules change - by comparing modules to
the list of projects in a group? If so, how to handle the edge cases
where extra projects are added to or removed from a group aside
Maria Odea Ching a écrit :
Hi Olivier,
I think CONTINUUM-798 is for automatic discovery of new modules of a
project that is already in Continuum. The current setup is that when
Continuum updates from svn, the module is not added as a separate
project. Considering CONTINUUM-774, this should
On 11/07/2007, at 5:51 PM, Emmanuel Venisse wrote:
Brett Porter a écrit :
This sounds fine to me.
Questions I think weren't answered here:
- how do you track when the modules change - by comparing
modules to the list of projects in a group? If so, how to handle
the edge cases where
Brett Porter a écrit :
On 11/07/2007, at 5:51 PM, Emmanuel Venisse wrote:
Brett Porter a écrit :
This sounds fine to me.
Questions I think weren't answered here:
- how do you track when the modules change - by comparing modules
to the list of projects in a group? If so, how to handle
Hi,
I haven't looked beyond this issue - so there may be more - but I see
CONTINUUM-761 is a new feature scheduled for 1.1-beta-2.
Shouldn't this be in beta-1, or a future version?
- Brett
Hi folks,
I'm currently doing the rounds of all the people using Continuum on
VMBuild. The set up on there ballooned despite the box being
underpowered and the installation intended to be experimental, so was
never very well maintained.
We have a new box to move vmbuild to now and with
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
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
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
Brett Porter a écrit :
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
Hi Brett,
Please see in-line comments below :-)
Brett Porter wrote:
This sounds fine to me.
Questions I think weren't answered here:
- how do you track when the modules change - by comparing modules to
the list of projects in a group? If so, how to handle the edge cases
where extra
Sorry, I didn't see these before I sent my last email. Anyway, I guess
some of the things I wrote there was already answered in the thread :-)
-Deng
Emmanuel Venisse wrote:
Brett Porter a écrit :
On 11/07/2007, at 5:51 PM, Emmanuel Venisse wrote:
Brett Porter a écrit :
This sounds
Issue Subscription
Filter: Outstanding Repository Maintenance: Evangelism (41 issues)
Subscriber: mavendevlist
Key Summary
MEV-518 Google Juice POM has wrong packaging - should be jar and not
pom
http://jira.codehaus.org/browse/MEV-518
MEV-513 Invalid POM:
Issue Subscription
Filter: Outstanding Repository Maintenance: Uploads (5 issues)
Subscriber: mavendevlist
Key Summary
MAVENUPLOAD-1509JETM 1.2.1 bundles
http://jira.codehaus.org/browse/MAVENUPLOAD-1509
MAVENUPLOAD-1508upload vraptor 2.3.2.2
Hi Peter,
Do you have packagingmaven-plugin/packaging ? I'm not sure what the
plugin descriptor not being found could be caused by - this descriptor
is an xml file that is generated automatically by maven.
Are you familiar with the docs?:
Hi everyone,
We've been trying for quite a long time to get into a mode of faster,
more incremental releases. However, when it comes to actually doing
this, we seem married to the idea of pushing out impressive feature
lists with new releases.
I'd like to call an end to that practice,
++1. The JIRA for 2.1-alpha-1 needs to be culled back to just the
regressions, IMO. (Frankly, 2.1.x needs a big scythe run over it too
and some more modest goals set in terms of features to include).
The only other thing I'd note is that we had a list running of things
that needed to be
+1
let's make more releases so we can track the problems as the arise
On 7/11/07, Brett Porter [EMAIL PROTECTED] wrote:
++1. The JIRA for 2.1-alpha-1 needs to be culled back to just the
regressions, IMO. (Frankly, 2.1.x needs a big scythe run over it too
and some more modest goals set in terms
From the resource filtering discussion, it might be a really good idea to
get a list of schema changes that would be nice to get in and at least
get those into the 2.1 alpha so people can try them and comment on them
and such.
The three things on my list that I'd like to see are:
1) Do
+1
Emmanuel
John Casey a écrit :
Hi everyone,
We've been trying for quite a long time to get into a mode of faster,
more incremental releases. However, when it comes to actually doing
this, we seem married to the idea of pushing out impressive feature
lists with new releases.
I'd like to
+1 as we say in New England, it's time to Fish or Cut Bait. Lets get
something out there.
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Wednesday, July 11, 2007 11:15 AM
To: Maven Developers List
Subject: Maven 2.1-alpha-1?
Hi everyone,
We've been trying for quite
None of these has been fleshed out into any sort of formal design,
right? I want to be clear about this: what I'm proposing is not a
feature-complete release of maven 2.1 that just has lingering bugs,
and it's not going to be without its regressions. We have a lot of
work in the trunk of
Vote passed with 7 binding +1 votes and a non-binding +1 vote, and
has been published.
On 04/07/2007, at 7:17 PM, Brett Porter wrote:
This component is used in the project-info-reports plugin (and is a
prereq to its next release) and analyses JAR files for Maven
information and general
On 10/07/2007, at 12:16 AM, John Casey wrote:
Yes, the idea was to provide the materials necessary for the code
grant (since it's coming over from codehaus). I'm not an ASF
member, so (according to the IP pages) all I can do is get the
materials together for someone else to submit.
Once
+1 to graduation from the sandbox, it has passed IP clearance and is
almost ready for release.
-1 to release for a few reasons:
a) the license in the ApplyMojo.java is legally correct, but not
matching the current policy (though all others do). It needs to have
it's text adjusted.
b) the
Hello every one,
I would like to introduce this new eclipse-plugin's mojo to provide
capability configuring eclipse workspace specific configurations
beside the current M2_REPO var in eclipse:add-maven-repo. The actual
motivation is the ability load code style file into the workspace
to be used
Hi,
I have a small patch that is useful to put in under maven-ear-plugin.. How
can I get in that fix/feature in to it...?
Thanks,
Sairam.
_
Tried the new MSN Messenger? Its cool! Download now.
On 11 Jul 07, at 8:15 AM 11 Jul 07, John Casey wrote:
Hi everyone,
We've been trying for quite a long time to get into a mode of
faster, more incremental releases. However, when it comes to
actually doing this, we seem married to the idea of pushing out
impressive feature lists with new
Hi,
I'm working on http://jira.codehaus.org/browse/MNG-1323. It's issue with
24 votes and many other issues depending on it. It's fully repeatable
(has attached maven-integration-test)
and there are some ways to fix it.
Business (user's) problem:
The problem is that maven only once resolve
On 11 Jul 07, at 3:54 PM 11 Jul 07, [EMAIL PROTECTED] wrote:
Author: carlos
Date: Wed Jul 11 15:54:30 2007
New Revision: 555428
URL: http://svn.apache.org/viewvc?view=revrev=555428
Log:
Don't check for the distribution status building MavenProjects
What does that mean exactly? We've never
36 matches
Mail list logo
