The following comment has been added to this issue:
Author: dion gillard
Created: Tue, 5 Aug 2003 9:19 AM
Body:
damn, applied the wrong patch
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=
The following issue has been updated:
Updater: Tim Anderson (mailto:[EMAIL PROTECTED])
Date: Fri, 8 Aug 2003 1:21 AM
Comment:
patch for src/plugins-build/war/plugin.jelly
Changes:
Attachment changed to plugin.jelly.patch
-
Sounds like a good one.
File it in Jira and I'll schedule it.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Colin Sampaleanu <[EMAIL PROTECTED]> wrote on 05/08/2003 04:42:49 AM:
> If an artifact is not available in the remote repo(s), but is available
dion2003/08/07 09:56:39
Modified:src/java/org/apache/maven/verifier Tag: MAVEN_RC1_STABLE
DependencyVerifier.java
src/java/org/apache/maven/jelly Tag: MAVEN_RC1_STABLE
JellyUtils.java
src/java/org/apache/ma
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-657
Here is an overview of the issue:
--
Hi all,
I am working on a Maven wrapper to the findbugs tool. Findbugs works
similar to PMD.
Findbugs is licensed under LGPL.. Does this mean the plugin could NOT go in
the maven core due to Apache licensing?
Information about findbugs is available here:
http://www.cs.umd.edu/~pugh/java/bugs/
dion2003/08/07 09:52:38
Modified:xdocs/reference Tag: MAVEN_RC1_STABLE dirlayout.xml
user-guide.xml project-descriptor.xml
xdocsTag: MAVEN_RC1_STABLE navigation.xml faq.fml
xdocs/start Tag: MAVEN_RC1_STABLE integrate.xml
I'm confused.
My understanding is:
- So RC1_STABLE is the branch people should be using if they want to build
and use latest maven and do bits and pieces development
- HEAD will be full of upheaval like renaming all of the properties in
plugins and likely be unstable until RC1
- for RC1, all fixes
Are you expecting that this will be merged back into HEAD, or HEAD
merged into this in the future? Unfortuntately I think your chance of
merging 2 diverged branches (where ongoing work has gone on in both)
with CVS is next to nil. What is probably more realistic is for Jason
or whoever to do
The following comment has been added to this issue:
Author: dion gillard
Created: Thu, 7 Aug 2003 12:10 AM
Body:
in cvs head the properties for ALL plugins will change.
There is currently no compatibility layer
-
The following comment has been added to this issue:
Author: dion gillard
Created: Tue, 5 Aug 2003 3:32 AM
Body:
Doesn't jelly use jaxp to determine it's sax parser?
-
View the issue:
http://jira.codehaus.org/sec
The following comment has been added to this issue:
Author: dion gillard
Created: Wed, 6 Aug 2003 9:46 PM
Body:
If you're happy this is a dupe of MAVEN-609, can I close this issue?
-
View the issue:
http://jira.
Eric Pugh wrote:
> Findbugs is licensed under LGPL.. Does this mean the plugin could NOT go in
> the maven core due to Apache licensing?
Yes, the policy is that no source code in ASF projects may compile- and
link-depend on GPL and LGPL code. Therefore your plugin can't go into
maven repository.
evenisse2003/08/05 02:14:26
Modified:src/plugins-build/war plugin.jelly
Log:
Test if sources is present before copy classes in webapp.
Revision ChangesPath
1.25 +8 -6 maven/src/plugins-build/war/plugin.jelly
Index: plugin.jelly
===
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-656
Here is an overview of the issue:
--
15 matches
Mail list logo
