RE: Pass classpath to ant
You might try the "maven ant" goal. It creates a build.xml file that allows ant to build your project. > -Original Message- > From: Mitch Mattek [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 26, 2004 2:47 PM > To: [EMAIL PROTECTED] > Subject: Pass classpath to ant > > Hey, > > I'm trying to slowly migrate our build system to maven. > > As step one, I'm just trying to use the maven jar dependency thing to > download jar's then shell to ant scripts which have everything happening > correctly. > > I have a custom plugin and am trying to do this > > > cdp antbuild > adding the classpath > > > >target="all"> > >refid="maven.dependency.classpath"/> > > > > > > I got the snippet above from the java:compile plugin, but I get a message > that "maven.dependency.classhpath" is undefined. > > The way we build now is, we have a large bat file which builds the > classpath > for ant and includes it when it launches ant. > > > > > - > 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: Is there a way to separate maven's repository from my reposit ory?
> -Original Message- > From: Courtney, Craig [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 26, 2004 10:32 AM > To: Maven Users List > Subject: RE: Is there a way to separate maven's repository from my reposit > ory? > > It is prudent to pay attention to this for internal only software as well. Good advice. > > How do you disable the local repository? Not sure. More knowledgeable folks than me have already said there really isn't one. I just ran a dist:build on my project and no libraries were included in the zip or tar.gz files. I think one might be able to write a postGoal for dist:build that jar'd the libraries referenced in your project.xml. Maybe then a separate remote repository wouldn't even have to be created. I also just commented out a dependency in my project.xml and tried to re-run a clean then a dist:build. The dist:build failed due to that dependency. The means that the classpath for compilation, unit tests, etc are based on the project.xml and not on everything that resides in the repository. It would seem that control over the dependencies in the project.xml = total control over the libraries used for your build. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Is there a way to separate maven's repository from my reposit ory?
> -Original Message- > From: Courtney, Craig [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 26, 2004 10:02 AM > To: Maven Users List > Subject: RE: Is there a way to separate maven's repository from my reposit > ory? > > Because the code I'm writing is internal and proprietary in nature. Using > maven to build it generates no licensing obligations on my code. Linking > against any of the libraries that maven uses does generate licensing > obligations on my code. Doh! That makes sense. Our organization doesn't distribute software, thus we don't worry as much about such issues. > > We are looking at setting up an interanl repository where all of our > shared libraries will reside. This will allow us control and tracking > over licensing. It would be against company policy to use any libraries > outside our central repository while writing your code. The build tool > should have no requirements about what's in my repository it should only > be about what my code needs. It sounds like you might already be doing this, or have already determined this wouldn't work, but if you used the maven.repo.local property to point to maven's build repository and maven.repo.remote to point to an internal repository that housed only libraries you use and can successfully license, then wouldn't solve most of the issue? I guess it would still be possible for a developer to use a Maven dependency, but his folly would get exposed when you only allowed the remote jars to be included in a distribution. Take care, Maury - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Is there a way to separate maven's repository from my reposit ory?
> -Original Message- > From: Courtney, Craig [mailto:[EMAIL PROTECTED] > Sent: Thursday, August 26, 2004 9:46 AM > To: Maven Users List > Subject: RE: Is there a way to separate maven's repository from my > repository? > > That's exactly what I want. I want maven to be able to download what it > needs... but it's repository for execution of the tool should be different > than the repository I use for my builds. Doesn't seem to be a way to do > this. > > Craig Hi, Craig, Doesn't Maven's use imply "certification" of the libraries it uses? In other words, why would you approve Maven's use, and thus its dependencies, and not certify those dependencies for use in other ways? I am very new to Maven and may not understand your issue at all, but I run Maven on a server with no internet access. I, somewhat tediously, downloaded all the jars Maven needed to a local repository and then manually added dependencies from my project. If my organization dictated that there was to be only one repository, then the only way for any other developer to add a library would be to go through whatever process we set up to get one manually added. Thoughts? Maury - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: update-project
> -Original Message- > From: Christopher Haskins [mailto:[EMAIL PROTECTED] > Sent: Wednesday, August 25, 2004 8:39 AM > To: [EMAIL PROTECTED] > Subject: scm:update-project > > I have left most things to use the default setting, so when I do a > scm:checkout-project it checks out the source files into the 'checkouts' > directory under the /target. I'm trying to get maven to do a > nightly build and I want to use 'scm:update-project' to update the > source before I do a build. This fails as I run it from the > and it can't see the source files in the checkouts dir so comes back > with a message; [cvs] cvs [update aborted]: there is no version here; > run 'cvs checkout' first. > > > > What is the best practice to overcome this problem? > I don't know if it's a best practice, but you can set the property: maven.scm.checkout.dir to the directory you need. Take a look at: http://maven.apache.org/reference/plugins/scm/properties.html HTH, Maury - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Copy without overwriting.
You can use an ant "Selector". Try something like this: Take a look at: http://ant.apache.org/manual/CoreTypes/selectors.html > -Original Message- > From: Ryan Owens [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 17, 2004 10:54 AM > To: Maven Users List > Subject: Copy without overwriting. > > Hello all. > I need to copy a set of files to a directory, but not overwrite a file > if it exists. > In other words I only want to copy files that have not been previously > copied. > > this is what I have in my maven goal now: > > > > > > > > The ant copy task's 'overwrite' attribute only prevents a copy if the > destination file is newer, so this snippet doesn't work. > I need to prevent a copy if the destination file exists at all. > This may be more of an ant question but I've scoured all the ant > resources I can find and I'm thinking I need to use jelly or something. > Is there a better way to copy in Maven than using the ant copy task? > > Thanks for your time and help! > > > - > 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: Error in generating site on HP-UX
Just a lurking newbie myself, but... > -Original Message- > From: Paterline, David L. [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 17, 2004 8:24 AM > To: 'Maven Users List' > Subject: RE: Error in generating site on HP-UX > Is anyone successfully using Maven v. 1.0-rc2 on HP-UX B.11.11? I'm not (I'm using Maven v.1.0-rc3 on HP-True64 Unix), but the error you speak of sounds eerily similar to ones I've run into. > > Does anyone have any idea what the cryptic error message "Could not parse > Jelly script" means, I somehow did a combination of un-tar's and unzips that got me DOS line endings on some of my files and those files couldn't be read on our HP-Tru64 5.1A box. Possible here? You can look for the "plugin.jelly" file in $HOME/.maven/plugins/xxx where xxx is the plugin for the goal you are executing (I'm guessing maven-site-plugin-x.x in this case?) > or how to understand what the parser is choking on in > source file, since no source file line number is referenced? I'm not a Jelly expert but it is a superset of ant. Ant tasks are often defined in the *.jelly files in their own namespace like so: This means that normal ant echo tasks could be used to determine where in the file you get to... something like this: Just after test:test goal. But it doesn't sound like your script is even being executed at all at this point. > > Thanks. > You're welcome. I hope this helps. For what it's worth, v 1.0rc3 was a big step forward for me in getting the whole thing to work. Cheers, Maury - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: NoSuchMethodError running Clover with Maven
J.B. wrote: > Oh it /does/, it /does/. You can see the fruit of my labor and your help > at diasparsoftware.com/toolkit. I'll check it out. It's definitely the blind leading in this case but I'm glad I could help. Good Luck! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: NoSuchMethodError running Clover with Maven
Hi, J.B.,
I had a similar issue when I first tried to get Maven working. In my case,
it had to do with Class Loaders and which ones are loading what. What
finally fixed it for me was to put the junit-3.8.1.jar in my
$MAVEN_HOME/bin/forehead.conf file in the root section like so:
[root]
${tools.jar}
${maven.home}/lib/commons-grant-1.0-beta-4.jar
${maven.home}/lib/ant-1.5.3-1.jar
${maven.home}/lib/endorsed/xml-apis-1.0.b2.jar
${maven.home}/lib/ant-optional-1.5.3-1.jar
${maven.home}/lib/endorsed/xerces-2.4.0.jar
${maven.home}/lib/commons-logging-1.0.3.jar
${maven.home}/lib/log4j-1.2.8.jar
/u01/home/oracle/fhrcc/lib/junit-3.8.1.jar
I'm not knowledgeable at all about root Class Loaders or Forehead, but I
found some similar issues in the Maven Users Mailing List Archive (on
http://maven.apache.org under Project Info. It's a little tedious to
search, but there is a lot of good info-- all pertinent to Maven.)
Another place I didn't take advantage of in my first few weeks was the
documentation for the plugins. (Again on the maven site under reference and
then plugins. Click on the "Maven Plugins" link under the heading "Plugins
Hosted by Maven" and you'll find tons (pounds?) of good info.)
Hope this helps,
Maury
> -Original Message-
> From: J. B. Rainsberger [mailto:[EMAIL PROTECTED]
> Sent: Monday, June 07, 2004 9:02 AM
> To: Maven Users List
> Subject: NoSuchMethodError running Clover with Maven
>
> When I run the goal on its own, all tests pass.
>
> When I run the goal and it runs , I get this in
> every test:
>
> java.lang.NoSuchMethodError:
> com.cortexeb.tools.clover.S.getRecorder([CJI)Lcom/cortexeb/tools/clover/n;
>
> Google told me nothing. Help!
>
> Thanks.
> --
> J. B. Rainsberger,
> Diaspar Software Services
> http://www.diasparsoftware.com :: +1 416 791-8603
> Let's write software that people understand
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Maven 1.0 RC3 released
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Thursday, May 20, 2004 10:27 AM > To: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] > Subject: [ANN] Maven 1.0 RC3 released > > The Maven team is pleased to announce the Maven 1.0-rc3 release! > I tip my hat to all the developers. I have expressed on this list some frustration in learning to work with Maven. Several of you helped and I'm grateful. With this release, I finally broke the code and I'm impressed with what Maven enables one to do in managing and communicating project information. Good Job, and Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compile from CVS
Thanks, Brett. Like I've said before, I'm still learning my way around cvs. Two things: 1. Vincent made a zip of rc3 for me which I plan to try today. 2. There was another consistent error on the test:test goal, which I got around by setting maven.test.skip=true. I'm not sure if this error is related to the one below. I'll let you guys know how the rc3 zip works, Maury > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 04, 2004 8:30 PM > To: 'Maven Users List' > Subject: RE: Compile from CVS > > Right - thanks. > > You don't need to build RC3 to fix this - just need to rebuild the xdoc > plugin. I'll attempt to cut a release of that sooner than RC3. > > - Brett > > > -Original Message- > > From: Jarrell, Maury [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, 4 May 2004 11:03 PM > > To: 'Maven Users List' > > Subject: RE: Compile from CVS > > > > > > > -Original Message- > > > From: Brett Porter [mailto:[EMAIL PROTECTED] > > > Sent: Monday, May 03, 2004 6:12 PM > > > To: 'Maven Users List' > > > Subject: RE: Compile from CVS > > > > > > I'm curious about these RC2 site:generate problems? > > > > Hi, Brett, > > You can look in the archives for this list. I started a > > thread on Apr 21 with a subject of "Problem with > > site:generate goal in *very* basic project" > > > > The error I reported was (in part): > > # Validating team-list.html > > # maven-linkcheck-plugin:report-real: > > # [echo] Generating > > /u01/home/oracle/maven1/target/docs/linkcheck.html > > # from /u01/home/oracle/maven1/target/linkcheck/docs/linkcheck.xml > > # > > # BUILD FAILED > > # File.. > > # > > file:/u01/home/oracle/.maven/plugins/maven-xdoc-plugin-1.6/plu > gin.jelly > # Element... j:include > # Line.. 345 > # Column 54 > # null:-1:-1: Could not parse Jelly script > # Total time: 4 minutes 34 seconds > # Finished at: Wed Apr 21 10:06:02 CDT 2004 > # > # This appears to be a part of the dependent goal "xdoc:jelly-transform" > > > Emmanuael Venisse's response to me was: > > #It's a known bug in xdoc plugin that was fixed in cvs. > # > #Emmanuel > > Hope this helps, > Maury > > > - > 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: Compile from CVS
> -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: Monday, May 03, 2004 6:12 PM > To: 'Maven Users List' > Subject: RE: Compile from CVS > > I'm curious about these RC2 site:generate problems? Hi, Brett, You can look in the archives for this list. I started a thread on Apr 21 with a subject of "Problem with site:generate goal in *very* basic project" The error I reported was (in part): # Validating team-list.html # maven-linkcheck-plugin:report-real: # [echo] Generating /u01/home/oracle/maven1/target/docs/linkcheck.html # from /u01/home/oracle/maven1/target/linkcheck/docs/linkcheck.xml # # BUILD FAILED # File.. # file:/u01/home/oracle/.maven/plugins/maven-xdoc-plugin-1.6/plugin.jelly # Element... j:include # Line.. 345 # Column 54 # null:-1:-1: Could not parse Jelly script # Total time: 4 minutes 34 seconds # Finished at: Wed Apr 21 10:06:02 CDT 2004 # # This appears to be a part of the dependent goal "xdoc:jelly-transform" Emmanuael Venisse's response to me was: #It's a known bug in xdoc plugin that was fixed in cvs. # #Emmanuel Hope this helps, Maury - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Compile from CVS
I deserve that. I was venting some frustration is a not-so-helpful way. The truth is that I'd love to participate if I can ever get Maven to successfully do a "site:generate". Unfortunately, I was told rc2 won't work because it there are some bugs with some goals that site:generate depends on. I'm not familiar with CVS so I'm on a learning curve there, too. Add to that the fact that I'm behind a firewall and the whole thing has been a succession of roadblocks for me. I'll stop whining and keep working... Thanks for your help, Maury > -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, May 03, 2004 2:28 PM > To: 'Maven Users List' > Subject: RE: Compile from CVS > > Building from HEAD or branch HEAD is reserved to power-users/developers. > I'd suggest you use the latest released version (rc2). Otherwise, stop > whining and start participating :-) > > Thanks > -Vincent > > > -Original Message- > > From: Jarrell, Maury [mailto:[EMAIL PROTECTED] > > Sent: 03 May 2004 20:50 > > To: 'Maven Users List' > > Subject: RE: Compile from CVS > > > > Amen. I think I was lulled into believing it's a more mature project > than > > it is by all the "Built With Maven" graphics on so many Jakarta > projects. > > > > > -Original Message- > > > From: Miguel Griffa [mailto:[EMAIL PROTECTED] > > > Sent: Monday, May 03, 2004 1:54 PM > > > To: Maven Users List > > > Subject: Re: Compile from CVS > > > > > > Hi > > > I'm getting the same problem there, > > > I just run > > > cvs up -r MAVEN-1_0-BRANCH -d -C > > > on maven and maven-plugins checkouts... > > > I's so happy with maven that I want to start building and > contributing > > > (if I can) but debugging the bootstrap seems a bit difficult fo rthe > > > first task.. > > > > > > [exec] __ __ > > > [exec] | \/ |__ _Apache__ ___ > > > [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > > > [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT > > > > > > [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] > > > [exec] at > > > > > > org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip > tH > > > ousings(GoalToJellyScriptHousingMapper.java:254) > > > [exec] at > > > > > > org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: > 64 > > > 5) > > > [exec] at > > > > > > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 > ) > > > [exec] at > > > org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) > > > [exec] at org.apache.maven.cli.App.doMain(App.java:485) > > > [exec] at org.apache.maven.cli.App.main(App.java:1208) > > > [exec] at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native > > > Method) > > > [exec] at > > > > > > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav > a: > > > 39) > > > [exec] at > > > > > > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor > Im > > > pl.java:25) > > > [exec] at java.lang.reflect.Method.invoke(Method.java:324) > > > [exec] at > com.werken.forehead.Forehead.run(Forehead.java:551) > > > [exec] at > com.werken.forehead.Forehead.main(Forehead.java:581) > > > > > > > > > Arnaud Heritier wrote: > > > > > > > > > > > > > > >>-Message d'origine- > > > >>De : Miguel Griffa [mailto:[EMAIL PROTECTED] > > > >>Envoyé : lundi 3 mai 2004 20:01 > > > >>À : Maven Users List > > > >>Objet : Re: Compile from CVS > > > >> > > > >>Hi I checked out the HEAD > > > >>But I'm used to compile without problems HEADs (from open source > > > >>projects...) > > > >>I posted all info at jira here (included the ouput of ant -d ) > > > >> > > > >>http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 > > > >> > > > >>Shouldn't the head version compile? > > > >> > > > >> > > > > >
RE: Compile from CVS
Thanks! I'll try that. I really appreciate your efforts. Ditto to Arnaud who just offered the same to me offline. Now I have to go erase the mean things I wrote about you guys off the bathroom wall... ;-) Thanks again, Maury > -Original Message- > From: Vincent Massol [mailto:[EMAIL PROTECTED] > Sent: Monday, May 03, 2004 4:21 PM > To: 'Maven Users List' > Subject: RE: Compile from CVS > > Ok, here's some help for you... :-) > > Follow these steps: > > 1/ remove your .maven/plugins directory > 2/ grab http://cvs.apache.org/~vmassol/maven-rc3-20040503.zip and unzip > it > 3/ ensure your MAVEN_HOME variable points to the place you've unzipped > it > 4/ ensure MAVEN_HOME/bin is in your classpath > 5/ try it > > Hope it helps, > -Vincent > > > -Original Message- > > From: Jarrell, Maury [mailto:[EMAIL PROTECTED] > > Sent: 03 May 2004 23:01 > > To: 'Maven Users List' > > Subject: RE: Compile from CVS > > > > I deserve that. I was venting some frustration is a not-so-helpful > way. > > The truth is that I'd love to participate if I can ever get Maven to > > successfully do a "site:generate". Unfortunately, I was told rc2 > won't > > work > > because it there are some bugs with some goals that site:generate > depends > > on. I'm not familiar with CVS so I'm on a learning curve there, too. > Add > > to > > that the fact that I'm behind a firewall and the whole thing has been > a > > succession of roadblocks for me. I'll stop whining and keep > working... > > Thanks for your help, > > Maury > > > > > -Original Message- > > > From: Vincent Massol [mailto:[EMAIL PROTECTED] > > > Sent: Monday, May 03, 2004 2:28 PM > > > To: 'Maven Users List' > > > Subject: RE: Compile from CVS > > > > > > Building from HEAD or branch HEAD is reserved to > power-users/developers. > > > I'd suggest you use the latest released version (rc2). Otherwise, > stop > > > whining and start participating :-) > > > > > > Thanks > > > -Vincent > > > > > > > -Original Message- > > > > From: Jarrell, Maury [mailto:[EMAIL PROTECTED] > > > > Sent: 03 May 2004 20:50 > > > > To: 'Maven Users List' > > > > Subject: RE: Compile from CVS > > > > > > > > Amen. I think I was lulled into believing it's a more mature > project > > > than > > > > it is by all the "Built With Maven" graphics on so many Jakarta > > > projects. > > > > > > > > > -Original Message- > > > > > From: Miguel Griffa [mailto:[EMAIL PROTECTED] > > > > > Sent: Monday, May 03, 2004 1:54 PM > > > > > To: Maven Users List > > > > > Subject: Re: Compile from CVS > > > > > > > > > > Hi > > > > > I'm getting the same problem there, > > > > > I just run > > > > > cvs up -r MAVEN-1_0-BRANCH -d -C > > > > > on maven and maven-plugins checkouts... > > > > > I's so happy with maven that I want to start building and > > > contributing > > > > > (if I can) but debugging the bootstrap seems a bit difficult fo > rthe > > > > > first task.. > > > > > > > > > > [exec] __ __ > > > > > [exec] | \/ |__ _Apache__ ___ > > > > > [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > > > > > [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT > > > > > > > > > > [exec] com.werken.werkz.NoSuchGoalException: No goal > [clean] > > > > > [exec] at > > > > > > > > > > > > > org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScrip > > > tH > > > > > ousings(GoalToJellyScriptHousingMapper.java:254) > > > > > [exec] at > > > > > > > > > > > > > org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java: > > > 64 > > > > > 5) > > > > > [exec] at > > > > > > > > > > > > > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597 > > > ) > > > > > [exec] at > > > > > org.apache.maven.MavenSession.attai
RE: Compile from CVS
Amen. I think I was lulled into believing it's a more mature project than it is by all the "Built With Maven" graphics on so many Jakarta projects. > -Original Message- > From: Miguel Griffa [mailto:[EMAIL PROTECTED] > Sent: Monday, May 03, 2004 1:54 PM > To: Maven Users List > Subject: Re: Compile from CVS > > Hi > I'm getting the same problem there, > I just run > cvs up -r MAVEN-1_0-BRANCH -d -C > on maven and maven-plugins checkouts... > I's so happy with maven that I want to start building and contributing > (if I can) but debugging the bootstrap seems a bit difficult fo rthe > first task.. > > [exec] __ __ > [exec] | \/ |__ _Apache__ ___ > [exec] | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ > [exec] |_| |_\__,_|\_/\___|_||_| v. 1.0-rc3-SNAPSHOT > > [exec] com.werken.werkz.NoSuchGoalException: No goal [clean] > [exec] at > org.apache.maven.plugin.GoalToJellyScriptHousingMapper.resolveJellyScriptH > ousings(GoalToJellyScriptHousingMapper.java:254) > [exec] at > org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java:64 > 5) > [exec] at > org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:597) > [exec] at > org.apache.maven.MavenSession.attainGoals(MavenSession.java:266) > [exec] at org.apache.maven.cli.App.doMain(App.java:485) > [exec] at org.apache.maven.cli.App.main(App.java:1208) > [exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native > Method) > [exec] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java: > 39) > [exec] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorIm > pl.java:25) > [exec] at java.lang.reflect.Method.invoke(Method.java:324) > [exec] at com.werken.forehead.Forehead.run(Forehead.java:551) > [exec] at com.werken.forehead.Forehead.main(Forehead.java:581) > > > Arnaud Heritier wrote: > > > > > > >>-Message d'origine- > >>De : Miguel Griffa [mailto:[EMAIL PROTECTED] > >>Envoyé : lundi 3 mai 2004 20:01 > >>À : Maven Users List > >>Objet : Re: Compile from CVS > >> > >>Hi I checked out the HEAD > >>But I'm used to compile without problems HEADs (from open source > >>projects...) > >>I posted all info at jira here (included the ouput of ant -d ) > >> > >>http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1253 > >> > >>Shouldn't the head version compile? > >> > >> > > > >Ok Miguel. > >In theory the Head must compile but in reality I'm not sure that all > >modifications are done in the two branches. > >The dev team is trying to produce a 1.0 RC3 (Final we hope) as soon as > >possible. > >Waiting for this, I advise you to get the branch : MAVEN-1_0-BRANCH > >We are sure that this one compile. > > > >I will try to find what the problem is with the HEAD. > > > > > >#Arnaud. > > > > > >- > >To unsubscribe, e-mail: [EMAIL PROTECTED] > >For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > -- > > Miguel Griffa > Software Architect > Technisys.NET "The First Digital e-nabler" > Transactional Solutions > > Miami +1 305 357 8109 > Madrid +34 915 726 763 > Buenos Aires: +54 11 43227100 > [EMAIL PROTECTED] > http://www.technisys.net > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Problem with site:generate goal in *very* basic project
Thanks for your prompt reply. I'll re-try with the cvs version. Maury > -Original Message- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 21, 2004 1:02 PM > To: Maven Users List > Subject: Re: Problem with site:generate goal in *very* basic project > > It's a known bug in xdoc plugin that was fixed in cvs. > > Emmanuel > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with site:generate goal in *very* basic project
I've been working on and off for a couple of weeks trying to figure out Maven and see if it will work for us. As the documentation says, the biggest bang for our buck in moving to Maven is the automatic site generation. I initially tried to generate a site based on our java sources, and I ran into a roadblock when it failed trying to run the tests. ( See my email to this list from 8 Apr 2004: test:test goal can't find JUnitTask ) I tried to start from scratch: I deleted my local repository. I reinstalled the binary version of Maven-1.0-rc2. I started in a fresh directory and ran "maven genapp" using the "-Dpackage=" switch to specify my package. I *still* got the error in the test:test goal when I ran "maven site:generate" I added "maven.test.skip=true" to my project.properties and tried "maven jar". This worked! Then I tried "maven site:generate" again. This time it fails consistently with the following error: ... Validating team-list.html maven-linkcheck-plugin:report-real: [echo] Generating /u01/home/oracle/maven1/target/docs/linkcheck.html from /u01/home/oracle/maven1/target/linkcheck/docs/linkcheck.xml BUILD FAILED File.. file:/u01/home/oracle/.maven/plugins/maven-xdoc-plugin-1.6/plugin.jelly Element... j:include Line.. 345 Column 54 null:-1:-1: Could not parse Jelly script Total time: 4 minutes 34 seconds Finished at: Wed Apr 21 10:06:02 CDT 2004 This appears to be a part of the dependent goal "xdoc:jelly-transform" My goal with this effort was to stay as close to a clean install/project and as close to the docs as I could. Any help would be appreciated. Thanks, Maury - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: test:test goal can't find JUnitTask
Dan Washusen wrote: > I found that I needed the below dependancy in my project.xml file: > > > junit > junit > 3.8.1 > > > to run my junit tests... Thanks for the response. I have that dependency, and added the ant dependencies as follows just in case: junit junit 3.8.1 ant ant 1.5.3-1 ant ant-optional 1.5.3-1 I still get the same error. This is a blank project generated by the genapp goal. This is a clean install (AFAIK) of maven 1.0-rc2. I'm stumped. Two general questions: 1. Does anyone else use this goal? (test:test) 2. If so, did you build from sources? >From what I can read in the docs, this is a basic operation for maven, and I've somehow messed it up, but I can't see how. I'd appreciate any help. Thanks, Maury - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: test:test goal can't find JUnitTask
Since I wrote this first message, I found the plugin.jelly script in $HOME/.maven/plugins/maven-test-plugin-1.5/plugin.jelly and added a line to echo the classpath. The classpath has the ant-optional-1.5.3-1.jar, but the task can't see the JUnitTask. Is Jelly referencing a different classpath? The output is below. I'd appreciate any nudge in the right direction. Thanks, Maury $ maven test:test __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc2 build:start: java:prepare-filesystem: java:compile: [echo] Compiling to $HOME/fhrcc-java/target/classes java:jar-resources: test:prepare-filesystem: test:test-resources: test:compile: test:test: [echo] Here we are. [echo] $HOME/.maven/repository/mail/jars/mail.jar:$HOME/.maven/repository/oro/jars/ oro-2.0.8.jar:$HOME/.maven/repository/commons-net/jars/commons-net-1.1.0.jar :$HOME/.maven/repository/oracle/jars/classes111.zip:$HOME/.maven/repository/ log4j/jars/log4j-1.2.8.jar:$HOME/.maven/repository/activation/jars/activatio n.jar:$HOME/.maven/repository/junit/jars/junit-3.8.1.jar:$HOME/.maven/reposi tory/jtds/jars/jtds-0.5.1.jar:$HOME/.maven/repository/bsh/jars/bsh-2.0b1.jar :$HOME/.maven/repository/ant/jars/ant-1.5.3-1.jar:$HOME/.maven/repository/an t/jars/ant-optional-1.5.3-1.jar BUILD FAILED File.. file:$HOME/.maven/plugins/maven-test-plugin-1.5/plugin.jelly Element... taskdef Line.. 108 Column 9 taskdef class org.apache.tools.ant.taskdefs.optional.junit.JUnitTask cannot be found Total time: 25 seconds Finished at: Tue Apr 06 16:44:37 CDT 2004 $ > -Original Message----- > From: Jarrell, Maury [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 06, 2004 9:11 AM > To: Maven Users List > Subject: test:test goal can't find JUnitTask > > The test:test goal can't find the JUnitTask. > > I think it might have to do with the fact that I have ant 1.6.1 installed. > Maven 1.0-rc2 seems to rely on ant 1.5.3-1. In 1.5.3-1 the JUnitTask is > in > optional.jar. In ant-1.6.1 it is in ant-junit.jar. > > I find the ant-optional-1.5.3-1.jar in $MAVEN_HOME/lib. It is also in > $HOME/.maven/repository/ant/jars > > I've tried unsetting my other ANT_HOME, but still get the same error. Any > ideas? > > > - > 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]
test:test goal can't find JUnitTask
The test:test goal can't find the JUnitTask. I think it might have to do with the fact that I have ant 1.6.1 installed. Maven 1.0-rc2 seems to rely on ant 1.5.3-1. In 1.5.3-1 the JUnitTask is in optional.jar. In ant-1.6.1 it is in ant-junit.jar. I find the ant-optional-1.5.3-1.jar in $MAVEN_HOME/lib. It is also in $HOME/.maven/repository/ant/jars I've tried unsetting my other ANT_HOME, but still get the same error. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: easy way to 'add' my own jars?
I am in no way an expert. In fact, I asked basically this same question
yesterday. (RE: "Dependencies and the local Repository" in the archive) I'm
going to try an answer and let folks correct me.
There are some ways to get around the dependency thing. For example, Henry
Isidro offered:
"Hi. I don't know if this will help but if you already have a copy of the
jar dependency that you need, you can override Maven trying to download
it from the central repository by setting the property
maven.jar.override to "on". Then you can set explicit paths of the
dependency by setting the property maven.jar.{artifactID} to the path of
the jar. You can place this in a project.properties file or a
build.properties file."
There were other great tips as well. My understanding, though, is that you
can also set up your own site remote repository (another idea offered by
Lester Ward) and let Maven download it from there. For one project, this is
probably of no benefit, but for one project neither is Maven (IMHO). The
real benefit is that all your Java efforts can access that resource from the
site repository and then there is a big benefit.
Just some thoughts,
Maury
> -Original Message-
> From: gabor [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 06, 2004 7:33 AM
> To: [EMAIL PROTECTED]
> Subject: easy way to 'add' my own jars?
>
> hi,
>
> for now, i have been using ant to build my java program.
>
> now i am trying to build it with maven.
>
> i simply have a directory, witha a 'src' and a 'lib' subdirectory.
> the source code is in 'src', the needed jar files are in 'lib'.
>
> i understand that maven likes to do it the other way, so that i specify
> the probablyopensource jars i want to use (xerces-4 or whatever), and he
> will fetch them for me, but in my case, most of the jars can't be found
> on the net (either in-house created jar libraries, or modified
> opensource jars and so on).
>
> i understand, that i could probably do the following:
> create a subdirectory in my homedir/.maven, like 'fake/jars', put all
> the jars here, and add a lot of these depencendy stuff into the project
> xml.
>
> but is this the only way???
>
> i mean, for every jar file i have to add
>
>
> xyz
> klm
> 1
> http://www.qwerty.com
>
> ?
>
> or is it at least enough to say:
> mycustom.jar
>
> ?
>
> or what should i do?
>
> thanks,
> gabor
>
>
> -
> 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: Dependencies and the local repository
Kevin, Henry,
Thanks for your tips. Maven is cool, I'm just having trouble wrapping my
mind around the repository concept for some reason.
Thanks,
Maury
> -Original Message-
> From: Kevin Hagel [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 06, 2004 4:21 AM
> To: Maven Users List
> Subject: Re: Dependencies and the local repository
>
> if you're using mail.jar you can dispense with the
> 1.3 completely, will in fact be ignored if
> the tag is used.
>
> the tag allows the use of un-versioned packages. You can use
> , ... I even put my JBoss .SAR file in my local repository,
> stored it in a sars subdirectory. I was able to specify
> mysar.sar and it worked.
>
> Henry Isidro wrote:
>
> > Jarrell, Maury wrote:
> >
> >> Forgive me for asking what must be a very basic question. I've
> >> searched the
> >> Maven site and scoured the archives for this list and haven't found an
> >> answer.
> >>
> >> I have a simple java project defined in an Ant file. The
> >> dependencies for
> >> my current project are in jars in the ${basedir}/lib directory. I've
> >> configured Ant to include in the classpath whatever jars it finds in
> >> that
> >> lib directory.
> >>
> >> I'm trying to duplicate this functionality with Maven, and I've hit a
> >> roadblock. I have jars that don't conform to Maven's idea of a
> standard
> >> name. An example would be the mail.jar from Sun's site. I use it.
> >> I tried
> >> a dependency entry in my project.xml as follows:
> >>
> >>
> >> mail
> >> mail
> >> 1.3
> >> mail.jar
> >>
> >>
> >> I tried putting the jar in ${HOME}/.maven/repository/jars, but it
> wasn't
> >> found. Then I tried to follow the format in the repository and made a
> >> directory structure as follows:
> >>
> >> $HOME/.maven/repository/mail/jars/mail.jar
> >>
> >> That appears to work, but is that what Maven expects me to do for
> >> each jar
> >> file? This seems like a lot of work for jars that will never be
> >> downloaded
> >> from a remote repository anyway.
> >>
> >> This all brings me to the fact that I don't grasp the remote repository
> >> concept. Is there 1 remote repository and it's global to the world?
> >> I went
> >> to http://www.imbiblio.org/maven and looked at the repository there.
> It
> >> seems small if it's supposed to be the global parking spot for Maven
> >> projects world-wide.
> >>
> >> Please forgive my misunderstanding,
> >> Maury
> >>
> >>
> >>
> > Hi. I don't know if this will help but if you already have a copy of
> > the jar dependency that you need, you can override Maven trying to
> > download it from the central repository by setting the property
> > maven.jar.override to "on". Then you can set explicit paths of the
> > dependency by setting the property maven.jar.{artifactID} to the path
> > of the jar. You can place this in a project.properties file or a
> > build.properties file.
> >
> > Anyway, hope this helps.
> >
> > Henry S. Isidro
> >
> > -
> > 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: Dependencies and the local repository
> -Original Message- > From: Lester Ward [mailto:[EMAIL PROTECTED] > For this and a number of other reasons, our company created our own Maven > repository on our company intranet. This allows us to control the > repository > ourselves and, since it is not public, put any jars we like on it > (including > commercial stuff). Not least, we can post our own internal jars for use by > other projects within the company. Thanks, Lester. I've got some learning to do, but this points me in the right direction. Maury - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dependencies and the local repository
Forgive me for asking what must be a very basic question. I've searched the
Maven site and scoured the archives for this list and haven't found an
answer.
I have a simple java project defined in an Ant file. The dependencies for
my current project are in jars in the ${basedir}/lib directory. I've
configured Ant to include in the classpath whatever jars it finds in that
lib directory.
I'm trying to duplicate this functionality with Maven, and I've hit a
roadblock. I have jars that don't conform to Maven's idea of a standard
name. An example would be the mail.jar from Sun's site. I use it. I tried
a dependency entry in my project.xml as follows:
mail
mail
1.3
mail.jar
I tried putting the jar in ${HOME}/.maven/repository/jars, but it wasn't
found. Then I tried to follow the format in the repository and made a
directory structure as follows:
$HOME/.maven/repository/mail/jars/mail.jar
That appears to work, but is that what Maven expects me to do for each jar
file? This seems like a lot of work for jars that will never be downloaded
from a remote repository anyway.
This all brings me to the fact that I don't grasp the remote repository
concept. Is there 1 remote repository and it's global to the world? I went
to http://www.imbiblio.org/maven and looked at the repository there. It
seems small if it's supposed to be the global parking spot for Maven
projects world-wide.
Please forgive my misunderstanding,
Maury
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
