m2 compiler plugin and adding additional gen/src folder

[Gautham Pamu]

Hi,

I have an EJB project created using RAD6 and I have used annotation features
for the session and entity beans. So it created
additional gen/src folder for the generated code. Could you tell me how to
add this additional source to the compilation
path. There was posting on previously, they recommended Ant task but it was
clear what task I should use to
add the source to the classpath. Are they just recommending to compile the
generated source using the ant task and
copying the classes to the same folder target/classes so that packaging
phase of the maven can package these classes ?
If anyone already ran in this situation and already wrote the ant task,
could you share what task you used ?

>m2 compiler plugin and generated
source
On 10/5/05, Robert Biernat
<[EMAIL 
PROTECTED]>
wrote:
>> I'm thinking the only way to do this is to write a java based plugin that

>> programmatically plugs in the new directory.
 >
>Yes, or to write an Ant task in antrun to do it...
 >
>- Brett

Thanks in advance

--
-Gautham Pamu

[m2] Compiling JSPs

[Matt Raible]

Is there a plugin that does compilation of JSPs and adding entries into web.xml?

Here's how to do it for Maven 1, but I'd like to do it with Maven 2:

http://www.savoirtech.com/roller/page/jgenender/20041011

Here's how I've done it in Ant.















Also, is there a plugin that can generate an archetype from an existing project?

Thanks,

Matt

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

Re: [m2] Missing properties in schemaexport

[Brill Pappin]

Any idea when it will be released? Its a real pain not to have support
and docs for something most of my db driven apps use.



On 11/24/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> There is currently no release of it.
>
> http://svn.mojo.codehaus.org/trunk/mojo/mojo-sandbox/hibernate3-maven-plugin/

Re: [m1] Any plans for latest PMD into PMD plugin?

[Arnaud HERITIER]

it's ready.
The future documentation is here :
http://people.apache.org/~aheritier/maven-stage-site/maven-1.x/reference/plugins/pmd/

You can download the snapshot with :
maven plugin:download
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/
-DgroupId=maven -DartifactId=maven-pmd-plugin -Dversion=1.8-SNAPSHOT

Give us your feedback ASAP

Arnaud

On 2/18/06, Jeff Jensen <[EMAIL PROTECTED]> wrote:
> Thanks Arnaud!  Ready to test when you say so...
>
> (and thanks for the page link - I did not know that existed!)
>
>
> -Original Message-
> From: Arnaud HERITIER [mailto:[EMAIL PROTECTED]
> Sent: Saturday, February 18, 2006 9:47 AM
> To: Maven Users List
> Subject: Re: [m1] Any plans for latest PMD into PMD plugin?
>
> Hi Jeff,
>
> It wasn't done because the 3.5 release wasn't available on ibiblio.
> I'm seeing that it's now done.
> As you can see in [1] this plugin is ready to be release.
> I'll update the dependency (and i'll test if it doesn't brake
> something) and publish a new snapshot in some hours.
> You'll be able to test it and we'll call for a vote to release it the next
> week.
>
> Arnaud
>
> [1] http://docs.codehaus.org/display/MAVEN/Maven+1.1+plugins
>
>
> On 2/18/06, Jeff Jensen <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > The latest maven-pmd-plugin release is 1.7, which uses PMD version 3.2
> > (from June 21, 2005).
> >
> > The latest PMD is 3.5 (from Jan 25, 2006).
> >
> > There is a 1.8 snapshot on
> > http://cvs.apache.org/repository/maven/plugins/
> > that brings it to PMD version 3.4 (from Nov 30, 2005).
> >
> > Is it possible to bump the snapshot to 3.5?  For example, it takes
> > extra work to coordinate the differing rules between the latest PMD
> > Eclipse plugin for the developers (which has newest PMD) and the
> > latest Maven PMD plugin for the site gen (which has 3 versions older
> > PMD).  Basically, we end up with different rules files (yech!).
> >
> > Is there a release planned?  If not, can we do one??
> >
> >
> > -
> > 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: Policy for releasing plugins

[Brett Porter]

Last month, I started a process where we should be looking at plugin
status once a quarter. In addition to that, we should update the
plugin matrix to list the number of open issues for a given plugin.

Right now, the priority is on documentation, and then rounding up some
of the plugins that you've mentioned.

Help is always welcome :)

- Brett

On 2/19/06, Brian E. Fox <[EMAIL PROTECTED]> wrote:
> +1. Some of the very important plugins seem to have very infrequent
> releases (war, jar etc). It seems that the release frequency is inversly
> proportional to the importance of the plugin.
>
> -Original Message-
> From: dan tran [mailto:[EMAIL PROTECTED]
> Sent: Friday, February 17, 2006 12:45 PM
> To: Maven Users List
> Subject: Re: Policy for releasing plugins
>
> I release my plugins weekly within my comp.  But I'd like to see maven's
> plugin release more often as well.
>
> -Dan
>
>
>
> On 2/17/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
> >
> > Hi,
> >
> > I would like to discuss the policy for releasing plugins. My
> > impression is, that most plugin developers policy can be described as
> > follows:
> >
> > - Be careful. We could break something.
> > - There's a change. Goes to SVN. Fine!
> > - Some weeks later. Nothing happened. Ok, possibly it works. We'll
> > publish a "beta 1"
> > version.
> > - More weeks later. Perhaps its time for an RC1.
> > - Months later. Release
> >
> > I appreciate such a behavior for large projects like the Maven core. I
>
> > don't think so for plugins, however. Plugins have a completely
> > different characteristic:
> >
> > - They are small components, typically maintained by one or two
> > programmers only.
> > - They can be controlled.
> > - Publishing them doesn't take much work.
> > - If a problem should be found, it can be fixed really fast.
> >
> > In other words, a better policy for plugins seems to me to be the
> > "release early, release often" mantra, which we know from Perl
> > modules. Indeed, they can very well be compared.
> >
> > What do you think?
> >
> > Jochen
> >
> > --
> > Whenever you find yourself on the side of the majority, it is time to
> > pause and reflect.
> > (Mark Twain)
> >
> > -
> > 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: [ANN] Maven Checkstyle Plugin 3.0 for Maven 1.x released

[Lukas Theussl]

I have deployed a new snapshot which uses a jsl transform instead of 
ant's style task. This should eliminate any jdk related issues, please test:


maven plugin:download 
-Dmaven.repo.remote=http://www.ibiblio.org/maven,http://cvs.apache.org/repository/ 
-DgroupId=maven -DartifactId=maven-checkstyle-plugin 
-Dversion=3.0.1-SNAPSHOT



Cheers,
Lukas


Andy Fyfe wrote:

 From my experience, using JDK 5 and maven 1.0.2,
checkstyle 3.0 and  3.0.1-SNAPSHOT with or without
the setProperty fail in this manner.

--Andy




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

RE: Policy for releasing plugins

[Brian E. Fox]

+1. Some of the very important plugins seem to have very infrequent
releases (war, jar etc). It seems that the release frequency is inversly
proportional to the importance of the plugin. 

-Original Message-
From: dan tran [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 17, 2006 12:45 PM
To: Maven Users List
Subject: Re: Policy for releasing plugins

I release my plugins weekly within my comp.  But I'd like to see maven's
plugin release more often as well.

-Dan



On 2/17/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I would like to discuss the policy for releasing plugins. My 
> impression is, that most plugin developers policy can be described as
> follows:
>
> - Be careful. We could break something.
> - There's a change. Goes to SVN. Fine!
> - Some weeks later. Nothing happened. Ok, possibly it works. We'll 
> publish a "beta 1"
> version.
> - More weeks later. Perhaps its time for an RC1.
> - Months later. Release
>
> I appreciate such a behavior for large projects like the Maven core. I

> don't think so for plugins, however. Plugins have a completely 
> different characteristic:
>
> - They are small components, typically maintained by one or two 
> programmers only.
> - They can be controlled.
> - Publishing them doesn't take much work.
> - If a problem should be found, it can be fixed really fast.
>
> In other words, a better policy for plugins seems to me to be the 
> "release early, release often" mantra, which we know from Perl 
> modules. Indeed, they can very well be compared.
>
> What do you think?
>
> Jochen
>
> --
> Whenever you find yourself on the side of the majority, it is time to 
> pause and reflect.
> (Mark Twain)
>
> -
> 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: taglibs vs jstl

[Brian E. Fox]

Seems to me like taglibs should have a dependency on jstl in it's pom.  

-Original Message-
From: KC Baltz [mailto:[EMAIL PROTECTED] 
Sent: Friday, February 17, 2006 6:16 PM
To: Maven Users List
Subject: RE: taglibs vs jstl

Right.  javax is the interface, taglibs.standard is the implementation.  

I have the following in my pom:



taglibs
standard
1.1.2


javax.servlet
jstl
1.1.2


K.C.

-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Friday, February 17, 2006 8:22 AM
To: Maven Users List
Subject: Re: taglibs vs jstl


taglibs.standard !=  javax.servlet.jstl

Generally, you need both

Emmanuel

Brian E. Fox a écrit :
> I'm probably having a brain cramp now. Can anyone confirm if 
> taglibs.standard is the same as javax.servlet.jstl?
>  
> 


-
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: WAR plugin in M2: excludes not all files

[Brian E. Fox]

This is a very old bug in the war plugin (circa Nov I think?). It has
been fixed forever in the svn version, but no recent release of the war
plugin has occurred. Your best bet is to build a version yourself to
make this work. Anyone have any idea when war is going to be released?
I've had to run a private version for many months now. 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Lee Meador
Sent: Friday, February 17, 2006 2:12 PM
To: Maven Users List
Subject: Re: WAR plugin in M2: excludes not all files

If I have **/lib/*.jar, no files go into my war.

If I have **/lib/*.jar all the
dependent jars go into my war.

Putting two  sections under the  doesn't make it
work.

Is there some other stuff you have to put in the pom to make it work?

-- Lee Meador

On 2/17/06, Mang Jun Lau <[EMAIL PROTECTED]> wrote:
>
> Actually, multiple excludes do work.  You should have the following
> snippet:
>
> 
>   WEB-INF/lib/geronimo-spec*.jar
>   WEB-INF/lib/junit*.jar
> 
>
>
>
> _Mang Lau
>
>
>
>
>
> Tim Davies <[EMAIL PROTECTED]>
> 02/17/2006 06:07 AM
> Please respond to
> "Maven Users List" 
>
>
> To
> Maven Users List  cc
>
> Subject
> Re: WAR plugin in M2: excludes not all files
>
>
>
>
>
>
> I believe that there is a bug which means that multiple excludes will 
> not work but a single one will. Im afraid I cant remember where I read

> about this as it was a while ago that I came across it.
>
>
>
> Martin Goldhahn wrote:
> > Hi!
> > I'm using Maven 2.0.1
> > I have the following snippet in my pom.xml:
> >
> > 
> > org.apache.maven.plugins
> > maven-war-plugin
> > 
> > WEB-INF/lib/geronimo-spec*.jar,
> > WEB-INF/lib/junit*.jar
> > 
> > 
> >
> > This doesn't seem to work, according to the doc it should. How do I 
> > tell the plug-in the exclude both my JUnit files and the
Geronimo-spec files.
> > I tried regexps, and the warSourceExcludes tag instead of the 
> > excludes tag. The result is the same.
> >
> > Is this a bug or am I doing something wrong?
> >
> > Martin
> >
> > 
> > - To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> --
> Tim Davies
> Analyst Developer
>
> KTS PLC: Service you can bank on
> 8th Floor, Finsbury Tower,
> 103-105 Bunhill Row,
> London  EC1Y 8LZ
> tel: +44 (0)20 7256 2300
> fax: +44 (0)20 7256 2301
>
> email: [EMAIL PROTECTED]
> web: http://www.ktsplc.com
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>


--
-- Lee Meador
Sent from gmail. My real email address is [EMAIL PROTECTED]



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

RE: [m1] Any plans for latest PMD into PMD plugin?

[Jeff Jensen]

Thanks Arnaud!  Ready to test when you say so...

(and thanks for the page link - I did not know that existed!)
 

-Original Message-
From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] 
Sent: Saturday, February 18, 2006 9:47 AM
To: Maven Users List
Subject: Re: [m1] Any plans for latest PMD into PMD plugin?

Hi Jeff,

It wasn't done because the 3.5 release wasn't available on ibiblio.
I'm seeing that it's now done.
As you can see in [1] this plugin is ready to be release.
I'll update the dependency (and i'll test if it doesn't brake
something) and publish a new snapshot in some hours.
You'll be able to test it and we'll call for a vote to release it the next
week.

Arnaud

[1] http://docs.codehaus.org/display/MAVEN/Maven+1.1+plugins


On 2/18/06, Jeff Jensen <[EMAIL PROTECTED]> wrote:
> Hello,
>
> The latest maven-pmd-plugin release is 1.7, which uses PMD version 3.2 
> (from June 21, 2005).
>
> The latest PMD is 3.5 (from Jan 25, 2006).
>
> There is a 1.8 snapshot on 
> http://cvs.apache.org/repository/maven/plugins/
> that brings it to PMD version 3.4 (from Nov 30, 2005).
>
> Is it possible to bump the snapshot to 3.5?  For example, it takes 
> extra work to coordinate the differing rules between the latest PMD 
> Eclipse plugin for the developers (which has newest PMD) and the 
> latest Maven PMD plugin for the site gen (which has 3 versions older 
> PMD).  Basically, we end up with different rules files (yech!).
>
> Is there a release planned?  If not, can we do one??
>
>
> -
> 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: [M2] Eclipse WTP not Working

[Srepfler Srgjan]

Fabrizio Giustina wrote:

I've tried to use maven-eclipse-plugin's support for WTP with Eclipse
3.1.1and WTP
1.0 (latest release). I could configure a TomCat 5.5 server and add my Web
project.  I also got to the point where I could start TomCat.  However, the
application did not load due to missing libraries on the classpath.
Everything works fine when I deploy the same war manually.



The released version of the eclipse plugin only supports WTP R7.
Wtp 1.0 support has been added recently (not released yet) but there
is a bug WTP 1.0 so that external dependencies are not working at all,
see:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=116783

As a workaround, the eclipse plugin in svn will move all the
dependencies to src/main/webapp/WEB-INF/lib while generating a WTP
configuration (with -Dwtpversion=1.0) but this is absolutely a
non-optimal solution.
A working wtp 1.0.1 build should be out in a couple of weeks so we'll
wait for it before releasing a new version of the plugin (btw, if you
are running web modules inside eclipse, wtp 1.0 has a big performance
regression which makes it unusable, regardless of the external
dependency problem...)

fabrizio

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


  
Does this bug affect also WTP 1.5M4? Anyhow isn't that issue fixed at 
least according to bugzilla or was it reopened the other day?
Can I use the 1.0 project support with 1.5? What do I need and where can 
I check out to build the new eclipse plugin? Thx

Srgjan

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

Re: Deploying signed releases

[Alan D. Cabrera]

What goes into:




Is there a sample working project that I can look at?


Regards,
Alan

On 2/16/2006 1:34 AM, Michael Böckling wrote:


Hi Alan ,

Next time, please write to users@maven.apache.org, this list is for 
maven development!


To use Jar signing, you have to checkout the latest SVN version of the 
maven-jar-plugin and install it.

Then, include this in your POM:



  
 
   org.apache.maven.plugins
   maven-jar-plugin
   2.1-SNAPSHOT
   
 
   jar.sign
   
 sign
   
   
 
 signed
   
 
   
 

How, your signed artifacts will be deployed as 
--signed.jar
Simply use "signed" as classifier in your dependecies-section to use 
the signed instead of the unsigned version.


Regards,
   Michael



How do I do this?


Regards,
Alan


-
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: [m2] HibernateDoclet

[Jacek Laskowski]

2006/2/15, Frederic Close <[EMAIL PROTECTED]>:
> hi,
>
> I have an application using hibernate (2.1) and I used an ant task +
> xdoclet in order to generate the hibernate mapping files (.hbm.xml).
>
> Could one of you point me to the good direction to get started with this.

Hi,

You may want to use the Maven2 XDoclet2 plugin:
http://xdoclet.codehaus.org/Maven2+plugin.

> Fred

Jacek

--
Jacek Laskowski
http://www.laskowski.org.pl

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

Re: [m1] Any plans for latest PMD into PMD plugin?

[Wayne Fay]

This is great news. Thanks Arnaud.

Wayne


On 2/18/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Hi Jeff,
>
> It wasn't done because the 3.5 release wasn't available on ibiblio.
> I'm seeing that it's now done.
> As you can see in [1] this plugin is ready to be release.
> I'll update the dependency (and i'll test if it doesn't brake
> something) and publish a new snapshot in some hours.
> You'll be able to test it and we'll call for a vote to release it the next 
> week.
>
> Arnaud
>
> [1] http://docs.codehaus.org/display/MAVEN/Maven+1.1+plugins
>
>
> On 2/18/06, Jeff Jensen <[EMAIL PROTECTED]> wrote:
> > Hello,
> >
> > The latest maven-pmd-plugin release is 1.7, which uses PMD version 3.2 (from
> > June 21, 2005).
> >
> > The latest PMD is 3.5 (from Jan 25, 2006).
> >
> > There is a 1.8 snapshot on http://cvs.apache.org/repository/maven/plugins/
> > that brings it to PMD version 3.4 (from Nov 30, 2005).
> >
> > Is it possible to bump the snapshot to 3.5?  For example, it takes extra
> > work to coordinate the differing rules between the latest PMD Eclipse plugin
> > for the developers (which has newest PMD) and the latest Maven PMD plugin
> > for the site gen (which has 3 versions older PMD).  Basically, we end up
> > with different rules files (yech!).
> >
> > Is there a release planned?  If not, can we do one??
> >
> >
> > -
> > 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: [m2] Xpp3 in ibiblio repo is very strange

[Wayne Fay]

Thanks Dan.

I've found a few other POMs that don't comply to M2 format (ie
3.0.0) and I'll post all those bugs to
the MEV JIRA, along with patches.

Wayne


On 2/18/06, Dan Diephouse <[EMAIL PROTECTED]> wrote:
> I think you just need to file an issue in the MEV JIRA.
> http://jira.codehaus.org/browse/MEV
>
> Also, patches for the poms expedite the process.
> - Dan
>
> Wayne Fay wrote:
> > This is bizarre...
> >
> > http://www.ibiblio.org/maven2/xpp3/xpp3/1.1.3.4/
> >
> > xpp3-1.1.3.4-RC3_min.jar (md5, sha1)
> > xpp3-1.1.3.4-RC8_min.jar (md5, sha1)
> > xpp3-1.1.3.4.pom  (md5, sha1)
> >
> > I tried:
> > 
> >   xpp3
> >   xpp3
> >   1.1.3.4
> > 
> >
> > Of course this fails because the name of the jar is actually
> > xpp-1.1.3.4-RC8_min.jar and M2 can't find the right directory etc.
> >
> > How in the world did these files end up in Maven2 repository? And what
> > can we do to fix it? All we'd need to do is move those files out of
> > this directory and into directories named 1.1.3.4-RC3_min/... and
> > 1.1.3.4-RC8_min/... with appropriate poms etc.
> >
> > Obviously I can pull down the jars and add them manually to my own
> > local repo. But I'd rather get this fixed in the master M2 repo so we
> > can all benefit.
> >
> > Thanks.
> > Wayne
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Dan Diephouse
> Envoi Solutions LLC
> http://envoisolutions.com
> http://netzooid.com/blog
>
>
> -
> 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: [m2] Xpp3 in ibiblio repo is very strange

[Dan Diephouse]

I think you just need to file an issue in the MEV JIRA.
http://jira.codehaus.org/browse/MEV

Also, patches for the poms expedite the process.
- Dan

Wayne Fay wrote:

This is bizarre...

http://www.ibiblio.org/maven2/xpp3/xpp3/1.1.3.4/

xpp3-1.1.3.4-RC3_min.jar (md5, sha1)
xpp3-1.1.3.4-RC8_min.jar (md5, sha1)
xpp3-1.1.3.4.pom  (md5, sha1)

I tried:

  xpp3
  xpp3
  1.1.3.4


Of course this fails because the name of the jar is actually
xpp-1.1.3.4-RC8_min.jar and M2 can't find the right directory etc.

How in the world did these files end up in Maven2 repository? And what
can we do to fix it? All we'd need to do is move those files out of
this directory and into directories named 1.1.3.4-RC3_min/... and
1.1.3.4-RC8_min/... with appropriate poms etc.

Obviously I can pull down the jars and add them manually to my own
local repo. But I'd rather get this fixed in the master M2 repo so we
can all benefit.

Thanks.
Wayne

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

  



--
Dan Diephouse
Envoi Solutions LLC
http://envoisolutions.com
http://netzooid.com/blog


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

Re: "scm url is invalid" with release:prepare

[Dan Diephouse]

Some information here for those who run into this...
- You definitely need the latest scm packages (should be out soon)
- You can't use this with eclipse and the extssh protocol, you need to 
check out your sources over ext via regular CVS
- Be careful that you delete release.properties if you change your 
setting such as your username as it overrides what is in the POM


- Dan

Dan Diephouse wrote:
OK so I grabbed the latest scm stuff and release plugin from cvs and 
here is what I did:


in the scm directory:
$ mvn -Dmaven.test.skip install

Skipped tests because they didnt' all pass. In the release plugin dir
$ mvn install

Then I declared the beta-4-SNAPSHOT release plugin in my POM like I 
showed below. But I still get the same error. Any ideas?


- Dan

Dan Diephouse wrote:

Wait, do I have to install newer version of maven scm?
- Dan

Dan Diephouse wrote:

I installed a snapshot and am still getting the error:
[INFO] 
 


[ERROR] BUILD ERROR
[INFO] 
 


[INFO] Can't load the scm provider.

Embedded error: The scm url is invalid.

This is what I added to my POM:

   org.apache.maven.plugins
   maven-release-plugin
   2.0-beta-4-SNAPSHOT
   

I tried it with and without the colon after the ${maven.username} too.

- Dan

Emmanuel Venisse wrote:
I think it's an error in cvs provider. Actual version of release 
plugin use an old version of it (1.0-alpha-2). We are now in 
1.0-beta-2 and 1.0 will be release in few days.


You can try release plugin snapshot from svn.

Emmanuel

Dan Diephouse a écrit :

Nah, I tried that too.  Eclipse has my cvs url set to:

:extssh:[EMAIL PROTECTED]:/home/projects/xfire/scm

Is that going to cause problems?
- Dan

dan tran wrote:


wild guess,

${maven.username}:@

You need a ":" after username

-D


On 2/16/06, Dan Diephouse <[EMAIL PROTECTED]> wrote:
 

I am trying to do a release, but Maven 2 doesn't seem to like my 
scm

url. Here is the scm section from my POM:



scm:cvs:pserver:anonymous:@cvs.xfire.codehaus.org
:/home/projects/xfire/scm:xfire

scm:cvs:ext:${maven.username}@
cvs.xfire.codehaus.org:/home/projects/xfire/scm:xfire

 https://cvs.xfire.codehaus.org/viewrep/xfire
   

Here is the output I get from runinng release:prepare (I skipped 
the

tests to test this functionality, but that doesn't seem to make a
difference)

[INFO] Verifying there are no local modifications ...
[INFO]

 


[ERROR] BUILD ERROR
[INFO]

 


[INFO] An error is occurred in the status process.

Embedded error: Can't load the scm provider.
The scm url is invalid.

Any ideas?

--
Dan Diephouse
Envoi Solutions LLC
http://envoisolutions.com
http://netzooid.com/blog


- 


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]













--
Dan Diephouse
Envoi Solutions LLC
http://envoisolutions.com
http://netzooid.com/blog


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

Re: [m1] Any plans for latest PMD into PMD plugin?

[Arnaud HERITIER]

Hi Jeff,

It wasn't done because the 3.5 release wasn't available on ibiblio.
I'm seeing that it's now done.
As you can see in [1] this plugin is ready to be release.
I'll update the dependency (and i'll test if it doesn't brake
something) and publish a new snapshot in some hours.
You'll be able to test it and we'll call for a vote to release it the next week.

Arnaud

[1] http://docs.codehaus.org/display/MAVEN/Maven+1.1+plugins


On 2/18/06, Jeff Jensen <[EMAIL PROTECTED]> wrote:
> Hello,
>
> The latest maven-pmd-plugin release is 1.7, which uses PMD version 3.2 (from
> June 21, 2005).
>
> The latest PMD is 3.5 (from Jan 25, 2006).
>
> There is a 1.8 snapshot on http://cvs.apache.org/repository/maven/plugins/
> that brings it to PMD version 3.4 (from Nov 30, 2005).
>
> Is it possible to bump the snapshot to 3.5?  For example, it takes extra
> work to coordinate the differing rules between the latest PMD Eclipse plugin
> for the developers (which has newest PMD) and the latest Maven PMD plugin
> for the site gen (which has 3 versions older PMD).  Basically, we end up
> with different rules files (yech!).
>
> Is there a release planned?  If not, can we do one??
>
>
> -
> 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]

[m1] Any plans for latest PMD into PMD plugin?

[Jeff Jensen]

Hello,

The latest maven-pmd-plugin release is 1.7, which uses PMD version 3.2 (from
June 21, 2005).

The latest PMD is 3.5 (from Jan 25, 2006).

There is a 1.8 snapshot on http://cvs.apache.org/repository/maven/plugins/
that brings it to PMD version 3.4 (from Nov 30, 2005).

Is it possible to bump the snapshot to 3.5?  For example, it takes extra
work to coordinate the differing rules between the latest PMD Eclipse plugin
for the developers (which has newest PMD) and the latest Maven PMD plugin
for the site gen (which has 3 versions older PMD).  Basically, we end up
with different rules files (yech!).

Is there a release planned?  If not, can we do one??


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

RE: [m2] jetty6 plugin & log4j

[Ceki Gülcü]

David,

I am not very familiar with maven-jetty6-plugin. However, from what
you describe, it looks like jetty is using SLF4J's SimpleLogger
binding instead of its log4j binding. This is attested by the
following line:

 2 [main] INFO org.mortbay.log - Logging to
[EMAIL PROTECTED] via org.mortbay.log.Slf4jLog

When Jetty uses SLF4J's SimpleLogger binding log4j configuration files
have no affect as log4j is not used by Jetty. You need to instruct
Maven or Jetty to use the correct binding. For more details on SLF4J
bindings please see http://www.slf4j.org.

> Hello all -
>
> Could anyone help me to understand how to change the log level that
> the maven-jetty6-plugin uses?  I would like to put debug logging
> statements into my code, but then I can't seem to figure out how to
> get the plugin to change from its default info level.  I would also
> like to set different logging levels on package name.
>
> Note also that I am using the Spring framework.  So first I tried
> using its Log4jConfigListener web util class in web.xml and pointing
> it at my log4j.properties file.  Info messages appeared indicating
> that it was alive and had read my configuration:
>
> 929 [main] INFO /myapp - Initializing Log4J from [/Users/davidm/
> dev/myapp/src/main/resources/webapp/WEB-INF/log4j.properties]
>
> But no changes were evident in the logged message, neither in format
> nor level.
>
> Then I found a posting on Gmane that indicated you can give Jetty
> your own log4j.properties file by configuring a systemProperty named
> "log4j.configuration", which I did in pom.xml.  Again, messages
> indicated that Jetty recognized my property setting:
>
> [INFO] Property log4j.configuration=/WEB-INF/log4j.properties was
> set
>
> but nothing seemed to change the way it logs.  In fact, two lines
> later in the log, there is this message:
>
> 2 [main] INFO org.mortbay.log - Logging to
> [EMAIL PROTECTED] via org.mortbay.log.Slf4jLog
>
> Here's my (very simple) log4j.properties file:
>
> log4j.rootLogger=WARN, stdout
>
> log4j.appender.stdout=org.apache.log4j.ConsoleAppender
> log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
> log4j.appender.stdout.layout.ConversionPattern=%d{ABSOLUTE} %5p %c
> {1}:%L - %m%n
>
> log4j.logger.net.sf.hibernate=WARN
> log4j.logger.net.sf.hibernate.type=WARN
> log4j.logger.org.springframework=WARN
>
> I read Jetty's tutorial on logging, but it :
> http://www.mortbay.org/jetty/tut/logging.html
>
> Finally, I gave the "-DDEBUG" and "-DDEBUG_PATTERNS=net.sf.hibernate"
> a shot, but these too seemed to be ignored.
>
> I get the feeling that I am clashing somehow with Jetty's own
> logging.  Can anyone help me unravel this?
>
> Thanks
> --David


--
Ceki Gülcü


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

ant plugin throwing error for execution of native2ascii task of ant

[Amit Khurana]

Hi Guys
 
As my project supports many languages, so I have various properties file
in utf8 encoding for messages to display on jsps. While building my
project through ant I run native2ascii tag
 

   
  
 
While using maven to build my project, I am doing the same step using
ant plugin in my pom file like this
 
search-app

   
   maven-antrun-plugin
   
 
   generate-sources
   
  

  
  

   
   
 run
   
 
   
   


 
but maven is throwing this exception
 
"[ERROR] BUILD ERROR
[INFO]


[INFO] Error executing ant tasks
 
Embedded error: Could not create task or type of type: native2ascii.
 
Ant could not find the task or a class this task relies upon.
 
This is common and has a number of causes; the usual
solutions are to read the manual pages then download and
install needed JAR files, or fix the build file:
 - You have misspelt 'native2ascii'.
   Fix: check your spelling.
 - The task needs an external JAR file to execute
 and this is not found at the right place in the classpath.
   Fix: check the documentation for dependencies.
   Fix: declare the task.
 - The task is an Ant optional task and the JAR file and/or libraries
 implementing the functionality were not found at the time you
 yourself built your installation of Ant from the Ant sources.
   Fix: Look in the ANT_HOME/lib for the 'ant-' JAR corresponding to the
 task and make sure it contains more than merely a
META-INF/MANIFEST.MF.
 If all it contains is the manifest, then rebuild Ant with the
needed
 libraries present in ${ant.home}/lib/optional/ , or alternatively,
 download a pre-built release version from apache.org
 - The build file was written for a later version of Ant
   Fix: upgrade to at least the latest release version of Ant
 - The task is not an Ant core or optional task
 and needs to be declared using .
 - You are attempting to use a task defined using
 or  but have spelt wrong or not
   defined it at the point of use
 
Remember that for JAR files to be visible to Ant tasks implemented
in ANT_HOME/lib, the files must be in the same directory or on the
classpath
 
Please neither file bug reports on this problem, nor email the
Ant mailing lists, until all of these causes have been explored,
as this is not an Ant bug.
 
If instead of native2ascii task, I execute simple copy or delete that
works fine. So assuming there is no issue with ant setting. Any Idea?
 
Thanks in advance
Amit