The maven-plugins team is pleased to announce the WebSphere 4.0 Plug-in 1.4.1
release!
http://maven-plugins.sourceforge.net/maven-was40-plugin/
A plugin to manage a WebSphere AppServer 4 installation
Changes in this version include:
Fixed bugs:
o Fix typo in was40:deploy-ear goal
To au
On Sun, 18 Jul 2004, Mark R. Diggory wrote:
1.) do not allow any interim content into www/dist. Interm content gets
placed under cvs.apache.org/repository. This gives us a means to allow
testing of interim content while not having all the mirrors (including
ibibilio and the archive) get flooded wit
The 1.1 JavaCC plugin for Maven list
appears to ignore the maven.javacc.javacc.target.dir and maven.javacc.jtree.target.dir
listed on its website. These need to be configurable because, althought
the source is generated output, it must still be kept in a our CVS and
so the target must be to the
The following comment has been added to this issue:
Author: Ray Roberts
Created: Mon, 19 Jul 2004 11:45 PM
Body:
You should be able to send in the following to the javadoc task:
additionalparam="-J-DproxyHost=myproxyhost.com -J-DproxyPort=8080"
Seems to be working fo
I agree with you.
+1 for me.
I'll release the plugin tomorrow.
Arnaud
> -Message d'origine-
> De : Dion Gillard [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 19 juillet 2004 23:00
> À : Maven Developers List
> Objet : Re: RE : [maven-ant-plugin] [vote] release 1.7.1 or 1.8
>
> Let's do the
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 19 Jul 2004 5:02 PM
Body:
Have a look in the distributions, that's where the license is. The license shown on
the web site is secondary and unimportant compared to the one in the shipped product
Let's do the release now,
release early and often.
On Mon, 19 Jul 2004 22:41:48 +0200, Arnaud Heritier
<[EMAIL PROTECTED]> wrote:
> I fixed MPANT-9 but I don't know how to fix MPANT-7 with Jelly.
> I need a Jelly guru to do it.
> I have the idea for the algorithm but for the implementation, I'm no
I fixed MPANT-9 but I don't know how to fix MPANT-7 with Jelly.
I need a Jelly guru to do it.
I have the idea for the algorithm but for the implementation, I'm not enough talented
:-)
What do we do? We try to fix MPANT-7 or we release the plugin?
Arnaud
> -Message d'origine-
> De : Dio
aheritier2004/07/19 13:16:45
Modified:ant/xdocs changes.xml
Log:
update changes
Revision ChangesPath
1.25 +1 -1 maven-plugins/ant/xdocs/changes.xml
Index: changes.xml
===
RCS file: /home/cv
aheritier2004/07/19 13:08:57
Modified:ant/src/plugin-resources/templates build.jelly
Log:
Don't compile tests classes if junit isn't present.
Revision ChangesPath
1.22 +6 -3 maven-plugins/ant/src/plugin-resources/templates/build.jelly
Index: build.jelly
=
Message:
The following issue has been closed.
Resolver: Arnaud HERITIER
Date: Mon, 19 Jul 2004 2:18 PM
fixed. Thanks.
-
View the issue:
http://jira.codehaus.org/browse/MPANT-9
Here is an overview of the issue:
--
aheritier2004/07/19 11:13:09
Modified:ant/src/plugin-resources/templates build.jelly
Log:
Remove unused code
Revision ChangesPath
1.21 +0 -18 maven-plugins/ant/src/plugin-resources/templates/build.jelly
Index: build.jelly
==
aheritier2004/07/19 11:12:04
Modified:ant/src/plugin-resources/templates build.jelly
Log:
Remove old duplicated code to copy resources for tests
Revision ChangesPath
1.20 +3 -35 maven-plugins/ant/src/plugin-resources/templates/build.jelly
Index: build.jelly
aheritier2004/07/19 11:08:34
Modified:ant/src/plugin-resources/templates build.jelly
Log:
Replace some && by and in jelly tests
Revision ChangesPath
1.19 +3 -3 maven-plugins/ant/src/plugin-resources/templates/build.jelly
Index: build.jelly
===
aheritier2004/07/19 10:59:04
Modified:ant/src/plugin-resources/templates build.jelly
ant/xdocs changes.xml
Log:
MPANT-9 : Add ant's setproxy tag.
Revision ChangesPath
1.18 +7 -0 maven-plugins/ant/src/plugin-resources/templates/build.jelly
Ind
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1382
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Augustinus Deimel
Created: Mon, 19 Jul 2004 10:57 AM
Body:
with maven 1.0 (final) this issue is "nearly" resolved insofar
that you can add a Class-Path entry in the manifest-File now for
the dependents if you like.
One lit
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1381
Here is an overview of the issue:
-
Key:
The following issue has been updated:
Updater: Felipe Leme (mailto:[EMAIL PROTECTED])
Date: Mon, 19 Jul 2004 10:12 AM
Comment:
Vince,
Looks like nobody in the list was interested in this discussion :-(
So, here is a new patch using your simpler solution.
Regards,
Felipe
C
Yes, copy the overridden jar to the lib directory. That's the only
thing that makes sense.
On Mon, 19 Jul 2004 15:55:05 +0200, Heritier Arnaud <[EMAIL PROTECTED]> wrote:
> Yes but what can we do ?
> Do you have an idea to replace when needed the get task by a copy ?
>
> Arnaud
>
> > -Mes
Yes but what can we do ?
Do you have an idea to replace when needed the get task by a copy ?
Arnaud
> -Message d'origine-
> De : Jerome Lacoste [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 19 juillet 2004 15:34
> À : Maven Developers List
> Objet : Re: [maven-ant-plugin] [vote] release 1.7
Message:
The following issue has been closed.
Resolver: Vincent Massol
Date: Mon, 19 Jul 2004 9:50 AM
Done.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1380
Here is an overview of the issue:
-
vmassol 2004/07/19 06:48:58
Modified:src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH
MavenUtils.java
Log:
Fixed MAVEN-1380
Revision ChangesPath
No revision
No revision
1.107.4.23 +2 -2 maven/src/java/org
The following comment has been added to this issue:
Author: Jerome Lacoste
Created: Mon, 19 Jul 2004 9:34 AM
Body:
The problem is I think in the get-deps build.jelly template.
See
http://cvs.apache.org/viewcvs.cgi/maven-plugins/ant/src/plugin-resources/templates/bu
> There are actually 4 bugs to fix but I have no idea to solve them:
> http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10316&statusIds=1
Can't MPANT-7 also be solved?
Jerome
-
To unsubscribe, e-mail: [
The following comment has been added to this issue:
Author: Jerome Lacoste
Created: Mon, 19 Jul 2004 9:24 AM
Body:
Or could one override the src uses when using an overriden jar.
-
View this comment:
http://jira
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1380
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Jerome Lacoste
Created: Mon, 19 Jul 2004 8:25 AM
Body:
All in all, I still don't understand why the run tests are found in the tests sources.
Why don't one use the compiled classes as input?
What are the drawbacks of doin
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPECLIPSE-35
Here is an overview of the issue:
-
Ke
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Mon, 19 Jul 2004 7:09 AM
Body:
Usage is now documented
-
View this comment:
http://jira.codehaus.org/browse/MPLICENSE-1?page=com
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPARTIFACT-32
Here is an overview of the issue:
-
K
No, I'm using sftp. I just check my remote repo and the SNAPSHOT symlinks
were already there and pointing to old jars.
I'll raise an issue to JIRA although not confirmed.
> -Original Message-
> From: Jörg Schaible [mailto:[EMAIL PROTECTED]
> Sent: Monday, July 19, 2004 12:24 PM
> To: Mav
carlos 2004/07/19 03:32:02
Modified:license/xdocs index.xml
Log:
Added report doc
Revision ChangesPath
1.3 +12 -0 maven-plugins/license/xdocs/index.xml
Index: index.xml
===
RCS file: /home
Carlos Sanchez wrote on Monday, July 19, 2004 12:21 PM:
> Hi,
>
> It seems that snapshot files deployed with the new artifact
> plugin don't overwrite those deployed with the old deploy
> plugin (xxx-SNAPSHOT symlinks), can anyone of you check in
> your repositories if it's an issue?
http://jira
Hi,
It seems that snapshot files deployed with the new artifact plugin don't
overwrite those deployed with the old deploy plugin (xxx-SNAPSHOT symlinks),
can anyone of you check in your repositories if it's an issue?
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPARTIFACT-31
Here is an overview of the issue:
-
K
Hi Mark,
You're right, when I said snapshots I meant dated builds (snapshots over the
time). Actually snapshots are no longer a symlink, just a copy.
As you have read in the Maven dev list, the opinion of Jason is that each
project members should be able to decide if they want their dated builds
Ok Stephan. Thanks for this explanation.
I will add the setproxy (and a comment about the JDK compatibility) to the generated
and script.
Arnaud.
> -Message d'origine-
> De : Stefan Bodewig [mailto:[EMAIL PROTECTED]
> Envoyé : lundi 19 juillet 2004 09:23
> À : Maven Developers List
>
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Mon, 19 Jul 2004 4:36 AM
Body:
It usually happens when you're extending a project.xml that doesn't exist or with a
malformed project.xml. Check it and if you don't find the error upload it.
---
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1379
Here is an overview of the issue:
-
Key:
Jason van Zyl <[EMAIL PROTECTED]> writes:
>Well that's perfectly fine, they are in complete control of what goes
>into the directories we sync to ibiblio. At apache all committers have
>access to the directory that goes to ibiblio. I started rejecting
>requests to push Apache artifacts to Ibiblio
On Mon, 19 Jul 2004, Arnaud Heritier <[EMAIL PROTECTED]> wrote:
> Yes you're right, but do you know why the ant's setproxy task is
> optional?
Because it requires JDK 1.2+ - and so it has traditionally been an
optional task since Ant up to 1.5.4 is JDK 1.1 compatible.
Stefan
---
42 matches
Mail list logo
