The following comment has been added to this issue:
Author: Shaposhnikov Konstantin
Created: Fri, 1 Aug 2003 1:59 AM
Body:
I think that such goals as jar:deploy, jar:deploy-snapshot, jar:install,
jar:install-snapshot should be handled using maven-artifact-plugin. You can see how
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Fri, 1 Aug 2003 12:50 AM
Changes:
Fix Version changed to 1.1
-
For a full history of the issue, see:
h
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-641
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 31 Jul 2003 11:44 PM
Body:
Any pointers as to where in the core?
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Thu, 31 Jul 2003 11:34 PM
Applied with fixes and docs
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-633
He
dion2003/07/31 21:30:31
Modified:src/plugins-build/ejb/xdocs properties.xml
src/plugins-build/ejb plugin.jelly plugin.properties
Log:
Applied patch for MAVEN-633, fixed patch rejections, added documentation
Revision ChangesPath
1.3 +20 -0 mave
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Thu, 31 Jul 2003 11:24 PM
Updated documentation to show how to override
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?
dion2003/07/31 21:21:02
Modified:src/plugins-build/war/xdocs properties.xml
Log:
Add docs on maven.war.final.name
Revision ChangesPath
1.4 +12 -0 maven/src/plugins-build/war/xdocs/properties.xml
Index: properties.xml
==
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 31 Jul 2003 11:20 PM
Body:
I believe it is possible to override the default name by setting the
maven.war.final.name property in project.properties.
-
Last 500 lines of a clean bootstrap build of maven at 20030731-2200
[exec] test:test:
[exec] jar:jar:
[exec] [jar] Building jar:
/usr/local/builds/maven/src/maven/src/plugins-build/was40/target/maven-was40-plugin-1.0.jar
[exec] [copy] Copying 1 file to /home/tirsen
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 9:29 PM
Changes:
Fix Version changed to 1.1
-
For a full history of the issue, see:
h
bwalding2003/07/31 19:16:08
Added: src/plugins-build/junit-report/src/plugin-resources
junit-failed.jsl
Log:
Start of new report that only shows failed test reports
*** This one uses the old location of the tool beans. Will need some fixing at short
notic
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 9:19 PM
Comment:
Do you have a patch?
Changes:
Fix Version changed to 1.0-rc1
-
For
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 9:17 PM
Changes:
Fix Version changed to 1.0-rc1
-
For a full history of the issue, see:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-640
Here is an overview of the issue:
--
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 9:15 PM
Changes:
Comment changed from to
-
For a full history of the issue, see:
ht
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 31 Jul 2003 9:15 PM
Body:
looks like groupId is not being inherited correctly
-
View the issue:
http://jira.codehaus.org/sec
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 9:13 PM
Changes:
description changed from A subproject which inherits most of its pom
(including dependencies) from a parent project has a problem with one of
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 31 Jul 2003 9:13 PM
Body:
it appears groupId is not inherited correctly
-
View the issue:
http://jira.codehaus.org/secure/Vi
Rafal,
I've added the ability for normal jira users to edit the issues.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Rafal Krzewski <[EMAIL PROTECTED]> wrote on 31/07/2003 08:17:20 PM:
> [EMAIL PROTECTED] wrote:
> > If you have a fix or a change you wo
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 9:07 PM
Changes:
Fix Version changed to 1.1
-
For a full history of the issue, see:
h
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 9:02 PM
Changes:
Fix Version changed to 1.1
-
For a full history of the issue, see:
h
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 9:01 PM
Changes:
Fix Version changed to 1.1
-
For a full history of the issue, see:
h
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-639
Here is an overview of the issue:
--
> James CE Johnson wrote:
>
>>
>>... lots of common stuff like
>>
>>
>>
>> Then in weblogic:ejbdoclet you would have this:
>>
>>
>>... lots of common stuff like
>>
>>
>>
>> How do we avoid duplicating all of the common stuff (ejbdoclet
>> attributes and subtasks) in an easy to
> I guess I'm having trouble figuring out how you would do that cleanly
> without duplicating a lot of jelly script.
>
> In jboss:ejbdoclet you would have this:
>
>
>... lots of common stuff like
>
>
>
> Then in weblogic:ejbdoclet you would have this:
>
>
>... lots of common stuff l
> -Original Message-
> From: Brian Towles [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 31, 2003 5:57 PM
> To: Maven Developers List
> Subject: RE: EJB plugin modification
>
>
>
> On Thu, 2003-07-31 at 03:54, Michal Maczka wrote:
> > IMHO the correct workflow which should be supported
> James CE Johnson wrote:
>
>>
>>... lots of common stuff like
>>
>>
>>
>> Then in weblogic:ejbdoclet you would have this:
>>
>>
>>... lots of common stuff like
>>
>>
>>
>> How do we avoid duplicating all of the common stuff (ejbdoclet
>> attributes and subtasks) in an easy to
On Thu, 2003-07-31 at 03:54, Michal Maczka wrote:
> IMHO the correct workflow which should be supported by ejb plugin looks
> like follows:
>
> a) gather all the files which will be packaged in ejb-jar in one place
> (equivalent of war:webapp)
> b) archive this directory (equivalent of war:war
James CE Johnson wrote:
>
>... lots of common stuff like
>
>
>
> Then in weblogic:ejbdoclet you would have this:
>
>
>... lots of common stuff like
>
>
>
> How do we avoid duplicating all of the common stuff (ejbdoclet attributes
> and subtasks) in an easy to maintain way?
The following issue has been updated:
Updater: James CE Johnsom (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 10:08 AM
Changes:
Attachment changed to ejb:ejbdoclet.patch
-
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-638
Here is an overview of the issue:
--
>
>
>>
>> Do you want to have a jboss:ejbdoclet and a weblogic:ejbdoclet goal
>> when both of them are going to be 80% the same?
>>
>
> Yeap! I would like to see them as two separate projects.
I guess I'm having trouble figuring out how you would do that cleanly
without duplicating a lot of jelly
>
> Do you want to have a jboss:ejbdoclet and a weblogic:ejbdoclet goal when
> both of them are going to be 80% the same?
>
Yeap! I would like to see them as two separate projects.
AFAIK XDoclet team (I know this from mailing lists not from developers) is
not going to maintain as many plugin a
>>
>> a) Because it can generate code for multiple appservers it doesn't
>> make
>>sense to invoke it in a container-specific plugin.
>>
>
> IMHO it does make sense.
But my point is that the task is *mostly* the same for any
appserver. Its only when you add the subtasks that it gets appserve
> -Original Message-
> From: James CE Johnson [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 31, 2003 2:44 PM
> To: [EMAIL PROTECTED]
> Subject: RE: EJB plugin modification
>
> Hi Michal,
>
> My $.02 worth... I'm biased towards invoking xdoclet, however, which is a
> slightly differe
Hi Michal,
My $.02 worth... I'm biased towards invoking xdoclet, however, which is a
slightly different focus than Brian (I think) so my replies may not be
100% compatible with yours.
> Hi Brian!
>
> I don't like the idea of making fatter ejb:plugin
> and putting there a logic which is particula
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-637
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-636
Here is an overview of the issue:
--
The following issue has been updated:
Updater: James CE Johnsom (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 7:31 AM
Changes:
Fix Version changed to 1.0-rc1
-
For a full history of the issue, s
The following issue has been updated:
Updater: James CE Johnsom (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 7:30 AM
Changes:
Fix Version changed to 1.0-rc1
-
For a full history of the issue, s
> If you have a fix or a change you would like to be in maven 1.0, please
> ensure that:
>
> 1) It's in Jira (
> http://jira.codehaus.org/secure/BrowseProject.jspa?id=10030 )
MAVEN-632 Please add maven.ejb.excludes to ejb:ejb goal
MAVEN-633 Contributing an ejb:ejb-client goal
I've got more contri
Please consider to fix the bug MAVEN-563
(http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-563) in the
final version. :-)
[EMAIL PROTECTED] wrote:
If you have a fix or a change you would like to be in maven 1.0, please
ensure that:
1) It's in Jira (
http://jira.codehaus.org/secure/Br
On Thu, 2003-07-31 at 06:17, Rafal Krzewski wrote:
> [EMAIL PROTECTED] wrote:
> > If you have a fix or a change you would like to be in maven 1.0, please
> > ensure that:
> >
> > 1) It's in Jira
> > 2) it's in the roadmap
> >
> > If it's not, it wont be looked at for the release.
> >
> > Ther
The following issue has been updated:
Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 7:08 AM
Changes:
Fix Version changed to 1.0-rc1
-
For a full history of the issue, see:
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 7:07 AM
Comment:
and again, this time with forehead.conf! :)
please disregard all others
Changes:
Attachment changed to MAVEN-470-final.diff
--
The following issue has been updated:
Updater: Brett Porter (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 7:01 AM
Comment:
resubmitting patch, post refragtering :)
supercedes both previous patches, includes all fixes
Changes:
Attachment changed to MAVEN-470-ag
The following issue has been updated:
Updater: Rafal Krzewski (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 5:28 AM
Comment:
Refreshed the patch - will apply cleanly against HEAD as of 2003-08-31, 10:30 GMT
Changes:
Attachment changed to developerConnection2.dif
[EMAIL PROTECTED] wrote:
> If you have a fix or a change you would like to be in maven 1.0, please
> ensure that:
>
> 1) It's in Jira
> 2) it's in the roadmap
>
> If it's not, it wont be looked at for the release.
>
> There are a whole heap of bugs listed as unscheduled
>
> These WILL NOT be
Hi Brian!
I don't like the idea of making fatter ejb:plugin
and putting there a logic which is particular to some application server.
IMHO the correct workflow which should be supported by ejb plugin looks
like follows:
a) gather all the files which will be packaged in ejb-jar in one place
(eq
The following comment has been added to this issue:
Author: Andy Jefferson
Created: Thu, 31 Jul 2003 3:27 AM
Body:
No patches added since Michal Maczka has said several times on the mailing list that
he has enabled this in the past and backed it out due to complaints by others. Th
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-635
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 31 Jul 2003 2:57 AM
Body:
Where are the patches for this?
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?k
The following comment has been added to this issue:
Author: Norbert Pabis
Created: Thu, 31 Jul 2003 2:30 AM
Body:
After further investigation I found that it does not work
only in iso-8859-1 and utf-8 output encoding.
---
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 2:20 AM
Changes:
Fix Version changed to 1.0-rc1
-
For a full history of the issue, see:
Message:
The following issue has been closed.
Resolver: dion gillard
Date: Thu, 31 Jul 2003 2:20 AM
Fixed last week
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-592
Here is an over
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 2:19 AM
Changes:
description changed from I have the following dependencies in my
project.xml
??? xdoclet
??? xdoclet-ejb-module
??? 1.2b4
??? http://xdoclet.
The following issue has been updated:
Updater: dion gillard (mailto:[EMAIL PROTECTED])
Date: Thu, 31 Jul 2003 2:19 AM
Changes:
Fix Version changed to 1.0-rc1
-
For a full history of the issue, see:
58 matches
Mail list logo
