from:"muhwas"

mvn dependency:unpack

2007-03-20 Thread muhwas

hi,

Can somebody please explain me how mvn
dependency:unpack works because i am trying to run
tuscany-incubating-M2 samples. when i run mvn
dependency:unpack i am getting 

[INFO]

[INFO] One or more required plugin parameters are
invalid/missing for 'dependen
y:unpack'

[0] inside the definition for plugin:
'maven-dependency-plugin'specify the foll
wing:

configuration
  ...
  artifactItemsVALUE/artifactItems
/configuration.


I found on the list that i have to include 

plugin
  groupIdorg.apache.maven.plugins/groupId
 
artifactIdmaven-dependency-plugin/artifactId
  version2.0-alpha-1/version
  executions
execution
  idunpack/id
  phasepackage/phase
  goals
goalunpack/goal
  /goals
  configuration
 artifactItems
  artifactItem
  groupIdmyModule/groupId
artifactIdmyArtifactId/artifactId
   version1.0-SNAPSHOT/version
typejar/type
  overWritefalse/overWrite
 
outputDirectory${project.build.directory}/outputDirectory
 /artifactItem
/artifactItems
  /configuration
/execution
  /executions
/plugin

in the plugins section in pom.xml file. but i what
to know how do i know what plug-ins to unpack?

regards,
muhwas

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

RE: mvn dependency:unpack

2007-03-20 Thread muhwas

thank you for your reply but i am still getting same
eror. could you please let me know what i am doing
wrong.

thanks


--- Brian E. Fox [EMAIL PROTECTED] wrote:

 I recently enhanced the plugin page to cover this
 specifically:

http://maven.apache.org/plugins/maven-dependency-plugin/faq.html
 
 -Original Message-
 From: muhwas [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, March 20, 2007 4:09 PM
 To: users@maven.apache.org
 Subject: mvn dependency:unpack
 
 hi,
 
 Can somebody please explain me how mvn
 dependency:unpack works because i am trying to run
 tuscany-incubating-M2 samples. when i run mvn
 dependency:unpack i am getting 
 
 [INFO]


 [INFO] One or more required plugin parameters are
 invalid/missing for 'dependen
 y:unpack'
 
 [0] inside the definition for plugin:
 'maven-dependency-plugin'specify the foll
 wing:
 
 configuration
   ...
   artifactItemsVALUE/artifactItems
 /configuration.
 
 
 I found on the list that i have to include 
 
 plugin

 groupIdorg.apache.maven.plugins/groupId

 artifactIdmaven-dependency-plugin/artifactId
 version2.0-alpha-1/version
 executions
   execution
 idunpack/id
 phasepackage/phase
 goals
   goalunpack/goal
 /goals
 configuration
artifactItems
 artifactItem
 groupIdmyModule/groupId
   artifactIdmyArtifactId/artifactId
  version1.0-SNAPSHOT/version
   typejar/type
 overWritefalse/overWrite


outputDirectory${project.build.directory}/outputDirectory
/artifactItem
   /artifactItems
 /configuration
   /execution
 /executions
   /plugin
 
 in the plugins section in pom.xml file. but i what
 to know how do i know what plug-ins to unpack?
 
 regards,
 muhwas
 

-
 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]
 
 
?xml version=1.0 encoding=UTF-8?
!--
 * Licensed to the Apache Software Foundation (ASF) under one
 * or more contributor license agreements.  See the NOTICE file
 * distributed with this work for additional information
 * regarding copyright ownership.  The ASF licenses this file
 * to you under the Apache License, Version 2.0 (the
 * License); you may not use this file except in compliance
 * with the License.  You may obtain a copy of the License at
 * 
 *   http://www.apache.org/licenses/LICENSE-2.0
 * 
 * Unless required by applicable law or agreed to in writing,
 * software distributed under the License is distributed on an
 * AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
 * KIND, either express or implied.  See the License for the
 * specific language governing permissions and limitations
 * under the License.
--
project
parent
groupIdorg.apache.tuscany.sca.samples/groupId
artifactIdparent/artifactId
version1.0-incubator-M2/version
/parent
modelVersion4.0.0/modelVersion
artifactIdsample-helloworldwsclient/artifactId
packagingjar/packaging
nameTuscany HelloWorld Web Service Client Sample/name
descriptionA sample client for a HelloWorld Web Service./description

dependencies

dependency
groupIdcommonj/groupId
artifactIdsdo-api-r2.0.1/artifactId
version${sdoVersion}/version
scopecompile/scope
/dependency
dependency
groupIdorg.osoa/groupId
artifactIdsca-api-r0.95/artifactId
version${scaVersion}/version
scopeprovided/scope
/dependency
dependency
groupIdorg.apache.tuscany.sca.kernel/groupId
artifactIdtuscany-api/artifactId
version${scaImplVersion}/version
scopeprovided/scope 
/dependency
dependency
groupIdorg.apache.tuscany.sca.kernel/groupId
artifactIdcore/artifactId
version${scaImplVersion}/version
scopeprovided/scope
/dependency
dependency
groupIdorg.apache.tuscany.sca.services.bindings/groupId
artifactIdaxis2/artifactId
version${scaImplVersion}/version
scopeprovided/scope
/dependency

dependency
groupIdorg.apache.tuscany.sca/groupId
artifactIdtest/artifactId

RE: mvn dependency:unpack

2007-03-20 Thread muhwas

Hi Brain,

I am trying to run Tuscany samples. I am following
their instructions. According to instruction they said
go to sample directory and run mvn and when built
successfully run mvn dependency:unpack. This will
create target\distribution folder and copy tuscany run
time enviornment. But when i am running mvn
dependency:unpack and getting error.

[0] inside the definition for plugin:
 'maven-dependency-plugin'specify the foll
 wing:

 configuration
   ...
   artifactItemsVALUE/artifactItems
 /configuration.

They didn't specify any thing what to put in
articactsItems. I also posted this question on tuscany
mailing list but no response so i thought may be i can
get help from maven list.

thank you,
muhwas

--- Brian E. Fox [EMAIL PROTECTED] wrote:

 Wayne, 
 I think you could be right. It's also possible
 though that the pom isn't
 intended to be run using 'mvn dependency:unpack' (I
 haven't looked at
 their site) because the pom is setup correctly to
 unpack during the
 package phase. I know this issue is a tricky one
 because the first time
 someone reported it, it took me quite a while to
 track it down. That's
 why I wrote the faq entry but maybe it's not clear
 enough. I'll have to
 look at it some more to see if I can present a more
 clear answer.
 
 --Brian
 
 -Original Message-
 From: Wayne Fay [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, March 20, 2007 9:13 PM
 To: Maven Users List
 Subject: Re: mvn dependency:unpack
 
 I think the primary problem is that muhwas is, in
 all likelihood, very
 new to Maven and so all the information you provide
 on the FAQ will
 probably be mostly insufficient to help him fix this
 issue. He simply
 lacks the base level of Maven knowledge to make the
 correct decisions
 about what goes in artifactItems and what does not.
 
 So, I think bouncing this support request over to
 the appropriate
 party is probably more reasonable. Someone in the
 Tuscany project (who
 created this pom in the first place) is probably the
 one who should
 fix the problem.
 
 Wayne
 
 On 3/20/07, Brian E. Fox [EMAIL PROTECTED]
 wrote:
  The problem is exactly as the faq describes.
 Perhaps I need to clarify
  some more in the faq... When you invoke a plugin
 from the cli that has
  configuration in the pom, that configuration must
 _not_ be contained
  inside an executions tag. I really think we need
 to look at changing
  that because it causes lots of user confusion
 (this is a maven thing,
  not a dependency plugin thing). Take a look at the
 second example on
 the
  usage page:
 
  If you intend to configure this mojo for execution
 on the command line
  using:
 
  mvn dependency:copy
 
  you must not put the configuration inside the
 executions tag. Your
  configuration should look like this:
 
  project
[...]
build
 plugins
   plugin
 
 groupIdorg.apache.maven.plugins/groupId
 
 artifactIdmaven-dependency-plugin/artifactId
  configuration
artifactItems
  artifactItem
groupId[ groupId ]/groupId
artifactId[ artifactId
 ]/artifactId
version[ version ]/version
type[ packaging ]/type
overWrite[ true or false
 ]/overWrite
outputDirectory[ output directory
 ]/outputDirectory
destFileName[ filename
 ]/destFileName
  /artifactItem
/artifactItems
!-- other configurations here --
  /configuration
/plugin
  /plugins
/build
[...]
  /project
 
  -Original Message-
  From: muhwas [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, March 20, 2007 5:18 PM
  To: Maven Users List; Brian E. Fox
  Subject: RE: mvn dependency:unpack
 
  thank you for your reply but i am still getting
 same eror. could you
  please let me know what i am doing wrong.
 
  thanks
 
 
  --- Brian E. Fox [EMAIL PROTECTED]
 wrote:
 
   I recently enhanced the plugin page to cover
 this
   specifically:
  
 

http://maven.apache.org/plugins/maven-dependency-plugin/faq.html
  
   -Original Message-
   From: muhwas [mailto:[EMAIL PROTECTED]
   Sent: Tuesday, March 20, 2007 4:09 PM
   To: users@maven.apache.org
   Subject: mvn dependency:unpack
  
   hi,
  
   Can somebody please explain me how mvn
 dependency:unpack works
   because i am trying to run
   tuscany-incubating-M2 samples. when i run mvn
 dependency:unpack i
 am
 
   getting
  
   [INFO]
  
 


   [INFO] One or more required plugin parameters
 are invalid/missing
 for
   'dependen y:unpack'
  
   [0] inside the definition for plugin:
   'maven-dependency-plugin'specify the foll
   wing:
  
   configuration
 ...
 artifactItemsVALUE/artifactItems
   /configuration.
  
  
   I found on the list that i have to include
  
   plugin
  
   groupIdorg.apache.maven.plugins/groupId
  
   artifactIdmaven-dependency-plugin/artifactId

mvn dependency:unpack

RE: mvn dependency:unpack

RE: mvn dependency:unpack

3 matches

Site Navigation

Mail list logo

Footer information