Re: sequence of prereqs in maven.xml file

[Brett Porter]

java:compile relies on some variables being set which are done when
the project is initialised. If your source is not there when you first
run the project, it will think there is none and will not attempt to
compile.

It is recommended that you check out whole projects, not just portions
of them. You might like to create a "bootstrap" project that will do
that checkout and run the desired goals (or use the
scm:bootstrap-project goals).

- Brett


On Fri, 25 Mar 2005 10:42:19 +0530, GOKULAM Jayaram
<[EMAIL PROTECTED]> wrote:
> Hi,
> 
> I have been trying to keep my maven.xml file in the following manner.
> 
>  xmlns:ant="jelly:ant" >
> 
>  prereqs="scm:cvs-checkout-project,java:compile,dashboard:report,xdoc">
> 
> 
> 
> 
> 
> But am getting a weird error, First time after checkout the source code
> is not being compiled.
> 
> The second time it gets compiled propertly.
> 
> Is my maven.xml definition correct or please guide me how I should
> define the commands so that, they execute one after the other in a
> sequence.
> 
> Expecting help on this.
> 
> Thanks in advance,
> 
> Jayaram
> 
> Confidentiality Statement:
> 
> This message is intended only for the individual or entity to which it is 
> addressed. It may contain privileged, confidential information which is 
> exempt from disclosure under applicable laws. If you are not the intended 
> recipient, please note that you are strictly prohibited from disseminating or 
> distributing this information (other than to the intended recipient) or 
> copying this information. If you have received this communication in error, 
> please notify us immediately by return email.
> 
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

sequence of prereqs in maven.xml file

[GOKULAM Jayaram]

Hi,

I have been trying to keep my maven.xml file in the following manner.

 



 





 

But am getting a weird error, First time after checkout the source code
is not being compiled.

The second time it gets compiled propertly.

 

Is my maven.xml definition correct or please guide me how I should
define the commands so that, they execute one after the other in a
sequence.

 

Expecting help on this.

 

Thanks in advance,

Jayaram

 

Confidentiality Statement:

This message is intended only for the individual or entity to which it is 
addressed. It may contain privileged, confidential information which is exempt 
from disclosure under applicable laws. If you are not the intended recipient, 
please note that you are strictly prohibited from disseminating or distributing 
this information (other than to the intended recipient) or copying this 
information. If you have received this communication in error, please notify us 
immediately by return email.

Re: Generate Download Page ?

[Ha ryon]

ahah ! cool, thanks a lot.

On Thu, 24 Mar 2005 17:30:31 +0100, Vincent Massol <[EMAIL PROTECTED]> wrote:
> Yes, there is a trick :-)
> 
> 1/ You need to define the following property:
> 
> # Location where the artifacts are distributed. This property is optional.
> # If it is not defined, then the Download report will not be added to the
> # navigation menu.
> # NOTE: In the future this information will be described in the POM
> # Ex: maven.xdoc.distributionUrl=http://www.ibiblio.org/maven/maven/plugins
> 
> 2/ You need to define  element in your POM for each version you
> wish to have a download link for.
> 
> -Vincent
> 
> > -Original Message-
> > From: Ha ryon [mailto:[EMAIL PROTECTED]
> > Sent: jeudi 24 mars 2005 16:59
> > To: Maven List
> > Subject: Generate Download Page ?
> >
> > Is there a command, trick, or plugin I missed that would automatically
> > generated the download page (that is a page where a list of version
> > and link to where they can be downloaded from ) when doing mave:site ?
> >
> > thanks in advance
> >
> > -
> > 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]
> 
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Ear plugin and multiproject

[Daniel Or]

Hi.

I have an ear project that has additional resource (the resource should
get into the META-INF dir).

I have specified maven.ear.src and maven.ear.resources.

When I run maven only for this project I get the resource into the ear.

When I run it as a part of multiproject it doesn't get into the ear.

 

Thanks in advance for any clue

 

Daniel Or

 

 

RE: Generate Download Page ?

[Vincent Massol]

Yes, there is a trick :-)

1/ You need to define the following property:

# Location where the artifacts are distributed. This property is optional. 
# If it is not defined, then the Download report will not be added to the 
# navigation menu.
# NOTE: In the future this information will be described in the POM
# Ex: maven.xdoc.distributionUrl=http://www.ibiblio.org/maven/maven/plugins

2/ You need to define  element in your POM for each version you
wish to have a download link for.

-Vincent

> -Original Message-
> From: Ha ryon [mailto:[EMAIL PROTECTED]
> Sent: jeudi 24 mars 2005 16:59
> To: Maven List
> Subject: Generate Download Page ?
> 
> Is there a command, trick, or plugin I missed that would automatically
> generated the download page (that is a page where a list of version
> and link to where they can be downloaded from ) when doing mave:site ?
> 
> thanks in advance
> 
> -
> 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]

Avoid tests being run twice when deploying

[Deblauwe, Wim]

Hi,
 
During the night, I would like to build all my modules. Since a module might
depend on a change made in another module during that day, I want to deploy
a snapshot version to our server repository. Using the multiproject plugin,
I call the following goals:
maven clean site jar:deploy
 
This results in my tests being run twice. Is there a way to avoid this?
 
I already tried this:
maven clean site artifact:deploy
 
With artifact:deploy defined in my maven.xml like this:
 
 
  
 
  
  

 
But this does not work because no jar is created when running the 'site'
goal!
 
I know there is a maven.test.skip property. Is there some way I could set
this before doing  and then set it back again afterwards?
 
any help would be appreciated!
 
regards,
 
Wim
 

  
Ing. Wim Deblauwe 
Software Development Engineer 
  
BarcoView - Medical Imaging Systems 
President Kennedypark 35 
B-8500 Kortrijk, Belgium 
Tel. +32 56 233 985 Fax +32 56 233 457 
www.barco.com   
[EMAIL PROTECTED]  

 
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically authorized to
receive it. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability for any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liablility for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.

Generate Download Page ?

[Ha ryon]

Is there a command, trick, or plugin I missed that would automatically
generated the download page (that is a page where a list of version
and link to where they can be downloaded from ) when doing mave:site ?

thanks in advance

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

How to : Build non-java artifacts ?

[Ha ryon]

Hi,

Instead of reinventing a build system, I am currently trying to use
maven concepts and engines to compile and document non-java projects.
In the instance, I'm working on building up NWN (Neverwinter Nights :
a computer game) custom content package add-ons. The 'sources' are xml
files, 3D models/anim, pictures. The build process is to translate the
xml into the game proprietary formats, compile 3D models into binary
form, then pack everything into legacy format.

For documentation, I'll have reports working on the xml files to
provide human-even-more-readable view of the add-on content (a kind of
javadoc in fact). I'll have java-computed reports to detect errors,
missing files, and such (something like PMD, JDepend and such tools
but much simplier).

I started to write a plugin that provide goals to make all of that.

Here are my questions :

- can I specify somewhere in the project.xml of the projects (not the
compile plugin) where non-java language sources are ?

- I want to provide a RAR packed distribution of the compiled add-on,
with addition of some documentation (might be all, part of maven:site
result, or something separate), licence/notice/install files. I saw
rar plugin, but it creates manifest. Can I avoid that ?

- Do you think I can reuse some of the distribution plugin to make
that rar and deploy it to target server ?

- how do I specific that my project (the add-on, not the plugin) type
is not jar but that nwn specific format ? (in fact there are two main
: .tlk and .hak).

- is there something like a 'maven build' that would do a jar is its a
jar project, a maven war if it's a war, and a tlk is that's a
neverwinter tlk file ? (I saw something similar for multiproject, but
I didn't see for mono project).

You can have a quick overview, of my plugin here :
http://www.thalarion.com/nwn/docs/halkhemy/halkhemy/SNAPSHOT/. It's
still heavily under development of course, hence the SNAPSHOT.

Anyone has similar experience ? using maven to build DLL projects f.e.
I'll most probably come back with extra questions later. Especially
when I'll start to work with dependencies between content add-ons, or
when I'll try to put the xml schema online !

thanks in advance for sharing advice/opinion.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven roadmap - should i stay or should i go

[Milos Kleint]

I've added a maven plugin project template into Mevenide for Netbeans.
It creates a project with plugin files, you have code completion in the 
plugin.jelly file etc.

Regards
Milos Kleint
Brett Porter wrote:
http://maven.apache.org/using/bestpractices.html#Scripting
On Thu, 24 Mar 2005 15:02:15 +0100, Serge Huber <[EMAIL PROTECTED]> wrote:
 

I once got the great advice from a MevenIDE developer that I should keep
the maven.xml file to a strict minimum, and develop plugins mostly using
Java classes. I've used that advice well, and it looks like at least for
me, migrating to Maven 2 wouldn't be too much of a problem.
Maybe this should be on a page somewhere, in order for people to prepare
for Maven 2 ? Basically telling them that in order to build scripts &
plugins that are compatible with Maven 2, they should follow these two
guidelines as much as possible ?
Regards,
 Serge Huber.
Brett Porter wrote:
   

Huh... Exactly how much trouble are we talking about to switch custom
plugins and such??? Is Jelly replaced?
   

Yes, though we are trying hard to put in a replacement that can
transparently run old Jelly scripts with minimal changes. Part of the
problem is that people have come to rely on bugs in Jelly/Jexl/Maven
for their scripts to work.

 

And if so, with what and why?
   

Speed and memory usage are a big factor. In Maven 2.x, most plugins
are written in pure Java, though theoretically adapters can be written
for any scripting language.
There will be an XML scripting language present for the benefit of
users who want to interface with Ant tasks, though it won't at all be
necessary to use it day to day.

 

Does it mean all the custom stuff I'm currently implementing will be
thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
be in production for more than a couple of months...
   

Maven 1.x is not going to disappear - if your investment outweighs the
benefit, then stick with it.
More information will be available as the first releases draw near.
For now - Maven 1.1 and its plugins continue to be developed.
- Brett
-
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]
   

-
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: maven roadmap - should i stay or should i go

[Serge Huber]

Brett Porter wrote:
http://maven.apache.org/using/bestpractices.html#Scripting
 

Oops sorry... I didn't check out the new content yet :)
Regards,
 Serge Huber.

On Thu, 24 Mar 2005 15:02:15 +0100, Serge Huber <[EMAIL PROTECTED]> wrote:
 

I once got the great advice from a MevenIDE developer that I should keep
the maven.xml file to a strict minimum, and develop plugins mostly using
Java classes. I've used that advice well, and it looks like at least for
me, migrating to Maven 2 wouldn't be too much of a problem.
Maybe this should be on a page somewhere, in order for people to prepare
for Maven 2 ? Basically telling them that in order to build scripts &
plugins that are compatible with Maven 2, they should follow these two
guidelines as much as possible ?
Regards,
 Serge Huber.
Brett Porter wrote:
   

Huh... Exactly how much trouble are we talking about to switch custom
plugins and such??? Is Jelly replaced?
   

Yes, though we are trying hard to put in a replacement that can
transparently run old Jelly scripts with minimal changes. Part of the
problem is that people have come to rely on bugs in Jelly/Jexl/Maven
for their scripts to work.

 

And if so, with what and why?
   

Speed and memory usage are a big factor. In Maven 2.x, most plugins
are written in pure Java, though theoretically adapters can be written
for any scripting language.
There will be an XML scripting language present for the benefit of
users who want to interface with Ant tasks, though it won't at all be
necessary to use it day to day.

 

Does it mean all the custom stuff I'm currently implementing will be
thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
be in production for more than a couple of months...
   

Maven 1.x is not going to disappear - if your investment outweighs the
benefit, then stick with it.
More information will be available as the first releases draw near.
For now - Maven 1.1 and its plugins continue to be developed.
- Brett
-
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]
   

-
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: maven roadmap - should i stay or should i go

[Brett Porter]

http://maven.apache.org/using/bestpractices.html#Scripting


On Thu, 24 Mar 2005 15:02:15 +0100, Serge Huber <[EMAIL PROTECTED]> wrote:
> 
> I once got the great advice from a MevenIDE developer that I should keep
> the maven.xml file to a strict minimum, and develop plugins mostly using
> Java classes. I've used that advice well, and it looks like at least for
> me, migrating to Maven 2 wouldn't be too much of a problem.
> 
> Maybe this should be on a page somewhere, in order for people to prepare
> for Maven 2 ? Basically telling them that in order to build scripts &
> plugins that are compatible with Maven 2, they should follow these two
> guidelines as much as possible ?
> 
> Regards,
>   Serge Huber.
> 
> Brett Porter wrote:
> 
> >>Huh... Exactly how much trouble are we talking about to switch custom
> >>plugins and such??? Is Jelly replaced?
> >>
> >>
> >
> >Yes, though we are trying hard to put in a replacement that can
> >transparently run old Jelly scripts with minimal changes. Part of the
> >problem is that people have come to rely on bugs in Jelly/Jexl/Maven
> >for their scripts to work.
> >
> >
> >
> >>And if so, with what and why?
> >>
> >>
> >
> >Speed and memory usage are a big factor. In Maven 2.x, most plugins
> >are written in pure Java, though theoretically adapters can be written
> >for any scripting language.
> >
> >There will be an XML scripting language present for the benefit of
> >users who want to interface with Ant tasks, though it won't at all be
> >necessary to use it day to day.
> >
> >
> >
> >>Does it mean all the custom stuff I'm currently implementing will be
> >>thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
> >>be in production for more than a couple of months...
> >>
> >>
> >
> >Maven 1.x is not going to disappear - if your investment outweighs the
> >benefit, then stick with it.
> >
> >More information will be available as the first releases draw near.
> >For now - Maven 1.1 and its plugins continue to be developed.
> >
> >- Brett
> >
> >-
> >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]
> 
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven roadmap - should i stay or should i go

[Serge Huber]

I once got the great advice from a MevenIDE developer that I should keep 
the maven.xml file to a strict minimum, and develop plugins mostly using 
Java classes. I've used that advice well, and it looks like at least for 
me, migrating to Maven 2 wouldn't be too much of a problem.

Maybe this should be on a page somewhere, in order for people to prepare 
for Maven 2 ? Basically telling them that in order to build scripts & 
plugins that are compatible with Maven 2, they should follow these two 
guidelines as much as possible ?

Regards,
 Serge Huber.
Brett Porter wrote:
Huh... Exactly how much trouble are we talking about to switch custom
plugins and such??? Is Jelly replaced? 
   

Yes, though we are trying hard to put in a replacement that can
transparently run old Jelly scripts with minimal changes. Part of the
problem is that people have come to rely on bugs in Jelly/Jexl/Maven
for their scripts to work.
 

And if so, with what and why?
   

Speed and memory usage are a big factor. In Maven 2.x, most plugins
are written in pure Java, though theoretically adapters can be written
for any scripting language.
There will be an XML scripting language present for the benefit of
users who want to interface with Ant tasks, though it won't at all be
necessary to use it day to day.
 

Does it mean all the custom stuff I'm currently implementing will be
thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
be in production for more than a couple of months...
   

Maven 1.x is not going to disappear - if your investment outweighs the
benefit, then stick with it.
More information will be available as the first releases draw near.
For now - Maven 1.1 and its plugins continue to be developed.
- Brett
-
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: maven roadmap - should i stay or should i go

[Steve Molloy]

OK, that is usually simple stuff anyway. 

Thanks for the relief... 

Steve

On Thu, 2005-24-03 at 14:47 +0100, Nicolas Chalumeau wrote:


All old plugin in jelly will be suported.
As far I know the trouble will be with all the goal you have in your
maven.xml as (I am maybe wrong) this file not be use in M2

Nicolas

On Thu, 24 Mar 2005 08:39:49 -0500, Steve Molloy <[EMAIL PROTECTED]> wrote:
> Huh... Exactly how much trouble are we talking about to switch custom
> plugins and such??? Is Jelly replaced? And if so, with what and why?
> Does it mean all the custom stuff I'm currently implementing will be
> thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
> be in production for more than a couple of months...
> 
> Steve
> 
> On Thu, 2005-24-03 at 19:05 +1100, Brett Porter wrote:
> 
> > Vincent has pretty well summed it up. I will try to clarify the document.
> >
> > Though the basic concepts are the same, Maven 2.x is really quite
> > different, and it will require some work to move a project over to it.
> > How much depends on how heavily you customise your Maven 1.x project -
> > if you stick to the defaults and don't use Jelly, then it should be
> > quite simple.
> >
> > Maven 1.x will still be developed until Maven 2.x is production ready
> > (which is not going to be until later this year).
> >
> > - Brett
> >
> >
> > On Thu, 24 Mar 2005 08:44:12 +0100, Vincent Massol <[EMAIL PROTECTED]> wrote:
> > > Hi Sejo,
> > >
> > > I'd personally go ahead with Maven 1.0.2. There should be a Maven 1.1
> > > version before this summer too with several components from Maven2
> > > backported. I believe the Maven2 team will make it as easy as possible for
> > > existing Maven users to switch to Maven2.
> > >
> > > Most of the Maven1 concepts will stay but will be implemented differently
> > > (new POM version for example).
> > >
> > > I'll let the Maven2 team comment further on details.
> > >
> > > -Vincent
> > >
> > > > -Original Message-
> > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> > > > Sent: jeudi 24 mars 2005 08:22
> > > > To: Maven Users List
> > > > Subject: maven roadmap - should i stay or should i go
> > > >
> > > > Hi all,
> > > >
> > > > In a project I am currently working on - which is just about to start with
> > > > the construction phase -  we are considering to use maven. I have been
> > > > encountering maven in previous projects as well and based on these
> > > > experiences i was quite sure I will use it on many others as well.
> > > >
> > > > However when i see the new roadmap description on maven site :
> > > >
> > > > <
> > > > with any of the Maven 1.x releases>>,
> > > >
> > > > i am having doubts on what exactly should we do right now.
> > > >
> > > > To take off with the current release (1.0.2) and wait for a complete
> > > > rewrite of our build scripts? How "complete" will that rewrite actually
> > > > have to be? All what the explanation in the roadmap leaves us with is a
> > > > bit of hope that  attempts will be made to stay backward compatible in the
> > > > new 2.0 release. What about the "conceptual approach", how many things can
> > > > we expect to be different, new or completely dissapear  (multiproject,
> > > > repository, ...goals)?
> > > >
> > > > Could someone point me to a document/person that can give a bit more of
> > > > vision/explanation concerning these issues? What would  you suggest to a
> > > > project that is just about to jump into maven?
> > > >
> > > > Thanks.
> > > >
> > > > -Sejo
> > > >
> > > >
> > >
> > > -
> > > 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]
> >
> 
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven roadmap - should i stay or should i go

[Brett Porter]

> Huh... Exactly how much trouble are we talking about to switch custom
> plugins and such??? Is Jelly replaced? 

Yes, though we are trying hard to put in a replacement that can
transparently run old Jelly scripts with minimal changes. Part of the
problem is that people have come to rely on bugs in Jelly/Jexl/Maven
for their scripts to work.

> And if so, with what and why?

Speed and memory usage are a big factor. In Maven 2.x, most plugins
are written in pure Java, though theoretically adapters can be written
for any scripting language.

There will be an XML scripting language present for the benefit of
users who want to interface with Ant tasks, though it won't at all be
necessary to use it day to day.

> Does it mean all the custom stuff I'm currently implementing will be
> thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
> be in production for more than a couple of months...

Maven 1.x is not going to disappear - if your investment outweighs the
benefit, then stick with it.

More information will be available as the first releases draw near.
For now - Maven 1.1 and its plugins continue to be developed.

- Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven roadmap - should i stay or should i go

[Nicolas Chalumeau]

All old plugin in jelly will be suported.
As far I know the trouble will be with all the goal you have in your
maven.xml as (I am maybe wrong) this file not be use in M2

Nicolas

On Thu, 24 Mar 2005 08:39:49 -0500, Steve Molloy <[EMAIL PROTECTED]> wrote:
> Huh... Exactly how much trouble are we talking about to switch custom
> plugins and such??? Is Jelly replaced? And if so, with what and why?
> Does it mean all the custom stuff I'm currently implementing will be
> thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
> be in production for more than a couple of months...
> 
> Steve
> 
> On Thu, 2005-24-03 at 19:05 +1100, Brett Porter wrote:
> 
> > Vincent has pretty well summed it up. I will try to clarify the document.
> >
> > Though the basic concepts are the same, Maven 2.x is really quite
> > different, and it will require some work to move a project over to it.
> > How much depends on how heavily you customise your Maven 1.x project -
> > if you stick to the defaults and don't use Jelly, then it should be
> > quite simple.
> >
> > Maven 1.x will still be developed until Maven 2.x is production ready
> > (which is not going to be until later this year).
> >
> > - Brett
> >
> >
> > On Thu, 24 Mar 2005 08:44:12 +0100, Vincent Massol <[EMAIL PROTECTED]> 
> > wrote:
> > > Hi Sejo,
> > >
> > > I'd personally go ahead with Maven 1.0.2. There should be a Maven 1.1
> > > version before this summer too with several components from Maven2
> > > backported. I believe the Maven2 team will make it as easy as possible for
> > > existing Maven users to switch to Maven2.
> > >
> > > Most of the Maven1 concepts will stay but will be implemented differently
> > > (new POM version for example).
> > >
> > > I'll let the Maven2 team comment further on details.
> > >
> > > -Vincent
> > >
> > > > -Original Message-
> > > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > > Sent: jeudi 24 mars 2005 08:22
> > > > To: Maven Users List
> > > > Subject: maven roadmap - should i stay or should i go
> > > >
> > > > Hi all,
> > > >
> > > > In a project I am currently working on - which is just about to start 
> > > > with
> > > > the construction phase -  we are considering to use maven. I have been
> > > > encountering maven in previous projects as well and based on these
> > > > experiences i was quite sure I will use it on many others as well.
> > > >
> > > > However when i see the new roadmap description on maven site :
> > > >
> > > > < > > > compatible
> > > > with any of the Maven 1.x releases>>,
> > > >
> > > > i am having doubts on what exactly should we do right now.
> > > >
> > > > To take off with the current release (1.0.2) and wait for a complete
> > > > rewrite of our build scripts? How "complete" will that rewrite actually
> > > > have to be? All what the explanation in the roadmap leaves us with is a
> > > > bit of hope that  attempts will be made to stay backward compatible in 
> > > > the
> > > > new 2.0 release. What about the "conceptual approach", how many things 
> > > > can
> > > > we expect to be different, new or completely dissapear  (multiproject,
> > > > repository, ...goals)?
> > > >
> > > > Could someone point me to a document/person that can give a bit more of
> > > > vision/explanation concerning these issues? What would  you suggest to a
> > > > project that is just about to jump into maven?
> > > >
> > > > Thanks.
> > > >
> > > > -Sejo
> > > >
> > > >
> > >
> > > -
> > > 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]
> >
> 
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven roadmap - should i stay or should i go

[Steve Molloy]

Huh... Exactly how much trouble are we talking about to switch custom
plugins and such??? Is Jelly replaced? And if so, with what and why?
Does it mean all the custom stuff I'm currently implementing will be
thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to
be in production for more than a couple of months...

Steve

On Thu, 2005-24-03 at 19:05 +1100, Brett Porter wrote:

> Vincent has pretty well summed it up. I will try to clarify the document.
> 
> Though the basic concepts are the same, Maven 2.x is really quite
> different, and it will require some work to move a project over to it.
> How much depends on how heavily you customise your Maven 1.x project -
> if you stick to the defaults and don't use Jelly, then it should be
> quite simple.
> 
> Maven 1.x will still be developed until Maven 2.x is production ready
> (which is not going to be until later this year).
> 
> - Brett
> 
> 
> On Thu, 24 Mar 2005 08:44:12 +0100, Vincent Massol <[EMAIL PROTECTED]> wrote:
> > Hi Sejo,
> > 
> > I'd personally go ahead with Maven 1.0.2. There should be a Maven 1.1
> > version before this summer too with several components from Maven2
> > backported. I believe the Maven2 team will make it as easy as possible for
> > existing Maven users to switch to Maven2.
> > 
> > Most of the Maven1 concepts will stay but will be implemented differently
> > (new POM version for example).
> > 
> > I'll let the Maven2 team comment further on details.
> > 
> > -Vincent
> > 
> > > -Original Message-
> > > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > > Sent: jeudi 24 mars 2005 08:22
> > > To: Maven Users List
> > > Subject: maven roadmap - should i stay or should i go
> > >
> > > Hi all,
> > >
> > > In a project I am currently working on - which is just about to start with
> > > the construction phase -  we are considering to use maven. I have been
> > > encountering maven in previous projects as well and based on these
> > > experiences i was quite sure I will use it on many others as well.
> > >
> > > However when i see the new roadmap description on maven site :
> > >
> > > < > > with any of the Maven 1.x releases>>,
> > >
> > > i am having doubts on what exactly should we do right now.
> > >
> > > To take off with the current release (1.0.2) and wait for a complete
> > > rewrite of our build scripts? How "complete" will that rewrite actually
> > > have to be? All what the explanation in the roadmap leaves us with is a
> > > bit of hope that  attempts will be made to stay backward compatible in the
> > > new 2.0 release. What about the "conceptual approach", how many things can
> > > we expect to be different, new or completely dissapear  (multiproject,
> > > repository, ...goals)?
> > >
> > > Could someone point me to a document/person that can give a bit more of
> > > vision/explanation concerning these issues? What would  you suggest to a
> > > project that is just about to jump into maven?
> > >
> > > Thanks.
> > >
> > > -Sejo
> > >
> > >
> > 
> > -
> > 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: Problem deploying to remote repository an artifact that already exists

[Kenney Westerhof]

On Wed, 23 Mar 2005, Craig S. Cottingham wrote:

According to the FTP message it seems your FTP server is configured not
to allow file overwrites (if this were a simple file permission issue,
the message would probably say 'Permission Denied').

This is most common when using anonymous ftp accounts. See the
manual of your flavor ftp server for how to allow
file overwrites.

For example, in ProFTPD:


AllowOverwrite On

AllowAll



Greetings,

Kenney Westerhof

> On Mar 23, 2005, at 15:21, Roberto Castro wrote:
>
> > Hi, all, I've been facing a problem when Maven tries to deploy to
> > remote repository an artifact that already exists. I'm using Maven
> > 1.02 and here are the master project properties:
> >
> > [snip]
> >
> > The followind messages are part of Mavenlog:
> > 227 Entering Passive Mode (172,20,238,32,213,118).
> > STOR ftpcetip-R1_0.pom
> > 550 ftpcetip-R1_0.pom: Overwrite permission denied
> > Failed to deploy to: CTPREPO Reason: Error executing FTP command
> > org.apache.maven.deploy.exceptions.TransferFailedException: Error
> > executing FTP command
>
> Check the file permissions on the artifact in the remote repository. It
> looks like the user you're using to deploy the artifact doesn't have
> the correct permissions to overwrite the file.
>
> --
> Craig S. Cottingham
> [EMAIL PROTECTED]
> OpenPGP key available from:
> http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x7977F79C
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>  Output from gpg 
> gpg: Signature made Wed 23 Mar 2005 10:33:07 PM CET using DSA key ID 7977F79C
> gpg: Good signature from "Craig S. Cottingham <[EMAIL PROTECTED]>"
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the owner.
> gpg: Fingerprint: C73E 3D4E 2176 4E8B 4ABE  9B27 1092 D0DC 7977 F79C
>
>

--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Log file creation

[Vincent Massol]

You can use the Ant  task but it'll log only the Ant tasks used by
Maven ( being one of them).

Check the Ant manual for more details.

-Vincent

> -Original Message-
> From: GOKULAM Jayaram [mailto:[EMAIL PROTECTED]
> Sent: jeudi 24 mars 2005 11:07
> To: Maven Users List
> Subject: Log file creation
> 
> Hi all,
> 
> I am trying to create a log file when a java compile fails, or when a
> deployment fails and so on. Can anybody help me how I should achieve
> this please.
> 
> 
> 
> Thanks in advance,
> 
> Jayaram
> 
> 
> 
> Confidentiality Statement:
> 
> This message is intended only for the individual or entity to which it is
> addressed. It may contain privileged, confidential information which is
> exempt from disclosure under applicable laws. If you are not the intended
> recipient, please note that you are strictly prohibited from disseminating
> or distributing this information (other than to the intended recipient) or
> copying this information. If you have received this communication in
> error, please notify us immediately by return email.





-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Log file creation

[GOKULAM Jayaram]

Thanks Deblauwe. But am calling java:compile from within maven.xml file.

My maven.xml file looks like





Which invokes the java:compile goal.

Is there anyother way to do this please?

Thanks in advance,
Jayaram
-Original Message-
From: Deblauwe, Wim [mailto:[EMAIL PROTECTED] 
Sent: Thursday, March 24, 2005 3:40 PM
To: 'Maven Users List'
Subject: RE: Log file creation

redirect the output to a file:

maven jar:compile > debug.txt

if you need to catch the stderr output as well:

maven jar:compile > debug.txt 2>&1

regards,

Wim
P.S.: This is on Windows ofcourse

-Original Message-
From: GOKULAM Jayaram [mailto:[EMAIL PROTECTED]
Sent: donderdag 24 maart 2005 11:07
To: Maven Users List
Subject: Log file creation


Hi all,
I am trying to create a log file when a java compile fails, or when a
deployment fails and so on. Can anybody help me how I should achieve
this please.
 
Thanks in advance,
Jayaram
 
Confidentiality Statement:
This message is intended only for the individual or entity to which it
is
addressed. It may contain privileged, confidential information which is
exempt from disclosure under applicable laws. If you are not the
intended
recipient, please note that you are strictly prohibited from
disseminating
or distributing this information (other than to the intended recipient)
or
copying this information. If you have received this communication in
error,
please notify us immediately by return email.
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically
authorized to
receive it. If you are not the intended recipient, you are hereby
notified
that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability for
any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liablility for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.
Confidentiality Statement:

This message is intended only for the individual or entity to which it is 
addressed. It may contain privileged, confidential information which is exempt 
from disclosure under applicable laws. If you are not the intended recipient, 
please note that you are strictly prohibited from disseminating or distributing 
this information (other than to the intended recipient) or copying this 
information. If you have received this communication in error, please notify us 
immediately by return email.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: Log file creation

[Deblauwe, Wim]

redirect the output to a file:

maven jar:compile > debug.txt

if you need to catch the stderr output as well:

maven jar:compile > debug.txt 2>&1

regards,

Wim
P.S.: This is on Windows ofcourse

-Original Message-
From: GOKULAM Jayaram [mailto:[EMAIL PROTECTED]
Sent: donderdag 24 maart 2005 11:07
To: Maven Users List
Subject: Log file creation


Hi all,
I am trying to create a log file when a java compile fails, or when a
deployment fails and so on. Can anybody help me how I should achieve
this please.
 
Thanks in advance,
Jayaram
 
Confidentiality Statement:
This message is intended only for the individual or entity to which it is
addressed. It may contain privileged, confidential information which is
exempt from disclosure under applicable laws. If you are not the intended
recipient, please note that you are strictly prohibited from disseminating
or distributing this information (other than to the intended recipient) or
copying this information. If you have received this communication in error,
please notify us immediately by return email.
- - - - - - - DISCLAIMER- - - - - - - -
Unless indicated otherwise, the information contained in this message is
privileged and confidential, and is intended only for the use of the
addressee(s) named above and others who have been specifically authorized to
receive it. If you are not the intended recipient, you are hereby notified
that any dissemination, distribution or copying of this message and/or
attachments is strictly prohibited. The company accepts no liability for any
damage caused by any virus transmitted by this email. Furthermore, the
company does not warrant a proper and complete transmission of this
information, nor does it accept liablility for any delays. If you have
received this message in error, please contact the sender and delete the
message. Thank you.

Log file creation

[GOKULAM Jayaram]

Hi all,

I am trying to create a log file when a java compile fails, or when a
deployment fails and so on. Can anybody help me how I should achieve
this please.

 

Thanks in advance,

Jayaram

 

Confidentiality Statement:

This message is intended only for the individual or entity to which it is 
addressed. It may contain privileged, confidential information which is exempt 
from disclosure under applicable laws. If you are not the intended recipient, 
please note that you are strictly prohibited from disseminating or distributing 
this information (other than to the intended recipient) or copying this 
information. If you have received this communication in error, please notify us 
immediately by return email.

Re: How to distinguish compile, test and runtime dependency?

[Andrew Thornton]

Libor Kramoliš wrote:
Image I work on webapp ABC. The application connects to XYZ database and 
use JUnit for testing. Now I have to specify dependency on 
jdbc2_0-stdext.jar, jdbc-xyz.jar and junit.jar.

And now I would like to say SRC is compiled just with jdbc2_0-stdext.jar 
(I do not want to have jdbc-xyz.jar and junit.jar on classpath) and TEST 
is compiled with jdbc2_0-stdext.jar and junit.jar. Dependency on 
jdbc-xyz.jar is here to be bundled in final .war file, it should never 
be on classpath.

Is it posible to configure this in project.xml or is Maven going to 
support it in next release(s)?
Don't whether this is what you want or not, but if you split the webapp 
into two sub-projects, one containing the src/java bits and another 
containing the src/webapp bits, you then get to list the dependencies 
indpendently.

andy
--
Andrew Thornton
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: How to distinguish compile, test and runtime dependency?

[Brett Porter]

This will only be supported from Maven 2.x onwards.

- Brett


On Thu, 24 Mar 2005 10:11:28 +0100, Libor Kramoliš
<[EMAIL PROTECTED]> wrote:
> Hello.
> 
> Image I work on webapp ABC. The application connects to XYZ database and
> use JUnit for testing. Now I have to specify dependency on
> jdbc2_0-stdext.jar, jdbc-xyz.jar and junit.jar.
> 
> And now I would like to say SRC is compiled just with jdbc2_0-stdext.jar
> (I do not want to have jdbc-xyz.jar and junit.jar on classpath) and TEST
> is compiled with jdbc2_0-stdext.jar and junit.jar. Dependency on
> jdbc-xyz.jar is here to be bundled in final .war file, it should never
> be on classpath.
> 
> Is it posible to configure this in project.xml or is Maven going to
> support it in next release(s)?
> 
> Best regards,
> -libor
> 
> -
> 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]

How to distinguish compile, test and runtime dependency?

[=?ISO-8859-2?Q?Libor_Kramoli=B9?=]

Hello.
Image I work on webapp ABC. The application connects to XYZ database and 
use JUnit for testing. Now I have to specify dependency on 
jdbc2_0-stdext.jar, jdbc-xyz.jar and junit.jar.

And now I would like to say SRC is compiled just with jdbc2_0-stdext.jar 
(I do not want to have jdbc-xyz.jar and junit.jar on classpath) and TEST 
is compiled with jdbc2_0-stdext.jar and junit.jar. Dependency on 
jdbc-xyz.jar is here to be bundled in final .war file, it should never 
be on classpath.

Is it posible to configure this in project.xml or is Maven going to 
support it in next release(s)?

Best regards,
-libor
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven roadmap - should i stay or should i go

[Brett Porter]

> Arg I want Maven 2 now :)
> 

Be patient, good things come to those who wait :)

> Just kidding, keep up the great work guys, but it's a long wait to Maven
> 2 it seems. Can you enlighten us as to the major road blocks you're
> encountering with Maven 2 ?
> 

It has almost entirely been available time of the developers.

- Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven roadmap - should i stay or should i go

[Serge Huber]

Brett Porter wrote:
Vincent has pretty well summed it up. I will try to clarify the document.
Though the basic concepts are the same, Maven 2.x is really quite
different, and it will require some work to move a project over to it.
How much depends on how heavily you customise your Maven 1.x project -
if you stick to the defaults and don't use Jelly, then it should be
quite simple.
Maven 1.x will still be developed until Maven 2.x is production ready
(which is not going to be until later this year).
 

Arg I want Maven 2 now :)
Just kidding, keep up the great work guys, but it's a long wait to Maven 
2 it seems. Can you enlighten us as to the major road blocks you're 
encountering with Maven 2 ?

Regards,
 Serge Huber.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven roadmap - should i stay or should i go

[Brett Porter]

Vincent has pretty well summed it up. I will try to clarify the document.

Though the basic concepts are the same, Maven 2.x is really quite
different, and it will require some work to move a project over to it.
How much depends on how heavily you customise your Maven 1.x project -
if you stick to the defaults and don't use Jelly, then it should be
quite simple.

Maven 1.x will still be developed until Maven 2.x is production ready
(which is not going to be until later this year).

- Brett


On Thu, 24 Mar 2005 08:44:12 +0100, Vincent Massol <[EMAIL PROTECTED]> wrote:
> Hi Sejo,
> 
> I'd personally go ahead with Maven 1.0.2. There should be a Maven 1.1
> version before this summer too with several components from Maven2
> backported. I believe the Maven2 team will make it as easy as possible for
> existing Maven users to switch to Maven2.
> 
> Most of the Maven1 concepts will stay but will be implemented differently
> (new POM version for example).
> 
> I'll let the Maven2 team comment further on details.
> 
> -Vincent
> 
> > -Original Message-
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> > Sent: jeudi 24 mars 2005 08:22
> > To: Maven Users List
> > Subject: maven roadmap - should i stay or should i go
> >
> > Hi all,
> >
> > In a project I am currently working on - which is just about to start with
> > the construction phase -  we are considering to use maven. I have been
> > encountering maven in previous projects as well and based on these
> > experiences i was quite sure I will use it on many others as well.
> >
> > However when i see the new roadmap description on maven site :
> >
> > < > with any of the Maven 1.x releases>>,
> >
> > i am having doubts on what exactly should we do right now.
> >
> > To take off with the current release (1.0.2) and wait for a complete
> > rewrite of our build scripts? How "complete" will that rewrite actually
> > have to be? All what the explanation in the roadmap leaves us with is a
> > bit of hope that  attempts will be made to stay backward compatible in the
> > new 2.0 release. What about the "conceptual approach", how many things can
> > we expect to be different, new or completely dissapear  (multiproject,
> > repository, ...goals)?
> >
> > Could someone point me to a document/person that can give a bit more of
> > vision/explanation concerning these issues? What would  you suggest to a
> > project that is just about to jump into maven?
> >
> > Thanks.
> >
> > -Sejo
> >
> >
> 
> -
> 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]