Re: maven-clover-plugin not working

[Jeff Mutonho]

On 11/15/06, Vincent Massol <[EMAIL PROTECTED]> wrote:


I'll try to have a look at it today (no guarantees though). What you could
investigate is to read the code and fix what's wrong! :-)


Lol...Of course... I forgot I should just leap in and submit a patch
:^) .Seriously though, will take a look

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

Re: Surefire report issues

[Dave Syer]

Wayne Fay wrote:
> 
> Chris H sent an email to the list on a similar topic recently that
> might be helpful to you:
> 

Thanks, I saw that.  I might even use it (if I can get it to work - I
haven't so far).  I was also looking for general comments on surefire
reports.  What are they supposed to give me that I can't get from JUnit? 
Why are they the default if there are so many problems with them?
-- 
View this message in context: 
http://www.nabble.com/Surefire-report-issues-tf2634455s177.html#a735
Sent from the Maven - Users mailing list archive at Nabble.com.


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

RE: maven-clover-plugin not working

[Vincent Massol]

Jeff,

I'll try to have a look at it today (no guarantees though). What you could
investigate is to read the code and fix what's wrong! :-)

I gave it a cursory look and couldn't find anything especially as several
users are using the exclude mechanism and it seems to work fine for them
(except for the compile bug reported today by Nick:
http://jira.codehaus.org/browse/MCLOVER-62

Thanks
-Vincent

> -Original Message-
> From: Jeff Mutonho [mailto:[EMAIL PROTECTED]
> Sent: mercredi 15 novembre 2006 07:59
> To: Maven Users List
> Subject: Re: maven-clover-plugin  not working
> 
> Hi guys
> 
> Anyone with an idea what I could perhaps investigate?
> 
> 
> 
> 
> --
> 
> Jeff  Mutonho
> Cape Town
> South Africa
> 
> GoogleTalk : ejbengine
> Skype: ejbengine
> Registered Linux user number 366042
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]






___ 
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! 
Profitez des connaissances, des opinions et des expériences des internautes sur 
Yahoo! Questions/Réponses 
http://fr.answers.yahoo.com

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

Re: maven-clover-plugin not working

[Wayne Fay]

You can try setting the debug flags and stepping through the
maven-clover-plugin code in Eclipse/Netbeans while its executing...

Wayne

On 11/15/06, Jeff Mutonho <[EMAIL PROTECTED]> wrote:

Hi guys

Anyone with an idea what I could perhaps investigate?




--

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042

-
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: Surefire report issues

[Wayne Fay]

Chris H sent an email to the list on a similar topic recently that
might be helpful to you:

From: "Chris Hilton" <[EMAIL PROTECTED]>
To: "Maven Users List" 
Subject: RE: replace surefire with ant task
Date: Fri, 3 Nov 2006 11:24:30 -0600

Wayne


On 11/15/06, Dave Syer <[EMAIL PROTECTED]> wrote:


Does anyone have any experience with using the surefire report is a large
project (like 1000s of unit tests)?  I can imagine that the single-page
format of the report would be a problem - hard to read, long time to load in
browser.

Also, I noticed a problem with the surefire report contents.  It seems to
create a report that lists test results grouped together by package and
class, but when you look closer you find tests from other classes and even
other packages in the same group.  It looks like total anarchy.  Surely this
must be wrong?  Am I missing something?

I would prefer to go back to the old JUnit style aggregate reporting.  Can I
do that?  How?  If I can, why would I not?
--
View this message in context:
http://www.nabble.com/Surefire-report-issues-tf2634455s177.html#a7353146
Sent from the Maven - Users mailing list archive at Nabble.com.


-
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]

Surefire report issues

[Dave Syer]

Does anyone have any experience with using the surefire report is a large
project (like 1000s of unit tests)?  I can imagine that the single-page
format of the report would be a problem - hard to read, long time to load in
browser.

Also, I noticed a problem with the surefire report contents.  It seems to
create a report that lists test results grouped together by package and
class, but when you look closer you find tests from other classes and even
other packages in the same group.  It looks like total anarchy.  Surely this
must be wrong?  Am I missing something?

I would prefer to go back to the old JUnit style aggregate reporting.  Can I
do that?  How?  If I can, why would I not?
-- 
View this message in context: 
http://www.nabble.com/Surefire-report-issues-tf2634455s177.html#a7353146
Sent from the Maven - Users mailing list archive at Nabble.com.


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

maven-plugin-testing-harness: Nonexistent component

[Jochen Wiedmann]

Hi,

in order to fix some bugs in the javacc plugins JTBMojo, I wrote a
little integration test, based on the maven-plugin-testing-harness.
However, I am unable to get it running, because I always receive the
following error message:

[ERROR] Nonexistent component:
org.apache.maven.plugin.Mojoorg.codehaus.mojo:javacc-maven-plugin:2.2-SNAPSHOT:jtb
org.codehaus.plexus.component.repository.exception.ComponentLookupException:
Component descriptor cannot be found in the component repository:
org.apache.maven.plugin.Mojoorg.codehaus.mojo:javacc-maven-plugin:2.2-SNAPSHOT:jtb.
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:319)
at 
org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:436)
at org.codehaus.plexus.PlexusTestCase.lookup(PlexusTestCase.java:222)
at 
org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:164)
at 
org.apache.maven.plugin.testing.AbstractMojoTestCase.lookupMojo(AbstractMojoTestCase.java:110)
at 
org.codehaus.mojo.javacc.test.JTBMojoTest.newMojo(JTBMojoTest.java:42)
at 
org.codehaus.mojo.javacc.test.JTBMojoTest.runTest(JTBMojoTest.java:53)
at 
org.codehaus.mojo.javacc.test.JTBMojoTest.testJTB(JTBMojoTest.java:35)

Would anyone please be so kind to check what I might be doing wrong?
Here's my POM:

   
4.0.0
  
org.codehaus.mojo
javacc-maven-plugin
2.2-SNAPSHOT
  
  javacc-maven-plugin-it1
  

  
org.codehaus.mojo
javacc-maven-plugin
2.2-SNAPSHOT

  

 
 

and here's my test case:
public class JTBMojoTest extends AbstractMojoTestCase {
   /**
* Tests running the WSDL generator.
*/
   public void testJTB() throws Exception {
   final String dir = "src/test/it1";
   runTest(dir , "jtb" );
   }

   protected JTBMojo newMojo( String pDir, String pGoal ) throws Exception
   {
   final File baseDir = new File(new File(getBasedir()), pDir);
   File testPom = new File( baseDir, "pom.xml" );
   JTBMojo mojo = (JTBMojo) lookupMojo( pGoal, testPom );
   MavenProjectStub project = new MavenProjectStub(){
   public File getBasedir() { return baseDir; }
   };
   setVariableValueToObject(mojo, "project", project);
   return mojo;
   }

   protected void runTest( String pDir, String pGoal )
   throws Exception
   {
   newMojo( pDir, pGoal ).execute();
   }
}


Thanks,

Jochen



--
My wife Mary and I have been married for forty-seven years and not
once have we had an argument serious enough to consider divorce;
murder, yes, but divorce, never.
(Jack Benny)

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

Re: maven-clover-plugin not working

[Jeff Mutonho]

Hi guys

Anyone with an idea what I could perhaps investigate?




--

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042

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

Re: Maven dependency question

[Wayne Fay]

Incorrect, Lee M. responded to you earlier...

-- Forwarded message --
From: Lee Meador <[EMAIL PROTECTED]>
Date: Nov 14, 2006 3:17 PM
Subject: Re: Maven dependency question
To: Maven Users List 


What I do is put the utility jar in my dependency for the war as compile.
Then I put an exclude in the pom for the war that tells it to leave out the
jar and not put it into the war. The classloader for your application server
should cause the war to have access to the jar since it is in the ejb jar's
classpath. This has to do with the nesting of the classloaders. Some app
servers let you change the way that works though.

-- Lee


On 11/14/06, Enrique Gaona <[EMAIL PROTECTED]> wrote:




I posted this message earlier and didnt get any replies. Anyone know the 
answer:) Thanks.

Enrique

Enrique Gaona/Austin/[EMAIL PROTECTED]







Enrique Gaona/Austin/[EMAIL PROTECTED]

11/14/2006 01:33 PM

Please respond to
"Maven Users List" 


To
users@maven.apache.org


cc



Subject
Maven dependency question




Hi folks,

We have a J2EE application project (ear) which contains one Web project
(war), one EJB project and one utilities java project.
The war and EJB jar projects depends from the same utilities project.
We included the WEB, EJB and utilities projects as dependencies into the
ear pom file, so all three output files are included into ear file.
EJB project works as expected it only adds Class-Path: entry into its
Manifest.MF class

The problem with the Web project, it adds the common utility jar file into
its WEB-INF/lib directory. We tried to change the dependency scope from
"compile" to "provided". In this case neither the jar was  added nor the
Class-Path: entry.

How can we specify dependency from the common utility jar file in the war's
pom file?

Any help is appreciated.  Thanks

Enrique





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

Re: EhCacheProvider not found with other hibernate classes during test

[Wayne Fay]

Run mvn -X and then grep the output for ehcache... You'll probably see
a different version getting pulled in by another dependency
somewhere...

Wayne

On 11/14/06, Trevor Torrez <[EMAIL PROTECTED]> wrote:

Ok; that almost makes sense; what, other than 'Quartz' should I search
nabble for?  I cant find anything relevent.

Answers to any of the following questions would also be appreciated:

How do i find out which of the dependencies is requesting the bogus
version?  The only thing 'maven site' shows in the dependencies is
ehcache-1.2, the version that must be used with hibernate-3.  The dependency
graph shows that ehcache was required by hibernate-3, and no other
(dissimilar) reference to ehcache is on the page.  I pulled out explicit
dependencies on hibernate from my project pom, and likewise the only
hibernate listed is 3.2.0.rc4 required by spring-hibernate3.

Why is it a class not found exception for a class that is obviously there
and correct and not a no-class-def error as would be expected for a bogus
version of a dependency (wrong method invocation, exception in initializer,
etc)?

Why is this error not showing up in eclipse, when as far as i can tell the
same jar files are being used.

Thanks; much appreciated;
-t.

On 11/14/06, Lee Meador <[EMAIL PROTECTED]> wrote:
>
> This has been discussed before. You can find it in nabble, I think.
>
> The issue has to do with spring wanting one version of hibernate and
> hibernate wanting a version of ehcache and the versions conflict with each
> other. In my case, using Quartz which wanted another version of ehcache,
> it
> would pick one version of ehcache for one project and another version for
> another project.
>
> You solve it by specifying versions for things in some places and
> excluding
> dependencies in others. I forget the details.
>
> -- Lee
> [snip]
>
> --
> -- Lee Meador
> Sent from gmail. My real email address is lee AT leemeador.com
>
>




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

Re: Deployment without installation

[Wayne Fay]

mvn deploy:deploy-file

Wayne

On 11/14/06, Morgovsky, Alexander (US - Glen Mills)
<[EMAIL PROTECTED]> wrote:

Is it possible to execute a deploy operation without doing an install?
This is when, for example, the application is already installed, and I
just want to call deploy.  Thanks.


This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, you should delete this message.


Any disclosure, copying, or distribution of this message, or the taking of any 
action based on it, is strictly prohibited. [v.E.1]




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

Re: java2iiop (Visibroker)

[Dan Tran]

Jim,  A snapshot has been deployed to
http://snapshots.repository.codehaus.org

It is best to build from source

http://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/visibroker-maven-plugin/

-D


On 11/14/06, Jim Bethancourt <[EMAIL PROTECTED]> wrote:


Hi Dan,
I've finally been able to tinker a little more and got the build
section settings correct (I think)  that you've mentioned on the
website, but the plugin isn't downloading and I'm not finding it in
the subversion repository, unless I'm looking in the wrong place.  Any
pointers you might be able to provide would be really handy.  Is there
any possibility you could post it to the mojo sandbox?

Thanks,
Jim

On 10/30/06, Jim Bethancourt <[EMAIL PROTECTED]> wrote:
> Dan,
> Awesome!  Thanks so much.  I'd be happy to help where I can.
> Jim
>
> On 10/29/06, Dan Tran <[EMAIL PROTECTED]> wrote:
> > Jim, I just cookedup a set of maven wrappers for visibroker tools.
> > Please provide feedbacks, patches, docs if you find it it useful.
> >
> > You will need to check out the source at mojo-sandbox
> >
> > The site is at  http://mojo.codehaus.org/visibroker-maven-plugin/
> >
> >
> > -D
> >
> >
> > On 10/28/06, Jim Bethancourt <[EMAIL PROTECTED]> wrote:
> > >
> > > Hi Tim,
> > > I've been tinkering with migrating the build process for the place
> > > where I work from Ant to Maven 2 and noticed that you worked on a
> > > VisiBroker plugin for Maven 2 and had considered posting it.  Any
> > > chance you could consider posting it?  I know I could put it to use
> > > quickly and I'm sure plenty of other folks using VisiBroker would
find
> > > it very useful too.
> > >
> > > Thanks,
> > > Jim
> > >
> > > On 6/27/06, TimHedger <[EMAIL PROTECTED]> wrote:
> > > >
> > > > Thanks Dan - got most of it working now.
> > > > --
> > > > View this message in context:
> > >
http://www.nabble.com/java2iiop-%28Visibroker%29-tf1846831.html#a5071927
> > > > Sent from the Maven - Users forum at Nabble.com <
http://nabble.com/>.
> > > >
> > > >
> > > >
-
> > > > 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: java2iiop (Visibroker)

[Jim Bethancourt]

Hi Dan,
I've finally been able to tinker a little more and got the build
section settings correct (I think)  that you've mentioned on the
website, but the plugin isn't downloading and I'm not finding it in
the subversion repository, unless I'm looking in the wrong place.  Any
pointers you might be able to provide would be really handy.  Is there
any possibility you could post it to the mojo sandbox?

Thanks,
Jim

On 10/30/06, Jim Bethancourt <[EMAIL PROTECTED]> wrote:

Dan,
Awesome!  Thanks so much.  I'd be happy to help where I can.
Jim

On 10/29/06, Dan Tran <[EMAIL PROTECTED]> wrote:
> Jim, I just cookedup a set of maven wrappers for visibroker tools.
> Please provide feedbacks, patches, docs if you find it it useful.
>
> You will need to check out the source at mojo-sandbox
>
> The site is at  http://mojo.codehaus.org/visibroker-maven-plugin/
>
>
> -D
>
>
> On 10/28/06, Jim Bethancourt <[EMAIL PROTECTED]> wrote:
> >
> > Hi Tim,
> > I've been tinkering with migrating the build process for the place
> > where I work from Ant to Maven 2 and noticed that you worked on a
> > VisiBroker plugin for Maven 2 and had considered posting it.  Any
> > chance you could consider posting it?  I know I could put it to use
> > quickly and I'm sure plenty of other folks using VisiBroker would find
> > it very useful too.
> >
> > Thanks,
> > Jim
> >
> > On 6/27/06, TimHedger <[EMAIL PROTECTED]> wrote:
> > >
> > > Thanks Dan - got most of it working now.
> > > --
> > > View this message in context:
> > http://www.nabble.com/java2iiop-%28Visibroker%29-tf1846831.html#a5071927
> > > Sent from the Maven - Users forum at Nabble.com .
> > >
> > >
> > > -
> > > 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: site-deploy not copying Java Docs

[Dmystery]

I dont think it adresses the issue here. I changed it to the lastest plugin
though :) 

dennisl-2 wrote:
> 
> Dmystery wrote:
>> I've a multi-module project for which i'm generating a site. 
>> 
>> I'm doing a mvn site:stage -DstagingDirectory=somedirectory. This works
>> fine
>> and the modules are linked properly too. However, the Java doc generated
>> are
>> not copied to the staging directory. Only the index.html is copied, the
>> rest
>> remains in the project build directory. 
>> 
>> My parent pom looks like, 
>> .
>> .
>> 
>>   
>>   my-site 
>>   my-site 
>>   file:// 
>>   
>> 
>> 
>> 
>>
>>  
>>maven-javadoc-plugin
>>  
>>  
>>org.codehaus.mojo
>>jxr-maven-plugin
>>
>>
>> 
>> .
>> .
>> 
>> Interestingly, instead of the above command, if i use 'mvn site-deploy'
>> with
>> 
>>   
>>   my-site 
>>   my-site 
>>   file://c:/somedirectory 
>>  
>> 
>> in my pom, the apidocs are copied but the module and apidocs links do not
>> exists. 
>> 
>> Is there a clean way of deploying a site on to the local machine?? 
> 
> You might want to replace the old org.codehaus.mojo:jxr-maven-plugin 
> with the newer org.apache.maven.plugins:maven-jxr-plugin.
> 
> -- 
> Dennis Lundberg
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/site-deploy-not-copying-Java-Docs-tf2628872s177.html#a7352031
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: change the local repository in maven 1.x

[Neeraj Bisht]

thank it works

On 11/15/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:


in your project or user settings you define the property
maven.repo.local=c:/somewherelese

http://maven.apache.org/maven-1.x/reference/properties.html

Arnaud



On 11/14/06, Neeraj Bisht <[EMAIL PROTECTED]> wrote:
>
> hi
> we are using GWT ,and we build our GWT project with maven 1.x ,now
> google release new jar and this time the jar path should not contain any
> spaces in between the path
> but we all know that maven build the repository at
> $(userhome}/.maven/repositort
>
> and  userhome contain spaces like c:/document and seeting/   (by
> default
> maven genrate the local repository at this location)
>
> now i need to change the local repository to the place where there is no
> space in path
>
> like c:/mavenrepository
>
> in maven 2.x i know we can do it by seeting.xml how we can do in maven
> 1.xplease any body tell me with example
>
> Regards
> Neeraj
>
>

Re: Maven dependency question

[Enrique Gaona]

I posted this message earlier and didnt get any replies.  Anyone know the answer:)  Thanks.

Enrique

Enrique Gaona/Austin/[EMAIL PROTECTED]








Enrique Gaona/Austin/[EMAIL PROTECTED] 
11/14/2006 01:33 PM

Please respond to
"Maven Users List" 








To
users@maven.apache.org


cc



Subject
Maven dependency question










Hi folks,

We have a J2EE application project (ear) which contains one Web project
(war), one EJB project and one utilities java project.
The war and EJB jar projects depends from the same utilities project.
We included the WEB, EJB and utilities projects as dependencies into the
ear pom file, so all three output files are included into ear file.
EJB project works as expected it only adds Class-Path: entry into its
Manifest.MF class

The problem with the Web project, it adds the common utility jar file into
its WEB-INF/lib directory. We tried to change the dependency scope from
"compile" to "provided". In this case neither the jar was  added nor the
Class-Path: entry.

How can we specify dependency from the common utility jar file in the war's
pom file?

Any help is appreciated.  Thanks

Enrique

Re: Running Maven 2 reports

[Alan D. Salewski]

On Tue, Nov 14, 2006 at 03:28:31PM -0600, Morgovsky, Alexander (US - Glen 
Mills) spake thus:
> Is it possible to run Maven 2 reports, like pmd, for example, outside of
> the site generation phase?  For example, if I want to create a report
> without associating it with any site, can I do this?  If so, how can I
> do this?  Thanks. 

Sure. I generate just the dependency report all the time with this:

$ mvn -o project-info-reports:dependencies

(I find that difficult enough to remember that I've created a
'mvn-dep-report' shell alias...)

To generate both the 'dependencies' report and the 'license' report, I
would do this:

$ mvn -o project-info-reports:dependencies project-info-reports:license

Check the documentation for a specific plugin for the name of the goal
to run to create a specific report.

-Al

-- 
:: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: ::
::
Alan D. Salewski
Software Developer
Health Market Science, Inc.
:: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: ::
:: 

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

Re: EhCacheProvider not found with other hibernate classes during test

[Trevor Torrez]

Ok; that almost makes sense; what, other than 'Quartz' should I search
nabble for?  I cant find anything relevent.

Answers to any of the following questions would also be appreciated:

How do i find out which of the dependencies is requesting the bogus
version?  The only thing 'maven site' shows in the dependencies is
ehcache-1.2, the version that must be used with hibernate-3.  The dependency
graph shows that ehcache was required by hibernate-3, and no other
(dissimilar) reference to ehcache is on the page.  I pulled out explicit
dependencies on hibernate from my project pom, and likewise the only
hibernate listed is 3.2.0.rc4 required by spring-hibernate3.

Why is it a class not found exception for a class that is obviously there
and correct and not a no-class-def error as would be expected for a bogus
version of a dependency (wrong method invocation, exception in initializer,
etc)?

Why is this error not showing up in eclipse, when as far as i can tell the
same jar files are being used.

Thanks; much appreciated;
-t.

On 11/14/06, Lee Meador <[EMAIL PROTECTED]> wrote:


This has been discussed before. You can find it in nabble, I think.

The issue has to do with spring wanting one version of hibernate and
hibernate wanting a version of ehcache and the versions conflict with each
other. In my case, using Quartz which wanted another version of ehcache,
it
would pick one version of ehcache for one project and another version for
another project.

You solve it by specifying versions for things in some places and
excluding
dependencies in others. I forget the details.

-- Lee
[snip]

--
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com

Re: http://www.ibiblio.org/maven2 vs. http://repo1.maven.org/maven2?

[jiangshachina]

Dear Wayne,
Thanks very much!

a cup of Java, cheers!
Sha Jiang


Wayne Fay wrote:
> 
> You can use the Geronimo-provided J2EE jars for now, while waiting for
> the Sun JavaEE jars to be published under an open source license etc:
> 
> http://www.ibiblio.org/pub/packages/maven2/geronimo-spec/
> http://www.ibiblio.org/pub/packages/maven2/geronimo/
> 
> The Glassfish jars are slowly making their way into Maven repos too so
> you could use those instead of Geronimo if you prefer, assuming the
> jars are available from both sources.
> 
> Wayne
> 
> On 11/14/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
>> If you look in more detail:
>> http://www.ibiblio.org/pub/packages/maven2/javax/j2ee/j2ee/1.4/
>>
>> You'll see that no binaries are available for javax.j2ee, but only
>> poms. This is due to the licensing of the J2EE 1.4 jars. So you can
>> use these poms but must download and manually install the jars.
>>
>> Eventually we will get JavaEE jars which are available under a license
>> (CDDL or GPL) which allows redistribution. At that time, the files
>> will be hosted and available via Maven.
>>
>> Wayne
>>
>> On 11/13/06, jiangshachina <[EMAIL PROTECTED]> wrote:
>> >
>> > It seems that j2ee.jar(javax.j2ee) is at central repository, but
>> > javaee.jar(JavaEE 5.0).
>> > javaee.jar would be added to the repository in the future, or no
>> forever?
>> >
>> > a cup of Java, cheers!
>> > Sha Jiang
>> >
>> >
>> > jiangshachina wrote:
>> > >
>> > > Hi Brett,
>> > > It means that group springframework is deprecated, too.
>> > > Oh, I may make a serious mistake, if without your help.
>> > > Thanks very much!
>> > >
>> > > a cup of Java, cheers!
>> > > Sha Jiang
>> > >
>> > >
>> > > Brett Porter wrote:
>> > >>
>> > >> On 14/11/06, jiangshachina <[EMAIL PROTECTED]> wrote:
>> > >>> They have same artifactsId, but the artifacts in springframework
>> are
>> > >>> newer.
>> > >>> It means the group spring is deprecated?
>> > >>
>> > >> Some newer versions get moved to a new group ID. We are generally
>> > >> trying to consolidate them over time, and migrate old ones.
>> > >>
>> > >>>
>> > >>> There are many similar cases in central repository, how can I deal
>> with
>> > >>> the
>> > >>> matter?
>> > >>
>> > >> Find the one with the version you are using.
>> > >>
>> > >>> May have a convention for names of the groups?
>> > >>
>> > >> The convention is reverse-domain. So you will probably find all the
>> > >> newest releases in org.springframework group ID (directory
>> > >> org/springframework/).
>> > >>
>> > >> - Brett
>> > >>
>> > >>
>> -
>> > >> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > >> For additional commands, e-mail: [EMAIL PROTECTED]
>> > >>
>> > >>
>> > >>
>> > >
>> > >
>> >
>> > --
>> > View this message in context:
>> >
>> http://www.nabble.com/http%3A--www.ibiblio.org-maven2-vs.-http%3A--repo1.maven.org-maven2--tf2627036s177.html#a7331953
>> > Sent from the Maven - Users mailing list archive at Nabble.com.
>> >
>> >
>> > -
>> > 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]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/http%3A--www.ibiblio.org-maven2-vs.-http%3A--repo1.maven.org-maven2--tf2627036s177.html#a7349962
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Deployment without installation

[Morgovsky, Alexander \(US - Glen Mills\)]

Is it possible to execute a deploy operation without doing an install?
This is when, for example, the application is already installed, and I
just want to call deploy.  Thanks. 


This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, you should delete this message. 


Any disclosure, copying, or distribution of this message, or the taking of any 
action based on it, is strictly prohibited. [v.E.1]

Running Maven 2 reports

[Morgovsky, Alexander \(US - Glen Mills\)]

Is it possible to run Maven 2 reports, like pmd, for example, outside of
the site generation phase?  For example, if I want to create a report
without associating it with any site, can I do this?  If so, how can I
do this?  Thanks. 


This message (including any attachments) contains confidential information 
intended for a specific individual and purpose, and is protected by law.  If 
you are not the intended recipient, you should delete this message. 


Any disclosure, copying, or distribution of this message, or the taking of any 
action based on it, is strictly prohibited. [v.E.1]

Re: change the local repository in maven 1.x

[Arnaud HERITIER]

in your project or user settings you define the property
maven.repo.local=c:/somewherelese

http://maven.apache.org/maven-1.x/reference/properties.html

Arnaud



On 11/14/06, Neeraj Bisht <[EMAIL PROTECTED]> wrote:


hi
we are using GWT ,and we build our GWT project with maven 1.x ,now
google release new jar and this time the jar path should not contain any
spaces in between the path
but we all know that maven build the repository at
$(userhome}/.maven/repositort

and  userhome contain spaces like c:/document and seeting/   (by
default
maven genrate the local repository at this location)

now i need to change the local repository to the place where there is no
space in path

like c:/mavenrepository

in maven 2.x i know we can do it by seeting.xml how we can do in maven
1.xplease any body tell me with example

Regards
Neeraj

Re: Version management question

[Christian Goetze]

Lee Meador wrote:


This does not work.

If you think about it you can see why.

You would define 'sensage-version' in the parent pom and use it in all 
the
children. The problem is that as it is parsing the child pom, maven 
has to
find the parent. To do that, it looks in the  section and has 
to use

the value of "sensage-version'.


Not really, since I pass in  the value of sensage-version via a -D flag. 
Maven just refuses to resolve it within a ... section.




Its a classic catch-22 situation. You can't find the parent without the
value of 'sensage-version' and you you can't find the value of
'sensage-versin' without the parent.


Yeah, I guess so... I'm wondering, though, why maven can't just go look 
in the parent directory for a pom.xml file and not require me to specify 
where the parent is - after all, maven has no qualms about imposing all 
sorts of directory structure conventions, so why not just go that extra 
step, or at least have a tag "use whatever is in the parent directory"


Meanwhile, I guess I just need to live with having to manage all 
versions in all the pom.xml files by hand - sigh -.

--
cg

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

RE: [M1] AspectJ with two source trees (main/src & main/test)

[diyfiesta]

Hi,

Just out of interest: another quick comment about code coverage etc, I was
having a problem with the findbugs and cobertura plugins where it'd fail
with out of memory problems.

It seems this was caused becuase I had the java:compile pre-goal calling the
aspectj:init (as suggested on the aspectj plugin site), running either
findbugs or cobertura would just recursively call the aspectj task and I'd
end up out of memory.

My (slightly hacky) fix was to augment the pre-goal with jelly to ensure it
runs only once. Cobertura and find bugs now work fine.

I used something like this




Running aspectj compilation *once*: 






posted incase its useful or intersting to anyone :)


diyfiesta wrote:
> 
> Thanks Jeff,
> 
> hmmm, I kind of thought that this wouldn't be too far off the beaten track
> but perhaps it is!
> 
> I managed to change most of my aspects to use execution instead of call
> (which in my case makes more sense, I just didn't realise it!), this ind
> of breaks the test dependency so helps.
> 
> Incidentally, I spotted you'd posted to a few threads about aspectj and
> code coverage... would you know if its possible to use Cobertura with
> AspectJ from Maven 1? It doesn't for me and just wondered if in theory it
> should, or perhaps I should think about using M2...
> 
> anyway, thanks again,
> Toby
> 
> 
> Jeff Jensen wrote:
>> 
>> So you have aspects in your test classes, and therefore the tests
>> compilation need AspectJ run on them too.  Changing the maven.test.dest
>> does
>> not solve the problem.
>> 
>> Have you determined a needed plugin change yet?  I am wondering if the
>> "correct fix" is to enhance the plugin to have a property that says to
>> run
>> AspectJ on the tests compilation too?
>> 
>> 
>> -Original Message-
>> From: diyfiesta [mailto:[EMAIL PROTECTED] 
>> Sent: Tuesday, November 14, 2006 3:01 AM
>> To: users@maven.apache.org
>> Subject: RE: [M1] AspectJ with two source trees (main/src & main/test)
>> 
>> 
>> Hi,
>> 
>> Thanks for the note, sorry, its probably not very clear (late night
>> sessions
>> and all that!).
>> 
>> Not sure if its a red hering or not but I have test classes that are
>> *affected* by the aspects. So, I have a call pointcut on some method
>> (called
>> A.doSomething) and and before aspect. The test code calls the method
>> doSomething and so is affected by the aspect.
>> 
>> Running
>> 
>> maven aspectj
>> 
>> creates target/classes which contain the A class, ATest class and the
>> aspect. Reverse engineering the test class here shows it has the
>> correctly
>> weaved (is that the right word) aspect code in it.
>> 
>> running 
>> 
>> maven test (which has a pregoal to run the aspectj compiler)
>> 
>> creates target/test-classes and target.test-reports
>> 
>> The test-classes folder here only contains the test class (ATest.class)
>> and
>> reverse engineering it shows that the aspect was not weaved. So, runing
>> the
>> test will fail becuase the test is testing that the aspect is being used.
>> 
>> Changing the default maven.test.dest to something like
>> ${maven.build.dir}/classes seems to help but in my real project doesn't
>> solve it completly.
>> 
>> I have a test project that demonstrates this (if anyone is interested),
>> all
>> the settings are pretty much default.
>> 
>> I'll keep playing and post my findings here.
>> 
>> Cheers,
>> 
>> 
>> 
>> Jeff Jensen wrote:
>>> 
>>> Are you saying that the test classes in test-classes need a pass by 
>>> the AspectJ compiler, or the test classes do not see the AspectJ 
>>> compiled classes in the classes dir?  (or something else entirely?)
>>> 
>>> The fact that the "production" classes compile to target/classes and 
>>> the test classes compile to /target/test-classes seems correct to me 
>>> (from what I understand from your emails).  When the tests run, the 
>>> production code is also on the classpath, so works well (now there 
>>> could be some bug in that...
>>> :-).
>>> 
>>> 
>>> -Original Message-
>>> From: diyfiesta [mailto:[EMAIL PROTECTED]
>>> Sent: Monday, November 13, 2006 9:53 AM
>>> To: users@maven.apache.org
>>> Subject: Re: [M1] AspectJ with two source trees (main/src & main/test)
>>> 
>>> 
>>> So, looking into this more (and having created a simple example 
>>> project to demonstrate it), it looks like the the aspectj plugin is 
>>> compiling things correctly, its just that the tests are being run from
>>> the
>> incorrect place.
>>> 
>>> So, for example, the output of the aspectj compilation goes into
>>> 
>>> target/classes/...
>>> 
>>> but the tests run from a folder called
>>> 
>>> target/test-classes/... 
>>> 
>>> which has the compiled test code, but not the aspectj compiled code. 
>>> So, if a test is affected by an aspect, it isn't in this folder.
>>> 
>>> 
>>> diyfiesta wrote:
 
 Hi,
 
 Thanks for the note, I tried this but still don

Re: site-deploy not copying Java Docs

[Dennis Lundberg]

Dmystery wrote:
I've a multi-module project for which i'm generating a site. 


I'm doing a mvn site:stage -DstagingDirectory=somedirectory. This works fine
and the modules are linked properly too. However, the Java doc generated are
not copied to the staging directory. Only the index.html is copied, the rest
remains in the project build directory. 

My parent pom looks like, 
.

.

  
  my-site 
  my-site 
  file:// 
  




   
 
   maven-javadoc-plugin
 
 
   org.codehaus.mojo
   jxr-maven-plugin
   
   


.
.

Interestingly, instead of the above command, if i use 'mvn site-deploy' with

  
  my-site 
  my-site 
  file://c:/somedirectory 
 


in my pom, the apidocs are copied but the module and apidocs links do not
exists. 

Is there a clean way of deploying a site on to the local machine?? 


You might want to replace the old org.codehaus.mojo:jxr-maven-plugin 
with the newer org.apache.maven.plugins:maven-jxr-plugin.


--
Dennis Lundberg

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

Re: successful AJDT integration?

[diyfiesta]

Hi,

I'm using M1 so can't comment direclty on M2 stuff, but thought I'd
chip in with some thoughts on source file placement.

I've tried a few different approaches and have settled on putting the
aspects in with the java source as I view them as java-like if not
strict java (after all AJDT lets you name your files .java instead of
.aj). So, mine live in plain old main/src/java and it works well in
Eclipse and from Maven.

In M1 I did have some problems with having aspects across source trees
(or indead affecting source in multiple trees, for example
main/test/java)...

Cheers,
T


gdub-2 wrote:
> 
> Good morning-
> 
> I'm trying to figure out the best way to
> use AspectJ with both Eclipse and Maven 2.
> 
> Problem 1:
> I have the Codehaus plugin installed and
> working. But the eclipse:eclipse target
> does not configure the project as AspectJ.
> Does anyone know if this feature is being
> considered? If it is not in the works
> already, in which plugin (aspectj or
> eclipse or both) should the support lie?
> 
> Problem 2:
> Say the rt dependency in Maven is set
> to Eclipse 1.5.2a. Run eclipse:eclipse
> target and the dependency is is set
> correctly in the IDE. However, changing
> the project to an AJ project from within
> the IDE (required because of P1 above),
> adds a conflicting dependency on a jar from
> AJDT itself (1.5.2.something).
> 
> Problem 3:
> There is, AFAICT, no Maven source location
> convention for source files that require an
> AspectJ compiler. I am not sure that
> src/{main,test}/java is the correct
> place since it is not strictly Java code.
> I imagine that there are good reasons
> against establishing a convention such as
> using src/{main,test}/aspectj and I'd like
> to hear them. Pragmatically wrt to
> the topic at hand, the use of the
> AspectJ compiler is all-or-nothing at the
> project level in Eclipse so a separate
> code location is meaningless there. But, I
> don't think basic build convention
> decisions should be made on the basis
> of supporting any particular development
> tool.
> 
> I know this is a big conceptual
> problem. The value of AspectJ in many
> cases is to enable unanticipated extension
> of Java software. So, a large portion
> of the code that is compiled/woven by ajc is
> not aware (nor should it be) that it is
> being advised--meaning the advised code
> developer would rightly place sources in
> .../java. Aspects might be best packaged
> separately for such situations. But, a
> growing body of software is being designed
> with aspects for application logic. That
> means, for instance, pointcuts in class
> definitions and aspect source files mixed
> in with standard java sources. Such code
> might belong in a directory such as
> .../aspectj to signal, by convention, that
> the code requires an AspectJ compiler.
> There are many such issues with this
> particular language because it doesn't fit
> traditional language models and probably
> breaks subtle assumptions in the models
> of many development tools such as Maven
> and Eclipse.
> 
> Any thoughts? Am I missing some
> fundamental piece of understanding that
> makes AJDT and Maven integration a
> snap?
> 
> TIA,
> 
>-dub
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/successful-AJDT-integration--tf2631647s177.html#a7347170
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Maven does not get latest snapshot for building

[Jan Thomä]

Hi,

we are using a library called ICC for our projects. The library is built from 
SVN on our server once per night and stored as icc-1.0-SNAPSHOT on the 
server. We have added the server to our remote repositories via settings.xml. 

Also, since ICC is still in heavy development, every developer has a local 
copy of ICC as well on his machine.

When a developer changes ICC if he needs the change for some other project 
depending on ICC, he finally calls mvn install, to install his local changes 
to ICC into his local repository (which creates an icc-1.0-SNAPSHOT.jar in 
the local repo).

When building the other project, maven fetches the latest copy of ICC from our 
server and puts it into the local repository. Now here is where the problem 
starts. Maven always uses the copy from the server, not the locally installed 
one (using mvn install in ICC), even if the locally created version is 
newer . Is there something we are doing wrong?

Best regards,
-- 

Jan Thomä
insOMnia - We never sleep...   http://www.insomnia-hq.de


pgpn8p1mNOpyb.pgp
Description: PGP signature

Re: EhCacheProvider not found with other hibernate classes during test

[Lee Meador]

This has been discussed before. You can find it in nabble, I think.

The issue has to do with spring wanting one version of hibernate and
hibernate wanting a version of ehcache and the versions conflict with each
other. In my case, using Quartz which wanted another version of ehcache, it
would pick one version of ehcache for one project and another version for
another project.

You solve it by specifying versions for things in some places and excluding
dependencies in others. I forget the details.

-- Lee

On 11/14/06, Trevor Torrez <[EMAIL PROTECTED]> wrote:


Hi; I am trying to convert our framework over to maven, and am running
into
a bit of a snag.  When trying run the tests, I get a class not found for
org.hibernate.cache.EhCacheProvider; but when running from eclipse (using
the eclipse maven plugin to setup the libraries) everything works fine.

I have tried letting the project just pull the relevent spring 2.0 jars
for
hibernate and explicitly pulling the hibernate jar files.  The class
exists
in the hibernate-3 jar, the same jar file that contains the
HibernateException as the root throwable.

[stack trace follows]

org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'mockManager' defined in class path
resource [application-context-service-test.xml]:
Cannot create inner bean '
org.govgrnds.mock.service.impl.MockManagerImpl#64c34e' while setting bean
property 'target';
Caused by: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name '
org.govgrnds.mock.service.impl.MockManagerImpl#64c34e' defined in class
path
resource [application-context-service-test.xml]:
Cannot resolve reference to bean 'baseHibernateDAO' while setting
bean property 'dao';
Caused by: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'baseHibernateDAO' defined in class path
resource [application-context-service-test.xml]:
Cannot resolve reference to bean 'hibernateTemplate' while setting
bean property 'hibernateTemplate';
Caused by: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'hibernateTemplate' defined in class
path
resource [application-context-service-test.xml]:
Cannot resolve reference to bean 'sessionFactory' while setting
bean
property 'sessionFactory';
Caused by: org.springframework.beans.factory.BeanCreationException:
Error creating bean with name 'sessionFactory' defined in class path
resource [application-context-service-test.xml]:
Invocation of init method failed;
Caused by: org.hibernate.HibernateException:
could not instantiate CacheProvider:
org.hibernate.cache.EhCacheProvider
at org.hibernate.cfg.SettingsFactory.createCacheProvider(
SettingsFactory.java:361)
at org.hibernate.cfg.SettingsFactory.buildSettings(
SettingsFactory.java
:232)
at org.hibernate.cfg.Configuration.buildSettings(Configuration.java
:1933)
at org.hibernate.cfg.Configuration.buildSessionFactory(
Configuration.java:1216)
at

org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory
(LocalSessionFactoryBean.java:807)
at

org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory
(LocalSessionFactoryBean.java:740)
at

org.springframework.orm.hibernate3.AbstractSessionFactoryBean.afterPropertiesSet
(AbstractSessionFactoryBean.java:131)
at

org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods
(AbstractAutowireCapableBeanFactory.java:1062)
at

org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean
(AbstractAutowireCapableBeanFactory.java:1029)
at

org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean
(AbstractAutowireCapableBeanFactory.java:420)
at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(
AbstractBeanFactory.java:245)
at

org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton
(DefaultSingletonBeanRegistry.java:141)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:242)
at
org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:156)
at

org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference
(BeanDefinitionValueResolver.java:246)
at

org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary
(BeanDefinitionValueResolver.java:128)
at

org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues
(AbstractAutowireCapableBeanFactory.java:955)
at

org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean
(AbstractAutowireCapableBeanFactory.java:729)
at

org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean
(Abst

Re: Version management question

[Lee Meador]

This does not work.

If you think about it you can see why.

You would define 'sensage-version' in the parent pom and use it in all the
children. The problem is that as it is parsing the child pom, maven has to
find the parent. To do that, it looks in the  section and has to use
the value of "sensage-version'.

Its a classic catch-22 situation. You can't find the parent without the
value of 'sensage-version' and you you can't find the value of
'sensage-versin' without the parent.

-- Lee

On 11/14/06, Christian Goetze <[EMAIL PROTECTED]> wrote:


I recently asked the question below, but no answer.

I was wondering whether I really need to edit all pom.xml files in all
my project whenever I bump version numbers.

I'm still new at this, so if this is a trivial question, please bear
with me...
--
cg

Christian Goetze wrote:

> Why can't I do this:
>
> 
>  4.0.0
>
>  
>  
>   com.sensage
>   sensage
>   ${sensage-version}
>  
>
> I do run "mvn -Dsensage-version=3.6"...
>
> It works fine when I run from the top of the project down.
> --
> cg
>
> -
> 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]





--
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com

Re: Maven dependency question

[Lee Meador]

What I do is put the utility jar in my dependency for the war as compile.
Then I put an exclude in the pom for the war that tells it to leave out the
jar and not put it into the war. The classloader for your application server
should cause the war to have access to the jar since it is in the ejb jar's
classpath. This has to do with the nesting of the classloaders. Some app
servers let you change the way that works though.

-- Lee

On 11/14/06, Enrique Gaona <[EMAIL PROTECTED]> wrote:




Hi folks,

We have a J2EE application project (ear) which contains one Web project
(war), one EJB project and one utilities java project.
The war and EJB jar projects depends from the same utilities project.
We included the WEB, EJB and utilities projects as dependencies into the
ear pom file, so all three output files are included into ear file.
EJB project works as expected it only adds Class-Path: entry into its
Manifest.MF class

The problem with the Web project, it adds the common utility jar file into
its WEB-INF/lib directory. We tried to change the dependency scope from
"compile" to "provided". In this case neither the jar was  added nor the
Class-Path: entry.

How can we specify dependency from the common utility jar file in the
war's
pom file?

Any help is appreciated.  Thanks

Enrique





--
-- Lee Meador
Sent from gmail. My real email address is lee AT leemeador.com

EhCacheProvider not found with other hibernate classes during test

[Trevor Torrez]

Hi; I am trying to convert our framework over to maven, and am running into
a bit of a snag.  When trying run the tests, I get a class not found for
org.hibernate.cache.EhCacheProvider; but when running from eclipse (using
the eclipse maven plugin to setup the libraries) everything works fine.

I have tried letting the project just pull the relevent spring 2.0 jars for
hibernate and explicitly pulling the hibernate jar files.  The class exists
in the hibernate-3 jar, the same jar file that contains the
HibernateException as the root throwable.

[stack trace follows]

org.springframework.beans.factory.BeanCreationException:
   Error creating bean with name 'mockManager' defined in class path
resource [application-context-service-test.xml]:
   Cannot create inner bean '
org.govgrnds.mock.service.impl.MockManagerImpl#64c34e' while setting bean
property 'target';
Caused by: org.springframework.beans.factory.BeanCreationException:
   Error creating bean with name '
org.govgrnds.mock.service.impl.MockManagerImpl#64c34e' defined in class path
resource [application-context-service-test.xml]:
   Cannot resolve reference to bean 'baseHibernateDAO' while setting
bean property 'dao';
Caused by: org.springframework.beans.factory.BeanCreationException:
   Error creating bean with name 'baseHibernateDAO' defined in class path
resource [application-context-service-test.xml]:
   Cannot resolve reference to bean 'hibernateTemplate' while setting
bean property 'hibernateTemplate';
Caused by: org.springframework.beans.factory.BeanCreationException:
   Error creating bean with name 'hibernateTemplate' defined in class path
resource [application-context-service-test.xml]:
   Cannot resolve reference to bean 'sessionFactory' while setting bean
property 'sessionFactory';
Caused by: org.springframework.beans.factory.BeanCreationException:
   Error creating bean with name 'sessionFactory' defined in class path
resource [application-context-service-test.xml]:
   Invocation of init method failed;
Caused by: org.hibernate.HibernateException:
   could not instantiate CacheProvider: org.hibernate.cache.EhCacheProvider
   at org.hibernate.cfg.SettingsFactory.createCacheProvider(
SettingsFactory.java:361)
   at org.hibernate.cfg.SettingsFactory.buildSettings(SettingsFactory.java
:232)
   at org.hibernate.cfg.Configuration.buildSettings(Configuration.java
:1933)
   at org.hibernate.cfg.Configuration.buildSessionFactory(
Configuration.java:1216)
   at
org.springframework.orm.hibernate3.LocalSessionFactoryBean.newSessionFactory
(LocalSessionFactoryBean.java:807)
   at
org.springframework.orm.hibernate3.LocalSessionFactoryBean.buildSessionFactory
(LocalSessionFactoryBean.java:740)
   at
org.springframework.orm.hibernate3.AbstractSessionFactoryBean.afterPropertiesSet
(AbstractSessionFactoryBean.java:131)
   at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.invokeInitMethods
(AbstractAutowireCapableBeanFactory.java:1062)
   at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.initializeBean
(AbstractAutowireCapableBeanFactory.java:1029)
   at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean
(AbstractAutowireCapableBeanFactory.java:420)
   at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(
AbstractBeanFactory.java:245)
   at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton
(DefaultSingletonBeanRegistry.java:141)
   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:242)
   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:156)
   at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference
(BeanDefinitionValueResolver.java:246)
   at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary
(BeanDefinitionValueResolver.java:128)
   at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues
(AbstractAutowireCapableBeanFactory.java:955)
   at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean
(AbstractAutowireCapableBeanFactory.java:729)
   at
org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean
(AbstractAutowireCapableBeanFactory.java:416)
   at
org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(
AbstractBeanFactory.java:245)
   at
org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton
(DefaultSingletonBeanRegistry.java:141)
   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:242)
   at org.springframework.beans.factory.support.AbstractBeanFactory.getBean
(AbstractBeanFactory.java:156)
   at
org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference
(BeanDefinitionValueRe

Maven dependency question

[Enrique Gaona]

Hi folks,

We have a J2EE application project (ear) which contains one Web project
(war), one EJB project and one utilities java project.
The war and EJB jar projects depends from the same utilities project.
We included the WEB, EJB and utilities projects as dependencies into the
ear pom file, so all three output files are included into ear file.
EJB project works as expected it only adds Class-Path: entry into its
Manifest.MF class

The problem with the Web project, it adds the common utility jar file into
its WEB-INF/lib directory. We tried to change the dependency scope from
"compile" to "provided". In this case neither the jar was  added nor the
Class-Path: entry.

How can we specify dependency from the common utility jar file in the war's
pom file?

Any help is appreciated.  Thanks

Enrique

Version management question

[Christian Goetze]

I recently asked the question below, but no answer.

I was wondering whether I really need to edit all pom.xml files in all 
my project whenever I bump version numbers.


I'm still new at this, so if this is a trivial question, please bear 
with me...

--
cg

Christian Goetze wrote:


Why can't I do this:


 4.0.0

 
 
  com.sensage
  sensage
  ${sensage-version}
 

I do run "mvn -Dsensage-version=3.6"...

It works fine when I run from the top of the project down.
--
cg

-
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]

successful AJDT integration?

[gdub]

Good morning-

I'm trying to figure out the best way to
use AspectJ with both Eclipse and Maven 2.

Problem 1:
I have the Codehaus plugin installed and
working. But the eclipse:eclipse target
does not configure the project as AspectJ.
Does anyone know if this feature is being
considered? If it is not in the works
already, in which plugin (aspectj or
eclipse or both) should the support lie?

Problem 2:
Say the rt dependency in Maven is set
to Eclipse 1.5.2a. Run eclipse:eclipse
target and the dependency is is set
correctly in the IDE. However, changing
the project to an AJ project from within
the IDE (required because of P1 above),
adds a conflicting dependency on a jar from
AJDT itself (1.5.2.something).

Problem 3:
There is, AFAICT, no Maven source location
convention for source files that require an
AspectJ compiler. I am not sure that
src/{main,test}/java is the correct
place since it is not strictly Java code.
I imagine that there are good reasons
against establishing a convention such as
using src/{main,test}/aspectj and I'd like
to hear them. Pragmatically wrt to
the topic at hand, the use of the
AspectJ compiler is all-or-nothing at the
project level in Eclipse so a separate
code location is meaningless there. But, I
don't think basic build convention
decisions should be made on the basis
of supporting any particular development
tool.

I know this is a big conceptual
problem. The value of AspectJ in many
cases is to enable unanticipated extension
of Java software. So, a large portion
of the code that is compiled/woven by ajc is
not aware (nor should it be) that it is
being advised--meaning the advised code
developer would rightly place sources in
.../java. Aspects might be best packaged
separately for such situations. But, a
growing body of software is being designed
with aspects for application logic. That
means, for instance, pointcuts in class
definitions and aspect source files mixed
in with standard java sources. Such code
might belong in a directory such as
.../aspectj to signal, by convention, that
the code requires an AspectJ compiler.
There are many such issues with this
particular language because it doesn't fit
traditional language models and probably
breaks subtle assumptions in the models
of many development tools such as Maven
and Eclipse.

Any thoughts? Am I missing some
fundamental piece of understanding that
makes AJDT and Maven integration a
snap?

TIA,

  -dub

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

Error With dependency plugin

[Lyndon Washington]

Greetings,

I am attempting to use maven on a project and it appears to be having
problems retrieving a plugin before it even tries to handle the project's
pom.xml.


From the console output below, the problem seems to be with a version of

maven-dependency-plugin that is not available.  The strange thing is that
the version for the plugin is a SNAPSHOT release.

[INFO] Scanning for projects...
[INFO]

[INFO] Building Error Handler Example
[INFO]task-segment: [clean]
[INFO]

[INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for
updates from central
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.1/maven-clean-plugin-2.1.pom
703b downloaded
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.1/maven-clean-plugin-2.1.jar
5K downloaded
Downloading:
http://people.apache.org/maven-snapshot-repository/org/apache/maven/plugins/maven-dependency-plugin/2.0-SNAPSHOT/maven-dependency-plugin-2.0-20060907.213033-3.pom
[WARNING] Unable to get resource from repository apache-plugin-snapshots (
http://people.apache.org/maven-snapshot-repository)
Downloading:
http://snapshots.repository.codehaus.org/org/apache/maven/plugins/maven-dependency-plugin/2.0-SNAPSHOT/maven-dependency-plugin-2.0-20060907.213033-3.pom
[WARNING] Unable to get resource from repository codehaus-snapshots (
http://snapshots.repository.codehaus.org)
[INFO]

[ERROR] BUILD ERROR
[INFO]

[INFO] Failed to resolve artifact.

GroupId: org.apache.maven.plugins
ArtifactId: maven-dependency-plugin
Version: 2.0-20060907.213033-3

Reason: Unable to download the artifact from any repository

 org.apache.maven.plugins:maven-dependency-plugin:pom:2.0-20060907.213033-3

from the specified remote repositories:
 central (http://repo1.maven.org/maven2),
 codehaus (http://repository.codehaus.org),
 codehaus-snapshots (http://snapshots.repository.codehaus.org),
 apache-plugin-snapshots (
http://people.apache.org/maven-snapshot-repository)


Cheers,
-Lyndon-

Re: http://www.ibiblio.org/maven2 vs. http://repo1.maven.org/maven2?

[Wayne Fay]

You can use the Geronimo-provided J2EE jars for now, while waiting for
the Sun JavaEE jars to be published under an open source license etc:

http://www.ibiblio.org/pub/packages/maven2/geronimo-spec/
http://www.ibiblio.org/pub/packages/maven2/geronimo/

The Glassfish jars are slowly making their way into Maven repos too so
you could use those instead of Geronimo if you prefer, assuming the
jars are available from both sources.

Wayne

On 11/14/06, Wayne Fay <[EMAIL PROTECTED]> wrote:

If you look in more detail:
http://www.ibiblio.org/pub/packages/maven2/javax/j2ee/j2ee/1.4/

You'll see that no binaries are available for javax.j2ee, but only
poms. This is due to the licensing of the J2EE 1.4 jars. So you can
use these poms but must download and manually install the jars.

Eventually we will get JavaEE jars which are available under a license
(CDDL or GPL) which allows redistribution. At that time, the files
will be hosted and available via Maven.

Wayne

On 11/13/06, jiangshachina <[EMAIL PROTECTED]> wrote:
>
> It seems that j2ee.jar(javax.j2ee) is at central repository, but
> javaee.jar(JavaEE 5.0).
> javaee.jar would be added to the repository in the future, or no forever?
>
> a cup of Java, cheers!
> Sha Jiang
>
>
> jiangshachina wrote:
> >
> > Hi Brett,
> > It means that group springframework is deprecated, too.
> > Oh, I may make a serious mistake, if without your help.
> > Thanks very much!
> >
> > a cup of Java, cheers!
> > Sha Jiang
> >
> >
> > Brett Porter wrote:
> >>
> >> On 14/11/06, jiangshachina <[EMAIL PROTECTED]> wrote:
> >>> They have same artifactsId, but the artifacts in springframework are
> >>> newer.
> >>> It means the group spring is deprecated?
> >>
> >> Some newer versions get moved to a new group ID. We are generally
> >> trying to consolidate them over time, and migrate old ones.
> >>
> >>>
> >>> There are many similar cases in central repository, how can I deal
with
> >>> the
> >>> matter?
> >>
> >> Find the one with the version you are using.
> >>
> >>> May have a convention for names of the groups?
> >>
> >> The convention is reverse-domain. So you will probably find all the
> >> newest releases in org.springframework group ID (directory
> >> org/springframework/).
> >>
> >> - Brett
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >>
> >
> >
>
> --
> View this message in context:
>
http://www.nabble.com/http%3A--www.ibiblio.org-maven2-vs.-http%3A--repo1.maven.org-maven2--tf2627036s177.html#a7331953
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> -
> 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: Surefire and TestNG

[Wayne Fay]

Bugs should be posted in JIRA, not the Users list.

Wayne

On 11/14/06, Christopher Maki <[EMAIL PROTECTED]> wrote:

Hi

I seem to be having a problem with TestNG 5.1 and the Surefire plugin
(either 2.3-SNAPSHOT or 2.2).  When using Surefire 2.3-SNAPSHOT I get this
error when I try to run my tests:

---
 T E S T S
---
org.apache.maven.surefire.booter.SurefireExecutionException:
Cannot find class in classpath: org.maki.model.BankAccountFactory; nested
exception is org.testng.TestNGException:
Cannot find class in classpath: org.maki.model.BankAccountFactory
org.testng.TestNGException:
Cannot find class in classpath: org.maki.model.BankAccountFactory
at org.testng.xml.XmlClass.getSupportClass(XmlClass.java:45)
at org.testng.internal.Utils.xmlClassesToClasses(Utils.java:82)
at org.testng.TestRunner.initMethods(TestRunner.java:273)
at org.testng.TestRunner.init(TestRunner.java:212)
at org.testng.TestRunner.init(TestRunner.java:184)
at org.testng.TestRunner.(TestRunner.java:121)
at
org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:376)


The problem stems from using a testng.xml file.  If I just run the tests
without testng.xml all methods for all tests are executed, but if I try to
customize the execution via testng.xml I get the above error.  I've attached
a very small project to illustrate the problem I'm having.

Any feedback is much appreciated.

Thanks

Chris






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

Surefire and TestNG

[Christopher Maki]

Hi

I seem to be having a problem with TestNG 5.1 and the Surefire plugin (either 
2.3-SNAPSHOT or 2.2).  When using Surefire 2.3-SNAPSHOT I get this error when I 
try to run my tests:

---
 T E S T S
---
org.apache.maven.surefire.booter.SurefireExecutionException: 
Cannot find class in classpath: org.maki.model.BankAccountFactory; nested 
exception is org.testng.TestNGException: 
Cannot find class in classpath: org.maki.model.BankAccountFactory
org.testng.TestNGException: 
Cannot find class in classpath: org.maki.model.BankAccountFactory
at org.testng.xml.XmlClass.getSupportClass(XmlClass.java:45)
at org.testng.internal.Utils.xmlClassesToClasses(Utils.java:82)
at org.testng.TestRunner.initMethods(TestRunner.java:273)
at org.testng.TestRunner.init(TestRunner.java:212)
at org.testng.TestRunner.init(TestRunner.java:184)
at org.testng.TestRunner.(TestRunner.java:121)
at 
org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:376)


The problem stems from using a testng.xml file.  If I just run the tests 
without testng.xml all methods for all tests are executed, but if I try to 
customize the execution via testng.xml I get the above error.  I've attached a 
very small project to illustrate the problem I'm having. 

Any feedback is much appreciated. 

Thanks

Chris


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

Re: Setting up a new jre to maven

[Allan Valeriano]

Thanks a lot for the help. =)
It was exactly my problem.
java was pointing to 1.4 and javac was pointing to 5.


Allan Valeriano

On 11/14/06, Wayne Fay <[EMAIL PROTECTED]> wrote:


Unsupported major.minor version indicates you're trying to run a
newer-compiled Java class in an older JRE. In this case, seems like
you've compiled classes with JRE 5 and are attempting to execute them
(testing w/Surefire?) with JRE 3 or 4.

Check your PATH... I'd guess you've got a JRE 3 or 4 in your PATH
somewhere and its being used instead of JRE 5.

Wayne

On 11/14/06, Allan Valeriano <[EMAIL PROTECTED]> wrote:
> I found out that my project' parent have on its pom.xml the
configuration to
> compile with jre5 already.
> So I was thinking the problem I'm having is not being caused by the jre
and
> so by another mystical thing.
> Here goes the error:
>
> [INFO]
> >
>

> > [INFO] Building scap-integration-core
> > [INFO]task-segment: [install]
> > [INFO]
> >
>

> > [INFO] [resources:resources]
> > [INFO] Using default encoding to copy filtered resources.
> > [INFO] [compiler:compile]
> > [INFO] Nothing to compile - all classes are up to date
> > [INFO] [resources:testResources]
> > [INFO] Using default encoding to copy filtered resources.
> > [INFO] [compiler:testCompile]
> > [INFO] Nothing to compile - all classes are up to date
> > [INFO] [surefire:test]
> > [INFO] Surefire report directory:
> >
>
/home/valeriano/.eclipse/scap-integration-branch/scap-integration-core/target/surefire-reports
> > org.apache.maven.surefire.booter.SurefireExecutionException:
> > com/longadata/scapintegration/core/EnotariusSubjectHandlerTest
> (Unsupported
> > major.minor version 49.0); nested exception is
> > java.lang.UnsupportedClassVersionError:
> > com/longadata/scapintegration/core/EnotariusSubjectHandlerTest
> (Unsupported
> > major.minor version 49.0)
> > java.lang.UnsupportedClassVersionError:
> > com/longadata/scapintegration/core/EnotariusSubjectHandlerTest
> (Unsupported
> > major.minor version 49.0)
> > at java.lang.ClassLoader.defineClass0(Native Method)
> > at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
> > at java.security.SecureClassLoader.defineClass(
> > SecureClassLoader.java:123)
> > at java.net.URLClassLoader.defineClass(URLClassLoader.java
:251)
> > at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
> > at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
> > at java.security.AccessController.doPrivileged(Native Method)
> > at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
> > at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
> > at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
> > at
org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(
> > IsolatedClassLoader.java:100)
> > at
> >
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(
> > AbstractDirectoryTestSuite.java:84)
> > at
org.apache.maven.surefire.Surefire.createSuiteFromDefinition(
> > Surefire.java:147)
> > at org.apache.maven.surefire.Surefire.run(Surefire.java:108)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke(
> > NativeMethodAccessorImpl.java:39)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:324)
> > at
> > org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(
> > SurefireBooter.java:225)
> > at org.apache.maven.surefire.booter.SurefireBooter.main(
> > SurefireBooter.java:747)
> >
> >
> Anybody has any idea about what might be causing this error?
>
> Thanks in advance
> Allan Valeriano
>
> On 11/13/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
> >
> > Then I have no idea why its not working for Aaron... ;-)
> >
> > Wayne
> >
> > On 11/13/06, Arnaud Bailly <[EMAIL PROTECTED]> wrote:
> > > "Wayne Fay" <[EMAIL PROTECTED]> writes:
> > >
> > > > You can put it in the parent "pom" project with complete
configuration
> > > > etc, but then you also need to include a reference to the
> > > > compiler-plugin in the build section in each of your modules.
> > > >
> > > Hello,
> > >
> > > I tried without adding the reference to compiler plugin in 
> > > section of child project and it works ok.
> > >
> > > Regards,
> > > --
> > > OQube < software engineering \ génie logiciel >
> > > Arnaud Bailly, Dr.
> > > \web> http://www.oqube.com
> > >
> > >
> > >
-
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > --

RE: [M1] AspectJ with two source trees (main/src & main/test)

[diyfiesta]

Thanks Jeff,

hmmm, I kind of thought that this wouldn't be too far off the beaten track
but perhaps it is!

I managed to change most of my aspects to use execution instead of call
(which in my case makes more sense, I just didn't realise it!), this ind of
breaks the test dependency so helps.

Incidentally, I spotted you'd posted to a few threads about aspectj and code
coverage... would you know if its possible to use Cobertura with AspectJ
from Maven 1? It doesn't for me and just wondered if in theory it should, or
perhaps I should think about using M2...

anyway, thanks again,
Toby


Jeff Jensen wrote:
> 
> So you have aspects in your test classes, and therefore the tests
> compilation need AspectJ run on them too.  Changing the maven.test.dest
> does
> not solve the problem.
> 
> Have you determined a needed plugin change yet?  I am wondering if the
> "correct fix" is to enhance the plugin to have a property that says to run
> AspectJ on the tests compilation too?
> 
> 
> -Original Message-
> From: diyfiesta [mailto:[EMAIL PROTECTED] 
> Sent: Tuesday, November 14, 2006 3:01 AM
> To: users@maven.apache.org
> Subject: RE: [M1] AspectJ with two source trees (main/src & main/test)
> 
> 
> Hi,
> 
> Thanks for the note, sorry, its probably not very clear (late night
> sessions
> and all that!).
> 
> Not sure if its a red hering or not but I have test classes that are
> *affected* by the aspects. So, I have a call pointcut on some method
> (called
> A.doSomething) and and before aspect. The test code calls the method
> doSomething and so is affected by the aspect.
> 
> Running
> 
> maven aspectj
> 
> creates target/classes which contain the A class, ATest class and the
> aspect. Reverse engineering the test class here shows it has the correctly
> weaved (is that the right word) aspect code in it.
> 
> running 
> 
> maven test (which has a pregoal to run the aspectj compiler)
> 
> creates target/test-classes and target.test-reports
> 
> The test-classes folder here only contains the test class (ATest.class)
> and
> reverse engineering it shows that the aspect was not weaved. So, runing
> the
> test will fail becuase the test is testing that the aspect is being used.
> 
> Changing the default maven.test.dest to something like
> ${maven.build.dir}/classes seems to help but in my real project doesn't
> solve it completly.
> 
> I have a test project that demonstrates this (if anyone is interested),
> all
> the settings are pretty much default.
> 
> I'll keep playing and post my findings here.
> 
> Cheers,
> 
> 
> 
> Jeff Jensen wrote:
>> 
>> Are you saying that the test classes in test-classes need a pass by 
>> the AspectJ compiler, or the test classes do not see the AspectJ 
>> compiled classes in the classes dir?  (or something else entirely?)
>> 
>> The fact that the "production" classes compile to target/classes and 
>> the test classes compile to /target/test-classes seems correct to me 
>> (from what I understand from your emails).  When the tests run, the 
>> production code is also on the classpath, so works well (now there 
>> could be some bug in that...
>> :-).
>> 
>> 
>> -Original Message-
>> From: diyfiesta [mailto:[EMAIL PROTECTED]
>> Sent: Monday, November 13, 2006 9:53 AM
>> To: users@maven.apache.org
>> Subject: Re: [M1] AspectJ with two source trees (main/src & main/test)
>> 
>> 
>> So, looking into this more (and having created a simple example 
>> project to demonstrate it), it looks like the the aspectj plugin is 
>> compiling things correctly, its just that the tests are being run from
>> the
> incorrect place.
>> 
>> So, for example, the output of the aspectj compilation goes into
>> 
>> target/classes/...
>> 
>> but the tests run from a folder called
>> 
>> target/test-classes/... 
>> 
>> which has the compiled test code, but not the aspectj compiled code. 
>> So, if a test is affected by an aspect, it isn't in this folder.
>> 
>> 
>> diyfiesta wrote:
>>> 
>>> Hi,
>>> 
>>> Thanks for the note, I tried this but still don't have any luck, for 
>>> example, I'm using the convention main/src/java and main/src/test for 
>>> my source trees, so adding an src/aspectj folder doesn't really fit 
>>> in, if I add it to main/src/aspectj, I get the same problem (and just 
>>> for completness, setting it to src/aspectj causes is the same!).
>>> 
>>> From the plugin's homepage, I didn't get the impression that setting 
>>> the soruce directiory to src/aspectj was a requirement more of an 
>>> example, and you should be able to set this to whatever your folder 
>>> is. Is this not the case?
>>> 
>>> I think I'll have a go at creating a simple test project that 
>>> demonstrates the problem, see if I can get some feedback.
>>> 
>>> Any other ideas?
>>> 
>>> Cheers
>>> 
>>> 
>>> Alexandre Touret wrote:
 
 Hello,
 There are 2 builds : the classes and test classes.
 If you specify the aspectsourcedirectory in src/java, aspectj doesn 
 t parse any file in src/test. Its the 

Re: mvn2: Failed to validate POM error

[Attila Mezei-Horvati]

Deng,

I deleted the whole folder with everything in it. I
still don't know why is doing it, the war however
includes the jar file. 

For now I decided to keep going with my project. It is
annoying to see the warning coming up at every phase
while building the package but I will have to live
with it for a while so I can meet the deadline.

If you have any ideas please let me know. I would like
to understand what is wrong with it.

thanks,
Attila



 

Cheap talk?
Check out Yahoo! Messenger's low PC-to-Phone call rates.
http://voice.yahoo.com

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

Re: Plugin Test Harness and expression

[Emmanuel Hugonnet]

zze-Amicom HUGONNET E ext RD-TECH a écrit :

Hi,
I have a quite simple plugin working correctly but when I try to test 
it the expression is not evaluated. I am using :


 org.apache.maven.shared
 maven-plugin-testing-harness
 1.0-beta-1

On the doc on codehaus they talk about 
"StubResolverExpressionEvaluator" which seems to help resolve this 
issue but I don't see any example. When I look at the unit test for 
expression evaluation on svn I don't see anything specific to be done.

What am I missing ?
Thanks,
Emmanuel

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


While debugging my simple test I have watched that my expression while 
seen as an expression to be evaluated is not in fact evaluated in the 
"ResolverExpressionEvaluatorStub". Why can't we use Maven's own 
expression resolver ? I would like to try this but I have yet to find 
where the expression are resolved in Maven. I am looking for any insight.

Emmanuel

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

Re: Setting up a new jre to maven

[Allan Valeriano]

I found out that my project' parent have on its pom.xml the configuration to
compile with jre5 already.
So I was thinking the problem I'm having is not being caused by the jre and
so by another mystical thing.
Here goes the error:

[INFO]


[INFO] Building scap-integration-core
[INFO]task-segment: [install]
[INFO]

[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [surefire:test]
[INFO] Surefire report directory:
/home/valeriano/.eclipse/scap-integration-branch/scap-integration-core/target/surefire-reports
org.apache.maven.surefire.booter.SurefireExecutionException:
com/longadata/scapintegration/core/EnotariusSubjectHandlerTest (Unsupported
major.minor version 49.0); nested exception is
java.lang.UnsupportedClassVersionError:
com/longadata/scapintegration/core/EnotariusSubjectHandlerTest (Unsupported
major.minor version 49.0)
java.lang.UnsupportedClassVersionError:
com/longadata/scapintegration/core/EnotariusSubjectHandlerTest (Unsupported
major.minor version 49.0)
at java.lang.ClassLoader.defineClass0(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
at java.security.SecureClassLoader.defineClass(
SecureClassLoader.java:123)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
at org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(
IsolatedClassLoader.java:100)
at
org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(
AbstractDirectoryTestSuite.java:84)
at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(
Surefire.java:147)
at org.apache.maven.surefire.Surefire.run(Surefire.java:108)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at
org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(
SurefireBooter.java:225)
at org.apache.maven.surefire.booter.SurefireBooter.main(
SurefireBooter.java:747)



Anybody has any idea about what might be causing this error?

Thanks in advance
Allan Valeriano

On 11/13/06, Wayne Fay <[EMAIL PROTECTED]> wrote:


Then I have no idea why its not working for Aaron... ;-)

Wayne

On 11/13/06, Arnaud Bailly <[EMAIL PROTECTED]> wrote:
> "Wayne Fay" <[EMAIL PROTECTED]> writes:
>
> > You can put it in the parent "pom" project with complete configuration
> > etc, but then you also need to include a reference to the
> > compiler-plugin in the build section in each of your modules.
> >
> Hello,
>
> I tried without adding the reference to compiler plugin in 
> section of child project and it works ok.
>
> Regards,
> --
> OQube < software engineering \ génie logiciel >
> Arnaud Bailly, Dr.
> \web> http://www.oqube.com
>
>
> -
> 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: [M1] AspectJ with two source trees (main/src & main/test)

[Jeff Jensen]

So you have aspects in your test classes, and therefore the tests
compilation need AspectJ run on them too.  Changing the maven.test.dest does
not solve the problem.

Have you determined a needed plugin change yet?  I am wondering if the
"correct fix" is to enhance the plugin to have a property that says to run
AspectJ on the tests compilation too?


-Original Message-
From: diyfiesta [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 14, 2006 3:01 AM
To: users@maven.apache.org
Subject: RE: [M1] AspectJ with two source trees (main/src & main/test)


Hi,

Thanks for the note, sorry, its probably not very clear (late night sessions
and all that!).

Not sure if its a red hering or not but I have test classes that are
*affected* by the aspects. So, I have a call pointcut on some method (called
A.doSomething) and and before aspect. The test code calls the method
doSomething and so is affected by the aspect.

Running

maven aspectj

creates target/classes which contain the A class, ATest class and the
aspect. Reverse engineering the test class here shows it has the correctly
weaved (is that the right word) aspect code in it.

running 

maven test (which has a pregoal to run the aspectj compiler)

creates target/test-classes and target.test-reports

The test-classes folder here only contains the test class (ATest.class) and
reverse engineering it shows that the aspect was not weaved. So, runing the
test will fail becuase the test is testing that the aspect is being used.

Changing the default maven.test.dest to something like
${maven.build.dir}/classes seems to help but in my real project doesn't
solve it completly.

I have a test project that demonstrates this (if anyone is interested), all
the settings are pretty much default.

I'll keep playing and post my findings here.

Cheers,



Jeff Jensen wrote:
> 
> Are you saying that the test classes in test-classes need a pass by 
> the AspectJ compiler, or the test classes do not see the AspectJ 
> compiled classes in the classes dir?  (or something else entirely?)
> 
> The fact that the "production" classes compile to target/classes and 
> the test classes compile to /target/test-classes seems correct to me 
> (from what I understand from your emails).  When the tests run, the 
> production code is also on the classpath, so works well (now there 
> could be some bug in that...
> :-).
> 
> 
> -Original Message-
> From: diyfiesta [mailto:[EMAIL PROTECTED]
> Sent: Monday, November 13, 2006 9:53 AM
> To: users@maven.apache.org
> Subject: Re: [M1] AspectJ with two source trees (main/src & main/test)
> 
> 
> So, looking into this more (and having created a simple example 
> project to demonstrate it), it looks like the the aspectj plugin is 
> compiling things correctly, its just that the tests are being run from the
incorrect place.
> 
> So, for example, the output of the aspectj compilation goes into
> 
> target/classes/...
> 
> but the tests run from a folder called
> 
> target/test-classes/... 
> 
> which has the compiled test code, but not the aspectj compiled code. 
> So, if a test is affected by an aspect, it isn't in this folder.
> 
> 
> diyfiesta wrote:
>> 
>> Hi,
>> 
>> Thanks for the note, I tried this but still don't have any luck, for 
>> example, I'm using the convention main/src/java and main/src/test for 
>> my source trees, so adding an src/aspectj folder doesn't really fit 
>> in, if I add it to main/src/aspectj, I get the same problem (and just 
>> for completness, setting it to src/aspectj causes is the same!).
>> 
>> From the plugin's homepage, I didn't get the impression that setting 
>> the soruce directiory to src/aspectj was a requirement more of an 
>> example, and you should be able to set this to whatever your folder 
>> is. Is this not the case?
>> 
>> I think I'll have a go at creating a simple test project that 
>> demonstrates the problem, see if I can get some feedback.
>> 
>> Any other ideas?
>> 
>> Cheers
>> 
>> 
>> Alexandre Touret wrote:
>>> 
>>> Hello,
>>> There are 2 builds : the classes and test classes.
>>> If you specify the aspectsourcedirectory in src/java, aspectj doesn 
>>> t parse any file in src/test. Its the default behaviour I can 
>>> suggest you to put all the aspects file have in 
>>> ${maven.src.dir}/aspectj (as described in the plugin homepage). I 
>>> suppose this directory is accessible in both the build classpaths and
test classpath.
>>> 
>>> Hope this helps.
>>> Alexandre
>>> 
>>> Toby Weston wrote:
 Hi Folks,
 [...]
 I've got my source code under main/src and the unit tests under 
 main/test, however I can't get aspectj compiling both. I added this 
 to my project.xml hoping it would pick up both, but it doesn't seem 
 to,,,

main/src/java

 main/test/java

 I'm kind of not confident I know the correct process, so may be 
 doing something really silly. I was thinking that the pregoal for 
 compile to run the aspectj compiler 

Re: continuum build project more than once

[Martin Testrot]

Hmm, AFAIK showprojects works fine.
At least in my testproject.

Wierschke Robert schrieb:

Ok I already suspected this, but what should I use to update the page in
order to see the results. I tried the Show Projects link but it seems
also to trigger another build.

Thanks
robert

-Original Message-
From: Martin Testrot [mailto:[EMAIL PROTECTED] 
Sent: Dienstag, 14. November 2006 08:45

To: continuum-users@maven.apache.org
Subject: Re: continuum build project more than once

Hi,

don't click "refresh" or hit F5 in your browser.
It seems each refresh sends a new build request.

Greetings,
Martin

Wierschke Robert schrieb:
  

hi,

why does continuum build my projects multiple times (up to 31) when i


click on build now???
  

robert
  



  

RE: out of memory problem in maven 1.x

[Jeff Jensen]

http://maven.apache.org/maven-1.x/reference/command-line.html
 

-Original Message-
From: Neeraj Bisht [mailto:[EMAIL PROTECTED] 
Sent: Tuesday, November 14, 2006 6:25 AM
To: Maven Users List
Subject: out of memory problem in maven 1.x

hi
we are  compiling  our gwt source with maven 1.x but now our  project is
become heaver and on compiling through maven it give out of memory problem

is there any way by which we increash the memory of maven 1.x

Thanks

Regards
Neeraj



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

Re: out of memory problem in maven 1.x

[Arnaud HERITIER]

Set your JVM settings in the environment's variable MAVEN_OPTS
For example : MAVEN_OPTS=-Xmx512m

Arnaud



Neeraj Bisht wrote:
> 
> hi
> we are  compiling  our gwt source with maven 1.x but now our  project
> is  become heaver and on compiling through maven it give out of memory
> problem
> 
> is there any way by which we increash the memory of maven 1.x
> 
> Thanks
> 
> Regards
> Neeraj
> 
> 

-- 
View this message in context: 
http://www.nabble.com/out-of-memory-problem-in-maven-1.x-tf2629140s177.html#a7337663
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Problems using Maven 2 exec plugin

[Petterson F. Paula]

Hello,

 

I'm having a problem while I try to run the maven-exec-plugin with goal=exec
and phase=generate-sources.  The executable I want to run is the apt (Java
Annotation Tool Processor), so I set executable=apt.

 

What occurs is that for some reason the command invoked is the base
directory of the project (basedir) is concatenated with apt.

i.e.:

Project Base Directory (basedir): c:\dev\eclipse-workspace\myproject

 

The invoked command when I call mvn install is:

C:\dev\eclipse-workspace\myproject\apt .

 

Anyone knows how to fix this?

 

Thanks in Advance,

 

Petterson

Re: Archiva Start-Up Error

[Emmanuel Venisse]

As it is written in this page : "A Derby exception "Schema 'SA' does not exist" occurs, but is not 
of concern."


It isn't an error, the database doens't exist and jpox create it after this 
message.

Emmanuel

[EMAIL PROTECTED] a écrit :

Hi

I am trying to start up Archiva using the jetty:run, using the
Getting-Started 
guide http://maven.apache.org/archiva/guides/getting-started/index.html


When I pointed my browser to localhost:9091 I got a severe error.


2006-11-14 10:20:28,866 [btpool0-2] INFO
EnvironmentCheck:required-roles - Chec
king the existance of required roles.
2006-11-14 10:20:34,522 [btpool0-2] WARN  RDBMS
- Error
 initialising derby schema : Schema 'SA' does not exist
ERROR 42Y07: Schema 'SA' does not exist
at
org.apache.derby.iapi.error.StandardException.newException(Unknown So
urce)
at
org.apache.derby.impl.sql.catalog.DataDictionaryImpl.getSchemaDescrip
tor(Unknown Source)
at
org.apache.derby.impl.sql.compile.QueryTreeNode.getSchemaDescriptor(U
nknown Source)
at
org.apache.derby.impl.sql.compile.DDLStatementNode.getSchemaDescripto
r(Unknown Source)
at org.apache.derby.impl.sql.compile.DropAliasNode.bind(Unknown
Source)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown
Source)

at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown
Source)
at
org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepa
reInternalStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown
Source)
at
org.jpox.store.rdbms.adapter.DerbyAdapter.initialiseDatastore(DerbyAd
apter.java:125)
at
org.jpox.store.rdbms.RDBMSManager.initialiseSchema(RDBMSManager.java:
492)
at
org.jpox.store.rdbms.RDBMSManager.(RDBMSManager.java:265)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)

at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at org.jpox.util.ClassUtils.newInstance(ClassUtils.java:64)
at
org.jpox.store.StoreManagerFactory.getStoreManager(StoreManagerFactor
y.java:73)
at
org.jpox.AbstractPersistenceManager.(AbstractPersistenceManager
.java:224)
at
org.jpox.PersistenceManagerImpl.(PersistenceManagerImpl.java:42
)
at
org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager(Persiste
nceManagerFactoryImpl.java:175)
at
org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager(Persiste
nceManagerFactoryImpl.java:150)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.get
PersistenceManager(JdoTool.java:114)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.get
ObjectById(JdoTool.java:236)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.obj
ectExistsById(JdoTool.java:283)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoRbacMana
ger.roleExists(JdoRbacManager.java:124)
at
org.codehaus.plexus.rbac.profile.AbstractRoleProfile.getRole(Abstract
RoleProfile.java:236)
at
org.codehaus.plexus.rbac.profile.DefaultRoleProfileManager.getRole(De
faultRoleProfileManager.java:72)
at
org.codehaus.plexus.security.ui.web.checks.security.RequiredRolesEnvi
ronmentCheck.validateEnvironment(RequiredRolesEnvironmentCheck.java:64)
at
org.codehaus.plexus.security.ui.web.interceptor.EnvironmentCheckInter
ceptor.init(EnvironmentCheckInterceptor.java:78)
at
org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(Plexus
ObjectFactory.java:101)
at
com.opensymphony.xwork.config.providers.InterceptorBuilder.constructI
nterceptorReference(InterceptorBuilder.java:48)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.look
upInterceptorReference(XmlConfigurationProvider.java:702)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.load
InterceptorStack(XmlConfigurationProvider.java:569)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.load
InterceptorStacks(XmlConfigurationProvider.java:582)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.load
Interceptors(XmlConfigurationProvider.java:603)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.addP
ackage(XmlConfigurationProvider.java:204)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.load
ConfigurationFile(XmlConfigurationProvider.java:676)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.init
(XmlConfigurationProvider.java:91)
at
com.opensymphony.xwork.config.impl.DefaultConfiguration.reload(Defaul
tConfig

Re: Intalled pom version is not expanded resulting in a bogus pom version in the repository.

[pjungwir]

If you're installing the artifact every build, you might want to use a
-SNAPSHOT version.

Paul


Arne Saeten wrote:
> 
> 
> Hi,
> 
> I have the same problem. Any solutions out there?
> 
> Thanks,
> Arne
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Intalled-pom-version-is-not-expanded-resulting-in-a-bogus-pom-version-in-the-repository.-tf1558832s177.html#a7340673
Sent from the Maven - Users mailing list archive at Nabble.com.


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

out of memory problem in maven 1.x

[Neeraj Bisht]

hi
   we are  compiling  our gwt source with maven 1.x but now our  project
is  become heaver and on compiling through maven it give out of memory
problem

is there any way by which we increash the memory of maven 1.x

Thanks

Regards
Neeraj

Re: Setting up a new jre to maven

[Wayne Fay]

Unsupported major.minor version indicates you're trying to run a
newer-compiled Java class in an older JRE. In this case, seems like
you've compiled classes with JRE 5 and are attempting to execute them
(testing w/Surefire?) with JRE 3 or 4.

Check your PATH... I'd guess you've got a JRE 3 or 4 in your PATH somewhere and 
its being used instead of JRE 5.

Wayne

On 11/14/06, Allan Valeriano <[EMAIL PROTECTED]> wrote:

I found out that my project' parent have on its pom.xml the configuration to
compile with jre5 already.
So I was thinking the problem I'm having is not being caused by the jre and
so by another mystical thing.
Here goes the error:

[INFO]
>

> [INFO] Building scap-integration-core
> [INFO]task-segment: [install]
> [INFO]
>

> [INFO] [resources:resources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:compile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [resources:testResources]
> [INFO] Using default encoding to copy filtered resources.
> [INFO] [compiler:testCompile]
> [INFO] Nothing to compile - all classes are up to date
> [INFO] [surefire:test]
> [INFO] Surefire report directory:
>
/home/valeriano/.eclipse/scap-integration-branch/scap-integration-core/target/surefire-reports
> org.apache.maven.surefire.booter.SurefireExecutionException:
> com/longadata/scapintegration/core/EnotariusSubjectHandlerTest
(Unsupported
> major.minor version 49.0); nested exception is
> java.lang.UnsupportedClassVersionError:
> com/longadata/scapintegration/core/EnotariusSubjectHandlerTest
(Unsupported
> major.minor version 49.0)
> java.lang.UnsupportedClassVersionError:
> com/longadata/scapintegration/core/EnotariusSubjectHandlerTest
(Unsupported
> major.minor version 49.0)
> at java.lang.ClassLoader.defineClass0(Native Method)
> at java.lang.ClassLoader.defineClass(ClassLoader.java:539)
> at java.security.SecureClassLoader.defineClass(
> SecureClassLoader.java:123)
> at java.net.URLClassLoader.defineClass(URLClassLoader.java:251)
> at java.net.URLClassLoader.access$100(URLClassLoader.java:55)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:194)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:187)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:289)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:235)
> at org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(
> IsolatedClassLoader.java:100)
> at
> org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.locateTestSets(
> AbstractDirectoryTestSuite.java:84)
> at org.apache.maven.surefire.Surefire.createSuiteFromDefinition(
> Surefire.java:147)
> at org.apache.maven.surefire.Surefire.run(Surefire.java:108)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(
> NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at
> org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess(
> SurefireBooter.java:225)
> at org.apache.maven.surefire.booter.SurefireBooter.main(
> SurefireBooter.java:747)
>
>
Anybody has any idea about what might be causing this error?

Thanks in advance
Allan Valeriano

On 11/13/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
>
> Then I have no idea why its not working for Aaron... ;-)
>
> Wayne
>
> On 11/13/06, Arnaud Bailly <[EMAIL PROTECTED]> wrote:
> > "Wayne Fay" <[EMAIL PROTECTED]> writes:
> >
> > > You can put it in the parent "pom" project with complete configuration
> > > etc, but then you also need to include a reference to the
> > > compiler-plugin in the build section in each of your modules.
> > >
> > Hello,
> >
> > I tried without adding the reference to compiler plugin in 
> > section of child project and it works ok.
> >
> > Regards,
> > --
> > OQube < software engineering \ génie logiciel >
> > Arnaud Bailly, Dr.
> > \web> http://www.oqube.com
> >
> >
> > -
> > 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: tomcat deployer

[Greg_Vaughn]

"Kevin Jackson" <[EMAIL PROTECTED]> wrote on 11/14/2006 03:17:09 AM:

> Hi all,
> 
> I'm trying to work on a webapp with tomcat and mvn.  I want to be able
> to edit a jsp, type mvn tomcat:redeploy and have just the changed jsp
> be reloaded, without having to compile/package/deploy
> 
> I'm fairly sure that this is possible using a combination of mvn +
> tomcat-plugin, but I'm failing the correct incantation test
> 
> so far I can do a mvn tomcat:deploy, but this
> compiles/filters/packages and takes forever - not good for rapid
> development of ui stuff
> 
> mvn tomcat:redeploy seems to just redeploy the application that's
> already deployed in the CATALINA_HOME/webapps directory, what I need
> is some way to configure the plugin to deploy my development directory
> as an exploded web application

This gets discussed fairly regularly and there's multiple ways to handle 
it.
If you're not aware, there's a great search engine for this list at
http://www.nabble.com/Maven---Users-f178.html

The way I've setup things I can see the changed jsp without calling
any maven target. There's more details of my solution here
http://www.nabble.com/Eclipse-war-builder-tf2371898s177.html#a6646490
Another fellow wrote a custom eclipse plugin to help him.

If you actually want to call tomcat:redeploy before seeing the changed
jsp, you may want to look at the tomcat:inplace goal or maybe 
war:exploded.

Greg Vaughn
[EMAIL PROTECTED]

==
Confidentiality Notice: The information contained in and transmitted with this 
communication is strictly confidential, is intended only for the use of the 
intended recipient, and is the property of Countrywide Financial Corporation or 
its affiliates and subsidiaries.  If you are not the intended recipient, you 
are hereby notified that any use of the information contained in or transmitted 
with the communication or dissemination, distribution, or copying of this 
communication is strictly prohibited by law.  If you have received this 
communication in error, please immediately return this communication to the 
sender and delete the original message and any copy of it in your possession.
==

Re: SCM integration issue with deleted files

[Wayne Fay]

Tell your developers to stop deleting files? ;-)

Sounds like a bug, go file it in JIRA and I'm sure it will be looked
at and hopefully addressed in a future version.

Wayne

On 11/14/06, ETIENNE Olivier <[EMAIL PROTECTED]> wrote:

I got the same problem and the only way I foun to solve it has been to
drop the project and to create a new one.

Adam Hardy a écrit :
> I keep seeing a problem with continuum when a developer deletes a file.
>
> Sometimes but not always continuum fails to delete the file from its
> working directory. Then at some point soon afterwards, that deleted
> class file will no longer compile, so the build fails and I receive a
> notification.
>
> What is the best procedure to deal with this? Must I hunt down the
> deleted files and manually delete them?
>
> In a rush this morning, I deleted everything in /working-dir/ with rm
> -rf *
>
> Continuum did not like it. When I launched the build, it stopped
> immediately with:
>
> java.lang.NullPointerException
> at
>
org.codehaus.plexus.component.configurator.converters.lookup.DefaultConverterLookup.findConverterForType(DefaultConverterLookup.java:115)
>
>
> I had to restart continuum, and then the first build attempt died
> badly with this:
>
> Exception:
> Cannot checkout sources.
> null
>
> but on the second attempt it behaved OK. Why is the working-dir so
> important? Can't continuum detect that it needs to check out the
> sources again? Is there a better way to delete all the sources without
> causing this mess?
>
>
> Thanks
> Adam
>
>

Re: Surefire and TestNG

[Christopher Maki]

Hi Wayne

Thanks for getting back to me.  I didn't think this was a bug.  I thought it 
had something to do with the way I was using Surefire and TestNG.  The Surefire 
plugin page indicates you can use a testng.xml file so I thought it should 
work.  I was hoping to find someone that uses TestNG with Maven 2 and find out 
how they got the testng.xml file to work with their project.  If this is a bug 
I have not problem opening a JIRA issue, but I wanted to find out what others 
experiences were before I did that :-)

Thanks again

Chris

On Tuesday, November 14, 2006, at 08:18AM, "Wayne Fay" <[EMAIL PROTECTED]> 
wrote:
>Bugs should be posted in JIRA, not the Users list.
>
>Wayne
>
>On 11/14/06, Christopher Maki <[EMAIL PROTECTED]> wrote:
>> Hi
>>
>> I seem to be having a problem with TestNG 5.1 and the Surefire plugin
>> (either 2.3-SNAPSHOT or 2.2).  When using Surefire 2.3-SNAPSHOT I get this
>> error when I try to run my tests:
>>
>> ---
>>  T E S T S
>> ---
>> org.apache.maven.surefire.booter.SurefireExecutionException:
>> Cannot find class in classpath: org.maki.model.BankAccountFactory; nested
>> exception is org.testng.TestNGException:
>> Cannot find class in classpath: org.maki.model.BankAccountFactory
>> org.testng.TestNGException:
>> Cannot find class in classpath: org.maki.model.BankAccountFactory
>>  at org.testng.xml.XmlClass.getSupportClass(XmlClass.java:45)
>>  at org.testng.internal.Utils.xmlClassesToClasses(Utils.java:82)
>>  at org.testng.TestRunner.initMethods(TestRunner.java:273)
>>  at org.testng.TestRunner.init(TestRunner.java:212)
>>  at org.testng.TestRunner.init(TestRunner.java:184)
>>  at org.testng.TestRunner.(TestRunner.java:121)
>>  at
>> org.testng.SuiteRunner$DefaultTestRunnerFactory.newTestRunner(SuiteRunner.java:376)
>> 
>>
>> The problem stems from using a testng.xml file.  If I just run the tests
>> without testng.xml all methods for all tests are executed, but if I try to
>> customize the execution via testng.xml I get the above error.  I've attached
>> a very small project to illustrate the problem I'm having.
>>
>> Any feedback is much appreciated.
>>
>> Thanks
>>
>> Chris
>>
>>
>>
>>
>
>-
>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]

site-deploy not copying Java Docs

[Dmystery]

I've a multi-module project for which i'm generating a site. 

I'm doing a mvn site:stage -DstagingDirectory=somedirectory. This works fine
and the modules are linked properly too. However, the Java doc generated are
not copied to the staging directory. Only the index.html is copied, the rest
remains in the project build directory. 

My parent pom looks like, 
.
.

  
  my-site 
  my-site 
  file:// 
  



   
 
   maven-javadoc-plugin
 
 
   org.codehaus.mojo
   jxr-maven-plugin
   
   

.
.

Interestingly, instead of the above command, if i use 'mvn site-deploy' with

  
  my-site 
  my-site 
  file://c:/somedirectory 
 

in my pom, the apidocs are copied but the module and apidocs links do not
exists. 

Is there a clean way of deploying a site on to the local machine?? 






-- 
View this message in context: 
http://www.nabble.com/site-deploy-not-copying-Java-Docs-tf2628872s177.html#a7335796
Sent from the Maven - Users mailing list archive at Nabble.com.


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

how to make an installer for my application ?

[Valerio Schiavoni]

hello everyone,
i'm developing a application that need to be installed on customer
machines (possibly, different machines, win/lin/mac).

the packaging of my application is 'war', which restrict the field of
possibilities: my installer should infact ship with an application
server. my choice  in this perspective is jetty (even because I use it
to test my application).

Not being enough, the installer should also ship a dbms to be used by
my application: for my tests i've been using hsql, which is fine, but
the size of the dbms can possibly grow up to gigabytes, and hsql is
not an option..


Now, how can I produce such a magic installer, possibly within maven ?
I've seen a izpack-maven-plugin in JIRA
http://jira.codehaus.org/browse/MOJO-277, but i'm not sure it could be
enough..

thanks for any suggestions!
valerio
--
http://jroller.com/page/vschiavoni

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

Re: Trying Quickly build Archiva

[Tom Huybrechts]

If you are behing a proxy, this might be caused by the
https-repository that is added by the archiva POMs. Try adding cmdline
arguments: -Dhttps.proxyHost=... -Dhttps.proxyPort=...

Tom

On 11/13/06, Wendy Smoak <[EMAIL PROTECTED]> wrote:

On 11/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:

> I download all of the software from the required page as described. The
> sun jars.
> I cant see what is wrong there. It happens more than once in build
> Archive Security
> Configuration project.

The error you posted said it couldn't download commons-configuration
1.3, which is definitely available.  Are you still getting the same
error?  Does it download anything at all?

(At this point I start suspecting you're behind a proxy, because we've
seen numerous reports of problems when a proxy is involved.)

Sorry I can't help more, but Archiva builds fine here.

--
Wendy

-
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]

SCM integration issue with deleted files

[Adam Hardy]

I keep seeing a problem with continuum when a developer deletes a file.

Sometimes but not always continuum fails to delete the file from its 
working directory. Then at some point soon afterwards, that deleted 
class file will no longer compile, so the build fails and I receive a 
notification.


What is the best procedure to deal with this? Must I hunt down the 
deleted files and manually delete them?


In a rush this morning, I deleted everything in /working-dir/ with rm -rf *

Continuum did not like it. When I launched the build, it stopped 
immediately with:


java.lang.NullPointerException
	at 
org.codehaus.plexus.component.configurator.converters.lookup.DefaultConverterLookup.findConverterForType(DefaultConverterLookup.java:115)


I had to restart continuum, and then the first build attempt died badly 
with this:


Exception:
Cannot checkout sources.
null

but on the second attempt it behaved OK. Why is the working-dir so 
important? Can't continuum detect that it needs to check out the sources 
again? Is there a better way to delete all the sources without causing 
this mess?



Thanks
Adam

change the local repository in maven 1.x

[Neeraj Bisht]

hi
   we are using GWT ,and we build our GWT project with maven 1.x ,now
google release new jar and this time the jar path should not contain any
spaces in between the path
but we all know that maven build the repository at
$(userhome}/.maven/repositort

and  userhome contain spaces like c:/document and seeting/   (by default
maven genrate the local repository at this location)

now i need to change the local repository to the place where there is no
space in path

like c:/mavenrepository

in maven 2.x i know we can do it by seeting.xml how we can do in maven
1.xplease any body tell me with example

Regards
Neeraj

Re: SCM integration issue with deleted files

[ETIENNE Olivier]

I got the same problem and the only way I foun to solve it has been to 
drop the project and to create a new one.


Adam Hardy a écrit :

I keep seeing a problem with continuum when a developer deletes a file.

Sometimes but not always continuum fails to delete the file from its 
working directory. Then at some point soon afterwards, that deleted 
class file will no longer compile, so the build fails and I receive a 
notification.


What is the best procedure to deal with this? Must I hunt down the 
deleted files and manually delete them?


In a rush this morning, I deleted everything in /working-dir/ with rm 
-rf *


Continuum did not like it. When I launched the build, it stopped 
immediately with:


java.lang.NullPointerException
at 
org.codehaus.plexus.component.configurator.converters.lookup.DefaultConverterLookup.findConverterForType(DefaultConverterLookup.java:115) 



I had to restart continuum, and then the first build attempt died 
badly with this:


Exception:
Cannot checkout sources.
null

but on the second attempt it behaved OK. Why is the working-dir so 
important? Can't continuum detect that it needs to check out the 
sources again? Is there a better way to delete all the sources without 
causing this mess?



Thanks
Adam

JExcelAPI in Repository: 2.4.2. Latest Version: 2.6.2

[Subhash Chandran]

I have done this before: filing a bug for newer version of a library.
But I do not remember the procedure now, and I am not able to find the
document describing how to do this.

If anybody could get this component updated, it would be helpful:

http://www.ibiblio.org/maven2/jexcelapi/jxl/

--
Regards,
Subhash Chandran S

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

Maven plugin interaction

[Mikko]

Hi,

First the environment: 

1. Multimodule midp2.0 application - must have (OK)
2. Assembly is required - must have (OK)
3. Assembled code jar obfuscation - optinal (NOK)
3. Assembled code jar preverification - must have (NOK)

What I'm trying to do is to write a plugin(s) for our MIDP project so that
above steps are accomplished. My problem is that after the assembly is
complete some jar is constructed and once either the obfuscation or the
preverification needs to take place the plugin does not know the name of the
jar that was produced by the maven-assembly-plugin.

It might be that I'm approaching this the wrong way, but could someone point
me to the right direction, either by suggesting another approach or
whatever... ;) Basically once the assembly is complete I need to do the
obfuscation and preverification with the result.

thanks in advance,
Mikko

-- 
View this message in context: 
http://www.nabble.com/Maven-plugin-interaction-tf2628577s177.html#a7335041
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: jars not being included in compiler classpath

[Jeff Mutonho]

Thanx ...much appreciated

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042

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

Re: JExcelAPI in Repository: 2.4.2. Latest Version: 2.6.2

[Gisbert Amm]

AFAIK, you have to file a JIRA against MAVENUPLOAD.

-Gisbert

Subhash Chandran wrote:

I have done this before: filing a bug for newer version of a library.
But I do not remember the procedure now, and I am not able to find the
document describing how to do this.

If anybody could get this component updated, it would be helpful:

http://www.ibiblio.org/maven2/jexcelapi/jxl/


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

Re: jars not being included in compiler classpath

[Wayne Fay]

Scope test is not included in build classpath. Both "problem" jars are
scoped "test". The others have no scope so they default to "compile".

Wayne

On 11/14/06, Jeff Mutonho <[EMAIL PROTECTED]> wrote:

I have a small proof of concept I'm trying to build.In the project's
super pom , I have a dependency to spring specified as

  
  oracle.ldap
  ldapjclnt
  1.0


  javax.j2ee
  j2ee
  1.3.0

   
  org.springframework
  spring
  1.2.3
  test


  org.apache.log4j
  log4j
  1.2.13
  test



However when I run the build I'm getting build failure due to failed
dependencies on the spring-1.2.3.jar and the log4j-1.2.13.jar  files.

A snippet of the log shows that these two jars are not being passed to
the maven-compiler-plugin 's classpath :

[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.0.1:compile' -->
[DEBUG]   (f) basedir =
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal
[DEBUG]   (f) buildDirectory =
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target
[DEBUG]   (f) classpathElements =
[C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes,
D:\Documents and
Settings\mutonhj\.m2\repository\javax\j2ee\j2ee\1.3.0\j2ee-1.3.0.jar,
D:\Documents and
Settings\mutonhj\.m2\repository\oracle\ldap\ldapjclnt\1.0\ldapjclnt-1.0.jar]
[DEBUG]   (f) compileSourceRoots =
[C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src]
[DEBUG]   (f) compilerId = javac
[DEBUG]   (f) debug = true
[DEBUG]   (f) fork = false
[DEBUG]   (f) optimize = false
[DEBUG]   (f) outputDirectory =
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
[DEBUG]   (f) outputFileName = dev-ep1x-eportal-1.0.0
[DEBUG]   (f) projectArtifact =
za.co.pragmaticus.dev-ep1x.eportal:dev-ep1x-eportal:ejb:1.0.0
[DEBUG]   (f) showDeprecation = false
[DEBUG]   (f) showWarnings = false
[DEBUG]   (f) staleMillis = 0
[DEBUG]   (f) verbose = false
[DEBUG] -- end configuration --
[INFO] [compiler:compile]
[DEBUG] Using compiler 'javac'.
[DEBUG] Source directories:
[C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src]
[DEBUG] Classpath:
[C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
 D:\Documents and
Settings\mutonhj\.m2\repository\javax\j2ee\j2ee\1.3.0\j2ee-1.3.0.jar
 D:\Documents and
Settings\mutonhj\.m2\repository\oracle\ldap\ldapjclnt\1.0\ldapjclnt-1.0.jar]
[DEBUG] Output directory:
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
[DEBUG] Classpath:
[DEBUG]
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
[DEBUG]  D:\Documents and
Settings\mutonhj\.m2\repository\javax\j2ee\j2ee\1.3.0\j2ee-1.3.0.jar
[DEBUG]  D:\Documents and
Settings\mutonhj\.m2\repository\oracle\ldap\ldapjclnt\1.0\ldapjclnt-1.0.jar
[DEBUG] Source roots:
[DEBUG]
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src
Compiling 392 source files to
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] Compilation failure

.

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[5,24]
package org.apache.log4j does not exist

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[6,43]
package org.springframework.web.servlet.mvc does not exist

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[7,44]
package org.springframework.web.servlet.view does not exist

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[8,39]
package org.springframework.web.servlet does not exist

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[10,41]
package org.springframework.beans.factory does not exist


This does not seem to make any sense , because the other 2 jars in my
dependency configuration , namely  ldapjclnt-1.0.jar and
j2ee-1.3.0.jar , are included in the build classpath.

--

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042

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




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

Re: http://www.ibiblio.org/maven2 vs. http://repo1.maven.org/maven2?

[Wayne Fay]

If you look in more detail:
http://www.ibiblio.org/pub/packages/maven2/javax/j2ee/j2ee/1.4/

You'll see that no binaries are available for javax.j2ee, but only
poms. This is due to the licensing of the J2EE 1.4 jars. So you can
use these poms but must download and manually install the jars.

Eventually we will get JavaEE jars which are available under a license
(CDDL or GPL) which allows redistribution. At that time, the files
will be hosted and available via Maven.

Wayne

On 11/13/06, jiangshachina <[EMAIL PROTECTED]> wrote:


It seems that j2ee.jar(javax.j2ee) is at central repository, but
javaee.jar(JavaEE 5.0).
javaee.jar would be added to the repository in the future, or no forever?

a cup of Java, cheers!
Sha Jiang


jiangshachina wrote:
>
> Hi Brett,
> It means that group springframework is deprecated, too.
> Oh, I may make a serious mistake, if without your help.
> Thanks very much!
>
> a cup of Java, cheers!
> Sha Jiang
>
>
> Brett Porter wrote:
>>
>> On 14/11/06, jiangshachina <[EMAIL PROTECTED]> wrote:
>>> They have same artifactsId, but the artifacts in springframework are
>>> newer.
>>> It means the group spring is deprecated?
>>
>> Some newer versions get moved to a new group ID. We are generally
>> trying to consolidate them over time, and migrate old ones.
>>
>>>
>>> There are many similar cases in central repository, how can I deal with
>>> the
>>> matter?
>>
>> Find the one with the version you are using.
>>
>>> May have a convention for names of the groups?
>>
>> The convention is reverse-domain. So you will probably find all the
>> newest releases in org.springframework group ID (directory
>> org/springframework/).
>>
>> - Brett
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>
>

--
View this message in context:
http://www.nabble.com/http%3A--www.ibiblio.org-maven2-vs.-http%3A--repo1.maven.org-maven2--tf2627036s177.html#a7331953
Sent from the Maven - Users mailing list archive at Nabble.com.


-
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: Trying Quickly build Archiva

[Peter . Pilgrim]

> -Original Message-
> From: Wendy Smoak [mailto:[EMAIL PROTECTED] 
====
> 
> On 11/13/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> 
> > I download all of the software from the required page as described. 
> > The sun jars.
> > I cant see what is wrong there. It happens more than once in build 
> > Archive Security Configuration project.
> 
> The error you posted said it couldn't download 
> commons-configuration 1.3, which is definitely available.  
> Are you still getting the same error?  Does it download 
> anything at all?
> 
> (At this point I start suspecting you're behind a proxy, 
> because we've seen numerous reports of problems when a proxy 
> is involved.)
> 
> Sorry I can't help more, but Archiva builds fine here.
 
Indeed it does, Wendy, I just download the dependencies and put them
into
the POM.

-- 
Peter Pilgrim
JUG Leader( JAVAWUG http://jroller.com/page/javawug )
Registration http://developers.sun.com/jugs/display/europe/gbr/london )

   ( ( (  (   (  
   (   )\(   (   )\)\))(   '   (  )\ )  
   )_)(  )\  )_)( ((_)()\ ))\(()/(  
  ((_)\ _ )\((_)((_)\ _ )\_(())\_)()_ ((_)/(_))_
 _ | (_)_\(_) \ / /(_)_\(_) \((_)/ / | | (_)) __|
| || |/ _ \  \ V /  / _ \  \ \/\/ /| |_| | | (_ |
 \__//_/ \_\  \_/  /_/ \_\  \_/\_/  \___/   \___| 

Visit our website at http://www.ubs.com

This message contains confidential information and is intended only
for the individual named.  If you are not the named addressee you
should not disseminate, distribute or copy this e-mail.  Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.

E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses.  The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission.  If
verification is required please request a hard-copy version.  This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.


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

Archiva Start-Up Error

[Peter . Pilgrim]

Hi

I am trying to start up Archiva using the jetty:run, using the
Getting-Started 
guide http://maven.apache.org/archiva/guides/getting-started/index.html

When I pointed my browser to localhost:9091 I got a severe error.


2006-11-14 10:20:28,866 [btpool0-2] INFO
EnvironmentCheck:required-roles - Chec
king the existance of required roles.
2006-11-14 10:20:34,522 [btpool0-2] WARN  RDBMS
- Error
 initialising derby schema : Schema 'SA' does not exist
ERROR 42Y07: Schema 'SA' does not exist
at
org.apache.derby.iapi.error.StandardException.newException(Unknown So
urce)
at
org.apache.derby.impl.sql.catalog.DataDictionaryImpl.getSchemaDescrip
tor(Unknown Source)
at
org.apache.derby.impl.sql.compile.QueryTreeNode.getSchemaDescriptor(U
nknown Source)
at
org.apache.derby.impl.sql.compile.DDLStatementNode.getSchemaDescripto
r(Unknown Source)
at org.apache.derby.impl.sql.compile.DropAliasNode.bind(Unknown
Source)
at org.apache.derby.impl.sql.GenericStatement.prepMinion(Unknown
Source)

at org.apache.derby.impl.sql.GenericStatement.prepare(Unknown
Source)
at
org.apache.derby.impl.sql.conn.GenericLanguageConnectionContext.prepa
reInternalStatement(Unknown Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown
Source)
at org.apache.derby.impl.jdbc.EmbedStatement.execute(Unknown
Source)
at
org.jpox.store.rdbms.adapter.DerbyAdapter.initialiseDatastore(DerbyAd
apter.java:125)
at
org.jpox.store.rdbms.RDBMSManager.initialiseSchema(RDBMSManager.java:
492)
at
org.jpox.store.rdbms.RDBMSManager.(RDBMSManager.java:265)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native
Method)

at
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstruct
orAccessorImpl.java:39)
at
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingC
onstructorAccessorImpl.java:27)
at
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
at org.jpox.util.ClassUtils.newInstance(ClassUtils.java:64)
at
org.jpox.store.StoreManagerFactory.getStoreManager(StoreManagerFactor
y.java:73)
at
org.jpox.AbstractPersistenceManager.(AbstractPersistenceManager
.java:224)
at
org.jpox.PersistenceManagerImpl.(PersistenceManagerImpl.java:42
)
at
org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager(Persiste
nceManagerFactoryImpl.java:175)
at
org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager(Persiste
nceManagerFactoryImpl.java:150)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.get
PersistenceManager(JdoTool.java:114)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.get
ObjectById(JdoTool.java:236)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoTool.obj
ectExistsById(JdoTool.java:283)
at
org.codehaus.plexus.security.authorization.rbac.store.jdo.JdoRbacMana
ger.roleExists(JdoRbacManager.java:124)
at
org.codehaus.plexus.rbac.profile.AbstractRoleProfile.getRole(Abstract
RoleProfile.java:236)
at
org.codehaus.plexus.rbac.profile.DefaultRoleProfileManager.getRole(De
faultRoleProfileManager.java:72)
at
org.codehaus.plexus.security.ui.web.checks.security.RequiredRolesEnvi
ronmentCheck.validateEnvironment(RequiredRolesEnvironmentCheck.java:64)
at
org.codehaus.plexus.security.ui.web.interceptor.EnvironmentCheckInter
ceptor.init(EnvironmentCheckInterceptor.java:78)
at
org.codehaus.plexus.xwork.PlexusObjectFactory.buildInterceptor(Plexus
ObjectFactory.java:101)
at
com.opensymphony.xwork.config.providers.InterceptorBuilder.constructI
nterceptorReference(InterceptorBuilder.java:48)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.look
upInterceptorReference(XmlConfigurationProvider.java:702)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.load
InterceptorStack(XmlConfigurationProvider.java:569)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.load
InterceptorStacks(XmlConfigurationProvider.java:582)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.load
Interceptors(XmlConfigurationProvider.java:603)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.addP
ackage(XmlConfigurationProvider.java:204)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.load
ConfigurationFile(XmlConfigurationProvider.java:676)
at
com.opensymphony.xwork.config.providers.XmlConfigurationProvider.init
(XmlConfigurationProvider.java:91)
at
com.opensymphony.xwork.config.impl.DefaultConfiguration.reload(Defaul
tConfiguration.java:85)
at
com.opensymphony.xwork.config.ConfigurationManager.getConfiguration(C
onfigurationManager.java:54)
at
com.opensymphony.xwork.DefaultActionProxy.(DefaultActionProxy.j
ava:57)
at
com.opensymphony.xwo

RE: weblogic-maven-plugin:using properties file

[Dmystery]

Scott, 

Can you let me know the correct way to do this? I'm not able to substitute
the plugin config values using the properties file. I think this is quite
trivial. 



Dmystery wrote:
> 
> I did somthing like - 
> 
>   
>deploy 
> 
> 
>deploy 
>true 
> 
> 
>
> 
> 
>  org.codehaus.mojo
>  weblogic-maven-plugin
>  2.8.0-SNAPSHOT
>  
>  
> ${project.build.directory}/${project.artifactId}-${project.version}.ear
>   true
>   true
>   false
>   true
>   ${host}
>   ${port}
>   t3
>   ${user}
>   ${password}
>   false
>   false
>   false
>   false
>   ${server.name}
>  
>  
>   
>package
>
>   deploy
>
>
>  
>  
> 
>  
>  ../../env/${env}.properties //The configuration
> values marked bold are in this file
>  
> 
>   
> 
> When i do 'mvn install -Ddeploy=true -Denv=dev', the above profile is
> executed but it fails to pick up the porperties from the dev.properties
> file. It tries to use the default porperties as of a localhost. Is it the
> case that the filter will only work for resources? I'm using the same
> filter for compiling the resources. 
> 
> 
> Scott Ryan-2 wrote:
>> 
>> You just need to configure the plugin in your different profiles.  You
>> can
>> have a different set of configurations in each profile definition.
>> 
>> Scott Ryan
>> Chief Technology Officer
>> Soaring Eagle L.L.C.
>> [EMAIL PROTECTED]
>> www.soaringeagleco.com
>> (303) 263-3044
>> 
>> -Original Message-
>> From: Dmystery [mailto:[EMAIL PROTECTED]
>> Sent: Wednesday, November 08, 2006 4:35 AM
>> To: users@maven.apache.org
>> Subject: weblogic-maven-plugin:using properties file
>> 
>> 
>> 
>> How can i use a properties file in weblogic-maven-plugin. I've to deploy
>> an
>> ear on different enviroments and the
>> ,
>> etc will hold values based on the environment. At the pom level i can
>> access
>> the appropriate properties file using profiles, but the same properties
>> are
>> not available in the plugin.
>> 
>> Any solution???
>> --
>> View this message in context:
>> http://www.nabble.com/weblogic-maven-plugin%3Ausing-properties-file-tf259470
>> 5s177.html#a7236919
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>> 
>> 
>> -
>> 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]
>> 
>> 
>> 
> 
> 

-- 
View this message in context: 
http://www.nabble.com/weblogic-maven-plugin%3Ausing-properties-file-tf2594705s177.html#a7334793
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: jars not being included in compiler classpath

[Mark Struberg]

> I get  confused by the scope thing.If scope is test
> , does that mean
> the jars will only be used in the test phase of the
> build lifecycle?

Exactly, they are only available for the phases needed
for the test compile, executing the test and building
the test reports.

This are the following phases of the default lifecycle
(more at
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
)
.) generate-test-sources
.) process-test-sources
.) generate-test-resources
.) process-test-resources
.) test-compile
.) test
and for what i know also the integration test phases:
.) pre-integration-test
.) integration-test
.) post-integration-test

plus the phases from the site lifecycle (for building
test reports)

lg,
strub

--- Jeff Mutonho <[EMAIL PROTECTED]> schrieb:

> On 11/14/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
> > Scope test is not included in build classpath.
> Both "problem" jars are
> > scoped "test". The others have no scope so they
> default to "compile".
> >
> > Wayne
> >
> 
> I get  confused by the scope thing.If scope is test
> , does that mean
> the jars will only be used in the test phase of the
> build lifecycle?
> 
> Jeff  Mutonho
> Cape Town
> South Africa
> 
> GoogleTalk : ejbengine
> Skype: ejbengine
> Registered Linux user number 366042
> 
>
-
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 







___ 
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: 
http://mail.yahoo.de

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

Re: jars not being included in compiler classpath

[Geoffrey De Smet]

Yep, but it seems your mixing your main sources and your test sources 
into one dir: /src.

So a normal compile also tries to compile the test sources.
You're better off splitting the sources directories up:
/src/main/java
/src/main/resources
/src/test/java
/src/test/resources

Jeff Mutonho wrote, On 2006-11-14 11:03 AM:

On 11/14/06, Wayne Fay <[EMAIL PROTECTED]> wrote:

Scope test is not included in build classpath. Both "problem" jars are
scoped "test". The others have no scope so they default to "compile".

Wayne



I get  confused by the scope thing.If scope is test , does that mean
the jars will only be used in the test phase of the build lifecycle?

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042


--
With kind regards,
Geoffrey De Smet


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

RE: continuum build project more than once

[Wierschke Robert]

Ok I already suspected this, but what should I use to update the page in
order to see the results. I tried the Show Projects link but it seems
also to trigger another build.

Thanks
robert

-Original Message-
From: Martin Testrot [mailto:[EMAIL PROTECTED] 
Sent: Dienstag, 14. November 2006 08:45
To: continuum-users@maven.apache.org
Subject: Re: continuum build project more than once

Hi,

don't click "refresh" or hit F5 in your browser.
It seems each refresh sends a new build request.

Greetings,
Martin

Wierschke Robert schrieb:
> hi,
>
> why does continuum build my projects multiple times (up to 31) when i
click on build now???
>
>
> robert
>   

Re: jars not being included in compiler classpath

[Jeff Mutonho]

On 11/14/06, Wayne Fay <[EMAIL PROTECTED]> wrote:

Scope test is not included in build classpath. Both "problem" jars are
scoped "test". The others have no scope so they default to "compile".

Wayne



I get  confused by the scope thing.If scope is test , does that mean
the jars will only be used in the test phase of the build lifecycle?

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042

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

jars not being included in compiler classpath

[Jeff Mutonho]

I have a small proof of concept I'm trying to build.In the project's
super pom , I have a dependency to spring specified as

 
 oracle.ldap
 ldapjclnt
 1.0
   
   
 javax.j2ee
 j2ee
 1.3.0
   
  
 org.springframework
 spring
 1.2.3
 test
   
   
 org.apache.log4j
 log4j
 1.2.13
 test
   


However when I run the build I'm getting build failure due to failed
dependencies on the spring-1.2.3.jar and the log4j-1.2.13.jar  files.

A snippet of the log shows that these two jars are not being passed to
the maven-compiler-plugin 's classpath :

[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-compiler-plugin:2.0.1:compile' -->
[DEBUG]   (f) basedir =
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal
[DEBUG]   (f) buildDirectory =
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target
[DEBUG]   (f) classpathElements =
[C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes,
D:\Documents and
Settings\mutonhj\.m2\repository\javax\j2ee\j2ee\1.3.0\j2ee-1.3.0.jar,
D:\Documents and
Settings\mutonhj\.m2\repository\oracle\ldap\ldapjclnt\1.0\ldapjclnt-1.0.jar]
[DEBUG]   (f) compileSourceRoots =
[C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src]
[DEBUG]   (f) compilerId = javac
[DEBUG]   (f) debug = true
[DEBUG]   (f) fork = false
[DEBUG]   (f) optimize = false
[DEBUG]   (f) outputDirectory =
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
[DEBUG]   (f) outputFileName = dev-ep1x-eportal-1.0.0
[DEBUG]   (f) projectArtifact =
za.co.pragmaticus.dev-ep1x.eportal:dev-ep1x-eportal:ejb:1.0.0
[DEBUG]   (f) showDeprecation = false
[DEBUG]   (f) showWarnings = false
[DEBUG]   (f) staleMillis = 0
[DEBUG]   (f) verbose = false
[DEBUG] -- end configuration --
[INFO] [compiler:compile]
[DEBUG] Using compiler 'javac'.
[DEBUG] Source directories:
[C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src]
[DEBUG] Classpath:
[C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
D:\Documents and
Settings\mutonhj\.m2\repository\javax\j2ee\j2ee\1.3.0\j2ee-1.3.0.jar
D:\Documents and
Settings\mutonhj\.m2\repository\oracle\ldap\ldapjclnt\1.0\ldapjclnt-1.0.jar]
[DEBUG] Output directory:
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
[DEBUG] Classpath:
[DEBUG]  
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
[DEBUG]  D:\Documents and
Settings\mutonhj\.m2\repository\javax\j2ee\j2ee\1.3.0\j2ee-1.3.0.jar
[DEBUG]  D:\Documents and
Settings\mutonhj\.m2\repository\oracle\ldap\ldapjclnt\1.0\ldapjclnt-1.0.jar
[DEBUG] Source roots:
[DEBUG]  C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src
Compiling 392 source files to
C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\target\classes
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Compilation failure

.

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[5,24]
package org.apache.log4j does not exist

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[6,43]
package org.springframework.web.servlet.mvc does not exist

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[7,44]
package org.springframework.web.servlet.view does not exist

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[8,39]
package org.springframework.web.servlet does not exist

C:\pragmaticus-sea-ias\eclipse-3.1.2-workspaces\dev-ep1x\eportal\src\za\co\pragmaticus\portal\controllers\ApplicationPDCRegistrationController.java:[10,41]
package org.springframework.beans.factory does not exist


This does not seem to make any sense , because the other 2 jars in my
dependency configuration , namely  ldapjclnt-1.0.jar and
j2ee-1.3.0.jar , are included in the build classpath.

--

Jeff  Mutonho
Cape Town
South Africa

GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042

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

Let Maven wait between tests

[Deluigi Marcus]

Hi 

I am quite desperate: I want to let Maven sleep for a few seconds
between the tests.
I added this ant tasks in the build phase in a previous project and it
worked fine:
-8<-


 
org.apache.maven.plugins
maven-antrun-plugin


 
 
 
 
 
 
 
 
 
 
 


   
   
   wait
   test
   
   run
   
   
   
 


->8-

However, in my new project, this task never gets executed and I just
can't figure out why.
Everything seems the same. If I change the phase from "test" to
"generate-test-sources" I get the first echo task, but not the whole
process. But the effective pom looks fine.

Can anybody give me a hint, what might go wrong?
Is there any other way to let maven wait for a few seconds between the
tests?

Thanks for any help!

Greetings,
Marcus

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

Parent/modules File path compression

[Vincent Beretti]

Hi,
Sometimes a problem appears in M2 with parent and module structure due to
the OS limitation in filepath length.
For example Windows file path can not exceed 255 characters.
But in complex maven 2 structure of parent/modules we can encounter a
problem with that.
I use Eclipse so I have to put my children projects in a flat structure.
Example :
in my filesystem my projects are :

C:/
|-- parentProject/
|-- childprojectA/
|-- childProjectB/

But in maven the structure is as following :

parentProject
|-- childProjectA
|-- childProjectB

So in childProjectX poms, I have to references parent project like this :
../parentProject and the same for modules in
parent

On a very complex structure, I have a path longer than 255 but in fact i
could be compressed to remove ..
for example when maven deletes target dir, it does like this :
delete C:/parentProject/../childProjectA/target
instead it could do
delete C:/childProjectA.
This would reduce the path length in very complex structures.
Could it be possible to do this ?
What do you think about this idea ?
Thanks
Vincent.

tomcat deployer

[Kevin Jackson]

Hi all,

I'm trying to work on a webapp with tomcat and mvn.  I want to be able
to edit a jsp, type mvn tomcat:redeploy and have just the changed jsp
be reloaded, without having to compile/package/deploy

I'm fairly sure that this is possible using a combination of mvn +
tomcat-plugin, but I'm failing the correct incantation test

so far I can do a mvn tomcat:deploy, but this
compiles/filters/packages and takes forever - not good for rapid
development of ui stuff

mvn tomcat:redeploy seems to just redeploy the application that's
already deployed in the CATALINA_HOME/webapps directory, what I need
is some way to configure the plugin to deploy my development directory
as an exploded web application

Thanks in advance for any/all help

Kev

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

RE: [M1] AspectJ with two source trees (main/src & main/test)

[diyfiesta]

Hi,

Thanks for the note, sorry, its probably not very clear (late night sessions
and all that!).

Not sure if its a red hering or not but I have test classes that are
*affected* by the aspects. So, I have a call pointcut on some method (called
A.doSomething) and and before aspect. The test code calls the method
doSomething and so is affected by the aspect.

Running

maven aspectj

creates target/classes which contain the A class, ATest class and the
aspect. Reverse engineering the test class here shows it has the correctly
weaved (is that the right word) aspect code in it.

running 

maven test (which has a pregoal to run the aspectj compiler)

creates target/test-classes and target.test-reports

The test-classes folder here only contains the test class (ATest.class) and
reverse engineering it shows that the aspect was not weaved. So, runing the
test will fail becuase the test is testing that the aspect is being used.

Changing the default maven.test.dest to something like
${maven.build.dir}/classes seems to help but in my real project doesn't
solve it completly.

I have a test project that demonstrates this (if anyone is interested), all
the settings are pretty much default.

I'll keep playing and post my findings here.

Cheers,



Jeff Jensen wrote:
> 
> Are you saying that the test classes in test-classes need a pass by the
> AspectJ compiler, or the test classes do not see the AspectJ compiled
> classes in the classes dir?  (or something else entirely?)
> 
> The fact that the "production" classes compile to target/classes and the
> test classes compile to /target/test-classes seems correct to me (from
> what
> I understand from your emails).  When the tests run, the production code
> is
> also on the classpath, so works well (now there could be some bug in
> that...
> :-).
> 
> 
> -Original Message-
> From: diyfiesta [mailto:[EMAIL PROTECTED] 
> Sent: Monday, November 13, 2006 9:53 AM
> To: users@maven.apache.org
> Subject: Re: [M1] AspectJ with two source trees (main/src & main/test)
> 
> 
> So, looking into this more (and having created a simple example project to
> demonstrate it), it looks like the the aspectj plugin is compiling things
> correctly, its just that the tests are being run from the incorrect place.
> 
> So, for example, the output of the aspectj compilation goes into
> 
> target/classes/...
> 
> but the tests run from a folder called 
> 
> target/test-classes/... 
> 
> which has the compiled test code, but not the aspectj compiled code. So,
> if
> a test is affected by an aspect, it isn't in this folder.
> 
> 
> diyfiesta wrote:
>> 
>> Hi,
>> 
>> Thanks for the note, I tried this but still don't have any luck, for 
>> example, I'm using the convention main/src/java and main/src/test for 
>> my source trees, so adding an src/aspectj folder doesn't really fit 
>> in, if I add it to main/src/aspectj, I get the same problem (and just 
>> for completness, setting it to src/aspectj causes is the same!).
>> 
>> From the plugin's homepage, I didn't get the impression that setting 
>> the soruce directiory to src/aspectj was a requirement more of an 
>> example, and you should be able to set this to whatever your folder 
>> is. Is this not the case?
>> 
>> I think I'll have a go at creating a simple test project that 
>> demonstrates the problem, see if I can get some feedback.
>> 
>> Any other ideas?
>> 
>> Cheers
>> 
>> 
>> Alexandre Touret wrote:
>>> 
>>> Hello,
>>> There are 2 builds : the classes and test classes.
>>> If you specify the aspectsourcedirectory in src/java, aspectj doesn t 
>>> parse any file in src/test. Its the default behaviour I can suggest 
>>> you to put all the aspects file have in ${maven.src.dir}/aspectj (as 
>>> described in the plugin homepage). I suppose this directory is 
>>> accessible in both the build classpaths and test classpath.
>>> 
>>> Hope this helps.
>>> Alexandre
>>> 
>>> Toby Weston wrote:
 Hi Folks,
 [...]
 I've got my source code under main/src and the unit tests under 
 main/test, however I can't get aspectj compiling both. I added this 
 to my project.xml hoping it would pick up both, but it doesn't seem 
 to,,,

main/src/java
main/test/java

 I'm kind of not confident I know the correct process, so may be 
 doing something really silly. I was thinking that the pregoal for 
 compile to run the aspectj compiler would apply my aspects to the 
 code that they affect? After running this though, my unit tests 
 confirm that the aspect isn't applied, and if I reverse engineer the 
 test code, there is no aspect code in there (and there is if I do a 
 normal eclipse aspectj compile).

 So, for some reason, its not applying my aspects to test code in the 
 second source tree... :(

 Cheers,
 Toby

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

RE: Plugin Annotation to control Inheritance

[franz see]

Good day to you, Barrett,

You may want to use the @aggregator on  your mojo. This will mark the goal
it represents as an aggregator. 

Aggregators goals are treated by maven differently than none aggregator.
Simply put, aggregator goals are executed only once and only against the
maven project you invoked your maven command on (root project).
Non-aggregator tasks on the other hand are executed on your root project,
and on all of its modules.

Cheers,
Franz


Barrett.Nuzum wrote:
> 
> Dawn:
> 
> That made just as much sense as it did before.
>  
> false in a  at the
> ParentPom level would cause the plugin to only get run when I install
> ParentPom, and never when I install a ProjectPom.
>  
> I want it run when I install a ProjectPom, and no other times, but I want
> to specify it only *once*.
>  
> The projectPom still has
>
>   
>   
> myPluginGroup
> myArtifactId
>   
>
>  
> as is required for execution, but i want it to get
> false from the configuration in ParentPom and not
> pass the plugin to it's children. Setting standard configuration options
> which are shared but only come into effect when a plugin is explicitly
> executed is what pluginManagement is for, isn't it?
>  
> If it just plain doesn't do that, that's fine. :)
>  
> Barrett
>  
> Barrett Nuzum
> Consultant, Skill Development
> [EMAIL PROTECTED]
> T:  +1 (918) 640 4414
> F:  +1 (972) 789 1340
> 
> 
> Valtech
> 5080 Spectrum Drive Suite 700 West 
> Addison, Texas 75001
> USA
> T: +1 (972) 789 1200
> 
> 
> 
> From: dawn.angelito [mailto:[EMAIL PROTECTED]
> Sent: Sat 11/11/2006 12:19 AM
> To: users@maven.apache.org
> Subject: RE: Plugin Annotation to control Inheritance
> 
> 
> 
> 
> Hi Barrett,
> 
> Yes, that is correct. You should edit the parent POM. I can see that
> you've
> specified the false in
> . Try adding this in the
>  instead.
> 
> The inherited tags are used to merge the parent pom and the child pom
> (though no actual pom file is created, the pom object is created). The
> resulting pom is the one that gets executed. So, if you don't inherit the
> pluginManagement but inherit the plugin, it will still get executed. But
> if
> you don't inherit the plugin, even if you inherit the pluginManagement, it
> will not get executed.
> 
> Hope this makes more sense this time.
> 
> Dawn
> 
> 
> 
> Barrett.Nuzum wrote:
>>
>> Hi Dawn (and all).
>> 
>> We have 20-30 projects that share one, single parent POM.
>> Each project has usually 7 modules in it.
>> 
>> To clarify:
>>  ParentPom (1)
>>  \-- ProjectPom (1..30)
>>   \-- ModulePom (1..7, each)
>>
>> I did specify false in pluginManagement in the
>> Parent POM, but it did not seem to work.
>> 
>> Only hardcoding inherited in each project POM seemed to have any effect
>> whatsoever.
>> 
>> That doesn't answer the second part of my question, though -- why can't I
>> configure the plugin the way the plugin API seems to be designed to
>> intend?
>> 
>> Barrett
>> 
>> Barrett Nuzum
>> Consultant, Skill Development
>> [EMAIL PROTECTED]
>> T:  +1 (918) 640 4414
>> F:  +1 (972) 789 1340
>>
>>
>> Valtech
>> 5080 Spectrum Drive Suite 700 West
>> Addison, Texas 75001
>> USA
>> T: +1 (972) 789 1200
>>
>> 
>>
>> From: dawn.angelito [mailto:[EMAIL PROTECTED]
>> Sent: Fri 11/10/2006 1:15 AM
>> To: users@maven.apache.org
>> Subject: Re: Plugin Annotation to control Inheritance
>>
>>
>>
>>
>> Hi Barrett,
>>
>> I'd like to clarify if you're referring to 20-30 submodules or 20-30
>> projects that each has a parent POM? For the former, just specify
>> false to the parent POM. But if you have 20-30
>> different projects, I suggest that you create another project and include
>> all these as subprojects. Afterwards, do the same thing, specify
>> false to the parent POM.
>>
>> Hope this helps.
>>
>> Dawn
>>
>>
>> Barrett.Nuzum wrote:
>>>
>>> Hi Maven mavens.
>>>
>>> OK -- my turn for a query.
>>> I've written a plugin.   I do *not* want that plugin to be inherited by
>>> children poms.
>>>
>>> Our design is like this:
>>> ParentPom
>>> \-- ProjectPom
>>>  \-- ModulePom (1..n)
>>>
>>> I want my plugin to be executed by the ProjectPom but not seen by the
>>> ModulePoms.
>>>
>>> I can do this in XML in the POM by specifying
>>> false
>>> in ProjectPom.
>>> The problem is that we have 20-30 ProjectPoms for different projects and
>>> do not want to violate the DRY principle.
>>> I *cannot* seem to do so by specifying that in the pluginManagement
>>> section in ParentPom.
>>> That would be sufficient.
>>>
>>> Even more frustrating, it seems plugin.xml has an 
>>> item --
>>> I can't seem to put an annotation on the Mojo which is read by Maven
>>> which
>>> causes this to flip from true to false. @inheritedByDefault false should
>>> be enough, I would think! Why every plugin.xml entity doesn't have an
>>> associated annotation is beyond

Servlet not initialized error

[Nik Gonzalez]

Hi all,

I'm running continuum 1.0.3 on a linux server. After restarting 
continuum, I always get Servlet not initialized error on my browser. 
Whenever this happens, the only solution I could find is to reinstall a 
fresh copy of continuum and load all my projects again.


TIA
Nik

Plugin Test Harness and expression

[Emmanuel Hugonnet]

Hi,
I have a quite simple plugin working correctly but when I try to test it 
the expression is not evaluated. I am using :


 org.apache.maven.shared
 maven-plugin-testing-harness
 1.0-beta-1

On the doc on codehaus they talk about 
"StubResolverExpressionEvaluator" which seems to help resolve this issue 
but I don't see any example. When I look at the unit test for expression 
evaluation on svn I don't see anything specific to be done.

What am I missing ?
Thanks,
Emmanuel

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