Howdy,
For almost all JIRA components in the main Maven project that were for
components have been removed and a new JIRA project for that specific
plugin has been created.
I took the liberty of deleting some dupes, or issues that have been
fixed that were so trivial that I saw no problem removin
The following issue has been updated:
Updater: Jason van Zyl (mailto:[EMAIL PROTECTED])
Date: Sun, 30 Nov 2003 10:18 PM
Changes:
environment changed to
-
For a full history of the issue, see:
ht
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-444
Summary: md5sum in maven-new could b
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-388
Summary: Move util classes from the
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-411
Summary: Create the maven-cli-client
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-153
Summary: Wizard plugin breaks maven
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-684
Summary: maven-license-plugin doesn'
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-678
Summary: Log4JCategoryLog does not i
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-325
Summary: need to pass ssh command li
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-618
Summary: [Submission] Cruise Control
Only deletions have come to the list. I'm just not sure what point there is
of doing anything to issues that are already closed.
- Brett
> -Original Message-
> From: Jason van Zyl [mailto:[EMAIL PROTECTED]
> Sent: Monday, 1 December 2003 1:59 PM
> To: Maven Developers List
> Subject: Re:
On Sun, 2003-11-30 at 21:27, Brett Porter wrote:
> Is there a reason that CLOSED bugs are being deleted from JIRA? This will
> mess up some history I imagine, especially since some of the relate to Maven
> core anyway.
Deleting what I think can go, most stuff I'm moving but that doesn't
appear to
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-787
Summary: Single plugin build fails w
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-960
Summary: convert-snapshot does nothi
Is there a reason that CLOSED bugs are being deleted from JIRA? This will
mess up some history I imagine, especially since some of the relate to Maven
core anyway.
- Brett
--
Brett Porter
Team Leader, Core Systems
f2 network ~ everything essential
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-1
Summary: dist:deploy should respect
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-2
Summary: deploy:dist does not create t
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-3
Summary: Separate deploy:dist from sha
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-30
Summary: SNAPSHOT jars should not use
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-636
Summary: distributions get deployed
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-934
Summary: multiproject and dist ton't
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-249
Summary: custom tag define in reacto
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-257
Summary: Reactor problem with some p
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-414
Summary: Reactor does not read prope
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-440
Summary: Reactor handles badly goals
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-463
Summary: Project properties overwrit
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-465
Summary: [PATCH] set failure propert
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-442
Summary: Reactor does not correctly
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-920
Summary: Can't combine mutliproject:
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-546
Summary: reactor includes only one p
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-469
Summary: CVS HEAD Broken - build fai
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-953
Summary: Release maven-release-plugi
The following comment has been added to this issue:
Author: Jason van Zyl
Created: Sun, 30 Nov 2003 7:50 PM
Body:
I plan to which I noted in an email I sent to one of the lists. That I would take the
stuff from db.apache.org, which predates the multiproject plugin, and modify it t
Hokey doke.
I'll wait.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Brett Porter <[EMAIL PROTECTED]> wrote on 01/12/2003 09:15:49 AM:
> Hi dIon,
>
> Sorry for the late reply. I rolled in Jason's bootstrap changes and
moved
> the branch Wednesday nig
The following comment has been added to this issue:
Author: dion gillard
Created: Sun, 30 Nov 2003 7:02 PM
Body:
Why don't we eat our own dogfood and use multiproject?
-
View the issue:
http://jira.codehaus.org/
Hi dIon,
Sorry for the late reply. I rolled in Jason's bootstrap changes and moved
the branch Wednesday night and have been moving ever since. I tried this
today and noticed the same thing. The reason is that the new code only loads
the unpacked plugins of those that have a corresponding .jar in
$
Hi,
I have now removed all plugin components from the Maven core that have
no issues associated with them. So all plugin components that are now
there need to be dealt with. I notice for lots of plugins that have been
separated they still have issues associated with them in the core.
If you have
Message:
The following issue has been closed.
Resolver: Jason van Zyl
Date: Sun, 30 Nov 2003 3:48 PM
Updated.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-925
Here is an overview o
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-1047
Summary: [patch] genapp uses user-d
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-1053
Summary: [patch] genapp filtering s
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-1052
Summary: [patch] genapp fails to fi
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-1046
Summary: [patch] genapp ignores mav
Message:
The following issue has been deleted from JIRA.
-
Here is an overview of the issue:
-
Key: MAVEN-1045
Summary: [patch] genapp should incl
Message:
The following issue has been closed.
Resolver: Jason van Zyl
Date: Sun, 30 Nov 2003 3:32 PM
Patches applied.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPGENAPP-1
Here is an o
jvanzyl 2003/11/30 13:26:27
Modified:genapp plugin.jelly plugin.properties project.xml
genapp/xdocs changes.xml properties.xml
Log:
o applying patches for MPGENAPP-1
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPGENAPP-1
Revision ChangesPath
1
Message:
The following issue has been closed.
Resolver: Jason van Zyl
Date: Sun, 30 Nov 2003 3:23 PM
Patch applied.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPHIBERNATE-1
Here is an
jvanzyl 2003/11/30 13:17:51
Modified:hibernate/src/main/org/apache/maven/hibernate/beans
SchemaExportBean.java
hibernate/src/main/org/apache/maven/hibernate/jelly
SchemaExportTag.java
hibernate/xdocs changes.xm
Howdy,
I was going to direct changes in the top-level site module (maven-site)
to the [EMAIL PROTECTED] list.
There is a [EMAIL PROTECTED] list now BTW :-)
--
jvz.
Jason van Zyl
[EMAIL PROTECTED]
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and tec
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPA-9
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=MPA-8
Here is an overview of the issue:
--
The following issue has been updated:
Updater: Shaposhnikov Konstantin (mailto:[EMAIL PROTECTED])
Date: Sun, 30 Nov 2003 1:33 PM
Comment:
patch
Changes:
Attachment changed to diff3
-
For a full
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MPHIBERNATE-1
Here is an overview of the issue:
--
On Sun, 2003-11-30 at 05:16, Konstantin Shaposhnikov wrote:
> Hello,
>
> I've just update my CVS sources and it seems to me that you
> have applied only part of my patch (project.properties,
> project.xml and plugin.jelly files), but there were no
> changes to the sources (SchemaExportBean.java an
> -Original Message-
> From: Konstantin Shaposhnikov [mailto:[EMAIL PROTECTED]
> Sent: Sunday, November 30, 2003 11:16 AM
> To: Maven Developers List
> Subject: Re: patch for hibernate plugin : add delimiter property
>
>
> Hello,
>
> I've just update my CVS sources and it seems to me that
evenisse2003/11/30 03:20:28
Modified:changelog/xdocs properties.xml
Log:
Fix documentation
Revision ChangesPath
1.4 +1 -1 maven-plugins/changelog/xdocs/properties.xml
Index: properties.xml
=
Hello,
I've just update my CVS sources and it seems to me that you
have applied only part of my patch (project.properties,
project.xml and plugin.jelly files), but there were no
changes to the sources (SchemaExportBean.java and
SchemaExportTag.java files). Should I create JIRA issue for
that?
As
* Alain Javier Guarnieri del Gesu <[EMAIL PROTECTED]> [2003-11-28 23:55]:
> * 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
57 matches
Mail list logo
