Howdy,
Anyone know how to do this. I'm going to flush a bunch of issues listed
in the core into separate plugin projects but I don't want to clutter
the default dashboard with 50 maven plugin projects.
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for
Vincent,
Is there an easy way to transfer issues to another project? I'm going to
continue your work on creating separate projects and I want to start
transfering issues to their respective plugins. Is this the approach you
took? I'll just follow in your footsteps.
Have
--
jvz.
Jason van Zyl
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPA-5
Here is an overview of the issue:
--
The following comment has been added to this issue:
Author: Jason van Zyl
Created: Fri, 28 Nov 2003 6:19 PM
Body:
Request for the mailing list redirection has been made on [EMAIL PROTECTED]
-
View the issue:
htt
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPA-4
Here is an overview of the issue:
--
* Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> [2003-11-27 21:41]:
> Dion?
>
> I've fixed the problem I was having with Javadoc linking. I create a
> temporary directory and copy the source fields specified by the
> includes and excludes. I then run Javadoc on that directory. It
> works wel
Vincent,
Perhaps just keep it simple. Only indicate what the minimum Maven version that
the plugin needs. Going beyond that will get extremely complex IMO.
I wouldn't bother failing either even if the plugin is run in a maven older than
that stated in the plugin POM. Maybe just give a warning
Yes, I would prefer to keep some goal that puts the expanded plugin jar into my
plugin cache only. Call it what you will, but perhaps it could mention
installing the plugin to cache i.e. plugin:install-to-cache or whatever.
The use case is when you are sharing your local repo with other develope
Message:
The following issue has been closed.
Resolver: Jason van Zyl
Date: Fri, 28 Nov 2003 10:25 AM
URL updated.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPGENAPP-2
Here is an over
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPGENAPP-2
Here is an overview of the issue:
-
The following issue has been updated:
Updater: Jörg Schaible (mailto:[EMAIL PROTECTED])
Date: Fri, 28 Nov 2003 10:16 AM
Comment:
Completely rewritten xdocs/changes.xml. Undocumented properties added, new
functionality for user-defined filter parameters included. A native speaker ma
The following issue has been updated:
Updater: Jörg Schaible (mailto:[EMAIL PROTECTED])
Date: Fri, 28 Nov 2003 10:12 AM
Comment:
Patch for xdocs/changes.xml.
Caution: Accumulates all patches (all unapplied) to this file from MAVEN-1045,
MAVEN-1046, MAVEN-1047, MAVEN-1052 and MAVEN
The following issue has been updated:
Updater: Jörg Schaible (mailto:[EMAIL PROTECTED])
Date: Fri, 28 Nov 2003 10:09 AM
Comment:
Patch for project.xml. Fixes unapplied patch for this file from MAVEN-1045.
Changes:
Attachment changed to project.xml.diff
-
The following issue has been updated:
Updater: Jörg Schaible (mailto:[EMAIL PROTECTED])
Date: Fri, 28 Nov 2003 10:07 AM
Comment:
Replacement for plugin.properties. Entries have been added and existing ones
restructured to allow an easier overview for an user to define his own filte
The following issue has been updated:
Updater: Jörg Schaible (mailto:[EMAIL PROTECTED])
Date: Fri, 28 Nov 2003 10:03 AM
Comment:
Patch for plugin.jelly.
CAUTION: Accumulates open issues MAVEN-1047, MAVEN-1052 and MAVEN-1053
Changes:
Attachment changed to plugin.jell
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPGENAPP-1
Here is an overview of the issue:
-
[EMAIL PROTECTED] wrote on Friday, November 28, 2003 1:29 AM:
> Jörg Schaible <[EMAIL PROTECTED]> wrote on 28/11/2003
> 02:17:16 AM:
> [snip]
So is there any solution to create such assembled variables?
>>>
>>>
>>> Use something like this:
>>>
>>> var="variable">jdbc.datab
Hi,
first of all, I apologize, but I didn't find a bug tracking system for
maven. I clicked some time through the web site, did a google search,
but no luck. So if this is out of place, don't shout at me, just
redirect me.
I decided to give maven a try and found a problem in the very first
st
Jason van Zyl wrote:
> plugin:deploy sounds like it should deploy to the remote repo. Is there
> no plugin:install for just doing things locally?
General contract was that :install would deploy the artifact into
the local repository. plugin:install does that, plus it installs the
plugin into MAVE
vmassol 2003/11/28 00:15:48
Added: clover/src/plugin-test .cvsignore
Log:
ignore target/ dir
Revision ChangesPath
1.1 maven-plugins/clover/src/plugin-test/.cvsignore
Index: .cvsignore
==
vmassol 2003/11/28 00:14:35
Modified:clover project.xml
clover/xdocs changes.xml
Log:
continue work for 1.4
Revision ChangesPath
1.26 +6 -1 maven-plugins/clover/project.xml
Index: project.xml
==
vmassol 2003/11/28 00:12:14
Modified:clover/xdocs properties.xml navigation.xml index.xml
goals.xml changes.xml
clover project.xml
Removed: clover/xdocs futures.xml build-file.xml dirlayout.xml
Log:
- Reworked documentation
- Prepare t
vmassol 2003/11/28 00:11:29
Modified:changes/src/plugin-test .cvsignore
Log:
ignore maven.log
Revision ChangesPath
1.2 +1 -0 maven-plugins/changes/src/plugin-test/.cvsignore
Index: .cvsignore
==
The following comment has been added to this issue:
Author: Florin Vancea
Created: Fri, 28 Nov 2003 1:48 AM
Body:
Sorry for being rather briefer than clearer :)
I mean that when starting, JBoss "deploys" that file. One can check for that file's
deployment status using RMI or HTTP
The following comment has been added to this issue:
Author: Vincent Massol
Created: Fri, 28 Nov 2003 1:33 AM
Body:
Florin, what do you mean by waiting on a file?
-
View the issue:
http://jira.codehaus.org/secure
25 matches
Mail list logo
