The following comment has been added to this issue:
Author: Vincent Massol
Created: Tue, 30 Nov 2004 2:01 AM
Body:
I would also like to make the generation of zip/targz/bzip/etc parametrizable.
I don't understand your reasoning (certainly it's not new to use properties to
customi
On Mon, 2004-11-29 at 14:49, Brett Porter wrote:
> Hi Jason,
>
> I thought the best was that the current one was always o.a.m.model.*,
> and all the historical ones were included with package name.
> ie in maven-model-4.0.0, there is just o.a.m.model; in maven-model-4.0.1
> there is o.a.m.model.
The following comment has been added to this issue:
Author: dion gillard
Created: Tue, 30 Nov 2004 12:00 AM
Body:
I think if you start parameterising goals to death they become unmaintainable
and unusable. Adding parameters to choose zip, tar.gz etc for dist is overkill
IMHO
Taxonomy as a name doesn't gel with the web site concepts.
'Parent'/'Child'?
On Mon, 29 Nov 2004 15:23:13 +0100, Maczka Michal <[EMAIL PROTECTED]> wrote:
> Howdy!
>
> As I described before in one of my previous emails I would like to improve
> the usability of maven generated websites and add t
The following comment has been added to this issue:
Author: Brett Porter
Created: Mon, 29 Nov 2004 9:19 PM
Body:
>From Dr Wes Munsil:
For me, adding this to my top-level project.properties file seemed to make
everything happy again:
maven.property.inheritance=true
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPIDEA-14
Here is an overview of the issue:
-
Key:
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPIDEA-13
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Trygve Laugstol
Created: Mon, 29 Nov 2004 5:45 PM
Body:
This issue should be closed and a new one created.
-
View this comment:
http://jira.codehaus.org
Message:
The following issue has been closed.
Resolver: Arnaud HERITIER
Date: Mon, 29 Nov 2004 5:31 PM
This image is generated from the javadoc tool. We didn't create it.
-
View the issue:
http://jira.codehaus.org
Hi,
About the first issue if you think there's a bug you can raise an issue in
JIRA, ideally with the proposed patch and a test case,
and I'll take a look.
About the maven.aspectj.dest if you provide a patch it can be applied, could
you file an improvement issue at JIRA?
Regards
Carlos Sanche
On Mon, 2004-11-29 at 14:32, Eric Pugh wrote:
> I don't know how this affects your question, but my immediate use case for
> maven-model is to load up a POM for a project, and then attempt to load up
> each dependencies POM. I'd like to be able to generate a report that lets
> me know that I am us
Message:
The following issue has been reopened.
Reopener: Adrian Tarau
Date: Mon, 29 Nov 2004 3:25 PM
But still... adding the source to dependencies...this remains
-
View the issue:
http://jira.codehaus.org/browse
The following comment has been added to this issue:
Author: Adrian Tarau
Created: Mon, 29 Nov 2004 3:23 PM
Body:
HmmmGood point...I will close the issue
-
View this comment:
http://jira.codehaus.org/browse/MP
Message:
The following issue has been closed.
Resolver: Adrian Tarau
Date: Mon, 29 Nov 2004 3:24 PM
Could cause problems with import order.
-
View the issue:
http://jira.codehaus.org/browse/MPIDEA-13
Here is an o
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1519
Here is an overview of the issue:
-
Key:
Hi Jason,
I thought the best was that the current one was always o.a.m.model.*,
and all the historical ones were included with package name.
ie in maven-model-4.0.0, there is just o.a.m.model; in maven-model-4.0.1
there is o.a.m.model.* and o.a.m.model.v400.*.
An exception is for the v3.0.0 seri
Celera Diagnostics company has an immediate contract opportunity for a
Maven Developer! The ideal candidate works on a continuous integration
system that is based on Apache Maven and its numerous plug-ins.
Skills / knowledge requirements:
The position requires at least 1 year of hands-on develop
I don't know how this affects your question, but my immediate use case for
maven-model is to load up a POM for a project, and then attempt to load up
each dependencies POM. I'd like to be able to generate a report that lets
me know that I am using the latest and greatest versioned artifact of each
Howdy,
There was a post on the user list about some fellow wanting to read in a
POM so I figured it would be a good opportunity to prepare some examples
for a maven-model release.
What we are doing now is generating the most current version of the
model is generated without versioning in the pac
The following comment has been added to this issue:
Author: Trygve Laugstol
Created: Mon, 29 Nov 2004 12:44 PM
Body:
You don't want to group the dependencies and thus change the order of the
libraries in the classpath. The reason is that this will cause the classpath to
be differ
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPIDEA-13
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPDIST-19
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1520
Here is an overview of the issue:
-
Key:
Howdy,
I was chatting with Brett on IRC so I thought I would bring the
discussion here. I would like to cut a release of m2 sometime in the
next 8 weeks but something I think would be really good would be to have
the core folks, and anyone else who desired to come, meet up somewhere
and discuss th
Howdy!
As I described before in one of my previous emails I would like to improve
the usability of maven generated websites and add the possibility of adding
links to parent modules.
The example of such functionality can be found here
http://style.tigris.org/nonav/docs/sampler_tigris.html
(I me
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
[...]
> >I feel that both your and mine solutions are hacks.
> >First one requires to override goals, second binds two
> plugins: site and
> >multiproject.
> >Before proposing my solution - which I hope will be the
> t
The following comment has been added to this issue:
Author: Matthias Kerkhoff
Created: Mon, 29 Nov 2004 8:50 AM
Body:
Same problem for ${maven.docs.src} (inherited value not used), but old
behaviour for ${maven.war.src}. Very strange...
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1519
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJIRA-7
Here is an overview of the issue:
-
Key: M
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-59
Here is an overview of the issue:
-
Ke
The following comment has been added to this issue:
Author: Felipe Leme
Created: Mon, 29 Nov 2004 7:29 AM
Body:
Why do you disagree? Which alternative do you think it's better than, the
postGoal approach?
-
View t
Then you can do
maven.multiproject.site.goal=site
or
maven.multiproject.site.goal=multiproject:site
depending on the context.
I feel that both your and mine solutions are hacks.
First one requires to override goals, second binds two plugins: site and
multiproject.
Before proposing my solution
Hello All,
Some days ago I have started to use aspectj plugin for compilation
aspects. I use aspects only for tests. I have following structure in
project:
-src
|
aspectj - aspect sources
|
java - application sources
|
test - test sources
I have an "lst" file where defined what files
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 28, 2004 9:07 PM
> To: Maven Developers List
> Subject: Re: one more time: [site&multiproject plugins] -
> reorganization
> of goals used to generate sites
>
>
> Michal Maczka wrote:
>
> > Som
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPEAR-29
Here is an overview of the issue:
-
Key: M
35 matches
Mail list logo
