Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1022
Here is an overview of the issue:
-
The following issue has been updated:
Updater: David Eric Pugh (mailto:[EMAIL PROTECTED])
Date: Tue, 11 Nov 2003 2:19 AM
Comment:
These all go in the /repo/findbugs/jars directory.
Changes:
Attachment changed to findbugs-0.7.0.jar
---
The following issue has been updated:
Updater: David Eric Pugh (mailto:[EMAIL PROTECTED])
Date: Tue, 11 Nov 2003 2:20 AM
Changes:
Attachment changed to findbugs-ant-0.7.0.jar
-
For a full history of
The following issue has been updated:
Updater: David Eric Pugh (mailto:[EMAIL PROTECTED])
Date: Tue, 11 Nov 2003 2:20 AM
Changes:
Attachment changed to findbugs-coreplugin-0.7.0.jar
-
For a full his
dIon,
I don't quite agree. Each of these plugins are separate. Sharing the
same properties ties them together. I would agree, provided the
multiproject plugin provides some useful infrastructure for all plugins
dealing with several projects. In which case the other plugins would
"extend" it and it
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: 10 November 2003 22:05
> To: 'Maven Developers List'
> Subject: RE: [changes] New goal for release report!
>
> This isn't the first attempt actually - from what I understand
> multiproject's dependency convergenc
Vincent Massol wrote:
dIon,
I don't quite agree. Each of these plugins are separate. Sharing the
same properties ties them together. I would agree, provided the
multiproject plugin provides some useful infrastructure for all plugins
dealing with several projects. In which case the other plugins w
> -Original Message-
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> Sent: 11 November 2003 11:16
> To: Maven Developers List
> Subject: Re: cvs commit:
maven-plugins/multichanges/src/plugin-resources
> releases.jsl
>
> Vincent Massol wrote:
>
> >dIon,
> >
> >I don't quite agree. Each
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 11/11/2003 09:14:34 PM:
[snip]
> A way this could be done is by registering a jsl with a multireport
> plugin (I think multiproject should be renamed multisite and the
> convergence report extracted from it).
Multiproject is about more than producing
Hi,
Shouldn't we define project deliverables in the POM? I think this could
be very useful. Let me give some potential usages:
- ability to automatically say "build me this project", whether the
project generates a war, an ejb, an ear, a jar, a plugin jar, etc. ATM,
there is no way to recognize a
Hi dIon,
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: 11 November 2003 13:02
> To: Maven Developers List
> Subject: RE: [changes] New goal for release report!
>
> "Vincent Massol" <[EMAIL PROTECTED]> wrote on 11/11/2003 09:14:34
PM:
>
> [snip]
> > A wa
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1023
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Joakim Erdfelt (mailto:[EMAIL PROTECTED])
Date: Tue, 11 Nov 2003 6:29 AM
Comment:
See primary report for details of what this patch contains.
Changes:
Attachment changed to maven-pmd-docu2.patch
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 11/11/2003 07:54:55 PM:
> dIon,
>
> I don't quite agree. Each of these plugins are separate. Sharing the
> same properties ties them together. I would agree, provided the
> multiproject plugin provides some useful infrastructure for all plugins
> deal
For 1/, yes, there is already the multiproject plugin and the reactor.
Are we saying we want to deprecate the reactor and promote using the
multiproject plugin. Isn't that a bit too "heavy". Unless the
multiproject offers additional features of course (I have to admit I
haven't looked too far in
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1024
Here is an overview of the issue:
-
"Vincent Massol" <[EMAIL PROTECTED]> wrote on 11/11/2003 11:26:14 PM:
> Hi dIon,
[snip]
> This is not my intent. It's simply from my lack of understanding. We'll
> fix that and come to an agreement I'm sure. I just need to understand a
> bit more. Please be patient with me :-)
Sure, I've got lots
dion2003/11/11 04:59:33
Modified:cruisecontrol/xdocs properties.xml
Log:
Update docs with fixed typo
Revision ChangesPath
1.2 +1 -1 maven-plugins/cruisecontrol/xdocs/properties.xml
Index: properties.xml
===
Vincent Massol wrote:
Hi,
Shouldn't we define project deliverables in the POM? I think this could
be very useful. Let me give some potential usages:
- ability to automatically say "build me this project", whether the
project generates a war, an ejb, an ear, a jar, a plugin jar, etc. ATM,
there is
> -Original Message-
> From: Michal Maczka [mailto:[EMAIL PROTECTED]
> Sent: 11 November 2003 14:21
> To: Maven Developers List
> Subject: Re: [Proposal] Project deliverables definition in POM
>
> Vincent Massol wrote:
>
> >Hi,
> >
> >Shouldn't we define project deliverables in the POM?
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1025
Here is an overview of the issue:
-
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, November 11, 2003 6:50 PM
> To: 'Maven Developers List'
> Subject: RE: [Proposal] Project deliverables definition in POM
>
>
>
>
> > -Original Message-
> > From: Michal Maczka [mailto:[EMAIL PRO
> > >
> > > Why type is not sufficient?
> >
> > Adding a type would be a good first step. But a project
> does not have a
> > single deliverable.
> >
>
> Sorry but I don't understand:
> Aren't artifactId and groupId always the same for all deliverables ?
> (please forget about the fact that mave
> Assuming a 1 to 1 relationship with groupId and artifactId would
> be harmful for many projects. (including mine. ;-)
>
I didn't mean that artifactId=groupId :)
I meant that the same artifactId and groupId are shared between two or more
artifacts.
Just their types are different.
For example:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1026
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Andy Jefferson (mailto:[EMAIL PROTECTED])
Date: Tue, 11 Nov 2003 3:35 PM
Changes:
Attachment changed to jpox-1.0.0-alpha-3.jar
-
For a full history of
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1027
Here is an overview of the issue:
-
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1028
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Scott Foster (mailto:[EMAIL PROTECTED])
Date: Tue, 11 Nov 2003 7:12 PM
Comment:
Let me know if this patch is in the wrong format.
Changes:
Attachment changed to javac.patch
--
Hi,
I've come up against a problem whilst developing an ejb code generation plugin.
outline of what the plugin does
1) generates all ejb sources from a single ejb java file (remote, home, local,
localHome, descriptors etc).
2) These sources are placed in target/ejbgen
3) target/ejbgen dir added
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1029
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Tue, 11 Nov 2003 9:47 PM
Changes:
summary changed from documentation out of date
-
For a full history of
32 matches
Mail list logo
