I'd had a similar thought initially, but I've not really looked at the
internals of maven yet to know if there is such a distinct thing, or a
pluggable resolver ( I did see that the resolution was on the VersionRange
class so I suspect maybe there isn't ).
Mark
--
Pull me down under...
On Fri,
I'm concerned by this "fix" too.
Here are my thought for now: the fix should not have been done in VersionRange
but in a version conflict resolution phase, since a range is a mathematical
notion we can't alter.
but I didn't have time yet to transform these thoughts in code...
Regards,
Hervé
Any pointers to where in the code base I should start looking/hacking if I
wanted to try and write such a patch?
As I'm the main one arguing for this improvement, I'm willing to at least
try and solve it :)
--
Pull me down under...
On Fri, Sep 3, 2010 at 1:27 PM, Brian Fox wrote:
> Seems logi
I think i agree with Jason on shooting maven 3.0 out to public as soon
as you can, however the dev team might want fix up blocking bugs which
prevent user like me from using maven 3
one of the blocking bug for me is http://jira.codehaus.org/browse/MNG-4788
Thanks
-Dan
On Thu, Sep 2, 2010 at 6:1
Issue Subscription
Filter: Design & Best Practices (24 issues)
Subscriber: mavendevlist
Key Summary
MNG-2184Possible problem with @aggregator and forked lifecycles
http://jira.codehaus.org/browse/MNG-2184
MNG-612 implement conflict resolution techniques
On Fri, Sep 3, 2010 at 9:46 AM, Barrie Treloar wrote:
> On Thu, Sep 2, 2010 at 11:48 PM, John Casey wrote:
>> In your dependencySet, specify the following:
>>
>> false
>
> Cheers.
>
> Did I just miss this in the documentation (other than in the
> configuration page)?
>
> I've had another look aro
Forking this discussion:
On Thu, Sep 2, 2010 at 9:12 PM, Mark Derricutt wrote:
> Personally I'd still like to see some resolution to the problems introduced
> by the version range resolution change ( no more -SNAPSHOT resolution except
> for on the bounds ).
>
> On one hand I applaud the change f
Personally I'd still like to see some resolution to the problems introduced
by the version range resolution change ( no more -SNAPSHOT resolution except
for on the bounds ).
On one hand I applaud the change from a release standpoint, but it currently
causes issues for our integration build process
> When 3.0 is released, is 2.2 pretty much a dead branch? I have no
> problem with that btw :-)
Isn't it essentially dead now?
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@m
When 3.0 is released, is 2.2 pretty much a dead branch? I have no
problem with that btw :-)
On Thu, Sep 2, 2010 at 7:44 PM, Jason van Zyl wrote:
> I think trying to release 3.0 sooner, and then sticking to 6 week release
> cycles would be a better use of time. We're going to fix anything that ar
I think trying to release 3.0 sooner, and then sticking to 6 week release
cycles would be a better use of time. We're going to fix anything that arises
but I don't believe there will be widespread testing until 3.0 is released, and
I don't believe many will pick up 3.x in large-scale production
On Thu, Sep 2, 2010 at 8:40 PM, Barrie Treloar wrote:
> On Fri, Sep 3, 2010 at 9:04 AM, Brian Fox wrote:
>> Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty
>> safely call it feature complete. I'd like to propose a few goals to
>> get some things done. We have ApacheCon coming
On Fri, Sep 3, 2010 at 9:04 AM, Brian Fox wrote:
> Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty
> safely call it feature complete. I'd like to propose a few goals to
> get some things done. We have ApacheCon coming up the first week of
> November, and it would be great to se
I didn't want to hijack the other thread with my questions after
reading https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html
Caching of Artifact Resolution Errors
Marker files are great! Is there any documentation on what they
are? The maven-eclipse-plugin has the hack I added wi
On Thu, Sep 2, 2010 at 11:48 PM, John Casey wrote:
> In your dependencySet, specify the following:
>
> false
Cheers.
Did I just miss this in the documentation (other than in the
configuration page)?
I've had another look around the doco now that I know what to look for
and can't see it.
I'd li
Now that Maven 3 beta 3 is out with Guice and Aether, we can pretty
safely call it feature complete. I'd like to propose a few goals to
get some things done. We have ApacheCon coming up the first week of
November, and it would be great to set that as a target to get Maven
3.0 out the door.
So far
Congrats to Kristian!!
On Thu, Sep 2, 2010 at 6:19 PM, Brian Fox wrote:
> This is a little delayed, but still deserved. A few weeks ago,
> Kristian joined us on the Maven PMC. He's been driving a lot of
> interesting work in Maven 3 to support parallel builds. If you haven't
> tried that out yet,
This is a little delayed, but still deserved. A few weeks ago,
Kristian joined us on the Maven PMC. He's been driving a lot of
interesting work in Maven 3 to support parallel builds. If you haven't
tried that out yet, please do and send some feedback.
Welcome Kristian!
--Brian Fox
Maven PMC Chair
The Maven team is pleased to announce the release of Apache Maven
3.0-beta-3.
Maven is a project comprehension and build tool, designed to simplify
the process of maintaining a healthy development lifecycle for your
project. You can read more here:
http://maven.apache.org/
Downloads of so
Sorry, for the late response. I'm running into a few issues building
the JBoss App server with beta-3. I'm currently trying to narrow down
the issues enough to create small test projects/test cases.
The issues seem to be related to very specific edge cases, so I don't
think they are things to ho
Hi,
Despite a few known bugs in the code, I consider the vote has passed
with the following result:
+1 (binding): Benjamin Bentmann, Jason van Zyl, Brian Fox, Emmanuel
Venisse, Arnaud Héritier, Oliver Lamy, Kristian Rosenvold
+1 (non-binding): Paul Merlin, Stephen Connolly, Tony Chemit, Igo
BTW, this was added for http://jira.codehaus.org/browse/MASSEMBLY-197,
in revId 549995.
-j
On 9/2/10 10:18 AM, John Casey wrote:
In your dependencySet, specify the following:
false
That should take care of things.
On 9/2/10 3:21 AM, Barrie Treloar wrote:
I can't tell exactly when this occu
In your dependencySet, specify the following:
false
That should take care of things.
On 9/2/10 3:21 AM, Barrie Treloar wrote:
I can't tell exactly when this occurred since we forked an internal
release of 2.2 at r487459 where we have applied patches for
* http://jira.codehaus.org/browse/MASSEM
I can't tell exactly when this occurred since we forked an internal
release of 2.2 at r487459 where we have applied patches for
* http://jira.codehaus.org/browse/MASSEMBLY-118
* http://jira.codehaus.org/browse/MASSEMBLY-166
* http://jira.codehaus.org/browse/MASSEMBLY-170
I suspect beta-1 has this
24 matches
Mail list logo
