maven-jar-plugin version 2.3 MANIFEST.MF SNAPSHOT problem
I see that http://jira.codehaus.org/browse/MJAR-28 was "fixed" in the 2.3
release. From my perspective, this seems to have broken things, including a
viable working system I had using 2.2.
In 2.3 I have several SNAPSHOT dependencies, but when I build a jar with
addClasspath, only one of those is getting a timestamp version, the rest
still say -SNAPSHOT. In 2.2 all would say -SNAPSHOT. By adding:
${artifact.artifactId}-${artifact.baseVersion}.${artifact.extension}
to my dependency-set config for the assembly plugin, the assembly plugin
would also always use -SNAPSHOT.
In 2.3 the versions in the MANIFEST still do not match up to the assembly
(after removing the outputFileNameMapping), as in that case all the versions
in the assembly are timestamped, but many are not in the manifest.
Should I reopen MJAR-28?
--
Stephen Duncan Jr
www.stephenduncanjr.com
Re: Why are repositories usually separated into releases and snapshots?
On Sat, Oct 24, 2009 at 9:36 PM, David Weintraub wrote: > No one has answered the basic question: Why two repositories? > > I know the differences between a release and snapshot. but that doesn't > explain why the releases and snapshots are in two separate repositories. > Why > not keep both snapshots and releases in the same repository. We know > something is a snapshot simply because it has the word "SNAPSHOT" appended > to it. > > Because of the dual repository structure, I have to configure everything > with two separate repository names, two separate repository URLs, and two > sets of accounts and passwords. So, why not simply have a single repository > which can store both snapshots and releases? > > These are the only reasons I can think of: > > * Administration: Backing up a release repository is extremely important. > Backing up snapshots -- not so much. But, is this actually true? > > * Who can see what. I might want my snapshot repository available to my > developers, but not to the world. However, this would be more of something > my repository management software should be able to do. > > * Releases should only be added to the release repository by a release > manager, and not by any developer. However, snapshots would be added by > developers. Again, this seems better handled via my repository management > software. > > So, what is the reason to have two separate and distinct repositories for > snapshots and for releases? > > On Thu, Oct 22, 2009 at 4:43 AM, Costin Caraivan >wrote: > > > > -- > David Weintraub > qazw...@gmail.com > I think both security and administration were the original reasons. It's easier to say now "well, the repository manager can make the distinction between releases and snapshots", but you couldn't assume the existence of sophisticated repository managers when Maven 2 was initially designed/released. At that time simple file-system repositories independent of Maven were used (scp/sftp/webdav). -- Stephen Duncan Jr www.stephenduncanjr.com
Re: How to update parent during release:prepare
; >> > > On 09/10/2009 05:30 AM, Lewis, Eric wrote: > >> > > > Hi > >> > > > > >> > > > I'm trying to use release:prepare for a project with > >> > > several modules. > >> > > > The project has a parent which is a SNAPSHOT. Now my > >> > > question is: How can I tell release:prepare to update the > >> > > project's parent version to the parent's released version? > >> > > > > >> > > > Best regards, > >> > > > Eric > >> > > > > >> > > > >> - > >> > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > > > For additional commands, e-mail: users-h...@maven.apache.org > >> > > > > >> > > > > >> > > > >> > > > >> - > >> > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > > For additional commands, e-mail: users-h...@maven.apache.org > >> > > > >> > > > >> > > >> - > >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> > For additional commands, e-mail: users-h...@maven.apache.org > >> > > >> > > >> > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Stephen Duncan Jr www.stephenduncanjr.com
Re: How to update parent during release:prepare
I certainly have the exact same problem. And using the versions plugin only helps somewhat in partially automating what I currently do manually. Last time I made the mistake of not manually changing the parent version, the release plugin, I believe, offered to update to a released version, but didn't actually change it, resulting in what was essentially a broken release (since it had a SNAPSHOT parent). Similarly I face problems with the release plugin not handling SNAPSHOT versions of "dependencies" declared outside the dependencies section (typically using the maven-dependency plugin instead). I would like to see the release plugin updated to handle these rather than work around them with the versions plugin. -Stephen On Fri, Sep 11, 2009 at 9:51 AM, Lewis, Eric wrote: > Thanks, that works well! > > However, I'm still wondering whether I'm the only one releasing that way. > It seems to me that the release plugin can only be used together with the > versions plugin. > I think that most developers have some sort of company-wide parent POM > which they refer to, and when releasing, they probably all have the same > problem as I do. > > Best regards, > Eric > >
Re: Can I access timestamp version of SNAPSHOT dependency within a build?
On Fri, Jul 31, 2009 at 10:53 AM, Stephen Duncan Jr < stephen.dun...@gmail.com> wrote: > I'm trying to manually build an assembly that aggregates multiple > assemblies, to make an installer. So, I depend on the .tar.gz produced from > other assemblies, I use the dependency-plugin to unpack those dependencies. > While versions are SNAPSHOTs, all of the directories after unpacking have > names like artifactId-1.0-SNAPSHOT. I'd like to rename them to match the > timestamped version when the dependencies are pulled from the repository. > Is there a way to access the timestamped version number from the build? > (From there I could use the antrun plugin or the GMaven plugin to do the > rename) > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > For now, I'm using the maven-assembly-plugin to to create a directory assembly with dependencySet. This is the only tool I know of right now that produces the dependency files with the timestamp in the name instead of "SNAPSHOT". I'm then looping over the files in the directory produced and extracting out the names and the versions from the name. I'd love to find out a cleaner way of getting this information... -- Stephen Duncan Jr www.stephenduncanjr.com
Can I access timestamp version of SNAPSHOT dependency within a build?
I'm trying to manually build an assembly that aggregates multiple assemblies, to make an installer. So, I depend on the .tar.gz produced from other assemblies, I use the dependency-plugin to unpack those dependencies. While versions are SNAPSHOTs, all of the directories after unpacking have names like artifactId-1.0-SNAPSHOT. I'd like to rename them to match the timestamped version when the dependencies are pulled from the repository. Is there a way to access the timestamped version number from the build? (From there I could use the antrun plugin or the GMaven plugin to do the rename) -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Make Google Code ant projects available
On Thu, May 28, 2009 at 12:19 PM, Sam Halliday wrote: > > Not interested in moving my project hosting. > > > Stuart McCulloch wrote: > > > > ... What appears to be a sales pitch... > > > > -- > View this message in context: > http://www.nabble.com/Make-Google-Code-ant-projects-available-tp23763883p23765110.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > Just reading about for the first time, but: 1) it may be a sales pitch, but it does look to be a sales pitch for something that's free 2) It wouldn't involve changing your project hosting. It doesn't do project hosting, just repository hosting. Essentially it just gives you way to put artifacts somewhere to be rsync'd since Google Code doesn't... Once you had a place to put things that allows rsync (which it appears Sonatype is one, though I imagine there may be other ways), you should be able to use the Maven Ant Tasks: http://maven.apache.org/ant-tasks/index.html and Ant to automate deploying your releases there, and then they'd get sync'd to central. Sorry, I'm not much an Ant person anymore, so I can't give you the step-by-step, but it does seem a viable approach. -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Make Google Code ant projects available
On Thu, May 28, 2009 at 11:51 AM, Jeff MAURY wrote: > I don't think Google Code does support rsync. > What I have done on one of my Google Code project is to create inside the > sourcde tree a folder called repository which is a Maven repository. Then, > when my build is release, it is deployed into this part (I think this can > be > done with the WebDav protocol which is supported by SVN). > Any projects wanted to use your artifacts should declared this repository > you just created. > > Regards > Jeff MAURY > > On Thu, May 28, 2009 at 5:15 PM, Sam Halliday >wrote: > > This is, generally speaking, not a very good solution. Other open-source projects that wish to use your artifacts as dependencies will not be able to get their artifacts into the central repository if they have to have a third-party (your google code site) repository added. (See the original link). Also, for those that don't use repository managers, added a repository to your pom slows Maven down, as now every artifact is looked for in every repository you have to specify. Repository proliferation considered harmful. My own Google code release fell very much into the infrequent release category, so I built a bundle as described on the site and filed an issue for it to be uploaded. I've done this both for my own Maven-built project, as well as manually building an upload-bundle for binaries for other projects that are built with Ant. -- Stephen Duncan Jr www.stephenduncanjr.com
maven-eclipse-plugin 2.6 project references
Amongst several other surprising changes in the 2.6 release of the maven-eclipse-plugin, I'd like to explain on one change caused some confusion for myself and other members of my development team. I'm not sure it's really a bug, or exactly what feature enhancement to file, so I'm hoping this thread can help determine a better future outcome. Background: We have many different components as individual maven projects, no multi-project/reactor projects, and Hudson continuously building and deploying SNAPSHOTs to Nexus. The typical workflow for a developer would be to check out any particular component they needed to work on, and they could run 'mvn eclipse:eclipse' to get the classpath right, and to download the latest versions of any dependent components (settings.xml defined the repository with a updatePolicy of always). If they wanted to make changes to a dependent component locally, they'd make the changes, run mvn install, and then refresh the project to get those changes. This all worked without any extra configuration of the eclipse plugin. Also, the name of the project in eclipse didn't necessarily match the artifactId in anyway; typically it matched the folder in Subversion (which is sometimes, though rarely, different from the artifactId), or the the name of the branch in Subversion (artifactId-version, where version might be a SNAPSHOT, or be something like 1.2.x). With the eclipse plugin 2.6, it seems new work has been done to try to identify other projects in the eclipse workspace, and use those as project dependencies, instead of jar dependencies in the local repository. To get the workflow described above, I've gone ahead and configured (in our corporate parent pom) the eclipse plugin to not do project references at all. However, I didn't have to specify that before (I think it only used to affect reactor-builds), and therefore our team did get confused by the new behavior. When all SNAPSHOT dependencies were being downloaded from the repository, the version was the timestamp version of the SNAPSHOT, and never matched a project in the workspace, and so it behaved as before, so no problem. However, once somebody installed a dependency locally, the version was just -SNAPSHOT, so the eclipse plugin believed it found a match in the workspace. However, the name it tried to use for the project reference was the artifactId, not the actual name of the project in eclipse, and therefore the project showed up as broken in eclipse, due to the unsatisfied dependency. I think it would be better if the default went back to only doing project references for reactor builds. I also don't know if there's some better way to figure out the right project name to use for the reference. Even if our dependency had been named to match the project reference, somebody working on the branch may have gotten the WRONG project reference (the trunk would have the artifactId, but the wrong version, the branch project name would be the right version, but not match the expected name). -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Maven EAR Plugin ContextRoot
On Sun, Jan 18, 2009 at 5:30 AM, Stephane Nicoll wrote: > On Wed, Jan 14, 2009 at 11:39 PM, Stephen Duncan Jr > > It is working with both 2.3.1 and the trunk. I've just tried on a > stupid project that I have for testing and it worked. Can you maybe > post your pom.xml file? > > > maven-ear-plugin > 2.3.1 > > > >root.project.servlets >servlet >/foobar > > > > > > > > > -- > > Stephen Duncan Jr > > www.stephenduncanjr.com > > > > > > -- > Large Systems Suck: This rule is 100% transitive. If you build one, > you suck" -- S.Yegge > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > Somehow I'd gone all this time without noticing that I was missing the level of the configuration. Thanks for verifying that it did work so that I re-examined my pom more closely. Apologies for the mistake. -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Maven EAR Plugin ContextRoot
On Thu, Jan 15, 2009 at 3:43 PM, Wayne Fay wrote: > > For now I've worked around the issue by using the applicationXml > > configuration to point to my own application.xml with the context-root > being > > set, instead of using the generated one. I'd still like to know if this > is > > just broken for everyone, or if there's something I'm missing so I can > > decide how to file a bug. > > Take a look at the source code: > > http://svn.apache.org/viewvc/maven/plugins/trunk/maven-ear-plugin/src/main/java/org/apache/maven/plugin/ear/WebModule.java?revision=728546&view=markup > > If I were you, I'd debug that class/method in an IDE or add some > System.out's to see what's going on during the execution of the code. > (This assumes you pull down the entire plugin and rebuild it with a > new version eg 2.3.99 which you'd build and install locally, and then > specify it in your pom.xml file -- make sure you delete it later!) > Without doing that, I'm not sure if there's a bug here or not. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > I don't see anything in the source code that looks like it gets the contextRoot from the configuration. The one method that mentions it 1) checks for null, and then sets it to the default if it's still null, even though the constructor initializes it the default, 2) that method (resolveArtifact) is never called. I don't really understand how nested configuration elements like this are supposed to be set. I'd be willing to try to debug the issue further if I knew where to start. -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Maven EAR Plugin ContextRoot
On Wed, Jan 14, 2009 at 5:39 PM, Stephen Duncan Jr wrote: > I'm following the instructions here to set the context-root for my web > modules as specified here: > http://maven.apache.org/plugins/maven-ear-plugin/examples/customizing-context-root.html > > It seems to have no effect on the generated application.xml, the > context-root still has the default values. I couldn't find any mention of > this problem. Can anyone else indicate if this works or not in the current > release of the maven-ear-pluging (2.3.1)? > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > For now I've worked around the issue by using the applicationXml configuration to point to my own application.xml with the context-root being set, instead of using the generated one. I'd still like to know if this is just broken for everyone, or if there's something I'm missing so I can decide how to file a bug. -- Stephen Duncan Jr www.stephenduncanjr.com
Maven EAR Plugin ContextRoot
I'm following the instructions here to set the context-root for my web modules as specified here: http://maven.apache.org/plugins/maven-ear-plugin/examples/customizing-context-root.html It seems to have no effect on the generated application.xml, the context-root still has the default values. I couldn't find any mention of this problem. Can anyone else indicate if this works or not in the current release of the maven-ear-pluging (2.3.1)? -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Using springframework in maven project
Notice that there's no jar file, only a pom for spring-full: http://repo1.maven.org/maven2/org/springframework/spring-full/1.2.8/ I'm guessing you want just spring http://repo1.maven.org/maven2/org/springframework/spring/1.2.9/ (if you need 1.x line), or http://repo1.maven.org/maven2/org/springframework/spring/2.5.5/ (if you want the latest) -Stephen On Wed, Sep 10, 2008 at 11:29 AM, Simon Aquilina <[EMAIL PROTECTED]> wrote: > Hi, > > I am trying to use springframework inside a maven project. My dependency is > as follows: > > > org.springframework > spring-full > 1.2.8 > > > However when I enter the command mvn compile I get the following error: > > [console] > D:\Projects\test>mvn compile > [INFO] Scanning for projects... > [INFO] > > [INFO] Building test Maven Webapp > [INFO]task-segment: [compile] > [INFO] > > [INFO] [resources:resources] > [INFO] Using default encoding to copy filtered resources. > Downloading: > http://repo1.maven.org/maven2/org/springframework/spring-full/1.2.8 > /spring-full-1.2.8.pom<http://repo1.maven.org/maven2/org/springframework/spring-full/1.2.8/spring-full-1.2.8.pom> > Downloading: > http://repo1.maven.org/maven2/org/springframework/spring-full/1.2.8 > /spring-full-1.2.8.jar<http://repo1.maven.org/maven2/org/springframework/spring-full/1.2.8/spring-full-1.2.8.jar> > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Failed to resolve artifact. > > Missing: > -- > 1) org.springframework:spring-full:jar:1.2.8 > > Try downloading the file manually from the project website. > > Then, install it using the command: > mvn install:install-file -DgroupId=org.springframework > -DartifactId=spring > -full -Dversion=1.2.8 -Dpackaging=jar -Dfile=/path/to/file > > Alternatively, if you host your own repository you can deploy the file > there: > > mvn deploy:deploy-file -DgroupId=org.springframework > -DartifactId=spring-f > ull -Dversion=1.2.8 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] > -Drepositor > yId=[id] > > Path to dependency: >1) com.test:test:war:1.0-SNAPSHOT >2) org.springframework:spring-full:jar:1.2.8 > > -- > 1 required artifact is missing. > > for artifact: > com.test:test:war:1.0-SNAPSHOT > > from the specified remote repositories: > central (http://repo1.maven.org/maven2) > > > [INFO] > > [INFO] For more information, run Maven with the -e switch > [INFO] > > [INFO] Total time: 42 seconds > [INFO] Finished at: Wed Sep 10 17:25:07 CEST 2008 > [INFO] Final Memory: 2M/5M > [INFO] > > > D:\Projects\test> > [/console] > > I cannot understand why it is not working since the path to the spring > resource I want is correct " > http://repo1.maven.org/maven2/org/springframework/spring-full/1.2.8 > > /spring-full-1.2.8.pom". > > Does anyone know how this can be solved? I read on the internet that it > could be because I need the jmx library as well. I tried to include this as > a dependency but also failed! :( > > Regards, > Simon J. > > _ > News, entertainment and everything you care about at Live.com. Get it now! > http://www.live.com/getstarted.aspx -- Stephen Duncan Jr www.stephenduncanjr.com
Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released
On Fri, Sep 5, 2008 at 9:24 AM, Stephen Duncan Jr <[EMAIL PROTECTED]>wrote: > My first attempt to run it gave this output that seems...incorrect: > > [INFO] The following dependency updates are available: > [INFO] c3p0:c3p0 .. 0.9.1.2 -> > 0.9.0 > > Sorry about the noise; I see from the FAQ that a fourth digit in a version number isn't handled numerically by default... -- Stephen Duncan Jr www.stephenduncanjr.com
Re: [ANN] Versions Maven Plugin 1.0-alpha-1 released
On Thu, Sep 4, 2008 at 7:18 PM, Stephen Connolly < [EMAIL PROTECTED]> wrote: > The Mojo team is pleased to announce the release of the Versions Maven > Plugin, version 1.0-alpha-1. > > This plugin allows: > * the querying for newer versions of plugins used in a project. > * the querying for newer versions of dependencies used in a project. > * updating a project's parent to the latest available version > (e.g. useful for syncing with corporate poms to ensure the latest is > used prior to rolling a release) > * updating properties defined in a project to the latest version of a > specific > artifact (e.g. for ensuring that a suite of dependencies are all the same > version) > > http://mojo.codehaus.org/versions-maven-plugin/ > > You can run mvn -up to get the latest version of the plugin, or specify > the version in your project's plugin configuration: > > > org.codehaus.mojo > versions-maven-plugin > 1.0-alpha-1 > > > Release Notes - Maven 2.x Versions Plugin - Version 1.0-alpha-1 > > ** Bug >* [MVERSIONS-1] - javadoc plugin doesn't have its version specified but > it has >* [MVERSIONS-2] - display-plugin-updates does not include lifecycle > plugins that are not defined in the pom. > > ** Known Issues - Maven 2.x Versions Plugin - Version 1.0-alpha-1 >* [MVERSIONS-3] - display-plugin-updates does not identify the plugin > version as not being provided when derived from the super-pom > > Enjoy, > > -The Mojo team > My first attempt to run it gave this output that seems...incorrect: [INFO] The following dependency updates are available: [INFO] c3p0:c3p0 .. 0.9.1.2 -> 0.9.0 -- Stephen Duncan Jr www.stephenduncanjr.com
Re: release:prepare and multi-module projects
Sounds like the same problem many are facing with a bug in SVN 1.5.1 See these threads on the SVN & Maven mailing lists: http://www.nabble.com/Mac-OS-X-%2B-SVN-1.5.1-%3D-Branch-problem-td19017538.html#a19142776 http://www.nabble.com/Release-fails-during-SVN-commit-td19084270.html I'm still looking to get some confirmation that it's a bug before reporting it ion the SVN issue tracker... -Stephen On Tue, Aug 26, 2008 at 9:18 AM, David Roussel <[EMAIL PROTECTED]>wrote: > > I've been trying to run release:prepare on a nested project and I keep > running into the same SVN related issues. Has anyone else got it working? > > I can supply the full trace, but the basic problem I get is: > > ... > [INFO] Executing: svn --non-interactive copy --file > C:\DOCUME~1\UT159N\LOCALS~1\Temp\maven-scm-1626400052.commit . > http://gcm-svn/ > svn/REPO1/Projects/InstallTools/tags/installer-0.5<http://gcm-svn/svn/REPO1/Projects/InstallTools/tags/installer-0.5> > [INFO] Working directory: D:\dev\workspace1\installer > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Unable to tag SCM > Provider message: > The svn tag command failed. > Command output: > svn: Commit failed (details follow): > svn: File > > '/svn/REPO1/Projects/InstallTools/tags/installer-0.5/installer-plugin/pom.xml' > already exists > > > If I repeat that svn command on the comand line it does fail again. The > file does not exist. But if I do 'svn update' and then repeat it, then it > works. > > Also if I manually, do a 'svn copy URL URL' version of tagging, that also > works. > > I've been trying to reproduce the problem in raw svn, just doing svn > commands and I can't. So I guess it must be a maven-release-plugin bug. > > So has anyone else got the release plugin to work in multi-module projects > using svn? > > Thanks > > David > -- > View this message in context: > http://www.nabble.com/release%3Aprepare-and-multi-module-projects-tp19161884p19161884.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com
Re: AW: Release fails during SVN commit
If it's happening directly from the command-line as Daniel indicated (I haven't tried it myself, but as far as I know Maven uses the command-line, not JavaHL), then it can't be a JavaHL issue. -Stephen On Thu, Aug 21, 2008 at 10:38 AM, Emmanuel Venisse < [EMAIL PROTECTED]> wrote: > The issue is discussed on the subversion users list : > > http://www.nabble.com/Mac-OS-X-%2B-SVN-1.5.1-%3D-Branch-problem-td19017538.html > > It is related to a change in JavaHL: > * correctly set the peg revision for copy in JavaHL (r31994) > > Emmanuel > > On Thu, Aug 21, 2008 at 4:15 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > > On Thursday 21 August 2008 10:09:07 am Stephen Duncan Jr wrote: > > > On the other hand, the fact that I forgot to run svn up before running > > the > > > release plugin has bitten me before, and I had to make a second release > > > because I didn't realize it. Ideally it'd warn you about remote > changes > > > the same way it does about local uncommitted changes. But that still > > > leaves the possibility of a commit sneaking in like you mentioned. > > > > > > So is there an existing bug for Svn 1.5 not being able to tag from a > > > working copy, or does it need to be filed? > > > > Probably needs to be filed. > > > > Dan > > > > > > > > > > > > -Stephen > > > > > > On Thu, Aug 21, 2008 at 10:03 AM, Daniel Kulp <[EMAIL PROTECTED]> > wrote: > > > > I had the same problem with 1.5.1 on Gentoo.It's a subversion > > > > problem, not > > > > a release plugin problem.If you run the same command that release > > is > > > > trying to run (can be seen when you run mvn with -X), it fails. > > > > Basically, > > > > with 1.5, you apparently cannot "svn cp" your working copy into a > tag. > > > > Something like: > > > > svn cp . http://vblah.com/repo/tag/foo.1.2.3 > > > > which is what release is trying to do. > > > > > > > > I ended up manually doing: > > > > svn cp http://vblah.com/repo/trunk > http://vblah.com/repo/tag/foo.1.2.3 > > > > and editing the release.properties thing to mark that the tag phase > was > > > > done > > > > and then resumed it. Kind of sucked. > > > > > > > > The release plugin COULD tag/branch via the trunk. However, it > > > > explicitly does NOT do it that way so if a commit sneaks in between > the > > > > commit of the poms and the tag command, that commit wouldn't be part > of > > > > the tag. > > > > > > > > Dan > > > > > > > > On Thursday 21 August 2008 9:27:13 am Andreas Heinecke wrote: > > > > > Hi Stephen, > > > > > > > > > > thank you for your answer. > > > > > Can anyone else confirm this? So one (probably me) should report > this > > > > > > > > issue > > > > > > > > > at the issue tracker. > > > > > > > > > > Andreas. > > > > > > > > > > -Ursprüngliche Nachricht- > > > > > Von: Stephen Duncan Jr [mailto:[EMAIL PROTECTED] > > > > > Gesendet: Donnerstag, 21. August 2008 14:48 > > > > > An: Maven Users List > > > > > Betreff: Re: Release fails during SVN commit > > > > > > > > > > I've had the problem as well on Ubuntu Linux, so it's a general > > problem > > > > > with SVN 1.5. > > > > > > > > > > -Stephen > > > > > > > > > > On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke > > > > > > > > <[EMAIL PROTECTED]>wrote: > > > > > > No, we use MS Windows Vista, and XP. The problem occurs on each > of > > > > > > > > these > > > > > > > > > > platforms. > > > > > > > > > > > > -Ursprüngliche Nachricht- > > > > > > Von: Luke Daley [mailto:[EMAIL PROTECTED] > > > > > > Gesendet: Donnerstag, 21. August 2008 11:12 > > > > > > An: Maven Users List > > > > > > Betreff: Re: Release fails during SVN commit > > > > > > > > > > > > If your on Mac OS 10.5, check out > > > > > > > > > > > http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive- >
Re: AW: Release fails during SVN commit
On the other hand, the fact that I forgot to run svn up before running the release plugin has bitten me before, and I had to make a second release because I didn't realize it. Ideally it'd warn you about remote changes the same way it does about local uncommitted changes. But that still leaves the possibility of a commit sneaking in like you mentioned. So is there an existing bug for Svn 1.5 not being able to tag from a working copy, or does it need to be filed? -Stephen On Thu, Aug 21, 2008 at 10:03 AM, Daniel Kulp <[EMAIL PROTECTED]> wrote: > > I had the same problem with 1.5.1 on Gentoo.It's a subversion problem, > not > a release plugin problem.If you run the same command that release is > trying to run (can be seen when you run mvn with -X), it fails. > Basically, > with 1.5, you apparently cannot "svn cp" your working copy into a tag. > Something like: > svn cp . http://vblah.com/repo/tag/foo.1.2.3 > which is what release is trying to do. > > I ended up manually doing: > svn cp http://vblah.com/repo/trunk http://vblah.com/repo/tag/foo.1.2.3 > and editing the release.properties thing to mark that the tag phase was > done > and then resumed it. Kind of sucked. > > The release plugin COULD tag/branch via the trunk. However, it explicitly > does NOT do it that way so if a commit sneaks in between the commit of the > poms and the tag command, that commit wouldn't be part of the tag. > > Dan > > > > On Thursday 21 August 2008 9:27:13 am Andreas Heinecke wrote: > > Hi Stephen, > > > > thank you for your answer. > > Can anyone else confirm this? So one (probably me) should report this > issue > > at the issue tracker. > > > > Andreas. > > > > -Ursprüngliche Nachricht- > > Von: Stephen Duncan Jr [mailto:[EMAIL PROTECTED] > > Gesendet: Donnerstag, 21. August 2008 14:48 > > An: Maven Users List > > Betreff: Re: Release fails during SVN commit > > > > I've had the problem as well on Ubuntu Linux, so it's a general problem > > with SVN 1.5. > > > > -Stephen > > > > On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke > <[EMAIL PROTECTED]>wrote: > > > No, we use MS Windows Vista, and XP. The problem occurs on each of > these > > > platforms. > > > > > > -Ursprüngliche Nachricht- > > > Von: Luke Daley [mailto:[EMAIL PROTECTED] > > > Gesendet: Donnerstag, 21. August 2008 11:12 > > > An: Maven Users List > > > Betreff: Re: Release fails during SVN commit > > > > > > If your on Mac OS 10.5, check out > > > > > > > > > > http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive- > > >pro > > > blems-in-leopards-subversion/< > http://blogs.exist.com/bporter/2008/02/25/w > > >orking-around-non-interactive-problems-in-leopards-subversion/> > > > > > > On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote: > > > > Hi there, > > > > > > > > I encountered a strange problem. Since a few weeks I'm not able to > > > > perform a > > > > release with Maven. The release process fails during executing the > > > > release:prepare goal at the same position, always. The point at > > > > which the > > > > release fails is when Maven tries to commit the release POM's to > > > > SVN. This > > > > commit fails with the error message that the file which is about to > be > > > > committed already exists at the position in SVN. But it isn't there. > > > > Strange, uh? > > > > > > > > I actually checked the tagbase configuration of the plugin and tried > > > > to > > > > alter it, but the effect remains. > > > > I don't know what I can try to fix this issue. > > > > The last thing altered at the configuration is a switch of the SVN > > > > server. > > > > We had to switch to a newer SVN version 1.5.0. We also switched to > > > > the new > > > > 1.5.0 SVN client as we know that there are problems with newer server > > > > software and older client software. > > > > > > > > Please find parts of my pom.xml configuration attached below. > > > > > > > > Any pointers are welcome. > > > > > > > > Regards, > > > > Andreas. > > > > > > > > My SCM configuration: > > > > > > > >scm:svn:http://xxx.xxx.xxx.xxx/svndir/project &
Re: Release fails during SVN commit
I've had the problem as well on Ubuntu Linux, so it's a general problem with SVN 1.5. -Stephen On Thu, Aug 21, 2008 at 5:37 AM, Andreas Heinecke <[EMAIL PROTECTED]>wrote: > No, we use MS Windows Vista, and XP. The problem occurs on each of these > platforms. > > -Ursprüngliche Nachricht- > Von: Luke Daley [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 21. August 2008 11:12 > An: Maven Users List > Betreff: Re: Release fails during SVN commit > > If your on Mac OS 10.5, check out > > > http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-pro > blems-in-leopards-subversion/<http://blogs.exist.com/bporter/2008/02/25/working-around-non-interactive-problems-in-leopards-subversion/> > > On 21/08/2008, at 6:04 PM, Andreas Heinecke wrote: > > > Hi there, > > > > I encountered a strange problem. Since a few weeks I'm not able to > > perform a > > release with Maven. The release process fails during executing the > > release:prepare goal at the same position, always. The point at > > which the > > release fails is when Maven tries to commit the release POM's to > > SVN. This > > commit fails with the error message that the file which is about to be > > committed already exists at the position in SVN. But it isn't there. > > Strange, uh? > > > > I actually checked the tagbase configuration of the plugin and tried > > to > > alter it, but the effect remains. > > I don't know what I can try to fix this issue. > > The last thing altered at the configuration is a switch of the SVN > > server. > > We had to switch to a newer SVN version 1.5.0. We also switched to > > the new > > 1.5.0 SVN client as we know that there are problems with newer server > > software and older client software. > > > > Please find parts of my pom.xml configuration attached below. > > > > Any pointers are welcome. > > > > Regards, > > Andreas. > > > > My SCM configuration: > > > >scm:svn:http://xxx.xxx.xxx.xxx/svndir/project > connection> > > > > scm:svn:http://xxx.xxx.xxx.xxx/svndir/project > develope > > rConnection> > >http://xxx.xxx.xxx.xxx/svndir/project > > > > > > My release plugin configuration: > > > >org.apache.maven.plugins > >maven-release-plugin > > > >http://XXX.XXX.XXX.XXX/svndir/project/tags > >true > >clean install > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > > LD. > > > - > 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] > > -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Using the Release Plugin For Testing-Releases
That's a fair question. This may very well be a "Doc, it hurts when I do X", "Well, dont' do X" case. However, we currently have things set up to include the Maven version in UI for one of the web components, so that would still say SNAPSHOT, whereas doing a real-release would help indicate the version running to a tester, and be consistent with what we want in a full release. And the version number, even just in jar files, is a lot easier to see in the file name than opening up the manifest to see an SVN attribute that I configure to be added. I will think through whether we should skip the beta release process, but I'd like to hear other suggestions as well... -Stephen On Thu, Jul 17, 2008 at 10:08 AM, nicolas de loof <[EMAIL PROTECTED]> wrote: > Why don't you test the snapshots ? You can configure a cron to deploy > nightly-buils, and SNAPSHOTS to have a unique timestamp number. You can > also > configure the cron to tag if required, or (simplier IMHO) to include the > SVN > revision in MANIFEST files. > > Nicolas > > 2008/7/17 Stephen Duncan Jr <[EMAIL PROTECTED]>: > > > On Thu, Jul 17, 2008 at 9:40 AM, nicolas de loof <[EMAIL PROTECTED]> > > wrote: > > > > > For comparable use case I use the release:stage goal (in place of > > > release:perform) to create the release but not remove the "rolback" > > files. > > > I > > > can then create a 1.0 release to get tested, and return to 1.0-SNAPSHOT > > if > > > some issues are found. I just have to rename the tag from 1.0 to > 1.0-rcX > > > (or > > > delete it). > > > > > > Nicolas > > > > > > > I think our usage is a bit different. These beta builds are used on a > test > > environment for multi-day testing. And for some, I even know there will > be > > changes before a final release; I just want versioned & tagged releases > to > > report bugs against for the functionality that is completed now, even > > though > > I know, perhaps, that some more issues are being worked on before the > final > > release. > > > > -- > > Stephen Duncan Jr > > www.stephenduncanjr.com > > > -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Using the Release Plugin For Testing-Releases
On Thu, Jul 17, 2008 at 9:40 AM, nicolas de loof <[EMAIL PROTECTED]> wrote: > For comparable use case I use the release:stage goal (in place of > release:perform) to create the release but not remove the "rolback" files. > I > can then create a 1.0 release to get tested, and return to 1.0-SNAPSHOT if > some issues are found. I just have to rename the tag from 1.0 to 1.0-rcX > (or > delete it). > > Nicolas > I think our usage is a bit different. These beta builds are used on a test environment for multi-day testing. And for some, I even know there will be changes before a final release; I just want versioned & tagged releases to report bugs against for the functionality that is completed now, even though I know, perhaps, that some more issues are being worked on before the final release. -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Using the Release Plugin For Testing-Releases
On Thu, Jul 17, 2008 at 8:46 AM, Stephen Duncan Jr <[EMAIL PROTECTED]> wrote: > I want to use the release plugin to make testing releases, without > interrupting ongoing development. So, for example I want to take a project > that is at 1.0-SNAPSHOT, and has dependencies that are at 1.0-SNAPSHOT. I > want to make a release for 1.0-beta-1, with the dependencies at 1.0-beta-1 > (assume I've already made those releases). And then I want trunk to be back > at 1.0-SNAPSHOT for the version and dependencies. > > Right now, that almost works, except the release plugin won't accept > 1.0-SNAPSHOT as the "new development version" for the dependencies. Should > I enter that as a feature request/bug? Is there a better practice I should > follow? > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > Oh, and also it will try to set the new version of the dependencies to release, but it doesn't tell you that it goes to "1.0" instead of "1.0-beta-1". -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Using the Release Plugin For Testing-Releases
On Thu, Jul 17, 2008 at 8:49 AM, Stephen Connolly < [EMAIL PROTECTED]> wrote: > why not use mvn scm:branch to move to a branch and then make the > release from the branch and finally remove the branch > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > Well, my goal is to have as little manual steps as possible, as that's an invitation for mistakes. I'm not sure making a branch & deleting it makes things any easier than what I currently do, which is update the dependencies to beta-1 & commit, then use the release plugin, and then update the dependencies back to 1.0-SNAPSHOT & commit. -- Stephen Duncan Jr www.stephenduncanjr.com
Using the Release Plugin For Testing-Releases
I want to use the release plugin to make testing releases, without interrupting ongoing development. So, for example I want to take a project that is at 1.0-SNAPSHOT, and has dependencies that are at 1.0-SNAPSHOT. I want to make a release for 1.0-beta-1, with the dependencies at 1.0-beta-1 (assume I've already made those releases). And then I want trunk to be back at 1.0-SNAPSHOT for the version and dependencies. Right now, that almost works, except the release plugin won't accept 1.0-SNAPSHOT as the "new development version" for the dependencies. Should I enter that as a feature request/bug? Is there a better practice I should follow? -- Stephen Duncan Jr www.stephenduncanjr.com
Re: How to make nexus work with thirdparty libraries??
To match up to a server id in settings.xml if there is authentication required for the repository. On Wed, Jun 11, 2008 at 6:35 PM, Kent Närling <[EMAIL PROTECTED]> wrote: > Using a local repository? > > But then every developer has to add this to their local repository?? > And it gets even more messy to get this working with automatic builds? > > Or do you mean that I should add another hosted repository in nexus? > (usually "local" repository refers to the repository on your own machine?) > Again, the central part was just an example, the question was more: > If I have a nexus server, WHERE should I install it? > > http://localhost:8081/nexus/content/repositories/thirdparty > -DrepositoryId=thirdparty<http://localhost:8081/nexus/content/repositories/thirdparty-DrepositoryId=thirdparty> > < > http://localhost:8081/nexus/content/repositories/central-DrepositoryId=central > >? > (since a "thirdparty" hosted repository is already defined in the default > nexus setup?) > > And by the way, why IS there a -DrepositoryId if that is part of the URL > anyway? > > > 2008/6/12 Ed Hillmann <[EMAIL PROTECTED]>: > > > On Wed, Jun 11, 2008 at 4:59 PM, Kent Närling <[EMAIL PROTECTED]> > > wrote: > > > Actually, I tried to upload this plugin manually to our nexus > repository, > > > but cannot get it to install properly... > > > > > > Trying the command: > > > b-plugin\1.1>mvn deploy:deploy-file -DgroupId=com.sun.tools.xjc.maven2 > > > -DartifactId=maven-jaxb-plugin -Dversion=1.1 -Dpackaging=maven-plugin > > > -Dfile=maven-jaxb-p > > > lugin-1.1.jar -Durl= > > > http://localhost:8081/nexus/content/repositories/central-DrepositoryId=central > > > > > > But only get the error: > > > [ERROR] BUILD ERROR > > > [INFO] > > > > > > > [INFO] Error deploying artifact: Failed to transfer file: > > > > > > http://localhost:8081/nexus/content/repositories/central/com/sun/tools/xjc/maven2/maven-jaxb-plugin/1.1/maven-jaxb-plugin-1.1.jar > > . > > > Return code is: 401 > > > > > > Guess I probably use the wrong URL, but the documentation regarding > which > > > URL to specify is well, non-existing? > > > Should it point to the nexus root? (would be logical considering you > > specify > > > -DrepositoryId etc) tried this too, doesn't work... > > > > > > //Kent > > So, you are trying to deploy an artifact to your mirror of central? I > > don't know if you can do that or not. But taking an uneducated guess > > I'd think you couldn't do that. Wouldn't you be better off having a > > local repository called "third.party" and use that as repository of > > third party artifacts that are manually deployed to your Nexus server? > > Then, you can include the third.party repository in the public group > > and it's available. > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Kent Närling > > System Architect > SEAMLESS > Dalagatan 100, 8 tr, 113 43 Stockholm, Sweden > Phone: +46 8 5648 7800, fax: +46 8 5648 7823 > Mobile: +46 70 836 9925 > Mail: [EMAIL PROTECTED] > www.seamless.se > -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Cannot deploy using webdav with Maven 2.0.6
If I can reproduce it in an example, I'll create an issue. I was surprised to find, in my attempt to make a sample, that I couldn't reproduce it in the sample, though it continues to occur on my actual project. I notice that in my project (that doesn't work) I get the following at the beginning of the build: [INFO] Scanning for projects... - this realm = app0.child-container[extensions] urls[0] = file:/home/jrduncans/.m2/repository/junit/junit/3.8.2/junit-3.8.2.jar urls[1] = file:/home/jrduncans/.m2/repository/de/zeigermann/xml/xml-im-exporter/1.1/xml-im-exporter-1.1.jar urls[2] = file:/home/jrduncans/.m2/repository/org/apache/maven/wagon/wagon-webdav/1.0-beta-2/wagon-webdav-1.0-beta-2.jar urls[3] = file:/home/jrduncans/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar urls[4] = file:/home/jrduncans/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar urls[5] = file:/home/jrduncans/.m2/repository/slide/slide-webdavlib/2.1/slide-webdavlib-2.1.jar urls[6] = file:/home/jrduncans/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar urls[7] = file:/home/jrduncans/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar urls[8] = file:/home/jrduncans/.m2/repository/commons-httpclient/commons-httpclient/3.0.1/commons-httpclient-3.0.1.jar Number of imports: 0 this realm = plexus.core urls[0] = file:/home/jrduncans/apps/maven/lib/maven-core-2.0.6-uber.jar Number of imports: 0 - But in my sample that does work I get: [INFO] Scanning for projects... [INFO] snapshot com.stephenduncanjr.test:webdavparent:1.0-SNAPSHOT: checking for updates from ce-snapshots WAGON_VERSION: 1.0-beta-2 Any ideas? I'm having difficulty figuring out what I might need to add to the sample to reproduce the problem... -Stephen On 4/2/07, Carlos Sanchez <[EMAIL PROTECTED]> wrote: open a jira http://jira.codehaus.org/browse/MNG and attach a sample with as much detailas possible On 4/2/07, jrduncans <[EMAIL PROTECTED]> wrote: > > Sorry, I realize I wasn't clear. That IS how I am using is. I have the > build extension defined, it worked in Maven 2.0.5, but it does not work in > Maven 2.0.6. (The build extension is defined in a parent POM, but I tested > adding it directly to the POM of the project I was testing, and the result > is the same). > > -Stephen > > > Wendy Smoak-3 wrote: > > > > On 4/2/07, jrduncans <[EMAIL PROTECTED]> wrote: > >> > >> I can't deploy using webdav after upgrading to Maven 2.0.6 > >> > >> I get the following output: > >> [INFO] [deploy:deploy] > >> altDeploymentRepository = null > >> [INFO] Retrieving previous build number from ce-snapshots > >> [WARNING] repository metadata for: 'snapshot > >> mil.jfcom.cie.guard:guardtransport:1.0-SNAPSHOT' could not be retrieved > >> from > >> repository: ce-snapshots due to an error: Unsupported Protocol: 'dav': > >> Cannot find wagon which supports the requested protocol: dav > > > > The easiest way to get dav to work is to add the wagon-webdav jar as a > > build extension. > > > > The Archiva docs explain how: > > > > http://maven.apache.org/archiva/guides/getting-started/maven-configuration.html > > > > -- > > Wendy > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: http://www.nabble.com/Cannot-deploy-using-webdav-with-Maven-2.0.6-tf3506686s177.html#a9797799 > Sent from the Maven - Users mailing list archive at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to deploy sources and javadocs?
Check out the following post: http://www.nabble.com/How-to-upload-3rd-party-source-jars-to-external-repository-tf2594844.html#a7240886 -Stephen On 2/14/07, Dave Hoffer <[EMAIL PROTECTED]> wrote: What I meant was is there a way to use deploy:deploy-file [with all the parameters] to handle source and javadoc jars? I can't see any to do this? I have an external artifact I want to deploy to my corporate maven repo and it has binary, source & javadoc jars. I would like to deploy all three instead of just the binary. -dh -Original Message- From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Wednesday, February 14, 2007 9:18 PM To: Maven Users List Subject: Re: How to deploy sources and javadocs? On 14 Feb 07, at 8:17 PM 14 Feb 07, Stephen Duncan wrote: > mvn clean deploy -DperformRelease=true > I would use the release plugin and not that property because that triggers a profile in the SuperPOM which is going away. That property is only used by the release plugin and the release plugin is the interface. Using that property will burn you in the future. Jason. > -Stephen > > On 2/14/07, Dave Hoffer <[EMAIL PROTECTED]> wrote: >> It doesn't seem the deploy plug-in supports deploying sources and >> javadocs for external artifacts. How can this be done? >> >> >> >> -dh >> >> > > > -- > Stephen Duncan Jr > www.stephenduncanjr.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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to deploy sources and javadocs?
Damn, I keep giving all the wrong advice based on things that are going to stop working... The release plugin isn't really a replacement; in order to easily have source access in Eclipse for debugging, I want to install/deploy the source/javadocs for SNAPSHOTs too. Plus, even for releases, I haven't yet embraced using the release plugin; it's a bit heavyweight for simple releases. Admittedly, performRelease=true for deploying SNAPSHOT sources and jars is quite the misleading name, so I guess I'll just have to come up with a better property name and put it in my global parent POM. Anyhow, new answer for the most direct correct way to do this: mvn clean source:jar javadoc:jar deploy -Stephen On 2/14/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 14 Feb 07, at 8:17 PM 14 Feb 07, Stephen Duncan wrote: > mvn clean deploy -DperformRelease=true > I would use the release plugin and not that property because that triggers a profile in the SuperPOM which is going away. That property is only used by the release plugin and the release plugin is the interface. Using that property will burn you in the future. Jason. > -Stephen > > On 2/14/07, Dave Hoffer <[EMAIL PROTECTED]> wrote: >> It doesn't seem the deploy plug-in supports deploying sources and >> javadocs for external artifacts. How can this be done? >> >> >> >> -dh >> >> > > > -- > Stephen Duncan Jr > www.stephenduncanjr.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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to deploy sources and javadocs?
mvn clean deploy -DperformRelease=true -Stephen On 2/14/07, Dave Hoffer <[EMAIL PROTECTED]> wrote: It doesn't seem the deploy plug-in supports deploying sources and javadocs for external artifacts. How can this be done? -dh -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jetty in maven repo seems a bit messy?
Here you go: org.mortbay.jetty org.mortbay.jetty 5.1.12 runtime Notice the weird artifactId -Stephen On 1/17/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Trying to use Jetty version 5.1.*, but having trouble defining the dependency in my pom. Looking at http://repo1.maven.org/maven2 the jetty stuff seems a bit of a mess? Can anyone give me a working dependency definition please? TIA, Adrian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Version Info and Can't find version "RELEASE"
I was attempting to specify the version of commons-codec as [1.3,), and I got the results posted here: http://www.nabble.com/Abdera%2C-commons-codec-and-Maven-tf2834889.html#p7943556 It seems to be the same as this issue: http://jira.codehaus.org/browse/MNG-613 but I'm not really sure what the nature of the fix was there... -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn2: dev-activity report
Do you have the developers with their id's (matching the SCM username) configured in your POM? I noticed it doesn't report dev-activity for developers not listed in the pom (or in a parent POM). -Stephen On 10/27/06, Attila Mezei-Horvati <[EMAIL PROTECTED]> wrote: Hello all, My dev-activity report is empty. It does display this: Range: Wed Sep 27 16:48:29 EDT 2006 to Sat Oct 28 16:48:29 EDT 2006, Total commits:17, Total Number of Files Changed:33 But it will not display the users who did the commits. Can anybody spot the problem? I tried to add version number: 2.0-SNAPSHOT , too. No luck. See the pom part below. thanks, Attila org.apache.maven.plugins maven-changelog-plugin devreport range 30 changelog file-activity dev-activity 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin Documentation and the Index Page
Yes, you need to specify the version of plugin-plugin in your pom.xml. -Stephen On 10/19/06, Manuel Ledesma <[EMAIL PROTECTED]> wrote: I downloaded version 2.0.5-SNAPSHOT, still getting the same problem. Do I have to specifically tell which version of plugin-plugin to use ? jrduncans wrote: > > Thanks. > > (Notes for anyone else: 2.0.5-SNAPSHOT builds are here: > http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/ ) > > -Stephen > > On 9/21/06, Brett Porter <[EMAIL PROTECTED]> wrote: >> It was a bug in the current release of the plugin plugin. You can use >> the new version, but it also requires a snapshot of maven 2.0.5. I'm >> hoping to work on correcting that shortly, but for now if you grab a >> Maven nightly and build the plugin plugin from SVN you should be good >> to go. >> >> - Brett >> >> On 22/09/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: >> > I'm working on a new maven plugin (see an upcoming e-mail soon), and >> > I'm trying to create the site generally matching the best >> > practices of the new maven plugin sites. I'm having trouble though: I >> > have an src/site/apt/index.apt, but the contents of index.html is the >> > auto-generated plugin documentation. Am I doing something wrong? Is >> > there some workaround? >> > >> > -- >> > Stephen Duncan Jr >> > www.stephenduncanjr.com >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> >> >> -- >> Apache Maven - http://maven.apache.org >> "Better Builds with Maven" book - http://library.mergere.com/ >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Plugin-Documentation-and-the-Index-Page-tf2315168.html#a6896561 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependency quirck?
Provided-scope dependencies are not set to provided when pulled in transitively. See: http://jira.codehaus.org/browse/MNG-2205 (I think) The only solution I know of is to declare the dependency on the servlet-api in the web module with scope=provided. -Stephen On 10/9/06, Jeroen Verhagen <[EMAIL PROTECTED]> wrote: Hi Ronny, On 10/9/06, Naess, Ronny <[EMAIL PROTECTED]> wrote: > Compile scope is included in classpath. Try scope = provided I tried that, made sure everything was cleaned but the servlet-api jar is still there. regards, Jeroen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checkstyle Behind A Firewall
You could put the config file into a jar project, and depend on that project as a build extension, and use a relative url to that file. -Stephen On 9/30/06, Craig McClanahan <[EMAIL PROTECTED]> wrote: On 9/30/06, Andreas Guther <[EMAIL PROTECTED]> wrote: > > > > Looking at the content of the URL a checkstyle config xml file comes up. > Did you try to overwrite the configuration and point to a checkstyle > configuration file of your own? I agree that the file is really there. The problem is that Checkstyle is not respecting the proxy settings to retrieve it, which causes a failure when trying to generate the website (from behind the firewall -- it works fine on a direct connection to the Internet). I bet you can have that file somewhere behind your firewall and either > have a reltaive, absolute, or internal URL reference to it. That would work for me, but it would break the build for everyone else. Andreas Craig -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Craig > McClanahan > Sent: Saturday, September 30, 2006 2:44 PM > To: Maven Users List > Subject: Checkstyle Behind A Firewall > > In the Maven2 build of Shale, I'm having a problem generating the site > when > running behind a firewall. A bit of research indicates that the problem > relates to the following configuration setting for the Checkstyle > plugin. > > > maven-checkstyle-plugin > > > http://svn.apache.org/repos/asf/shale/maven/trunk/build/shale_checks.xml > > > > > This setting works fine when not behind a firewall ... but when I am, it > fails (even though I have the correct proxy set up in by settings.xml > file, > and I can download from repositories normally). Is there any way to > convince the Checkstyle plugin to use the http proxy for looking up this > configuration resource? > > Craig > > --------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is TestNG support in M2 2.0.4 already stable?
I've only tried the JDK15 version with annotations, so I don't know
the status of the javadoc-based runner...
-Stephen
On 9/26/06, Davy Toch <[EMAIL PROTECTED]> wrote:
Hi,
I have the following M2 2.0.4 project containing the following 3 files:
A. $PROJECT_ROOT/src/test/java/testgroup/AppTest.java :
package testgroup;
public class AppTest
{
/**
* @testng.test
*/
public void doSomething()
{
System.out.println("doSomething() called");
}
}
B. $PROJECT_ROOT/testng.xml :
http://testng.org/testng-1.0.dtd"; >
C. $PROJECT_ROOT/pom.xml :
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
testgroup
testapp
jar
1.0-SNAPSHOT
Maven Quick Start Archetype
http://maven.apache.org
org.testng
testng
5.1
test
jdk14
org.apache.maven.plugins
maven-surefire-plugin
testng.xml
When running the tests I get:
$mvn test
[INFO] Scanning for projects...
[INFO]
[INFO] Building Maven Quick Start Archetype
[INFO]task-segment: [test]
[INFO]
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
[INFO] No sources to compile
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
Compiling 1 source file to C:\tmp\xxx\testapp\testapp\target\test-classes
[INFO] [surefire:test]
[INFO] Surefire report directory:
C:\tmp\xxx\testapp\testapp\target\surefire-reports
---
T E S T S
---
Running Regression1
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.09 sec
Results :
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 7 seconds
[INFO] Finished at: Tue Sep 26 21:16:26 CEST 2006
[INFO] Final Memory: 3M/10M
[INFO]
So no tests were found by M2! However if I directly run the TestNG tests
from
the command-line, e.g.:
$c:\devtools\j2sdk1.4.2_10\bin\java.exe -cp \
target\test-classes;c:\devtools\testng-5.1\testng-5.1-jdk14.jar \
org.testng.TestNG \
-sourcedir src\test\java testng.xml
then I get :
doSomething() called
===
Suite1
Total tests run: 1, Failures: 0, Skips: 0
===
Remark that before I ran the above tests, I completely deleted ~/.m2, so the
local repository would be reinitialized from scratch based on what's
available
in http://www.ibiblio.org/maven2.
Regards,
Davy Toch
Davy Toch wrote:
> Hi,
>
> I was just wondering whether TestNG support in M2 is already
> stable and can be used as a viable replacement of JUnit? I
> already tried using TestNG in M2 but I had different problems
> (tests not being run, ClassCastException, ...).
>
> So before I start posting my TestNG-related problems in detail,
> I just have this simple question : is M2 2.0.4 already supposed
> to fully support TestNG or is it recommended to wait until M2
> 2.0.5 or higher?
>
> Regards and thanks,
> Davy Toch
>
>
-----
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen Duncan Jr
www.stephenduncanjr.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is TestNG support in M2 2.0.4 already stable?
My experience is that the only way to use TestNG is to specify a suiteXml file and do all your configuration there. The rest of the TestNG support does not work as documented. While you won't have to wait for Maven 2.0.5 necessarily, you will have to wait for another surefire-plugin release (at least) to get everything working as it's supposed to. -Stephen On 9/25/06, Davy Toch <[EMAIL PROTECTED]> wrote: Hi, I was just wondering whether TestNG support in M2 is already stable and can be used as a viable replacement of JUnit? I already tried using TestNG in M2 but I had different problems (tests not being run, ClassCastException, ...). So before I start posting my TestNG-related problems in detail, I just have this simple question : is M2 2.0.4 already supposed to fully support TestNG or is it recommended to wait until M2 2.0.5 or higher? Regards and thanks, Davy Toch - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is TestNG support in M2 2.0.4 already stable?
Any reason not to bump up the version of TestNG to the latest in the docs? (i.e. 4.7->5.1) -Stephen On 9/26/06, franz see <[EMAIL PROTECTED]> wrote: Davy Toch wrote: > > Hi, > > I was just wondering whether TestNG support in M2 is already > stable and can be used as a viable replacement of JUnit? I > already tried using TestNG in M2 but I had different problems > (tests not being run, ClassCastException, ...). > > So before I start posting my TestNG-related problems in detail, > I just have this simple question : is M2 2.0.4 already supposed > to fully support TestNG or is it recommended to wait until M2 > 2.0.5 or higher? > > Regards and thanks, > Davy Toch > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > Good day to you, Davy, If im not mitaken, yes it is already supported. Furthermore, you can try and read [1] for more information about configuring your maven2 for TestNG. However, [1] is not yet final, and it's stil being reviewed. So if you have any comments or suggestions about it, please let do let us know so that we can improve it. Thanks, Franz [1] http://people.apache.org/~aramirez/maven-surefire-plugin/examples/testng.html -- View this message in context: http://www.nabble.com/Is-TestNG-support-in-M2-2.0.4-already-stable--tf2333996.html#a6500391 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SCM Url's and Tags, Branches, etc.
Does anybody have advice for the issues discussed here: http://www.nabble.com/Re%3A-svn-commit%3A-r449509---in--incubator-abdera-java-trunk%3A-client-pom.xml-core-pom.xml-dependencies-json-pom.xml-examples-pom.xml-extensions-pom.xml-parser-pom.xml-pom.xml-protocol-pom.xml-security-pom.xml-server-pom.xml-tf2328489.html#a6478045 The two issues are: 1) Having to specify scm information in every module because the module folder name does not match the artifactId. 2) Should this scm info be updated for every branch and tag? -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Code Samples in Sites
Ahh. I was thinking that if someone wanted to implement this they'd have to do somethig similar to this muse-java thing I saw on the mailing list earlier... -Stephen On 9/23/06, Arnaud Bailly <[EMAIL PROTECTED]> wrote: "Stephen Duncan" <[EMAIL PROTECTED]> writes: > Can you share the site source? Did you just manually run jhighlight Sorry, I forgot that :-) http://www.oqube.com/projects/object-traversal/generic-traversal.tgz You will need that: http://www.oqube.com/projects/muse-java > and copy the html in? No. See above. -- 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Code Samples in Sites
Can you share the site source? Did you just manually run jhighlight and copy the html in? -Stephen On 9/23/06, Arnaud Bailly <[EMAIL PROTECTED]> wrote: http://www.oqube.com/projects/object-traversal/visitor.html Sorry, this example is in french :-) -- 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Code Samples in Sites
Has anyone investigated or worked on syntax highlighting of code samples in site documentation? Compare the code examples http://www.stephenduncanjr.com/projects/easymock-propertyutils/index.html vs. http://www.stephenduncanjr.com/2006/09/easymock-propertyutils-example.shtml I used jhighlight to do the highlighting on the blog version: https://jhighlight.dev.java.net/ I don't know if there are better alternatives out there for the syntax highlighting library. My point is that it would be really cool to have this highlighting for documentation produced by the maven site plugin. Is there something out there already like this? If not, what are the options for making it happen someday? I'm still relatively new to actually using the site plugin, and have only used APT so far. Which formats would it be possible to add this to, and which are either not modifyable, or not feasible targets? Should I just open a JIRA issue for this, or what? -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XPath Replacement Plugin: Looking for Feedback
An issue I forgot. My implementation requires Java 5. If there's interest from those who can't live with that, I will heartily welcome alternative implementations. - Stephen On 9/21/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: I'm looking for some feedback on a project I started: http://www.stephenduncanjr.com/projects/xpathreplacement-maven-plugin/index.html The basic motivation behind creating this plugin is to get the type of benefits that filtering gets you, without having to put in placeholder expressions. I mostly develop web-apps, and I prefer to develop directly out of the source folders for the most part (using Eclipse WTP). Using placeholders in things like web.xml, or spring configuration files prevents me from doing that, and I'm stuck back at the build->deploy->test cycle. In my mind, this plugin can help solve that. My questions are: 1) Is anybody else interested in this at all? 2) Naming? I hate naming, so names for both the plugin and the goals are welcome. 3) Is the namespace configuration clear enough? 4) Should the parser not be namespace-aware when you don't specify a namespace mapping? 5) What shoud the real usage look like? For now it's very simple: one goal that lets you process a single file, and by default puts that file into the root of target/classes. While I have some other ideas on what the answers to 5 might be, I'd rather hear other peopele's ideas first. -- Stephen Duncan Jr www.stephenduncanjr.com -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
XPath Replacement Plugin: Looking for Feedback
I'm looking for some feedback on a project I started: http://www.stephenduncanjr.com/projects/xpathreplacement-maven-plugin/index.html The basic motivation behind creating this plugin is to get the type of benefits that filtering gets you, without having to put in placeholder expressions. I mostly develop web-apps, and I prefer to develop directly out of the source folders for the most part (using Eclipse WTP). Using placeholders in things like web.xml, or spring configuration files prevents me from doing that, and I'm stuck back at the build->deploy->test cycle. In my mind, this plugin can help solve that. My questions are: 1) Is anybody else interested in this at all? 2) Naming? I hate naming, so names for both the plugin and the goals are welcome. 3) Is the namespace configuration clear enough? 4) Should the parser not be namespace-aware when you don't specify a namespace mapping? 5) What shoud the real usage look like? For now it's very simple: one goal that lets you process a single file, and by default puts that file into the root of target/classes. While I have some other ideas on what the answers to 5 might be, I'd rather hear other peopele's ideas first. -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin Documentation and the Index Page
Thanks. (Notes for anyone else: 2.0.5-SNAPSHOT builds are here: http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/ ) -Stephen On 9/21/06, Brett Porter <[EMAIL PROTECTED]> wrote: It was a bug in the current release of the plugin plugin. You can use the new version, but it also requires a snapshot of maven 2.0.5. I'm hoping to work on correcting that shortly, but for now if you grab a Maven nightly and build the plugin plugin from SVN you should be good to go. - Brett On 22/09/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: > I'm working on a new maven plugin (see an upcoming e-mail soon), and > I'm trying to create the site generally matching the best > practices of the new maven plugin sites. I'm having trouble though: I > have an src/site/apt/index.apt, but the contents of index.html is the > auto-generated plugin documentation. Am I doing something wrong? Is > there some workaround? > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Apache Maven - http://maven.apache.org "Better Builds with Maven" book - http://library.mergere.com/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Plugin Documentation and the Index Page
I'm working on a new maven plugin (see an upcoming e-mail soon), and I'm trying to create the site generally matching the best practices of the new maven plugin sites. I'm having trouble though: I have an src/site/apt/index.apt, but the contents of index.html is the auto-generated plugin documentation. Am I doing something wrong? Is there some workaround? -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven+Checkstyle - Configuration file location
tyle.xml), using maven > > variables ($project.dir/mycheckstyle.xml) but without success, always with > > one or another error message from maven such as > > > >Unable to find location '../mycheckstyle.xml' as URL, File or Resource. > > > > Is there any way to combine maven's knowledge of the project/components > > tree > > so that each individual component knwos the top level and use it to locate > > the mycheckstyle.xml. Even better: is there a way to support component > > with > > different level in the tree (as subComponent2 and subComponent2.1 in the > > example above) > > > > Thanks, > > Olivier > > > > > > > > - > > 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Checksum problem
On 9/18/06, Brett Porter <[EMAIL PROTECTED]> wrote: On 19/09/2006, at 4:32 AM, Stephen Duncan wrote: > (Aside: How could I > configure the central repository to treat checksum errors as failures > normally in settings.xml?) fail inside So, define a repository in settings.xml with an id of "central", (even though I'll also have a mirror for central)? > Is there some way to maybe due a scan of > central to find out the list of invalid checksums? Archiva can do that, and we'll be repairing problems in the not too distant future. Great - Brett -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Checksum problem
I've noticed the same thing. I started trying to use Archiva as a proxy, and noticed that items failed to resolve due to checksum errors. I don't have a problem with that in theory, but there appear to be several plugins on the central repo with bad checksums. I opened an issue about the one I noticed (the war plugin), but I've noticed some others when using Maven regularly. (Aside: How could I configure the central repository to treat checksum errors as failures normally in settings.xml?) Is there some way to maybe due a scan of central to find out the list of invalid checksums? -Stephen On 9/18/06, VAUCHER Laurent <[EMAIL PROTECTED]> wrote: Trying to do a 'mvn archetype:create', I encounter checksum errors from the IBiblio repository. When Maven is configured to go directly to IBiblio, I get a warning, but when I configure a proxy, it's archiva that gets the warning and it seems to treat it as a blocking error. It does not deliver the plugin to the maven 'client'. Is there a way to configure it to be less picky? Are files on IBiblio corrupted? Does anybody care? (The files in question seem to be several months old 1.0-alpha-4). Laurent. -- Stephen Duncan Jr www.stephenduncanjr.com
Re: Maven+Checkstyle - Configuration file location
My experience is that this won't work for people who have not manually installed the shared project; the dependency won't be downloaded from an internal repository, it will only try "central" (you won't see this if you use a proxy & mirror for central I guess). I believe the correct way to do this is by declaring acompany:acompany_style as an extension. acompany acompany_style 1.0-SNAPSHOT -Stephen On 9/4/06, Roy van der Kuil <[EMAIL PROTECTED]> wrote: Hi, We have a similar setup and have created a 'project' with only a couple of resources. (our own version of the checkstyle xml and suppressions). We deployed this 'jar' and made the maven-checkstyle-plugin dependant on that dependancy: org.apache.maven.plugins maven-checkstyle-plugin acompany acompay_style 1.0-SNAPSHOT This actually works very well and makes sure every project uses the 'latest' style. On 9/4/06, Olivier Vierlinck <[EMAIL PROTECTED]> wrote: > > We use maven+checkstyle on a multi-project. > > We have defined our checks (mycheckstyle.xml) for one of the component. > The > xml file is stored right at the root of the component (next to the src and > target folders) in the top pom file we have: > > > org.apache.maven.plugins > maven-checkstyle-plugin > > mycheckstyle.xml > > > > So we have a structure like this > >topProject >--- pom.xml > >--- subComponent1 >--- --- src >--- --- target >--- --- pom.xml >--- --- mycheckstyle.xml >--- --- ... > >--- subComponent2 >--- --- src >--- --- target >--- --- pom.xml >--- --- ... > >--- --- subsubComponent2.1 >--- --- --- src >--- --- --- target >--- --- --- pom.xml >--- --- --- ... > > This works fine. But now, we would like to use the same configuration file > for ALL our component. So, we would like to have our (single) > mycheckstyle.xml file stored only once, right under the topProject, next > to > the top pom.xml file. > > How can we define that in the pom file. I tried using relative path > (../mycheckstyle.xml), full url (file:../mycheckstyle.xml), using maven > variables ($project.dir/mycheckstyle.xml) but without success, always with > one or another error message from maven such as > >Unable to find location '../mycheckstyle.xml' as URL, File or Resource. > > Is there any way to combine maven's knowledge of the project/components > tree > so that each individual component knwos the top level and use it to locate > the mycheckstyle.xml. Even better: is there a way to support component > with > different level in the tree (as subComponent2 and subComponent2.1 in the > example above) > > Thanks, > Olivier > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Real world uses for adding peer directories besides main/ in src/ ?
Well, primarily, there's "test" and "site" at the same level as "main"... -Stephen On 9/4/06, Dave Comeau <[EMAIL PROTECTED]> wrote: Are there any examples out there that use addition src/ directories besides main/ ? I have never had the need for this in my projects, but I realize that it provides room to expand/enhance your project cleanly. Just curious... -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: sql server jars
FYI: My experience is that the JTDS driver is better than the one from Microsoft anyway. -Stephen On 9/1/06, Geoffrey De Smet <[EMAIL PROTECTED]> wrote: Interesting, I think I 'll try this one as an alternative :) Wendy Smoak wrote, On 2006-09-01 4:03 PM: > On 9/1/06, Douglas Ferguson <[EMAIL PROTECTED]> wrote: > >> Are there sql server jars in central, of so what's the groupId? > > Are you looking for a JDBC driver for Microsoft SQL Server? > > Google turned up jTDS: http://jtds.sourceforge.net/ > > It's on ibiblio in groupId net.sourceforge.jtds > http://www.ibiblio.org/maven2/net/sourceforge/jtds/ > > HTH, -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: commons-lang 2.0 is newer than 2.1?
I'm not sure why adding it to your POM explicitly didn't work. What was the output of -X in that case? -Stephen On 8/24/06, Matt Raible <[EMAIL PROTECTED]> wrote: I need to have commons-lang-2.1.jar included in my WAR for displaytag-1.1. However, Acegi Security 1.0.1 depends on commons-lang-2.0.jar. From "mvn -X": org.acegisecurity:acegi-security:jar:1.0.1:compile ... commons-lang:commons-lang:jar:2.0:compile (selected for compile) displaytag:displaytag:jar:1.1:compile (selected for compile) commons-lang:commons-lang:jar:2.1:compile (removed - nearer found: 2.0) Why is 2.0 considered newer? I figured the fix would be to exclude commons-lang from acegi-security: org.acegisecurity acegi-security 1.0.1 commons-lang commons-lang However, this results in both 2.0 and 2.1 being added to my WAR. [DEBUG] adding entry WEB-INF/lib/commons-lang-2.0.jar [DEBUG] adding entry WEB-INF/lib/commons-lang-2.1.jar I tried adding the following to my pom explicitly, but no dice. commons-lang commons-lang 2.1 displaytag displaytag 1.1 Any ideas? Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: goal not found error
These questios probably better belong on the eXo mailing list. Manually downloading the jar & placing it in your repository will not work as far as I know. You should be able to set up http://maven.objectweb.org/maven2 as a pluginRepository, and have it download the plugin from there, but I've had no luck, and I don't really understand why it's not working (anybodye else? Some help?) Your best bet is probably to check out the eXo source code and install the plugin. -Stephen On 8/23/06, john_sh <[EMAIL PROTECTED]> wrote: You can use the fully-specified syntax for executing a goal, eg. "mvn :::" When using the short form of specifying a goal, maven, by default, only searches two groupIds: org.apache.maven.plugins and org.codehaus.mojo. Odds are the maven-evo-plugin is not in either of these groups and that's why she doesn't find the evo plugin. You can modify the groupIds maven searches when using the short form by adding the following to your settings.xml: some.groupId some.other.groupId HTH, Doug -- thank u for ur reply but maven-exo-plugin exists in the org\apache\maven\plugins dir, and plugin groupId is set to the same groupId(org.apache.maven.plugin), and even when i specify the groupId and other properties in the command line it says that "required goal not found: org.apache.maven.plugins:maven-exo-plugin:1.0:exo and please tell me from which path i must execute this command? from where my exo business process(which i want to create par file from that with maven with this plugin) is located or from maven bin dir? or? -- View this message in context: http://www.nabble.com/goal-not-found-error-tf2152081.html#a5946596 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PMD report plugin fails the build
Have you run with -U to get the latest version of the plugin? This used to happen to me, but stopped recently after running "mvn site -U" -Stephen On 8/9/06, Ciprian Duma <[EMAIL PROTECTED]> wrote: It's in the reports section. But I think the plugin calls first pdm-check and I can't tell it not to fail (or it ignores the option). On 8/9/06, Denis Cabasson <[EMAIL PROTECTED]> wrote: > > Add the pmd plugin to your reporting section instead of your build section, > and it shouldn't breal the build anymore (but still generate the report). > > Denis. > > > Ciprian Duma wrote: > > > > How can I configure the PMD plugin not to fail the build when > > generating the report? I tried passing the parameter "failOnViolation" > > with value "false" but it's ignored. And I dont want to configure this > > plugin in the "build" section, it should be called only when is site > > is generated. > > > > The classes that fail this report were automatically generated. > > > > Thx, > > > > Ciprian > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: http://www.nabble.com/PMD-report-plugin-fails-the-build-tf2077581.html#a5722804 > 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependency on two versions
While this is generally true, the problem/confusion is caused by the fact that the groupId for ehcach in version 1.1 is "ehcache", whereas for 1.2 it is "net.sf.ehcache", cause Maven to treat them as different artifacts, and therefore both will be included unless ehcache 1.1 is explicitly excluded. A similar problem occurs when trying to use the full spring jar, and having to exclude individual spring jars that are transitive dependencies. - Stephen On 7/26/06, Edwin Punzalan <[EMAIL PROTECTED]> wrote: Hi. Direct dependencies take precedence over transitive dependencies. Therefore, if you declare ehcache 1.2 in your pom.xml, then any transitive dependency of the same artifact but different version will not go into your project's classpath. No need to exclude if the problem is only the version. You need only to put the artifact with the version you want in your pom.xml. Hope that helps. ^_^ Satish wrote: > I have the following dependecies in my POM > - ecahce - 1.2 >- hibernate 3.1rc1 > > I have one of the package which depends on ecahce 1.2, but as part of > hibernate dependency, it downloads ecache1.1. There are some method > signatures change between ecache 1.1 and 1.2 and this results in the compile > error as the end, i assume > ecache 1.1 is taking the precedence in the classpath. > > any tips to resolve this. > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Super Pom
You can choose to make a "super-pom" that all your projects inherit from to provide common configuration. - Stephen On 7/26/06, Lakshman Srilakshmanan <[EMAIL PROTECTED]> wrote: Hi Emmanuel, Thanks for your reply. The http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html describes how to include a customised checkstyle within a POM. I need to know the location of the super POM itself, if one exists. Thanks Lakshman > -Original Message- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Wednesday, 26 July 2006 5:28 PM > To: Maven Users List > Subject: Re: Super Pom > > http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html > > Lakshman Srilakshmanan a écrit : > > Hi All, > > > > I have used maven 1.x for a couple of years now and am in the process of > > migrating to maven 2.x > > > > I need to set some configuration globally (eg customised checkstyle). I > > find the appropriate place would be to include it in the super pom. > > > > Unfortunately I don't seem to be able to find it. Could you please > > direct me to where it is located. > > > > Thanks > > Lakshman > > > > > > - > > 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: deploying jars without version information
Use the Antrun plugin: http://maven.apache.org/plugins/maven-antrun-plugin/ to run an Ant script, and attach that to the package phase of your Maven build. - Stephen On 7/25/06, Trent Albright <[EMAIL PROTECTED]> wrote: > Note you can change the names of jars/wars > within an ear so that the module URI in the application.xml does not > need to change with every version increment. How? Do tell! =) > As Chris mentioned, the best way is to add a copy step after the fact > which renames the file to your legacy format and uploads to the server. What is the "maven2 way" of doing this? Creating a custom script that is executed from instructions in the POM after a certain phase? Or are you suggesting I write a script to be run completely seperate from the execution of the maven2 build? I'm new to maven so if you could point me in the general direction, I can read up and take it from there. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM with Resources
Except that the build-tools jar should be referred to as an extension, not a dependency of the plugin. My experience was that Maven would only try ibiblio to look for the build-tools jar if I left it as a plugin dependency. See the bottom of this checkstyle plugin doc for an example: http://maven.apache.org/plugins/maven-checkstyle-plugin/customize.html -Stephen On 7/24/06, dcabasson <[EMAIL PROTECTED]> wrote: Nick Panienski wrote: > > As far as I know I cannot include XMLs in a project that has a > pom. I already tried to build a resources project > packaged as a jar and define a dependency in my parent pom. Maven doesn't > complain about this, but I still don't know how to access my config > files... > Common practice is indeed to have a build-tools module, with packaging jar. To use this module (with checkstyle), in the build/plugins part, of your parent POM: org.apache.maven.plugins maven-checkstyle-plugin com.myApplication build-tools 1.2-SNAPSHOT your_checks.xml Every sub-project will now use this checkstyle configuration. Denis. -- View this message in context: http://www.nabble.com/Parent-POM-with-Resources-tf1990950.html#a5463782 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Copy Files Plugin
I'm wondering if there's anything out there like this already, or being planned. Basically what I'd like to see is the ability to deploy a file somewhere arbitrary. It shoudl reuse the wagon stuff, so that all the same protocols supported for repository deployment are still available. My specific use case is that I want to copy a checkstyle configuration file to a location on a webserver to be used in IDE's whenever I release my jar that contains that configuration file (for use in Maven). The webserver location is the same as my repository: I can only access it via sftp. So I'd want be able to reuse my authentication settings from settings.xml. -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven-Dependency-Plugin
I'd to at least see a site push. mojo.codehaus.org no longer has the site, and the link on maven.apache.org is broken: http://maven.apache.org/plugins/maven-dependency-plugin/ - Stephen On 7/19/06, Brian E. Fox <[EMAIL PROTECTED]> wrote: It's not abandoned, just neglected. I intend to resume cleaning it up shortly and release a beta. The current code should work, it was pretty much done when I last worked on it. There where some new features that started in 1.1 that didn't get fully finished yet, but the core of the 1.0 functionality (plus resolve) is done. -Original Message- From: dan tran [mailto:[EMAIL PROTECTED] Sent: Monday, July 17, 2006 1:14 PM To: Maven Users List Subject: Re: Maven-Dependency-Plugin maven-dependency-plugin-2.0-SNAPSHOT is stable for me + if we can cut a beta release -D On 7/17/06, Alexander Rau <[EMAIL PROTECTED]> wrote: > > hi all, > > I recently needed to find a way downloading all dependencies before > starting any work on my projects. > > After trying different "solutions" which were not what I want I found > the maven-dependency-plugin with its goal resolve. Perfect. > > However I can't clearly determine the current state of the plugin. > Version 1.0.x seems to be somehow outdated (resolve goal non-existent) > and the plugin moved from codehaus to apache. The project website > (linked on maven.apache.org on the plugins section) is broken. However > there's a 2.0-SNAPSHOT. > > Does anyone know if the plugin is orphaned ? I'd appreciate a 2.0 > release as the plugin seems (at least for me) stable :) > > > Regards, > > Alex > > - > 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] dependencyManagement question ?
Well I don't agree that dependencyManagement should override what's specified as a hard dependency in the child POM, applying to transitive dependencies is certainly a valid use case: http://jira.codehaus.org/browse/MNG-1577 - Stephen On 7/17/06, David Smiley <[EMAIL PROTECTED]> wrote: Is there a reason why versions specified in dependencyManagement only apply to dependencies which don't have a version specified? In other words... why not have it specify the dependency regardless of whatever is specified in some child pom? The use case here is for 3rd party pom's transitively brought in like cglib for example. Hibernate depends on cglib... and so does SpringFramework's AOP stuff. I'd like to specify at the top level of my project which version I want chosen without having to introduce a hard dependency via directly since my project does not directly use cglib. -- View this message in context: http://www.nabble.com/-m2--dependencyManagement-question---tf864496.html#a5363288 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is maven seeing another jar?
Is it possible you have a different copy of the jar somewhere else on your classpath? Such as in $JAVA_HOME/jre/lib/ext? (This occurred recently to a coworker of mine, so...) - Stephen On 7/17/06, Jeff Mutonho <[EMAIL PROTECTED]> wrote: One of my projects module is failing to build with the message : D:\M2-WORK\eportal-services\src\za\co\mycompany\portal\services\PersonServiceImpl.java:[111,69] cannot find symbol symbol : method getClarifyAccountKey() location: class za.co.mycompany.portal.Organisation This class Organisation is in a jar called eportal-domain-1.0.0.jar and its included in the classpath as shown from the m2 debug output shown below: DEBUG] Output directory: D:\M2-WORK\eportal-services\target\classes [DEBUG] Classpath: [DEBUG] D:\M2-WORK\eportal-services\target\classes [DEBUG] D:\Documents and Settings\mutonhj\.m2\repository\za\co\mycompany\eportal\eportal-domain\1.0.0\eportal-domain-1.0.0.jar [DEBUG] D:\Documents and Settings\mutonhj\.m2\repository\javax\j2ee\j2ee\1.3.0\j2ee-1.3.0.jar I opened the eportal-domain-1.0.0.jar using winrar and opened the Organisation.class file using cavaj(a decompiler) and the method getClarifyAccountKey() exists in the class. What am I missing? -- Jeff Mutonho GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse, WTP & Maven2
I don't know about the plugin for Eclipse, but mvn eclipse:eclipse with wtpversion set to 1.0 integrates just fine with WTP. - Stephen On 7/12/06, Trent Nelson <[EMAIL PROTECTED]> wrote: The last time I looked into it, the coherency between Eclipse's Maven2 plugin (http://m2eclipse.codehaus.org/) and Maven2's eclipse:eclipse was quite poor; each one didn't seem to know about the other, and you certainly couldn't use both in harmony. What's the state of play now? Can 'mvn eclipse:eclipse' be made to produce an Eclipse environment that the Eclipse Maven2 plugin plays nicely with? Also, what's the state of all of the above when it comes to WTP support? Can all three components be coerced to play together nicely? The last time I tried, if I created a WTP-enabled web project directly in Eclipse (or MyEclipse in my case), I'd get all the nice warm and fuzzy features offered by WTP, but lost all the project/library management offered by Maven2. (And vice-versa with regards to taking the Maven2 approach; I'd have to 'mvn compile|deploy' to push code changes I was making back onto the app server.) Regards, Trent. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Eclipse Plugin
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html You can set additionalProjectnatures, or projectnatures - Stephen On 7/9/06, Markus Wolf <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, is there a way to add specific eclipse project natures to the generated .project file using the maven-eclipse-plugin (like spring nature or new dali persistence nature)? In maven 1.x there where some properties in the build.properties to set with which most of the project files could be customized. Thanks Markus Wolf - -- > > emedia-solutions wolf > Wedeler Landstrasse 63 > 22559 Hamburg > (040) 550 083 70 > >> web: http://www.emedia-solutions-wolf.de >> mail: [EMAIL PROTECTED] >> pgp: http://wwwkeys.de.pgp.net > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEsVoZeyJE91ndMG4RAtNAAJ4voUNiTScqpRyy73ILuyTwGcWsBwCbBzue 2qtJ6kgiX33Gm3594kWpqpM= =hkwe -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.4's 'package' not copying contents or main resources to WEB-INF/classes
No, src/main/resources is the correct location. -Stephen On 7/7/06, Jesse McConnell <[EMAIL PROTECTED]> wrote: pretty sure you want to put that stuff in src/main/webapp/WEB-INF/classes On 7/7/06, Vinny <[EMAIL PROTECTED]> wrote: > One additional datapoint: the files are being copied > to target/classes correctly just not to target//WEB-INF/classes > > On 7/7/06, Vinny <[EMAIL PROTECTED]> wrote: > > Hello, > > I thought the standard behavior for 'package' would be to copy > > all files from src/main/resources to WEB-INF/classes. The issue > > I'm facing is with my spring applicationContext.xml file. I want to make that > > file available to both my tests and to be put into my webapp. I though > > having it in > > src/main/resources would solve that problem, but it's not being > > copied into the > > webapp anywhere. Currently I have to keep 2 copies. Is this the > > expected behaivior? > > > > -- > > Ghetto Java: http://www.ghettojava.com > > > > > -- > Ghetto Java: http://www.ghettojava.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- -- jesse mcconnell [EMAIL PROTECTED] --------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Overriding dependencies
From Project A? In project A's pom: project-b project-c project-d - Stephen On 7/5/06, Jose Gonzalez Gomez <[EMAIL PROTECTED]> wrote: Hi there, Is there any way to override a dependency in a project you depend on? I know you can control which version of a dependency you use using the dependency management section, I mean the folowing: Project A +-> Depends on project B +-> Depends on project C Is there any way to point the dependency on project C to another project? I'm asking this because I'm using the hibernate annotations project, and that seems to point to javax.persistence:ejb:jar:3.0-public-draft-20060502, that doesn't seem to exist anymore. I guess annotations would work properly changing that dependency to javax.persistence:persistence-api:1.0. Best regards Jose -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn install with sources?
Run "mvn -DperformRelease=true clean install" - Stephen On 7/5/06, Aleksei Valikov <[EMAIL PROTECTED]> wrote: Hi. I'd like to get sources for my jar artifacts installed into the local repo. I usually do mvn (clean) install, but this only builds and copies the binary jar into the repo. What should I do to get sources along? Bye. /lexi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Need to include ONLY a new version of a transitive dependency
Well, 'mvn clean' would not cleanup src/main/webapp/WEB-INF/lib. Those files are treated as valid source. -Stephen On 7/2/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: On 7/2/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: > On 7/2/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > > > I would: > > 1. declare a dependency on the correct version of Y > > 2. add an exclusion to the X dependency, excluding its transitive > > dependency on Y > > > > -- > > Wendy > > This is a bad idea currently due to: http://jira.codehaus.org/browse/MNG-1797 Thanks. In this case I think the two Y's are really "different". Otherwise there's no way that both of them would be ending up in WEB-INF/lib. (Unless, as you suggested, it's a simple matter of 'mvn clean' not having been run recently...) -- Wendy --------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Need to include ONLY a new version of a transitive dependency
On 7/2/06, Wendy Smoak <[EMAIL PROTECTED]> wrote: I would: 1. declare a dependency on the correct version of Y 2. add an exclusion to the X dependency, excluding its transitive dependency on Y -- Wendy This is a bad idea currently due to: http://jira.codehaus.org/browse/MNG-1797 -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Need to include ONLY a new version of a transitive dependency
It should not occur that the older version is included if you specify a new version directly in your pom. Can you provide more details? Also, make sure the older version is not your source tree (for instance, already in src/main/webapp/WEB-INF/lib from running war:inplace or something like it) - Stephen On 7/2/06, Brad O'Hearne <[EMAIL PROTECTED]> wrote: I have a project which is dependent on a resource we'll call "X". X is dependent on a resource called "Y", so in my pom, I am only specifying the direct dependency on X. My project builds a WAR, and when packaged, X and Y are included. Everything's fine so far. But it turns out, for various reasons, I actually need a newer version of Y, than the one that X is specifying. If I specify the newer version of Y in my pom.xml file, when packaged, both versions of Y are included -- not what I want. So if I specify both versions of Y in my pom.xml file, and list the scope of the older version as "provided" and the scope of the newer one as "compile", neither one is included. How can I get maven to include only the newer version of Y when packaging my WAR? Thanks, Brad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Transitive Dependency Questions
In either case, with Maven 2, the solution (as far as I know) is simply to directly declare your dependency on Bob's Ace Logger v1.0.1. Then you'll get that version. - Stephen On 6/30/06, Graham Lea <[EMAIL PROTECTED]> wrote: Hi all I am new to using Maven2 and am concerned about the behaviour of transitive dependencies. In particular, I foresee certain situations where automated transitive dependencies, controlled by a third party, could be a Bad Thing. I have documented two such situations below. If anybody knows of and can explain ways in which Maven attempts to handle or allows someone to themselves account for these kinds of situations, I would be most appreciative if you could describe it or give a reference. (Not to source code, please.) ;-) Thanks very much, Graham. *Scenario One* 1. Bob makes Bob's Ace Logger, v1.0 2. Sally makes Sally's Awesome Web Framework, v2.0, and it depends on Bob's Ace Logger v1.0 3. I tell Maven I want Sally's Awesome Web Framework, v2.0, and it automatically downloads both it and Bob's Ace Logger v1.0 4. Bob realises there is a crucial security flaw in v1.0 of his logger, fixes it and releases 1.0.1, which is interface- and functionally-compatible with 1.0 5. Sally doesn't know about Bob's security flaw or the update 6. Because Sally never updates her POM, my application continues to use the flawed logger *Scenario Two */(1-4 are the same)/* */1. Bob makes Bob's Ace Logger, v1.0 2. Sally makes Sally's Awesome Web Framework, v2.0, and it depends on Bob's Ace Logger v1.0 3. I tell Maven I want Sally's Awesome Web Framework, v2.0, and it automatically downloads both it and Bob's Ace Logger v1.0 4. Bob realises there is a crucial security flaw in v1.0 of his logger, fixes it and releases 1.0.1, which is interface- and functionally-compatible with 1.0 / 5. Sally has been working on Sally's Awesome Web Framework, v3.0, and changes it to use the updated Bob's Ace Logger v1.0.1 6. For reasons known only to my manager, I am not allowed to upgrade to Sally's v3.0 framework, so have to continue using 2.0, which relies on Bob's flawed Logger 1.0 -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to generate -sources.jar on install/deploy
If you only want to do it sometimes, you can do it without modifications by running: "mvn package -DperformRelease=true" - Stephen On 6/28/06, Nicolas De Loof <[EMAIL PROTECTED]> wrote: Hello, I'd like my projects to automatically generate the -sources.jar when running mvn install or deploy. I've lokked for this at maven-sources-plugin but there is no doc. How to include sources jars in my build process ? Nico. This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Spring 2.0 M4 vs. M5
Do optional dependencies have any effect at all, or are they purely descriptive? Do they play a role in dependency version resolution, for instance if they are the "nearest" source of a dependency? Are there issues or wiki pages regarding the design of "optional" for Maven 2.1? (A bit off-topic, I suppose, but if Spring is going to have that many optional dependencies, I'll be having to deal with it a lot more in the future...) -Stephen On 6/20/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote: only one required, but all the others as optional On 6/20/06, Matt Raible <[EMAIL PROTECTED]> wrote: > Here's what the Juergen had to say: > > > We tried a number of different jar file arrangements and eventually went > with the all-encompassing spring.jar for 2.0 M5, as alternative to a > combination of fine-grained jars from the "modules" directory. The mock jar > is still separate, sitting alongside either spring.jar or a combination of > fine-grained jars. The same applies to the jar that contains the AspectJ > aspects. > > The line between what's within spring.jar and what's a separate jar was just > becoming too arbitrary, with the various O/R Mapping options on the one hand > and the various web integration options on the other hand. Hence, the > current plan is so stick with the "one-big-jar versus > many-fine-grained-jars" strategy for 2.0 RC1 and final again (just like we > had it in Spring 1.2.x). > > > Because of this, it seems to me that spring-2.0-m5 should have a POM > at http://www.ibiblio.org/maven2/org/springframework/spring/2.0-m5/ > with a single dependency - commons-logging. True? > > Matt > > On 6/19/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote: > > hehe, I think you have wrote to the wrong list! you have to ask Spring > > guys they are the official ones > > > > and M5 is not missing dependencies, it doesn't have pom at all! > > > > You can vote at > > http://opensource.atlassian.com/projects/spring/browse/SPR-1484 > > > > I'm opening another thread to poing Maven users there > > > > On 6/19/06, Matt Raible <[EMAIL PROTECTED]> wrote: > > > The spring.jar for 2.0 M4 didn't include > > > org.springframework.orm.hibernate*. The one for M5 does. The > > > spring-hibernate3.jar for M4 included Hibernate dependencies, the one > > > for M5 does not. Which is the correct way moving forward? Which way > > > will it be in 2.0 Final? > > > > > > Thanks, > > > > > > Matt > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > I could give you my word as a Spaniard. > > No good. I've known too many Spaniards. > > -- The Princess Bride > > > -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: assembly as a dependency
I think you add dep to the dependency declaration. -Stephen On 6/17/06, Ovidio Mallo <[EMAIL PROTECTED]> wrote: Hi everyone, when I install an assembly into my local repository, how can I reference it via a in my POM file? E.g. I have the Maven embedder assembly at ~/.m2/repository/org/apache/maven/maven-embedder/2.1-SNAPSHOT/maven-embedder-2.1-SNAPSHOT-dep.jar in my local repository. The embedder assembly descriptor has its set to "dep" which gets included into the filename in the repository. So, do I need to specify this ID in my declaration somehow to allow Maven to find the file? Thanks a lot for any help! Cheers, Ovidio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent vs. Multi Project super pom
On 6/13/06, Stefan Hübner <[EMAIL PROTECTED]> wrote: Hi Kenney, 2006/6/13, Kenney Westerhof <[EMAIL PROTECTED]>: > On Mon, 12 Jun 2006, Stephen Duncan wrote: > > Another advantage, more of convenience, of differ between parent and aggregating pom: you can have the parent pom at the same level as it's inherited poms. Thus in Eclipse I can edit at least the parent pom easily, since I can import it as a Eclipse project. This is not true for the aggregating pom, though. But since typically the parent pom is more often edited than the aggregating pom, this is fine by me. -- Stefan Note: With Eclipse 3.2, you can have overlapping projects, so it is possible to edit the aggregating pom that lives a directory above the modules. -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent vs. Multi Project super pom
I personally do more as you do.
I have team-wide "super-POMs" I have a primary one that has basic
url, issue management, etc. type settings. Then I have a "core" POM
with common dependencyManagment section to encourage use of the same
versions of Jar's to prevent incompatibilities, as well as common
reporting configuration. Then I have a "webapp" parent POM that
specifically states the provided dependencies for webapps to be
deployed to our target server, as well as webapp specific stuff, such
as setting ${project.artifactId} to remove the
version number from wars, and 1.0 for the
Eclipse plugin.
For multi-module project, I have an aggregating POM that defines the
modules, but each module uses the appropriate "super-POM" as its
parent, not the aggregating POM.
I've found this to work better for us. But I too have been wondering
what the reasoning for the pattern of using the aggregating POM also
as the parent POM is...
-Stephen
On 6/12/06, Stefan Hübner <[EMAIL PROTECTED]> wrote:
Hi all,
this is kind of a best-practise-question about your habbits of using
the concepts of multi-project-super-pom.
First of all, are there distinctive terms commonly agreed upon for
each of those concepts?
Second, those two ways of using POMs appear to me to be orthogonal to
each other, really. Parent POMs are used to define common
characterisitics for a group of projects. Multi Project POMs on the
other hand aggregate modules belonging to a greater project. I usually
have the habbit of defining two diffent poms for multiproject
situations. e.g.:
/multiproject-pom X
-parent-pom Y
-module A / pom A (parent pom: Y)
-module B / pom B (parent pom: Y)
In most examples found though (e.g. in maven's own sources themselfs)
typically multi project poms at the same time are used as parent poms
for those modules they aggregated.
So, what I can't get my head around yet is, is it just a matter of
habbit or taste to combine those two usages in just one POM? or am I
really missing something important here, if I define two distinctive
POMs the way described above.
I'm thinking about this for quite a while now and any clarification
would be much appreciated.
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen Duncan Jr
www.stephenduncanjr.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 sources/javadocs installation question
You can simply run mvn -DperformRelease=true install This will build source & javadoc jars & install them. No configuration option. -Stephen On 6/9/06, Matt Wheeler <[EMAIL PROTECTED]> wrote: Never mind my last email. I moved the plugin under build outside of profiles and added a package phase, and it works now. Matt W. -- NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -- -- Forwarded message -- From: "Matt Wheeler" <[EMAIL PROTECTED]> To: users@maven.apache.org Date: Fri, 09 Jun 2006 09:45:29 -0600 Subject: Maven 2 sources/javadocs installation question I have a project that I run install on to install the project and all of its sub project's main artifacts in the local repository. However, I would also like to "automatically" install the sources and the javadocs as well. I can generate these using sources:jar and javadoc:jar commands, however, I cannot get them to be automatically generated using the profile section in the pom that is shown in the documentation under "Introduction to the POM" at http://maven.apache.org/guides/introduction/introduction-to-the-pom.html. What would I need to do to make that example work? Also, even if I coudl get the profile to generate the source and javadoc jars, I am not sure how to install them. I assume that I could use install:install-file, but I woudl really like a more automated way if there is one. I have tried to install them manually, but the problem is that I can't get it to install in the same directory as the projects main artifact. For instance, say my project artifact is in .m2/repository/org/whatever/2.0-SNAPSHOT/stack-code-2.0-SNAPSHOT.jar. Well, if I then run a commond something like: mvn install:install-file -DartifactId=stack-code -DgroupId=org.lds.stack -Dpackaging=jar -Dversion=2.0-SNAPSHOT -Dfile=D:/Projects/Stack/stack-code/target/stack-code-2.0-SNAPSHOT-sources.jar Then, it overwrites the projects main artifact stack-code-2.0-SNAPSHOT.jar. However, if I change the version to 2.0-SNAPSHOT-sources, then it put the jar (this time with the correct name stack-code-2.0-SNAPSHOT-sources) out in the repository, but under a 2.0-SNAPSHOT-sources directory instead of under the 2.0-SNAPSHOT directory with the main artifact. I am am seeing sources placed correctly on ibiblio however, so I am just wondering what I am doing wrong, or if there is an easier way to accomplish this? Thanks, Matt W. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assembly Plugin & Snapshot Dependencies
Not sure. Like I said, this was experienced by a co-worker of mine. However, I ran mvn -U package to try to get the latest plugins, so I believe he was using the latest of each... -Stephen On 6/7/06, Edwin Punzalan <[EMAIL PROTECTED]> wrote: This is odd... I checked both the sources of jar and assembly plugin, and found that both are using getArtifacts().getFile() which should point to the same file. What version of the plugins are you using? Stephen Duncan wrote: > I noticed this when a coworker was having touble with the Netbeans IDE > plugin. In order to run a project, the Netbeans plugin sets up custom > profile that's sets the runtime information in the manifest > (classpath, main class, etc.) & also runs an assembly to put the > dependent jars in the right place, etc. > > The problem is with SNAPSHOT dependencies: the > true option in the jar plugin causes > entries such as myutility-1.0-SNAPSHOT.jar to be added to the > manifest. However, the assembly plugin resolves these dependencies as > myutility-1.0-20060212.050059-12.jar. This mismatch leads to > NoClassDefFound errors, of course. > > My temporary workaround was to use the dependency plugin to copy the > dependencies, which does use the SNAPSHOT version (this is just lucky > that it works though, due to: http://jira.codehaus.org/browse/MDEP-5 ) > > Is there another option? Should this be considered a bug in the > assembly plugin? > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Assembly Plugin & Snapshot Dependencies
I noticed this when a coworker was having touble with the Netbeans IDE plugin. In order to run a project, the Netbeans plugin sets up custom profile that's sets the runtime information in the manifest (classpath, main class, etc.) & also runs an assembly to put the dependent jars in the right place, etc. The problem is with SNAPSHOT dependencies: the true option in the jar plugin causes entries such as myutility-1.0-SNAPSHOT.jar to be added to the manifest. However, the assembly plugin resolves these dependencies as myutility-1.0-20060212.050059-12.jar. This mismatch leads to NoClassDefFound errors, of course. My temporary workaround was to use the dependency plugin to copy the dependencies, which does use the SNAPSHOT version (this is just lucky that it works though, due to: http://jira.codehaus.org/browse/MDEP-5 ) Is there another option? Should this be considered a bug in the assembly plugin? -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] No Java test frameworks found?
Try adding it directly to the project you are looking at rather than the parent (just for testing purposes). I did this yesterday on a project, adding: junit junit 3.8.1 test And the error went away. -Stephen On 5/25/06, Morgan Rachell <[EMAIL PROTECTED]> wrote: I tried that. Specifically, I added junit junit 3.2.8 test To my parent pom. But that didn't work. So I removed it and added back: org.apache.maven.plugins maven-surefire-plugin 2.1.3 Which made 'mvn test' work. Just for kicks, I changed the surefire version to 2.2 and got that original "No Java test frameworks found" build error. For reference, the only 3rd-party jars that I'm explicitly listing as a are: Spring 1.2.7 Hibernate 3.1.3 Struts 1.2.8 Log4j 1.2.8 Xercesimpl 2.7.1 Xml-apis 1.3.02 -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Thursday, May 25, 2006 3:30 PM To: Maven Users List Subject: RE: [m2] No Java test frameworks found? I had this problem and resolved it by placing an explicit dependency on JUnit. It seems that something in one of the other plugins I have been using had a reference to JUnit which made everything work right. The updated plugins removed that indirect reference and caused the problem. -Original Message- From: Morgan Rachell [mailto:[EMAIL PROTECTED] Sent: Thursday, May 25, 2006 14:49 To: users@maven.apache.org Subject: [m2] No Java test frameworks found? I had setup my project a few weeks ago and was running 'mvn install' (with JUnit tests, etc.) without problems. Someone new just joined my project and just did a 'mvn install', which first downloaded all plugins and dependencies, but then he got this error: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] No Java test frameworks found [INFO] We can reproduce the error with just a 'mvn test' command too. I noticed that his download was getting maven-surefire-plugin version 2.2. I was unable to duplicate the problem on my machine because I had version 2.1.3 of the plugin. When I deleted version 2.1.3 from local repository (actually, I foolishly deleted my entire local repo!) I got the same error. Now we're stuck and cannot get past this error. I should also mention that we use a mirror pointing to http://repo.mergere.com/maven2. It's much faster than ibiblio. Has anyone else experienced this problem or know how to get past it? Thanks, Morgan -- View this message in context: http://www.nabble.com/-m2-+No+Java+test+frameworks+found--t1682690.html# a4564033 Sent from the Maven - Users forum at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - 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] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant tasks executing twice
Possibly this bug: http://jira.codehaus.org/browse/MNG-2221 Which, by the way (to the larger group) is a pretty major bug related to the regressions fixed in 2.0.4? Can we get this looked at as a similarly critical bug for a 2.0.5 release? -Stephen On 5/15/06, Nick Bolton <[EMAIL PROTECTED]> wrote: I'm running into an issue with maven-antrun-plugin where it's executing the containing tasks twice. Has anyone come across this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven, dependencies and eclipse wtp
Using mvn -Dwtpversion=1.0 eclipse:eclipse works for me to get them added when deploying within Eclipse using WTP 1.0.2 & Eclipse 3.1.2. The applicable file that eclipse:eclipse generates is .settings/.component Make sure the dependencies that should be bundled are described in that file correctly. -Stephen On 5/15/06, Matthijs Wensveen <[EMAIL PROTECTED]> wrote: Fabrizio Giustina wrote: > On 5/10/06, Matthijs Wensveen <[EMAIL PROTECTED]> wrote: >> When I try to run the project on a server from within eclipse, the >> dependencies that would normally be in WEB-INF/lib are not deployed on >> the server. > > They should be deployed, probably you are using a buggy version of > WTP. WTP r7 shipped with this bug, which has also recently been > reintroduced in WTP 1.5 beta builds and fixed again in the latest rc. > > fabrizio > I haven't got it working yet. When I don't use the mergere m2eclipe plugin for eclipse, but only the mvn -Dwtpversion=1.0 eclipse:eclipse goal, the dependencies are added as M2_REPO/commons-collections/commons-collections/2.0/commons-collections-2.0.jar (for example). These are available in the war, but not when I run it on a server from inside eclipse. When I do use the m2eclipse plugin, the dependencies are added to the "Maven2 Dependencies" classpath container, but are not available to the webapp when I run it from inside eclipse. Again, they are added to the war when I package the app with "mvn package" Is there a way to add it to the configuration files manually? Somewhere in the .settings directory maybe? Matthijs - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XMLBeans Plugin + Eclipse Mayhem
Well, then I'd suggest just manually removing the project dependency & setting the repository dependency. Alternatively, you can try to add "target/generate-sources" as a source folder in the XSD project. It's not perfect, in that there will be a lot of errors shown about not being able to resolve something, but you can then refer to the XMLBeans classes elsewhere. That's what I'm doing now, since I have some extra classes inside my xmlbeans project. -Stephen On 5/5/06, Wilfred Springer <[EMAIL PROTECTED]> wrote: Hi Stephen, > Wilfred, I think you just need to run mvn install on the xmlbeans > project, and then run eclipse:eclipse on only the subproject so that > it uses the dependency in your local repository, instead of the > Eclipse project. The problem with that approach is that all of the other dependencies will also be turned into dependencies to jar files in M2_REPO, which is not what I want. (I have many more modules as siblings of 'project-client'.) > > -Stephen > > On 5/5/06, Domsch, Christian <[EMAIL PROTECTED]> wrote: > > Hi Wilfred, > > > > Yes I had the same problem and I think I have a working solution. The key is, that I wrote an additional plugin, that would generate a jar containing the generated sources and classes from xmlbeans. My normal project now includes this project. > > > > The process is like this: > > > > The normal XMLBeans Plugin generates ist sources and classes and puts them to a defined location. My plugin picks up thoses resources at the same location and builds the jar and installes it into the local repository. For this, my plugin runs in the process-resources phase. > > > > Now the project insode eclipse can resolve anything it needs, with one downside that you have to run the lifecycle one time outside eclipse for the initial generation of this jar. > > > > Greetings, > > > > Christian Domsch. > > > > P.S.: I attached the pom and the source for this plugin. > > > > > -Ursprüngliche Nachricht- > > > Von: Wilfred Springer [mailto:[EMAIL PROTECTED] > > > Gesendet: Freitag, 5. Mai 2006 08:20 > > > An: [EMAIL PROTECTED] > > > Cc: Maven Users List > > > Betreff: XMLBeans Plugin + Eclipse Mayhem > > > > > > Hi all, > > > > > > I am using the XMLBeans Maven Plugin in a couple of projects, > > > but using this plugin in combination with Eclipse is giving > > > me a headache. I was just wondering if somebody has already solved it. > > > > > > The layout of my project is a little like this: > > > > > > project > > > +--- pom.xml > > > +--- project-xml-binding > > > +--- pom.xml > > > +--- src/main/xsd/test.xsd > > > +src/main/xsdconfig/xsdconfig.xml > > > +--- project-client > > > +--- pom.xml > > > +--- src/main/java > > > > > > > > > The 'project-client' module depends on project-xml-binding. > > > The problem > > > is that client code in 'project-client' does not always see > > > the classes > > > or source files generated from the XMLBeans plugin. So > > > Eclipse is giving > > > a lot of warnings for missing class file definitions, I don't > > > have code > > > completion, and my tests do not always run when running it > > > from Eclipse. > > > > > > So the question is: how do I make sure that my client code has all of > > > the class definitions of the 'project-xml-binding' project, > > > and how do I > > > configure my poms to make sure that eclipse:eclipse is giving me the > > > proper project settings? > > > > > > Thanks, > > > > > > Wilfred > > > > > > Wilfred Springer | Software Architect | TomTom | > > > [EMAIL PROTECTED] | +31 646 720 990 > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Wilfred Springer | Software Architect | TomTom | [EMAIL PROTECTED] | +31 646 720 990 -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XMLBeans Plugin + Eclipse Mayhem
I don't think I understand why you did this. The normal xmlbeans plugin will produce a jar with the xmlbeans-generated code by default. I think Wilfred's problem is just that the eclipse:eclipse is giving him a project-dependcy for the sibling projects. Since Eclispe isn't generating the xmlbeans sources, this doesn't do anything for him. Wilfred, I think you just need to run mvn install on the xmlbeans project, and then run eclipse:eclipse on only the subproject so that it uses the dependency in your local repository, instead of the Eclipse project. -Stephen On 5/5/06, Domsch, Christian <[EMAIL PROTECTED]> wrote: Hi Wilfred, Yes I had the same problem and I think I have a working solution. The key is, that I wrote an additional plugin, that would generate a jar containing the generated sources and classes from xmlbeans. My normal project now includes this project. The process is like this: The normal XMLBeans Plugin generates ist sources and classes and puts them to a defined location. My plugin picks up thoses resources at the same location and builds the jar and installes it into the local repository. For this, my plugin runs in the process-resources phase. Now the project insode eclipse can resolve anything it needs, with one downside that you have to run the lifecycle one time outside eclipse for the initial generation of this jar. Greetings, Christian Domsch. P.S.: I attached the pom and the source for this plugin. > -Ursprüngliche Nachricht- > Von: Wilfred Springer [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 5. Mai 2006 08:20 > An: [EMAIL PROTECTED] > Cc: Maven Users List > Betreff: XMLBeans Plugin + Eclipse Mayhem > > Hi all, > > I am using the XMLBeans Maven Plugin in a couple of projects, > but using this plugin in combination with Eclipse is giving > me a headache. I was just wondering if somebody has already solved it. > > The layout of my project is a little like this: > > project > +--- pom.xml > +--- project-xml-binding > +--- pom.xml > +--- src/main/xsd/test.xsd > +src/main/xsdconfig/xsdconfig.xml > +--- project-client > +--- pom.xml > +--- src/main/java > > > The 'project-client' module depends on project-xml-binding. > The problem > is that client code in 'project-client' does not always see > the classes > or source files generated from the XMLBeans plugin. So > Eclipse is giving > a lot of warnings for missing class file definitions, I don't > have code > completion, and my tests do not always run when running it > from Eclipse. > > So the question is: how do I make sure that my client code has all of > the class definitions of the 'project-xml-binding' project, > and how do I > configure my poms to make sure that eclipse:eclipse is giving me the > proper project settings? > > Thanks, > > Wilfred > > Wilfred Springer | Software Architect | TomTom | > [EMAIL PROTECTED] | +31 646 720 990 > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: JUnit Eclipse vs. Maven Question
It still doesn't work. As I said before, setting it just in
doesn't even result it in being set at all. Any pointers on why that
might be?
-Stephen
On 5/3/06, Stephen Duncan <[EMAIL PROTECTED]> wrote:
I'll have him try it tomorrow. However, we initially had it in the
argLine, and it wasn't even setting the property at all (i.e.
System.getProperty("java.library.path") returned the default value,
not the value set in ). I guess I can only try to do both &
see what happens...
-Stephen
On 5/2/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
> On Tue, 2 May 2006, Stephen Duncan wrote:
>
> > Sorry, forgot to mention that I tried with forkMode set to once & with
> > it set to pertest. Still didn't work.
> >
> > Could it be that aren't passed to the JVM when it's
> > forked? They are only set afterwards?
>
> Took me some digging, but the system properties are loaded after the jvm
> is started. The only way to define them in time is to define command line
> arguments to the jvm: -Djava.library.path= AND use
> forkMode once or pertest.
> You could also configure environment vars like LD_LIBRARY_PATH but that's
> not really portable.
>
> Hope this helps,
>
> -- Kenney
>
> >
> > -Stephen
> >
> > On 5/2/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
> > > On Tue, 2 May 2006, Stephen Duncan wrote:
> > >
> > > Hi,
> > >
> > > The library path is only scanned on JVM startup; you can't modify it later
> > > and expect the JRE to load any additional libraries.
> > >
> > > You'll have to use forked tests for that to work. Try configuring the
> > > surefire plugin to have once, for instance.
> > >
> > > -- Kenney
> > >
> > >
> > > > I have a colleague with a problem running a JUnit test. It works in
> > > > Eclipse, but not with Maven.
> > > >
> > > > Basically, he uses a class that needs to load a native library. The
> > > > location of a directory to look for this native .so object is
> > > > specified with java.library.path.
> > > >
> > > > Initially, this value was not being set correctly because you must
> > > > specify it using , not . We fixed that,
> > > > and now a debug output indicates that
> > > > System.getProperty("java.library.path") does return correctly.
> > > > However, the error indicating that the native library could not be
> > > > found persists. Any ideas on where else to look or tips on
> > > > troubleshooting?
> > > >
> > > > --
> > > > Stephen Duncan Jr
> > > > www.stephenduncanjr.com
> > > >
> > > > -
> > > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > > --
> > > Kenney Westerhof
> > > http://www.neonics.com
> > > GPG public key: http://www.gods.nl/~forge/kenneyw.key
> > >
> > > -----
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> >
> > --
> > Stephen Duncan Jr
> > www.stephenduncanjr.com
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
> --
> Kenney Westerhof
> http://www.neonics.com
> GPG public key: http://www.gods.nl/~forge/kenneyw.key
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Stephen Duncan Jr
www.stephenduncanjr.com
--
Stephen Duncan Jr
www.stephenduncanjr.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: JUnit Eclipse vs. Maven Question
I'll have him try it tomorrow. However, we initially had it in the
argLine, and it wasn't even setting the property at all (i.e.
System.getProperty("java.library.path") returned the default value,
not the value set in ). I guess I can only try to do both &
see what happens...
-Stephen
On 5/2/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
On Tue, 2 May 2006, Stephen Duncan wrote:
> Sorry, forgot to mention that I tried with forkMode set to once & with
> it set to pertest. Still didn't work.
>
> Could it be that aren't passed to the JVM when it's
> forked? They are only set afterwards?
Took me some digging, but the system properties are loaded after the jvm
is started. The only way to define them in time is to define command line
arguments to the jvm: -Djava.library.path= AND use
forkMode once or pertest.
You could also configure environment vars like LD_LIBRARY_PATH but that's
not really portable.
Hope this helps,
-- Kenney
>
> -Stephen
>
> On 5/2/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
> > On Tue, 2 May 2006, Stephen Duncan wrote:
> >
> > Hi,
> >
> > The library path is only scanned on JVM startup; you can't modify it later
> > and expect the JRE to load any additional libraries.
> >
> > You'll have to use forked tests for that to work. Try configuring the
> > surefire plugin to have once, for instance.
> >
> > -- Kenney
> >
> >
> > > I have a colleague with a problem running a JUnit test. It works in
> > > Eclipse, but not with Maven.
> > >
> > > Basically, he uses a class that needs to load a native library. The
> > > location of a directory to look for this native .so object is
> > > specified with java.library.path.
> > >
> > > Initially, this value was not being set correctly because you must
> > > specify it using , not . We fixed that,
> > > and now a debug output indicates that
> > > System.getProperty("java.library.path") does return correctly.
> > > However, the error indicating that the native library could not be
> > > found persists. Any ideas on where else to look or tips on
> > > troubleshooting?
> > >
> > > --
> > > Stephen Duncan Jr
> > > www.stephenduncanjr.com
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
> > --
> > Kenney Westerhof
> > http://www.neonics.com
> > GPG public key: http://www.gods.nl/~forge/kenneyw.key
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen Duncan Jr
www.stephenduncanjr.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: JUnit Eclipse vs. Maven Question
Sorry, forgot to mention that I tried with forkMode set to once & with
it set to pertest. Still didn't work.
Could it be that aren't passed to the JVM when it's
forked? They are only set afterwards?
-Stephen
On 5/2/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote:
On Tue, 2 May 2006, Stephen Duncan wrote:
Hi,
The library path is only scanned on JVM startup; you can't modify it later
and expect the JRE to load any additional libraries.
You'll have to use forked tests for that to work. Try configuring the
surefire plugin to have once, for instance.
-- Kenney
> I have a colleague with a problem running a JUnit test. It works in
> Eclipse, but not with Maven.
>
> Basically, he uses a class that needs to load a native library. The
> location of a directory to look for this native .so object is
> specified with java.library.path.
>
> Initially, this value was not being set correctly because you must
> specify it using , not . We fixed that,
> and now a debug output indicates that
> System.getProperty("java.library.path") does return correctly.
> However, the error indicating that the native library could not be
> found persists. Any ideas on where else to look or tips on
> troubleshooting?
>
> --
> Stephen Duncan Jr
> www.stephenduncanjr.com
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Kenney Westerhof
http://www.neonics.com
GPG public key: http://www.gods.nl/~forge/kenneyw.key
---------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Stephen Duncan Jr
www.stephenduncanjr.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JUnit Eclipse vs. Maven Question
I have a colleague with a problem running a JUnit test. It works in
Eclipse, but not with Maven.
Basically, he uses a class that needs to load a native library. The
location of a directory to look for this native .so object is
specified with java.library.path.
Initially, this value was not being set correctly because you must
specify it using , not . We fixed that,
and now a debug output indicates that
System.getProperty("java.library.path") does return correctly.
However, the error indicating that the native library could not be
found persists. Any ideas on where else to look or tips on
troubleshooting?
--
Stephen Duncan Jr
www.stephenduncanjr.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Problem When Mirror is Down
It appeared that the http://ibiblio.lsu.edu/main/pub/packages/maven2 mirror was down earlier today. This had the effect that when a user with no repository, or when running with -U, the maven-metadata-central.xml was essentially empty (just a reference to LATEST, I think...), and therefore couldn't be found. In either case (new user or -U), when switching back to the central repo instead of the mirror, you have to run with -U again to get the new version of the file, and therefore get the plugins, etc. I guess I'm asking for two things: a better indication that the mirror was down (error message) & when a mirror is down, not replacing the maven-metadata-central.xml file so that -U is not needed when turning off the mirror in my settings.xml. -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jetty out of memory reloading spring app
Also look at the second question in this FAQ: http://tomcat.apache.org/faq/deployment.html It explains why reloading an app causes this problem to show up more quickly. The description sounds like it would apply to any container that uses multiple classloaders, not just Tomcat, so it's likely true for Jetty as well. -Stephen On 4/20/06, Rolf Strijdhorst <[EMAIL PROTECTED]> wrote: > Hi is this a problem with perm memory? if so I think it is the same problem > Matt Railble describes on his blog: > http://raibledesigns.com/page/rd/20060419 > > the fix is to collect the memory consumtion data and express a solution on > that problem by setting the perm mem size accordingly -XX:MaxPermSize=256m > to MAVEN_OPTS. > Matt says it to add to JAVA_OPTS but that doesn't really work for maven. > > On 4/20/06, Burkhard Graves <[EMAIL PROTECTED]> wrote: > > > > Hi, just a small remark: > > > > I experienced similar out-of-memory problems with my > > spring/hibernate-app after around 10 or 12 reloads - but under tomcat > > 5.5.12! I'm switching to jetty right now - as soon as everything is > > running (actually some other problems hinder me ;-) I'll tell you if I > > still have out-of-memory problems... > > > > Regards > > Burkhard > > > > Jan Bartel schrieb: > > > Hi dub, > > > > > > The jetty maven plugin is up to release beta14 > > > so I would give that a go and see if it helps > > > with your memory issue. > > > We don't currently have any reported issues with out-of-memory problems > > > for the plugin. The webapp > > > classloader is ditched and then re-created on > > > each restart so stuff loaded from the webapp's > > > dependencies and classes should not be leaking. > > > > > > Are the spring jars explicitly on the plugin's classpath or are they as > > > dependencies of the > > > project? > > > > > > regards > > > Jan > > > > > > > > > gdub wrote: > > >> I use the jetty6:run (6.0 beta 9) target > > >> to launch Jetty with my web app under > > >> integration. > > >> > > >> It has a not-too-extensive Spring/Hibernate > > >> configuration. Jetty detects code changes > > >> just fine but after maybe 10 reloads, it > > >> starts reporting out-of-memory problems > > >> and refuses to reload. The machine isn't > > >> out of memory so it's the JVM itself that > > >> hits a wall. > > >> > > >> Is this a known Jetty plug-in problem? Or > > >> should I be looking for memory leaks in > > >> Spring and Hibernate (or, e gads, my own > > >> code). Is there something I need to > > >> configure to make sure that Jetty releases > > >> all app objects before reloading? > > >> > > >> BTW, I also ran into out of memory > > >> problems under surefire when running > > >> integration tests but was able to solve > > >> it by using a singleton Spring application > > >> context as a class member. But it leads > > >> me to think that my Spring context isn't > > >> releasing everything when it stops being > > >> referenced (closing the context and > > >> explicitly setting all references to it > > >> null helped me get about 10 more tests > > >> in a run). > > >> > > >> This is really only an issue during this > > >> final integration phase so it's not too > > >> big a deal but it does stop the thought > > >> flow when it happens. It's also an appli- > > >> cation confidence issue but I will do > > >> some memory profiling later. > > >> > > >> > > >> TIA, > > >> > > >> -dub > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Remove mavern folder in META-INF
What about the version number in the manifest? Personally, I'd rather build the artifact with just a version number change once the product is ready for release, to take advantage of Maven properly providing the version number in the Manifest, etc. -Stephen On 4/13/06, Gunther Popp <[EMAIL PROTECTED]> wrote: > I had the same issue with jars and am currently using the 2.1-SNAPSHOT > of the jar-plugin to exclude the pom.xml and pom.properties from the > generated file. One problem with the included pom is that it contains a > version number (in my case 1.2.0-SNAPSHOT). I am running an integration > build every night and deploy a new snapshot-build of the product to an > internal repository. Other guys pick up the builds and verify them. At > some point in time, hopefully, we decide that the product is ready and > release it - as is. We explicitly do NOT want to modify the artifact in > any way. > > However, if the pom.xml is included in all the jars, the version number > contained within will state "1.2.0-SNAPSHOT" for a released product. > That´s not a big issue, but I simply dislike it. So it decided to > exclude the poms from the beginning from all jars. > > Gunther > > Wayne Fay schrieb: > > Just curious why you care about this? It doesn't affect/break anything > > for me, so I've just ignored it until now. > > > > (You're not the only person to ask this question on the users list, so > > I'm wondering what issues people are running into etc, and if perhaps > > this "create META-INF/maven folder" is something that should be > > defaulted to false if its causing problems for people...) > > > > Wayne > > > > On 4/13/06, RobJac <[EMAIL PROTECTED]> wrote: > > > >> My EJB project has a META_INF folder that i have placed under "resources" > >> folder When I execute maven package for my project. The project gets jarred > >> but when I actually open the Jar file i see some maven folder under the > >> META-INF folder. How can i avouid this from getting created? > >> Thanks in advance > >> > >> -- > >> View this message in context: > >> http://www.nabble.com/Remove-mavern-folder-in-META-INF-t1444885.html#a3902183 > >> 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] > > -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Need to Package w/o executing Test
mvn -Dmaven.test.skip=true package -Stephen On 4/12/06, RobJac <[EMAIL PROTECTED]> wrote: > > I have a src/main and src/test folders in my project. All the Test classes > will not pass if i execute them. But I still would want package my project > even if my Test does not execute . When i run "mvn package" command, it > tries to execute my test which fails and will not allow me to create a jar. > Is there a way i can over ride this so that i can package atleast the files > under my src/main folder? > > Thanks in advance. > Robin > -- > View this message in context: > http://www.nabble.com/Need-to-Package-w-o-executing-Test-t1438538.html#a3883045 > Sent from the Maven - Users forum at Nabble.com. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PMD, CPD, cobertura, jdepend, etc. etc. on my project site
You can cut that to "mvn clean install site-deploy" :) Although, if you're deploying the site, wouldn't you deploy the artifact too? "mvn clean deploy site-deploy"? -Stephen On 4/11/06, Mike Perham <[EMAIL PROTECTED]> wrote: > That's what the POM element is for. All reports in > are run when site:site is run. Our build is just "mvn clean install > site:site site:deploy" and includes 5-6 different report plugins (javadoc, > pmd, cpd, jxr, project-info, etc) > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 11, 2006 4:38 PM > To: Maven Users List > Subject: PMD, CPD, cobertura, jdepend, etc. etc. on my project site > > I'd love to automatically have all this stuff show up on my project site. > > Currently I do the following: > > mvn site:site > mvn pmd:pmd -Dformat=html > mvn pmd:cpd -Dformat=html > mvn cobertura:cobertura -Dformat=html > mvn jdepend:generate > mvn site:deploy > > I know I'm nitpicking, but is there some way to put this into the project > file to just run all these before doing site:deploy or do I need to define a > batch file that'll call all these targets? > > > -j > > --- > Justin Fung > [EMAIL PROTECTED] > Sr. Analyst, Business Systems > IT Banking Systems, e-Business > HSBC Bank Canada > http://www.hsbc.ca > p: (604) 643-6605 > f: (604) 643-6727 > *** > This email may contain confidential information, and is intended only for the > named recipient and may be privileged. Distribution or copying of this email > by anyone other than the named recipient is prohibited. If you are not the > named recipient, please notify us immediately and permanently destroy this > email and all copies of it. Internet email is not private, secure, or > reliable. No member of the HSBC Group is liable for any errors or omissions > in the content or transmission of this email. Any opinions contained in this > email are solely those of the author and, unless clearly indicated otherwise > in writing, are not endorsed by any member of the HSBC Group. > *** > Ce courriel peut renfermer des renseignements confidentiels et privilégiés > et s'adresse au destinataire désigné seulement. La distribution ou la > copie de ce courriel par toute personne autre que le destinataire désigné est > interdite. Si vous n'êtes pas le destinataire désigné, veuillez nous en > aviser immédiatement et détruire de façon permanente ce courriel ainsi que > toute copie de celui-ci. La transmission de courriel par Internet ne > constitue pas un mode de transmission confidentiel, sécuritaire ou fiable. > Aucun membre du Groupe HSBC ne sera responsable des erreurs ou des omissions > relatives au contenu ou à la transmission de ce courriel. > L'auteur de ce courriel est seul responsable des opinions émises dans ce > courriel, lesquelles, à moins d'un avis contraire fourni par écrit, ne sont > pas endossées par aucun membre du Groupe HSBC. > *** > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Assembly Plugin Changes
Thanks. I had briefly considered it yesterday, but promptly forgot about as I attempted to remember everything else I wanted to say. I suppose this will be a chance to test out pluginManagement in the parent POM, as the current configuration for this is in several projects... -Stephen On 4/11/06, Wayne Fay <[EMAIL PROTECTED]> wrote: > I don't know much about these assembly changes etc so I can't comment > on any of that. Perhaps search the dev@ list to find more details. > > Here's another idea you might not have considered... You could find > out the version number for the old (working) assembly plugin and > specify it directly in your pom.xml as a plugin dependency... This > would allow you to keep using your old mvn assembly etc as you are > used to, without these recent changes affecting your build process. > > Not saying this is a great solution, but it might make you happier for > the short term, until these issues with assembly are worked out in a > new release. > > Wayne > > On 4/10/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: > > I know I'm a bit slow here, as it appears these changes were released > > quite a while ago. But still, I've just noticed today the issue > > (discussed before, but since I didn't realize it was affecting ME, I > > didn't pay attention!) regarding the assembly plugin forking the > > lifecycle, causing my existing setup to run everything twice because I > > have assembly attached to the package phase. > > > > I really don't get that decision. What I think I understand is that > > now you can run "mvn assembly:assembly", and you get the same behavior > > you would have gotten before running "mvn package assembly:assembly"? > > Was this "gain" really worth breaking existing builds, and now > > requiring features for the ability to run assembly:assembly and > > assembly:directory in non-lifecycle-forking mode? > > > > Also, it's really hard to tell what's going on, because the site for > > the assembly plugin doesn't seem to have been updated for quite some > > time (in fact, it still has "m2" as the Maven command, not "mvn"). > > Also, shouldn't there be somewhere in the site that states the version > > number the site is associated with? (Please indicate if these are > > known issues, or I'll plan to put them in JIRA tomorrow). > > > > My use case for the assembly plugin is this: > > > > 1) I want to be able to generate the whole thing easily in one command. > > 2) I want to use assembly:assembly to create a zip of my source. > > 3) I want to do assembly:directory to create a directory of files I > > will then upload into a another system where my file releases go. > > 4) In that directory I want the sources and javadoc jars included, as > > well as the src zip. > > > > I see where forking the lifecycle fulfills item #1 but it makes it > > very confusing for users of my project that, instead of running mvn > > with a lifecycle phase to do a release, run "assembly:assembly". I > > think this breaks the normal usage model. > > > > I haven't tested how the forking of the lifecycle works. I get the > > javadoc and sources jars to be created by passing > > -DperformRelease=true. If I run "mvn -DperformRelease=true > > assembly:assembly" will the property be passed along, causing > > javadoc:jar and source:jar to be run? If so, then that could solve 4. > > > > My solution prior to these changes in the plugin was to put > > configuration for execution of assembly:assembly and > > assembly:directory attached to the package phase into a profile > > activated by performRelease=true, and simply have the assembly be run > > when a user ran "mvn -DperformRelease=true package". > > > > What would be the right way now? Since I would need two > > configurations of the assembly plugin, I would have to have all the > > configuration on the command-line and run two separate commands. And > > how do you specify multiple descriptors on the command-line? Are > > lists comma-separated, or what? > > > > Or I guess I have to wait for another release of the assembly plugin. > > In that case would I just use newly created goals that avoid the > > forked-lifecycle and go back to how it was before, or would I only use > > the non-forking assembly:assembly in a profile, and then run > > assembly:directory from the command-line? What exactly is the new > > use-case idea here? > > > > I apologize for the lengt
Assembly Plugin Changes
I know I'm a bit slow here, as it appears these changes were released quite a while ago. But still, I've just noticed today the issue (discussed before, but since I didn't realize it was affecting ME, I didn't pay attention!) regarding the assembly plugin forking the lifecycle, causing my existing setup to run everything twice because I have assembly attached to the package phase. I really don't get that decision. What I think I understand is that now you can run "mvn assembly:assembly", and you get the same behavior you would have gotten before running "mvn package assembly:assembly"? Was this "gain" really worth breaking existing builds, and now requiring features for the ability to run assembly:assembly and assembly:directory in non-lifecycle-forking mode? Also, it's really hard to tell what's going on, because the site for the assembly plugin doesn't seem to have been updated for quite some time (in fact, it still has "m2" as the Maven command, not "mvn"). Also, shouldn't there be somewhere in the site that states the version number the site is associated with? (Please indicate if these are known issues, or I'll plan to put them in JIRA tomorrow). My use case for the assembly plugin is this: 1) I want to be able to generate the whole thing easily in one command. 2) I want to use assembly:assembly to create a zip of my source. 3) I want to do assembly:directory to create a directory of files I will then upload into a another system where my file releases go. 4) In that directory I want the sources and javadoc jars included, as well as the src zip. I see where forking the lifecycle fulfills item #1 but it makes it very confusing for users of my project that, instead of running mvn with a lifecycle phase to do a release, run "assembly:assembly". I think this breaks the normal usage model. I haven't tested how the forking of the lifecycle works. I get the javadoc and sources jars to be created by passing -DperformRelease=true. If I run "mvn -DperformRelease=true assembly:assembly" will the property be passed along, causing javadoc:jar and source:jar to be run? If so, then that could solve 4. My solution prior to these changes in the plugin was to put configuration for execution of assembly:assembly and assembly:directory attached to the package phase into a profile activated by performRelease=true, and simply have the assembly be run when a user ran "mvn -DperformRelease=true package". What would be the right way now? Since I would need two configurations of the assembly plugin, I would have to have all the configuration on the command-line and run two separate commands. And how do you specify multiple descriptors on the command-line? Are lists comma-separated, or what? Or I guess I have to wait for another release of the assembly plugin. In that case would I just use newly created goals that avoid the forked-lifecycle and go back to how it was before, or would I only use the non-forking assembly:assembly in a profile, and then run assembly:directory from the command-line? What exactly is the new use-case idea here? I apologize for the lengthe here, but I found the experience quite frustrating. I know I saw several e-mails about either infinite-loops or just the repeated-builds after these changes were released, but did I just miss my opportunity (here or on the dev list) to comment on these changes before they were made? -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [2.0.3] scp with password in settings.xml still needs type in pwd
Due to a server change/security settings change, I now use sftp://, but had previously used scp:// with success. -Stephen On 4/10/06, Roland Kofler <[EMAIL PROTECTED]> wrote: > Hi, I use scp://... andI believe this is a standard java SCP that > is part of maven dist. I don't want to use a native SCP because we > develop in a heterogenous environment. Also my aim is to produce as > minimal configuration hassle as possible for my coworkers. Everybode > else use scpexe? At least the list messages almost suggest this. > > Regards, > Roland > > Jörg Schaible schrieb: > > Hi Roland, > > > > What are you using as scp? There are quite some packages, starting with > > PuTTY, native OpenSSH and Cygwin's version of it. > > > > - Jörg > > > > Roland Kofler wrote on Friday, April 07, 2006 5:44 PM: > > > > > >> Thanks again. I have a .ssh dir in my home folder. but he complains > >> aubout a password at every deploy. > >> I am so sad that I can't use full deployment fancy, plz help. > >> > >> Roland > >> > >> > >> Kaare Nilsen schrieb: > >> > >>> I have had that problem on windows, but not on unix/linux. > >>> Seems like the scp plugin thingy does not create the .ssh directory > >>> under c:\documents and settings or whatever\username > >>> So if you manually create that directory yourself and then run your > >>> stuff it should work. (well that is if you are on windows) > >>> > >>> /Kaare > >>> > >>> On 07/04/06, Roland Kofler <[EMAIL PROTECTED]> wrote: > >>> > >>> > >>>> Thanks, tried to set > >>>> > >> false , but > >> > >>>> didn't work , always promting for pwd... > >>>> > >>>> Roland > >>>> > >>>> Geoffrey De Smet schrieb: > >>>> > >>>> > >>>>> With me it works, but I remember I had to comment out > >>>>> interactiveMode is true in my settings.xml > >>>>> > >>>>> Roland Kofler wrote: > >>>>> > >>>>> > >>>>>> Really, I don't get it. Why scp still asks me for a password when > >>>>>> I have > >>>>>> > >>>>>> settings.xml: > >>>>>> > >>>>>> > >>>>>> systemone-repository > >>>>>> lalala > >>>>>> lalala > >>>>>> > >>>>>> > >>>>>> and pom.xml: > >>>>>> > >>>>>> > >>>>>> > >>>>>> systemone-repository > >>>>>> System One Repository > >>>>>> scp://development1/var/www/repository/ > >>>>>> > >>>>>> > >>>>>> Why deploy goal continues to ask me for passwords every time? > >>>>>> I don't want to use scpexe with keys and ssh-agent as I want to > >>>>>> keep configuration of developer machines as slim as possible > >>>>>> > >>>>>> strange is also that i have to set ssh-wagon-alpha-7 explicitly. > >>>>>> this should be the default for 2.0.3 not? > >>>>>> > >>>>>> thanks, > >>>>>> Roland > >>>>>> > >>>>>> > >> - > >> > >>>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>>> For additional commands, e-mail: [EMAIL PROTECTED] > >>>> > >>>> > >>>> > >>>> > >>> > >> - > >> > >>> To unsubscribe, e-mail: [EMAIL PROTECTED] > >>> For additional commands, e-mail: [EMAIL PROTECTED] > >>> > >>> > >>> > >>> > >> - > >> To unsubscribe, e-mail: [EMAIL PROTECTED] > >> For additional commands, e-mail: [EMAIL PROTECTED] > >> > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Shared projects and Maven best practice
Yes, you can override both version and scope in the child POM. -Stephen On 4/4/06, Arnaud Bailly <[EMAIL PROTECTED]> wrote: > Didn't know about this tag. This allows to > specify default characteristics for a dependency that may be overriden > by a pom ? > > > -- > Arnaud Bailly, Dr. - Ingénieur de Recherche > NORSYS > 1, rue de la Cense des Raines > ZAC du Moulin > 59710 ENNEVELIN > Tel : (33) 3 28 76 56 76 > Mob : (33) 6 17 12 19 78 > Fax : (33) 3 28 76 57 00 > Web : http://www.norsys.fr > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven runtime
There is a runtime plugin the in the mojo sandbox, but it doesn't even
seem to have a site published...
In the meantime, you can remove the version number from your artifact
by doing the following in your pom:
${project.artifactId}
-Stephen
On 4/3/06, Pierre Monestie <[EMAIL PROTECTED]> wrote:
> Hi
> I was reading somewhere that there is a runtime plugin aimed at
> providing a declarative mechanism for describing runtime enviroment.
> Does this work yet?
>
> My problem is that I run mvn assembly:directory and I couldn't find a
> way to rename my artifact so that the version number would be removed.
> (There is a way to remove that from the depending artifacts, but not
> the artifact itself). I therefore have to go and manually edit my .bat
> file.
>
> Anyone has a suggestion to easily create a launch file for my application?
>
> Thanks,
> Pierre
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Stephen Duncan Jr
www.stephenduncanjr.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
