Issue Subscription
Filter: Design & Best Practices (28 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
htt
I just deployed a new snapshot of maven-artifact, hopefully that will
correct the issue.
Cheers,
Brett
On 27/06/2008, at 5:42 AM, Timothy Reilly wrote:
I just checked out maven-components from trunk per the "Guide to
Building Maven" and I ran into this compilation failure.
Any ideas ?
[INFO
My bad ! (opening multiple files with the same vi can cause typo -:) )
Sorry !
--
Olivier
2008/6/26 Vincent Siveton <[EMAIL PROTECTED]>:
> Hi olivier,
>
> 2008/6/26, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
>> Author: olamy
>> Date: Thu Jun 26 14:09:50 2008
>> New Revision: 672030
>>
>> URL: ht
Hi olivier,
2008/6/26, [EMAIL PROTECTED] <[EMAIL PROTECTED]>:
> Author: olamy
> Date: Thu Jun 26 14:09:50 2008
> New Revision: 672030
>
> URL: http://svn.apache.org/viewvc?rev=672030&view=rev
> Log:
> upgrade some plugins to last version
>
> Modified:
> maven/pom/trunk/maven/pom.xml
>
>
I just checked out maven-components from trunk per the "Guide to
Building Maven" and I ran into this compilation failure.
Any ideas ?
[INFO] Compiling 74 source files to
C:\temp\m\maven-components\maven-project\target\classes
[INFO]
---
The ball is now in motion:
https://svn.apache.org/viewvc?view=rev&revision=672009
Feel free to propose new rules on this list, that can later be added to
the style guide.
Dennis Lundberg wrote:
Hi
Maven is about convention over configuration and using best practices.
One best practice on th
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&status=1
Staging repo:
http://people.apache.org/~dennisl/
Paul Gier wrote:
Anyway, I definitely like the idea of a pom plugin to do "pom:reformat"
or "pom:reorder" and maybe I can add a parameter about sorting the
dependencies.
Instead of a parameter, I believe sorting the dependencies should be a
distinct mojo. Otherwise, how to handle the use cas
Hello,
This is a bit a re-post of an earlier message I posted to the user list.
I got no replies, so I hope the developer community can help me better.
I have been searching mailing list archives, Googled, etc. for days, but
I can't get my problem resolved. I have two Ant-based mojo's that cause
Brett Porter wrote:
On 26/06/2008, at 10:10 PM, John Casey wrote:
I think basedir will be null if the project is being read from the
repository. The second line is just a debug statement that crept
through, from when I was having trouble with something like 10 ITs
fail. They all pass under
I originally just wrote some code because I wanted to put the dependencies in my
pom in alphabetical order and/or grouped by scope. Then I was thinking that
there could be a general pom plugin to do things like sort the dependencies or
reformat etc [1]. I didn't realize that there was already
On 26/06/2008, at 10:27 PM, Brett Porter wrote:
On 26/06/2008, at 10:10 PM, John Casey wrote:
I think basedir will be null if the project is being read from the
repository. The second line is just a debug statement that crept
through, from when I was having trouble with something like 10
On 26/06/2008, at 10:10 PM, John Casey wrote:
I think basedir will be null if the project is being read from the
repository. The second line is just a debug statement that crept
through, from when I was having trouble with something like 10 ITs
fail. They all pass under the current changes
I think basedir will be null if the project is being read from the
repository. The second line is just a debug statement that crept
through, from when I was having trouble with something like 10 ITs fail.
They all pass under the current changes.
This holds true even with the changes to the sup
Hi,
2008/6/26 Dennis Lundberg <[EMAIL PROTECTED]>:
> Vincent,
>
> I was planning to put an explanation for ISO dates on the upcoming
> "Documentation Style Guide" document. I don't think that we need them on
Sounds good.
> every page, do you?
Nope. I see that we could leave the "Release ISO Dat
Vincent,
I was planning to put an explanation for ISO dates on the upcoming
"Documentation Style Guide" document. I don't think that we need them on
every page, do you?
[EMAIL PROTECTED] wrote:
Author: vsiveton
Date: Wed Jun 25 17:34:22 2008
New Revision: 671697
URL: http://svn.apache.org/v
The Maven team is pleased to announce the release of the Maven
Repository Plugin, version 2.1
This plugin is used to create bundles of artifacts that can be uploaded
to the central repository.
http://maven.apache.org/plugins/maven-repository-plugin/
You can run mvn -up to get the latest version
Some more comments for the shared model (sorry, going backwards in
time)...
On 18/06/2008, at 2:10 AM, [EMAIL PROTECTED] wrote:
Author: sisbell
Date: Tue Jun 17 11:10:16 2008
New Revision: 668774
URL: http://svn.apache.org/viewvc?rev=668774&view=rev
Log:
General model builder API.
Firstl
18 matches
Mail list logo
