John,
It looks to me like this is related to the Hudson/Nexus configuration.
There are a number of problems on there at the moment - getting some
empty responses from Nexus, 500 errors on deployment in the last 2.1.x
build, timeouts. There are also a whole bunch of other projects
building
That was with 2.0.x, btw.
On trunk, I get failures in the embedder with paths that look like:
c:\users\brett\...\target\embedder-test-project-caching\c:\users\brett
\...\target\embedder-test-project-caching\target\classes
(ie, double appending - could well be a problem with detecting whether
Hi John, all,
I don't have time to investigate fixing this up, but I ran the ITs on
windows and found that these failed with / vs \ problems:
- it0088
- MNG2339a
- MNG3355
- MNG3475
Thought you might like to check it out if you have your hands on a
windows VM.
Cheers,
Brett
--
Brett Port
I've just reverted a portion of the change to distributionManagement
as it was breaking CI (you can't move things between objects).
I also find a few things weird about the order. IMO,
- dependencies and repositories should be together
- dependencies and dependencyManagement should be together
2008/6/29, Dennis Lundberg <[EMAIL PROTECTED]>:
> Vincent Siveton wrote:
>
> > Excellent work Dennis!
> >
> > About the "Maven projects" list, I think maven 2 should be in first to
> > improve the usability.
> >
>
> I doubt it will make things more usable. I find that ordering stuff
> alphabetical
Agree with you, Paul.
Vincent
2008/6/29, Paul Benedict <[EMAIL PROTECTED]>:
> I think it is very smart to always mark issues that are both 2.0.x and 2.1
> (HEAD). While it my be "common knowledge" among the depths Maven developers
> that issues being applied to 2.0.x are usually applied to trun
Hi Brett,
2008/6/29, Brett Porter <[EMAIL PROTECTED]>:
> Vincent,
>
> I'm a bit confused about these changes. It should be obvious that if it
> were fixed in 2.0.9 that it is also present (if relevant) in 2.1... won't it
Since the changes have not been applied initially, it is not so obvious ;)
Can you file a jira and attach a project that reproduces the issue? This
will be the best way for us to figure out what's up. There were some
changes between 2.0.8-9 that may cause this (and wouldn't be bugs per
se), but we won't know until we look. If it truly is a regression, we
want to fix it fo
I think it is very smart to always mark issues that are both 2.0.x and 2.1
(HEAD). While it my be "common knowledge" among the depths Maven developers
that issues being applied to 2.0.x are usually applied to trunk as well, it
shouldn't be assumed when managing issues. It's possible for issues to b
On 30/06/2008, at 5:00 AM, Dennis Lundberg wrote:
Vincent Siveton wrote:
Excellent work Dennis!
About the "Maven projects" list, I think maven 2 should be in first
to
improve the usability.
I doubt it will make things more usable. I find that ordering stuff
alphabetically is more access
Vincent,
I'm a bit confused about these changes. It should be obvious that if
it were fixed in 2.0.9 that it is also present (if relevant) in 2.1...
won't it be confusing to see the 2.1 release notes and see a whole lot
of things that are essentially not different from the last 2.0.x
rele
On Mon, 23 Jun 2008 14:26:38 Michael McCallum wrote:
> have a meeting will explain in more detail later...
have not forgotten just been really busy and want to give this a proper
treatment...
--
Michael McCallum
Enterprise Engineer
mailto:[EMAIL PROTECTED]
-
+1, to get things started :-)
Dennis Lundberg wrote:
Hi,
We solved 23 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11146&styleName=Html&version=13092
There are still a lot of issues left in JIRA:
http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=11146&
Vincent Siveton wrote:
Excellent work Dennis!
About the "Maven projects" list, I think maven 2 should be in first to
improve the usability.
I doubt it will make things more usable. I find that ordering stuff
alphabetically is more accessible that having them ordered by
"importance". Simply b
Vincent Siveton wrote:
IMHO devs should be after licenses, since they describe more a project
than a build.
[...]
same reasoning for ML.
[...]
I propose to put dependencyManagement before dependencies to improve
the readingness.
All fine with me. Also taking into account Paul Benedict's sugges
Dennis Lundberg wrote:
http://people.apache.org/~dennisl/inherited-menu-2.png
Feedback still wanted: negative or positive.
Looks nice ;-)
Benjamin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail
Excellent work Dennis!
About the "Maven projects" list, I think maven 2 should be in first to
improve the usability.
In this case, wdyt to put a list with expanded sub projects (not sure
about the rendering)
Cheers,
Vincent
2008/6/29, Dennis Lundberg <[EMAIL PROTECTED]>:
> OK, listening to the
Hi,
2008/6/29, Benjamin Bentmann <[EMAIL PROTECTED]>:
> Vincent Siveton wrote:
>
>
> > FYI I created MNG-3634 and you could see the result here:
> >
> http://people.apache.org/~vsiveton/MNG-3634/maven-2.0.x/site/maven.html
> >
> > Comments are welcome!
> >
>
> I prefer your initial suggestion, wh
OK, listening to the suggestions and coming up with a second attempt:
http://people.apache.org/~dennisl/inherited-menu-2.png
Feedback still wanted: negative or positive.
Jesse McConnell wrote:
I agree with vincent and this is a great improvement
nice!
jesse
On Wed, Jun 25, 2008 at 10:22 AM,
On Sun, Jun 29, 2008 at 3:42 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> Niall Pemberton wrote:
>>
>> On Sat, Jun 28, 2008 at 5:56 PM, Ralph Goers <[EMAIL PROTECTED]>
>> wrote:
>>>
>>> What does -X tell you?
>>
>> Not alot that makes any sense to me, but thanks for the suggestion - I
>> ran it
Niall Pemberton wrote:
On Sat, Jun 28, 2008 at 5:56 PM, Ralph Goers <[EMAIL PROTECTED]> wrote:
What does -X tell you?
Not alot that makes any sense to me, but thanks for the suggestion - I
ran it with that option for both maven 2.0.8 and 2.0.9 and the output
for both is here:
http://people.ap
If you're going to reorder the POM, put before
or even higher. I've seen them used to specify dependencies, build info, and
alot of other things. Properties aren't just left overs, they are an early
step in the build process and should be "early" in the POM too.
Paul
On Sun, Jun 29, 2008 at 4:
On Sun, Jun 29, 2008 at 5:20 AM, Ralph Goers <[EMAIL PROTECTED]> wrote:
> This caught my eye. I have no idea what it means though or if it could be
> responsible for the problem.
>
> The following artifacts were filtered out for plugin:
> org.apache.commons:commons-build-plugin:1.0 because they're
Vincent Siveton wrote:
FYI I created MNG-3634 and you could see the result here:
http://people.apache.org/~vsiveton/MNG-3634/maven-2.0.x/site/maven.html
Comments are welcome!
I prefer your initial suggestion, which might be looking like that after
incorporating the other elements:
24 matches
Mail list logo
