Re: Compatibility with Ant 1.6?
I don't want to overstep my bounds but even with significant compatibility issues I think that it would be crucial to keep up with the progression of Ant. Eventually, you'd have to abandon Ant or incur an even bigger compatibility problem. Not keeping up may encourage people to abandon Maven. Regards, Earl Hokens 312-322-4173 (desk) 312-404-2718 (mobile) [EMAIL PROTECTED] Brett Porter [EMAIL PROTECTED] 10/13/2004 11:33 PM Please respond to Maven Users List To: Maven Users List [EMAIL PROTECTED] cc: Subject:Re: Compatibility with Ant 1.6? Yep, as Arnaud and Dion have said. It's targetted for 1.1, but is also on the chopping block if it causes significant compatibility problems. Set yourself to watch the JIRA issue if interested. You'll find it on the Roadmap for 1.1 - Brett On Thu, 14 Oct 2004 14:30:23 +1000, Dion Gillard [EMAIL PROTECTED] wrote: Ant 1.6's classloader changes break Maven. Near future? I'd say not. On Wed, 13 Oct 2004 18:19:22 -0400, Will McKinley [EMAIL PROTECTED] wrote: I've searched the maven archive, so pardon me if this has already been discussed. I've noticed that maven only supports ant 1.5.3. I have a situation where I need the input parameter to the java task which is only available in ant 1.6. Is there a strategy for delivering maven with 1.6 compatibility in the near future? thanks, Will McKinley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Compatibility with Ant 1.6?
Again, I'm not trying to ruffle any feathers so please do not take it personally. I really do like the concept of Maven and I am trying to get it incorporated into our environment. We also have people here that are currently using Ant and are on 1.6 version. I think Maven is a next natural step beyond Ant but getting people to switch from Ant 1.6 and move back to something utilizing Ant 1.5.3 would make it harder for me to convince people to switch. Furthermore, as Ant continues to progress relying on an old version opens up Maven to risk whether real or perceived. The perception risk is Maven uses old Ant = not current, not good. Regardless of how well Maven may function perception counts. Regards, Earl Hokens 312-322-4173 (desk) 312-404-2718 (mobile) [EMAIL PROTECTED] Craig S.Cottingham [EMAIL PROTECTED] 10/14/2004 09:42 AM Please respond to Maven Users List To: Maven Users List [EMAIL PROTECTED] cc: Subject:Re: Compatibility with Ant 1.6? On Oct 14, 2004, at 09:29, [EMAIL PROTECTED] wrote: I don't want to overstep my bounds but even with significant compatibility issues I think that it would be crucial to keep up with the progression of Ant. Eventually, you'd have to abandon Ant or incur an even bigger compatibility problem. Not keeping up may encourage people to abandon Maven. I don't see how any of your points are logical conclusions of not using the latest and greatest version of Ant. Whichever version of Ant is currently used in Maven, will continue to work in Maven. Ant going to version 1.7, or 2.0, won't suddenly cause Maven to stop working. And if Maven is still working, why would I abandon it? Certainly not just because there's a newer version of Ant available. -- Craig S. Cottingham [EMAIL PROTECTED] OpenPGP key available from: http://pgp.mit.edu:11371/pks/lookup?op=getsearch=0x7977F79C - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0 question
Is there a planned release date for Maven 2.0? Regards, Earl Hokens 312-322-4173 (desk) 312-404-2718 (mobile) [EMAIL PROTECTED] Jason van Zyl [EMAIL PROTECTED] 10/07/2004 02:52 PM Please respond to Maven Users List To: Maven Users List [EMAIL PROTECTED] cc: Subject:Re: Maven 2.0 question On Thu, 2004-10-07 at 14:47, STRAYER, JON (SBCSI) wrote: Is Jelly still the scripting language for Maven 2.0? The short answer is no. The long answer is that there will be several options for scripting plugins: the XML scripting option is something called Marmalade which is something like Jelly except it actually works and doesn't result in the operator pulling out his own teeth trying to get it work. Jelly is a guaragantuan piece of crap and I made the dire mistake of incorporating it into Maven which I will always regret. Marmalade is written by John Casey who has been long involved in Maven, he's heavily involved in Maven 2.x and is committed to the long-term maintenance of Marmalade. He's got all the core Jelly tag libs working as well. Some other options are Beanshell, Janino and possibly JRuby. Don't even ask about Groovy because I wouldn't touch it with a 10' pole. -- jvz. Jason van Zyl [EMAIL PROTECTED] http://maven.apache.org happiness is like a butterfly: the more you chase it, the more it will elude you, but if you turn your attention to other things, it will come and sit softly on your shoulder ... -- Thoreau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven war problem
No question is ever silly! I thought I had run maven clean but apparently
I did not. Works like a charm now.
As for the jar files in the lib dir, we use WebSphere Studio and do our
testing on the embedded server in the tool. They are needed somewhere in
the class path for running it local. Some of us put things in the lib
directory, other put them in a separate project and refer to them as
external jars. We haven't decided which is better both have pros and
cons.
Thanks a lot Nathan.
Regards,
Earl Hokens
312-322-4173 (desk)
312-404-2718 (mobile)
[EMAIL PROTECTED]
Nathan Coast [EMAIL PROTECTED]
09/16/2004 08:12 PM
Please respond to Maven Users List
To: Maven Users List [EMAIL PROTECTED]
cc:
Subject:Re: maven war problem
looks ok to me,
this might be a silly suggestion but have executed maven clean since you
modified the
maven.war.src.excludes?
is your source directory [project]/WebContent
or
[project]/src/WebContent
if the latter, you'll want
maven.war.src=${maven.src.dir}/WebContent
you might want to check there is no overriding maven.war.src.excludes
entry in
[user_home]/build.properties
One more thing, you probably don't want jar files in your maven.war.src
dir these should
probably be identified with dependency elements in your project.xml
hope this is useful
[EMAIL PROTECTED] wrote:
I am trying to package up a war file with Maven 1.0. I am able to get
it
to work but I am trying to exclude files from the war and it is not
working.
This is the information in my project.properties
maven.multiproject.type=war
maven.war.src=${basedir}/WebContent
maven.war.src.excludes=**/*.jar,**/*.gph,**/*.xmi
The files matching these criteria are still included in the war. I've
tried various permutations of the exclude files to no avail. What I am
doing wrong?
Thanks,
Earl Hokens
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
