Re: pom builds empty jar, but only on release:perform
Hi,
check connection and developerConnection elements in your pom.xml.
Typically it points to real SVN path, not tags directory. Both
release goals
works with these settings instead of SVN path in your current working copy.
Martin Schayna
C. Benson Manica wrote:
Hi, I have a simple POM that can build package, deploy, and
release:prepare, but on release:perform it deploys an empty jar. The
SVN labels also have no files associated with them. Contents of POM
follow...
project xmlns=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;
modelVersion4.0.0/modelVersion
groupIdcom.cnn/groupId
artifactIdelection-api/artifactId
packagingjar/packaging
version1.1-SNAPSHOT/version
nameelection-api/name
urlhttp://maven.apache.org/url
scm
connectionscm:svn:
http://ide-svn.turner.com/svn/cnn/election/trunk/components/tags
/connection
developerConnectionscm:svn:
http://ide-svn.turner.com/svn/cnn/election/trunk/components/tags
/developerConnection
/scm
distributionManagement
repository
idide-artifactory-release/id
nameIDE Artifactory Release/name
urlhttp://ide-svn.turner.com/artifactory/libs-releases-local
/url
/repository
snapshotRepository
idide-artifactory-snapshot/id
nameIDE Artifactory Repository/name
urlhttp://ide-svn.turner.com/artifactory/libs-snapshots-local
/url
/snapshotRepository
/distributionManagement
dependencies
dependency
groupIdlog4j/groupId
artifactIdlog4j/artifactId
version1.2.14/version
typejar/type
scopecompile/scope
/dependency
dependency
groupIdcom.intellij.idea/groupId
artifactIdannotations/artifactId
version8.1.3/version
/dependency
dependency
groupIdcom.cnn/groupId
artifactIdelection-core/artifactId
version1.0/version
/dependency
/dependencies
build
finalName${pom.artifactId}-${pom.version}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.6/source
target1.6/target
/configuration
/plugin
/plugins
/build
/project
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Configuring source plugin to skip execution
Hello Maven users, Is there a way to configure source plugin to skip execution for a single module, or at least not to fail build because module doesn't contain any sources? In my project source plugin is being run by release plugin's perform goal (with default useReleaseProfile=test parameter value), and it fails a build because a war module has no sources. That war module just depends on a jar module and is used to start spring application context from that jar in web application container. Temporary workaround was to set useReleaseProfile to false but this skips releasing source and javadoc for all modules. Not sure if configuring release plugin not to useReleaseProfile for that war module only would do the trick. Regards, Stevo.
Struts 2 archetypes
Hi, Looks like the Struts2 snapshot archetypes are removed from the internal catalog: http://jira.codehaus.org/browse/ARCHETYPE-199 Is there a way I can add them to my internal archetypes to be able to use them in the archetype:generate interactive mode? Thanks in advance - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: system scoped dependencies are attempted to be downloaded
Ok. In the future, it would be great if you include this kind of info when you ask about a problem. You need to provide all info for us to be able to help. /Anders On Fri, Nov 6, 2009 at 23:47, EJ Ciramella ecirame...@upromise.com wrote: Yeah, we have a pretty out-of-the-ordinary build process using jboss/atg/etc. Try this - zip up any jar and try to both unpack that AND put that jar as a dependency with a system scope. This won't work. It will try to resolve the dependency and fail so it never unpacks the zip. -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Friday, November 06, 2009 4:20 PM To: Maven Users List Subject: Re: system scoped dependencies are attempted to be downloaded Sorry, I don't know. I take it your setup is a little bit more complicated than your initial posts indicated? /Anders On Fri, Nov 6, 2009 at 22:12, EJ Ciramella ecirame...@upromise.com wrote: Hmm - here's a question - if the jar I'm looking for exists inside a zip file that needs to be downloaded, unpacked and then and only then will systemPath actually point at a jar - will that fail? When does dependency resolution happen - at the validate stage? If so, the zip won't be downloaded and unpacked by then resulting in a systemPath that doesn't exist. -Original Message- From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Friday, November 06, 2009 3:41 PM To: Maven Users List Subject: Re: system scoped dependencies are attempted to be downloaded And you have tried the very simplest project, containing just the dependencies section with just this dependency? And no parent pom which could hide something not obvious. For example, use the quickstart archetype. Also, have you tried it in a different environment (computer)? If that still reproduces the issue, I suggest you create a jira and attach that project. /Anders On Fri, Nov 6, 2009 at 21:33, EJ Ciramella ecirame...@upromise.com wrote: We're not using a version range. The numbers I'm speaking of below is the range of maven 2 versions I tried and had this problem. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Friday, November 06, 2009 3:29 PM To: Maven Users List Subject: Re: system scoped dependencies are attempted to be downloaded It's simple - if you have a dependency with a system scope, maven 2.0.9 - 2.2.1 tries looking up that dependency in any repos you may have mapped. Shouldn't it just skip that part? What happens when you change the version range to a fixed value eg 2.1.3 or [2.1.3]? Or if you remove the version stanza entirely since it does not apply to system scoped artifacts? Wayne - 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
